Andy, What values are you using for Poll and Timeout in OmniRig? I'm using 100 ms polling and 200 ms timeout.
I ask because I have been having a problem with transmitting (with an external radio in FM mode when using SDRC's External Radio capability) I have played with the Polling and Timeout values, but not see any change...and this is the 2nd computer I've run this on with the same behavior. Both Windows10, one Home and Pro. I'm very suspicious of Omnirig at this point. While this may seem disconnected with WSJT-X , don't think it is. I think it is a side-effect of Omni-Rig losing connection to the FT-857D external radio. I only use Omni-Rig for this purpose, I don't use it with WSJT-X. Interestingly, this never happens with SSB or CW modes, only FM. ...and if I wait a bit, I can resume TX'ing. The symptom is, PTT is asserted, but their is no RF out. I'm guessing OmniRig issues, but don't really know how to follow up with it. Anythoughts that might help? 73, N0AN Hasan On Sun, Aug 18, 2019 at 11:43 AM Andy Durbin <a.dur...@msn.com> wrote: > I have attempted to use WSJT-X ver 2.1.0 a few more times but continue to > be plagued by rig control failure messages. I have found that WSJT-X rig > control failures are associated with OmniRig Client declarations "Status: > Rig not responding. However, OmniRig seems to issue these messages when > when communication is still good. For example, with OmniRig Poll Int = > 250 and Timeout = 1000, Baud 38400, simply opening the Client "Dialog" > window and then closing it with "OK" will result in a "Rig not responding" > message and WSJT-X rig control error. > > May I suggest that WSJT-X should be desensitized from these transient > OmniRig fault reports by only responding if they persist for x seconds. > > Typical OmniRig Client Event report: > > Dialog VISIBLE > Rig type: WSJT-X > Dialog invisible > Status: Rig is not responding > Status: Rig is not responding > Status: Rig is not responding > Status: On-line > > Typical station controller log for WSJT-X recovery from loss of rig > control: > > 1:06:53.976 New IF - IF00010136055 003700005020010000; > 1:06:53.985 New FA - FA00010136055; > 1:06:53.987 New RX freq=10136055 > 1:06:53.988 split offset = 945 > 1:06:54.300 New IF - IF00010136000 003700005020010000; > 1:06:54.309 New FA - FA00010136000; > 1:06:54.311 New RX freq=10136000 > 1:06:54.313 split offset = 1000 > > > My station controller is currently set to alarm if TS-590 data is not > received for 5 seconds. There is no alarm for events that cause WSJT-X > ver 2.1.0 to abandon rig control. > > BTW - OmniRIg setting "Timeout" does not behave as I had expected. I > expected it to re-try for timeout period and then, if no response received, > declare rig not responding. What it actually does is send nothing for > timeout period then resume polling by repeating the command that had no > response. If it missed a reply that was actually sent then it cannot > recover until timeout period has elapsed. > > None of this is an issue with WSJT-X ver 2.0.1. > > 73, > Andy, k3wyc > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
