Towertalk
[Top] [All Lists]

[Towertalk] 100M-long boom Yagi for 20M -- correction

To: <towertalk@contesting.com>
Subject: [Towertalk] 100M-long boom Yagi for 20M -- correction
From: W4EF@dellroy.com (Michael Tope)
Date: Mon, 13 Jan 2003 08:34:48 -0800
Yes, agreed, but the stack has a wider elevation coverage in the
sense that you can quickly change configuration (U/L/BIP/BOP).
With the single long boom yagi, you can only adjust azimuth, the
elevation pattern is pretty much fixed.

73 de Mike, W4EF..............................

----- Original Message -----
From: "W0UN--John Brosnahan" <shr@ricc.net>
To: <Towertalk@contesting.com>
Sent: Monday, January 13, 2003 7:31 AM
Subject: Re: [Towertalk] 100M-long boom Yagi for 20M -- correction


>
>
> >
> >Yes, and 21+ dB (including ground reflection) is hard to come by any
other
> >way.  I was thinking more in terms of a contester making the choice
> >between, say, 16 dBi from a long-boom yagi versus  the same gain from a
> >stack.  The stack would not only have a wider azimuth beamwidth but also
a
> >wider elevation beamwidth.  Whether this extra width is "useful" is much
> >harder to test, or to prove...
>
> Pete, I don't think you can have it both ways.  If they are the same gain
> and one has a wider
> azimuth beam width it must have a narrower elevation beam width.  That
gain
> (power) has
> to come from somewhere and if it gets spread over a wider azimuth the only
> place it
> can come from is from the elevation beam width.  All assuming that side
> lobe performance
> is good enough to make any energy in the side lobes to be relatively
> insignificant.
>
> --John  W0UN
>
> _______________________________________________
> AN Wireless Self Supporting Towers at discounted prices,
> See http://www.mscomputer.com
>
> Wireless Weather Stations now $349.95. Call Toll Free,
> 888-333-9041 for additional information.
> _______________________________________________
> Towertalk mailing list
> Towertalk@contesting.com
> http://lists.contesting.com/mailman/listinfo/towertalk
>




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