[FADCA] Antenna recommendations for the SNCP, BARTOW, 200 foot tower

Wed, 10 Mar 2004 14:04:50 -0500

comments noted, thanks for the feed back..

Evans

----- Original Message -----=20
From: "Welcker" <[email protected]>
To: <[email protected]>
Sent: Wednesday, March 10, 2004 08:57
Subject: Re: [FADCA] Antenna recommendations for the SNCP, BARTOW, 200 =
foot tower

> You might want to think through #3 "the UHF Beams".  With this=20
> configuration you will encounter severe desence to the non =
transmitting=20
> radios plus IM products
> if two radios are transmitting simultaneously.  UNLESS you provide a=20
> minimum of 60db of quality bandpass filter per radio (very expensive). =
=20
> The alternative is to
> stagger the beams up and down the tower depending on the path loss=20
> caluclations with a minimum separation of thirty feet..  We (the Palm=20
> Beach Packet Group) have aready corrected two sites (Lake Placid & =
Vero)=20
> in the past six months that had their UHF beams collocated.
>=20
> Doug (WB4KGY)
>=20
> Evans Mitchell kd4efm / afa2th fl wrote:
>=20
> >From: Evans F. Mitchell, ARES EC, Polk County
> >To: Ben Holycross, Director of Communications, Polk County Emergency =
Management
> >CC: Polk County Communicators Program Volunteers; Lakeland ARC, Polk =
ARES Group
> >REF: Antenna recommendations for the SNCP, BARTOW, 200 foot tower.
> >
> >Dear Mr. Holycross,
> >    I would like to share with you some of the site recommendations I =
have received and
> >some that I, Evans,  have included for the 200 foot tower at the SNCP =
/ HAM EOC site.=20
> >These are the considerations, and only that, till you finalize and =
approve the recommendations.
> >
> >1) Your recommendation for the top is One Each; 800 MHz, UHF, EMWIN, =
and a VHF (EMWIN left at current location)
> >    The 800, UHF and VHF would be mounted on 4 to 6 foot stand off's. =
ARES agrees.
> >
> >2)    At the 175 foot level, two side arms with one VHF and one 220 =
MHz antenna on each, the vhf one would serve the IRLP
> >node, the 220 would serve as a communications antenna for a 220 rig =
at one of the control stations.=20
> >(Evans added the antenna idea the IRLP node, ARES added line item 2B)
> >
> >2B)    One note, a multi-banded antenna at the second stand has been =
suggested that would cover VHF LOW (6 meter), 2=20
> >meter VHF HIGH, and 220 MHz. OR and antenna that would cover all =
bands, 6 m 2m 23cm 70 cm and 1.2 GHz.
> >Research will be done to locate such an antenna for this option.
> >
> >3)    At the 150 foot spot, One VHF antenna for the Polk County area =
wide packet station on a frequency of 145.570
> >    At the level of 136 to 140 foot (10 to 15 foot below the packet =
antenna) 3 UHF beams staggered, one points to
> >Clermont, (140') One to Tampa (138') and one to the south towards =
Arcadia at the 136' spot. (4 to 10 element beam antennas)
> >recommended by members of the FADCA organization to provide seamless =
coverage between EOC's, email can be forwarded
> >at your request.
> >
> >4)    At the 125 foot mark, a WIDE BANDED HF ANTENNA, inverted "V",  =
recommendation, YES, should be able to use it
> >       for 160 meters (1,800 kHz to 2,000 kHz) Ideally being able to =
operate from 1.8 MHz to 30 MHz General Coverage Tx / Rx.
> >
> >5)    At the 100 foot mark, two pulleys with lines, recommended. =
Additions: a second HF antenna called a SLOPPER
> >be added, the Shield (ground of the antenna) should be connected to =
the tower at this spot also. The center conductor should
> >extend to the east towards the wooded area and secured from there.
> >
> >These are the notes I have collected for your review and tower =
loading studies as needed. Please advise should the loading
> >be too extreme for the tower, and need to be revised. It is also =
suggested to have the stand offs not under each other, but offset
> >under each other.
> >
> >Item number 3 is to support intra-state communications on a digital =
network using
> >high speed back bone data links, UHF, and a 1200 baud LAN (the single =
VHF antenna at 150") This system will
> >support NTS and EMCOMM traffic for the center of the state and will =
also help support the SEDAN network during
> >an actual emergency. To find out more on the packet system the site =
may be found at www.fadca.org as well as a map
> >showing Polk County as lacking digital communications between the =
East coast and the West coast, and serving as a
> >Central packet zone for the packet system would be crucial to all =
hams. I can provide you with more information if=20
> >needed at your request.
> >
> >
> >73 From,
> >KD4EFM / AFA2TH USAF MARS
> >Evans F. Mitchell
> >Polk County ARES Member / SkyWarn #POL-017
> >Polk County EC
> >Polk County Communications Program Volunteer
> >
> ><http://www.kd4efm.org>
> >kd4efm at arrl dot net
> >kd4efm at hotmail.com
> >kd4efm at kd4efm dot org
> >
> >
> >
> >
> >---
> >Outgoing mail is certified Virus Free.    =20
> >
> >ANTI-SPAM COUNTER MEASURE ENABLED.
> >PLEASE CHECK EMAIL ADDRESS YOUR REPLYING TO.
> >
> >Signed: Evans F. Mitchell kd4efm AT KD4EFM DOT ORG
> >Checked by AVG anti-virus system (http://www.grisoft.com).
> >Version: 6.0.613 / Virus Database: 392 - Release Date: 3/7/2004
> >
> >--- StripMime Report -- processed MIME parts ---
> >multipart/alternative
> >  text/plain (text body -- kept)
> >  text/html
> >The reason this message is shown is because the post was in HTML
> >or had an attachment.  Attachments are not allowed.  To learn how
> >to post in Plain-Text go to: http://www.expita.com/nomime.html  ---
> >_______________________________________________
> >FADCA mailing list
> >[email protected]
> >http://mailman.qth.net/mailman/listinfo/fadca
> >
> > =20
> >
>=20
> _______________________________________________
> FADCA mailing list
> [email protected]
> http://mailman.qth.net/mailman/listinfo/fadca
>=20

---
Outgoing mail is certified Virus Free.    =20

ANTI-SPAM COUNTER MEASURE ENABLED.
PLEASE CHECK EMAIL ADDRESS YOUR REPLYING TO.

Signed: Evans F. Mitchell kd4efm AT KD4EFM DOT ORG
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.613 / Virus Database: 392 - Release Date: 3/8/2004