You are here

NanoStation Loco M5 (XW) test date before / after Nov 2017

7 posts / 0 new
Last post
DL8MA
DL8MA's picture
NanoStation Loco M5 (XW) test date before / after Nov 2017

hello,
what is the different between

  • NanoStation Loco M5 (XW) test date before Nov 2017

and

  • NanoStation Loco M5 (XW) test date after Nov 2017

?

73 de Jürgen, DL8MA

AE6XE
AE6XE's picture
The  device has 2 different

The  device has 2 different Ethernet port chips.   There is no other known notation that helps us distinguish the difference.   Ubiquiti started shipping a new hardware revision somewhere around Nov 2017.   The device's test date by the manufacturer is on the sticker of the packaging.   If you load the wrong image, the Ethernet port is not functional, but the node can be accessed by the wireless card.   So not a problem to recover, then just load the other image  (loco-m-xw or rocket-m-xw). 

Joe AE6XE

KB9OIV
Let's say, if one were to

Let's say, if one were to load the pre-2017 firmware on a post-2017 unit as part of an 'upgrade', what condition would the wifi be in?  How would one proceed to recover from this?

Just askin' for a friend.

KB9OIV
The node will have a wifi AP

The node will have a wifi AP called 'Mesh5G' with no password. Connect to that and flash the correct post/pre 2017 firmware. :)

K2QA
NanoStation Loco M5 (XW) Version

Joe,

Have a bunch of these to upgrade to 3.20.2.0. Don't remember the version of each node.
Is there a way to tell from a support file which Ethernet chip is installed?

Thanks,

John

AE6XE
AE6XE's picture
Yes, in the "dmesg" output,

Yes, in the "dmesg" output, included in the support data file, search to find the Ethernet chip found (or not found).  As I recall, the newer one takes the AR8035 chip (commonly used in rockets, PBEs, and newer devices), and the older one has the AR8032.

Joe AE6XE

K2QA
NanoStation Loco M5 (XW) Version

I'm in the process of updating all my nodes to 3.20.3.1. I have several NanoStation Loco M5 units, and of course can't remember revision of each.
So, I used Joe's suggestion of using "dmesg" output to determine Ethernet chip version.
Just documenting the difference in output from two different units.

UNIT 1 - 8032 chip
========== cat /proc/cpuinfo ==========
system type        : Atheros AR9342 rev 2
machine            : Ubiquiti Loco M XW

========== dmesg ==========
[    1.433677] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:01 [uid=004dd023, driver=Atheros 8032 ethernet]

UNIT 2 - 8035 chip:
========== cat /proc/cpuinfo ==========
system type        : Atheros AR9342 rev 2
machine            : Ubiquiti Rocket M XW


========== dmesg ==========
[    1.443035] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:04 [uid=004dd072, driver=Atheros 8035 ethernet]

 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer