[OKDXA] DX COPS AMD MALICIOUS QRM

[K5TT]

Not that I have had that many opportunities, but when I was in the DX op 
position, I noted those guys calls and did not work then until later if at 
all.  Another justified response is to work them to get rid of them but 
don't log them.  I have even responded to people and asked them to leave 
because I was not going to work them.  That helps to clean up the pileup.

Jim
----- Original Message ----- 
From: "Ken Case" <caseke at cox.net>
To: "Discussion of OKDXA" <okdxa at mailman.qth.net>
Sent: Sunday, December 03, 2006 6:18 PM
Subject: Re: [OKDXA] DX COPS AMD MALICIOUS QRM


> Froggy and all,
>
> I suspect we all agree about the malicious interference.
>
> The OTHER one that has begun over the years and is now up to an art form 
> is EVERYBODY calling even when the DX station has identified someone and 
> is in QSO.  That happens simplex (often understandably due to QRM), but 
> also split.  I just cannot believe it when some DX station comes back 
> K5XYZ 599 (for example) and then everybody up and down the band is calling 
> at the same time K5XYZ is trying to complete the QSO.  Even when the DX 
> station asks for ONLY K5XYZ there are still many who are calling. 
> UNFORTUNATELY, that is too often the fault of the DX station who, in the 
> interest of trying to appear like an ultra-efficient multi-tasker, starts 
> answering these guys instantly after the preceding QSO.  That sends the 
> CLEAR message to everyone that the way to get through to the DX is to 
> continue calling at all times.  Then, the pileup gets out of control.  It 
> didn't use to be like that!
>
> 73 Ken K5KC
> ----- Original Message ----- 
> From: <K8fu at aol.com>
> To: <okdxa at mailman.qth.net>
> Sent: Sunday, December 03, 2006 10:13 AM
> Subject: [OKDXA] DX COPS AMD MALICIOUS QRM
>
>
>> It took me a bit to find the VU7 this am. So when I  determined that I 
>> could
>> hear him well enough to work, I turned on the amp. It  was working fine 
>> last
>> night and I gave Ed a Q in the contest. Turned it on this  am immediately
>> experienced a healthy dose of RF PMS.
>>
>> Luckily I was able to find the prob and repair it  myself. By that time 
>> his
>> sig was starting to drop. Then N1LID started calling CQ  on his freq.
>>
>> When I started getting interested in DX and  contesting, through my 
>> friend
>> and neighbor Don K8MFO, I can't remember anything  at all that compares 
>> to what
>> is occurring today. I don't understand  it.
>>
>> Hams have had a history of policing their own and with  the epidemic of
>> malicious interference escalating I am left wondering why there  isn't 
>> some vehicle
>> of enforcement initiated.
>>
>> I realize the FCC probably doesn't hv the money to put  tracking and
>> enforcement teams in the field, but why couldn't the ARRL organize 
>> voluntary regional
>> teams to track and identify these deliberate and malicious  stations.
>>
>> It's really getting to the point for me that chasing  DX is no longer 
>> fun.
>> It's hard enough to work places like Lakshadweep at the  bottom of the 
>> sunspot
>> cycle but to hv to endure operators calling on the dx  calling freq and 
>> the
>> malicious interference is leaving me frustrated and  angry.
>>
>> It seems this phenomenon is not only confined to the  US. I saw yest 
>> where
>> euros were screaming for something to be done abt IT9RYH (I  think) on 
>> 14.190.
>>
>> I sure would like to see someone like Sumner or  Harrison take the bull 
>> by
>> the horns and aggressively address this  problem.
>>
>> The Ranting's and Musings of a Frustrated  Frog.............
>>
>> Ribbit..........................Ribbit..........................   BOHICA
>> _______________________________________________
>> OKDXA mailing list
>> OKDXA at mailman.qth.net
>> http://mailman.qth.net/mailman/listinfo/okdxa
>
> _______________________________________________
> OKDXA mailing list
> OKDXA at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/okdxa