Complete reference guide for all system error codes
Codes are shown on the HMI and repeated in the controller event log. The log is the more useful of the two, because it keeps the order in which events arrived. When several codes appear together, work on the earliest one: the rest are usually consequences.
| Code | Meaning | First action |
|---|---|---|
| E001 | Power supply fault | Check incoming voltage, fuses and the control supply MCB. |
| E002 | Communication timeout | Check the network cable, link lights and the address of the device that stopped responding. |
| E003 | Over temperature | Check cooling fans, filters and room ambient temperature. Reduce load if the room is above rating. |
| E004 | Emergency stop active | Confirm every E-Stop is released, then reset and acknowledge the alarm. |
| E005 | Protection trip | Do not reset until the cause is identified. Read the relay fault record first. |
| E006 | Configuration mismatch | A device was replaced or reflashed. Compare the loaded configuration against the project record. |
A trip is a protective action, not a nuisance. Resetting without finding the cause can re-energise a fault into a damaged circuit. E005 in particular should never be reset until the relay record has been read and the reason understood.
Record the exact code, the time, and the state of the plant when it appeared, then export the controller event log. Send those to ECS support through the contact page. The code set varies by controller family, so the log is what makes a remote diagnosis possible.
Was this support article helpful?