Differences

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

--- eeros_architecture:sequencer:exceptions [2017/08/20 21:19] – [Sequence Supervised by more than one Monitor] graf
+++ eeros_architecture:sequencer:exceptions [2017/09/24 11:39] (current) – external edit 127.0.0.1
@@ Line 6: / Line 6: @@
 [{{ .:sequencemonitorcase1.png?500 | //Monitor checks condition and causes a switch to an exception sequence after which the original sequence is restarted//}}]
 As soon as a monitor checking for a certain condition fires, an exception sequence is called. The exception must always be blocking. However, it would be possible to omit it altogether. After this the control goes back to the original sequence. How does this sequence now continue? Every monitor can be assigned one of the following properties:
-  * nothing: the sequence continues normally
+  * resume: the sequence continues normally
-  * abortOwner: the sequence is aborted and control goes back to its calling sequence
+  * abort: the sequence is aborted and control goes back to its calling sequence
-  * restartOwner: the sequence gets restarted, its timeout monitor is reset (that's the situation shown in the figure above)
+  * restart: the sequence gets restarted, its timeout monitor is reset (that's the situation shown in the figure above)
-  * abortCallerOfOwner: TODO
-  * restartCallerOfOwner: TODO
 The following table shows the behavior for various situations
 ^Property^behavior of sequence after monitor fires^exception sequence if present^
-|nothing|sequence continues normally|exception sequence will run for each further step|
+|resume|sequence continues normally|exception sequence will run for each further step|
-|abortOwner|remaining steps aborted|exception sequence will run once|
+|abort|remaining steps aborted|exception sequence will run once|
-|restartOwner|remaining steps aborted, sequence restarts with first step|exception sequence will run once, after restarting will run again if monitor fires again|
+|restart|remaining steps aborted, sequence restarts with first step|exception sequence will run once, after restarting will run again if monitor fires again|
 ===== Sequence Supervised by more than one Monitor =====
@@ Line 22: / Line 20: @@
 [{{ .:sequencemonitorcase2.png?500 | //Two monitors checking the same sequence. While monitor 1 causes the sequence to abort, the second restarts the sequence in case of a condition to be met.//}}]
 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).