RTTY
[Top] [All Lists]

Re: [RTTY] The RTTY efficiency myth and SUPERFILL

To: rtty@contesting.com
Subject: Re: [RTTY] The RTTY efficiency myth and SUPERFILL
From: Tim Shoppa <tshoppa@gmail.com>
Date: Wed, 16 Jul 2014 12:42:29 -0400
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
In a real RTTY contest, the "PLEASE COPY" is surprisingly rare. (It was
pretty common on field day, which thank God is not an actual contest!)

More common in real RTTY contests, are long preambles of punctuation
especially from EU contesters, and/or canned macros that greet me as
"Timothy" from a licensing database every time I ask for a fill. I don't
mind the guys who call me by name in exchange because they actually know
me, that's fine.

On the subject of asking for a fill... I saw on several occasions "PLEASE
MORE NR" in the DL RTTY contest a few weekends ago. That was very pleasing
to see! Asking for a fill in marginal conditions, and getting a long canned
macro that prints fine except for the actual variable exchange info which
was only sent once, is very frustrating!

I would encourage anyone setting up macros for CW or RTTY contesting, to
include a button for "superfill", where the variable exchange info is
repeated many times over. This is what I set up for that DL contest, I
encourage this become part of any standard contest macro package:

F6 Superfill, {TX}{ENTER}{EXCH} {EXCH} {EXCH} {EXCH} {EXCH} {EXCH} {EXCH}
{EXCH}{RX}

In the past Ed W0YK and others have tried to steer folks to "modular
macros". In my modular macro setup, I can use the macro keys to make any
initial exchange have multiple repeats of actual variable exchange
depending on conditions/QRM. I will generally send the variable exchange
info twice in the initial exchange except under the most optimal
conditions, because that is more efficient than having to give fills.

Tim.
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

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