As much as I do not necessarily favour cut numbers, I'm at a loss to see why
the ARRL requiring us to translate cut numbers into integers on CW differs
in any way from the ARRL requiring us to translate sent phonetics on phone
into the intended meaning.
I doubt anyone working SS Phone has ever logged "Sugar Juliet Victor" or
"November Tango" for SJV and NT, respectively. And even if phonetics weren't
used, most loggers don't have room either for San Joaquin Valley anyway.
As to the suggestion the ARRL is all wrong on this, well, it's their
contest, it's their prerogative:
2.Conditions of Entry:
2.1.Entrants agree to be bound by the provisions and intent of ARRL
contest rules.
2.2.Entrants agree to be bound by the regulations of their national
licensing authority.
2.3.Entrants agree to be bound by the decisions of the ARRL Awards
Committee.
2.4. All entries become the property of the ARRL.
73, kelly
ve4xt
----- Original Message -----
From: "Paul J. Piercey" <p.piercey@nl.rogers.com>
To: <cq-contest@contesting.com>
Sent: Saturday, December 02, 2006 11:43 AM
Subject: Re: [CQ-Contest] CW abbreviations
Thanks for that, Mike.
I was going to say that from now on my call in contests was going to be
VOAHE and my report in CQ contests would be ENN E, which would increase my
QSO rate by a large amount, but now, taking your lead, I'm going to be E
with the report of ENN E.
24 to go...
73 -- Paul E (formerly VO1HE)
> -----Original Message-----
> From: cq-contest-bounces@contesting.com
> [mailto:cq-contest-bounces@contesting.com] On Behalf Of Mike Fatchett
> Sent: December 2, 2006 17:23
> To: 'David Pruett'; 'José Nunes CT1BOH'
> Cc: cq-contest@contesting.com
> Subject: Re: [CQ-Contest] CW abbreviations
>
> Then I believe it will be the responsibility of the ARRL to
> publish the official cut list so that all may have an
> opportunity to convert what is sent to what should have been sent.
>
> Punishing a station for copying what is sent is just wrong
> whether you or the ARRL dictates it or not! How is a casual
> op supposed to know all the cut number abbreviations?
> Wouldn't it be easier for the ARRL and log checkers to
> include the possible translations in the log checking routine?
>
> I think the ARRL is completely wrong on this one.
>
> I am making it official that T is now the cut abbreviation
> for W0MU. I will be registering it with all appropriate
> registration entities. I guess I will have to send my call
> at least once every 10 mins for FCC regs but other than that
> if you hear T calling it is me.
>
> T
>
>
>
>
>
> -----Original Message-----
> From: cq-contest-bounces@contesting.com
> [mailto:cq-contest-bounces@contesting.com] On Behalf Of David Pruett
> Sent: Friday, December 01, 2006 11:27 PM
> To: José Nunes CT1BOH
> Cc: cq-contest@contesting.com
> Subject: Re: [CQ-Contest] CW abbreviations
>
> All:
>
> On a related note, keep in mind that it is the ARRL
> logchecking position that when receiving a serial number, it
> is the responsibility of the receiving station to translate
> any received cut numbers into numeric digits in the log.
> K9TM and I do the logchecking for the ARRL 10M Contest where
> DX stations send RST/serial numbers as their exchange. If
> CT3NT sends "VVN"to you as his serial number, it is your
> responsibility to turn it into "339".
> If you put "VVN" in the log, your QSO will be scored as invalid.
>
> Now before anybody begins wringing their hands or starts a
> thread complaining that you should "log what is sent", the
> topic is not open for discussion. I've confirmed this
> direction with the ARRL HQ Contest Department, and this is
> the way the 10M Contest Logs have been scored since 1998.
> There is logic to this; cut numbers exist solely to help CW
> operators convey numeric data quicker over the air. It is
> not the logchecker's responsibility to decode these numbers
> to "interpret" your log.
>
> Just trying to be helpful here, not start a controversy
> (which we seem wont to do on the reflector these days). And
> I'm only speaking for the 10M contest, which I'm on the
> logchecking team for.
>
> Dave/K8CC
>
>
> José Nunes CT1BOH wrote:
> > MR Tree says
> >
> > "PS: What about sending VV for "33" - anyone have a problem
> with that?"
> >
> > Well I don't since I used it from CT3NT.
> >
> > Do you have a problem when you send 5NN and use N for 9?
> Guess not cuz
> > you are doing it all along.
> > If you don't why should you have a problem when I use V for a 3? Or
> > some abbreviations are OK and others are not?
> >
> > As far as CW numbers go I see the following abbreviations:
> >
> > 1=A
> > 2=U
> > 3=V
> > 4
> > 5=E
> > 6
> > 7=B
> > 8=D
> > 9=N
> > 0=T
> >
> > CW is a mode where abbreviations are common and are there
> to save time.
> > Probably you are not aware but:
> >
> > transmitting "33" times 7.000 at 40wpm = 105.73 minutes
> transmitting
> > "8" times 7.000 at 40wpm= 54.59 minutes Transmitting "VV"
> times 7.000
> > at 40wpm= 76.56 minutes
> >
> > And I'm still 22 minutes behind the zone 8 guys,
> transmitting just the
> > zone for every QSO made
> >
> > EE CT3NT
> >
> > Ohh do you also have a problem I send EE instead of TU?!
> >
> >
>
>
> _______________________________________________
> 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
|