Request with Rig Connection Consistency

[krossphire]

I've had my rig settings for my FTDX-5000 working well in QLog, but lately, it seems like nothing wants to work.

A rig connection that has always been really solid for me in the DX Labs suite Commander. It would be cool to see Commander offered as a Rig connection setting option such as what WSJT-X offer. Thanks and 73 de K5PO

Background: Yaesu FTDX-5000. CAT at 4800. Have tried CAT direct to Edgeport serial to USB and also Yaesu's SCU-17. CAT from the rig is going into VSPE and split to a virtual connector. I've tested and have been able to connect to the rig with DX Lab's Commander, WSJT-X, Ham Radio Deluxe, Spectravue software, and AC Log software.

Edit: Initially this was requesting DX Lab's Commander rig control support. Upon more thinking, DX Labs Commander would be cool, but I'd rather not run yet another application when QLog has so much of what I need. Really just hoping to improve rig connection consistency.

Andy K5PO

[krossphire]

I'm finding that for my FTDX-5000, WSJT-X with Hamlib "4.5.5 Apr 04" will keep a constant connection while Qlog with Hamlib "20241118.11" won't seem to connect with the same settings.

[foldynl]

just for reference, Commander message specification. http://www.dxlabsuite.com/commander/Commander%20TCPIP%20Messages.pdf

[krossphire]

Also finding that Ham Radio Deluxe rig connection is working consistently.

[aa5sh]

Have you tried with omnirig?

Michael, AA5SH

[krossphire]

Have you tried with omnirig?

Michael, AA5SH

I can connect with Omni-Rig V1 and QLog will communicate with it, however, if I open a second application on the same VSPE Virtual Splitter, the frequency being captured by QLog suddenly becomes inaccurate.

Example, I'm on 28.444. Once a second application using the same virtual splitter as Omni-Rig is opened, the frequency in QLOg reflects 11.92844 MHz (but I'm still on 28.444)

The behavior was the same for the Omni-Rig FTDX-5000MP and FTDX-5000MP-D profiles. The FTDX-5000-BETA profile would not connect at all.

[foldynl]

It's strange that many users of FTDX have issues with all sorts of things in QLog. Maybe it would be good if at least one operator dive into analyzing the problem and sends a pull request to fix it.

[aa5sh]

I am using a FTDX-101D that I recently switched to from a Flex 6400M. I initially connected straight to QLog or WSJT-X and had no issues. Now I launch a rigctld instance using 'rigctld -m 1040 -r /dev/cu.SLAB_USBtoUART' on my Mac. Only issue I have is the need to adjust the port at times if I disconnect the USB cable for whatever reason. I then will use rigctl.net rig in QLog and WSJTX. The only thing I notice - and I think it is a hamlib issue - is if on my rig I select the sub vfo as the tuning knob control QLog and WSJT starts to display the sub vfo frequency instead of Main. But that is really minor in my opinion.

Have you tried to have the rig talk directly to QLog not going through any VSPEs or anything?

[aa5sh]

I'm finding that for my FTDX-5000, WSJT-X with Hamlib "4.5.5 Apr 04" will keep a constant connection while Qlog with Hamlib "20241118.11" won't seem to connect with the same settings.

Can you send a screenshot of your WSJTX settings and your QLog settings so I can see what is working in WSJTX?

[krossphire]

Apologies. I've got the FTDX-5000 off the desk and boxed up now. Running a Flex 6400 now.

I wish I could say that my Flex 6400 is communicating with QLog well, but not yet. I believe perhaps Hamlib hates me haha

Am I correct that the TCI rig protocol is limited to Apache Labs only? Has anyone been able to connect a Flex via TCP?