Tab: Monitoring

Object: Task Configuration

The tab displays the status of the CODESYS tasks in online mode as well as some current measurements for the cycles and cycle times. The values are refreshed in the same time interval as for monitoring of values from the controller.

For more information, see: Definitions of Jitter and Latency

The displayed values can be reset to 0 by means of the Reset context menu command.

Task	Task name (as defined in the task configuration)
Status	Not created: The task has not been started since the last update (especially for event tasks). Generated: The task is recognized in the runtime, but not yet in operation. Valid: The task is operating normally. Exception: The task has produced an exception status.
IEC-Cycle Count	Number of cycles, which have been executed since first starting the application, where the IEC code has actually been called. As a result, this value corresponds to a Hugo counter in the code. But if the target system does not support the counting function, then the number remains at `0`.
Cycle Count	Number of executed cycles since logging in to the controller, even if the task is in STOP The number corresponds to the calls of `IecTaskCycle2` and is incremented even when the application is in STOP. However, it depends on the target system whether cycles are counted where the application is not running. In these cases, the Cycle Count can be greater than the IEC-Cycle Count.
Last Cycle Time (µs)	Last measured cycle time [µs]
Average Cycle Time (µs)	Average cycle time over all cycles [µs]
Max. Cycle Time (µs)	Maximum measured cycle time over all cycles [µs]
Min. Cycle Time (µs)	Minimum measured cycle time over all cycles [µs]
Jitter (µs)	Current value of the periodic jitter [µs] Note: From CODESYS 3.5 SP11 to SP15, the peak-peak value of the periodic jitter is displayed. In earlier versions and in SP16 and higher, the current value of the periodic jitter is displayed.
Min. Jitter (µs)	Minimum measured periodic jitter [µs]
Max. Jitter (µs)	Maximum measured periodic jitter [µs]
Core	Number of the processor core where the task is currently running Example: `2` Requirement: The controller is equipped with a multicore processor. If the CPU is not a multicore CPU, then the value `-1` is displayed here.