|
From: | Barry Jackson |
Subject: | Re: xlog hamlib functionality with model 2 |
Date: | Sun, 7 Feb 2021 11:37:52 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 |
On 02/02/2021 22:14, Dr. Karsten Schmidt wrote:
I have been trying to report issues with xlog and hamlib-4.x for a while now, but have problems with my mails being bounced, or ignored.Hi Graeme, I have the same client... Quisk. Btw. I'm using hamlib 4.0 73, Karsten dg1vs On Wed, 2021-02-03 at 11:00 +1300, Graeme Jury wrote: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
I find that if the hamlib model number is correct in the config file then it works, but the the hamlib setup GUI dialogue displays the model number minus one.
My correct radio is model 2003, which I have set manually in the config file.
It shows in the GUI as 2002 but works.Setting the radio model in the GUI puts 2003 in the GUI, but in the config fle it is stored as 2004.
This needs sorting out. Check what is in your config file! Cheers, Barry G4MKT
[Prev in Thread] | Current Thread | [Next in Thread] |