Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+Cut\s+\#\'s\s+in\s+RDX\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+Cut\s+\#\'s\s+in\s+RDX\s*$/: 7 ]

Total 7 documents matching your query.

1. [CQ-Contest] Cut #'s in RDX (score: 1): Author: "Mike Smith VE9AA" <ve9aa@nbnet.nb.ca>; Date: Sun, 22 Mar 2020 14:09:34 -0300; OK, so I can copy CW just as good as the next guy, but when signals are uber weak or there is QRM/QRN/QSB, I just abhor cut #'s.sometimes parts of #'s can be missing, but I can still figure it out. (; /archives//html/CQ-Contest/2020-03/msg00188.html (7,635 bytes)
2. Re: [CQ-Contest] Cut #'s in RDX (score: 1): Author: "Yuri" <ve3dz@rigexpert.net>; Date: Sun, 22 Mar 2020 14:25:00 -0400; I have simpler question to Russian DXC committee: I call CQ TEST on 14010 and IK3ITX calls me. Very loud. We exchanged the numbers, everything seemed to be O.K. Confirmation from both sides. No QRM.; /archives//html/CQ-Contest/2020-03/msg00189.html (9,235 bytes)
3. Re: [CQ-Contest] Cut #'s in RDX (score: 1): Author: K9MA <k9ma@sdellington.us>; Date: Sun, 22 Mar 2020 13:29:56 -0500; I agree: Cut numbers in serial numbers should be banned! I had the same problem in the Russian DX contest this weekend, especially on 80 and 160. 73, Scott K9MA On 3/22/2020 12:09, Mike Smith VE9AA w; /archives//html/CQ-Contest/2020-03/msg00190.html (9,607 bytes)
4. Re: [CQ-Contest] Cut #'s in RDX (score: 1): Author: Jim Brown <k9yc@audiosystemsgroup.com>; Date: Sun, 22 Mar 2020 13:23:56 -0700; Me too. Under poor conditions, the rhythm of the full number is often the difference between me asking for a fill or not. I won't accept a cut number as part of a serial number. 73, Jim K9YC ________; /archives//html/CQ-Contest/2020-03/msg00194.html (7,621 bytes)
5. Re: [CQ-Contest] Cut #'s in RDX (score: 1): Author: K8MR via CQ-Contest <cq-contest@contesting.com>; Date: Mon, 23 Mar 2020 00:08:23 +0000 (UTC); I'm no fan of cut serial numbers either, though applied judiciously they can be useful. Like if you can figure the guy is having trouble between a 9 and a 0, sending a T is useful. (Don't use A or N; /archives//html/CQ-Contest/2020-03/msg00196.html (8,050 bytes)
6. Re: [CQ-Contest] Cut #'s in RDX (score: 1): Author: Tom Haavisto <kamham69@gmail.com>; Date: Sun, 22 Mar 2020 21:40:12 -0400; I confess - I did use cut #'s in RDX... In a nutshell - I was sending full numbers for my exchange, Conditions were marginal, and I was asked for a repeat. So - send full #, then cut # to help the ot; /archives//html/CQ-Contest/2020-03/msg00197.html (9,397 bytes)
7. Re: [CQ-Contest] Cut #'s in RDX (score: 1): Author: Jim Brown <k9yc@audiosystemsgroup.com>; Date: Sun, 22 Mar 2020 19:42:15 -0700; EN is tough enough -- if I had to send it, I'd use E~N I once sat with top QRP contester W6JTI as he played with half-spaces in his call for his expedition to CM79. I send my grid as CM~87. I do the; /archives//html/CQ-Contest/2020-03/msg00199.html (8,485 bytes)

Current List: 1 - 7
Page: [1]