[CQ-Contest] Fewer CK and SEC Repeat Requests in SS

Mike Fatchett mike at mallardcove.com
Mon Nov 6 20:53:42 EST 2006


As a journeyman CW op some of the number combination just threw me
completely.  I don't know why.  Speed did not seem to be the overall
determining factor of error either.

I always cringe when the UBN reports come out for code.  I really need to
operate more CW.

Mike W0MU 

-----Original Message-----
From: cq-contest-bounces at contesting.com
[mailto:cq-contest-bounces at contesting.com] On Behalf Of Eric Hilding
Sent: Monday, November 06, 2006 4:41 PM
To: cq-contest at contesting.com
Cc: nccc at contesting.com; writelog at contesting.com
Subject: [CQ-Contest] Fewer CK and SEC Repeat Requests in SS

I just love it when a plan comes together.

This year I experienced fewer CK and SEC Repeat Requests in SS, which I
attribute to specifically adding some tweaked partial spacing between the
characters in the WriteLog message slots.

5^^7 s^c^v

If you have a CK or SEC which has caused you too many repeat request
problems, you might consider a similar approach for SS next year.  Methinks
"casual" once-per-year SS ops have the biggest difficulty in copying data at
higher speeds.  I may retweak things again to hopefully further reduce the
repeat requests.

Yeah, I know, there will always be *some* repeat requests do to QRM ;-(

FYI & 73...

RIck, K6VVA
_______________________________________________
CQ-Contest mailing list
CQ-Contest at contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest



More information about the CQ-Contest mailing list