On 08/07/2015 22:03, Steven Franke wrote: > Mike and Bill, Hi Steve, > I deleted my hamlib directory, downloaded the latest from git, changed the > timeout from 200 to 1000 in ts480.c and recompiled hamlib. Then I recompiled > wsjtx. Same problem - an excerpt from the trace is included below. I believe > that the effect of the increased timeout is evident in the 1s interval > between re-tries… This is something more fundamental than timing or numbers of retries. Also replying to your other message about not understanding the change that caused this, I don't think this is a WSJT-X change that has caused this - something else has changed.
I have a hunch that it is something to do with sending two "IF;" commands in succession. It is a bit tricky stopping that happening as we only call Hamlib API functions and several are likely to use the "IF;" alone to retrieve the requested state. Can you try using "PTT Method" as "VOX" in WSJT-X, that should eliminate one of the double invocations of the "IF;" command that is likely to happen just before trying to change the rig state like changing frequency. ... 73 Bill G4WJS. ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
