2014-07-27 Setting CTCSS tones on the Yaesu FT-857 while gpredict is running 5 years ago
This evening I tried another pass of the SO-50 amateur radio satellite. It wasn't as high as the afternoon pass, only 66⁰ maximum elevation. The experiences from the afternoon pass learned me to search around a bit for the downlink signal. I did not hear a lot of activity, it almost sounded to me like the transponder wasn't "armed" with the 74.4 Hz ctcss tone. This tone activates the transponder for 10 minutes, but to actually use the transponder you need to use a 67.0 Hz ctcss tone. Switching tones on the fly isn't easy when the FT-857 is controlled by gpredict, so I'll either have to control that via the computer assisted tuning (CAT) interface and rigctld or temporary switch to manual and use the memory in the FT-857 which has the different ctcss tone. Browsing the rigtctl(1) manpage suggests a script which can set ctcss tones is quite doable. Update: Indeed, it can be done. Hamlib can't read the current ctcss tone, but it can set it on this radio. Model 2 in rigctl is the connection to a running rigctld on localhost.koos@machiavelli:~$ rigctl -m 2 -h Usage: rigctl [OPTION]... [COMMAND]... Send COMMANDs to a connected radio transceiver or receiver. .. Commands (some may not be available for this rig): .. C: set_ctcss_tone (CTCSS Tone) c: get_ctcss_tone () D: set_dcs_code (DCS Code) d: get_dcs_code () ?: set_ctcss_sql (CTCSS Sql) ?: get_ctcss_sql () ?: set_dcs_sql (DCS Sql) ?: get_dcs_sql ()and it works:koos@machiavelli:~$ rigctl -m 2 C 744 koos@machiavelli:~$ rigctl -m 2 C 670 koos@machiavelli:~$And the ctcss frequency on the radio indeed changes with what I set. And I can do this while gpredict is tuning the radio.