Back to top

AKD PDMM Alarm and Error Messages

Valid for AKD-M (AKD PDMM)

LED-akd-pdmm.jpg

The two digits LED display indicates the messages of the drive. Fault messages are coded with "F", warnings are coded with "n". See Fault Messages AKD.

The one digit LED indicates the PDMM messages of the controller. Error messages are coded with "E", alarms are coded with "A". See table below.

Error/
Warning
Description Cause Remedy
E01
A01
Critical temperature exceeded. PDMM operation is stopped, CPU will be put to sleep. CPU temperature exceeded safe operating temperature limit. Power-off. Check airflow and operating environment are within hardware specifications. Allow unit to cool before power-on.
E02
A02
Out of memory. KAS runtime is stopping. Memory leak, memory corrupted, or hardware memory failure. Power-off/on. If problem is recurrent, check release notes for firmware updates or return hardware for repair.
E03 Fan failure. CPU cooling fan was not able to operate properly. Check temperature and monitor for High temp alarm (see A01). Return hardware for fan replacement.
A04 Low input voltage +24 volt input power is +19 volts or less. Check power supply voltage and connection to the PDMM.
E10 Firmware is corrupted. Flash memory corrupted during firmware download or flash hardware failure. Re-download firmware or boot into recovery image, downloadIf problem is recurrent, power-off/on. Check release notes for firmware updates. firmware, and power-off/on. If problem persists, return hardware for repair.
E11 Flash is corrupted, no filesystem is available. At startup the filesystem could not be mounted on the flash. Reset to factory defaults. If problem persists, return hardware for repair.
E12
A12
Not enough flash memory available. Flash memory is full, unable to write to flash. Clean-up the flash memory by removing log files, application programs, recipes, or other data files.
E13 Out of NVRAM space for retained variables. NVRAM is full. Change application to reduce the amount of retained variables.
E14 Reset to Factory Defaults failed. Flash memory could not be formatted during a Reset to Factory Defaults procedure. Try reset to factory defaults again from power-on. If problem persists, return hardware for repair..
E15 Cannot read/write files from/to a SD card. SD card is not plugged-in or the file system is corrupt and cannot be mounted. Insert a valid SD card or re-format the SD card using Settings->SD card->Format button.
E16 Not enough space available on the SD card. SD card is full, unable to write to the SD card. Clean-up SD card space by deleting files or re-format the card using Settings->SD card->Format button.
E20 Runtime plug-in, process, thread or application failed to start. KAS runtime or application code failed to auto-start at boot. Power-off/on. Reset to factory defaults. If problem is recurrent, check release notes for firmware updates or download firmware.
E21
A21
Runtime plug-in, process, or thread failed to respond during operation. KAS runtime code failed during normal operation. Power-off/on. If problem is recurrent, check release notes for firmware updates.
E22 Fatal error in PLC program, application stopped. Virtual machine failed to execute an instruction. Re-compile application, download, and re-start.
E23
A23
CPU is overloaded. Either the motion engine cycle did not complete or the PLC program did not complete within the timeout period due to excessive CPU loading. Stop the application or power-off/on. Reduce the sample rate, simplify the application,or reduce the application cycles and re-start the application.
E30
A30
EtherCAT communication failure during operational mode. EtherCAT network operation failed due to a network communciation error. Check the EtherCAT network wiring and devices state. Re-start the application.
E31 EtherCAT communication failure during preop mode. EtherCAT network operation failed due to a network communciation error. Check the EtherCAT network wiring and devices state. Re-start the application.
E32 EtherCAT communication failure during bootstrap mode. EtherCAT network operation failed due to a network communciation error. Check the EtherCAT network wiring and devices state. Re-start the application.
E33 EtherCAT failed to initialize into operational mode. EtherCAT network initialization failed due to a network communciation error. Check the EtherCAT network wiring and devices state. Re-start the application.
E34 EtherCAT failed to initialize into preop mode. EtherCAT network initialization failed due to a network communciation error. Check the EtherCAT network wiring and devices state. Re-start the application.
E35 EtherCAT failed to initialize into bootstrap mode. EtherCAT network initialization failed due to a network communciation error. Check the EtherCAT network wiring and devices state. Re-start the application.
E36 EtherCAT failed to discover the expected devices. EtherCAT network discovery failed due to a mismatch between the discovered and expected devices. Check the EtherCAT devices and wiring order. Correct the device order wiring or re-scan the network, re-compile, and download the updated application. Re-start the application.
E37 EtherCAT failed to return to init state. EtherCAT network initialization failed due to a network communciation error. Check the EtherCAT network wiring and devices state. Re-start the application.
A38 EtherCAT missed a receive frame during operation mode. EtherCAT master did not receive a frame for one or more cycles. Check the EtherCAT network wiring and devices.
A40 Local digital IO missed a cyclic update Local digital IO was not updated during a cycle or the updates are no longer synchronous. Reduce the sample rate, simplify the application, or reduce the application cycles.
E50 Backup to SD card failed. An unrecoverable error occurred during the backup operation. Repeat the backup to SD card operation. If it fails again, replace the SD card.
E51 Restore from SD card failed. An unrecoverable error occurred during the restore operation. Do NOT reboot the PDMM! Repeat the restore operation. If it fails again, reset the PDMM to factory defaults. If problem persists, return hardware for repair.
E52 SD Backup files are missing or corrupt. The restore operation failed due to missing, incomplete, or corrupt files on the SD card. Perform a backup operation before the restore or use an SD card with valid back upfiles.
E53
A53
SD Backup files are not compatible. The restore operation failed. The backup files are not compatible with the PDMM 800 MHz model. Use an SD card with a backup from a PDMM 800 MHz model.