Dave - I wonder if you have any VB code examples of communications with the IC-7610 that you can share? I found an old link to some examples at your site for other communications, but it was a dead li

Hmmmmm... Guess I didn't do a very good job with the terminology, so I'll give it another try. I said UDP not based on personal knowledge, but based on the fact that to get the communications to work

I have a new IC-7610 and at first had Commander directly connected to the rig via USB. I have WSJT-X configured with Commander as the rig, exchanging information via UDP. That all worked great. The ne

And the answer is: I should have set up USB B in the 7610 menu instead of USB A. The answer was in a contest university presentation seen here: https://www.kkn.net/~n6tv/N6TV_Dayton_2019_Everything_US

New IC-7610 here and the goal is to get it working with Winwarbler on FSK RTTY. At this point, I have PTT working, but no FSK output when transmitting. In the 7610, I have these settings: USB Send = D

I hope the reborn Joe will still get excited about North Korea.

Joe - that question was enough to lead me to the right place. I had to uncheck the Lookup box in SpotCollector WSJT-X setup and now all is well. Thanks! 73, Floyd - K8AC

No JTAlert.

Have been through the help with no success on this. I want to have DXKeeper display my log, sorted in UTC and Date order all the time so that I can see the last contacts logged. When I mouse on a spot

The connection to DXKeeper was TCP, as specified in the JTDX Reporting tab. Unfortunately, in some previous testing when I was using JTAlert, I had also checked the box in the UDP panel that caused th

I don't think this is a DXLab problem, but hopefully someone who is successfully using DXKeeper with JTDX can shed some light on what's happening. I normally use WSJT-X with DXLab with no problems and

OK - thanks, guys. Have it working properly again.

Had these two working together about 18 months back, but many changes to station since then and just now trying to get it to work again. Following the info in the DXLab Wiki, trying to determine which

Port 7300, that is.,

That works for me. 73, Floyd - K8AC

The power spec was the problem. I changed it in config to be higher than the logged power, but that still didn't pick up the S01WS QSO. I then altered the logged power and saved the contact and at tha

I worked S01WS this morning on FT8, but it doesn't appear in the Marathon realtime award tracking. DXCC and entity are correct in log entry. Thought I understood the risk ratings, but maybe missed som

Nothing at all wrong with a clean install, but I wouldn't agree that it's the best thing to do. My Win 10 system started out as a Win 7 system years ago and I've done nothing but upgrades to the syste

Yes - works just fine. It would be perfect if Commander would only pass the RIT reset command through to the connected transceiver via the secondary CAT port. Any chance of that?

I'm using VSP Manager from K5FR. If you're a licensed ham, k5FR will send you a free copy. You could also use VSPE and there are a couple of others as well.