On 11/09/2016 01:53, Dan Bates wrote: > I see the failures when a second client is polling the rigctld socket. > > The current code, in the failure routine just toggles a bool variable for a > single retry before throwing the error. Other apps (example fldigi) have a > user configurable variable for retry count.
Hi Dan, that sounds like a rigctld issue. It should arbitrate clients at the single command level, it uses a mutex to serialize the client's server thread access to the rig serial port. Do you know what the reported error from Hamlib is? It should be shown in the "Details..." box in the WSJT-X rig control error message box. The reason for the single retry at the UI level in WSJT-X is because there should be several retries in the WSJT-X rig control thread or in Hamlib before an error gets as far as the WSJT-X UI code. 73 Bill G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
