[wsjt-devel] WSJT-X Hamlib Rig Failure - command rejected by the rig

[Bob M. <EM...@W1...>]

Last weekend was at Frank NC1I QTH and working with WSJT-X, which we have been running for a couple of weeks since the call for EMEers to migrate to Q65.

We ran into a problem with rig control though - I attempted to post using web based email from Frank's but the email alias I use for this list was overwritten and the posts rejected.  I've finally sorted that out and am back.  Unfortunately the orig post seems to have been lost (not in sent items or available on listserv).

Setup has not changed in years and worked fine with WSJT 10.  K3s rig in data mode is connected to microKEYER II interface.  One COM port is used for CAT and a second COM port for RTS PTT.

The last RC is when the issue started and we updated to WSJT-X v2.5.0 and it continues.  When transmitting sometimes an error pops up (I'll have to grab the screen shot of the error from the station computer later).  While it seems one can get by the error the operating frequency returns to the 23cm default - bad news if you're not watching what is going on.

While this happens during automatic sequencing of messages we can also reproduce it by using settings and clicking the PTT on / off / on / etc.

I did have a copy of the wsjtx_syslog file which is attached.  Within that file is the info that is also displayed in a pop-up window in WSJT - like this (extracted from the file):

k3.c(1171):k3_set_mode return(-9)
rig_set_mode: targetable retcode after set_mode=-9
rig.c(2200):rig_set_mode return(-9)
[SYSLOG][2021-06-06 09:55:57.447863][23:11:31.459795][error] handle_transceiver_failure: reason: Hamlib error: Command rejected by the rig
k3.c(1171):k3_set_mode return(-9)
rig_set_mode: targetable retcode after set_mode=-9
rig.c(2200):rig_set_mode return(-9) while setting current VFO mode

I will be at NC1I on Friday and Saturday (and possibly Sunday AM local time) and glad to gather any additional info or make adjustments as recommended.

Bob W1QA