-
Notifications
You must be signed in to change notification settings - Fork 46
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
Failsafe auto flight termination #132
Comments
I think the cleanest way to do this is to publish a The other change necessary is that we need to allow offboard control to be processed even if RC is lost. @dpkoch, do you have any thoughts? |
I just added a status message which is published by As of right now, we default to RC. However, we could allow onboard computer commands to be executed even in the absence of RC. This should be supported by the |
The latest |
awesome. I will work on handling this message in ROSPlane |
When you get around to testing this, I can show you a quick hack that tricks ROSflight into thinking it's lost RC when you flip a switch. |
We should just make this a parameter so it can be turned on, but by default is turned off. |
Failsafe behavior is something we'd like to revisit, so I'll leave this open. |
For fixed wing ideally we would like flight termination to be: throttle closed, full up elevator,
full right rudder, full right or left aileron.
It would be nice to have different levels of fail safe, i.e. after 30 seconds of communications loss, the aircraft automatically Returns to Home or Returns To Land. After 3 minutes of communication loss, the aircraft terminates flight.
Also would be ideal if RTH/RTL and flight termination were activatable by the safety pilot and ground station.
(These are our requirements for AUVSI)
The text was updated successfully, but these errors were encountered: