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
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.
FWIW, I did some more poking around. Increasing the RF gain to present
Winlink with a louder signal helps to alleviate this problem. Looking at
the meter in Winlink, when it switches from TX to RX, there's some ramp
time before it reflects the full amplitude of the incoming signal.
Curious
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
4 matches
Mail list logo
