Differences

This shows you the differences between two versions of the page.

--- eeros_architecture:safety_system:start [2016/11/03 17:29] – [Events] graf
+++ eeros_architecture:safety_system:start [2020/02/09 21:17] – [How it works] graf
@@ Line 8: / Line 8: @@
      - has a unique name
      - defines the state of all critical outputs
-     - defines conditions of the critical inputs, which are proofed periodically by an inspection task
+     - defines conditions for the critical inputs, which are checked periodically by an inspection task
-     - can have accept certain events
+     - can accept certain events
      - can cause events
   * The order of the safety level numbering corresponds to the potential damage in case of an error
@@ Line 21: / Line 21: @@
 {{ .:safetysystemevents1.png?300 | //Typical safety levels and associated events//}}
-===== 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.
+===== 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>
@@ Line 42: / Line 45: @@
 If you want to learn more about the individual parts of the safety system, look at the links below:
-  *[[.:hal|HAL (Hardware Abstraction Layer)]]\\
-  *[[.:properties|Safety Properties]] \\
+  *[[.:properties|Safety Properties]]
-  *[[.:io_actions|Input / Output Actions]]\\
+  *[[.:io_actions|Input / Output Actions]]
-  *[[.:usage|Creation]]
+  *[[.:usage|Setup a Safety System]]