I like to track the frequency of a FT817 to compensate the Doppler shift with Gpredict but I cannot get them communicate via CAT.

The FT817 does work fine with FLrig and FLdigi via CAT.

Any suggestions on how to get this running?

73' Ron
ON2RON

开云体育

Then from gpredict:

开云体育

I forgot to specify on my previous email (I pasted from my notes), that is because I chose to stop trying to to figure it out. Often software upgrades broke the functionality and for some reason the person who writes rigctl is a wizard that always gets that right. I use it instead of direct serial from some apps.

I had it running, but with another cmd line, but it stopped after a short time. I give your solution a try later today.

73' Ron - on2ron

Using N3RDR’s rigctl line, on my rpi 4 and version it’s device 1020 and I have a baud rate of 4800, it worked great.

Followup question: I’m trying to use gpredict to track sat frequencies, but I want to run FT4 using wsjtx or something else. ?Anyone know how to allow one program to control CAT (gpredict) and yet allow transmit/receive control as well?

Right now gpredict and wsjtx are “battling” for control of the FT-817. I am using an xggcomms digi 2 cable for cat/audio interface to the FT-817.

Seems like somehow I should be able to make this work, but I haven’t found the secret sauce yet.

Rob KA2CZU

Trying to get gpredict and wsjtx to work together. Using the rigctl command above (with a different port # and baud rate) seems to work fine in gpredict. I had read that for rigctl to be used by WSJTX you have to select that as the “rig” in the radio config tab. However, it’s a Hamlib/rigctl line and now I’m getting a hamlib protocol error (even though gpredict is working fine, and also choosing FT817 in WSJTX seems to work … but by itself…gpredict and WSJTX seem to fight with each other if both are running while “FT817” is selected in WSJTX).

Any thoughts appreciated.

Rob KA2CZU