Closed fillods closed 1 year ago
Working here on db891187 against my IC7300 with grig -m 2 -r localhost
:
$ rigctld -V
rigctl Hamlib 4.4 Thu Dec 02 23:46:51 2021 +0000 SHA=5f8c4c
Also appears to work with gqrx 2.15.9.
However if I fire up another instance of rigctld using either the "Dummy" (1) or "Dummy No VFO" (6) rigs, startup seems to take a lot longer. No timeout errors, however it takes well over a minute for the grig window to appear. That is odd as I would expect the dummy rig to be quick as it is not working with any hardware.
So this is good news @mattmelling, thanks for reporting. The bug only disturbs rigctld
launched with "Dummy" (1) or "Dummy No VFO" (6) rigs then, It's a lower priority fixing it.
I fixed it in the latest Hamlib -- it will be in 4.5.4 You can compile the latest master repo and it should work. git clone https://github.com/Hamlib/Hamlib.git cd Hamlib ./bootstrap ./configure make install
Indeed, fixed in the forthcoming Hamlib 4.5.4. Thanks @mdblack98 for taking care of this issue :+1:
Grig does not work with "NET rigctl" model id 2. This is unfortunate because not only Hamlib
rigctld
uses this remote protocol but others like Gqrx, ...How to reproduce the bug:
$ rigctld -vvvvv
$ grig -m 2 -r localhost
Upon start-up (and during running), Grig times-out repeatedly:
It happens after querying
u SCEN
and beforeu TRANSCEIVE
, and many times later on.Please note the "NET rigctl" is a special Hamlib rig model, a kind of virtual rig that retrieves its caps (of the real distant rig) remotely during opening.