I flashed AREDN version aredn-3.21.4.0-ar71xx-ubnt-rocket-m-factory.bin on an older(2009?) Rocket M2 with a USB port. The unit took the update, but it shows a banner of "Untested Hardware" and the unit will not operate on channel -2. It shows the actual frequencies in the channel pulldown window, such as 2.212 GHZ, 2.417 GHZ, etc. It appears to receive OK on 2.412 as I can see my home wireless AP. The data shown when I click the banner is shown below. Anyone have an solutions?
Glenn WA3LAB
!!EDIT!! I found a post from 2015 about this problem, but no solution.
-------------------------------------------------------------------------------------------------
Rocket M2 - "UNTESTED HARDWARE" Banner
published by
K5YKG on Sat, 07/25/2015 - 00:19
I have been running a Rocket M2 for months using both BBHN 3.0.1 and ARDEN 3.0.2, Beta 1 and now beta 2. The Node Status page of each of the firmwares shows the yellow banner with the inscription "!!!!
--------------------------------------------------------------------------------------------------------------------------------------------
node: WA3LAB-RocketM2
model: Ubiquiti Rocket M
!!!! UNSUPPORTED DEVICE !!!!
boardid: 0xe112
Device has not been tested. Please file a ticket with your experiences.
br-lan 00:15:6D:FD:F3:F3
eth0 00:15:6D:FD:F3:F3
eth0.1 00:15:6D:FD:F3:F3
eth0.2 00:15:6D:FD:F3:F3
tunl0 00-00-00-00-00-00-00-44-00-00-00-00-00-00-00-00
wlan0 00:15:6D:FC:F3:F3
wlan0-1 02-15-6D-FC-F3-F3-00-44-00-00-00-00-00-00-00-00
/proc/cpuinfo
system type : Atheros AR7240 rev 2
machine : Ubiquiti Rocket M
processor : 0
cpu model : MIPS 24Kc V7.4
BogoMIPS : 265.42
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa : mips1 mips2 mips32r1 mips32r2
ASEs implemented : mips16
Options implemented : tlb 4kex 4k_cache prefetch mcheck ejtag llsc dc_aliases perf_cntr_intr_bit nan_legacy nan_2008 perf
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='00:15:6d:fc:f3:f3'
hsmmmesh.settings.mac2='252.243.243'
hsmmmesh.settings.dtdmac='253.243.243'
hsmmmesh.settings.node='WA3LAB-RocketM2'
hsmmmesh.settings.config='mesh'
hsmmmesh.settings.nodeupgraded='0'
vi /www/cgi-bin/perfunc.pm
Find in this file and change the string "0xe1b2" to "0xe112". Save the change and refresh the basic setup page. Possibly this device is very close to one we've seen before and all will work. Please capture the support download file, link at bottom of Advanced Settings page, and upload here. I need to review regardless if this change works or not.
Joe AE6XE
73,
Glenn WA3LAB
73,
Glenn WA3LAB
Orv W6BI
Yes it has a minus in front of the longitude. One of the hams in our group forgot the minus sign on his new node, and it showed up in China I believe. hihi Thanks for the tip. I just ran the server polling in test mode and it is seeing the node and the stations it sees also, so maybe the program is kicking out later due to a unknown Board ID, which is how this all started. You got me thinking .
73,
Glenn WA3LAB
I will offer nother W.A.G.
Is the node co-located?
e.g. Are other nodes using about the same coordinates?
Is another node 'on top of' your node on the map?
Did you zoom-in enough to get 'Spiderfy-Active' ?
I hope this helps,
Chuck
73,
Glenn WA3LAB
I contacted the author of the meshmap program Eric KG6WXC for any ideas on why this particular node was not recognized. His response was that all the data sent from the node appeared OK. He told me about a button on admin page that would reset the timers in the program so it would force a complete polling, and I could watch the debug output. What I found was that only about 50 out of 70+ nodes were being polled, and then the polling was aborted. This was caused by a duplicate entry in the database of an existing node. The program differentiates nodes not only by the node name, but by the MAC address. A week or so ago the node in question was replaced with a new one with a different MAC address, but the SAME NAME. The program determined there were two nodes, or 2 different MAC addresses, one in the database , and one just polled with the same node name. Duplicate! THAT'S when the meshmap program broke. If you don't add any nodes, nobody would notice it is broken because you are not expecting to see a new dots on the map.
The fix is to go to the admin node report and remove offending node from the list, The next full poll will repopulate all the missing dots and lines. Eric KG6WXC suggested removing all entries over a day old. Thanks so much Eric and Joe for your assistance. Man that was fun!
Glenn WA3LAB