Especially when they are sending at 50wpm with over the pole flutter.
I've fond the best thing to do if they are running is just keep asking
for repeats until they slow down or send numbers.
After everyone just keeps sending 'agn??' they might get the idea cut
number don't work 73
Tom W7WHY
On 12/14/2014 10:34 AM, Bill Hider wrote:
Pete,
I couldn't agree with you more!
I shake my head every time I hear a cut number, before I go into 'translation
mode' to figure out what the heck the actual number was that was sent.
Bill N3RR
On Dec 14, 2014 9:50 AM, Pete Smith N4ZR <n4zr@contesting.com> wrote:
Please, please don'tuse cut numbers when transmitting a serial number.
I've even heard some Es and As today - that's just absurd, and
counterproductive..
There is good information science behind this plea. When you really
need to get a number right, particularly with weak signals, even the
most common cut numbers, like N and T, are more trouble than they are
worth in time saving. Why? Because each full number has five elements,
grouped together - that is consecutive dots or dashes. Your brain can
use this fact to copy confidently, even if QRM or QSB causes you not to
hear a dit or dah, because of spacing *between* numbers. If you send a
cut number, you deprive the receiving op of this aid - he asks for a
fill, and you've lost more time than the cut number would save you in 5
QSOs.
--
73, Pete N4ZR
Check out the Reverse Beacon Network at
http://reversebeacon.net,
blog at reversebeacon.blogspot.com.
For spots, please go to your favorite
ARC V6 or VE7CC DX cluster node.
_______________________________________________
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
|