VHFcontesting
[Top] [All Lists]

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

To: Steve Raas <sraas@optonline.net>,'Nate Duehr' <nate@natetech.com>, vhfcontesting@contesting.com
Subject: Re: [VHFcontesting] 50.125 ..yes, but what about 144.200?
From: John Geiger <n5ten@yahoo.com>
Date: Wed, 6 Jun 2007 07:04:14 -0700 (PDT)
List-post: <mailto:vhfcontesting@contesting.com>
I just wish we had that much activity here.

73s John W5TD EM04to

--- Steve Raas <sraas@optonline.net> wrote:

> I wish it was that easy on the east coast.. ssb sigs
> from 144.150-250
> usually sometimes even down to 125.. 432 is almost
> the same way 432.060-180
> usually find cq'ers. I prefer it this way however..
> less qrm.
> 
> 
>  
> N2JDQ
> Steven J. Raas
> Locator FN20vg
> QRV 2/432 ,  V/U U/V Sats & WSJT
> Home Page & Sked Requests @
> http://n2jdq2007.tripod.com/
> AMSAT Member # 36396
> 
> -----Original Message-----
> From: vhfcontesting-bounces@contesting.com
> [mailto:vhfcontesting-bounces@contesting.com] On
> Behalf Of Nate Duehr
> Sent: Wednesday, June 06, 2007 4:33 AM
> To: vhfcontesting@contesting.com
> Subject: Re: [VHFcontesting] 50.125 ..yes, but what
> about 144.200?
> 
> 
> 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
> 
> 
> 
> 
> _______________________________________________
> VHFcontesting mailing list
> VHFcontesting@contesting.com
>
http://lists.contesting.com/mailman/listinfo/vhfcontesting
> 
> _______________________________________________
> VHFcontesting mailing list
> VHFcontesting@contesting.com
>
http://lists.contesting.com/mailman/listinfo/vhfcontesting
> 



       
____________________________________________________________________________________
Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for 
today's economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow  
_______________________________________________
VHFcontesting mailing list
VHFcontesting@contesting.com
http://lists.contesting.com/mailman/listinfo/vhfcontesting

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