Re: [wsjt-devel] when starting WSJT-X rig defaults to "ADAT www.adat.ch" and not the wanted rig

[Peter S. <vk...@gm...>]

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
>