I have just acquired a PBE-M5-300 and flashed it with the nightly build. It has an "Untested Hardware" banner on it. From other posts here, I gather that means there may be something different about my hardware than you have run into before. Below is what the /sysinfo.json page shows. As you can see, the board ID is0xe3e5.
Please advise what if anything further I should do. I just got this, and so far all I know is that this node will communicate with a NSM5 in an adjacent room of my house! But we are counting on it for an upcoming ARES event with a 10 mile hop, so hopefully there won't be any show stoppers.
Dave
Below is the /sysinfo page:
node: K7PVA-PBE-M5
model: PowerBeam M5 XW 300
!!!! UNSUPPORTED DEVICE !!!!
boardid: 0xe3e5
Device has not been tested. Please file a ticket with your experiences.
eth0 F0:9F:C2:5D:AA:A8
eth0.1 F0:9F:C2:5D:AA:A8
eth0.2 F0:9F:C2:5D:AA:A8
wlan0 F0:9F:C2:5C:AA:A8
wlan0-1 F0-9F-C2-5C-AA-A8-00-44-00-00-00-00-00-00-00-00
/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='f0:9f:c2:5c:aa:a8'
hsmmmesh.settings.mac2='92.170.168'
hsmmmesh.settings.dtdmac='93.170.168'
hsmmmesh.settings.config='mesh'
hsmmmesh.settings.node='K7PVA-PBE-M5'
hsmmmesh.settings.tactical='Wilson-5'
Please advise what if anything further I should do. I just got this, and so far all I know is that this node will communicate with a NSM5 in an adjacent room of my house! But we are counting on it for an upcoming ARES event with a 10 mile hop, so hopefully there won't be any show stoppers.
Dave
{
"lon": "-112.410667",
"ssid": "AREDN-10-v3",
"tunnel_installed": false,
"interfaces": [
{
"name": "eth0.1",
"mac": "F0:9F:C2:5D:AA:A8"
},
{
"mac": "F0:9F:C2:5C:AA:A8",
"name": "wlan0",
"ip": "10.92.170.168"
},
{
"mac": "F0:9F:C2:5D:AA:A8",
"name": "eth0",
"ip": "10.229.85.65"
},
{
"mac": "F0:9F:C2:5D:AA:A8",
"name": "eth0.2",
"ip": "10.93.170.168"
}
],
"api_version": "1.1",
"chanbw": "10",
"grid_square": "DN32tv",
"lat": "42.876278",
"active_tunnel_count": "0",
"channel": "182",
"model": "PowerBeam M5 XW 300 ",
"board_id": "0xe3e5",
"firmware_mfg": "AREDN",
"node": "K7PVA-PBE-M5",
"firmware_version": "develop-176-8c5be0cf"
}
Below is the /sysinfo page:
node: K7PVA-PBE-M5
model: PowerBeam M5 XW 300
!!!! UNSUPPORTED DEVICE !!!!
boardid: 0xe3e5
Device has not been tested. Please file a ticket with your experiences.
eth0 F0:9F:C2:5D:AA:A8
eth0.1 F0:9F:C2:5D:AA:A8
eth0.2 F0:9F:C2:5D:AA:A8
wlan0 F0:9F:C2:5C:AA:A8
wlan0-1 F0-9F-C2-5C-AA-A8-00-44-00-00-00-00-00-00-00-00
/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='f0:9f:c2:5c:aa:a8'
hsmmmesh.settings.mac2='92.170.168'
hsmmmesh.settings.dtdmac='93.170.168'
hsmmmesh.settings.config='mesh'
hsmmmesh.settings.node='K7PVA-PBE-M5'
hsmmmesh.settings.tactical='Wilson-5'
It is sitting in the testing phase awaiting feedback from users of any issues/concerns/successes.
It is best to put that in the ticket so its part of the official record and helps provide a single source to see how well the hardware is progressing (so it can get moved to officially supported status) or any known flaws from users running them become seen and others can quickly confirm if the issue is real.
You can log into bloodhound with your existing aredn.org credentials.
Dave