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

MAV_CMD_DO_SET_CAM_TRIGG_DIST.trigger=1 Support #13779

Closed
Saijin-Naib opened this issue Mar 10, 2020 · 4 comments · Fixed by #13791
Closed

MAV_CMD_DO_SET_CAM_TRIGG_DIST.trigger=1 Support #13779

Saijin-Naib opened this issue Mar 10, 2020 · 4 comments · Fixed by #13791

Comments

@Saijin-Naib
Copy link

https://discuss.ardupilot.org/t/3dr-solo-compatibility/53216/15?u=saijin_naib

For example support for MAV_CMD_DO_SET_CAM_TRIGG_DIST.trigger=1, which allows you to start distance based triggering with an initial image triggered right away. This allows you to catch the image right at survey edge entry.

@DonLakeFlyer
Copy link
Contributor

The trigger is on param3

@MattKear
Copy link
Contributor

I have used param3 in the pr. The packet was already definied in the mavlink message. All I have done is added support for it in ArduPilot

@DonLakeFlyer
Copy link
Contributor

Yup, thanks for adding this. So far test results with QGC and other firmwares are showing the combination of these two are working to provide higher quality survey coverage without needing to over cover the area.

@Saijin-Naib
Copy link
Author

Yup, thanks for adding this. So far test results with QGC and other firmwares are showing the combination of these two are working to provide higher quality survey coverage without needing to over cover the area.

This is so crucial, especially in suburban environments when there are lots of concerns over privacy, access, safety, etc. Not having to grossly overfly is so wonderful.

@MattKear MattKear linked a pull request Mar 17, 2020 that will close this issue
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 a pull request may close this issue.

3 participants