eeros_architecture:sequencer:exceptions
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
eeros_architecture:sequencer:exceptions [2017/08/19 11:53] – [Sequence Supervised by Monitor] graf | eeros_architecture:sequencer:exceptions [2017/08/20 20:42] – [Sequence Supervised by more than one Monitor] graf | ||
---|---|---|---|
Line 11: | Line 11: | ||
* abortCallerOfOwner: | * abortCallerOfOwner: | ||
* restartCallerOfOwner: | * restartCallerOfOwner: | ||
+ | |||
+ | 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| | ||
+ | |abortOwner|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| | ||
+ | |||
+ | ===== Sequence Supervised by more than one Monitor ===== | ||
+ | A sequence can be checked by more than one monitor where each monitor checks for a certain condition to be met. While a first monitor could check for a timeout condition a second could supervise whether a payload of a robot didn't get lost. | ||
+ | [{{ .: | ||
eeros_architecture/sequencer/exceptions.txt · Last modified: 2017/09/24 11:39 by 127.0.0.1