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

Always depart loiter WP towards next WP #3694

Closed
wants to merge 3 commits into from

Conversation

magicrub
Copy link
Contributor

@magicrub magicrub commented Mar 1, 2016

This is only helpful for plane but available for all. When exiting a liter_turns, loiter_alt, or loiter_time there is now an optional cmd param field of heading required where when set to 1 yo must be +/- 10deg of the next waypoint before you are allowed to exit the loiter.

There needs to be a GCS change to added the bool label field 3 for loiter time/turns.

This fixes #1906

@magicrub
Copy link
Contributor Author

magicrub commented Mar 1, 2016

The bool flag is 1 for checking for heading, so you must enable it via param. I'm wondering if we should invert that so you have to set the flag to ignore heading and by default (0) it checks the heading.

@iskess
Copy link

iskess commented Mar 1, 2016

I'm in favor of the heading alignment being default behavior as I feel this is what most operators would expect.

@magicrub
Copy link
Contributor Author

magicrub commented Mar 2, 2016

I've removed the bool flag and now this behavior will be default so no GCS change is needed

@magicrub
Copy link
Contributor Author

magicrub commented Mar 2, 2016

merged be3941e

@magicrub magicrub closed this Mar 2, 2016
@magicrub magicrub deleted the master_loiter_header_req branch June 24, 2016 17:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Plane: Always departs loiter WP towards next WP
2 participants