Elecraft K4 Data mode not working

[mdblack98]

I'm afraid the Hamlib support for the K4 has regressed in WSJT-X 2.5 compared to WSJT-X 2.5rc5 that I last tested in August. The Hamlib release distributed with WSJT-X 2.5 does NOT work well with the K4 now, because it's using DT0; instead of DT$0; to set the SubRx mode to DATA. The X command works, the K command does not.

Log attached. Summary below:

Initial conditions: both VFOs in FSK mode (MD6;MD$6;DT2;DT$2;)

rigctl-wsjtx.exe -m 2047 -s 38400 -r COM5

Rig command: k
TX Frequency: 14080000
TX Mode: RTTY
TX Passband: 800

Rig command: K 14074000 PKTUSB 2800
TX Passband:
Rig command: k
TX Frequency: 14074000
TX Mode: PKTUSB
TX Passband: 800

Rig command: w dt;dt$;
Reply: DT0;DT$2; !!!!!!!!!!!!! It changed VFO A to DATA instead of VFO B.

(I put both VFOs back into FSK mode, then checked status):

Rig command: w dt;dt$;
Reply: DT2;DT$2;

Rig command: S 0 VFOB

Rig command: k
TX Frequency: 14080000
TX Mode: RTTY
TX Passband: 250

Rig command: m
Mode: RTTY
Passband: 300

Rig command: K 14074000 PKTUSB 2800
TX Passband:
Rig command: w dt;dt$;
Reply: DT0;DT$2; !!!!!!!!!!!

Rig command: m
Mode: PKTUSB
Passband: 2800

Rig command: k
TX Frequency: 14074000
TX Mode: PKTUSB
TX Passband: 800

73,
Bob, N6
rigctlK4Log22.txt
TV

[mdblack98]

This version works better. It still flashes a lot of stuff including the ER59 message while it is changing things, but it eventually (most of the time) turns SPLIT ON and moves both VFOs to DATA mode, after cycling through many other things like FSK mode.

However, the 3rd band change popped up a "Rig Control Failure," which I had not seen before. I repeated the band change tests with no logging enabled and still got the error occasionally. The RETRY button worked.

Log attached (doesn't include the RETRY click).

I think the K4 may not respond to certain commands while it is in the middle of doing things, or some additional delays are needed now? Not sure. WSJT-X certainly seems to be sending way more commands than required to change bands and put both VFOs into DATA mode and enable split. This command all on one line runs fast, produces no errors.

FA21074;FB21073;MD6;MD$6;DT0;DT$0;FT1;

[mdblack98]

Working now but getting ER59 on WSJTX startup. Would like to fix that.

[mdblack98]

Getting better. Harder to reproduce the ER59 now. Still got one, right after the switch to 28 MHz, which was in CW mode (both VFOs). In the log, search for FA00028074000; you'll see WJST-X send MD; and DT$; commands instead of and MD$; and DT$; So it fails to switch VFO B with an AB3; or MD$6; before turning split ON (FT1;), which causes ER59, though it eventually gets VFO B set to DATA mode. DT$0; does not mean the K4 is in DATA mode unless MD$6; is also returned.

The message "mode/width no change, skipping" is logged because the code is mislead by the results of MD; instead of MD$;, then it issues the FT1; with VFO B still in CW mode.

73,
Bob, N6TV