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

RangeFinder: enhance mavlink driver to use RNGFNDx_ADDR field #28837

Open
rmackay9 opened this issue Dec 11, 2024 · 0 comments
Open

RangeFinder: enhance mavlink driver to use RNGFNDx_ADDR field #28837

rmackay9 opened this issue Dec 11, 2024 · 0 comments

Comments

@rmackay9
Copy link
Contributor

The AP_RangeFinder_MAVLink backend uses the DISTANCE_SENSOR message's orientation field to map to the RNGFNDx_ORIENT parameter (see code here)

We should consider enhancing this condition so that if the user has set the RNGFNDx_ADDR field (defaults to -1) then this is compared against the DISTANCE_SENSOR.id field. This would allow more than one distance sensor in each direction to be used.

This request comes from this wiki discussion

@rmackay9 rmackay9 changed the title RangeFinder: enhance mavlink driver to use RangeFinder: enhance mavlink driver to use RNGFNDx_ADDR field Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant