The node I flashed today is an XM version of the Rocket M5-GPS. It went well except the displayed range of transmit frequencies is wrong (too low). It reports my other 5 GHz node as being on channel 180 - which is correct,
When selected an operating frequency about 5 channels down from the top of the available list, the other reported that the M5-GPS was operating on channel 3460 (if I remember). So I powered it down.
UBNT loads the same firmware into the GPS and non-GPS versions. I guess that is not true of AREDN?
Anyway - what to do? Can I just fix a list somewhere in software? This unit is at the top of a tower.
I will download a support file later this afternoon.
You are here
M5-GPS
Sun, 05/08/2016 - 15:25
#1
KE2N
M5-GPS
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
The board info file from AirOS is needed to prepare the proper AREDN config settings. The symptoms indicate the default guess settings think the device is 3Ghz (a 5Ghz device to linux with a -2Ghz down converter).
When you see ch 3460, but the nodes are 5Ghz devices, simply add +2Ghz. This would be 5460. There is a range of 5Ghz frequencies outside of part 15 and ISM space, that in the AREDN code we assume means we're seeing a 3Ghz device in part 97 space 'bleeding through'. However, we've since discovered in practice, there are WISPs or other entities that are using these 5Ghz frequencies (with some creative fcc licensing ;) ).
Joe AE6XE
attached: the two board files from another GPS running OEM firmware
Edit /www/cgi-bin/perlfunc.pm and add the entry below or touch up the existing '0xe1b5'. This definition is needed to test out the device:
'0xe1c5' => {
'name' => 'Rocket M5 GPS',
'comment' => 'Rocket M5 GPS',
'supported' => '-2',
'maxpower' => '22',
'pwroffset' => '5',
'usechains' => 1,
'rfband' => '5800ubntus',
},
reboot. Please post results of your testing with this device.
Joe AE6XE
I entered that listing as an additional entry - just ahead of the standard M5 - and it came up with the correct frequency list. It is running paired with an NS5 at the moment on 5900 MHz.
Thanks.
AREDN now can add M5GPS to the list of hardware supported.
Long story short, I purchased a box of 10 RM5s on eBay, guy sent 8, I contacted and he sent 4 to make up for the short. Turns out 1 of the 4 is an RM5 GPS (XM). It tested Good/Good with U-Boot Tester, so after reading this thread I figured I'd put 3.16.1.0 on it. When it boots up, the far-right light flashes for a bit, and then goes solid. Wireshark shows no ethernet packets from that node whatsoever.
I did run an U-Boot Tester backup before trying to put AREDN on it. I have it in TFTP mode right now. How can I restore the U-Boot Tester backup via TFTP? What file do I need to restore?
Other question: Does AREDN know how to take advantage of the GPS timing between two GPS nodes? If not, is there plans to add it?
We have two hilltop locations which we'd like to do a direct connection with some high-gain PtP dishes, but it's a stretch and a half (80 miles). I've read somewhere that some folks are using these GPS models on non-ham bands with the original software to achieve greater PtP distances.
Ok, so fortunately I do a screen print out of each node before I start dinking, that way I can track what software it came with. Looks like my node came with XM.v5.6-beta9.25854.150113.1823. I was able to find this version with some Google searching and TFTP is happy with that.
So at least I am back online, but would still like to know the tricks to get it up on AREDN.
Joe AE6xE
I meant TFTP in the literal use. I understand what you're saying and apperciate the info. But after putting AREDN on this node, I thought it was basically bricked (it wasn't, see my last comment), so I had to find something to put back on it. It looks like what was required was a 5.6 version to TFTP with. Not sure if I had to go to the exact version I was on originally, but that is what I did and it fixed it.
So, to recap, my error was trusting u-Boot Tester saying "Good / Good" on a 5.6Beta version. I should have back-revved to my trusty 5.5.11 version first, which is what I normally do (just didn't realize the GPS versions run the same firmware code).
I started with this: XM.v5.6-beta9.25854.150113.1823
Backrevved to this via AirOS: XM.v5.5.11.28002.150723.1344
AREDN flashed via AirOS to this: 3.16.1.0
Actually, I think I was totally fine doing what I did originally going from a Good/Good 5.6beta9 to AREDN 3.16.1.0, My mistake was being in the Secondary Port, which after the AREDN upgrade I could not access the management interface on. Interesting that the Main and Secondary ports on the Rocket is reversed from the NanoStation M5 (my first experience with Ubiquiti nodes).
Thanks!
So, can we get GPS support for LAT/LON and ASYNC support between two GPS nodes in AREDN?
Well, mine too comes up with untested hardware banner and inability to store or change anything... Board ID: 0xe1c5
So, My basic question is how does one edit: /www/cgi-bin/perlfunc.pm ???
Thank you,
Chris K7AZ
the M5-GPS support was added in our nightly build #120 (resolved ticket #162: http://bloodhound.aredn.org/ticket/162 )
See the latestes changelog here: http://downloads.aredn.org/snapshots/trunk/ar71xx/generic/changelog.md
For more info on nightly builds: http://www.aredn.org/content/development-code-branch-now-available
Nice that there is a fix but I am clueless on how to put or edit those lines into my Rocket M5-GPS.
Need lots of neubie help here. Thanks, Chris K7AZ
We don't advocate editing the configs manually, especially for newbies who are not comfortable with the linux commandline and programs. I'm not trying to offend by any mean. I'm just trying to protect you from getting frustrated and potentially having to reload your firmware.
So, your options are:
1) just use the node with the "warning".
2) try the nightly build. (but, that comes with risks as noted on the nightly build article.)
3) wait for the next production release.
Darryl
Thanks again to Ken! 73 Chris K7AZ Lompoc.
According to Google Maps, that's a 30 mile link. Did you ever get this link going?
73
Orv W6BI
TeamView and Hamshack Hotline available as well as good old CF or VoIP land line.
Thank you,
Chris K7AZ
https://github.com/aredn/aredn
If the device has AirOS XW, then possibly the rockect-m-xw image needs to be loaded instead of the rocket-m-ti image. It's been too long that I don't recall the specifics of why this documentation has different images specified.
Joe AE6XE