[MVMA] If 'all' the equipment at W-Xenia is to be replaced,
tim-yvonne at juno.com
tim-yvonne at juno.com
Wed Sep 19 11:01:04 EDT 2018
yes, the 2.4 SISO is a boat anchor; there's an installed base that we need to still cater to... unless someone was to offer the funds and climbing services to swap everything out. I'm all for ADDING additional nodes at existing installations to help into the migration of MIMO though. Problem at the W. 2nd st Xenia tank is that the missing "safety ring" was not added along with the repaint. There's no room to add additional nodes to the existing installation; we're lucky to have anything up there at the moment. Bill and I are in agreement that any new community that was to contact the MVMA and say they wanted help getting started in mesh... we'd suggest MIMO right off the bat. Keep in mind that the AREDN group still suggests 2.4 MIMO omni @ 10mhz on -2 for neighborhood flooding applications; I heard this straight from Andre.There is at least one MIMO omni on 2.4 that attempts to cover a small area. End users mostly go with NanoStations to connect to this "beacon". But like Chuck mentioned... these 2.4's beacons are not intended to link with other neighborhoods (the 2.4 nodes in one community are not to see the 2.4 nodes to a different community). In other words, 2.4 in any config (SISO or MIMO) should not to be used to link communities together... either intentionally or accidentally. It's too much traffic for one channel... especially with 10mhz bandwidth. 3ghz with its abundant channels, would allow a small community to put up multiple "flooding omnis" for maximum bug-zapper coverage... with no fear that a nearby community would connect directly; accomplished with channel selection coordination.I foresee the future with 3ghz as being the neighborhood flooding choice, with 5.8 directional as the link between communities... and 900mhz used to get coverage to single users that have terrain/tree issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/mvma/attachments/20180919/9d7e5b53/attachment.html>
More information about the MVMA
mailing list