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

VTOL front transition direction #12455

Closed
RomanBapst opened this issue Jul 10, 2019 · 1 comment
Closed

VTOL front transition direction #12455

RomanBapst opened this issue Jul 10, 2019 · 1 comment

Comments

@RomanBapst
Copy link
Contributor

Currently the user has two possibilities to plan a front transition:

  1. Use VTOL Takeoff waypoint: This is a combined takeoff and transition waypoint. The vehicle can transition in arbitrary directions, e.g. it does not align with the next waypoint. The idea is to use this type of waypoint with the weathervane feature such that the vehicle will automatically turn and transition into the wind.

  2. Use dedicated transition waypoint. In this case the vehicle transitions into the direction of the next waypoint. The target heading is enforced before a transition can commence.

Issue:

  • if you enable weathervane using option 2) and the wind direction is not aligned with the next waypoint then the transition will never occur as the vehicle does not even attempt to turn towards the traget heading (due to weathervane active).
  • if the user uses option 1) he should be able to specify whether he wants the vehicle to align with the direction of the next waypoint after reaching transition altitude.
  • if enforcing a transition heading then a strategy needs to be implemented how the vehicle can try (for a certain amount of time) to achieve the target heading. If it cannot be achieved the transition should be aborted.
@sfuhrer
Copy link
Contributor

sfuhrer commented Oct 1, 2019

closing, as mostly solved with #12630

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants