CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] When is speed not speedy?

To: Rex Maner <k7qq@netzero.net>
Subject: Re: [CQ-Contest] When is speed not speedy?
From: Jeffrey Embry <jeffrey.embry@gmail.com>
Reply-to: jeffrey.embry@gmail.com
Date: Fri, 31 May 2013 14:39:24 -0400
List-post: <cq-contest@contesting.com">mailto:cq-contest@contesting.com>
I agree with Bob and Rex, but for some odd reason I don't mind a cut
number 0 (T) if they are beginning with a SN like 001.  My mind can
handle that...but once past 100 I like, and expect to hear no cut
numbers.

73,

-- 
Jeff Embry, K3OQ
FM19nb
ARCI #11643, FPQRP #-696,
QRP-L # 67, NAQCC #25, ARS #1733
AMSAT LM-2263

--
WWWDWOA?
(What Would We Do Without Acronyms?)


On Fri, May 31, 2013 at 12:04 PM, Rex Maner <k7qq@netzero.net> wrote:
> Bob
>
> I agree 100% with use of 5nn  and  also - - 2 in a serial nr exchange,  and
> as you say under condx as we had last weekend , I ask many to QRS and repeat
> the SN several times to attempt to get it in the log correct.  I have enough
> problem with FAT Finger hi hi.
>
> Quack  aka:   Rex K7QQ
>
>
> -----Original Message-----
> From: CQ-Contest [mailto:cq-contest-bounces@contesting.com] On Behalf Of
> Robert Chudek - K0RC
> Sent: Friday, May 31, 2013 3:38 PM
> To: cq-contest@contesting.com
> Subject: Re: [CQ-Contest] When is speed not speedy?
>
> I don't care for cut numbers other than 5NN, the standard "synch pulse"
> of contest exchanges.
>
> During the WPX last weekend with very poor conditions, those using cut
> numbers hurt themselves and the stations they were working. Of all the
> stations I worked who used cut numbers, at least 75% of them I needed to ask
> for a repeat, if not two or more repeats. Here's why...
>
> The number sequence 0 to 9 (should) always contain 5 'elements'. Sending
> numbers in this manner provides a built-in error checking scheme. If I am
> expecting a serial number and I hear two dits and one dah, I already know
> this will be the number 2. When I hear the remaining two dahs, this confirms
> that I just heard the number two. Likewise, if I hear a dah dit, I already
> know this is the number 6, and the trailing three dits confirms that.
>
> Furthermore, when listening to a sequence of four numbers, I am expecting
> four groups of 5-elements with appropriate spacing between the groups. This
> built-in error checking can often survive moderate QRN without having to ask
> for a repeat.
>
> However, when you start throwing cut numbers into the sequence, the entire
> error checking scheme goes out the window and requires a strong, noiseless
> environment. This was not the band conditions I experienced last weekend. In
> addition to QRN, the propagation, auroral flutter, and back scatter was
> severely distorting signals at times. It was tough enough receiving the full
> 5-element numbers, let alone a solo dit or dah thrown into the middle of a
> serial number sequence.
>
> Those of you who use cut numbers should be aware that I will continue to ask
> for a repeat until I am 100% confident I received the correct number for the
> log. I am not about to take a 3X penalty because you believe using cut
> numbers has some kind of advantage.
>
> 73 de Bob - KØRC in MN
>
> ------------------------------------------------------------------------
> On 5/31/2013 5:48 AM, Ktfrog007@aol.com wrote:
>> I agree with the comment below.  I do a lot of S&P and always try  to
>> get the serial number of the previous QSO if possible.  I still have
>> to  be alert when I am are sent a serial number because SO2Rs can jump
>> by more  than one if an intervening QSO occurred on another band.  I
>> don't expect  any running station to slow down for me unless I ask them
> to.
>>
>> There are stations where I can copy the call sign but not the serial
> number
>>   if they are very fast and using high cut numbers.  I recognize a lot
>> of well known calls, plus I may have worked them earlier on another
>> band.  It seems that I get older and slower all the time and everyone else
> is getting
>> faster.  After this WPX-CW I added a QRS PSE button to my N1MM.   I expect
>> I'll be using it since most likely I'll be older yet next year.
>>
>> I don't understand why some speed demons don't slow down or stop
>> cutting toward the end of the contest as their numbers get high and
>> they are working the  Sunday afternoon and evening casual ops who are
>> just on for fun and to give  out a few Qs.  It's rude to blast back at
>> these folks who  are really just helping out the high scorers.  Show some
> gratitude and slow  down, guys.
>>
>> 73,
>> Kermit, AB1J
>>
>>
>> In a message dated 5/30/2013 22:29:12 Coordinated Universal Time,
>> john@kk9a.com writes:
>>
>> If  you
>> call someone, they assume that you were already able to copy  their
>> callsign and that you would be able to copy the report and recognize
>> your callsign at their speed. You probably already heard the report
>> that  they gave to the station before you so you should already have
>> some idea  what to expect.
>> _______________________________________________
>> CQ-Contest mailing list
>> CQ-Contest@contesting.com
>> http://lists.contesting.com/mailman/listinfo/cq-contest
>>
>
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
>
> ____________________________________________________________
> BlackBerry&#174 10
> Find out more about the new BlackBerry 10 smartphone.
> http://thirdpartyoffers.netzero.net/TGL3241/51a8ca1c20de94a1b53bfst01vuc
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest



-- 
Jeff Embry, K3OQ
FM19nb
ARCI #11643, FPQRP #-696,
QRP-L # 67, NAQCC #25, ARS #1733
AMSAT LM-2263

--
WWWDWOA?
(What Would We Do Without Acronyms?)
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest

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