¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Rig control with Gpredict #ft817 #rpi


 

I'm trying to persuade Gpredict to control my FT-817 to no avail. When I open the Radio Control menu, it shows pretty Doppler corrections that it simply won't send to the radio. When I invoke rigctl and ask for the frequency, it looks like this:

pi@aramis:~ $ rigctl -l | grep FT-817? 1020? Yaesu? ? ?FT-817? ? ?20201015.0? ? ? Stable? ? ? RIG_MODEL_FT817
pi@aramis:~ $ rigctl -m 1020 -r /dev/ttyUSB0
?
Rig command: f
get_freq: error = Communication timed out
rig.c(2090):rig_get_freq return(-5)
rigctl_parse.c(1998):rigctl_get_freq return(-5)
rigctl_parse: vfo_opt=0
?
Rig command: q
pi@aramis:~ $ rigctl -m 1020 -r /dev/ttyAMA0
?
Rig command: f
get_freq: error = Communication timed out
rig.c(2090):rig_get_freq return(-5)
rigctl_parse.c(1998):rigctl_get_freq return(-5)
rigctl_parse: vfo_opt=0
?
Rig command: q
pi@aramis:

The lights on my USB/serial adapter don't do anything. Nothing does anything. I believe that rigctl isn't seeing my adapter at all. Yet, flrig and fldigi work perfectly using the same adapter.

Any suggestions?

Joe KB6WIJ


 

I should have mentioned... RPi4, BAP 3.0.8, and a FT817. Everything is a new fresh install.


 

You also need to verify that the baud rate is set in the rigctl statement and that it matches what you have set on the radio. I don't have my 817 in front of me but I believe it is called the CAT RATE in the 817 menu. Off the top of my head, so take with a grain of salt:
rigctld -m 1020 -r /dev/ttyUSB0 -s 4800
where -s sets the rate.

--
73, de KM4ACK
|
|


 

Thanks, Jason! That works. Now I just have to find out why it's ignoring Gpredict.

Joe KB6WIJ