Nanostation loco M5 (XW) - can not config nor recover

21 posts / 0 new

Tue, 05/15/2018 - 22:40

N2JWC

Good day fellow hams. So as many the latest hardware is the newer XW, I used the code specific for the XW. Firmware seemed to take just fine, now the LEDs on the back show power (green), ethernet activity (flashing green) and the FAR right LED is green. Best I can tell this means all is normal, however when I change my NIC to DHCP I never receive an IP address from the NSM5 loco.

Of course I have power cycled it and still nothing. Finally decided to recover, no go. I have followed the steps on the documentations, I have followed forum posts and Video posts from the form. I do have the alternating LED pattern, however I am not able to ping 192.168.1.20 as indicated in all references.

Any ideas?

Thanks,
John
N2JWC

Wed, 05/16/2018 - 01:32

K5DLQ

Let's start with some basic

Let's start with some basic questions:

Which version of AirOS did the device have on it to begin with?
Which version of AREDN did you load on it?

Wed, 05/16/2018 - 12:43

N2JWC

sounds good

Firmware 5.5.10 XW was the firmware I downgraded too.

I installed AREDN firmware 3.16.11 (AREDN-3.16.1.1-ubnt-nano-m-xw-squashfs-factory.bin).

And thank you for any help you can provide.

John
N2JWC

Wed, 05/16/2018 - 13:04

k1ky

Check fro proper version for "LOCO" XW model

You need to load the appropriate XW AREDN Firmware for the LOCO model. I believe it is different from the basic NANO XW model.

Wed, 05/16/2018 - 13:43

N2JWC

That's what this firmware name says..

Or am I reading this wrong?

AREDN-3.16.1.1-ubnt-nano-m-xw-squashfs-factory.bin

The only other thing I saw was 3.17 RC1 specifically point out the Nano M5 XW in testing, however I did not use that. At this point I will try any firmware, however first I need to be able to get into the NSlocoM5. :(

The last nightly build, in early March has this more specific to the model types:

AREDN-develop-176-8c5be0cf-ubnt-loco-m-xw-squashfs-factory.bin

Wed, 05/16/2018 - 14:27

(Reply to #5) #6

k1ky

dev-176 locoxw is correct

Yes, you will want to use the dev-176 loco XW firmware.

Wed, 05/16/2018 - 14:55

N2JWC

understood...

However, at this point I can not get into the NS to do anything. I can't do a firmware recovery, I can't do anything.

Wed, 05/16/2018 - 15:23

(Reply to #7) #8

k1ky

Have you tried a TFTP load?

You will probably need to do a TFTP Firmware load. Might be easiest to TFTP the UBNT 5.5.1.0XW Firmware back on it and try the graphical interface to load the dev-176 NANO LOCO XW. I believe we may be close to having a "new" installer, so you may wish to wait - or you can contact me direct and I'll attempt to assist.

Wed, 05/16/2018 - 19:40

(Reply to #8) #9

K5DLQ

A serial console recovery may

A serial console recovery may be required at this point.
Might try this: https://www.aredn.org/content/unbricking-node-kd4rsx

Thu, 05/17/2018 - 08:08

(Reply to #9) #10

N2JWC

that is what I was thinking..

but avoiding if at all possible. I did miss my buddies heading up to Dayton, they left earlier than originally planned and I could have intercepted them if they had told me. Anyway, I have it at work today and will try a normal windows machine, worse case I already ordered a USB to TTL cable as I have no other way to drop header connections on bare wires.

I will let you all know what happens :)

John
N2JWC

Wed, 05/16/2018 - 18:01

#11

N2JWC

TFTP was attempted and failed

I did try the TFTP recovery mode. I end up with the alternating LED lights, however the NS5 never replies to a ping on 192.168.1.20. The only thing I have not been able to try is use a dedicated Windows machine. I have tried from my Mac and I have tried from my Windows VM on my Mac.

I am willing to wait, would eventually to get it going becuase I want to build a 2 node mesh, create some presentation slides so I can stir interest in AREDN in my area. I have two friends ending out to Hamvention tomorrow, they will likely go to the AREDN forum and be more interested when they return.

I can video and upload the experience I am getting with the LEDs if that helps.

John

Wed, 05/16/2018 - 18:37

#12

k1ky

It should be there

It should be there on 192.168.1.20 - Suggest using a Windows PC, set the IP to 192.168.1.22 and Gateway 192.168.1.20
You should be able to FTP the UBNT image (or possibly the AREDN image) Otherwise - have your friends take it to Dayton and maybe some of the AREDN Gurus can fix it up for you at the booth!

Wed, 05/16/2018 - 19:20

#13

N2JWC

man.. I should have posted sooner

I tried pinging 192.168.1.20. I will have to take it to work to use a windows machine then, or I'll see if I can get it to my buddies before they leave.

So the out of the box AirOS was v5.6.11 (XW).

My second one is still factory and of course works fine.

Image Attachments:

Thu, 05/17/2018 - 15:31

#14

AE6XE

Sometimes the tftp doesn't

Sometimes the tftp doesn't work unless the loco sees a network link light when it powers on. Make sure the cat5 is connected to a switch or to your computer which has a live ethernet port before the loco is powered up.

Does the device still boot with the led light behavior as you described? -- Power light on, network port line possibly blinking, last link (blinking while booting) solid green after boot.

If the loco is in this state, you should still be able to directly tftp the nightly build loco-m-xw factory image. The alternative is a serial cable and unbrick procedure...

If in this booting state, I suspect the network port will not function with the image used. tftp is best/first option to recover, although you could test and confirm it is in this state with wireless:

1) connect with a laptop on wifi SSID "meshnode", browse to "localnode.local.mesh:8080" or "192.168.1.1:8080"
2) go into basic setup and configure, reboot.
3) make an RF connection to the node from another mesh node, so you can remotely access setup, then do a sysupgrade with the correct nightly build loco-m-xw sysupgrade image.

Joe AE6XE

Wed, 06/06/2018 - 22:03

(Reply to #14) #15

N2JWC

Thanks - current state

Thanks for the email Joe.

I finally got the cable and more importantly some time to get into the nano. It has NOT UART header pin set on the board at all. Nothing.

The lights are in the correct state. Are you in the belief that it may be in TFTP mode already? If so, the IP is not pingable. I will try using a switch rather than a cable to my computer. I do have another nanostation with the same hardware. If we can be sure which firmware to use, and attempt a mesh I am good with it.

John
N2JWC

Wed, 06/13/2018 - 23:28

(Reply to #15) #16

N2JWC

Saw the meshnode - configured

Joe,

I saw the meshnode and I was able to get into it. Based on what you are saying I need to get my other NS5 up and running, then use it to get on the 'broken' node to bring it up to the nightly loco-m-xw build. So before I do that, I am assuming you are suggesting I use the nightly build for the loco-m-xw first, make sure it is good and it will auto mesh with the 'broken' NS5, correct?

4 Mar 2018

AREDN-develop-176-8c5be0cf-ubnt-nano-m-xw-squashfs-factory.bin

John
N2JWC

Wed, 06/06/2018 - 22:17

#17

AE6XE

If the leds are as described

If the leds are as described in my previous post, this would indicate the AREDN firmware has booted and is running. But due to the (wrong) AREDN firmware image previously loaded, the physical network port may not be functional. When the loco is running with the leds in this state, on your laptop, without any cat5 cables connected, look for a wifi access point to connect to. Do you see one called "meshnode"? If so, connect and follow the procedure above.

Joe AE6XE

Thu, 06/14/2018 - 08:15

(Reply to #17) #18

N2JWC

Got in on the "meshnode"...

As indicated on the other thread response. I did get in on the meshnode. Once rebooted I guess the meshnode is hidden ( I haven't scanned with my tools for hidden SSIDs), and now I have to use another node to get in and manage it. From what I read in your previous response.

BTW, I commented there was not UART or serial header pins. And that is true, however after looking at some pictures of newer models and performing boot recoveries. I have these pads that seem to be the serial connections. Just in case I need them or someone else finds this post and has newer-ish XW gear.

John
N2JWC

Image Attachments:

Wed, 06/27/2018 - 17:26

(Reply to #18) #19

AA6E

Same situation here?

I started a separate thread about this, but it looks like I have exactly N2JWC's situation here -- up to a point. I have two new NanoStation loco M5's. To start with, I've just been working with one. It began life with AirOS 6.0.6 (XW). I could downgrade to 5.6 and 5.5 as advised on the web. Then I loaded one or two different images, ending up with AREDN-develop-176-8c5be0cf-ubnt-loco-m-xw-squashfs-factory.bin. No loading errors, but we end up with a mute Ethernet port. [Right green LED solid ON (after a period of faster then slower flashes).] The LAN LED shows some activity as my host is trying DHCP discovery. However, it never gets an IP. Wireshark shows nothing coming out of the node.

But fortunately Joe pointed me to the MeshNode wifi access (ch 36). With that, I can connect and start to configure the node. There was the suggestion that uploading the sysupgrade file might cure the Ethernet problem. Tried that, no change. Furthermore, when I configure the node and try to "save changes", the node says "configuration not saved: parameter 'DTDMAC' in file '_setup.default' does not exist". Could that cause an Ethernet problem? When I force a reboot, the node comes up with at least some of my configuration OK. I can view Net Status.

Am I correct in thinking that "MeshNode" goes away when the node starts mesh operation? If that's so, I would lose any direct control over the node from my PC. Why then do I still see MeshNode after my reboot?

If we don't have any further suggestions, I can always start configuring the second node to see if it has the same issues.

BTW here is my sysinfo dump:

 node: AA6E-LocoM5-001
model: NanoStation Loco M5 XW 

!!!! UNSUPPORTED DEVICE !!!!
boardid: 0xe845
Device has not been tested. Please file a ticket with your experiences.

br-lan 78:8A:20:AA:0E:29
wlan0  78:8A:20:AA:0E:29

/proc/cpuinfo
system type		: Atheros AR9342 rev 2
machine			: Ubiquiti Loco M XW
processor		: 0
cpu model		: MIPS 74Kc V4.12
BogoMIPS		: 266.64
wait instruction	: yes
microsecond timers	: yes
tlb_entries		: 32
extra interrupt vector	: yes
hardware watchpoint	: yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa			: mips1 mips2 mips32r1 mips32r2
ASEs implemented	: mips16 dsp dsp2
shadow register sets	: 1
kscratch registers	: 0
package			: 0
core			: 0
VCED exceptions		: not available
VCEI exceptions		: not available


nvram
hsmmmesh.settings=settings
hsmmmesh.settings.wifimac='78:8a:20:aa:0e:29'
hsmmmesh.settings.mac2='170.14.41'
hsmmmesh.settings.node='AA6E-LocoM5-001'
hsmmmesh.settings.config='mesh'

Thanks for any additional tips!

73 Martin AA6E

Thu, 06/14/2018 - 10:29

#20

AE6XE

N2JWC, if you can get in

N2JWC, if you can get in and navigate to setup and then Administration page, then you can upload the loco-m-xw sysupgrade firmware directly (uncheck 'keep settings').

use this image: https://downloads.aredn.org/snapshots/trunk/ar71xx/generic/AREDN-develop...

Joe AE6XE

Sat, 06/16/2018 - 17:48

(Reply to #20) #21

N2JWC

SitRep - all good!

Thanks Joe. I am all good now. I had already performed setup on the 'broken' NS5loco. I was able to successfully install the nightly on my other NS5loco, the mesh did it's thing. I was then able to get into the 'broken' NS5loco and perform the upgrade to the nightly build as well. ALL IS GOOD.

Thank you again!

John
N2JWC

Amateur Radio Emergency Data Network

Menu SF

You are here

Nanostation loco M5 (XW) - can not config nor recover

AREDN-3.16.1.1-ubnt-nano-m-xw-squashfs-factory.bin

Amateur Radio Emergency Data Network

Search form

Menu SF

You are here

Nanostation loco M5 (XW) - can not config nor recover

AREDN-3.16.1.1-ubnt-nano-m-xw-squashfs-factory.bin