Hello Karsten,
It will be no consolation but I get the same error. I am using an SDR
client called Quisk and it communicates without any problems with
cqrlog. I have not tried to analyze it any further but will have a go soon.
73, Graeme ZL2APV
On 3/02/21 9:29 am, Dr. Karsten Schmidt wrote:
Hallo,
maybe someone can help me.
I’m trying to get xlog hamlib functionality running. My Rig is a
Quisk-software-transceiver which is accessible via model 2 from hamlib.
The port is localhost and the port 4575. After setting up, it reads out
the frequency once. Afterwards xlog reports an error via a dialog box
“There was an error while communicating with our rig, hamlib has stopped”.
I’m quite sure, that hamlib itself is able to handle to read out the
frequency from quisk, since the commad “rigctl –model=2
–rig-file=localhost:4575” works like a charm. Tracing the hamlib traffic
via xlog doesn’t work, it’s to fast to enable the hamlib logging.
Any hints?
Kind regards
Karsten
73 de dg1vs
