For some reason, measuring the tags with tx power = 15.0 dBm via
while true; do echo -n '100000 26' > driver/measure && echo "$(cat read_rate) $(cat rssi)"; done;
gives readings with greater frequency and the measurement values are more stable which I can tell solely by looking at the numbers in the terminal. I'm comparing this behaviour with
while true; do echo -n '100000 26' > driver/measure && echo "$(cat read_rate) $(cat rssi)"; done; which corresponds to tx power = 26.0 dBm and thus I'd expect it to measure the tags more reliably than the 15.0 dBm approach, however this is not the case.
Why is it so? Could this be caused by some kind of bug in our software, or is it an issue on the r200/m100 / firmware side or related to physical phenomena?
For some reason, measuring the tags with tx power = 15.0 dBm via
while true; do echo -n '100000 26' > driver/measure && echo "$(cat read_rate) $(cat rssi)"; done;gives readings with greater frequency and the measurement values are more stable which I can tell solely by looking at the numbers in the terminal. I'm comparing this behaviour withwhile true; do echo -n '100000 26' > driver/measure && echo "$(cat read_rate) $(cat rssi)"; done;which corresponds to tx power = 26.0 dBm and thus I'd expect it to measure the tags more reliably than the 15.0 dBm approach, however this is not the case.Why is it so? Could this be caused by some kind of bug in our software, or is it an issue on the r200/m100 / firmware side or related to physical phenomena?