The EC-C1200 and C1700 inverters can indicate one of several generic software fault codes, labeled application faults. These faults are usually related to issues in the CAN bus connection and communication, but can indicate also other software faults that are originating from incorrect parameter configuration or wiring issues.
By connecting to the device with PowerUSER, more detailed information about the faults can be found via the active faults and fault log functions. The fault displays will show a column labeled "argument" which gives more detailed information on the exact root cause of the fault.
Application fault 36
Application fault 36 is reserved for the internal software applications of the inverter, and can be triggered for example by the CODESYS application. The standard Editron software applications can indicate one of the following arguments:
General:
| Argument | Description |
| 0x1 Communication timeout | CAN bus timeout. Check the CAN bus configuration, wiring, bus load, and message configuration. Check the EC-C1200 communication manual for more information. |
| 0x2 Start timeout | Inverter did not start in the allocated time after the run command was given. Contact Editron for more information. |
Master-follower:
| Argument | Description |
| 0x400 Follower fault | Follower inverter reported a fault. Connect to the follower inverter and check the fault codes. Reboot the inverters at the same time to prevent faults due to the inverters starting at different times. |
| 0x410 Start timeout | Starting of the master and follower inverters was not successful in the allocated time. Check the CAN bus wiring, bus load and parameter configuration. If problem persists, contact Editron. |
| 0x420 Communication timeout | CAN bus timeout. Check the CAN bus configuration, wiring, bus load, and message configuration. |
Application fault 44 and 49
Application faults 44 and 49 are commonly caused by CAN bus wiring issues, too high bus load, or incorrect messaging configuration. Depending on the configuration and severity of the issue, these can be either warnings (device continues to operate), or faults (device is tripped immediately).
These faults also indicate a structured argument that can be observed through the PowerUSER program, which consists of eight letters in the form of NNMMXXXX, where:
- First two letters of the argument code (NN) show which module the error is originating from. This is always 04 for error 44, and 01 or 02 for error 49, which all refer to the CAN bus interface of the device. In case the error indicates some other module, contact Danfoss Editron for more information.
- The next two letters (MM) indicate the fault that occurred, see the tables below for a list of different faults.
- The last four letters (XXXX) indicate how many times this fault has occurred consecutively.
Example: fault code 44 with argument 04010007 can be decoded as follows:
module = 04 = CAN bus
fault = 01 = RX buffer overflow
occurrence = 0007 = occurred 7 times
So the full explanation would be "CAN bus RX buffer overflow which has occurred seven times". This would indicate too many messages coming to the inverter too quickly, which has filled the RX message buffer before the device had time to process the messages properly.
Fault 44
Application fault 44 usually indicates failures on the CAN bus protocol level, which are commonly caused by problems such as too high CAN bus load, wiring issues, incorrect termination resistance, etc. It can also be triggered by the message timeout function, if the configured messages were not received in time. See the communication manuals for more information regarding the timeouts and message configuration. See the articles CAN troubleshooting, How to reduce CAN bus load when using J1939, or CAN bus physical layer for more information about the CAN bus functionality.
| Module | Fault | Description |
| 04 - CAN bus | 01 - RX buffer overflow | Receive buffer overflow. Too many messages were sent to the device in a short time period, causing an overflow in the receive message buffer. Check CAN bus load and message configuration. |
| 02 - TX buffer overflow | Transmit buffer overflow. Device could not transmit it's configured messages to the bus fast enough, causing an overflow in the transmit message buffer. Check CAN bus load and message configuration. | |
| 03 - ACK error | Acknowledge error. Device does not receive a positive acknowledgment from any other node, indicating that the message was not properly received by the network. Check wiring, bus load and ensure that other devices on the CAN network are functioning normally. | |
| 04 - Passive | A passive condition was triggered, indicating error frames on the CAN bus. Check wiring, bus load and ensure that other devices on the CAN network are functioning normally. | |
| 05 - Timeout | A timeout was detected in the CAN messaging. Check the CAN bus configuration, wiring, bus load, and message configuration. Check the EC-C1200 communication manual for more information. |
Fault 49:
Application fault 49 usually indicates that the user is sending the fault clear command consecutively several times (module 2, error code 2). The fault clear command should be sent only as a singular pulse, meaning one CAN message with the fault clear command set to "true" and then immediately return it to "false". Otherwise fault 49 with module 2 and error code 2 is triggered, as clearing the faults consecutively can cause danger to the equipment or personnel in some situations. Consecutive fault reset pulses should be sent with a delay of >500 ms, otherwise error 49 is triggered.
Note that in firmware 7, the parameter network_application.fault_reset_mode (50006.50) should be switched to "Rising Edge" to prevent the error 49 from triggering in normal use (requires firmware 7.2.13 or newer).
| Module | Fault | Description |
| 01 - Fieldbus | 01 - RX overflow | Receive interface overflow. Similar to fault code 44 with argument 0x04010001. |
| 02 - Protection | 01 - Unexpected fault from check | Internal software fault. contact Editron for more information. |
| 02 - Clearing too fast | Fault clear command was sent to the device consecutively without long enough wait time in between. |