6700 with WSJT-X Somertimes Stays in TX

jerry stern

Have been running my 6700 (v2.49) with latest version (Windows 10) of WSJT-X and JAlert.  CAT control is through DXLabs Commander.  All works well 99% but at least once per every hour or so after WSJTX completes TX, the 6700 remains in TX.  I have not seen this with SSB or RTTY but the number of RX-TX cycles on FT8 have far exceeded other modes recently.  HOw can I tell if this is a 6700 relay issue or software CAT issue?

Steven WA8Y

Its most likely an RF problem. When RF gets into control lines. Try to shorten control lines by wrapping them around ferrite to choke RF.

jerry stern

Ted VE3TRQ

Are you using CAT for PTT, or control lines on the serial port? Also, I wonder if there is some way for a message from wsjt-x thru DXLabs to get lost - in this case the TX off (de-assert PTT) command. Are there any other instances of apparent loss of commands to the radio? i.e. not going into TX (assert PTT) when you expect it to>

jerry stern

No control lines.. both my 6700 and PC are hardwired to same router and use SmartSDR (not Smartlink) IP clients to talk to each other.  So WSJTX or WinWarbler or MMTY all use software control for PTT/CAT.  SInce I use DXLabs for logging, it was recommended to let DXLab's Commander software act as the interface between WSJTX/JTAlert so I get auto-logging.  Works great 99% but I was concerned whether it could be a sign of an issue in the 6700 as my warranty is soon coming to an end.   

Kevin

Kevin

JTAlert logs to DXKeeper just fine. There's a whole setup in the JTAlert settings to get it to work exactly how you want it to work. I can share my settings if that is helpful.

jerry stern

Kevin

I think it is mostly JTAlert settings to get the log over to DXKeeper. I believe there's one setting in WSJT-X (or JTDX) that allows you to autolog or confirm before logging. Then JTDX to setup the interaction with DXLab Suite.



Kev

jerry stern