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

Failsafe auto flight termination #132

Open
mmmfarrell opened this issue Mar 31, 2017 · 7 comments
Open

Failsafe auto flight termination #132

mmmfarrell opened this issue Mar 31, 2017 · 7 comments
Assignees

Comments

@mmmfarrell
Copy link
Contributor

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)

@superjax
Copy link
Contributor

superjax commented Apr 3, 2017

I think the cleanest way to do this is to publish a status message from fcu_io. This could include things like whether or not the safety pilot is in control, we are in failsafe, loop time, armed/disarmed, etc... I think that the RTH/RTL and flight termination should probably occur within ros_plane.

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?

superjax added a commit that referenced this issue Apr 6, 2017
@superjax
Copy link
Contributor

superjax commented Apr 6, 2017

I just added a status message which is published by fcu_io. This includes a flag of whether or not the flight controller is in failsafe mode. You'll have to watch this flag and act appropriately to fulfill your requirements.

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 status branches of fcu_io and fcu_common and the status_message branch of ROSflight. That is, until we merge into RC1.0

@superjax
Copy link
Contributor

superjax commented Apr 7, 2017

The latest status_message branch should allow for onboard commands to be accepted even if RC is lost.

@mmmfarrell
Copy link
Contributor Author

awesome. I will work on handling this message in ROSPlane

@superjax
Copy link
Contributor

superjax commented Apr 7, 2017

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.

This was referenced Apr 21, 2017
superjax added a commit that referenced this issue May 2, 2017
superjax added a commit that referenced this issue May 3, 2017
@superjax superjax modified the milestone: v1.2 Aug 11, 2017
@superjax
Copy link
Contributor

superjax commented Oct 3, 2017

We should just make this a parameter so it can be turned on, but by default is turned off.

@bsutherland333
Copy link
Contributor

Failsafe behavior is something we'd like to revisit, so I'll leave this open.

@bsutherland333 bsutherland333 removed this from the v1.2 milestone Oct 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

4 participants