Differences

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

--- eeros_architecture:sequencer:monitors [2017/09/13 17:38] – external edit 127.0.0.1
+++ eeros_architecture:sequencer:monitors [2021/10/20 16:07] (current) – [Define your own Condition] ursgraf
@@ Line 16: / Line 16: @@
 };
 </code>
+The method //validate// must return ''true'' in order for the monitor checking this condition to fire.
 IMPORTANT Every Sequence or step already has a timeout condition (of class ''ConditionTimeout''). It allows for checking a maximum duration of execution. Also, every sequence has an abort condition (of class ''ConditionAbort''). This condition makes it possible to abort a sequence, e.g. by pressing ''Ctrl-C''.
+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 ''true'' and the associated monitor fires. This might lead to an abortion of the current sequence together with all its blocking subsequences. This might take some time. You have to make sure that the condition delivers ''true'' until this work is done. If the condition is simply the state of the button this might be too short, if you press only for a short time.
 ===== Assign a Condition to a Monitor =====
 The second step is to define a monitor and assign it a condition.