User Tools

Site Tools


getting_started:tutorials:safetysystem2

Differences

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

Link to this comparison view

Next revision
Previous revision
Next revisionBoth sides next revision
getting_started:tutorials:safetysystem2 [2017/02/27 15:49] – created grafgetting_started:tutorials:safetysystem2 [2017/02/27 16:13] graf
Line 2: Line 2:
  
 In the EEROS library you will find a directory with examples. Open a shell in the build directory of your EEROS library and run ''examples/safety/SafetySystemTest2''. \\ In the EEROS library you will find a directory with examples. Open a shell in the build directory of your EEROS library and run ''examples/safety/SafetySystemTest2''. \\
-The example comprises a safety system with only two safety levels and two safety events. +The example comprises a safety system with only two safety levels and two safety events. The system will start in the safety level ''slStart''. It will stay there for three seconds after which a safety event is triggered which causes a level change to ''slRampingUp''. The control system for this example consists of three block as show below: (insert figure here). 
 +When the system changes into ''slRampingUp'' the integrator is enabled. The output of the integrator starts to ramp up.
 The levels and events are defined in the safety properties. The properties further include one critical input and one critical output. The levels and events are defined in the safety properties. The properties further include one critical input and one critical output.
  
Line 18: Line 19:
   * To start and stop running might be triggered by pressing or releasing a button connected to the critical input. In our simple example we do not have real hardware. Hence we simply start and never stop, because the state of the hypothetical input is always ''true''   * To start and stop running might be triggered by pressing or releasing a button connected to the critical input. In our simple example we do not have real hardware. Hence we simply start and never stop, because the state of the hypothetical input is always ''true''
   * When pressing ''Ctrl-C'' the system falls into level ''slShuttingDown''. A level action for this safety level causes the system to automatically switch to level ''slOff'' which then terminates the program. Here again, this would be signalled by the sequencer after a shutting down sequence has finished or by the control system as soon as a certain safe condition is reached.   * When pressing ''Ctrl-C'' the system falls into level ''slShuttingDown''. A level action for this safety level causes the system to automatically switch to level ''slOff'' which then terminates the program. Here again, this would be signalled by the sequencer after a shutting down sequence has finished or by the control system as soon as a certain safe condition is reached.
-===== How to shut down ===== 
-The example demonstrates how the system should be stopped in a well controlled manner, see [[getting_started:tutorials:stoppingsystem|]]. 
- 
- 
-