Differences

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

--- getting_started:practical_problems:faults_cs [2018/05/31 14:48] – graf
+++ getting_started:practical_problems:faults_cs [2018/05/31 14:51] (current) – graf
@@ Line 1: / Line 1: @@
 ===== Handle Faults in the Control System =====
-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|]].
+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|]]. \\ \\
-sinput not connected, forget to connect
+The root cause for these faults is
-nan
+  - input not connected: forget to connect the input
-initial signals = nan, forget to addBlock
+  - 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''.
-remove block