Re: [wsjt-devel] Net Hamlib - Mode None Should Not Query Existing Mode

[Kari S. <kai...@gm...>]

Hi Logan,

On 6/1/25 07:15, hobbies.wwsma--- via wsjt-devel wrote:
> Program Version: WSJT-X Improved v2.8.0 250501
> OS: Arch Linux
>
> Problem: When using, "Rig: Hamlib NET rigctl" to connect to rigctld 
> daemon for the FT-736R, WSJT-X bails out when rig_get_mode returns -11 
> for CAT control.
>
> The FT-736R is essentially write-only for CAT control and doesn't 
> support being asked what modes it supports. I have set mode to None, 
> but WSJTX still insists on querying the mode. If I use telnet to 
> connect to the rigctld daemon, I can PTT and set frequencies just fine.
>
> If I set WSJT-X to use the FT-736R directly, everything works just 
> fine with no hamlib errors, but modes don't work (as expected).
>
> Ideally, if none is set for mode, the existing mode shouldn't be 
> queried either.
>
> Thanks,
> Logan

Perhaps hamlib provided with you disto is too old? What is the driver version for FT-736?
In my Linux Mint 21.1 system it is 4 years old:

$ rigctl -l | grep FT736R
   1010  Yaesu                  FT-736R20210221.0       Stable      RIG_MODEL_FT736R

This version bails out when asked for mode:
$ rigctl -m 1010

Rig command: m
get_mode: error = Feature not available
rig.c(2328):rig_get_mode entered
rig.c(2344):rig_get_mode return(-11)
rigctl_parse.c(2150):rigctl_get_mode return(-11)


In the hamlib that comes with WSJT-X source package, version is more recent:
$ ./rigctl-wsjtx -l | grep FT736R
   1010  Yaesu                  FT-736R20240921.0       Stable      RIG_MODEL_FT736R

This version is happy to report mode ( it is empty because I have no rig connected, but no error ):
$ ./rigctl-wsjtx -m 1010

Rig command: m
Mode:
Passband: 2200

Are you able to compile WSJT-X locally from source tarball?
If so, then you could try what happens if you use*rigctld-wsjtx*  in stead of system rigctld.

73's de Kari, oh2gqc