RTTY
[Top] [All Lists]

Re: [RTTY] The RTTY efficiency myth

To: rtty contesting <rtty@contesting.com>
Subject: Re: [RTTY] The RTTY efficiency myth
From: Fabi <va2up@live.ca>
Date: Tue, 15 Jul 2014 10:13:26 -0400
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
Hi guys,
I sometimes wonder who has the most fun in contest. Is it the guys who never 
won or tried to win anything , the same guys that I meet in every single test 
and who are actually happy to give out the points, or is it the very implicated 
and all out to win ones?  Efficiency is for the latter I think and that's great 
but we sure welcome the 'PSE COPY' guys who are just having fun. One day some 
of them will get the urge to 'WIN' something and their macros will get a good 
shave and gain in efficiency, will they still have as much fun?? Hope so.
This forum brings great advice from many top notch contesters, some will take 
the advice some will just read through , that's fine. Just keep having fun and 
by all means...keep on giving out those precious points!
73

Fabi  va2up
http://va2up.com

> Date: Tue, 15 Jul 2014 06:40:39 -0500
> From: k0rc@citlink.net
> To: rtty@contesting.com
> Subject: Re: [RTTY] The RTTY efficiency myth
> 
> "Running out of time" is actually hidden within "Available time of 
> propagation to a given area".
> 
> For example, working the endless stream of JA's on a short opening, you 
> want to be running stations in the 180+ QSOs per hour rate. If the 
> opening lasts 60 minutes, you will put 180 calls into the log. If your 
> exchange is "inefficient", you will put much less than 180 QSOs in your 
> log during that opening.
> 
> As Hank, W6SX, pointed out, your exchange needs to be succinct in order 
> to covey the needed information as quickly as possible. That means: No 
> repeating the report back to the sending station, No "Please copy", No 
> RYRYRY's (I actually saw that in a recent contest!), No diddling around, 
> No AR, SK, K, Just his call, your requisite report to him, and your 
> call. Nothing more!
> 
> 73 de Bob - KØRC in MN
> 
> ------------------------------------------------------------------------
> On 7/15/2014 5:30 AM, Rudy Bakalov via RTTY wrote:
> > You run out of time in any contest, be it RTTY,  CW, or SSB. So this is not 
> > a criteria to decide how efficient the QSOs are. Then you start looking at 
> > how long each QSO takes and see the difference. In other words, look at the 
> > overall QSOs per hour rate.
> >
> > Rudy N2WQ
> >
> > Sent using a tiny keyboard.  Please excuse brevity, typos, or inappropriate 
> > autocorrect.
> >
> >
> >> On Jul 15, 2014, at 6:19 AM, "John  / NS1Z" <ns1zjohn@gmail.com> wrote:
> >>
> >> Thinking about efficient contacts, just how many of us have "run out of 
> >> time" before we have run out of stations to contact during a contest ??
> >>
> >> If the problem is not enough time to work all stations heard wouldn't 
> >> there be other means employed to increase contacts...
> >>
> >>
> >> -----Original Message----- From: Jeff AC0C
> >> Sent: Monday, July 14, 2014 11:19 PM
> >> To: Hank Garretson ; RTTY Reflector
> >> Subject: Re: [RTTY] Getting ready for NAQP RTTY problem
> >>
> >> Ron,
> >>
> >> You would do well to Hank's suggestions.
> >>
> >> RTTY contesting has a focus on efficiency and the best results are obtained
> >> by using the exchanges and formats that are the standards in the RTTY
> >>
> >> _______________________________________________
> >> 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
> >
> 
> _______________________________________________
> 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>