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:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]
