Real-Time Robotics Framework

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Example with Nonblocking Sequence ======
The following example all have a main sequence which calls a few steps and a another sequence. This second sequence is a nonblocking sequence. That means that the main sequence runs in parallel to the second sequence. A timeout monitor either supervises the main sequence or the second sequence.

===== Main Sequence Calls Nonblocking Sequence =====

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/SequencerTest30.cpp|SequencerTest30.cpp]].

Open a shell in the build directory of your EEROS library and run 
<code>
$ ./examples/sequencer/sequencerTest30
</code>
The main sequences starts with three ''Step A'' after which the ''Sequence B'' is called. ''Sequence B'' is nonblocking, that means both sequences run in parallel. The main sequence will do three more ''Step A'' before finishing.
[{{ :getting_started:tutorials:sequencetest30.png?250 | //Calling a nonblocking sequence// }}]
\\
Please note the method //action// of the main sequence.
<code cpp>
  int action() {
    for (int i = 0; i < 3; i++) {
      stepA(1);
    }
    seqS();
    for (int i = 0; i < 3; i++) {
      stepA(1);
    }
    seqS.wait();
    return 0;
  }
</code>
At the end of the method you have to wait for the subsequence as it runs in its own thread.

===== Main Sequence Has Timeout Monitor =====

The next example is [[https://github.com/eeros-project/eeros-framework/blob/master/examples/sequencer/SequencerTest31.cpp|SequencerTest31.cpp]]. It demonstrates what happens if the main sequence is interrupted by a monitor while a subsequence is called. Run 
<code>
$ ./examples/sequencer/sequencerTest31
</code>

The main sequence does three steps and starts the second sequence. The timeout monitor of the main sequence fires while the second sequence still runs. The monitor causes an exception sequence to run. After that the main sequence terminates immediately as the timeout behavior is set to ''abort''. The subsequence continues running in its own thread.

[{{ :getting_started:tutorials:sequencetest31.png?500 | //Aborting the main sequence// }}]
\\

===== Main Sequence Has Timeout Monitor With Resume =====

The next example is [[https://github.com/eeros-project/eeros-framework/blob/master/examples/sequencer/SequencerTest32.cpp|SequencerTest32.cpp]]. It demonstrates what happens if the main sequence is interrupted by a monitor while a subsequence is called. Run 
<code>
$ ./examples/sequencer/sequencerTest32
</code>

The main sequence does three steps and starts the second sequence. The timeout monitor of the main sequence fires while the second sequence still runs. The monitor causes an exception sequence to run. After that the main sequence continues where it was interrupted as the timeout behavior is set to ''resume''. The subsequence continues running in its own thread.

[{{ :getting_started:tutorials:sequencetest32.png?500 | //Resuming the main sequence// }}]
\\

===== Main Sequence Has Timeout Monitor With Restart =====

The next example is [[https://github.com/eeros-project/eeros-framework/blob/master/examples/sequencer/SequencerTest33.cpp|SequencerTest33.cpp]]. It demonstrates what happens if the main sequence is interrupted by a monitor while a subsequence is called. Run 
<code>
$ ./examples/sequencer/sequencerTest33
</code>

The main sequence does three steps and starts the second sequence. The timeout monitor of the main sequence fires while the second sequence still runs. The monitor causes an exception sequence to run. After that the main sequence starts again as the timeout behavior is set to ''restart''. The subsequence continues running in its own thread. The main sequence will again call the subsequence and the same procedure will follow. This would continue endlessly if the behavior would not change to ''abort'' after three runs.

[{{ :getting_started:tutorials:sequencetest33.png?500 | //Resuming the main sequence// }}]
\\

===== Subsequence Has Timeout Monitor =====

The next example is [[https://github.com/eeros-project/eeros-framework/blob/master/examples/sequencer/SequencerTest34.cpp|SequencerTest34.cpp]]. It demonstrates what happens if the subsequence is interrupted by a monitor while being called from the main sequence. Run 
<code>
$ ./examples/sequencer/sequencerTest34
</code>

The main sequence does three steps and starts the second sequence. The timeout monitor of the subsequence fires. The monitor causes an exception sequence to run. After that the subsequence terminates immediately as the timeout behavior is set to ''abort''. The main sequence continues running in its own thread.

[{{ :getting_started:tutorials:sequencetest34.png?500 | //Aborting the subsequence// }}]
\\

===== Subsequence Has Timeout Monitor With Resume =====

The next example is [[https://github.com/eeros-project/eeros-framework/blob/master/examples/sequencer/SequencerTest35.cpp|SequencerTest35.cpp]]. It demonstrates what happens if the subsequence is interrupted by a monitor while being called from the main sequence. Run 
<code>
$ ./examples/sequencer/sequencerTest35
</code>

The main sequence does three steps and starts the second sequence. The timeout monitor of the subsequence fires. The monitor causes an exception sequence to run. After that the subsequence continues from where it was interrupted as the timeout behavior is set to ''resume''. The main sequence continues running in its own thread.

[{{ :getting_started:tutorials:sequencetest35.png?500 | //Resuming the subsequence// }}]
\\

===== Subsequence Has Timeout Monitor With Restart =====

The next example is [[https://github.com/eeros-project/eeros-framework/blob/master/examples/sequencer/SequencerTest36.cpp|SequencerTest36.cpp]]. It demonstrates what happens if the subsequence is interrupted by a monitor while being called from the main sequence. Run 
<code>
$ ./examples/sequencer/sequencerTest36
</code>

The main sequence does three steps and starts the second sequence. The timeout monitor of the subsequence fires. The monitor causes an exception sequence to run. After that the subsequence restarts as the timeout behavior is set to ''restart''. The main sequence continues running in its own thread. The subsequence would restart again and again while the main sequence would have to wait for it. After three restarts the timeout behavior is set to ''abort'' and subsequence and main sequence terminate.

[{{ :getting_started:tutorials:sequencetest36.png?500 | //Aborting the subsequence// }}]
\\