eeros_architecture:sequencer:usage
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| eeros_architecture:sequencer:usage [2015/03/30 15:46] – external edit 127.0.0.1 | eeros_architecture:sequencer:usage [2015/10/30 10:48] (current) – removed graf | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======Sequencer Usage====== | ||
| - | This page describes the usage of the sequencer in the EEROS framework. | ||
| - | ===== Sequencer ===== | ||
| - | Create an instance of the sequencer. If its the first sequencer you define, it will automatically be the main sequencer. Start it with the method // | ||
| - | <code c> | ||
| - | Sequencer mainSequencer(" | ||
| - | MySequence sequence(" | ||
| - | | ||
| - | mainSequencer.start(); | ||
| - | while(!mainSequencer.isTerminated()){ | ||
| - | cout << " | ||
| - | } | ||
| - | </ | ||
| - | |||
| - | The method //start()// creates a thread, which runs until the //stop()// method is called. | ||
| - | |||
| - | If it is necessary to keep data which is specific to a certain sequencer you may define your own class // | ||
| - | |||
| - | <code c> | ||
| - | class MySequencer : public eeros:: | ||
| - | </ | ||
| - | |||
| - | ===== Sequence ===== | ||
| - | A sequence is a series of steps. The order has to be defined by the user. A step corresponds to a single method, such as | ||
| - | |||
| - | <code c> | ||
| - | void init(); | ||
| - | void homed(); | ||
| - | void move(); | ||
| - | </ | ||
| - | |||
| - | Implement each of the methods according to its task. Then, derive // | ||
| - | <code c> | ||
| - | class MySequence : public eeros:: | ||
| - | </ | ||
| - | |||
| - | As a next step you have to create an instance of // | ||
| - | <code c> | ||
| - | MySequence sequence(" | ||
| - | </ | ||
| - | Add the steps to the sequence with the method // | ||
| - | Insert these methods in the list of callbacks in your implementation of the method // | ||
| - | <code c> | ||
| - | void MySequence:: | ||
| - | addCallBack(static_cast< | ||
| - | addCallBack(static_cast< | ||
| - | addCallBack(static_cast< | ||
| - | } | ||
| - | </ | ||
| - | |||
| - | The constructor of // | ||
| - | |||
| - | <code c> | ||
| - | /** constructor MySequence | ||
| - | * name: Name of the Sequence | ||
| - | * caller: Sequencer to which this sequences belongs | ||
| - | */ | ||
| - | MySequence:: | ||
| - | : eeros:: | ||
| - | callerThread.addRunnable(this); | ||
| - | } | ||
| - | </ | ||
| - | |||
| - | Do not forget to stop the sequencer by calling //stop()// of the class // | ||
| - | <code c> | ||
| - | callerThread.stop(); | ||
| - | </ | ||
| - | |||
| - | {{ sequenceruml.png? | ||
| - | |||
| - | ===== Subsequence===== | ||
| - | A subsequence is a sequence which is called by a step of another sequence. Such a subsequence can be called in a blocking or non-blocking way. Blocking means that the step waits (or blocks) until the subsequence has finished. Non-blocking means that subsequence and main sequence run concurrently. | ||
| - | |||
| - | ====Blocking Call of a Subsequence==== | ||
| - | If you want to save your own data in the sequence, you need to create a new instance of a sequence. This should be done in the desired step (method) of the superior sequence. | ||
| - | e.g. in the method // | ||
| - | |||
| - | <code c> | ||
| - | MyBlockingSubSequence* subSequence = dynamic_cast< | ||
| - | if(!subSequence){ | ||
| - | // | ||
| - | subSequence = new MyBlockingSubSequence(" | ||
| - | } | ||
| - | </ | ||
| - | |||
| - | **Note:** | ||
| - | *In the above lines only one object of // | ||
| - | *It is not allowed to call the // | ||
| - | |||
| - | To start the sub-sequence just call //run()//, which calls all methods in the callback list (filled by // | ||
| - | |||
| - | <code c> | ||
| - | //Here we wait for the returning of the subSequence.run() method | ||
| - | while(subSequence-> | ||
| - | subSequence-> | ||
| - | } | ||
| - | </ | ||
| - | |||
| - | ====Non Blocking Call of a Sub-Sequence==== | ||
| - | Remark: Please use pointer for a non blocking call, because the memory referenced by a pointer to an object exists until you delete it However, an object is removed as soon the scope of the method is no longer being used. In the case where both sequences (sequence and sub-sequence) run contemporaneously, | ||
| - | |||
| - | A non-blocking sub-sequence has to be created as a thread, so you need a sub-sequencer for starting the new thread. | ||
| - | e.g.: | ||
| - | <code c> | ||
| - | MySequencer* subSequencer = new MySequencer(" | ||
| - | </ | ||
| - | |||
| - | Here you can reuse an existing sub-sequence if you want. | ||
| - | <code c> | ||
| - | MyNonBlockingSubSequence* subSequence = dynamic_cast< | ||
| - | if(!subSequence){ | ||
| - | subSequence = new MyNonBlockingSubSequence(" | ||
| - | } | ||
| - | </ | ||
| - | |||
| - | **Note:** | ||
| - | *The constructor of the // | ||
| - | *Do not forget to call // | ||
| - | |||
| - | As soon as you have created the sub-sequence, | ||
| - | |||
| - | <code c> | ||
| - | subSequencer-> | ||
| - | </ | ||
| - | |||
| - | In an other step of the superior sequence you can wait until the non-blocking sequence is terminated by using the method: // | ||
| - | <code c> | ||
| - | //Here we wait for the subsequencer Thread | ||
| - | eeros:: | ||
| - | if(seq && seq-> | ||
| - | ExecutorService:: | ||
| - | } | ||
| - | </ | ||
eeros_architecture/sequencer/usage.1427723177.txt.gz · Last modified: 2015/10/27 08:33 (external edit)