-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
How to handle custom flight tasks? #10235
Comments
One idea was to leave room in the state machine for custom classes of nav state.
These buckets would allow you to do anything you want within with the same control mode flags, but ensure consistent failsafe handling. #10237 is a good example of why this decentralized handling is potentially a bad idea. We need to have this logic handled by well defined state machines, but that doesn't mean all within commander. |
Conveying the mode to the ground is another problem. |
Could be a short term option
I think the current situation is a good example of why the commander should not have everything predefined. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Closing as stale. |
There should be a possibility to add a custom flight task (and launch it) without much effort or creating a large diff and conflicts.
Our long term goal is to move the logic if a task can run/be activated to the actual flight task because we think the current situation with commander knowing everything doesn't scale.
Approaches
The text was updated successfully, but these errors were encountered: