You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have also seen odd behavior when the multiranger sensors are out of range. A user probably expects some know value (or other mechanism) to be able to distinguish out of range from real distance measurements.
I think the Z-ranger behaves differently and reports a fixed distance when out of range. The sensor has a wide range of configurations and the Z-ranger is not set up in the same way as the multi ranger (short-range VS long-range).
The text was updated successfully, but these errors were encountered:
We are also seeing strange behavior when the multiranger is out of range. Here is an experiment I made, where I moved the crazyflie from one wall (left sensor - green line) to the other (right sensor - blue line). The left sensor starts at a small value and increases as I move away from the wall. When I reach the maximum range (around 395 on the horizontal axis) there is a high increase in the noise and then the sensor starts to report a short range, which increases as I keep moving farther and farther. This behavior is mirrored by the opossite sensor.
Reported in https://forum.bitcraze.io/viewtopic.php?f=6&t=5086
We have also seen odd behavior when the multiranger sensors are out of range. A user probably expects some know value (or other mechanism) to be able to distinguish out of range from real distance measurements.
I think the Z-ranger behaves differently and reports a fixed distance when out of range. The sensor has a wide range of configurations and the Z-ranger is not set up in the same way as the multi ranger (short-range VS long-range).
The text was updated successfully, but these errors were encountered: