Got a great tip from Elecraft support on this one, which I'll relate here for the next person who is searching for K3/K3S "T>R Latency measurement timeout" on Google or the list when operating with Winlink.
The answer is to assign CONFIG:SYNC DT to a PF button (I used PF1) and then enable it when in DATA mode. This cuts the TX/RX latency *substantially* and entirely eliminates the 60ms of artifacts I was seeing during switching (the slow ramp and the 40ms drop-out). Presumably those artifacts were the result of switching filters. T>R latency on my laptop now varies anywhere from 60-130ms, and I'm sure some of that is just variance in processing in Winlink itself. The important thing is that the measure no longer times out, and the latency is in the ballpark where it needs to be for the mode to work well. The moral of the story is that if you're using a DATA mode that relies on quick switching from transmit to receive, assign Sync DT to a button and engage it when working with that mode. Kudos to Gary at Elecraft! Nick On Thu, 11 Oct 2018 at 12:08, Brian Hunt <huntin...@coastside.net> wrote: > When calling to connect with winmor you will always get the timeout > message until the called station responds. Once it connects the error > message should go away. It drove me nuts for a while. :-) FWIW, I use > the CAT command option for PTT so I don't have to remember to set the > PTT-KEY menu. Seems to work fine. Note: K3 and external USB sound > card used here with Win10 desktop PC. HTH > > 73, > Brian, K0DTJ > > On 10/10/2018 22:42, Nicklas Johnson wrote: > > Somewhat related to my other post, but sufficiently different that I > > figured it should be its own thread: I consistently get the "Timeout in > T>R > > Latency Measurement" message from Winlink Express using the built-in > > software Winmor TNC. > > > > After some poking around and trying different things, I set up the K3S to > > do PTT on RTS, made sure the TX delay was as short as possible, > configured > > Winlink to use RTS for PTT, and as far as I can tell, the switching is > very > > fast... but Winlink is still not happy about it. I tried VOX as well, > but > > it seemed like latency should be less with RTS for PTT. > > > > I used to get the Timeout error on my KX3 on the first transmit, but > > subsequent transmissions always worked fine. > > > > Has anyone had more success with Winlink with the K3s and with avoiding > > this Timeout message? > > > > Nick > > > > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:Elecraft@mailman.qth.net > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to n...@n6ol.us -- *N6OL* Saying something doesn't make it true. Belief in something doesn't make it real. And if you have to lie to support a position, that position is not worth supporting. ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
