开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

Rig Connection Problem


 

I've been having difficulty in connecting my FT2000D to QLog version 0.29 using Windows 11.
I just installed version 0.30 and now I get the following connection errors:

Rig Error: Get Frequency Error
Error Detail: newcat_get_freq: unsupported vfo=currVFO

I'm using the same com settings as I do for WSJT and JTDX both of which work fine.
Can anyone point me in the right direction please?

--
73's de Dave, G8FXM


 

Hi Dave.

it is quite difficult to solve these things without detail. Can you please tell me how your rig is connected? It is mainly about how you have configured the rig in QLog, WSJTX... keep in mind that if you have a Serial port rig setting in QLog, then it is not possible to run WSJTX on the same port as well. But I don't know if that's your case. I would need to know more than just an error message from Hamlib.

It is also import to know that QLog works
differently than CQRLog. CQRLog rung own RigCTLd, what is server for sharing rig over the network. QLog does not provide this and it is up to the operator to build a shared rig for multiple applications (Log and WSJTX, JTDX etc).

My last note is about the difference between 0.29 and 0.30 for windows.
Release 0.30 contains the latest available version of Hamlib.

Regards
OK1MLG, Ladislav


 

On Mon, Dec 4, 2023 at 02:12 PM, ok1mlg wrote:
Hi Ladislav,
I'm using Windows 11 here via COM Port 3 connected to my FT2000D via Prolific PL2303GT serial cable to a 9 pin RS232 connector at the rig.
The port is configured for 38400, 8 bits, 1 start and 1 stop. No flow control and no parity.
This set up works well with WSJT and JTDX applications on the same PC.

For some reason I cant get QLog to connect to my Radio, I have installed 0.30 but still no joy. The Hamlib error I get is:

Rig Error: Get Frequency Error
Error Detail: newcat_get_freq: unsupported vfo=currVFO

Let me know if you need any further details?


?
--
73'd de Dave, G8FXM


 

I'm very sorry, but I can't help you. I ran tests and couldn't simulate the same error. Maybe someone who has more experience with this type of rig and the hamlib library.

I don't know what version of the Hamlib library your WSJTX uses, but I looked in the source code of WSJT and QLog use the same commands to control the rigs.

Regards
Ladislav


 

OK, many thanks anyway. It's very strange as Minos, Log4OM, WSJT, JTDX, OmniRig and FLrig (FLRig has some issues with VFOB, but still connects and works with VFOA) all connect to my FT2000 without any problems,-. It's only QLog I have an issue with?
--
73's de Dave, G8FXM


 

I'm not sure if it's relevant but on Googling the issue it seems there are many issues for other Yaesu radios with the current version of Hamlib. It seems a roll back to version 2.3.0 is a temporary fix for affected users. Is there a way I can roll back? the version of Hamlib installed with QLog or can you tell me which earlier version of QLog was compiled with Hamlib 2.3.0? I'd be happy to install a earlier version until Hamlib sort it out.

See?

--
73's de Dave, G8FXM


 

I will try to prepare a special version for you with a early version of hamlib. Maybe the installation package will be available tomorrow, but you reported that you have an issue with previous version of QLog that contains early version of the Hamlib.

To be exact, currently QLog for Windows use hamlib is 4.5.5. QLog 0.29 and older used hamlib 4.4. It seems that current WSJTX for windows (2.6.1) includes hamlib 4.5.4. WSJTX 2.3.0 is really old and contains 4.1.

what version of WSJTX are you using?


 

I'm using WSJT-X v2.5.4 d28164
Thanks for offering to compile a special version just for me.
I don't want to put you too too much trouble or create a lot of work just for one user!

sounds like I'm in the minority as an old FT2000D user ;-)
?
--
73's de Dave, G8FXM


 

Do you think this is relevant?

?
--
73's de Dave, G8FXM


 

I look at the source code of Hamlib and fix#569 is a part of Hamlib 4.5.5. This version is used by current QLog.

As promised I prepared 2 versions of QLog with Hamlib 4.3.1 and 4.1. You can find these versions here:




Theoretically, you could just run the installer and test it, but I would recommend that you remove the original rig setting after installation and set it up again.
We will see if we succeed.

73 de Ladislav



 

Hi Ladislav,

Still no joy I'm afraid.

hamlib 4.1 returns the following error:

Rig Error: Get Frequency Error

Error Detail: Invalid parameter

hamlog 4.3.1 returns this error:

Rig Error: Open Connection Error

Error Detail: Invalid parameter

Thanks for trying, not sure where we go from here?

73's de Dave, G8FXM


 

Looks like from these error messages that Hamlib 4.1 connects but fails to fetch VFO A Frequency whereas 4.3.1 fails to connect alltogether?
--
73's de Dave, G8FXM


 

Please, could you send me a screenshot of your QLog's Rig setting?


 

Hi?Ladislav,
I have now managed to connect QLog to my FT2000 via the FLRig app.
I chose FLRig in Hamlib settings nd it works fine

--
73'd de Dave, G8FXM


 

Here are my FT2000 settings:

--
73'd de Dave, G8FXM


 

It is a good workaround with FLRig. However, if you want to run it with WSJTX, then this is the best solution, because QLog does not share the RIG connection.

Otherwise, it doesn't make sense to me, because everything works against the simulator.


 

OK well I work SSB and WSJT so I'll have to switch connections when I switch modes.

I did think of installing the rigctld daemon on my window pc and see if I can use it as a rig gateway, but not quite sure how I'd install that. I would be easy on Linux ;-)
Maybe install it on my Raspbery Pi and use that as my rig gateway?

Thanks for taking the time to look into this, as I'm the only one reporting this problem not worth you wasting any more time over it.
If I ever manage to resolve it, I'll let you know.

--
73'd de Dave, G8FXM


 

Just in case it help to debut this issue attached is the debug output I got when directly connecting to my FT2000 from Hamlib which also works fine outside of QLog.
--
73'd de Dave, G8FXM