IFM Electronic Ecomat 100 ecomatmobile SmartController CR2500, System Manual

Page: 39 / 300

ifm System Manual ecomat mobile SmartController (CR2500, CR2502) V05
Error codes and diagnostic information Operating modes
39
6 Error codes and diagnostic information
Response to the system error ...................................................................................................40
To ensure maximum operational reliability the operating system checks the ecomat mobile controller
in the start phase (reset phase) and during the program execution by internal error checks.
The following error flags are set in case of an error:
Error Description
CANx_BUSOFF CAN interface x: Interface is not on the bus
CANx_LASTERROR ¹) CAN interface x: Error number of the last CAN transmission:
0= no error
≠
0
→
CAN specification
→
LEC
CANx_WARNING CAN interface x: Warning threshold reached (> 96)
ERROR ³) Set ERROR bit / switch off the relay *)
ERROR_MEMORY Memory error
ERROR_POWER Undervoltage/overvoltage error
ERROR_TEMPERATURE Excessive temperature error (> 85 °C)
ERROR_VBBR Terminal voltage error VBB
R
CANx stands for the number of the CAN interface (CAN 1...x, depending on the device).
¹) Access to this flags requires detailed knowledge of the CAN controller and is normally not required.
²) Flag NOT available for CR250n, CR0301, CR0302.
³) By setting the ERROR system flag the ERROR output (terminal 13) is set to FALSE. In the "error-
free state" the output ERROR = TRUE (negative logic).
*) Relay NOT available for CR250n and CR030n.
The following diagnostic messages are only available for devices with periphery terminals:
Diagnostic message
(only devices with periphery connections)
Type Description
ERROR_BREAK_Qx *) BYTE Wire break error on the output group x
ERROR_Ix BYTE Peripheral error on the input group x
ERROR_SHORT_Qx *) BYTE Short circuit error on the output group x
x stands for the input/output group x (word 0...x, depending on the device).
*) Flags only available for ClassicController, ExtendedController, SafetyController.
NOTE
In adverse cases the output transistor can already switch off a disturbed output before the operating
system could detect the error. The corresponding error flag is then NOT set.
We recommend that the application programmer (additionally) evaluates the error by reading back the
outputs.