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