¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

K2 PTT and mode issue with WSJT-X


 

Hey folks...
I was having the same problem as in this thread:
?
I have been using WSJT-X with the K2 without DXLab for some time - no issue.? After configuring WSJT-X to have DXLab control the rig (log contacts etc.), I had the same weird PTT issue as reported in the above thread.? I fixed it by changing the PTT method to RTS with a com port (I'm using the Timewave Navigator as the interface so I can have 2 com ports for the rig: one for CAT and one for PTT).? That fixed the quick PTT problem.
?
The next problem is rig mode.? Using WSJT-X alone, the Mode was set to Data/Pkt and the K2 went into the RTTY-R data mode which works great.? After combining with DXLab, the rig Mode switches to USB.? I switch it back in Commander, but as soon as the K2 transmits, the mode is returned to USB.
?
What settings am I missing?
?
Hank
K4HYJ


 

+ AA6YQ comments below

The next problem is rig mode. Using WSJT-X alone, the Mode was set to Data/Pkt and the K2 went into the RTTY-R data mode which works great. After combining with DXLab, the rig Mode switches to USB. I switch it back in Commander, but as soon as the K2 transmits, the mode is returned to USB.

+ On the Radio tab of WSJT-X's Setting window, set the Mode to "Data/Pkt".

73,

Dave, AA6YQ


 

Thanks Dave for the quick reply!
?
I've done that but after transmitting one time it changes to USB.? Commander shows USB, WSJT-X shows Data/Pkt.? Changing between USB and Data/Pkt in WSJT-X makes no change on the K2.? I can change the mode via Commander, but again after transmitting, it changes back to USB.
?
What should I try next?
?
Hank
K4HYJ


 

+ AA6YQ comments below


I've done that but after transmitting one time it changes to USB. Commander shows USB, WSJT-X shows Data/Pkt. Changing between USB and Data/Pkt in WSJT-X makes no change on the K2. I can change the mode via Commander, but again after transmitting, it changes back to USB.

+ Please do the following:

1. on the General tab of Commander's Configuration window, check the "Log debugging info" box

2. terminate Commander

3. start Commander

4. configure WSJT-x to use Commander for rig control with the mode set to Data/Pkt

5. wait 10 seconds

6. on a clear frequency with minimum power, direct WSJT-X to transmit

7. confirm that the mode changes to USB

8. on the General tab of Commander's Configuration window, uncheck the "Log debugging info" box

9. attach the errorlog.txt file from your Commander folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


 

Dave...
File sent!
?
Hank


 

+ AA6YQ comments below

Dave...
File sent!

+ The errorlog you sent me shows your transceiver rejecting valid commands from Commander:

2025-01-27 00:39:41.194 > CIVModule.DisplayLine: Port = P, Asc = ?;

2025-01-27 00:39:41.363 > CIVModule.DisplayLine: Port = P, Asc = ?;

+ That could be RFI, or some other problem with the COM port.

Dave