[NLRS] N0LAN 2m beacon

Arliss w7xu at w7xu.com
Fri Sep 20 01:12:54 EDT 2013


Hi Steve,

Thanks for taking a listen.  I chose 297 because I wanted to be at the 
high end of the band (to maximize the distance from 144.200), and I 
wanted to avoid the beacons that are well heard out here, like N0LL.  I 
don't recall ever hearing the WD9BGA beacon, or at most only very 
rarely.  The 2m beacons that I've heard most frequently over the years 
have been in MN, KS, ND and Manitoba.  I also thought that it would be 
on a different heading (vs Wisconsin) for stations to the east of me, 
and that would provide some separation.

Also, the listings I have seen show BGA to be on 298, so I assumed one 
KHz spacing from a beacon I never hear would be enough.  Obviously, it 
isn't enough spacing for you folks further east.

I see there is another beacon listed in Wisconsin on 290.  Is that 
accurate?  Do you have a suggestion for a good frequency?  292?  I'm not 
crystal controlled, so it's not hard to move frequency.  I'm open to 
suggestions to make the beacon more useful.

73,  Arliss  W7XU

On 2013-09-19 21:41, Steve N4PZ wrote:
>
>
> Arliss
> I can tell the bcn on 144.297 is in there but being almost zero beat
> with the WD9BGA BCN in EN53 it is very difficult if not impossible to
> copy in EN52.
> Why on earth did you put it on the same frequency? A shift of 3-4 khz is
> in order.
> 73
> Steve N4PZ


More information about the NLRS mailing list