eeros_architecture:practical_problems:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| eeros_architecture:practical_problems:start [2017/03/21 16:49] – [Trigger Safety Event from Control System] graf | eeros_architecture:practical_problems:start [2017/09/24 15:39] (current) – removed graf | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== 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 \\ | ||
| - | 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.1490111381.txt.gz · Last modified: 2017/03/21 16:49 (external edit)