RTTY
[Top] [All Lists]

Re: [RTTY] The RTTY efficiency myth and SUPERFILL

To: john <w8wej@citynet.net>, RTTY Reflector <RTTY@contesting.com>
Subject: Re: [RTTY] The RTTY efficiency myth and SUPERFILL
From: Dave Greig <daven3buo@att.net>
Date: Wed, 16 Jul 2014 17:26:28 -0500
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
John I also send TU in contests for the same reason.

Thank You!
Dave Greig N3BUO
*801 Tactical*
Phone: (682) 422-6667
http://www.801tactical.com
Google Plus: gplus.to/801Tactical
Facebook: https://www.facebook.com/801Tactical
Twitter: @801tactical


On Wed, Jul 16, 2014 at 5:24 PM, john <w8wej@citynet.net> wrote:

> with great reluctance,,, I was going to eliminate  the "TU" in the
> exchange---I have always felt, and still feel  that the rtty bunch is the
> nicest group of competitors that I have ever encountered, and,,, always
> felt pleasure in expressing my  thanks of a  contest qso by a "TU"--
>  I understand the need for speed and a "TU" multiplier by hundreds of
> times  would eat up time for  the big gun contester--   I get that,,,but
> still we, the rtty folks are a unique group--I feel notches above the
> average,,, I hate to see that being lost--as I write this,,, I want to go
> back to my roots--a "TU" is needed to remind the big guns,and everyone, if
> it were not for us little shots,,big gamers  would have very few folk  to
> work,..
> get over it--the "TU"    is staying  in to my macros--
> a matter of perspective.  If we can not take time to appreciate and
> acknowledge  the efforts of others, is a shame, for all of us,,,
> ,It is, or at least , should be a hobby,,,please lets keep it that
> way....see you this weekend  with a "TU"
>
> 73 and "good luck in the contest"
> john
>
>
>
>
>
> On 7/16/2014 16:42, Tim Shoppa wrote:
>
>> 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
>>
>>
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2014.0.4716 / Virus Database: 3986/7864 - Release Date: 07/16/14
>>
>>
>>
> _______________________________________________
> RTTY mailing list
> RTTY@contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
>
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

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