We’ve had several A5-14s around that were originally intended to take Ubnt M2 clients. We never really got around to that before we ended up swapping to AC gear and using RF Elements horns on the towers to massively improve the performance we were getting from the M2 gear. Part of the hold up was the perceived train wreck of the Mimosa gateway routers. We saw a high failure rate and lack of remote management after setup. I wasn’t here at the time. Just what I heard from those who were.
We recently got a bunch of C5xs and associate N5-x25 dishes. We installed the first two clients yesterday.
The first installed reasonably well. It happened to be to an A5-14 in wifi interop mode. The installer app was apparently useless without the G2. I just connected the radio to the LAN of the router and used my Ubuntu laptop. I had to wait through the C5x rebooting to WiFi interop mode. I didn’t have access to the AP until the C5x was installed or I’d have flipped the AP to SRS because I expect SRS to be more reliable/faster. There were hiccups but it got the job done with a few stutters via the auto option. We had to move on, so I didn’t try flipping the AP to SRS mode.
For the second install, I let our other installer run through. I also made sure the A5-14 to which he was attempting to install was in SRS mode before he started. We had the AP and the C5x on 2.5.4.
He had significantly more trouble. He was using his MacBook directly connected to the C5x. The auto setup process just didn’t work. The manual unlock setup process didn’t work either. Maybe it didn’t like the manually configured IP setup from his laptop?
We eventually got him through the firmware upgrade and unlock process the same way we do the B5s. But! Once installed, there was no alignment tool that we could find. Mimosa alignment is a slow process on the B5s with the alignment tool. It was glacial just going by the dashboard with it updating about 30 seconds after we mad adjustments. Is it hiding in plain sight on the dashboard?
We eventually got alignment to the point where we had 20 dB SNR. RSSI was about -70 dBm. Distance is 2.2 miles, 3.5 km. That distance is considered rather close on our network. According to GPS on the A5 and my phone, the client is about 15 meters above the A5.
The PHY would not come above 7/7. We tried a lot of things with positioning. We weren’t dealing with the most clear fresnel zone. I could see the A5 through binoculars. The ubiquiti PB-M5 400 radio we were trying to replace was working well to an UBNT AC omni on the same tower. The Ubiquiti had RSSI of -73 dBm and was installed two feet lower so that it did not have line of sight and was going through three pine trees about 10 meters from the client radio which had grown up since it was installed. We figured we should be seeing at least as much speed over the Mimosa link. PER was variable between 3% and 50%. I figure that kept the modulation down.
After a couple of hours of trying things, including changing AGC to auto and then slowly lowering it from about -62 to -77, I used the Ubiquiti link to switch the A5 to WiFi Interop mode. Bam! PHY was >80mbps with no other changes. PER was variable between 1 and 5. PHY would drift from about 47 to 180. It tended to settle around 87/87. Speed tests were pretty decent.
I don’t understand why SRS mode was seeing such a high PER. Maybe interference, but if so, it should have been there in WiFi Interop mode too…
I’m a noob with Mimosa PTMP so I’m probably just doing something stupid. Could someone whack me with a clue by four?
Today, I’ve found the config for a MikroTik hAP which we can substitute for the G2s during install. Maybe that will help with the install issues. I think all of the G2s went to recycling.