Use Periodic Tasks
To make synchronization, crossloads, and HMI updates as fast as possible, avoid using a continuous task. Instead, use periodic tasks. The fewer periodic tasks, the better the performance.
IMPORTANT:
While a continuous task is fully supported, you can manage performance easier without a continuous task. With a continuous task, the performance of some types of communication can be negatively impacted under certain conditions, such as heavy messaging or HMI data table writes of tags to the controller.
Multiple Periodic Tasks
Only the single highest-priority periodic task provides bumpless output switching on switchover.
ATTENTION:
If you use multiple periodic tasks, program all crucial outputs within the highest priority task. Failure to program outputs in the highest-priority task can result in outputs that change state if a switchover occurs.
- There are no task overlaps during synchronized steady state. The execution time of each task is smaller than its period.
- The total execution time of all your tasks is less than the period of the task with the largest period.
- The lower priority tasks have longer periods than higher priority tasks to allow time for task interruption by the higher priority tasks.
Task | Priority | Execution Time | Period Specified |
|---|---|---|---|
1 | Higher | 20 ms | 80 ms |
2 | Lower | 30 ms | 100 ms |
Total execution time: 50 ms | |||
- To check for overlaps, go online with the controller and access the Task Properties dialog box. On the Monitor tab, note the maximum scan time. Verify that the maximum scan time is smaller than the period for the periodic task.
- To determine how may task overlaps occurred since the last reset, check the Task Overlap Count parameter. Because task overlaps are expected during qualification, check the number of task overlaps while the controller is in a synchronized steady state.
Provide Feedback