Hi Dennis...
I've noticed that TRlog and N1MM (and probably others) will log "ANE" as 195
if ANE is what you type in as the exchange. So, their smart enough to know
how to handle cut numbers. But like a lot of the others, I prefer cut
numbers not be used, outside of the "NN" in the 5NN RST.
The number 1 being sent as a J, that's one I really don't see the benefit.
I'm not the CW operator I wish I was anyway. And yes, I did pass the 20 wpm
test, but that's been over 20 years ago. And I've spent too much time
exploring other modes. Oh well.
73, Mike K9MI
----- Original Message -----
From: "Dennis Younker NE6I" <ne6i@cox.net>
To: <cq-contest@contesting.com>
Sent: Wednesday, June 06, 2007 04:41
Subject: Re: [CQ-Contest] ARRL "endorses" cut numbers
> This brings up the point that when the rules say that a QSO "number" will
> be
> sent, a cut number is apparently not technically legal.
>
> --Dennis, NE6I
>
> ----- Original Message -----
> From: "David Pruett" <k8cc@comcast.net>
> Cc: <cq-contest@contesting.com>
> Sent: Tuesday, June 05, 2007 8:20 PM
> Subject: Re: [CQ-Contest] ARRL "endorses" cut numbers
>
>
>>I would like to remind everyone that "using" cut numbers is not the same
>> thing as "logging" cut numbers.
>>
>> I check the logs for the ARRL 10M contest, where DX stations send RST &
>> serial numbers for their exchange. If the station sends you a number
>> with cut digits, it is *your* responsibility to turn those into numeric
>> digits in your log. QSO numbers containing alphabetic digits will be
>> scored as non-valid (no penalties, but you lose the QSO). This
>> direction was concurred to by the ARRL Contest Department.
>>
>> I'm sure someone will claim "but I just copied what was sent". No
>> matter - the rules say a QSO *number* must be received and logged, so it
>> is the entrant's responsibility to make the translation, not the log
>> checkers. The entrant is the person present when the QSO is made; if
>> there is any doubt as to what the number is, they are the only ones who
>> can ask for a fill and remove all doubt.
>>
>> Again, it's not my intent to deter the use of cut numbers (although I
>> personally will not), but I want to make it clear that the log (at least
>> for ARRL 10M) must show actual numbers for the QSO to be valid.
>>
>> Dave/K8CC
>>
>>
>> Steve Harrison wrote:
>>> At 11:22 PM 6/4/2007 +0000, kr2q@optonline.net wrote:
>>>
>>>> Sorry...couldn't resist.
>>>>
>>>> See the section titled "Work the Experts" - this is an intro
>>>> for newbies who "can copy and send Morse code at 5 to 10 WPM."
>>>> http://www.arrl.org/news/features/2003/10/21/1/
>>>>
>>>
>>> Oh, brother..... I really didn't need to read that ;o(((((((
>>>
>>> It's been several decades since I did a SS and maybe things have sorta
>>> "evolved" in the meantime...... So I haven't the vaguest idea whether,
>>> for
>>> example, during the 2006 SS, A was often used by the faster ops for 1.
>>>
>>>
>>>> Even QRPers get it.
>>>> See "The 'Secret' Language of the Exchange"
>>>> http://www.arrl.org/news/features/2002/10/21/1/
>>>>
>>>
>>> I can see that, considering the QRPers are a pretty tight-knit and close
>>> group. When I was doing high-speed meteor scatter, we also had a few
>>> shortcuts we'd sometimes take that could completely bamboozle a newbie.
>>>
>>> Steve, K0XP
>>> _______________________________________________
>>> 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
>>
>
> _______________________________________________
> 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
|