Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+Spotting\s+Errors\s*$/: 24 ]

Total 24 documents matching your query.

1. [CQ-Contest] Spotting Errors (score: 1)
Author: Bob Schreibmaier <k3ph@ptd.net>
Date: Mon, 01 Dec 2008 13:59:27 -0500
After the contest, I checked to see how many times K3PS was spotted. It seems that K3PS was spotted twice -- both during MY Sunday afternoon run on 14048.7. No wonder I had 28 dupes on 20 meters! A w
/archives//html/CQ-Contest/2008-12/msg00014.html (7,146 bytes)

2. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: "K0HB" <kzerohb@gmail.com>
Date: Mon, 01 Dec 2008 12:13:49 -0800
You shouldn't get NIL'ed, but they will get hit for a busted call. 73 de Hans, K0HB _______________________________________________ CQ-Contest mailing list CQ-Contest@contesting.com http://lists.cont
/archives//html/CQ-Contest/2008-12/msg00018.html (8,697 bytes)

3. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: "Andy Faber" <andrewfaber@ymail.com>
Date: Mon, 01 Dec 2008 14:28:51 -0800
You think you had problems? I was spotted, I think, 7 times as P40Y and twice as PV9Y. I ended up logging 160 dupes, though sometimes I was so angry that I put on my QSO B4 message instead. It's very
/archives//html/CQ-Contest/2008-12/msg00023.html (10,137 bytes)

4. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: "Kenneth E. Harker" <kenharker@kenharker.com>
Date: Mon, 1 Dec 2008 13:27:10 -0800
If you log their call sign correctly, and they log K3PS instead of K3PH, they will have busted your call sign and be assessed the penalty, but you should get full credit for the QSO (or, if it is a d
/archives//html/CQ-Contest/2008-12/msg00024.html (8,216 bytes)

5. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: "Ron Notarius W3WN" <wn3vaw@verizon.net>
Date: Mon, 01 Dec 2008 18:49:04 -0500
And people wonder why I gave up WN3VAW. After 30+ years of busted calls, enough was enough < g >! To this day, I wonder how many cards are sitting at the bureau for N3VAW (who was a Tech the last tim
/archives//html/CQ-Contest/2008-12/msg00026.html (9,168 bytes)

6. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: "Robert Chudek - K0RC" <k0rc@pclink.com>
Date: Mon, 1 Dec 2008 19:59:06 -0600
Andy, When it becomes apparent you've been spotted wrong, besides laying on the QSO B4 macro is there the option of simply QSYing 20 KHz and begin running there? What are the trade-offs? 73 de Bob -
/archives//html/CQ-Contest/2008-12/msg00028.html (11,977 bytes)

7. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: Jim Reisert AD1C <jjreisert@alum.mit.edu>
Date: Mon, 01 Dec 2008 21:58:07 -0700
Good luck finding a new frequency when 95% of the contesters are on 20 meters because 10 and 15 are closed. NO ONE wants to voluntarily give up a run frequency. 73 - Jim AD1C
/archives//html/CQ-Contest/2008-12/msg00032.html (8,086 bytes)

8. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: "Paul J. Piercey" <p.piercey@nl.rogers.com>
Date: Tue, 02 Dec 2008 05:53:01 -0800
This is correct. Finding another frequency is almost impossible but there's another way to help solve the problem... Give your callsign more often and don't rely on the cluster to do it for you. Anyo
/archives//html/CQ-Contest/2008-12/msg00036.html (9,779 bytes)

9. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: "Paolo, IK3QAR" <ik3qar@gmail.com>
Date: Tue, 2 Dec 2008 15:09:17 +0100
It happened to me this week-end during my run at IR4M: we have been spotted with a wrong call and DUPES quickly started to arrive. Even if we always give the "TU IR4M" at the end of each Qso, when i'
/archives//html/CQ-Contest/2008-12/msg00045.html (11,471 bytes)

10. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: "Steve Lott" <lottsphoto@gmail.com>
Date: Tue, 2 Dec 2008 08:30:34 -0600
and as I am often reminded on snail mail QSL's rcvd after each contest some times we just need to slow down just a tad new comers often do not grasp our fast talking "qrz contest kg5vk" instead qrz c
/archives//html/CQ-Contest/2008-12/msg00046.html (11,291 bytes)

11. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: "Alfred Frugoli" <ke1fo@arrl.net>
Date: Tue, 2 Dec 2008 11:19:34 -0500
I came across several guys working "packet runs" where they would not give their call over the 3 or 4 q's it took me to get heard. I'd always ask for their call when they came back to me - "cl? tu 5n
/archives//html/CQ-Contest/2008-12/msg00049.html (11,566 bytes)

12. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: "Andy Faber" <andrewfaber@ymail.com>
Date: Tue, 02 Dec 2008 13:52:57 -0800
Robert, That strategy would be a last resort these days in CQWW due to the crowded bands. Usually the situation clears itself up in a few minutes. But one reason that it could be a good idea is that
/archives//html/CQ-Contest/2008-12/msg00050.html (13,649 bytes)

13. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: Fabian Kurz <mail@fkurz.net>
Date: Tue, 2 Dec 2008 23:16:09 +0100
Spotting errors and such things can get even worse: My callsign (DJ1YFK) is obviously about as bad as it gets for CW contesting. There are only very few DJ-callsigns with three-letter-suffixes and to
/archives//html/CQ-Contest/2008-12/msg00056.html (9,666 bytes)

14. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: "Kenneth E. Harker" <kenharker@kenharker.com>
Date: Tue, 2 Dec 2008 14:20:26 -0800
I hear this complaint (mostly from CW ops) a lot. Let me offer a different perspective. As a single op unassisted, if I dial across a station working people without giving a call sign, it is often fa
/archives//html/CQ-Contest/2008-12/msg00057.html (10,148 bytes)

15. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: "Mike McCarthy, W1NR" <lists@w1nr.net>
Date: Tue, 02 Dec 2008 17:52:36 -0500
I noticed two stations who had the sense enough to QSY after realizing they had been spotted with a busted call. That's about the only recourse a station has. This weekend seemed especially bad. I th
/archives//html/CQ-Contest/2008-12/msg00059.html (9,288 bytes)

16. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: "K0HB" <kzerohb@gmail.com>
Date: Tue, 02 Dec 2008 19:21:04 -0800
Also B and 6. 73, de Hans, K0 _______________________________________________ CQ-Contest mailing list CQ-Contest@contesting.com http://lists.contesting.com/mailman/listinfo/cq-contest
/archives//html/CQ-Contest/2008-12/msg00063.html (9,063 bytes)

17. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: "Tom Haavisto" <kamham69@gmail.com>
Date: Tue, 2 Dec 2008 18:41:28 -0500
Hi Fabian Since you know there are issues with your call, perhaps you could get a "contest" callsign? Use your other call the rest of the time... My first call was VE3HHS (try THAT in a contest!) Bad
/archives//html/CQ-Contest/2008-12/msg00064.html (9,228 bytes)

18. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: Jan Erik Holm <sm2ekm@telia.com>
Date: Wed, 03 Dec 2008 07:03:46 +0100
This is what I do too. Since I usually have a big or at least decent signal I can crack any pile-up quite fast. Instead of waiting I just call these jokers instead, it´s faster. Many times it will be
/archives//html/CQ-Contest/2008-12/msg00068.html (11,464 bytes)

19. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: Jacques Saget <f6bee@free.fr>
Date: Wed, 03 Dec 2008 07:28:25 +0100
K0HB a écrit : Agreed, no 6, no B and also no E 73 Jacques, F (formerly F6BEE !) _______________________________________________ CQ-Contest mailing list CQ-Contest@contesting.com http://lists.contest
/archives//html/CQ-Contest/2008-12/msg00069.html (9,045 bytes)

20. Re: [CQ-Contest] Spotting Errors (score: 1)
Author: "Albert Crespo" <f5vhj@orange.fr>
Date: Wed, 03 Dec 2008 06:38:38 -0800
People with long calls increase the rate of error that the other station will bust their call. If I find in my log something like KZ0ZZZ , it is more likely to be a product of fatigue at my end then
/archives//html/CQ-Contest/2008-12/msg00071.html (10,756 bytes)

Current List: 1 - 20
Page: [1] [2]
This search system is powered by Namazu