User Tools

Site Tools


eeros_architecture:practical_problems:start

This is an old revision of the document!


Practical Problems

Every EEROS system consists of a control system, a safety system, and a sequencer. In order to guarantee maximum stability we strongly recommend that you adhere to a strict set of design rules as given below.

Trigger Safety Event from Control System

signale aus dem cs sollen se bewirken (signal checker).
Seq soll signale in CS setzen (const) oder lesen

Avoid Hidden States in the Safety System

It might be tempting to define elaborate actions in a certain safety level. However, in order to keep the safety system clean and simple avoid such practises. Do not define different states in a safety level. If you need to stay a certain amount of time in a safety level use the field nofActivations as described in counter. As soon as you want to model a more complex behaviour use a Sequence.

Handle Faults in the Control System

input not connected, forget to connect nan initial signals = nan, forget to addBlock remove block

Block with Parameters

Situation: inner states of blocks can be changed only through signals or getter / setter methods. How to implement a slowly changing inertia matrix? You do not want to calculate this matrix out of regular signals with full speed. Solution: use slow time domain for this purpose and change …

eeros_architecture/practical_problems/start.1490198092.txt.gz · Last modified: 2017/03/22 16:54 by graf