TenTec
[Top] [All Lists]

RE: [TenTec] OMNI 6+ and Iambic (Different issues)

To: <tentec@contesting.com>
Subject: RE: [TenTec] OMNI 6+ and Iambic (Different issues)
From: "NJ0IP" <Rick@dj0ip.de>
Reply-to: tentec@contesting.com
Date: Wed, 14 Apr 2004 07:58:23 -0700
List-post: <mailto:tentec@contesting.com>
Ben,

They are using special-purpose contest keyers which are programmed to send
the 599 at a high speed and then slow down for the part of the message which
the operator on the other end must copy.
These keyers may also be used in standard mode, but when in contest mode,
they may be programmed to send the contest exchange (RST + whatever else is
required).  In most contests, everyone seems to just send 599, even if the
other station is down in the mud.  That's the part of today's contesting
which I dislike.

73
Rick

-----Original Message-----
From: tentec-bounces@contesting.com
[mailto:tentec-bounces@contesting.com]On Behalf Of Ben K8DIT
Sent: Tuesday, April 13, 2004 10:39 PM
To: tentec@contesting.com
Subject: Re: [TenTec] OMNI 6+ and Iambic (Different issues)


I have a question for the group.

Listening to QRQ from time to time I notice that many ops speed up briefly,
especially when sending 599, then slow back down. How is this done? One
notices it more in pileups and/or contests, but is also heard in regular
qsos from time to time.
My guess is that its a memory button on a keyer, is this correct? But it
sounds seemless and one would think that the sender would mistake one memory
button for another from time to time. So straighten me out here. If you
turned the speed up on any keyer you would overshoot the speed and send
gibberish, but whenever you hear the sudden speedup, it seems smooth and
very nice.


_______________________________________________
TenTec mailing list
TenTec@contesting.com
http://lists.contesting.com/mailman/listinfo/tentec


_______________________________________________
TenTec mailing list
TenTec@contesting.com
http://lists.contesting.com/mailman/listinfo/tentec

<Prev in Thread] Current Thread [Next in Thread>