There are a million reasons why an operator may be slow to respond or not
respond, never mind SO2R. They could be having a software issue, a stupid
little moth flew into your eye, a sneezing fit, a group of visitors arrives
("he's just doing rtty..."), etc. I had all of these and more happen to me
this time out (though I must say the visitors this time were very nice and
caused no delays ;)
There was one loud top ten finisher who didn't answer my CQ despite
multiple tries. I assume that 1) he is not avoiding giving me his mult; 2)
he is not inexperienced; 3) there is some reasonable explanation - maybe
some quirk of propagation?
73 jeff wk6i
On Mon, Jul 17, 2017 at 8:58 AM, Richard Kriss <aa5vu@arrl.net> wrote:
> I enjoyed the NAQP-RTTY contest and the majority were very good operators.
> My Pet Peeve is the unskilled operator trying to run SO2R. Skilled SO2R
> operators are seamless and the S&P callers never know the station calling
> CQ are running SO2R. To S&P operators an unskilled CQ station seems to be
> deaf, keeps calling CQ over and over again and not responding to S&P
> callers. My guess is the SO2R station may be tied up working pileup of S&P
> callers on another band.
>
> If you are an SO2R operator and start getting a lot of action on one band,
> turn off the CQ bubble machine on the other band until you work the pileup
> down to a manageable level.
>
> My 2-cents worth!
>
> Dick AA5VU
> _______________________________________________
> RTTY mailing list
> RTTY@contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
>
--
Jeff Stai ~ wk6i.jeff@gmail.com
Twisted Oak Winery ~ http://www.twistedoak.com/
Facebook ~ http://www.facebook.com/twistedoak
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|