WSJT-X not tracking 8600 Frequency

WX7Y · May 8

The only one I can get to work right now is the "FlexRadio 6xxx" the other with the individual Slices doesn't work for me.

Geoff AB6BT · May 8

Bret-Great clue!

Geoff AB6BT · May 9

Updating the hamlib dll and selecting "FlexRadio 6xxx" as the rig seems to have resolved the problem.

Thanks for all the help and tips!!!

WX7Y · May 9

that's great, glad you got it working

73

Bret WX7Y

Geoff AB6BT · May 9

Bret — I appreciate your assistance! I'll probably play with the other rig selections to see what I can break… HA

WX7Y · May 9

let me know if you get it working with the other driver, since I updated HAMLIB and got WSJT-X working JTSDX tcp connection is Broken go figure.

73

Bret WX7Y

Geoff AB6BT · May 9

Gotta love it…

Mike-VA3MW · May 9

Just in case you are following this:

There are many ways to have a digital program to communicate with the radio. There is no one way to do it.

Since FlexRadios emulated Kenwood CAT protocol, you’ll find telling any digital program you are using a TS-480 or TS-2000 works about 100% of the time using the legacy RS232 protocols. Hamlib is not required for any of these methods as the interfacing to the radio is via SmartSDR CAT. Doing it this way is not any faster or slower than any other method.

As we get away from RS232 protocols and into TCP/IP as a communications path which is my preference, you will find more options. It was cool to see FlexRadio + Slice Support which is really started to leverage all the radio power.

Keep experimenting. That is what we do.

David Decoons, wo2x · May 9

Geoff,

There is a selection for Flex 6xxx. Use that and set IP to 127.0.0.1:5002. CAT as a default creates a virtual COM port and virtual TCP port 5002. You can create a different TCP port if you prefer or create additional TCP ports for other slices to run multiple copies of WSJT- X on different slices, each with their own port assigned to a slice in CAT.

This is tested on my new PC build with SmartSDR 3.8.23 (and upcoming 3.9) with WSJT-X 2.7.2

Geoff AB6BT · May 9

Hi Dave—Yes that's what I did, I used "FlexRadio 6xxx" ; see my post a few up the thread.

I was trying to use one of the newer slice specific Flex rigs in WSJT-X. I also updated HamLib, although I'm not sure that was necessary. I made both chages at the same time.

I had created the CAT TCP port previously set to 5002 as well as the port in WSJT-X. I have been using it that way for years with my 6400.

I have not tried setting up multiple instances.

Thanks.

Geoff AB6BT · May 9

Hey Dave— Where did you find WSJT-X 2.7.2?

David Decoons, wo2x · May 10

typo. 2.7.0.
The “improved” branch is at 2.8.0

73 Dave wo2x

Geoff AB6BT · May 10

OK, sticking w/2.7.0 fwe now.

David Ahrendts · June 22

Echoing the work-around above from ****, KC9YRA. Solved the issue for me. Manually shutting down CAT and DAX and then manually re-opening CAT and DAX appears to re-establish frequency follow for FLDIGI 4.2.07 (current) and presumably other programs. I am three days into my new 8600 with SDR 3.9.18 and encountered the frequency follow problem with FLDIGI. The program would work for while on, for instance, 40M, then stop working if I changed to 20M and back to 40M. Rig control, audio streams were OK — just wouldn't follow frequency changes. Manually shutting down CAT and DAX, and then re-opening fixed it.

David A., KK6DA

WSJT-X not tracking 8600 Frequency

Answers

Leave a Comment

Categories