Rich, I had this happen to me before on 20..the recorded CQ thing. I
actually worked stations, and thanked the offender for giving me a break, and
letting him do the work for me, while I logged the points. He stopped right
then.
Best thing to do, if you have a 2nd rig, is keep on keeping on. Use the 2nd
rig at that time to S&P, he will bet very bored.
73- Chuck KI9A
In a message dated 11/20/2008 9:32:37 P.M. Central Standard Time,
rmthorne@suddenlink.net writes:
I'm curious how the malicious interference was this year. I operated at
K5NA this year. I had a major problem around 14.281 this year. I was
sucked into a conversation with a station who would not use his call
sign. He told me that I was splattering so I adjusted my mic gain and
compression. The ham thanked me and said it was fixed. After a few q's
he said I was splattering again, I figured out he was playing games.
Soon after he was transmitting recordings of my cq's. I was able to
work through it for a while but my rate suffered so I ended up moving.
In this particular case it was at the beginning of the contest. I had
made a few qso's about starting 15 minutes prior to the contest so I had
established that the frequency was not previously used and there were no
frequency conflicts.
So how did it go for every one else this year? I guess in the future I
need to add 14.280 to the list of frequencies to avoid. The sstv
window has been on my list for quite some time.
Rich - N5ZC
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
**************One site has it all. Your email accounts, your social networks,
and the things you love. Try the new AOL.com
today!(http://pr.atwola.com/promoclk/100000075x1212962939x1200825291/aol?redir=http://www.aol.com/?optin=new-dp
%26icid=aolcom40vanity%26ncid=emlcntaolcom00000001)
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|