eeros_architecture:sequencer:monitors
                Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| eeros_architecture:sequencer:monitors [2017/09/13 17:36] – [Define your own Condition] graf | eeros_architecture:sequencer:monitors [2021/10/20 16:07] (current) – [Define your own Condition] ursgraf | ||
|---|---|---|---|
| Line 16: | Line 16: | ||
| }; | }; | ||
| </ | </ | ||
| + | The method // | ||
| + | |||
| IMPORTANT Every Sequence or step already has a timeout condition (of class '' | IMPORTANT Every Sequence or step already has a timeout condition (of class '' | ||
| + | |||
| + | IMPORTANT Make sure that your condition is properly set and reset. To give an example: A condition might be the state of a button. As soon as the button is pressed, the condition might return '' | ||
| ===== Assign a Condition to a Monitor ===== | ===== Assign a Condition to a Monitor ===== | ||
| The second step is to define a monitor and assign it a condition. | The second step is to define a monitor and assign it a condition. | ||
| <code cpp> | <code cpp> | ||
| - |  | + | SequenceA seq(...); | 
| - | MyCondition myCondition; | + | MyCondition myCondition; | 
| - | Monitor myMonitor(& | + | Monitor myMonitor(" | 
| - | setExceptionSequence(exceptionSeq); | + | setExceptionSequence(exceptionSeq); | 
| - | seq.addMonitor(& | + | seq.addMonitor(& | 
| - | }; | + | |
| </ | </ | ||
| - | IMPORTANT Here again, every sequence or step already has a timeout monitor which helps to check its associated timeout condition. | + | IMPORTANT Here again, every sequence or step already has a timeout monitor which helps to check its associated timeout | 
eeros_architecture/sequencer/monitors.1505316992.txt.gz · Last modified: 2017/09/13 17:36 by graf
                
                