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

AP_Mission: Add support for DO_SET_CAM_TRIGG_DIST #13791

Merged
merged 2 commits into from
Mar 30, 2020

Conversation

MattKear
Copy link
Contributor

This PR adds support for the trigger parameter already available as the 3rd packet in DO_SET_CAM_TRIGG_DIST.

Now, if the packet 3 of DO_SET_CAM_TRIGG_DIST is set to 1, it will trigger the camera once, immediately upon recieving the command. This is oppose to the current behaviour in which the first image is taken after the predefined distance has been covered.

This addresses the feature request raised in #13779

Tested in SITL.

@MattKear
Copy link
Contributor Author

Behaviour before this PR was always:
Cam_trigger_before

This PR now gives the option to have this behaviour:
Cam_trigger_after

@tridge
Copy link
Contributor

tridge commented Mar 23, 2020

better to trigger immediately and avoid the extra var

@MattKear
Copy link
Contributor Author

Simplified this PR as requested/suggested.

@tridge tridge merged commit c97cc71 into ArduPilot:master Mar 30, 2020
@MattKear MattKear deleted the support_cam_dist.trigger branch March 30, 2020 23:07
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 this pull request may close these issues.

MAV_CMD_DO_SET_CAM_TRIGG_DIST.trigger=1 Support
3 participants