eeros_architecture:control_system:time_domains
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
eeros_architecture:control_system:time_domains [2017/03/21 13:00] – [Time domains] graf | eeros_architecture:control_system:time_domains [2017/04/07 12:43] – [Time domains] graf | ||
---|---|---|---|
Line 13: | Line 13: | ||
</ | </ | ||
Finally, you have to add the time domain to the executor, refer to [[eeros_architecture: | Finally, you have to add the time domain to the executor, refer to [[eeros_architecture: | ||
+ | If a block no longer has to run - this could be the case for blocks used solely for initializing - it can be removed with | ||
+ | <code cpp> | ||
+ | td.removeBlock(const1); | ||
+ | </ | ||
+ | |||
===== Time Stamps ===== | ===== Time Stamps ===== | ||
Each signals' | Each signals' | ||
Line 24: | Line 29: | ||
===== Catching Faults in Time Domains ===== | ===== Catching Faults in Time Domains ===== | ||
- | Time domains are responsible to run their blocks in a predetermined way. However, if a block fails to run properly due to a fault within this block the time domain must catch this fault and be able to trigger a safety event. In order to do this you can create | + | Time domains are responsible to run their blocks in a predetermined way. However, if a block fails to run properly due to a fault within this block the time domain must catch this fault and be able to trigger a safety event. In order to do this you can assign |
<code cpp> | <code cpp> | ||
- | | + | td.registerSafetyEvent(& |
</ | </ | ||
The safety system will change to a safe level for this condition and might stop the time domain with | The safety system will change to a safe level for this condition and might stop the time domain with |
eeros_architecture/control_system/time_domains.txt · Last modified: 2021/05/16 15:27 by ursgraf