CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] Big Gun hogging two frequencies (K3KU complaint)

To: Martin Durham <w1md@cfl.rr.com>
Subject: Re: [CQ-Contest] Big Gun hogging two frequencies (K3KU complaint)
From: W0MU Mike Fatchett <w0mu@w0mu.com>
Date: Mon, 14 Jan 2013 21:45:10 -0700
List-post: <cq-contest@contesting.com">mailto:cq-contest@contesting.com>
So with this logic I could be using 6 freqs, maybe 1000? What he is doing elsewhere has nothing to do with the frequency in question.

The Sprint folks were way ahead of their time. Everyone moves all the time. No frequency hogs.

Welcome to the entitlement generation, because I WAS using it means I can go back expect to use it even if I am really using another frequency.

Mike W0MU

 On 1/14/2013 6:07 PM, Martin Durham wrote:
So...if you are not transmitting on a frequency then it's NOT in
use...right? No time for 'listening' right? How do you KNOW that SO2R
operator is off transmitting on a second radio rather than taking a 'listen'
on his frequency in use?


W1MD



-----Original Message-----
From: CQ-Contest [mailto:cq-contest-bounces@contesting.com] On Behalf Of
W0MU Mike Fatchett
Sent: Monday, January 14, 2013 5:05 PM
To: cq-contest@contesting.com
Subject: Re: [CQ-Contest] Big Gun hogging two frequencies (K3KU complaint)

Either the Frequency is being used or it isn't.  If you are off making a 2nd
radio contact aren't you effectively giving up the other freq?  If you say
no than you are operating on two freqs at the same time....Right?????  DQ
time right??

This is a slippery slope.

There is no hold period where you get to use the bathroom or scan for mults.
If you are not actively using the freq and someone comes along and does you
need to move.  End of story.  You have no dibs, rights or otherwise.

Mike W0MU

On 1/14/2013 1:47 PM, Alan Dewey wrote:

I
lways ask twice if a frequency is open, and it does not take more than
en seconds to do that.


I think this is the key.  I am suprised the number of guys who hear a
clear frequency and just jump in and call CQ without asking if the frequency
is QRL?  It could be the guy is on the second radio but it could also be
that he is trying to pull out the exchange from a QRP station that you do
not hear.
On the other hand, if a guy is tied up on the second radio and a guy QRLs
his CQ freq., he better respond quickly or he just lost his CQ frequency as
he should.
73,

Al, K0AD


-----Original Message-----
From: David Gilbert <xdavid@cis-broadband.com>
To: cq-contest <cq-contest@contesting.com>
Sent: Mon, Jan 14, 2013 1:58 pm
Subject: Re: [CQ-Contest] Big Gun hogging two frequencies (K3KU
complaint)



   have to disagree there.  Ten seconds in a major contest is plenty
long nough to check for an available frequency.  I can pretty much
guarantee hat if I wait longer than that somebody will grab it before
I do.  I lways ask twice if a frequency is open, and it does not take
more than en seconds to do that.  Try it yourself while watching the
clock.
However, if I start calling CQ and somebody jumps back in that clearly
ad the frequency before me, I move.
73,
ave   AB7E

On 1/14/2013 11:51 AM, steve.root@culligan4water.com wrote:

n the other hand, 10 seconds is no where near long enough to determine
if a requency is in use. I might not be on the second radio, I might
be copying a uy that you can't hear that's sending an exchange to me
at 15 WPM. His exchange ould easily take more than 10 seconds.
73 Steve K0SR

_______________________________________________
Q-Contest mailing list
Q-Contest@contesting.com
ttp://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>