[Hamlib-developer] possible changes to how data from FLRig is handled
Library to control radio transceivers and receivers
Brought to you by:
n0nb
|
From: Peter S. <vk...@gm...> - 2025-12-20 09:42:36
|
Hello,
I have been an avid user of WSJT-X - HAMLIB - FLRig for some time now and
have found that in builds after version 4.54 there were changes to flrig.c
that allow hamlib to display the radio model connected to FLRig. While
this seems like a minor change, it has cascaded into this extra
information being sent to software like WSJT-X that then saves this extra
information in its INI file. When WSJT-X starts up and queries HAMLIB it
gets a vanilla list of rigs that show "FLRig FLRig" as it used to be in
version 4.5.4 but in anything after that, the extra information bleeds
through to WSJT-X once the connection is open to FLRig.
This causes WSJT-X to store the rig type as: "Rig=FLRig IC-7600(FLRig)"
which does not match the value it sees at start up ("FLRig FLRig"), meaning
WSJT-X shows a rig control error and the user must manually select FLRig
from the list every time.
With my limited ability I have been able to identify where I think the
change happened (see below). Is there any way for this behaviour to be
changed with a setting in a JSON file or even reverted to how it was in
v4.5.4 ? unless there is a pressing need to have this extra information
from FLRig?
/ver 4.6.5 flrig.c
RIG_MODEL(RIG_MODEL_FLRIG),
.model_name = "",
.mfg_name = "FLRig",
.version = "20250107.0",
then down quite a bit around line 870 this happens (which is not in 4.5.4)
char model_name[256];
snprintf(model_name,sizeof(model_name), "%.248s(%s)", value, "FLRig");
rig->caps->model_name = strdup(model_name);
STATE(rig)->model_name = strdup(model_name);
//ver 4.5.4 flrig.c
RIG_MODEL(RIG_MODEL_FLRIG),
.model_name = "FLRig",
.mfg_name = "FLRig",
.version = "20221109.0",
I have asked George Blatz about this but he told me he had no experience
with FLRig and doubted he could be of assistance.
O/S windows 10 X64, I have no compilers and lack the experience to try and
compile a private version of HAMLIB.
hoping one of the members here can help
Regards,
Peter, vk5pj
|