User Tools

Site Tools


eeros_architecture:sequencer:exceptions

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
eeros_architecture:sequencer:exceptions [2017/08/20 21:19] – [Sequence Supervised by more than one Monitor] grafeeros_architecture:sequencer:exceptions [2017/08/23 13:56] – [Sequence Supervised by Monitor] graf
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//}}] [{{ .: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: 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 The following table shows the behavior for various situations
 ^Property^behavior of sequence after monitor fires^exception sequence if present^ ^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 ===== ===== Sequence Supervised by more than one Monitor =====
eeros_architecture/sequencer/exceptions.txt · Last modified: 2017/09/24 11:39 by 127.0.0.1