I thought you had to have correct information in your log for contacts in
any contest... So which contests allow us to do half the job?
Dave AFP
On Tue, Mar 12, 2019 at 12:36 PM NM5M <nm5meric@gmail.com> wrote:
> Don’t forget, in the Russian contest, the contest sponsor penalizes
> stations if the receiving party doesn’t get the information correctly into
> their log. To simplify, both stations have to copy correct information in
> order to get full points for the contact.
>
> We could learn something from the way the Russians score their contest.
>
> 73,
>
> NM5M
>
> Sent from my iPhone
>
> > On Mar 12, 2019, at 8:56 AM, cq-contest-request@contesting.com wrote:
> >
> > Send CQ-Contest mailing list submissions to
> > cq-contest@contesting.com
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > http://lists.contesting.com/mailman/listinfo/cq-contest
> > or, via email, send a message with subject or body 'help' to
> > cq-contest-request@contesting.com
> >
> > You can reach the person managing the list at
> > cq-contest-owner@contesting.com
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of CQ-Contest digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Phone Fray - Daylight Savings Time - Tuesday Nights
> > (dfaklis@frontiernet.net)
> > 2. Serial # contests, speed? (Mike Smith VE9AA)
> > 3. Re: Serial # contests, speed? (K9MA)
> > 4. Re: Serial # contests, speed? (Edward Sawyer)
> > 5. Re: Serial # contests, speed? (rjairam@gmail.com)
> > 6. Re: Serial # contests, speed? (jimk8mr@aol.com)
> > 7. Re: Serial # contests, speed? (Bob Shohet, KQ2M)
> > 8. Re: Serial # contests, speed? (Ed K1EP)
> > 9. Serial # contests, speed? (Bill Parry)
> > 10. Serial # contests, speed? (jpescatore@aol.com)
> > 11. Re: Serial # contests, speed? (Dave Edmonds)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Mon, 11 Mar 2019 22:16:05 +0000 (UTC)
> > From: "dfaklis@frontiernet.net" <dfaklis@frontiernet.net>
> > To: "cq-contest@contesting.com" <cq-contest@contesting.com>, MRRC
> > Reflector <mrrc@contesting.com>
> > Subject: [CQ-Contest] Phone Fray - Daylight Savings Time - Tuesday
> > Nights
> > Message-ID: <409963253.2905044.1552342565021@mail.yahoo.com>
> > Content-Type: text/plain; charset=UTF-8
> >
> > Phone Fray - Tuesday Evening, 10:30pm EDT (0230-0300z Wednesday),
> 30-minute SSB contest.? Please bring a friend and introduce a new contester
> into the mix.? One QSO or many, please enter your score.
> >
> > The Phone Fray is weekly and mirrors NAQP SSB; exchange name and S/P/C,
> mults per band.
> >
> > Suggested center frequencies are:? 21.325, 14.250, 7.175, 3.800, 1.875.?
> General Ops can be found above 3.800.
> >
> > 20 may be open at the start, then folks move down to 40, 80, and Q's are
> had on 160 in the last 5-10 minutes.
> >
> > Rules are here:? http://www.perluma.com/Phone_Fray_Contest_Rules.pdf
> >
> > Join the free Yahoo Groups Reflector for communications:
> > https://groups.yahoo.com/neo/groups/PhoneFray/info
> >
> > No logs, just report scores to http://www.3830scores.com
> >
> > Please forward this email to your clubs and amateurs that might be
> interested.?? Great for new contesters and veterans alike.
> >
> > Thanks!
> >
> > 73, Dean, NW2K
> >
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Mon, 11 Mar 2019 21:44:17 -0300
> > From: "Mike Smith VE9AA" <ve9aa@nbnet.nb.ca>
> > To: <cq-contest@contesting.com>
> > Subject: [CQ-Contest] Serial # contests, speed?
> > Message-ID: <002e01d4d86c$b9f0a350$2dd1e9f0$@nbnet.nb.ca>
> > Content-Type: text/plain; charset="us-ascii"
> >
> > For contests like RDX and WPX where the exchange is a serial #, do you:
> >
> >
> >
> > . Go as fast as always. (34-36wpm) , risking your qso partner
> busting
> > the #,but keeping rate high.
> >
> > . Go a bit slower (30-32wpm), hoping the QRS improves the copy &
> > reduces busted exchanges.
> >
> > . Send everything just as fast as normal (whatever that speed is),
> but
> > use brackets <<>> (a la N1MM) to slow down JUST the serial #
> >
> > . Slow down only for obviously slow callers
> >
> > . Something else?
> >
> >
> >
> > Inquiring minds.
> >
> >
> >
> > I don't want to skew the results, so I won't say (yet) what I do. (and
> who
> > knows if what I do is even 'right')
> >
> >
> >
> > Mike VE9AA
> >
> >
> >
> > Mike, Coreen & Corey
> >
> > Keswick Ridge, NB
> >
> >
> >
> >
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Mon, 11 Mar 2019 20:02:55 -0600
> > From: K9MA <k9ma@sdellington.us>
> > To: Mike Smith VE9AA <ve9aa@nbnet.nb.ca>
> > Cc: cq-contest@contesting.com
> > Subject: Re: [CQ-Contest] Serial # contests, speed?
> > Message-ID: <C7FA205D-26C9-4065-818E-C4B7227D2961@sdellington.us>
> > Content-Type: text/plain; charset=utf-8
> >
> > I slow down to the other?s speed, if necessary, and further if
> conditions are poor. I think slowing down just for the sn is
> counterproductive.
> >
> > 73,
> > Scott K9MA
> >
> > ----------
> >
> > Scott Ellington
> >
> > --- via iPad
> >
> >> On Mar 11, 2019, at 6:44 PM, Mike Smith VE9AA <ve9aa@nbnet.nb.ca>
> wrote:
> >>
> >> For contests like RDX and WPX where the exchange is a serial #, do you:
> >>
> >>
> >>
> >> . Go as fast as always. (34-36wpm) , risking your qso partner
> busting
> >> the #,but keeping rate high.
> >>
> >> . Go a bit slower (30-32wpm), hoping the QRS improves the copy &
> >> reduces busted exchanges.
> >>
> >> . Send everything just as fast as normal (whatever that speed
> is), but
> >> use brackets <<>> (a la N1MM) to slow down JUST the serial #
> >>
> >> . Slow down only for obviously slow callers
> >>
> >> . Something else?
> >>
> >>
> >>
> >> Inquiring minds.
> >>
> >>
> >>
> >> I don't want to skew the results, so I won't say (yet) what I do. (and
> who
> >> knows if what I do is even 'right')
> >>
> >>
> >>
> >> Mike VE9AA
> >>
> >>
> >>
> >> Mike, Coreen & Corey
> >>
> >> Keswick Ridge, NB
> >>
> >>
> >>
> >> _______________________________________________
> >> CQ-Contest mailing list
> >> CQ-Contest@contesting.com
> >> http://lists.contesting.com/mailman/listinfo/cq-contest
> >
> >
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Mon, 11 Mar 2019 22:01:42 -0400
> > From: Edward Sawyer <EdwardS@sbelectronics.com>
> > To: Mike Smith VE9AA <ve9aa@nbnet.nb.ca>, "cq-contest@contesting.com"
> > <cq-contest@contesting.com>
> > Subject: Re: [CQ-Contest] Serial # contests, speed?
> > Message-ID:
> > <
> 0D39B6681B67B44DAEC5D6AD99294A8E047CF8ED1E61@SBEMAIL.sbelectronics.com>
> >
> > Content-Type: text/plain; charset="us-ascii"
> >
> > For WPX and Russia DX or ARRL or CQWW, for me it doesn't matter, serial
> # or not. If conditions are good and you are working Europe, especially,
> Russia and Eastern Europe, its fast 36 - 40. If its all US or South
> America I slow it down to 32 - 34. When conditions are more marginal
> especially with QSB, I use 28 - 30. Especially over the pole - 26 - 28.
> >
> > Ed N1UR
> >
> > -----Original Message-----
> > From: CQ-Contest [mailto:cq-contest-bounces@contesting.com] On Behalf
> Of Mike Smith VE9AA
> > Sent: Monday, March 11, 2019 8:44 PM
> > To: cq-contest@contesting.com
> > Subject: [CQ-Contest] Serial # contests, speed?
> >
> > For contests like RDX and WPX where the exchange is a serial #, do you:
> >
> >
> >
> > . Go as fast as always. (34-36wpm) , risking your qso partner
> busting
> > the #,but keeping rate high.
> >
> > . Go a bit slower (30-32wpm), hoping the QRS improves the copy &
> > reduces busted exchanges.
> >
> > . Send everything just as fast as normal (whatever that speed is),
> but
> > use brackets <<>> (a la N1MM) to slow down JUST the serial #
> >
> > . Slow down only for obviously slow callers
> >
> > . Something else?
> >
> >
> >
> > Inquiring minds.
> >
> >
> >
> > I don't want to skew the results, so I won't say (yet) what I do. (and
> who knows if what I do is even 'right')
> >
> >
> >
> > Mike VE9AA
> >
> >
> >
> > Mike, Coreen & Corey
> >
> > Keswick Ridge, NB
> >
> >
> >
> > _______________________________________________
> > CQ-Contest mailing list
> > CQ-Contest@contesting.com
> > http://lists.contesting.com/mailman/listinfo/cq-contest
> >
> >
> > ------------------------------
> >
> > Message: 5
> > Date: Mon, 11 Mar 2019 22:05:47 -0400
> > From: "rjairam@gmail.com" <rjairam@gmail.com>
> > To: Mike Smith VE9AA <ve9aa@nbnet.nb.ca>
> > Cc: CQ-Contest Reflector <cq-contest@contesting.com>
> > Subject: Re: [CQ-Contest] Serial # contests, speed?
> > Message-ID:
> > <CAMCyBs6k43PRTDN14_t8r7c9vjAGdWqE1R8iadZ1R1Z7Wk+VOg@mail.gmail.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > Automatically have software go slower to send the exchange.
> >
> > 73
> > Ria, N2RJ
> >
> >> On Mon, 11 Mar 2019 at 21:58, Mike Smith VE9AA <ve9aa@nbnet.nb.ca>
> wrote:
> >>
> >> For contests like RDX and WPX where the exchange is a serial #, do you:
> >>
> >>
> >>
> >> . Go as fast as always. (34-36wpm) , risking your qso partner
> busting
> >> the #,but keeping rate high.
> >>
> >> . Go a bit slower (30-32wpm), hoping the QRS improves the copy &
> >> reduces busted exchanges.
> >>
> >> . Send everything just as fast as normal (whatever that speed
> is), but
> >> use brackets <<>> (a la N1MM) to slow down JUST the serial #
> >>
> >> . Slow down only for obviously slow callers
> >>
> >> . Something else?
> >>
> >>
> >>
> >> Inquiring minds.
> >>
> >>
> >>
> >> I don't want to skew the results, so I won't say (yet) what I do. (and
> who
> >> knows if what I do is even 'right')
> >>
> >>
> >>
> >> Mike VE9AA
> >>
> >>
> >>
> >> Mike, Coreen & Corey
> >>
> >> Keswick Ridge, NB
> >>
> >>
> >>
> >> _______________________________________________
> >> CQ-Contest mailing list
> >> CQ-Contest@contesting.com
> >> http://lists.contesting.com/mailman/listinfo/cq-contest
> >
> >
> >
> > --
> > Ria Jairam, N2RJ
> > Director, Hudson Division
> > ARRL - The national association for Amateur Radio?
> > +1.973.594.6275
> > https://hudson.arrl.org
> > n2rj@arrl.org
> >
> >
> > ------------------------------
> >
> > Message: 6
> > Date: Tue, 12 Mar 2019 02:15:35 +0000 (UTC)
> > From: jimk8mr@aol.com
> > To: ve9aa@nbnet.nb.ca, cq-contest@contesting.com
> > Subject: Re: [CQ-Contest] Serial # contests, speed?
> > Message-ID: <2066153686.3273616.1552356935422@mail.yahoo.com>
> > Content-Type: text/plain; charset=UTF-8
> >
> > I'm of a keep it at the same speed style - I don't think the 300
> milliseconds one saves by sending 5NN at warp speed compensates for the
> other guy's brain having to shift gears to copy what I'm sending.
> > I judge just how fast I'm sending by the nature of the pileup (assuming
> I have one!). The bigger the pileup, the safer it is to go fast, as it is
> quite likely the guy you're working just listened to your previous QSO and
> knows how to increment a number.
> >
> > Maybe not so much in serial number contests, but in a no-brain exchange
> contest (i.e. CQWW) sending on the fast side puts a sense of urgency for
> the other guy to call you now.
> >
> > And as a contest wears on, yes, sending somewhat slower is a good
> strategy. And if for some reason (hopefully other than you got spotted with
> a busted call) you do get a small pileup, go ahead and bump up the speed a
> bit.
> >
> >
> > 73? -? Jim? K8MR
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: Mike Smith VE9AA <ve9aa@nbnet.nb.ca>
> > To: cq-contest <cq-contest@contesting.com>
> > Sent: Mon, Mar 11, 2019 9:58 pm
> > Subject: [CQ-Contest] Serial # contests, speed?
> >
> > For contests like RDX and WPX where the exchange is a serial #, do you:
> >
> >
> >
> > .? ? ? Go as fast as always. (34-36wpm) , risking your qso partner
> busting
> > the #,but keeping rate high.
> >
> > .? ? ? Go a bit slower (30-32wpm), hoping the QRS improves the copy &
> > reduces busted exchanges.
> >
> > .? ? ? Send everything just as fast as normal (whatever that speed is),
> but
> > use brackets <<>> (a la N1MM) to slow down JUST the serial #
> >
> > .? ? ? Slow down only for obviously slow callers
> >
> > .? ? ? Something else?
> >
> >
> >
> > Inquiring minds.
> >
> >
> >
> > I don't want to skew the results, so I won't say (yet) what I do. (and
> who
> > knows if what I do is even 'right')
> >
> >
> >
> > Mike VE9AA
> >
> >
> >
> >
> > ------------------------------
> >
> > Message: 7
> > Date: Tue, 12 Mar 2019 00:18:04 -0400
> > From: "Bob Shohet, KQ2M" <kq2m@kq2m.com>
> > To: <jimk8mr@aol.com>, <ve9aa@nbnet.nb.ca>,
> > <cq-contest@contesting.com>
> > Subject: Re: [CQ-Contest] Serial # contests, speed?
> > Message-ID: <A2E111074D3949F6BBB370BE544F0B44@BOBWINPC1PC>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > What is fun is when a super op type calls you and you KNOW that you can
> speed up and send it to him at 60 wpm and he will get it the first time and
> vice-versa if I I call him/her. Get?s the blood pumping a little faster
> and puts a smile on my face (and hopefully theirs). :-) And there are
> some slow sending ops that can copy qrq easily ? but just can?t send fast ?
> and your turning up the speed to send to them is like a knowing handshake
> saluting their copying skill ? ?Hey I know who you are ? you?re a really
> good op so I am going to send fast to you!?.
> >
> > It also gets the attention of the pileup ? makes them listen and wonder
> what is going on. If they are listening then they are not transmitting
> which means that when the weak guy calls you will copy him and work him.
> Sometimes that weak guy is a polar path mult that you would never have
> heard if/when everyone was calling at once!
> >
> > It pays to slow down if cndx are disturbed and the signals start to
> sound auroral and/or of have significant flutter (like the W1 path to JA) ?
> if you are sending fast you will be harder to understand and callers may
> pass you by.
> >
> > 73
> >
> > Bob KQ2M
> >
> >
> > From: K8MR via CQ-Contest
> > Sent: Monday, March 11, 2019 10:15 PM
> > To: ve9aa@nbnet.nb.ca ; cq-contest@contesting.com
> > Subject: Re: [CQ-Contest] Serial # contests, speed?
> >
> > I'm of a keep it at the same speed style - I don't think the 300
> milliseconds one saves by sending 5NN at warp speed compensates for the
> other guy's brain having to shift gears to copy what I'm sending.
> >
> > I judge just how fast I'm sending by the nature of the pileup (assuming
> I have one!). The bigger the pileup, the safer it is to go fast, as it is
> quite likely the guy you're working just listened to your previous QSO and
> knows how to increment a number.
> >
> > Maybe not so much in serial number contests, but in a no-brain exchange
> contest (i.e. CQWW) sending on the fast side puts a sense of urgency for
> the other guy to call you now.
> >
> > And as a contest wears on, yes, sending somewhat slower is a good
> strategy. And if for some reason (hopefully other than you got spotted with
> a busted call) you do get a small pileup, go ahead and bump up the speed a
> bit.
> >
> >
> > 73 - Jim K8MR
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: Mike Smith VE9AA <ve9aa@nbnet.nb.ca>
> > To: cq-contest <cq-contest@contesting.com>
> > Sent: Mon, Mar 11, 2019 9:58 pm
> > Subject: [CQ-Contest] Serial # contests, speed?
> >
> > For contests like RDX and WPX where the exchange is a serial #, do you:
> >
> >
> >
> > . Go as fast as always. (34-36wpm) , risking your qso partner
> busting
> > the #,but keeping rate high.
> >
> > . Go a bit slower (30-32wpm), hoping the QRS improves the copy &
> > reduces busted exchanges.
> >
> > . Send everything just as fast as normal (whatever that speed is),
> but
> > use brackets <<>> (a la N1MM) to slow down JUST the serial #
> >
> > . Slow down only for obviously slow callers
> >
> > . Something else?
> >
> >
> >
> > Inquiring minds.
> >
> >
> >
> > I don't want to skew the results, so I won't say (yet) what I do. (and
> who
> > knows if what I do is even 'right')
> >
> >
> >
> > Mike VE9AA
> >
> >
> > _______________________________________________
> > CQ-Contest mailing list
> > CQ-Contest@contesting.com
> > http://lists.contesting.com/mailman/listinfo/cq-contest
> >
> >
> > ------------------------------
> >
> > Message: 8
> > Date: Tue, 12 Mar 2019 05:25:58 -0400
> > From: Ed K1EP <k1ep.list@gmail.com>
> > To: jimk8mr@aol.com
> > Cc: ve9aa@nbnet.nb.ca, cq Contest <cq-contest@contesting.com>
> > Subject: Re: [CQ-Contest] Serial # contests, speed?
> > Message-ID:
> > <CAKR4uUNq7qoQ2XRqRA=UmLPm9WOxg21na9sKUL8m8a8nQQOXDQ@mail.gmail.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > What I don't get are those who send at warp speed, but pause a second or
> > two before sending the exchange. Same amount of time if you just
> eliminated
> > the pause and sent at non-warp speed.
> >
> > On Mon, Mar 11, 2019, 23:41 K8MR via CQ-Contest <
> cq-contest@contesting.com>
> > wrote:
> >
> >> I'm of a keep it at the same speed style - I don't think the 300
> >> milliseconds one saves by sending 5NN at warp speed compensates for the
> >> other guy's brain having to shift gears to copy what I'm sending.
> >> I judge just how fast I'm sending by the nature of the pileup (assuming
> I
> >> have one!). The bigger the pileup, the safer it is to go fast, as it is
> >> quite likely the guy you're working just listened to your previous QSO
> and
> >> knows how to increment a number.
> >>
> >> Maybe not so much in serial number contests, but in a no-brain exchange
> >> contest (i.e. CQWW) sending on the fast side puts a sense of urgency for
> >> the other guy to call you now.
> >>
> >> And as a contest wears on, yes, sending somewhat slower is a good
> >> strategy. And if for some reason (hopefully other than you got spotted
> with
> >> a busted call) you do get a small pileup, go ahead and bump up the
> speed a
> >> bit.
> >>
> >>
> >> 73 - Jim K8MR
> >>
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Mike Smith VE9AA <ve9aa@nbnet.nb.ca>
> >> To: cq-contest <cq-contest@contesting.com>
> >> Sent: Mon, Mar 11, 2019 9:58 pm
> >> Subject: [CQ-Contest] Serial # contests, speed?
> >>
> >> For contests like RDX and WPX where the exchange is a serial #, do you:
> >>
> >>
> >>
> >> . Go as fast as always. (34-36wpm) , risking your qso partner
> busting
> >> the #,but keeping rate high.
> >>
> >> . Go a bit slower (30-32wpm), hoping the QRS improves the copy &
> >> reduces busted exchanges.
> >>
> >> . Send everything just as fast as normal (whatever that speed is),
> but
> >> use brackets <<>> (a la N1MM) to slow down JUST the serial #
> >>
> >> . Slow down only for obviously slow callers
> >>
> >> . Something else?
> >>
> >>
> >>
> >> Inquiring minds.
> >>
> >>
> >>
> >> I don't want to skew the results, so I won't say (yet) what I do. (and
> who
> >> knows if what I do is even 'right')
> >>
> >>
> >>
> >> Mike VE9AA
> >>
> >>
> >> _______________________________________________
> >> CQ-Contest mailing list
> >> CQ-Contest@contesting.com
> >> http://lists.contesting.com/mailman/listinfo/cq-contest
> >>
> >
> >
> > ------------------------------
> >
> > Message: 9
> > Date: Tue, 12 Mar 2019 05:00:39 -0500
> > From: "Bill Parry" <bparry@rgv.rr.com>
> > Cc: <cq-contest@contesting.com>
> > Subject: [CQ-Contest] Serial # contests, speed?
> > Message-ID: <000001d4d8ba$7445b8b0$5cd12a10$@rgv.rr.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > I have noticed that I need to send a little slower in JA pileups than in
> EU ones. Not sure why but if I try to speed up past 30 in a JA pileup the
> pileup starts to dwindle. If the pileup is unruly I DO speed up.
> >
> > Bill
> >
> > -----Original Message-----
> > From: CQ-Contest <cq-contest-bounces@contesting.com> On Behalf Of K9MA
> > Sent: Monday, March 11, 2019 9:03 PM
> > To: Mike Smith VE9AA <ve9aa@nbnet.nb.ca>
> > Cc: cq-contest@contesting.com
> > Subject: Re: [CQ-Contest] Serial # contests, speed?
> >
> > I slow down to the other?s speed, if necessary, and further if
> conditions are poor. I think slowing down just for the sn is
> counterproductive.
> >
> > 73,
> > Scott K9MA
> >
> > ----------
> >
> > Scott Ellington
> >
> > --- via iPad
> >
> >> On Mar 11, 2019, at 6:44 PM, Mike Smith VE9AA <ve9aa@nbnet.nb.ca>
> wrote:
> >>
> >> For contests like RDX and WPX where the exchange is a serial #, do you:
> >>
> >>
> >>
> >> . Go as fast as always. (34-36wpm) , risking your qso partner
> busting
> >> the #,but keeping rate high.
> >>
> >> . Go a bit slower (30-32wpm), hoping the QRS improves the copy &
> >> reduces busted exchanges.
> >>
> >> . Send everything just as fast as normal (whatever that speed
> is), but
> >> use brackets <<>> (a la N1MM) to slow down JUST the serial #
> >>
> >> . Slow down only for obviously slow callers
> >>
> >> . Something else?
> >>
> >>
> >>
> >> Inquiring minds.
> >>
> >>
> >>
> >> I don't want to skew the results, so I won't say (yet) what I do. (and
> >> who knows if what I do is even 'right')
> >>
> >>
> >>
> >> Mike VE9AA
> >>
> >>
> >>
> >> Mike, Coreen & Corey
> >>
> >> Keswick Ridge, NB
> >>
> >>
> >>
> >> _______________________________________________
> >> 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
> >
> >
> >
> > ------------------------------
> >
> > Message: 10
> > Date: Tue, 12 Mar 2019 11:17:48 +0000 (UTC)
> > From: jpescatore@aol.com
> > To: CQ-Contest@CONTESTING.COM
> > Subject: [CQ-Contest] Serial # contests, speed?
> > Message-ID: <939833448.4053654.1552389468740@mail.yahoo.com>
> > Content-Type: text/plain; charset=UTF-8
> >
> > I'll generally stay at high speed unless the caller is obviously slower.
> Then I will send their callsign back full speed and hit the PageDown key a
> few times before the variable part of the exchange, then back up.?
> > For information free exchanges, like CQ WW, I don't slow down. For NAQP,
> SS, FD and others that get lots of new or part timers, I don't speed up. On
> VHF tests, I send as if I was using a straight key...
> > 73 John K3TN
> >
> > ------------------------------
> >
> > Message: 11
> > Date: Tue, 12 Mar 2019 07:35:47 -0400
> > From: Dave Edmonds <dave@pkministrywebs.com>
> > To: Jim Stahl <jimk8mr@aol.com>
> > Cc: Mike Smith VE9AA <ve9aa@nbnet.nb.ca>, "cq-contest@contesting.com"
> > <cq-contest@contesting.com>
> > Subject: Re: [CQ-Contest] Serial # contests, speed?
> > Message-ID:
> > <CAHQrxhKcjm4OYZ4Oo=gLxbZqoj-WkT1+iX8GE6tpQAR7gtnGYw@mail.gmail.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > Amen K8MR!!!!!
> >
> > The comment about a sense of urgency is 100% DEAD ON! i never considered
> > this before, but Jim is right. It's also upbeat and energetic...Those are
> > always positive!
> >
> > Please do not change your CW speed during your exchange!... If you do,
> I'll
> > probably ask for a repeat. When I hear a 599 or 5NN (or the first element
> > of the exchange) at 40 wpm, my brain is primed to copy the rest of the
> > exchange at 40 wpm. Please oh please keep it constant. There's nothing
> for
> > difficult than copying variable speed transmissions...Who started this
> > weird technique anyway?
> >
> > Have you ever heard W1AW speed copy tests? They don't change the speed
> with
> > every other word. Perhaps they should create one and call it the
> contesters
> > variable speed copy test. When I took my 20 wpm test at the FCC offices
> in
> > Atlanta, New Orleans and Greenville hamfest in the lat 70's, they didn't
> > switch it up either.
> >
> > Frankly, even SS is pretty easy at the 36-40 range.
> >
> > This is a bit off the subject, but still relevant...Four more CW truths
> > that drive me to the 'funny farm'.
> >
> > 1. If you run in a contest, please don't set your CQ speed faster than
> you
> > can actually copy CW.
> >
> > 2. Don't use phonetics on CW. I asked someone for a repeat recently and
> > they spelled out the letter that I was mission... Holy moly... Just send
> > the letter a few times.
> >
> > 3. I'll add one more... I hear the good old "Please copy" on CW too.
> WHAT!
> >
> > 4. Please leave enough space between CQs for a guy with a 6-character
> > callsign to reply at a reasonable speed. This weekend, I had to reply at
> 44
> > wpm to fit my callsign in the GAP. I'm now calling this the 'CQ GAP'.
> >
> > Playing a little Prince "Let's Go Crazy", "Tom Sawyer" by Rush or some
> fast
> > Phil Collins vinyl during your breaks will also help keep your speed up
> > when you return.
> >
> > 73s Dave WN4AFP
> >
> > On Mon, Mar 11, 2019 at 11:41 PM K8MR via CQ-Contest <
> > cq-contest@contesting.com> wrote:
> >
> >> I'm of a keep it at the same speed style - I don't think the 300
> >> milliseconds one saves by sending 5NN at warp speed compensates for the
> >> other guy's brain having to shift gears to copy what I'm sending.
> >> I judge just how fast I'm sending by the nature of the pileup (assuming
> I
> >> have one!). The bigger the pileup, the safer it is to go fast, as it is
> >> quite likely the guy you're working just listened to your previous QSO
> and
> >> knows how to increment a number.
> >>
> >> Maybe not so much in serial number contests, but in a no-brain exchange
> >> contest (i.e. CQWW) sending on the fast side puts a sense of urgency for
> >> the other guy to call you now.
> >>
> >> And as a contest wears on, yes, sending somewhat slower is a good
> >> strategy. And if for some reason (hopefully other than you got spotted
> with
> >> a busted call) you do get a small pileup, go ahead and bump up the
> speed a
> >> bit.
> >>
> >>
> >> 73 - Jim K8MR
> >>
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Mike Smith VE9AA <ve9aa@nbnet.nb.ca>
> >> To: cq-contest <cq-contest@contesting.com>
> >> Sent: Mon, Mar 11, 2019 9:58 pm
> >> Subject: [CQ-Contest] Serial # contests, speed?
> >>
> >> For contests like RDX and WPX where the exchange is a serial #, do you:
> >>
> >>
> >>
> >> . Go as fast as always. (34-36wpm) , risking your qso partner
> busting
> >> the #,but keeping rate high.
> >>
> >> . Go a bit slower (30-32wpm), hoping the QRS improves the copy &
> >> reduces busted exchanges.
> >>
> >> . Send everything just as fast as normal (whatever that speed is),
> but
> >> use brackets <<>> (a la N1MM) to slow down JUST the serial #
> >>
> >> . Slow down only for obviously slow callers
> >>
> >> . Something else?
> >>
> >>
> >>
> >> Inquiring minds.
> >>
> >>
> >>
> >> I don't want to skew the results, so I won't say (yet) what I do. (and
> who
> >> knows if what I do is even 'right')
> >>
> >>
> >>
> >> Mike VE9AA
> >>
> >>
> >> _______________________________________________
> >> CQ-Contest mailing list
> >> CQ-Contest@contesting.com
> >> http://lists.contesting.com/mailman/listinfo/cq-contest
> >>
> >
> >
> > --
> > Dave Edmonds
> > PK Ministry Webs
> > 864.288.6678
> > dave@pkministrywebs.com
> > www.pkministrywebs.com
> >
> >
> > ------------------------------
> >
> > Subject: Digest Footer
> >
> > _______________________________________________
> > CQ-Contest mailing list
> > CQ-Contest@contesting.com
> > http://lists.contesting.com/mailman/listinfo/cq-contest
> >
> >
> > ------------------------------
> >
> > End of CQ-Contest Digest, Vol 195, Issue 11
> > *******************************************
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
>
--
Dave Edmonds
PK Ministry Webs
864.288.6678
dave@pkministrywebs.com
www.pkministrywebs.com
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|