User Tools

Site Tools


eeros_architecture:sequencer:monitors

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
eeros_architecture:sequencer:monitors [2019/03/28 13:22] – [Define your own Condition] grafeeros_architecture:sequencer:monitors [2021/10/20 16:07] (current) – [Define your own Condition] ursgraf
Line 19: Line 19:
  
 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 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 ===== ===== 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.
eeros_architecture/sequencer/monitors.1553775750.txt.gz · Last modified: 2019/03/28 13:22 by graf