Skip to content

AP_OpticalFlow: Use flow rates and add ground distance field in MAVLink driver #29355

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

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

snktshrma
Copy link
Contributor

@snktshrma snktshrma commented Feb 22, 2025

Closes #29131 #30019 . Updated OpticalFlow MAVLink driver for improved accuracy:

  • Replaced flow_x and flow_y (int16_t) with flow_rate_x and flow_rate_y (float) to enhance accuracy.
  • Added ground_distance field to transmit ground distance over MAVLink when available.

Edit:

  • Added EK3_FLOW_HGT_SRC param to select between Optical flow's ground distance (currently only mavlink and/or) or default.

@rmackay9
Copy link
Contributor

rmackay9 commented Jun 9, 2025

Hi @snktshrma,

We're still interested in this PR by the way. I'd like to try implementing optical flow using a downward facing camera gimbal.

@snktshrma
Copy link
Contributor Author

Hi @rmackay9 sir! Yes I am sorting the failing tests and will push the final updates to be merged asap and will try to add an example for optical flow through gimbal as well

@snktshrma snktshrma force-pushed the dev/flow_mav branch 8 times, most recently from 5d245bf to 88d6644 Compare June 20, 2025 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AP_OpticalFlow: mavlink driver should consume OPTICAL_FLOW message's flow_rate_x, flow_rate_y
2 participants