This is something I typed in another topic before but may have been missed. So a new topic.
I do have an issue with my radio control (TS-850, 2009 from the list) I never had before.
At first I got a pop-up telling me the radio did not respond in time. And the radio control showed 0000000.
So I changed the time-out setting to 15000 instead of 15 milliseconds. That works to some extend.
This problem is most prevalent when I tune up and down the band (any band) in a fairly rapid pace.
I also changed the poll to 200 and even 500 where I used to use 100 for a long time without that problem at all.
Then I changed some of the settings on the right side of the radio screen. Unticked some boxes.
I even tried more settings but to no avail.
As mentioned in the title: it was perfect in 128. Not in 138 nor 139.
It used to run perfectly and Hamlib was not changed. So what did?
Any suggestions?
Tjalling
Hi Tjalling!
There are major changes in rig control between 128 and 139 as you can except when jumping over 10 versions.
Rapid band tuning causing problems looks like TS850 is slow to handle CAT requests when it has "other things to do" I.E.
driving local things.
TIme-out is not directly milliseconds. It is a count how many poll rounds can be passed while waiting response to sent command from rig.
I must check the counting method as it seems this is not working as expected your poll 500mS x 15000 results 750000ms = 750s = 12minutes
and that indicates there is something wrong with counting.
Pity that I can not see that with my IC7300 that makes it "blind fixing" that is always harder.
--
Saku
OH1KH
Hi!
Just tested does the timeout X poll really work as should.
I did set polling to 1000 (1sec) and timeout to 15. That should cut of after 15secs of trying.
Enabled "Show communication with TRX in console" at preferences/TRXControl and after my IC7300 was up and running properly with Cqrlog
I manually switched off it's power.
Here is the debug out put result that shows the timeout really being 1000ms x 15 = 15sec:
Poll Sending:+f currVFO +m currVFO
Sent :22 TRUE
Polling - allowcommand:-1
Response waited: 1sec
Polling - allowcommand:-1
Response waited: 2sec
Msg from rig:GET_FREQ: CURRVFO|RPRT -5
a[0]:GET_FREQ: CURRVFO
a[1]:RPRT -5
Hamlib: Communication timed out
Polling - allowcommand:1
Queue has:
+\get_ptt currVFO
+\get_level currVFO RFPOWER
Queue Sending[0]:+\get_ptt currVFO
Queue left:
+\get_level currVFO RFPOWER
Sent :18 TRUE
Polling - allowcommand:-1
Response waited: 1sec
Polling - allowcommand:-1
Response waited: 2sec
Polling - allowcommand:-1
Response waited: 3sec
Polling - allowcommand:-1
Response waited: 4sec
Polling - allowcommand:-1
Response waited: 5sec
Polling - allowcommand:-1
Response waited: 6sec
Polling - allowcommand:-1
Response waited: 7sec
Polling - allowcommand:-1
Response waited: 8sec
Polling - allowcommand:-1
Response waited: 9sec
Polling - allowcommand:-1
Response waited: 10sec
Polling - allowcommand:-1
Response waited: 11sec
Polling - allowcommand:-1
Response waited: 12sec
Polling - allowcommand:-1
Response waited: 13sec
Polling - allowcommand:-1
Response waited: 14sec
Polling - allowcommand:-1
Rig/rigctld did not respond to command within timeout!
Response waited: 15sec
Destroy rigctld
1
2
3
Error with rigctld: Shutdown error [107]: Transport endpoint is not connected
4
5
6
Done!
So the problem with your TS-850 must appear outside of poll timeout somehow.
Could you set "Show communication with TRX in console" at preferences/TRXControl and start Cqrlog from command terminal as:
cqrlog > /tmp/debug.txt
See that everything works, then start making fast changes to vfo so that error appears and then close Cqrlog.
Send /tmp/debug.txt to me as email, or attach it to your message here.
Thank you!
--
Saku
OH1KH
Hi Saku,
Thanks for taking the time and effort to investigate my problem.
I did as you asked me to do and will attach debug.txt here.
Mind you, I unticked the lowest box in preferences so polls are done one by one.
It doesn't help but I forgot to re-tick it for this run.
The way it was in Alpha 128 was that CQRlog would stop showing changes in frequencies until the vfo came to a stop or was slowed down considerably.
Never a problem as such.
Of course, my TS-850 is now an older radio (which I bought new in 1994) with only a 4800 baud rate.
Still, it's a very good radio and I don't want to part with it. :)
Thanks again,
Tjalling
Somehow the file seems not attached.
Second attempt...
File:
Hi !
At least I found one bug from there.
-------------------------------------------------------
Rig init sending: +\set_func ?
Sent :13 TRUE
Msg from rig:SET_FUNC: ?|AIP LOCK |RPRT 0
Set functions: AIP LOCK
-------------------------------------------------------
How ever Cqrlog tries to reset XIT and RIT with "SET_FUNC" command.
I have no check are those supported by rig, that should be added.
I think that messes up the communication.
XIT and RIT are zeroed when band changes.
Changelog of version 137:
"TRXControl:Fix: 'change of band clears XitRit' was always on regardless checkbox"
That has happened between versions from 128 to 138.
I will fix this. Then we can try again.
Thanks for your support!
P.S.
Meanwhile you can try to uncheck "preferences/NewQSO/Clear RIT after saving qso" if it is checked.
This does not help for band change problem, but may help when saving a qso because there might be s problem also.
--
Saku
OH1KH
Hi Saku,
Thank you again for taking the time and effort to investigate my problem.
This could be the culprit indeed. The TS-850's RIT/XIT can only be switched on or off.
Not sure if it can be done remotely. There are just two potentiometers one can set. I rarely use them at all.
For now, I just switched the whole station down to get some sleep. Tomorrow I will give it a try.
My workaround for now is to have just selected one radio in preferences. So, when the frequency is not read, I quickly choose the none-existing radio.
CQRlog then switches back to the TS-850 and reads the frequency. That's quicker than restarting rigctld from preferences.
I'll report back tomorrow.
Tjalling
Hi Tjalling!
I have now rewritten some parts of RigControl. If you can compile by yourself you will find source from devel branch of git.
I you can/will not, send me an email and I will compile it for you. I'm ok at qrz.
--
Saku
OH1KH
Hello Saku,
First of all, Happy New Year 2026 and good health for a long time to come.
I just compiled your latest version, Ver.Alpha_140_Gtk2,
and everything is working perfectly. The minor issues with Cat control have disappeared! Well done on fixing those bugs. Here's the configuration:
IC7700 via serial port
IC7610 via USB port
FT897D via USB port
SunSDR2DX via network + TCI adapter for TCI support
Again, congratulations and thank you for everything you do for us!
73 Yves F5JQF
73 Yves, F5JQF
[ CQRlog Ver.Alpha_(140)_Gtk2 ]
...
Hi Yves!
Nice to hear!
Thanks for reporting.
--
Saku
OH1KH
Thank you Saku,
I sent you an email.
Tjalling