Differences

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

--- getting_started:practical_problems:faults_cs [2017/09/24 16:30] – created graf
+++ getting_started:practical_problems:faults_cs [2018/05/31 14:51] (current) – graf
@@ Line 1: / Line 1: @@
 ===== Handle Faults in the Control System =====
-input not connected, forget to connect
+When a time domain runs, it can encounter two main obstacles. It could try to read from an unconnected input or it could try to write the value of ''nan'' to an output. If either of this happens a fault is thrown. Such a fault will cause the application to stop unless it is properly handled in the control system, e.g. by changing into a safe level, see [[eeros_architecture:control_system:time_domains|]]. \\ \\
-nan
-initial signals = nan, forget to addBlock
+The root cause for these faults is
-remove block
+  - input not connected: forget to connect the input
+  - write nan to output: all signals are initialized to ''nan'', If a block never runs (probably forgot to add to time domain, or time domain never runs) its output signals will stay at ''nan''.