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/08/20 21:27] – [Define your own Condition] graf | eeros_architecture:sequencer:monitors [2021/10/20 16:07] (current) – [Define your own Condition] ursgraf | ||
---|---|---|---|
Line 16: | Line 16: | ||
}; | }; | ||
</ | </ | ||
- | ===== Assign a Condition | + | The method // |
+ | 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 ===== | ||
+ | The second step is to define a monitor and assign it a condition. | ||
+ | <code cpp> | ||
+ | SequenceA seq(...); | ||
+ | MyCondition myCondition; | ||
+ | Monitor myMonitor(" | ||
+ | setExceptionSequence(exceptionSeq); | ||
+ | seq.addMonitor(& | ||
+ | </ | ||
+ | IMPORTANT Here again, every sequence or step already has a timeout monitor which helps to check its associated timeout condition. A second monitor checks the abort condition. |
eeros_architecture/sequencer/monitors.1503257262.txt.gz · Last modified: 2017/08/20 21:27 by graf