eeros_architecture:sequencer:start
                Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| eeros_architecture:sequencer:start [2017/08/10 08:28] – graf | eeros_architecture:sequencer:start [2019/03/14 09:25] (current) – graf | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Sequencer ====== | ====== Sequencer ====== | ||
| - | A sequencer ensures that a robots can execute a series of user-defined tasks. Such a sequencer runs in non-realtime. The robot' | + | A sequencer ensures that a robots can execute a series of user-defined tasks. Such a sequencer runs in non-realtime. The robot' | 
| - | As soon as a sequence should run concurrently to another sequence a second sequencer has to be defined. In such a case the two sequencers each run in a separate thread of execution. \\ | + | |
| - | What happens if a certain step in a sequence cannot run due to some condition. In that case an exception might be thrown and a special exception handler has to take necessary steps. This could include repeating some steps or doing something completely different. | + | |
| + | What happens if a certain step in a sequence cannot run due to some condition? In that case an exception might be thrown and a special exception handler has to take necessary steps. This could include repeating some steps or doing something completely different. | ||
| - | {{ sequenceroverview.png? | + | |
| + | [{{ sequenceroverview.png? | ||
| Learn more about how to use the sequencer and how it handles exceptions: | Learn more about how to use the sequencer and how it handles exceptions: | ||
| * [[.: | * [[.: | ||
| * [[.: | * [[.: | ||
| + | * [[.: | ||
| + | * [[.: | ||
| * [[.: | * [[.: | ||
| - | * [[.:subsequence|Subsequence]] | + | * [[.:exceptions]] | 
| - | * [[.: | + | |
eeros_architecture/sequencer/start.1502346501.txt.gz · Last modified: 2017/08/10 08:28 (external edit)
                
                