[MVMA] If 'all' the equipment at W-Xenia is to be replaced,

[Chuck Gelm]

"The in-use 5.8 at MVHS is an AGM5 and that's what should be on the 
Xenia West tank"

Please, no dishes on water tanks. They are difficult to aim.


On 09/19/2018 09:54 AM, Maurice Riggins via MVMA wrote:
> *It will kill JJ and my only RF link to the mesh*, but

  OTOH, the gain of a AMO-5G13 is -2 dB compared to a NS-M5.

  East and West Beavercreek (N8NQH-N8DCP and WA8APB)
used to link with a NS-M5 at W-Xenia.

  If W-Xenia was a 5G omni, then East and West Beavercreek
could still link with W-Xenia
  plus one of N8NQH's array of NS-M5s
  plus W8XRN's NS-M5
thus retaining N8JJ and AB8XA's link to the mesh.

  Tim's array already has a separate 65 Mbps link to MVHS.

/ At W-Xenia the Bullet-M2-filter-LCom would be replaced with a//
//Rocket-M5_AMO-5G13.//
//
// The NS-M5 could be retained/replaced and pointed at the poorest//
//link of N8NQH-N8DCP, WA8APB, W8XRN, N8NQH-array.//
e.g. *Optimized for the N8NQH-N8DCP link serving AB8XA an**d N8JJ.*
/
With new equipment of one Rocket-M5 and AMO-5G13, I anticipate:

  * No loss of service to anyone.
  * Less LAN-to-LAN linking on 2397 MHz.
  * Establishes a 5G LAN that would not be competing with
    Huber Heights or Vandalia LAN activity for channel utilization.
    Providing that not all meshers from Wilmington to Tipp City
    add a node on the same channel. There are 14x 20 MHz
    bandwidth channels on 5 GHz. I think it is unlikely that an
    unacceptable number of additional meshers will join
    whatever channel we choose.

Chuck

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/mvma/attachments/20180920/e9d1c874/attachment.html>