¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: #QDX Hamlib Error #qdx


 

¿ªÔÆÌåÓý

Yet another hamlib struggle.

My suggestion is to load up FLRig and tell FLRig you are running a Kenwood TS480. ?Then tell ?WSJIT that your transceiver is ¡°FLRig¡±. ?Think of FLRig as a HAL (hardware abstraction layer) that is *way* ?better at understanding how to talk to rig hardware than Hamlib.

Also if you are OK with compiling your own FLRig from source the latest (test) bits include native support for the QDX . ?So you can tell FLRig that you are running a QDX not a Kenwood TS480.

I had nothing but trouble with hamlib and was very very happy to ¡°just say no¡± to it . ?FLRig rocks : its ?well documented, well supported and frequently updated to add support for new rigs (e.g the QDX will soon be supported in release builds). ? Hamlib on the other hand is frequently the subject of emails such as yours :-(


On Feb 8, 2023, at 21:31, Greg - Gmail <gregmew54@...> wrote:

Hi

I have been struggling with this for a few days without success and was wondering if someone can provide some guidance.? I have had a good troll around the previous posts but have not found any that give me a clue to what the problem is.

I am trying to use the QDX on a laptop for portable use.? I have had it working on a desktop so am reasonably happy that the QDX is working correctly though it took a few attempts to get it operational on the desktop.? Mostly changing the USB ports that it was connecting to.? I was able to upgrade the QDX firmware to the latest version and also use PuTTY to look at all the new screens that Hans has added in the latest version of the firmware.

I am using an ASUS ZenBook14 with a NOV8 TECH? 13 device HUB.? The QDX is connected to one of the USB3 ports on the hub which has a USBC connection to the ZenBook.

The problem on the laptop seems to be that when a first attempt is made to open the COM port using WSJT-X (latest version installed) that the port gets locked up or is maybe blocked in some fashion.? Any further attempts just get rejected and I get the following error message:

Hamlib error: 1:rig.c(1409):rig_close returning(-1) Invalid parameter

?

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:\WSJT\wsjtx

rig_open: C:\WSJT\wsjtx/hamlib_settings does not exist

rig_open: async_data_enable=0, async_data_supported=0

serial_open: COM5

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 COM5 - No such file or directory

port_open: serial_open(COM5) 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: 2023-02-09T05:03:40.626Z


In Device Manager I have made visible all of the hidden COM Ports and deleted all of these and then switched on the QDX which comes up with a COM port number.? Switching on the QDX brings up USB Serial Device (COM5) as the active port.? Using PuTTY and selecting Serial and COM5 and clicking the Open button gives the following popup:

<dummyfile.0.part>

I assume that this indicates that the port is locked??

Trying to run WSJT-X gives a Rig Control Error as follows:

Hamlib error: rig_token_lookup called for no_xchg

rig_confparam_lookup called for no_xchg

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:\WSJT\wsjtx

rig_open: C:\WSJT\wsjtx/hamlib_settings does not exist

rig_open: async_data_enable=0, async_data_supported=0

serial_open: COM5

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 COM5 - No such file or directory

port_open: serial_open(COM5) 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: 2023-02-09T05:23:03.879Z


Does anyone have an idea of what may be causing this problem?
Any help or suggestions as to what to try would be greatly appreciated.

Regards

Greg VK4GRM

Join [email protected] to automatically receive all group messages.