Hardware

The node I flashed today is an XM version of the Rocket M5-GPS.  It went well except the displayed range of transmit frequencies is wrong (too low). It reports my other 5 GHz node as being on channel 180 - which is correct,

When selected an operating frequency about 5 channels down from the top of the available list, the other reported that the M5-GPS was operating on channel 3460 (if I remember).  So I powered it down.

UBNT loads the same firmware into the GPS and non-GPS versions.  I guess that is not true of AREDN?

As an interim measure, where we want two directional antennas, pointing in different directions on 2.4 (on the same channel) that we could connect one "chain" of the radio (M2) to one of the inputs on a MIMO antenna and the other chain of the radio to a single-polarity antenna pointing in the other direction.

The idea is that, later, the node would be converted to two-frequency operation using MIMO in both directions.

I am referencing a past post:
Manual MCS control? | Amateur Radio Emergency Data Network (arednmesh.org)

   Does anyone know if the suggestion to add a addition as follows will still work?  I have been spending considerable time trying to understand why some of our nodes(ALL RF)  are having some throughput issues.  RF nodes shooting through some trees  are subjected to varying signals and it would be interesting to see if limiting the speed to create a more reliable, but slower connection. 

Cross posted to the FB group - 

NanoStation M2 XM - Using TFTP method, after downgrade to AirOS 5.5.x, can load up AREDN up to 3.19.3.0 (started with 3.15.1.0 factory), however, moving to the current 3.21.4.0 or the nightly builds hoses the radio.

Will flash LED #4 (green) the typical 30 or so seconds, but then does dark. Only power LED lights up.

Recover back to 3.19.3.0 and it behaves correctly with the Ethernet light and LED #4 solid upon boot.

Will also crash on the Apply button in the Setup web GUI - cgi-bin error.