60
edits
Failure Manager: Difference between revisions
Jump to navigation
Jump to search
→Implementation Details
| Line 59: | Line 59: | ||
== Implementation Details == | == Implementation Details == | ||
The current prototype | The current prototype includes three components: | ||
* A Failure Manager Nasal submodule. | * A Failure Manager Nasal submodule. | ||
| Line 73: | Line 73: | ||
;Trigger: A Trigger represents a condition that makes a given failure mode become active. The current prototype supports the following types: altitude, waytpoint proximity, timeout, MTBF (mean time between failures), MCBF (mean cycles between failures). More can be implemented by extending the FailureMgr.Trigger Nasal interface. | ;Trigger: A Trigger represents a condition that makes a given failure mode become active. The current prototype supports the following types: altitude, waytpoint proximity, timeout, MTBF (mean time between failures), MCBF (mean cycles between failures). More can be implemented by extending the FailureMgr.Trigger Nasal interface. | ||
;FailureMgr: The Failure Manager itself. Keeps a list of supported failure modes that can be added or removed dynamically. It also keeps a list of triggers associated to each mode. While running, it keeps an eye on triggers, and fires the relevant failure modes through their actuators. | ;FailureMgr: The Failure Manager itself. Keeps a list of supported failure modes that can be added or removed dynamically. It also keeps a list of triggers associated to each mode. While running, it keeps an eye on triggers, and fires the relevant failure modes through their actuators. The FailureMgr can be enabled and disabled on command. | ||
== Roadmap == | == Roadmap == | ||