Re: #Cat_RigControl #Cat_RigControl
Bob Stricklin <bstrick@...>
Hi Bill,toggle quoted messageShow quoted text
The issue I am seeing is timeouts on commands that take longer than WSJTX allows.
While working with a Hamlib CMD I for instance I captured the following using the WSJTX loging feature…..
[2021-04-28 02:42:47.983260][00:00:30.484853][RIGCTRL:trace] 0000 49 20 31 34 34 31 37 34 30 30 30 2e 30 30 30 30 I 144174000.0000
[2021-04-28 02:42:47.983276][00:00:30.484869][RIGCTRL:trace] 0010 30 30 0a 00.
[2021-04-28 02:42:47.983292][00:00:30.484884][RIGCTRL:trace] read_string called, rxmax=96
[2021-04-28 02:42:48.984465][00:00:31.486061][RIGCTRL:warning] read_string(): Timed out 1.001 seconds after 0 chars
[2021-04-28 02:42:48.984550][00:00:31.486143][RIGCTRL:debug] rig.c(3382):rig_set_split_freq return(-5)
[2021-04-28 02:42:48.984588][00:00:31.486181][RIGCTRL:debug] rig.c(3899):rig_set_split_freq_mode return(-5)
[2021-04-28 02:42:48.984604][00:00:31.486197][RIGCTRL:error] error: Communication timed out
WSJTX indicates it is timing out before my code and Hamlib get back with a reply. I reduced the amount of code I had active in the CMD I instruction and the the time issue goes away.
This is what led to my comment. I feel the timing requirements of a command like this are not critical. I know there has to be a time limit of some sort in WSJTX to cover the non responsive commands issued but this limit should be extended to give more latitude to user. How much time is needed, maybe 3 to 5 seconds. My code is on the edge now so if the timeout doubled it would help.
The error message seems like a generic error message which may be sent for more than one reason, this is just my observation and not a problem.
I am working here to get everything done within the time limits needed by WSJTX. It would help me though and possible others if the timing needs were relaxed a bit on non critical commands. I wanted to get the comment out there before the evaluation of the current version completed.
Thanks for all your efforts in making WSJTX a great package and helping the community. We are lucky to have your support!