This report refers to inSSIDer 2.0 for windows, installed on a W7 Sony Vaio laptop.
I have a nearby Access Point (AP), which is about 0.5 metres away from the laptop and it consistently has an RSSI of between -6 and -8 dBm. This causes a problem with both the Time Graph tab and the Channels tab because they both have an upper value of -10 dBm. On the Time Graph tab my AP is completely invisible because it is always outside the graph's upper boundary. On the Channels tab my AP is only partly visible with the sides of the plot visible but no top line and hence no name either. Is there a way to change the upper bound of the graphs so that it is high enough to show my AP?
These both seem like quite serious shortcomings to me. It would be nice if the vertical axis either went up as far as +5 dBm or was able to automatically scale itself to about 10 dBm higher than the highest recorded value - this would ensure that the graph was always making the best use of the available screen and also always showed everything.
This report refers to inSSIDer 2.0 for windows, installed on a W7 Sony Vaio laptop.
I have a nearby Access Point (AP), which is about 0.5 metres away from the laptop and it consistently has an RSSI of between -6 and -8 dBm. This causes a problem with both the Time Graph tab and the Channels tab because they both have an upper value of -10 dBm. On the Time Graph tab my AP is completely invisible because it is always outside the graph's upper boundary. On the Channels tab my AP is only partly visible with the sides of the plot visible but no top line and hence no name either. Is there a way to change the upper bound of the graphs so that it is high enough to show my AP?
These both seem like quite serious shortcomings to me. It would be nice if the vertical axis either went up as far as +5 dBm or was able to automatically scale itself to about 10 dBm higher than the highest recorded value - this would ensure that the graph was always making the best use of the available screen and also always showed everything.
Thanks, Brian.