overrun Cyc.-T

What does 0219 mean?

The cyclic task (PLC_PRG ID 1) has exceeded its allocated monitoring time. This indicates that the task processing duration is longer than the set monitoring time, potentially due to complex or lengthy program parts.

• Excessive processing load in the `PLC_PRG` task due to complex or long-running algorithms (e.g., large array processing, extensive string manipulation).
• Increased execution time of specific function blocks (FBs) or functions called within `PLC_PRG`, potentially from external library updates or changes in their internal logic.
• Insufficient cycle time configured for the `PLC_PRG` task (e.g., parameter `P0-03` set to 1ms while actual execution consistently exceeds 1ms).
• Higher priority tasks (e.g., motion control, communication) occasionally preempting `PLC_PRG` for extended periods, delaying its completion beyond the monitoring time.
• Communication interruptions or bus delays causing `PLC_PRG` to wait for I/O updates for longer than expected (e.g., `EtherCAT_Sync` issues).

Click steps to track your progress.

1. 1

   1. Use the controller's task monitoring tools or a built-in `Scope` trace to measure the actual execution time of the `PLC_PRG` and identify specific code sections that consume the most time.

2. 2

   2. Optimize `PLC_PRG` logic by reducing loop iterations, simplifying complex calculations, or moving non-time-critical code to lower-priority tasks.

3. 3

   3. Increase the cyclic task's configured cycle time (e.g., Parameter `P0-03` from 5ms to 10ms) to provide more execution budget, if acceptable for the application requirements.

4. 4

   4. Analyze the timing and priority settings of other tasks (e.g., `Task0_Priority`) and their impact on `PLC_PRG` using the controller's diagnostics.

5. 5

   5. Evaluate the efficiency of I/O communication (e.g., bus utilization, response times of `IO_Module_1`) and network configuration if I/O delays are causing task overruns.