Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiranger deck gives odd values when out of range #874

Closed
krichardsson opened this issue Oct 13, 2021 · 2 comments · Fixed by #1088
Closed

Multiranger deck gives odd values when out of range #874

krichardsson opened this issue Oct 13, 2021 · 2 comments · Fixed by #1088
Labels

Comments

@krichardsson
Copy link
Contributor

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).

@rafaelrgb
Copy link

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.

crazyflie_range

@krichardsson
Copy link
Contributor Author

Thanks for your input @rafaelrgb
This is also what I have observed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants