Realtime Runtime System for Windows NT/2000/XP
8 Behaviour in case of runtimeerrors
There are some different reasons, which lead to a cycle-stop of the user application. These errors are:
Number |
Name |
Reason |
|
|
|
16 |
Watchdog |
The application needed more than the defined cycle time to |
|
|
complete the current cycle. The cycle time, which is controlled, is |
|
|
computed by the watchdog-factor (see “Config” in the chapter “ |
|
|
Operation via the Service icon”) If the CoDeSys-version 2.3 is |
|
|
used, it may support the definition of the watchdog factor within |
|
|
the task configuration. Then the factor there is used. |
|
|
|
20 |
Fieldbus error |
An IO-driver could not initialize himself. Can only happen when |
|
|
starting the PLC. |
|
Error in configuration |
One of the used fieldbus cards did not accept the data coming |
|
data |
from the PLC-configuration. |
|
|
|
21 |
Error update IOs |
Can only happen after loading the program. Happens, if an IO- |
|
|
address, which no IO-driver can handle, is used. |
|
|
|
81 |
Access violation |
The application tried to access a memory address, which is |
|
|
invalid. Maybe a pointer is used and not correctly initialized? |
|
|
|
258 |
Division by zero |
The application tried to compute a division by zero. |
|
|
|
336-343 |
FPU-Error |
An invalid or impossible floatingpoint-operation was executed.. |
|
|
|
All these errors lead to the same behaviour of the PLC:
-The outputs are, if configured, set to 1 or 0.
-The PLC-cycle is stopped. (Remember, only the task that caused the error is left immediately. The other tasks, that may be active, will complete their current cycle and not begin a new one.)
-The IO-update of all tasks will continue. (Only the PIO may have been set to 1 or 0.)
The error that occurred is shown within “Diagnostic”-tab of the service menu.
The PLC will store the error with (if possible) the callstack. After logging in with CoDeSys, the line within the application can be found. (Online -> callstack)
tech_doc_e.doc / V1.1
3S - Smart Software Solutions GmbH |
Page 31 of 35 |
CoDeSys SP RTE_E.doc |
|