Yes, it can be good enough for contesting. I ran one CW Sprint with it and
it was adequate. I had to run low power because the amp wasn't yet
accessible remotely (It is now.) and I was single-radio. So my 218 Qs is
hard to compare to the 280-310 that I would have expected locally, high
power and SO2R. But most importantly, I didn't feel that latency was much
of an issue. That's surprising because of the rapid turnover at the end of
each QSO in a Sprint.
No, I haven't measured the latency in msec but my ping times are 30-80
msec. More to the point, if I turn up the remote monitor so I hear both
local and remote, then send a V at 30 wpm, I hear the local monitor V
followed by a tail ranging from U to a short T. Most of the time I hear an
A or a full T.
I'm using a full K3 as the Control head, not a K3/0. There shouldn't be any
difference.
More important than perceived latency is quality of the received audio
stream. Mine has pops and crackles. On a good day, it will be one pop of
maybe 50 msec every few minutes and I consider that acceptable. On a bad
day, it's bursts of 3 to 6 such pops in one second, several times a minute,
often obliterating a code element or most of a character each burst and I
consider that unusable for contesting. Others do not experience this and
I'm trying to track it down. I suspect lost UDP packets but haven't been
able to determine even which side is responsible.
Remote operation is a lot of fun when it works. I wish I could get it to
work all the time!
73,
/Rick
On Sun, Mar 30, 2014 at 11:50 AM, Brian Linn <
[hidden email]> wrote:
--
Rick Tavan N6XI
Truckee, CA
______________________________________________________________
Elecraft mailing list
Home:
http://mailman.qth.net/mailman/listinfo/elecraftHelp:
http://mailman.qth.net/mmfaq.htmPost: mailto:
[hidden email]
This list hosted by:
http://www.qsl.netPlease help support this email list:
http://www.qsl.net/donate.htmlMessage delivered to
[hidden email]
Locked
