8313 Excessive cycle time overrun
Refer to Diagnostic class (standard): 3
The excessive cycle time error is monitored by the system. The task stops immediately if an error caused by a cycle time overrun is detected. Stopping the task is controlled by the system, not by the task itself so it is done without taking into account any executing program operations.
Therefore, it cannot be ruled out that the task is performing for example, a read/write operation on the file system and so blocks another system resource exclusively. This resource is not released when the task is stopped. If other tasks try to access this resource, a subsequent error may occur.
The excessive cycle time error of a task is reported when the Watchdog (Time x Sensitivity in the TASK_SR_Main Configuration tab) is exceeded.
The task then receives an error status. You can quit the diagnostic message by resetting the program. The detected error can only be solved by resetting the controller (Online > Cold reset of controller). The cycle time monitoring of the task refers to the load parameter that is displayed in the task expansion object in the PLC configuration.
|
Cause |
Solution |
|---|---|
|
The processing time of a parameter or system functional block that is being called is taking too long. |
oPerform a reset of the controller. oVerify and correct if necessary the program (for example, access to Sercos parameter or FC_WaitTime() function). |
|
The time interval in the task configuration is too short. |
oIncrease the time interval in the task configuration. oIf possible, relocate critical activities in a new or in another task. |
