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_Misison: take location in landing sequence functions, copter passes stopping point. #26633

Merged
merged 5 commits into from
Apr 2, 2024

Conversation

IamPete1
Copy link
Member

Extract from #26383, this reworks to pass a location into the various landing mission methods. This is important for copter which may be closer to point A at the current time, but is going fast, so once it has stopped to head to A would have been better to head to point B.

Unfortunately there are scripting bindings for the jump_to_landing_sequence and jump_to_abort_landing_sequence so it would be a breaking change, this adds helpers in mission to fill in the location. We could also:

  • Decide were OK with the scripting breaking change (the functions are not used in any of our examples or applets).
  • Add custom bindings to make the location optional for scripting such that it gets the new functionality without breaking current uses.

Copy link
Contributor

@rmackay9 rmackay9 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm happy with the Copter changes. I'm not qualified re the Plane changes of course.

@tridge tridge merged commit afe257a into ArduPilot:master Apr 2, 2024
91 checks passed
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.

4 participants