I’ve upgraded to rc7 and when I turn on nv2 I don’t see any signal loss but my ccq goes from ~95% down to about 16% and wont sustain any traffic. Has anyone else encountered this or am I just doing something wrong. I’m using an R52Hn on both the AP and CPE with the AP being 2 chains on a dualpolarity sector antenna and the client I’m just using a single chain to a simple polarized panel antenna. On the plus side with 802.11n strait I’m getting 128mbps throughput with a single chain so I’m very happy about that, but I’d love to use nv2 if possible.
What is your noise floor/frequency usage like in the area?
Do you have your noise floor threshold set on your AP?
What do you have your TDMA period set to?
Do you have your noise floor threshold set on your AP?
How is this done?
It is under the advanced tab on the wireless interface. You don’t want to set it with the NV2 package though because it does some strange things with signal strengths and noise levels. I am not sure if it actually causes any ill effects but it will cause ROS to show signal levels much lower than they were without the noise floor threshold set.
Ok I note the default is -127,
Is a noise floor of -93dBm better than -107dBm
I would ask the question if one one my AP’s has a noise floor reading in the wireless status tab of -97dBm, should i set it at say -110 giving the AP a margin of 13dB?
I have just checked that most of my AP’s at one site are between -93dBm to -100dBm but one is at -107dBm,
Well the more negative the number the better, that means that your AP is seeing less noise from the environment. With your noise floors you shouldn’t need to mess with the noise floor threshold settings at all.
Normally a noise floor threshold ignores signals that are below what you have the threshold set at. For example if you have the noise floor threshold set at -80 in ROS and you have a client that with a signal level of -84 in theory that client shouldn’t be able to connect to the AP because the AP should ignore that signal level because it is lower than your threshold setting. But if all your clients have signals of say -65 or better then all your clients would connect fine but the AP would ignore outside signals that were less than -80.
I am in a fairly noisy environment so I usually run a noise floor threshold of -80 to -85 and wont install a new client with a signal strength of less than -65. But I noticed with the install of 4.16 with the NV2 package that all of my clients signals were on average 15db worse than they were with the version I upgraded from. So instead of being -65 the were -80, well after some playing around with the settings on the AP I figured out that with the NV2 package the received signal strength shown by ROS is directly related to the noise floor threshold setting. So the higher you have the threshold set to the worse ROS shows your received signal levels at. At this point in time I really am not sure how ROS is handling the noise floor threshold so I have just turned it off on all devices that I am running the NV2 package on. I have never seen another wireless device “including other ROS versions” where setting the noise floor threshold effects received signal strengths. I spoke with MT about it a little bit and they are indicating that it is working as it should, but to me it makes absolutely no sense whatsoever to work in the manner it does with the new wireless package.