When upgrading to version 2.7.0 I can no longer control my Icom R8600. It was working with earlier versions (2.6.1).
I am running Windows 10 Pro. The program starts and shows the current radio frequency. (This seems to be the case whether I start the program with the radio in the VFO mode or memory mode - it has never mattered before.) When I use the frequency drop down box the frequency does not change. When I try again I get a Rig Control Error box with details: > Hamlib error: > icom.c(9652):set_vfo_curr returning2(-9) Command rejected by the rig > > icom.c(1595):icom_set_freq returning2(-9) Command rejected by the rig > > rig_set_cache_freq(171): vfo=VFOA, current_vfo=currVFO > rig_set_freq: vfo=VFOA, save=currVFO > *rig.c(2410) trace > **2:rig.c(3333):rig_set_vfo entered > rig_set_vfo called vfo=currVFO > vfo_fixup:(from rig_set_vfo:3347) vfo=currVFO, vfo_curr=currVFO, split=0 > vfo_fixup: Leaving currVFO alone > **2:rig_set_vfo: elapsed=0ms > **2:rig.c(3352):rig_set_vfo returning(0) > *1:rig_set_freq: elapsed=31ms > rig_lock: client lock disengaged > *1:rig.c(2416):rig_set_freq returning(-9) Command rejected by the rig > > Command rejected by the rig > Command rejected by the rig > while setting frequency > > Timestamp: 2025-04-15T16:31:36.050Z When reverting to the previous hamlib version, but still running WSJT-X version 2.7.0 I have the same problem. I might note the current FLDIGI embedded hamlib version works, to a point. I can always set the frequency from the radio, but when I vary the frequency from the radio, FLDIGI only follows it for a few changes, then the display (on the program, not the radio) locks up. 73, Chris NX0E _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel