Skip to content
This repository has been archived by the owner on Aug 2, 2021. It is now read-only.

Failsafe Implementations #35

Open
chrishajduk84 opened this issue Jul 11, 2015 · 3 comments
Open

Failsafe Implementations #35

chrishajduk84 opened this issue Jul 11, 2015 · 3 comments
Milestone

Comments

@chrishajduk84
Copy link
Contributor

At competition we put in "last minute fail-safe" conditions. They were poorly implemented, but they did the job.

We want something more robust. This will involve checking GPS signals, datalink signals, RC controller signals and determining the required actions.

If we lose all 3 signals, kill within 5 seconds. Chances are it is already dead.

If we lose datalink and GPS, kill within 10 seconds. The ground station should notify in case of a datalink loss.
If we lose datalink and RC control, kill within 10 seconds. The ground station should notify in case of a datalink loss.
If we lose GPS and RC control, notify the ground station. Attempt to fly home using magnetometers.

If we lose RC Control, notify ground station. Appropriate action should be taken.
If we lose datalink, head home within 5 seconds. If a signal is not re-established within 2 minutes, kill the vehicle.
If we lose GPS, notify ground station. Use magnetometers to head home. Keep the vehicle at a constant altitude/or level.

@ianjfrosst
Copy link
Contributor

I'm thinking a number of system status flags are a good way to do this. Overhaul the various status and diagnostic indicators, and have one place for sensor status, etc.

@CoatedMoose
Copy link
Contributor

-1 should be implemented 10 min before safety inspection on flight day, with no testing.

@chrishajduk84
Copy link
Contributor Author

Sounds about right.

@ianjfrosst ianjfrosst added this to the Comp 2017 milestone Mar 3, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants