Rig type FLRig seems to have a bad name

[VK5PJ Peter Sumner]

Hi,
been using HAMLIB as part of the WSJT-X and other variants indirectly for
a long time now and have noticed that when I select FLRIG from inside
WSJT-X the RIG name is presented as "FLRig " (note the space)
This did not happen on older versions of HAMLIB, there seems to have been
an error crept in that truncates the entry for FLRig from being "FLRig
FLRig" down to be just "FLRig "

I have tried to seek help through the WSJT-X support but none of the DEV
team have replied over the last 10 days. The deeper I dig the more it
seems this is inside HAMLIB but I am no coder so it's hard to be certain.

Does anyone know how WSJT-X gets its list of RIG type? does it query the
HAMLIB-4.DLL or is it hard coded. Sorry to be crossing across the two
packages but I cannot be sure where the problem resides.
Regards,
Peter, vk5pj

[Nate Bargmann]

Good timing!

I just pushed a merge request to GitHub that references GitHub issue #1013. I'm going to merge it and it will change the Manufacturer to "W1HJK" and the Model to "FLrig".

[Nate Bargmann]

I've merged the changes into the master branch and they'll appear in tomorrow's daily snapshot. I've no idea of the schedule that WSJT-X updates their Hamlib copy.

[VK5PJ Peter Sumner]

Hi Nate,
thanks for the update, I have been swapping HAMLIB DLL's back and forth to try and work out where it went wrong, the only data points I have is one that works from back in 2023 (came with WSJT-X v2.61) and those that do not from 2024 (part of the ver 2.7x R.C stream) up to now (all were part of the WSJT-X packages) will have a look tomorrow or the next day to see what is in the nightly builds. I only just recently heard that Michael Black had died, which was very sad, he had always been a great help to us using HAMLIB as part of WSJT-X.
Regards,
Peter Sumner

[VK5PJ Peter Sumner]

Hi Nate,
I grabbed the nightly build for 2025-08-02 (2nd Aug) and I can see the change of the name for the FLRIG entry, thanks. I am finding it still miss behaves when used with WSJT-X 2.7, It is hard to describe but no where as smooth as when I use the very old HAMLIB DLL so it seems there is some thing not quite right for me. If I go through all the setup for the rig and it works well but when I close WSJT-X and open it again, I am back to a RIG error and it defaults to the ADAT rig settings grrrr... not sure how to describe it any better right now. Will look again when I have had a sleep.

Peter Sumner, vk5pj

[VK5PJ Peter Sumner]

Hello,
what I can report back, is with the new HAMLIB DLL's it reports back extra information to WSJT-X in the form of the Rig type that is connected to FLRIG and that string is stored in the WSJT-X INI file. This extra information in the RIG= string of WSJT-X triggers some form of mis match error and forces it back to being the 1st rig type in the list ( ADAT )

When I start WSJT-X and select the entry for "W1HKJ FLRig" and save that, it is all runs fine for that session BUT what is stored in the INI file for WSJT-X is actually: "W1HKJ IC-7610(FLRig)"
it would seem that some where HAMLIB is reading the Rig type from FLRIg and then passing that along in the rig list array, which also has now dynamically changed to be "W1HKJ IC-7610(FLRig)" this cascades into an eventual mis match of information.

Is there any way to stop HAMLIB reading the extra information from FLRig so that the list of rigs will always be predictable?

Regards
Peter, vk5pj