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

Factor in reverse pusher delay on mission acceptance radius #7915

Merged
merged 1 commit into from
Sep 13, 2017

Conversation

sanderux
Copy link
Member

@sanderux sanderux commented Sep 5, 2017

When using reverse thrust to brake and setting a reverse thrust delay this should be factored in to the acceptance radius of a vtol_land mission item.

@sanderux
Copy link
Member Author

sanderux commented Sep 9, 2017

test flown, works as expected: https://logs.px4.io/plot_app?log=947c9718-d299-472f-9333-0d5cec440dbc

@dagar
Copy link
Member

dagar commented Sep 10, 2017

This is fine for now, but we should start thinking about a more general pattern for this kind of thing.
Navigator should be agnostic to vehicle specifics. For example FW broadcasts a status message that navigator uses for acceptance radius. It seems like VTOL should be doing the same. If the land detector becomes "vehicle mode" that might be an appropriate home.

@dagar
Copy link
Member

dagar commented Sep 10, 2017

Is any of this interfering with tailsitter or tiltrotor?

@sanderux sanderux merged commit 919b3a2 into master Sep 13, 2017
@sanderux sanderux deleted the pr-vtol-mis-rev-del branch September 13, 2017 15:25
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.

2 participants