CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] WHY - and other observed behavior

To: cq-contest@contesting.com
Subject: Re: [CQ-Contest] WHY - and other observed behavior
From: john@kk9a.com
Date: Tue, 26 Nov 2013 08:25:00 -0500
List-post: <cq-contest@contesting.com">mailto:cq-contest@contesting.com>
A running station should not be sending faster than their copying ability,
however I agree slowing down (a little) is still good advice to get your
callsign copied correctly.  Just don't slow down too much. I have had
stations send super slow when I missed part of their callsign and it
really throws me off.

John KK9A  P40A


To:     cq-contest@contesting.com
Subject:         [CQ-Contest] WHY - and other observed behavior
From:   kr2q@optimum.net
Date:    Mon, 25 Nov 2013 19:14:54 +0000 (GMT)


[snip]


MY OTHER NOTABLE OBSERVATION:
If they guy you're calling is not getting your call, SLOW DOWN.  I heard many
of the USA
M/M's dumping it in.  The DX came back with their partial or busted call. 
The
US guys seem
to forget that CW has a speed control.  What a waste of time.  If the DX
can't
copy 40 wpm,
do you think sending your call 3x, 4x, or 5x is going to teach him how to
copy
faster?

Even worse, not uncommonly, the DX never got the caller's callsign correct.
But the caller,
knowing how the CQWW log analysis system works (busted calls have no
impact on
the caller,
but rather only on the logger), simply moves off, knowing full well that
their
call was busted
in the other guys log.  The M/M gets credit while the poor DX he works gets
dinged.  SHAME!

For goodness sake, just SLOW DOWN so the DX can copy you.  It takes more time
to do it
the wrong way and end up with one party getting dinged for a busted call.
Teach your
op's how to QRS on cw.  Honestly, QRSing to 25 wpm is just NOT THAT SLOW!  Do
the right
thing!

de Doug KR2Q

_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest

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