eeros_architecture:sequencer:exceptions
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
eeros_architecture:sequencer:exceptions [2017/08/23 13:56] – [Sequence Supervised by Monitor] graf | eeros_architecture:sequencer:exceptions [2017/09/24 11:39] – [Monitor for Exception Sequence] graf | ||
---|---|---|---|
Line 20: | Line 20: | ||
[{{ .: | [{{ .: | ||
Please note, that each monitor can have a different effect on its associated sequence. While one monitor can cause the sequence to abort further steps another can restart the sequence upon firing an exception. Further, one of the monitor can cause an exception sequence to run while another does not do so. | Please note, that each monitor can have a different effect on its associated sequence. While one monitor can cause the sequence to abort further steps another can restart the sequence upon firing an exception. Further, one of the monitor can cause an exception sequence to run while another does not do so. | ||
+ | |||
+ | ===== Monitor for Exception Sequence ===== | ||
+ | Exception sequences are used to handle situations where regular sequences do not work due to certain conditions. Besides this, an exception sequence is a normal sequences with exactly the same features and has to be defined in the same way. Therefore, an exception sequence has the same built-in conditions and monitors as a regular sequence (timeout and abort conditions). | ||
+ |
eeros_architecture/sequencer/exceptions.txt · Last modified: 2017/09/24 11:39 by 127.0.0.1