6700 with WSJT-X Somertimes Stays in TX

  • 1
  • Question
  • Updated 7 months ago
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?
Photo of jerry stern

jerry stern

  • 20 Posts
  • 12 Reply Likes

Posted 7 months ago

  • 1
Photo of Steven Linley

Steven Linley

  • 401 Posts
  • 68 Reply Likes
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.
Photo of jerry stern

jerry stern

  • 20 Posts
  • 12 Reply Likes
Only "external" line in/out of my 6700 is the internet cable and that is already has two big ferrites on each end of the 6' cable (I think this shipped with 6700).   Could it be a sticky relay in the 6700?   
Photo of Ted  VE3TRQ

Ted VE3TRQ

  • 580 Posts
  • 205 Reply Likes
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>
Photo of jerry stern

jerry stern

  • 20 Posts
  • 12 Reply Likes
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.   
Photo of Kevin

Kevin

  • 931 Posts
  • 271 Reply Likes
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.
Photo of Kevin

Kevin

  • 931 Posts
  • 271 Reply Likes
One way to eliminate DXLabs commander from the possible problems is to set WSJT-X (or JTDX) up so that the Rig is FlexRadio 6xxx rather than Commander. This doesn't have any impact on how anything works other than WSJT is sending the cat commands directly to the radio instead of an intermediary program.

My setup:
Rig: FlexRadio 6xxx
Poll Interval: 1s
Network Server: 127.0.0.1:60000 (have to set up 60000 or whatever you choose as CAT port in SmartSDR CAT)
PTT Method: CAT
Mode: None
Split Operation: None (or Fake It)

I've never experienced PTT getting locked.

73,
Kev K4VD

Photo of jerry stern

jerry stern

  • 20 Posts
  • 12 Reply Likes
Thanks Kevin,  Are the settings you list for WSJTX or JTAlert?  I will try to get rid of Commander as the middle-man and see how that works.

73 Jerry NY2KW
Photo of Kevin

Kevin

  • 931 Posts
  • 271 Reply Likes
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
Photo of jerry stern

jerry stern

  • 20 Posts
  • 12 Reply Likes
Ok I made the changes and logging working perfect without Commander as the CAT intermediate.  I will report back in few days on whether this resolved the issue

Thanks Kevin

73 Jerry NY2KW