I did it with a 5GHz version. Tried the latest openWRT build. Bricked the device...Going to either trash it or open it up and try to connect via serial to recover. It's in a pile in the shack.
Ref: https://wiki.openwrt.org/toh/ubiquiti/powerbeam
[after edit] let's make sure we are not talking about different hardware. Which device do you have? OpenWRT claims this XW bug does not exist on the following and *is* supported:
PBE-M5-300
PBE-M5-400
NBE-M5-16
OpenWRT claims this XW bug "is present on *some* models":
NBE-M5-19
OpenWRT emphatically claims this hardware is supported and does not have the 'XW' ethernet bug. Their wiki has been known to be wrong before, but this is something we are motivated to get to the bottom of and validate one-way-or-another. What is noteworthy, is that OpenWRT reports these devices to have a different System-on-a-chip, the SOC AR9380 vs. what is in the other XW devices with SOC AR934x. This would give credibility that the XW ethernet bug does not show in this hardware.
KG9DW, this should be the "loco-xw" image to install. Did you try this image?
If you have one of these devices, firmware images (factory and sysupgrade) to test and report results on are located with the nightly builds for AREDN:
Be sure to downgrade to the XW 5.5.x AirOS image first! Before loading AREDN, the 'boardid" info from AirOS may be needed (please send in):
1) The device should be running AirOS.
2) Telnet or Putty into the node (default user is ubnt; password ubnt; default ip 192.168.1.20)
3) Run "cat /etc/board.info"
4) Copy-and-paste the output and post it in response to this post.
I did not find tickets for the other models and the boardid information is probably needed. Note, if you install a nightly build image on any of these models, some basic settings, e.g. channel selection, may not have proper options until the boardid information is added to AREDN firmware.
Please sign the "don't beat up Joe for bricking my device" virtual waiver first. :) But I will assist to unbrick...
It is a PBE-M5-400. I tried the latest openWRT build when I bricked it back in June. I also read the wiki and said WOW, it might work! Well, it took the image, did the magical flashing of leds, rebooted twice, and then is deadish. Can't ping on any ip, won't give out an ip via dhcp. Tried to restore firmware via tftp but can't get it to go into tftp mode by holding the reset button on power up.
I can send you the radio if you want to take a look.
I managed to wrestle the device in a lock hold long enough to get AREDN nightly build loaded. There's a couple of issue to resolve in the nightly build before testing can commence on this device. http://bloodhound.aredn.org/ticket/185
Joe, Thank you for the fantastic step by step to convert the Powerbeams.
I was lucky and converted the powerbeam that I received today. (PBE-M2-400)
I will let you know how or if it performs.
Kevin - N0KVN
I just received a PBE-M5-400 with a test date of 6/27/2017.
It came with AirOS XWv5.6.11.
I downgraded to AirOS XW 5.5.10 via GUI
(XW.v5.5.10-u2.28005.150723.1358.bin)
then loaded
AREDN-develop-176-8c5be0cf-ubnt-rocket-m-xw-squashfs-factory.bin
I set the node name, changed the password, set channel 175 5875 MHz at 5 MHz BW, and rebooted.
I have two (2) NS-M5-XW within 20' (5875 MHz/5 Mhz) that see each other, but do not see the PBE-M5-400.
The PBE-M5-400 sees nothing.
I loaded AREDN-develop-176-8c5be0cf-ubnt-rocket-m-xw-squashfs-sysupgrade.bin
just in case I loaded the wrong 'factory' version earlier.
Same result. The (2) NS-M5-XWs see each other, but not the PBE-M5-400.
The PBE-M5-400 sees nothing.
Please, where is help ?
Thanks, Chuck nc8q
Had I also done a 'scan' on either nanostation I'd have caught it.
I would have seen my neighbors' WiFis. :-|
Different bandwidths.
Again, Thanks.
Chuck
This is great news. This will give the project another readily available radio option for point to point links. These are had for $100 each new from multiple sources. Outstanding!
Yes, it has been reported safe to load AREDN 3.17.1.0RC1, the release candidate to a PBE-M2-400. W7ADD loaded a previous nightly build on one of these devices and reported there were no issues after running for several weeks. Be sure to follow the normal procedure to downgrade to XWv5.5.x version of AirOS first before loading AREDN.
PBE-M5-300 and PBE-M5-400 OpenWRT support?
Ref: https://wiki.openwrt.org/toh/ubiquiti/powerbeam
[after edit] let's make sure we are not talking about different hardware. Which device do you have? OpenWRT claims this XW bug does not exist on the following and *is* supported:
PBE-M5-300
PBE-M5-400
NBE-M5-16
OpenWRT claims this XW bug "is present on *some* models":
NBE-M5-19
OpenWRT emphatically claims this hardware is supported and does not have the 'XW' ethernet bug. Their wiki has been known to be wrong before, but this is something we are motivated to get to the bottom of and validate one-way-or-another. What is noteworthy, is that OpenWRT reports these devices to have a different System-on-a-chip, the SOC AR9380 vs. what is in the other XW devices with SOC AR934x. This would give credibility that the XW ethernet bug does not show in this hardware.
KG9DW, this should be the "loco-xw" image to install. Did you try this image?
Joe AE6xE
For those early technology adopters...
If you have one of these devices, firmware images (factory and sysupgrade) to test and report results on are located with the nightly builds for AREDN:
PBE-M2-400 - loco-m-xw
PBE-M5-300 - loco-m-xw
PBE-M5-400 - rocket-m-xw
NBE-M5-16 - loco-m-xw
NBE-M5-19 - loco-m-xw <- ethernet bug on "some" models
Be sure to downgrade to the XW 5.5.x AirOS image first! Before loading AREDN, the 'boardid" info from AirOS may be needed (please send in):
I did not find tickets for the other models and the boardid information is probably needed. Note, if you install a nightly build image on any of these models, some basic settings, e.g. channel selection, may not have proper options until the boardid information is added to AREDN firmware.
Please sign the "don't beat up Joe for bricking my device" virtual waiver first. :) But I will assist to unbrick...
Joe AE6XE
It is a PBE-M5-400. I tried the latest openWRT build when I bricked it back in June. I also read the wiki and said WOW, it might work! Well, it took the image, did the magical flashing of leds, rebooted twice, and then is deadish. Can't ping on any ip, won't give out an ip via dhcp. Tried to restore firmware via tftp but can't get it to go into tftp mode by holding the reset button on power up.
I can send you the radio if you want to take a look.
I managed to wrestle the device in a lock hold long enough to get AREDN nightly build loaded. There's a couple of issue to resolve in the nightly build before testing can commence on this device. http://bloodhound.aredn.org/ticket/185
Joe AE6XE
Joe, Thank you for the fantastic step by step to convert the Powerbeams.
I was lucky and converted the powerbeam that I received today. (PBE-M2-400)
I will let you know how or if it performs.
Kevin - N0KVN
Hi, Joe et alia:
I just received a PBE-M5-400 with a test date of 6/27/2017.
It came with AirOS XWv5.6.11.
I downgraded to AirOS XW 5.5.10 via GUI
(XW.v5.5.10-u2.28005.150723.1358.bin)
then loaded
AREDN-develop-176-8c5be0cf-ubnt-rocket-m-xw-squashfs-factory.bin
I set the node name, changed the password, set channel 175 5875 MHz at 5 MHz BW, and rebooted.
I have two (2) NS-M5-XW within 20' (5875 MHz/5 Mhz) that see each other, but do not see the PBE-M5-400.
The PBE-M5-400 sees nothing.
I loaded AREDN-develop-176-8c5be0cf-ubnt-rocket-m-xw-squashfs-sysupgrade.bin
just in case I loaded the wrong 'factory' version earlier.
Same result. The (2) NS-M5-XWs see each other, but not the PBE-M5-400.
The PBE-M5-400 sees nothing.
Please, where is help ?
Thanks, Chuck nc8q
1) channel #
2) channel width is 5Mhz everywhere?
3) SSID
If all is the same, send the 'download support data' at the bottom fo the Administration screen in setup on each node.
Joe AE6XE
Thank you, Joe:
Had I also done a 'scan' on either nanostation I'd have caught it.
I would have seen my neighbors' WiFis. :-|
Different bandwidths.
Again, Thanks.
Chuck
XW.v5.6.2# cat /etc/board.info
board.sysid=0xe2c2
board.cpurevision=0x00001122
board.name=PowerBeam M2
board.shortname=P2B
board.subtype=400
board.netmodes=7
board.hwaddr=802AA8B20B16
board.reboot=40
board.upgrade=150
board.phycount=1
board.phy.1.maxmtu=2024
board.phy.2.maxmtu=2024
radio.1.name=
radio.1.shortname=
radio.1.bus=ahb
radio.1.subsystemid=0xe2c2
radio.1.subvendorid=0x0777
radio.1.txpower.max=28
radio.1.txpower.min=-4
radio.1.txpower.offset=10
radio.1.antennas=2
radio.1.def_antenna=1
radio.1.antenna.1.id=1
radio.1.antenna.1.name=400
radio.1.antenna.1.gain=18
radio.1.antenna.2.id=2
radio.1.antenna.2.name=Feed only
radio.1.antenna.2.gain=3
XW.v5.6.2#
Joe AE6XE