eeros_architecture:safety_system:start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
eeros_architecture:safety_system:start [2016/11/05 07:46] – [Key Features of a Safety Level] graf | eeros_architecture:safety_system:start [2023/02/26 17:59] (current) – [How it works] ursgraf | ||
---|---|---|---|
Line 21: | Line 21: | ||
{{ .: | {{ .: | ||
- | ===== What does it do? ===== | + | * If the safety system itself causes an event leading to a change of the safety level, this level change takes place only after the safety system completes this run. |
+ | * Multiple events fired during a single safety period would lead to ambiguities. The event leading to a lower prioritized safety level wins, while the other events are cancelled. | ||
+ | |||
+ | ===== What does the Safety System | ||
The most important function of the safety system is its run method. This method is called periodically by the executor. Here's how it works: | The most important function of the safety system is its run method. This method is called periodically by the executor. Here's how it works: | ||
<code cpp> | <code cpp> | ||
Line 42: | Line 45: | ||
If you want to learn more about the individual parts of the safety system, look at the links below: | If you want to learn more about the individual parts of the safety system, look at the links below: | ||
- | *[[.: | + | |
- | *[[.: | + | *[[.: |
- | *[[.: | + | *[[.: |
*[[.: | *[[.: | ||
+ |
eeros_architecture/safety_system/start.1478328391.txt.gz · Last modified: 2016/11/05 07:46 (external edit)