The newer GNSS equipped boards definitely maintain lock better. We
actually don't have any of the older GPS-only radios deployed. But..
some receivers still go stupid and/or lock up.
On 7/10/2017 7:56 PM, Mathew Howard wrote:
GPS problems haven't been as bad for us lately, but they are still
there. At least they increased the max holdoff time enough that
everything keeps running now... on the few sites where we still have
GPS issues, it's not that big of a deal if they get out of sync now
and then, so I just set the holdoff time to the max and gave up on it.
we have almost all of ours running at 25-27v, and they generally seem
pretty happy that way. It's when you get under 24v (at the radio... so
24v at the power supply generally isn't going to cut it) that they
tend to start getting flakey.
On Mon, Jul 10, 2017 at 7:33 PM, Joe Novak <[email protected]
<mailto:[email protected]>> wrote:
I think we are running 3.3 on everything now because of the 'Board
in reboot state'. I haven't seen it as a problem any time
recently.. but yeah. we have had our fair share of fun. Default
configuration of the 'reset' via power cycle is on. Thunderstorm
comes through... defaults 100 cpes. That was our mistake for not
being careful enough on the stock configuration, but I've never
actually had equipment do that to me.
Cold weather bug hit us so hard, it was just stupid. Almost all
our APs where bought in that time frame that had the bug.
I haven't had GPS problems though, and we do cruise along at ~27v
at multiple sites.
Joe
On Mon, Jul 10, 2017 at 7:24 PM, Steve Jones
<[email protected] <mailto:[email protected]>> wrote:
I love epmp, the same way i used to love ubnt, but this shits
getting out of hand, the distance reading only fluctuates by a
half mile or mile, 24 volts takes your sites down in a winter
power outage, never to return without sun, gps puck is about
50 percent useless, since even when its not flapping in the
wind it doesnt even work half the time, random reboots, now
"board in reboot" , snr being a flat out lie, and this with
the ap rssi. Id bet if they focused their limited codespace on
stuff that actually worked, the line would be better, still
not the garbage level of ubnt, but at this poibt its really
striving ti take that crown away
On Jul 10, 2017 7:00 PM, "Mathew Howard" <[email protected]
<mailto:[email protected]>> wrote:
Yeah, I've seen that a lot. The numbers on the AP used to
be pretty accurate, but somewhere around v3.0, it went all
wacky... I think they may have fixed it (or at least
improved it) in 3.3 or 3.4, but that particular release
note could be a figment of my imagination.
On Mon, Jul 10, 2017 at 6:56 PM, Steve Jones
<[email protected]
<mailto:[email protected]>> wrote:
They might as well not waste the codespace and memory
if its going to have this little value. Or just make
it a static number like ubnts fake noise floor
On Jul 10, 2017 4:47 PM, "Joe Novak"
<[email protected] <mailto:[email protected]>> wrote:
From what I understand Nate is correct. It's
calculated AP side. Ubiquiti has the so called
extra info packets they pass back and forth, as
far as I know EPMP does not at this point.
On Mon, Jul 10, 2017 at 11:42 AM, Nate Burke
<[email protected] <mailto:[email protected]>>
wrote:
I don't think it's a value that's passed
between the AP/SM, but Calculated at the AP
based on distance and MSC Level, and probably
some other things. So the Calc could be off.
On 7/10/2017 11:39 AM, Steve Jones wrote:
I haven't looked on other APs, just
dealing with an issue. this is 3.2.2
The AP is showing the downlink RSSI for
the SMs 10db or more stronger than the SM
is showing it. Is this a known bug?
