User Tools

Site Tools


eeros_architecture:safety_system:properties

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
eeros_architecture:safety_system:properties [2018/05/15 13:04] – external edit 127.0.0.1eeros_architecture:safety_system:properties [2020/02/11 14:17] – [Safety Events] graf
Line 57: Line 57:
 Each event must be defined **kPublicEvent** or **kPrivateEvent**. Private events can only be fired by the safety system itself whereas public events could also be caused by the //Control System// or the //Sequencer//.\\ Each event must be defined **kPublicEvent** or **kPrivateEvent**. Private events can only be fired by the safety system itself whereas public events could also be caused by the //Control System// or the //Sequencer//.\\
  
-It is also possible to add an event to many levels. In the following example we add from the level //slPowerOn// until the level //slMoving// the event //seDoEmergency//, which causes a transition to the level //emergency// and is a public event.+It is also possible to add an event to many levels. In the following example we add to all levels from //slPowerOn// onwards the event //seDoEmergency//, which causes a transition to the level //emergency// and which is a public event.
 <code c> <code c>
   // Add events to multiple levels   // Add events to multiple levels
-  addEventToLevelAndAbove(slPowerOn, slMoving, seDoEmergency, kPublicEvent);+  addEventToLevelAndAbove(slPowerOn, seDoEmergency, kPublicEvent);
 </code> </code>
 Two more functions serve a similar purpose. Two more functions serve a similar purpose.
eeros_architecture/safety_system/properties.txt · Last modified: 2024/06/10 09:45 by ursgraf