We have seen this on several nodes, and know it is not a real signal, but I wonder if it could an effect on the AGC, or other software tweaks that the node will do? Typically I have seen this on Nanostations M2 or M5, where the node is receiving a signal hovering right around the noise floor. This is not presenting any problems, but I just wanted to mention it in case it could affect the node operation.
73,
Glenn WA3LAB
73,
Glenn WA3LAB
I have many devices on adjacent channels that show no change in SNR or LQ/NLQ or TxMbps with/without neighbors
on adjacent channels.
Chuck
Joe AE6XE
I'd suggest that if the data returned is truly a "0" then "no value" should be considered NO DATA and left as a gap on the chart. Anything else would be artificial IMO.
Just an opinion,
- Don - AA7AU
I vote for -95 dBm...
Orv W6BI
At the noise floor - which is not always -95.
.
I assumed it was some type of bug. I would vote for no signal to at the noise floor as well. Thanks for all the answers.
73,
Glenn WA3LAB
Glenn, there is a fix for this issue in the latest Nightly Build (#257 or newer). http://downloads.arednmesh.org/snapshots/trunk/CHANGELOG.md Here is what it looks like.
Before the fix:
After the fix:
I like it. Upgraded a few of my nodes, and saw something quite unexpected on one. The two nodes that truly have nothing to talk to showed a flat line (as expected) Here is a S/N chart from a Rocket M3 while I updated the other end of the link. I was expecting the signal to drop to the noise floor while the far end node was rebooting. This is what I saw:
The Rocket that this screen capture came from is about two feet from the far end of the link, and is operating with dummy loads for antennas on the near end. The far end has the feed only for a Rocketdish antenna. Both radios are operating at low power settings.
Yes, it's a Google Chrome induced issue.