Yes, it was on 2.5. 20MHz worked fine. Only started doing this after I
switched the link to 40MHz. Just put 2.6 on both ends a 1/2hr ago. I
hope that's all it is because I need the throughput.
On 1/14/2016 11:58 AM, Josh Luthman wrote:
Wait you're in 2.5? I think you may be seeing the bug I had. Fixed
for me now...
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
On Jan 14, 2016 12:49 PM, "George Skorup" <[email protected]
<mailto:[email protected]>> wrote:
I've had this 13.7 mile link running v2.5, 5.1 band, 20MHz,
non-GPS radios for 110 days without any issues. I switched the
slave scan to include 40MHz and then moved the master to 40MHz
width the other day. Since then it appears the slave has been
rebooting. However this morning, the link wasn't passing traffic
for over two hours, then it magically fixed itself. An hour later
and it rebooted. I remember reading some stuff, possibly release
notes, that the ePTP slave could reboot under heavy interference.
This link is on a very clean channel though. About -58 RSSI and it
maintains MCS 15 both directions nearly all the time.
So I don't have a clue. Ran perfect on 20MHz channel bandwidth.
Just needed a little more throughput out of it, thus 40MHz. I just
upgraded both ends to v2.6, so I hope that fixes it.
And no, these radios are not CE+ MACs.
