CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] Why?

To: <cq-contest@contesting.com>
Subject: Re: [CQ-Contest] Why?
From: "Larry" <lknain@nc.rr.com>
Reply-to: Larry <w6nws@arrl.net>
Date: Wed, 27 Nov 2013 10:39:08 -0500
List-post: <cq-contest@contesting.com">mailto:cq-contest@contesting.com>
It is usually obvious when that mode of operation is being done. Usually a DX operation rather than contest in my experience. I have not seen it on CW that I recall but fairly often on SSB. Latecomers to the party may still call over the next in the list until they catch on to the short list aspect.

There are some great operators out there that can capture several calls at a time and keep the pile under control. I can capture several calls many times. But the danger is that going from call to call often triggers the calling frenzy that can easily get out of hand for most of us.

73, Larry  W6NWS

-----Original Message----- From: Zack Widup
Sent: Wednesday, November 27, 2013 9:41 AM
To: CQ Contest
Subject: Re: [CQ-Contest] Why?

There may be another scenario in the exchange outlined below. The
running station may write several callsigns down after he says "QRZ?".
Then, after working one, he may call the next on his little list. I've
known people who were very good at this!

73, Zack W9SZ


On 11/26/13, Larry <lknain@nc.rr.com> wrote:
I suspect people do it because it can work.

I have heard DX stations lecture the pile about not calling while working
someone. So then a QSO ends "LU5DX TU W7AAA 599.." which means the DX
station was copying other calls. Thus, one could conclude that I should call

during the QSO so the DX station will hear my call and call me next. But the

other stations listening often figure out the scheme and call too. Chaos. Of

course, if it was "LU5DX TU YU5DX 599..." I can understand in that you both

have very similar calls. It is not usually that close.

I don't think I have heard as belligerent case as your DL8 over the DK5.
Many stations will easily cave and work the DL8 and the poor DK5 may not get

worked after all. Once working the DL8 after having called the DK5 then it
can degenerate into a calling mess. (After all, how can you not hear me? I
am 599 and clear in my headphones!)  It can be hard sticking to what you
call because it can kill your rate but there are ops that do it (I forget
who but there were at least a couple heard this past weekend - a 5H and 5R I

think). Trying to regroup if I heard DK5 and it wasn't actually DK5 can be
interesting because that can open up the calling again.

73, Larry  W6NWS

-----Original Message-----
From: Martin , LU5DX
Sent: Tuesday, November 26, 2013 11:53 AM
To: Ron Notarius W3WN
Cc: CQ-Contest
Subject: Re: [CQ-Contest] Why?

Super weird things happened. Compulsive calling is spreading like a
decease!
But not only that. There is now bullying calling.

In the middle of an unruly pile up some DK5 called in. I copied his full
call at once and came back to him with ENNA2.
There was this other DL8 also calling and he simply continued to call after
I came back to the DK5.
He was so strong I was not able to copy the exchange being sent by the DK5.
No ony that. The DL8 said I'm not DK5... I'm DL8.....
So no way out but to stop the pile and asked the DL8 why he was that LID!!
And he insisted I'm not DK5... And I said. I know you are not, I'm working
someone else and I'm not working you for sure, so please QSY.
Really bad operating manners were mostly shown by countries from certain
countries, but now, it's pandemic!
Just as in 2012. I had to wait long on big egos to ID (some of them
repeating their techniques from last year).

Anyways lots of fun as usual.

I wonder if the WWROF will take a more proactive approach on all these
topics.

Best 73.

Martin, LU5DX
Op at CE3CT this past WWCW.


On Mon, Nov 25, 2013 at 1:51 PM, Ron Notarius W3WN
<wn3vaw@verizon.net>wrote:

And of course, we all remember a well know US amateur working in Kuwait,
who was known to answer partial calls (and other liddish behavior) with
"you're in the log" instead of a signal report.

So, someone who called (and called and called ) "FOUR LIMA) and sent a
card to that station's manager as "W4LID" would be told... he's not in
the
log.  The log showed '4L' but not 'W4LID'

(apologies to the real W4LID, if any, I simply used that call as an
example)

73

On 11/25/13, Milt -- N5IA wrote:

Been there; done that. During the CQ 160 SSB 'test I operated as VP6DX
from
Ducie Atoll in February of 2008 there were two prominent "Big Guns" who
never made it in the log because of their inability to follow
instructions
and kept calling, calling, calling while I was trying to get another call
sign correct. This went on for HOURS.

Sad, but true.

Mis dos centavos,

de Milt, N5IA


-----Original Message-----
From: Joe
Sent: Monday, November 25, 2013 7:53 AM
To: cq-contest@contesting.com
Subject: Re: [CQ-Contest] Why?

.... CUT ....

If i ever had the chance to be at the other end, I'd make a
list of lid's like this, and make sure they never get worked.

But Just my own opinion.

Joe WB9SBD



-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4158 / Virus Database: 3629/6831 - Release Date: 11/12/13

_______________________________________________
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

_______________________________________________
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

<Prev in Thread] Current Thread [Next in Thread>