Differences

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

--- getting_started:tutorials:sequencer4 [2020/12/03 19:47] – [Monitor Checking two Sequences] ursgraf
+++ getting_started:tutorials:sequencer4 [2021/03/31 15:40] (current) – [Monitor Checking two Sequences] ursgraf
@@ Line 3: / Line 3: @@
 ====== Sequence with two Monitors ======
-In the EEROS library you will find a directory with examples. Open a shell in the build directory of your EEROS library and run
+In the EEROS library you will find a directory with examples. For this example see [[https://github.com/eeros-project/eeros-framework/blob/master/examples/sequencer/SequencerTest40.cpp|SequencerTest40.cpp]].
+Open a shell in the build directory of your EEROS library and run
 <code>
 $ ./examples/sequencer/sequencerTest40
@@ Line 9: / Line 11: @@
 This example shows a sequence with two associated monitors. The ''Main Sequence'' tries to run several steps called ''Step A''. After each step a counter is incremented. A monitor checks for this count to reach a given level (''MyMonitor''). As soon as this happens an exception sequence is started. After termination of the exception sequence the original sequence resumes because the monitor property is set to ''resume''. The ''Main Sequence'' continues and is soon interrupted by its timeout monitor because its timeout limit has expired. The timeout monitor has no exception sequence assigned to it and immediately aborts the ''Main Sequence'' and with it the application because its monitor property is set to //abort//.
-[{{ .:sequencerexample4.png?450 | //Flow of SequencerTest4// }}]
+[{{ .:sequencerexample4.png?450 | //Two monitors checking the same sequence// }}]
 \\
@@ Line 19: / Line 21: @@
 ===== Monitor Checking two Sequences =====
+The next example is [[https://github.com/eeros-project/eeros-framework/blob/master/examples/sequencer/SequencerTest41.cpp|SequencerTest41.cpp]].
 Open a shell in the build directory of your EEROS library and run
 <code>
@@ Line 24: / Line 27: @@
 </code>
-This example shows a sequence with two associated monitors. The ''Main Sequence'' tries to run several steps called ''Step A''. After each step a counter is incremented. A monitor checks for this count to reach a given level (''MyMonitor''). As soon as this happens an exception sequence is started. After termination of the exception sequence the original sequence resumes because the monitor property is set to ''resume''. The ''Main Sequence'' continues and is soon interrupted by its timeout monitor because its timeout limit has expired. The timeout monitor has no exception sequence assigned to it and immediately aborts the ''Main Sequence'' and with it the application because its monitor property is set to //abort//.
+This example shows a sequence with two associated monitors. The ''Main Sequence'' tries to run several steps called ''Step A''. After each step a counter is incremented. A monitor checks for this count to reach a given level (''MyMonitor''). As soon as this happens an exception sequence is started. After termination of the exception sequence the original sequence resumes because the monitor property is set to ''resume''. The ''Main Sequence'' continues and is soon interrupted by its timeout monitor because its timeout limit has expired. The timeout monitor also has an exception sequence assigned to it. After this the sequence continues because its monitor behavior is set to //resume// as well. Both monitors will fire again as their conditions are met again before the sequence finally terminates
-[{{ .:sequencerexample4.png?450 | //Flow of SequencerTest4// }}]
+[{{ .:sequencerexample5.png?450 | //Two monitors with two exception sequences// }}]
 \\