[VHFcontesting] 50.125 ..yes, but what about 144.200?

[Nate Duehr]

On Jun 3, 2007, at 8:51 PM, Tim Coad wrote:

>
> There might be a problem with 50.125... but the one that bugs me is  
> the problem where people are glued to 144.200 during the contest.
>
> Here in the SF bay area you can call CQ for 1/2 hour on 144.190 or  
> 144.210 and not have a SINGLE answer...then move to 144.200 and get  
> a pile up during the contest.

Lead by example.  Call, get a response and instead of FINISHING the  
QSO on .200, ask 'em to listen "up 10".

One guy around here operates split and during openings and contests  
on .200 he just announces, "X0XXX listening up 10" and he refuses to  
reply to anyone that answers on .200.

Works for him.  People QSY up to work him.  Usually everyone  
around... then it gets quiet again for a while and he announces again  
after a couple of minutes... spacing them out a minute or more.

I'm a little too lazy to do that much work with the rig, especially  
roving, since I'd want to monitor both continuously with the sub-band  
receiver if I were going to do something like that.  But asking  
someone to move off .200 to finish the QSO is one way to give a  
subtle hint.

Plus roving, around here people are "parked" as someone mentioned on . 
200 as a "listening frequency"... but an announcement and maybe one  
QSO where you state you're there, work someone and then saying  
"Thanks for the contact, good luck.  WY0X/R is now in DM88... and  
QSY'ing up to .220" works fine... people go, if they want the contact.

It also depends a bit on my read of the remote operator -- if there's  
some guy that popped up or stays on .200 and he's able to work me  
faster than any of the Air Traffic Controllers I've ever talked to in  
an aircraft -- I'm not going to use tricks to try to get him to  
move.  We're already done with the QSO long before it'd ever a)  
bother anyone, or b) he'd get the hint.

:-)

Work 'em where you find 'em!!!

--
Nate Duehr, WY0X