Hi Petr
Cqrlog seems loose connection to rigvtld, when closing radio during night. Sometimes reading from rig can be done, but controlling rig from exsample dxcluster, no way. Information from cluster comes ok into logwriting window, but rig does not cange freq/mode, no matter if i do refres rx/tx control. Only way is, that I close cqrlog and restart it again. When control is lost, I telnet to rigctld port, I can resd freq from there. Using OH1KH dev version of cqrlog.
Sun, 2015-06-21 21:31
#1
Rigctld
Hi Petr
Have you got any clue of this? I use Saku's version and still problem is, when I open log first and rig after that, I do not get rigctl at all. But if I power rig first and then open cqrlog, all working fine, Ok, not all, bandmap makes cqrlog crashing every now and then, no clue with debug either.
<p>Jarmo</p>
Hi Petr,
It is the same in my case too. If I start CQRLog first the radio won't connect but sometimes refreshing trx control works but often it does not. My radio is a home brew SDR using 127.0.0.1 with rig ID = 2 and poll rate = 512 and port number = 4532. If I have started the radio first, CQRLog next then the interface works 100% but if I stop the radio and then restart it the refresh TRX/ROT control usually does not work but can sometimes. My usual fix is to close everything, start the radio and then start CQRLog.
73 es tnx fer great software, Graeme ZL2APV
Hi,
you are right, I have the same problem. It's on my todo list and I'll fix it.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Loaded Hamlib-3.0.1 and first tests seems to show rigctl working
with my TS-590. Before, I had to have rig on first, then open CQRLOG, now tested, opened cqrlog and then rig. Seems that control is working. First tests are naturally too hasty, butt hopefully true... Hi.
<p>Jarmo</p>
I was too optimistic. If I shut down radio and leave it little longer closed, then fire it up again, no rigctl, aaargh. I had radio closed about 2-3 hours and cqrlog lost connection, didn't find radio after I opened it again.. Sorry, I should have tested it better...
<p>Jarmo</p>