10.4.3.2 Errors
When an Error or Alarm occurs, always check the controller log messages. The log mes-
sages will provide more details about the failure and the history of events leading up to the fail-
ure. From the log messages, you can determine the specifics about the cause of the failure to
correct the underlying problem.
Eliminate errors and faults in compliance with work safety rules. Troubleshooting only by
qualified and trained staff.
More information about error and alarm messages, causes, remedy and clearing errors can
be found in the WorkBench online help and in
Error
Description
E01
Critical temperature exceeded. Operation is stopped, CPU will be put to sleep.
E02
Out of memory. KAS runtime is stopping.
E03
Fan failure.
E10
Firmware is corrupted.
E11
Flash is corrupted, no filesystem is available.
E12
Not enough flash memory available.
E13
Out of NVRAM space for retained variables.
E14
Reset to Factory Defaults failed.
E15
Cannot read/write files from/to a SD card.
E16
Not enough space available on the SD card.
E20
Runtime plug-in, process, thread or application failed to start.
E21
Runtime plug-in, process, or thread failed to respond during operation.
E22
Fatal error in PLC program, application stopped.
E23
CPU is overloaded.
E24
PLC application cannot be started
E30
EtherCAT communication failure during operational mode.
E31
EtherCAT communication failure during preop mode.
E32
EtherCAT communication failure during bootstrap mode.
E33
EtherCAT failed to initialize into operational mode.
E34
EtherCAT failed to initialize into preop mode.
E35
EtherCAT failed to initialize into bootstrap mode.
E36
EtherCAT network discovery failed.
E37
EtherCAT failed to return to init state.
E50
Backup to SD card failed.
E51
Restore from SD card failed..
E52
SD Backup files are missing or corrupt.
E53
SD Backup files are not compatible.
AKD Installation | 10 Setup
Kollmorgen | kdn.kollmorgen.com | October 2017
209