The Executor runs the time domains of the control system and the safety system. The time domains are handled by harmonic tasks. The following examples demonstrate the use of such harmonic tasks.

In the EEROS library you will find a directory with examples. For this example see PeriodicExample1.cpp.

Open a shell in the build directory of your EEROS library and run

$ sudo ./examples/task/periodicExample1

This examples does:

• Creates a main task mainTask with an execution period of 10ms. The task itself is defined of type Lambda with a run method given by an empty lambda function.
• Creates a time domain harmonicTask with a period of 2s.

Both harmonic tasks have a periodic counter which measure its periods and run times. Once every 200th run the results of the main task are logged. The harmonic task logs every time it runs. The results are printed in units of seconds. Additionally both harmonics have a default monitor function added. This monitor function logs a warning if the measured period differs more than 5%. Depending on your hardware platform and realtime support of your operating system you might get no warnings, several or many warnings.

If you don't specify a main task, the executor will create a default main task, which does nothing, see PeriodicExample2.cpp.

Run

$ sudo ./examples/task/periodicExample2

This examples does:

• Creates a time domain harmonicTask with a period of 2s.

The tasks has a periodic counter which measure its periods and run times. The harmonic task logs every time it runs. The results are printed in units of seconds.

An example with many tasks can be found under PeriodicExample3.cpp.

Run

$ sudo ./examples/task/periodicExample3

This examples does:

• Creates a main task mainTask with an execution period of one second. The task itself is defined of type Lambda with a run method given by a lambda function. It prints out two messages with a short delay in between.
• Creates a periodic t1 with a period of one second. Its run method prints out some messages with a short delay in between. t1 runs concurrently to mainTask.
• Creates a periodic t2 with a period of two seconds. Its run method prints out some messages with a short delay in between. t2 runs after t1 has finished.
• Creates a periodic t4 with a period of four seconds. Its run method prints out some messages with a short delay in between. t4 runs after t2 has finished.
• Creates a periodic t3 with a period of five seconds. Its run method prints out some messages with a short delay in between. t3 runs after t1 has finished but concurrently to t2.
• Creates a periodic t5 with a period of three seconds. Its run method prints out some messages with a short delay in between. t5 runs concurrently to t1.

All of the harmonic tasks have a periodic counter which measure its periods and run times. Once every 10th run the results are logged. The results are printed in milliseconds.