You are here

Nanostation Loco M2 - XW version

10 posts / 0 new
Last post
K5YX
K5YX's picture
Nanostation Loco M2 - XW version

Got hold of a new Nanstation Loco M2 but it has the XW hardware and firmware v5.6.12 (XW).

It will not allow upload of a down version of firmware.  Is there an estimated time frame for testing and development of AREDN firmware for these newer versions of the Loco that appear to be the ones shipping now?

Thanks and 73
Mike, K5YX

KG6JEI
You would be the first user

You would be the first user to bring up having seen an XW Series 2.4 GHz device.

You will need to raise this as a feature request for new hardware in bloodhound ( http://bloodhound.aredn.org ) to request the AREDN team support the device.

Untill a basic evaluation is done in a ticket there is no way to guess how long this would take.
 

VE3SKH
I have the same issue, but I

I have the same issue, but I have the Nanostation M2 (not loco)  It also had the XW 5.6.12 firmware and couldn't downgrade.  I ended up upgrading to 5.6.15 to see if then I could download, but no luck.

AJ6GZ
Success (?)

Unknowingly got an XW here too, same error, unable to downgrade. I was able to go directly from XW 5.6.12 to a nightly build, develop-169-d18d14f3. Trying the M5 XW release version resulted in ethernet ports not working no dhcp (may have been issue below). Your results may vary...or brick! Better to watch the ticket link above.

However so far it's been stable tho I don't have anyone connected to it yet on RF side. Has the same XW behavior where primary ethernet port is only untagged and the secondary carries vlan 1,2. Also the map seems to not want to update tho I can see it connect out the WAN and my firewall towards the internet.

AE6XE
AE6XE's picture
Yes, please use the nightly

Yes, please use the nightly build.  A downgrade of AirOS is not required and the nightly build images include a definition for the M2 XW and M2 Loco XW.

A superset of notes... the nightlybuilds will not work with the Bullet unless AirOS is downgraded to v5.5.x -- still a fix in the pipeline.  All the other models supported in 3.16.1.1 + the ones shown included in a release candidate on the supported hardware page, no longer require the AirOS downgrade or usage of the uboot compatibility program.   There is a fix in the nightly build (and 3.17.1.0RC1) such that a failed attempt to load these AREDN images will no longer brick the device -- can always tftp back to AirOS.

Joe AE6XE

nc8q
nc8q's picture
build images include a definition for the M2 XW and M2 Loco XW.

Woohoo! My LocoM2 5.6.12 (XW) arrived today and there is a chance I can load AREDN v3.something into it. :-) Box sticker says "Inspection date 6/20/2017".

Is it correct that since I am loading AREDN v3.nightly-build onto AirOS 5.6.12 XW, I need: https://downloads.aredn.org/snapshots/trunk/ar71xx/generic/AREDN-develop...

If loading from AREDN firmware, I would use AREDN-develop-169-d18d14f3-ubnt-loco-m-xw-squashfs-sysupgrade.bin ?

Many thanks to the AREDN Team.

Chuck nc8q

Image Attachments: 
AE6XE
AE6XE's picture
Chuck,  Correct and Correct

Chuck,  Correct and Correct on the images to load.   Some AirOS newer versions now require a signature on the firmware to upload in the UI.  I don't think the AirOS version you have requires that.   But for sure only AirOS firmware with the right signatures can only be uploaded starting around AirOS 6.0.x.     But, if the UI does not accept the factory image, with a sort of Security warning, the fallback is to upload via tftp method.   

Joe AE6XE

nc8q
nc8q's picture
LocoM2 XW 5.6.12 (out-of-box) -> AREDN development (2017-10-31)

AREDN-develop-169-d18d14f3-ubnt-loco-m-xw-squashfs-factory.bin 2017-10-31 12:13 5.3M
(AirOS identifies this firmware as 'XW v6.0.6')
loaded into
NanoLocoM2 factory AirOS firmware 'XW 5.6.12' (Ubiquiti Test date 06/20/2017)

Success! but,

"!!! THIS DEVICE IS STILL BEING TESTED !!!" banner with bright yellow background on all pages.
Is this normal?

Also, I "Upload data to AREDN Servers", yet it does not, yet, appear in the map.
Is this normal that 'develop' releases are not on the map?
Or do I need to 'give it more time'?

Many thanks to you, Joe, and the rest of the AREDN team.

Chuck

K5DLQ
K5DLQ's picture
The "warning" is normal since

The "warning" is normal since this is a new device and is still in our nightly builds.
The upload to map issue has been corrected and you should now see your nc8q-nst-m2 node on the map.

nc8q
nc8q's picture
The upload to map issue has been corrected...

Marvelous. Thanks Darryl.

Chuck

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer