Menu
▾
▴
wsjt-devel
|
From: Peter S. <vk...@gm...> - 2025-07-27 01:18:59
|
Hi, for some time now (all of the 2.7 variants and now 2.8) when I open WJST-X or swap between configurations, I end up with a rig control error and the current rig is shown to be "ADAT www.adat.ch" and not the previously selected FLRIG setting. I have learned to live with this for a while and today decided I should report this difficulty for evaluation. I use the FLRIG interface as it lets me see on my PC desktop what the SWR, power out and other settings of my two icom rigs as I do a lot of operating from the comfort of the house rather than the 50 metre journey to my shack in the stables shed. So far I have tried an empty INI file a few times and the error occurs with each iteration of testing I do, where I have set up multiple configurations. If I leave it as a SINGLE configuration then there is no error seen. Once I add a second or more configuration using FLRIG as the rig type I start seeing the Rig control error when starting WSJT-X or swapping configurations. When testing, if I use a direct connection (IC-7610) then I can add multiple configurations and not see an error when starting or swapping configs so the error seems to be confined to having FLRIG selected as a rig type. PC is a Windows 10 X64 O/S which is current with all updates. I have noticed that in the WSJT-X.INI file, that FLRig is shown in there with a trailing space and has inverted commas in some instances and in differently in other config (quite a puzzle for me), where as other entries are not shown like that, here are some examples from my BIG ini file that has about 8 configurations in it Rig=Icom IC-7610 Rig=FLRig FLRig Rig="FLRig " Rig=FLRig IC-7610(FLRig) hope I have no missed anything, any help would be appreciated Regards, Peter, vk5pj |
|
From: Andrew N. <ka...@ya...> - 2025-07-27 17:33:08
|
Peter, I don't know if this is a wjstx issue or a flrig issue. If you are unable to rectify your problem with help from this group, may I suggest posing the question to the linuxham group. I have placed the link below. That group is active and involves the programs created by W1HKJ, including flrig. Best of luck,73,Andy, ka2uqw https://groups.io/g/linuxham On Saturday, July 26, 2025 at 09:22:07 PM EDT, Peter Sumner via wsjt-devel <wsj...@li...> wrote: Hi, for some time now (all of the 2.7 variants and now 2.8) when I open WJST-X or swap between configurations, I end up with a rig control error and the current rig is shown to be "ADAT www.adat.ch" and not the previously selected FLRIG setting. I have learned to live with this for a while and today decided I should report this difficulty for evaluation. I use the FLRIG interface as it lets me see on my PC desktop what the SWR, power out and other settings of my two icom rigs as I do a lot of operating from the comfort of the house rather than the 50 metre journey to my shack in the stables shed. So far I have tried an empty INI file a few times and the error occurs with each iteration of testing I do, where I have set up multiple configurations. If I leave it as a SINGLE configuration then there is no error seen. Once I add a second or more configuration using FLRIG as the rig type I start seeing the Rig control error when starting WSJT-X or swapping configurations. When testing, if I use a direct connection (IC-7610) then I can add multiple configurations and not see an error when starting or swapping configs so the error seems to be confined to having FLRIG selected as a rig type. PC is a Windows 10 X64 O/S which is current with all updates. I have noticed that in the WSJT-X.INI file, that FLRig is shown in there with a trailing space and has inverted commas in some instances and in differently in other config (quite a puzzle for me), where as other entries are not shown like that, here are some examples from my BIG ini file that has about 8 configurations in it Rig=Icom IC-7610Rig=FLRig FLRigRig="FLRig "Rig=FLRig IC-7610(FLRig) hope I have no missed anything, any help would be appreciated Regards,Peter, vk5pj_______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Peter S. <vk...@gm...> - 2025-07-27 21:59:59
|
Hi Andy, thanks for the link, will have a look there. Since my original post I have dug deeper and widened my field of testing. I can see on 'other' derivatives of WSJT-X that the rig type is stored as "Q65-eme\Configuration\Rig=FLRig FLRig" and not the mangled: Rig="FLRig " I see in the current releases of WSJT-X and the Improved version. It would seem an error has crept into the code base at some point that mangles the storage of this parameter when selecting FLRig in the Configuration menu. Regards, Peter, vk5pj On Mon, Jul 28, 2025 at 3:07 AM Andrew Neumeier via wsjt-devel < wsj...@li...> wrote: > Peter, > > I don't know if this is a wjstx issue or a flrig issue. If you are unable > to rectify your problem with help from this group, may I suggest posing the > question to the linuxham group. I have placed the link below. That group > is active and involves the programs created by W1HKJ, including flrig. > > Best of luck, > 73, > Andy, ka2uqw > > https://groups.io/g/linuxham > > > > > > On Saturday, July 26, 2025 at 09:22:07 PM EDT, Peter Sumner via wsjt-devel > <wsj...@li...> wrote: > > > Hi, > for some time now (all of the 2.7 variants and now 2.8) when I open > WJST-X or swap between configurations, I end up with a rig control error > and the current rig is shown to be "ADAT www.adat.ch" and not the > previously selected FLRIG setting. > > I have learned to live with this for a while and today decided I should > report this difficulty for evaluation. > > I use the FLRIG interface as it lets me see on my PC desktop what the SWR, > power out and other settings of my two icom rigs as I do a lot of operating > from the comfort of the house rather than the 50 metre journey to my shack > in the stables shed. > > So far I have tried an empty INI file a few times and the error occurs > with each iteration of testing I do, where I have set up multiple > configurations. > > If I leave it as a SINGLE configuration then there is no error seen. Once > I add a second or more configuration using FLRIG as the rig type I start > seeing the Rig control error when starting WSJT-X or swapping > configurations. > > When testing, if I use a direct connection (IC-7610) then I can add > multiple configurations and not see an error when starting or swapping > configs so the error seems to be confined to having FLRIG selected as a rig > type. > > PC is a Windows 10 X64 O/S which is current with all updates. > > I have noticed that in the WSJT-X.INI file, that FLRig is shown in there > with a trailing space and has inverted commas in some instances and in > differently in other config (quite a puzzle for me), where as other entries > are not shown like that, here are some examples from my BIG ini file that > has about 8 configurations in it > > Rig=Icom IC-7610 > Rig=FLRig FLRig > Rig="FLRig " > Rig=FLRig IC-7610(FLRig) > > hope I have no missed anything, any help would be appreciated > > Regards, > Peter, vk5pj > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
|
From: Doug B. Sr. <dou...@gm...> - 2025-07-27 22:12:36
|
Great use for AI: have it deal with the configuration for Flrig, Fldigi, Js8call and Wsjtx. "AI, I'm going to get a coffee, when I come back, have these all talking to the radio properly, and have it come up the same way every time things get posted up. Cheers" On Sun, Jul 27, 2025, 6:03 PM Peter Sumner via wsjt-devel < wsj...@li...> wrote: > Hi Andy, > thanks for the link, will have a look there. > > Since my original post I have dug deeper and widened my field of testing. > I can see on 'other' derivatives of WSJT-X that the rig type is stored as > "Q65-eme\Configuration\Rig=FLRig FLRig" and not the mangled: Rig="FLRig " I > see in the current releases of WSJT-X and the Improved version. > > It would seem an error has crept into the code base at some point that > mangles the storage of this parameter when selecting FLRig in the > Configuration menu. > > Regards, > Peter, vk5pj > > On Mon, Jul 28, 2025 at 3:07 AM Andrew Neumeier via wsjt-devel < > wsj...@li...> wrote: > >> Peter, >> >> I don't know if this is a wjstx issue or a flrig issue. If you are >> unable to rectify your problem with help from this group, may I suggest >> posing the question to the linuxham group. I have placed the link below. >> That group is active and involves the programs created by W1HKJ, including >> flrig. >> >> Best of luck, >> 73, >> Andy, ka2uqw >> >> https://groups.io/g/linuxham >> >> >> >> >> >> On Saturday, July 26, 2025 at 09:22:07 PM EDT, Peter Sumner via >> wsjt-devel <wsj...@li...> wrote: >> >> >> Hi, >> for some time now (all of the 2.7 variants and now 2.8) when I open >> WJST-X or swap between configurations, I end up with a rig control error >> and the current rig is shown to be "ADAT www.adat.ch" and not the >> previously selected FLRIG setting. >> >> I have learned to live with this for a while and today decided I should >> report this difficulty for evaluation. >> >> I use the FLRIG interface as it lets me see on my PC desktop what the >> SWR, power out and other settings of my two icom rigs as I do a lot of >> operating from the comfort of the house rather than the 50 metre journey to >> my shack in the stables shed. >> >> So far I have tried an empty INI file a few times and the error occurs >> with each iteration of testing I do, where I have set up multiple >> configurations. >> >> If I leave it as a SINGLE configuration then there is no error seen. Once >> I add a second or more configuration using FLRIG as the rig type I start >> seeing the Rig control error when starting WSJT-X or swapping >> configurations. >> >> When testing, if I use a direct connection (IC-7610) then I can add >> multiple configurations and not see an error when starting or swapping >> configs so the error seems to be confined to having FLRIG selected as a rig >> type. >> >> PC is a Windows 10 X64 O/S which is current with all updates. >> >> I have noticed that in the WSJT-X.INI file, that FLRig is shown in there >> with a trailing space and has inverted commas in some instances and in >> differently in other config (quite a puzzle for me), where as other entries >> are not shown like that, here are some examples from my BIG ini file that >> has about 8 configurations in it >> >> Rig=Icom IC-7610 >> Rig=FLRig FLRig >> Rig="FLRig " >> Rig=FLRig IC-7610(FLRig) >> >> hope I have no missed anything, any help would be appreciated >> >> Regards, >> Peter, vk5pj >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
|
From: Andrew N. <ka...@ya...> - 2025-07-28 01:22:16
|
Peter, I should have pointed out that there are several support pages for W1HKJ software, depending on the O/S you are using. Here is the link for W1HKJ website, there are more details there. 73,Andy, ka2uqw https://www.w1hkj.org/ On Sunday, July 27, 2025 at 06:01:54 PM EDT, Peter Sumner via wsjt-devel <wsj...@li...> wrote: Hi Andy, thanks for the link, will have a look there. Since my original post I have dug deeper and widened my field of testing. I can see on 'other' derivatives of WSJT-X that the rig type is stored as "Q65-eme\Configuration\Rig=FLRig FLRig" and not the mangled: Rig="FLRig " I see in the current releases of WSJT-X and the Improved version. It would seem an error has crept into the code base at some point that mangles the storage of this parameter when selecting FLRig in the Configuration menu. Regards,Peter, vk5pj On Mon, Jul 28, 2025 at 3:07 AM Andrew Neumeier via wsjt-devel <wsj...@li...> wrote: Peter, I don't know if this is a wjstx issue or a flrig issue. If you are unable to rectify your problem with help from this group, may I suggest posing the question to the linuxham group. I have placed the link below. That group is active and involves the programs created by W1HKJ, including flrig. Best of luck,73,Andy, ka2uqw https://groups.io/g/linuxham On Saturday, July 26, 2025 at 09:22:07 PM EDT, Peter Sumner via wsjt-devel <wsj...@li...> wrote: Hi, for some time now (all of the 2.7 variants and now 2.8) when I open WJST-X or swap between configurations, I end up with a rig control error and the current rig is shown to be "ADAT www.adat.ch" and not the previously selected FLRIG setting. I have learned to live with this for a while and today decided I should report this difficulty for evaluation. I use the FLRIG interface as it lets me see on my PC desktop what the SWR, power out and other settings of my two icom rigs as I do a lot of operating from the comfort of the house rather than the 50 metre journey to my shack in the stables shed. So far I have tried an empty INI file a few times and the error occurs with each iteration of testing I do, where I have set up multiple configurations. If I leave it as a SINGLE configuration then there is no error seen. Once I add a second or more configuration using FLRIG as the rig type I start seeing the Rig control error when starting WSJT-X or swapping configurations. When testing, if I use a direct connection (IC-7610) then I can add multiple configurations and not see an error when starting or swapping configs so the error seems to be confined to having FLRIG selected as a rig type. PC is a Windows 10 X64 O/S which is current with all updates. I have noticed that in the WSJT-X.INI file, that FLRig is shown in there with a trailing space and has inverted commas in some instances and in differently in other config (quite a puzzle for me), where as other entries are not shown like that, here are some examples from my BIG ini file that has about 8 configurations in it Rig=Icom IC-7610Rig=FLRig FLRigRig="FLRig "Rig=FLRig IC-7610(FLRig) hope I have no missed anything, any help would be appreciated Regards,Peter, vk5pj_______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Peter S. <vk...@gm...> - 2025-07-28 07:02:06
|
Hello, when I look at this further and compare running up ver 2.61 and any of the 2.7x versions I have, the pull down list for choosing the RIG in version 2.61 shows an option with this text: FLRig FLRig any of the 2.7 or 2.8 releases in that same section of the rig selector show just: FLRig I am unsure if this is an error in an array of rigs or some other method used to populate the list of rigs but what is in the pull down list seems to correlate to what is populated in the WSJT-X.ini file. At some point when the 'bad' value is read at startup it seems to trigger an error and this is the details of the error: Hamlib error: rig_token_lookup called for client rig_confparam_lookup called for client 1:rig.c(817):rig_open entered rig_settings_get_path: path=.hamlib_settings rig_settings_load_all: settings_file (.hamlib_settings): No such file or directory rig_open: cwd=C:\ham_radio\wsjtx-2.8.0-imp\bin rig_open: C:\ham_radio\wsjtx-2.8.0-imp\bin/hamlib_settings does not exist rig_open: async_data_enable=0, async_data_supported=0 serial_open: COM3 serial_open(229): open failed#1 serial_open(229): open failed#2 serial_open(229): open failed#3 serial_open(229): open failed#4 serial_open: Unable to open COM3 - No such file or directory port_open: serial_open(COM3) status=-6, err=No such file or directory rig_open: rs->comm_state==0?=0 1:rig.c(1023):rig_open returning(-6) IO error IO error IO error while opening connection to rig Timestamp: 2025-07-28T06:57:34.969Z There is no COM port in my configuration, CAT is used for PTT so I have no clue why it is trying to open COM3 (My 1st COM port on the PC) Regards, Peter, vk5pj On Sun, Jul 27, 2025 at 10:48 AM Peter Sumner <vk...@gm...> wrote: > Hi, > for some time now (all of the 2.7 variants and now 2.8) when I open > WJST-X or swap between configurations, I end up with a rig control error > and the current rig is shown to be "ADAT www.adat.ch" and not the > previously selected FLRIG setting. > > I have learned to live with this for a while and today decided I should > report this difficulty for evaluation. > > I use the FLRIG interface as it lets me see on my PC desktop what the SWR, > power out and other settings of my two icom rigs as I do a lot of operating > from the comfort of the house rather than the 50 metre journey to my shack > in the stables shed. > > So far I have tried an empty INI file a few times and the error occurs > with each iteration of testing I do, where I have set up multiple > configurations. > > If I leave it as a SINGLE configuration then there is no error seen. Once > I add a second or more configuration using FLRIG as the rig type I start > seeing the Rig control error when starting WSJT-X or swapping > configurations. > > When testing, if I use a direct connection (IC-7610) then I can add > multiple configurations and not see an error when starting or swapping > configs so the error seems to be confined to having FLRIG selected as a rig > type. > > PC is a Windows 10 X64 O/S which is current with all updates. > > I have noticed that in the WSJT-X.INI file, that FLRig is shown in there > with a trailing space and has inverted commas in some instances and in > differently in other config (quite a puzzle for me), where as other entries > are not shown like that, here are some examples from my BIG ini file that > has about 8 configurations in it > > Rig=Icom IC-7610 > Rig=FLRig FLRig > Rig="FLRig " > Rig=FLRig IC-7610(FLRig) > > hope I have no missed anything, any help would be appreciated > > Regards, > Peter, vk5pj > |
|
From: Peter S. <vk...@gm...> - 2025-07-30 10:40:16
|
Hi, if there is anyone who reads this who is familiar with the source code for WSJT-X who could help me identify how the list of rigs in the 'RADIO' tab gets populated? I have been wandering through the source (downloaded a tarball from the main WSJT-X web site) but my level of experience is just scripting, its all a bit much for me. My theory at this point is the list of rigs has an error in it or the way the list is read has an error. In ver 2.61 the rig list showed the entry for FLrig as being: "FLRig FLRig" and the INI file shows it as: Rig=FLRig FLRig When I go to one of the 2.7x version, the entry for FLRig is just : "FLRig" and in the INI file it is: Rig="FLRig " next test... On my ver 2.61 folder if I change the libhamlib-4.dll to be a newer version the wheels fall off with the same problems at startup (radio selection goes back to Adat and a com port) I see on ver 2.7x BUT if I try the reverse and install an OLD libhamlib-4.dll into the ver 2.7x folder it does not improve things sadly but will recheck this in the morning (8pm local and feeling tired) Does WSJT-X read the list of rigs from the Hamlib DLL file to populate the list of rigs on the radio TAB of the Settings screen? as it feels like that is what is happening as when I change the Hamlib DLL's, the entry for FLRig changes inside WSJT-X. If this a Hamlib error, then I guess I need to contact Mike but until I can clarify where it is I am lost to know where to look. Regards, Peter vk5pj > On Saturday, July 26, 2025 at 09:22:07 PM EDT, Peter Sumner via wsjt-devel > <wsj...@li...> wrote: > > > Hi, > for some time now (all of the 2.7 variants and now 2.8) when I open > WJST-X or swap between configurations, I end up with a rig control error > and the current rig is shown to be "ADAT www.adat.ch" and not the > previously selected FLRIG setting. > > I have learned to live with this for a while and today decided I should > report this difficulty for evaluation. > > I use the FLRIG interface as it lets me see on my PC desktop what the SWR, > power out and other settings of my two icom rigs as I do a lot of operating > from the comfort of the house rather than the 50 metre journey to my shack > in the stables shed. > > So far I have tried an empty INI file a few times and the error occurs > with each iteration of testing I do, where I have set up multiple > configurations. > > If I leave it as a SINGLE configuration then there is no error seen. Once > I add a second or more configuration using FLRIG as the rig type I start > seeing the Rig control error when starting WSJT-X or swapping > configurations. > > When testing, if I use a direct connection (IC-7610) then I can add > multiple configurations and not see an error when starting or swapping > configs so the error seems to be confined to having FLRIG selected as a rig > type. > > PC is a Windows 10 X64 O/S which is current with all updates. > > I have noticed that in the WSJT-X.INI file, that FLRig is shown in there > with a trailing space and has inverted commas in some instances and in > differently in other config (quite a puzzle for me), where as other entries > are not shown like that, here are some examples from my BIG ini file that > has about 8 configurations in it > > Rig=Icom IC-7610 > Rig=FLRig FLRig > Rig="FLRig " > Rig=FLRig IC-7610(FLRig) > > hope I have no missed anything, any help would be appreciated > > Regards, > Peter, vk5pj > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
|
From: Wolfgang <oe...@gm...> - 2025-07-30 11:41:22
|
Hello Peter, a simple search using 'ReplaceStudio64' will reveal that 'Flrig' or 'flrig' string is only in "libhamlib-4.dll" Btw., Mike is SK since a while. He may rest in peace. 73's de OE1MWW Wolfgang Wednesday, July 30, 2025, 12:39:51 PM, you wrote: > Hi, > if there is anyone who reads this who is familiar with the source code for WSJT-X who could help me identify how the list of rigs in the 'RADIO' tab gets populated? I have been wandering through the source (downloaded a tarball from the main WSJT-X web site) but my level of experience is just scripting, its all a bit much for me. > My theory at this point is the list of rigs has an error in it or the way the list is read has an error. In ver 2.61 the rig list showed the entry for FLrig as being: "FLRig FLRig" and the INI file shows it as: Rig=FLRig FLRig > When I go to one of the 2.7x version, the entry for FLRig is just : "FLRig" and in the INI file it is: Rig="FLRig " > next test... > On my ver 2.61 folder if I change the libhamlib-4.dll to be a newer version the wheels fall off with the same problems at startup (radio selection goes back to Adat and a com port) I see on ver 2.7x BUT if I try the reverse and install an OLD libhamlib-4.dll into the ver 2.7x folder it does not improve things sadly but will recheck this in the morning (8pm local and feeling tired) > Does WSJT-X read the list of rigs from the Hamlib DLL file to populate the list of rigs on the radio TAB of the Settings screen? as it feels like that is what is happening as when I change the Hamlib DLL's, the entry for FLRig changes inside WSJT-X. > If this a Hamlib error, then I guess I need to contact Mike but until I can clarify where it is I am lost to know where to look. > Regards, > Peter vk5pj ---------- under construction: https://www.oe1mww.work/ |
|
From: Peter S. <vk...@gm...> - 2025-07-30 15:10:18
|
thanks Wolfgang, I knew Mike was unwell but had no idea he had passed away, that is quite a loss for the ham community. regards, Peter vk5pj On Wed, Jul 30, 2025 at 9:13 PM Wolfgang via wsjt-devel < wsj...@li...> wrote: > Hello Peter, > > > > a simple search using 'ReplaceStudio64' will reveal that 'Flrig' or > 'flrig' string is only in "libhamlib-4.dll" > > > > Btw., Mike is SK since a while. He may rest in peace. > > > > 73's de OE1MWW > > Wolfgang > > > > Wednesday, July 30, 2025, 12:39:51 PM, you wrote: > > > Hi, > if there is anyone who reads this who is familiar with the source code > for WSJT-X who could help me identify how the list of rigs in the 'RADIO' > tab gets populated? I have been wandering through the source (downloaded a > tarball from the main WSJT-X web site) but my level of experience is just > scripting, its all a bit much for me. > > My theory at this point is the list of rigs has an error in it or the way > the list is read has an error. In ver 2.61 the rig list showed the entry > for FLrig as being: "FLRig FLRig" and the INI file shows it as: Rig=FLRig > FLRig > > When I go to one of the 2.7x version, the entry for FLRig is just : > "FLRig" and in the INI file it is: Rig="FLRig " > > next test... > > On my ver 2.61 folder if I change the libhamlib-4.dll to be a newer > version the wheels fall off with the same problems at startup (radio > selection goes back to Adat and a com port) I see on ver 2.7x BUT if I try > the reverse and install an OLD libhamlib-4.dll into the ver 2.7x folder it > does not improve things sadly but will recheck this in the morning (8pm > local and feeling tired) > > Does WSJT-X read the list of rigs from the Hamlib DLL file to populate the > list of rigs on the radio TAB of the Settings screen? as it feels like > that is what is happening as when I change the Hamlib DLL's, the entry for > FLRig changes inside WSJT-X. > > If this a Hamlib error, then I guess I need to contact Mike but until I > can clarify where it is I am lost to know where to look. > > Regards, > Peter vk5pj > > > > ---------- > > under construction: https://www.oe1mww.work/ > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
|
From: Conrad F. <g0...@g0...> - 2025-08-01 21:13:57
|
Same here Peter, what a shame. Mike was (always) helpful. I feel a little ashamed that it took me 4 months to realise. Rest in peace Mike. Regards Conrad PA5Y From: Peter Sumner via wsjt-devel <wsj...@li...> Sent: Wednesday, 30 July 2025 14:45 To: Wolfgang <oe...@gm...>; WSJT software development <wsj...@li...> Cc: Peter Sumner <vk...@gm...> Subject: Re: [wsjt-devel] when starting WSJT-X rig defaults to "ADAT www.adat.ch" and not the wanted rig thanks Wolfgang, I knew Mike was unwell but had no idea he had passed away, that is quite a loss for the ham community. regards, Peter vk5pj On Wed, Jul 30, 2025 at 9:13 PM Wolfgang via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> wrote: Hello Peter, a simple search using 'ReplaceStudio64' will reveal that 'Flrig' or 'flrig' string is only in "libhamlib-4.dll" Btw., Mike is SK since a while. He may rest in peace. 73's de OE1MWW Wolfgang Wednesday, July 30, 2025, 12:39:51 PM, you wrote: Hi, if there is anyone who reads this who is familiar with the source code for WSJT-X who could help me identify how the list of rigs in the 'RADIO' tab gets populated? I have been wandering through the source (downloaded a tarball from the main WSJT-X web site) but my level of experience is just scripting, its all a bit much for me. My theory at this point is the list of rigs has an error in it or the way the list is read has an error. In ver 2.61 the rig list showed the entry for FLrig as being: "FLRig FLRig" and the INI file shows it as: Rig=FLRig FLRig When I go to one of the 2.7x version, the entry for FLRig is just : "FLRig" and in the INI file it is: Rig="FLRig " next test... On my ver 2.61 folder if I change the libhamlib-4.dll to be a newer version the wheels fall off with the same problems at startup (radio selection goes back to Adat and a com port) I see on ver 2.7x BUT if I try the reverse and install an OLD libhamlib-4.dll into the ver 2.7x folder it does not improve things sadly but will recheck this in the morning (8pm local and feeling tired) Does WSJT-X read the list of rigs from the Hamlib DLL file to populate the list of rigs on the radio TAB of the Settings screen? as it feels like that is what is happening as when I change the Hamlib DLL's, the entry for FLRig changes inside WSJT-X. If this a Hamlib error, then I guess I need to contact Mike but until I can clarify where it is I am lost to know where to look. Regards, Peter vk5pj ---------- under construction: https://www.oe1mww.work/ _______________________________________________ wsjt-devel mailing list wsj...@li...<mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Peter S. <vk...@gm...> - 2025-08-04 05:26:45
|
Hello, it seems users of FLRIg and WSJT-X / Improved are not too common, what I have found so far is, when WSJT-X starts, it queries the list of rigs from the HAMLIB DLL (lib-hamlib-4.dll) to create its rig list. This list of rigs appears to be a dynamic array as when HAMLIB finds any updated information it then presents that updated information to WSJT-X and the list of rigs when the pulldown list is viewed next. In WSJT-X 2.61 and before, the HAMLIB DLL that is part of the package provides only the 'basic' information from FLRig and in this way provides a stable RigName during use in the lrig list and in the WSJT-X.INI file. This version from WSJT-X v2.61 shows up as being: "HamLib 4.5~git Mon Jun 13 14:51:03 2022" At some point HAMLIB was changed to pass through extra information from FLRig, in this case it is the type of Rig that FLRig is connected to that is now passed through to WSJT-X. In my case, it is an Icom IC-7610. Initially the list of Rig types has a Rig type of "FLRig FLRig" in the earlier version of the DLL that came with WSJT-X 2.61 but the Release candidates of WSJT-X v2.7x all came with an updated HAMLIB that includes the extra information being passed through to it and ultimately defective for WSJT-X user that have FLRig in use. I have had a response from one of the HAMLIB team (Nate N0NB) that he had an update in play to correct the name for FLRig in the list to be: Manufacturer to "W1HJK" and the Model to "FLrig". which means all new HAMLIB DLL's with have the entry for FLRig as "WIHJK FLRig" Unfortunately this is just a cosmetic change for my needs as even this new DLL still gets the actual name of the Rig from FLFRig and dynamically changes the list from this: "W1HKJ FLRig" to this: "W1HKJ IC-7610(FLRig)" One could say this is all just cosmetic BUT the information in the Rig List is used to write data into the WSJT-X.INI for the next startup or to define other WSJT-X configurations. This then means what rig type in the INI file does not match the initial list of rigs queried from HAMLIB and then WSJT-X has a hissy fit and I get a world of hurt. For 99.9% of you, this probably will never happen but for me it's chaos. I can avoid all this by replacing the lib-hamlib-4.dll file with an older one each time WSJT-X gets an update but eventually there will be a critical change that stops me doing this. While this is primarily not a WSJT-X error and seems to live in the HAMLIB arena, I thought I would round out this topic as this is where it started and will pursue this with the HAMLIB team via their 'sourceforge' help forum. Regards, Peter, vk5pj |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X