Aha, I always wondered what this calibration was actually doing! So this is (one of) the things is does? It calibrates and set the noise floor level? Ok. Learning everyday! 
Noise floor threshold impacts on S/N => the way card (driver) selects the speed which CPE must send data to AP.
hmm, I thought to understood the rate selection is more base upon how many ack’s returns were received by AP from station. The influence on the S/N imho is having influence since a bad S/N only means the link is bad and therefore many ack requests/respond packages get lost so AP sets and tries lower data rate…
Insteresting that NF threshold is changing the measured RX level as well, not only the S/N ratio.
I don’t see this happening on my board. Also doesn’t make sense to me. RX is RX. As long as receiver can distinguish radio signal from noise it measures the eirp recieved by the transmitter for that signal. Software in ROS converts it to a level. Off course a software bug could have influence in this case but basically the RX signal strength should not differ as a result of surrounding ´noise´.
[One guy shouting on an empty square will be heard by listener at certain volume. Now, if AC/DC (rock band) is playing on that square and same guy shouts again with same volume listener could hear it at the same level (not considering sound will be damped by crowd) if he had good enough filter to reject all the other new noise surrounding him. A ´listener with a good filter will notice exactly the same volume for the ´shouter´. The physical sound waves generated by the ´shouter´ are not lost. Physically they are still around. You only need to distinguish them from all the rest. Radio wave energy works exactly the same imho. The radio wave is not get lost because other radio wave are around. You only need a good filter to catch them. But than the energy is still the same.]
Along the time (e.g. last 18 months), several changes on ROS version (and UBNT CPEs firmwares) results in several TX/RX signal level combinations and several TX/RX CCQs. Once, due to firmware/ros glitches I guess, the difference between TX & RX signal levels was 10dB! Why, if AP is 20dBm and CPEs are 20dBm devices? I even thought my UBNT CPEs was tampering the TX power (where they should be 20dBm was 10dBm, for instance).
Obviously sometimes something goes wrong in the programming code that make the receiver levels translate into date we get presented in the ROS.
From the interface wireless print advanced:
noise-floor-threshold=default > nv2-noise-floor-offset=default
There is this nv2 offset, for now “default”. May be due to the rx period (no more 25us but some miliseconds) the way to measure noise level has changed on such mode.
You show me again it is worth to check out the terminal more often!
Never saw this. What would it mean? NV2 has its own conversion (receiver to console) or does it really handles nf different? MT should give more clearance on this!
After all this, I am still not sure what a set nf level actually would do on a link that is strong (good signals) but is suffering from interferences or multipath receipts.
If CPE receives AP signal with -45 while a scan shows several other close distance (in freq’s) channels are being picked up at levels ranging from -60 to -95 while noise level for its working freq. is -90 to -95 would setting nf threshold to for instance -60 reduce the change receiver picks up eirp energy from other radios? Or the filters are set so only signals stronger than -60 are allowed to pass to receiver while anything else is filtered out?
I am just wondering if setting nf threshold at lower levels than defaults (= calculated) would sort of ´harden´ radio’s against unwanted interferences from other freq’s?
Most of my links have relative strong signal levels but a part of my network is located in a heavy urbanised environment where sort of all available 5Ghz band frequencies are to be used due topology and amount of users. As a result many radios are also picking up several other signals, sometimes at levels into the -70’s and -60’s!
So one of my main jobs has always been to fight against interferences, hidden nodes, multipath, etc. etc. etc. I want from channel separation to rts/cts to physical radio separation, narrowing bands and playing with virtually all other wireless dynamics and improved the links a lot. But now competition is overshooting my area with even more signals I need to go to next steps to keep my network stable and at the same time honouring bigger data throughputs and lower latencies. Hence I use now nv2 and explore the very last configs I didn’t bother to look at before..
So here is noise floor threshold setting. Firt red it doesn’t work on nv2 and now just discover (your post!) it might have a meaning, only probably different than in normal 802.11 environment…
The exploration journey in the land of wifi technology is not ended…