Access the complete reference guide for ABB ACH580 HVAC drive fault codes. Learn to diagnose issues via the Hand-Off-Auto panel, BACnet integration, and Fireman’s Override.

The ABB ACH580 is the industry-standard flagship drive for HVACR applications. Designed to control air handling units, cooling towers, and chillers, it ensures critical comfort and safety in buildings. When a malfunction occurs, the dedicated Hand-Off-Auto (HOA) control panel displays a 4-digit code alongside plain-text diagnostics, often integrated directly into the Building Management System (BMS).

This guide provides the most updated reference to help you interpret these codes and maintain building environmental standards.

ACH580 Fault Codes Reference Table

Use the search bar below or browse the table to identify your specific error code:

ABB ACH580 Drive Fault Codes List

Fault Code and Meaning	Cause and Remedy
A2B1 Overcurrent	Cause: Output current has exceeded internal fault limit. In addition to an actual overcurrent situation, this warning may also be caused by an earth fault or supply phase loss. Remedy: Check motor load. Check acceleration times in parameter group 23 Speed reference ramp (speed control) or 28 Frequency reference chain (frequency control). Check parameters 46.01 Speed scaling, 46.02 Frequency scaling and 46.03 Torque scaling. Check motor and motor cable (including phasing and delta/star connection). Check for an earth fault in motor or motor cables by measuring the insulation resistances. Check there are no contactors opening and closing in motor cable. Check that the start-up data in parameter group 99 Motor data corresponds to the motor rating plate. Check that there are no power factor correction capacitors or surge absorbers in motor cable.
A2B3 Earth leakage	Cause: Drive has detected load unbalance typically due to earth fault in motor or motor cable. Remedy: Check there are no power factor correction capacitors or surge absorbers in motor cable. Check for an earth fault in motor or motor cables by measuring the insulation resistances of motor and motor cable. If an earth fault is found, fix or change the motor cable and/or motor. If no earth fault can be detected, contact your local ABB representative.
A2B4 Short circuit	Cause: Short-circuit in motor cable(s) or motor. Remedy: Check motor and motor cable for cabling errors. Check motor and motor cable (including phasing and delta/star connection). Check for an earth fault in motor or motor cables by measuring the insulation resistances. Check there are no power factor correction capacitors or surge absorbers in motor cable.
A2BA IGBT overload	Cause: Excessive IGBT junction to case temperature. This warning protects the IGBT(s) and can be activated by a short circuit in the motor cable. Remedy: Check motor cable. Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up. Check motor power against drive power.
A3A1 DC link overvoltage	Cause: Intermediate circuit DC voltage too high (when the drive is stopped). Remedy: Check the supply voltage setting (parameter 95.01 Supply voltage). Note that the wrong setting of the parameter may cause the motor to rush uncontrollably, or may overload the brake chopper or resistor. Check the supply voltage. If the problem persists, contact your local ABB representative.
A3A2 DC link undervoltage	Cause: Intermediate circuit DC voltage too low (when the drive is stopped). Remedy: Check the supply voltage. If the problem persists, contact your local ABB representative.
A3AA DC not charged	Cause: The voltage of the intermediate DC circuit has not yet risen to operating level. Remedy: Check the supply voltage setting. Contact your local ABB representative.
A490 Incorrect temperature sensor setup	Cause: Temperature cannot be supervised due to incorrect adapter setup. Remedy: Check the settings of temperature source parameters 35.11 and 35.21.
A491 External temperature 1	Cause: Measured temperature 1 has exceeded warning limit. (Editable message text). Remedy: Check the value of parameter 35.02 Measured temperature 1. Check the cooling of the motor (or other equipment whose temperature is being measured). Check the value of 35.13 Temperature 1 warning limit.
A492 External temperature 2	Cause: Measured temperature 2 has exceeded warning limit. (Editable message text). Remedy: Check the value of parameter 35.03 Measured temperature 2. Check the cooling of the motor (or other equipment whose temperature is being measured). Check the value of 35.23 Temperature 2 warning limit.
A4A0 Control board temperature	Cause: Control board temperature is too high. Remedy: Check the auxiliary code. See actions for each code below: (none): Temperature above warning limit: Check ambient conditions, air flow, fan operation, and heatsink fins. 0001: Thermistor broken: Contact an ABB service representative for control board replacement.
A4A1 IGBT overtemperature	Cause: Estimated drive IGBT temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up. Check motor power against drive power.
A4A9 Cooling	Cause: Drive module temperature is excessive. Remedy: Check ambient temperature. (If > 40°C/104°F for IP21 frames R4-R9 or > 50°C/122°F for frames R1-R9, ensure load does not exceed derated capacity). For all P55 frames, check the derating temperatures in the Hardware manual. Check drive module cooling air flow and fan operation. Check inside of cabinet and heatsink for dust pick-up. Clean whenever necessary.
A4B0 Excess temperature	Cause: Power unit module temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up. Check motor power against drive power. Check the auxiliary code.
A4B1 Excess temperature difference	Cause: High temperature difference between the IGBTs of different phases. Remedy: Check the motor cabling. Check cooling of drive module(s).
A4F6 IGBT temperature	Cause: Drive IGBT temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up. Check motor power against drive power.
A581 Fan	Cause: Cooling fan feedback missing. Remedy: Check the auxiliary code to identify the fan. Code 0 denotes main fan 1. Other codes (format XYZ): “X” specifies state (1: ID run, 2: normal). “Y” = 0. “Z” specifies index (1: Main fan 1, 2: Main fan 2, 3: Main fan 3). Check fan operation and connection. Replace fan if faulty.
A582 Auxiliary fan missing	Cause: An auxiliary cooling fan (IP55 internal fan) is stuck or disconnected. Remedy: Check the auxiliary code. Check the auxiliary fan and connection. Replace faulty fan. Make sure the front cover of the drive is in place and tightened. If commissioning with cover off, set parameter 31.36 Aux fan fault function temporarily to 'No action'.
A5A0 Safe torque off	Cause: Safe torque off function is active, i.e., safety circuit signal(s) connected to connector STO is lost. (Programmable warning 31.22). Remedy: Check safety circuit connections. Refer to 'The Safe torque off function' in the Hardware manual. Check description of parameter 31.22 STO indication run/stop. Check the value of parameter 95.04 Control board supply.
A5EA Measurement circuit temperature	Cause: Problem with internal temperature measurement of the drive. Remedy: Check the auxiliary code. They depend on the control unit type: Frames R1…R5: (0000 0000: IGBT temp, 0003: Board temp, 0006: Power supply temp) - Contact your local ABB representative. Frames R6…R11: (0001: U-phase, 0002: V-phase, 0003: W-phase, 0004: Board, 0005: Brake chopper, 0006: Air inlet, 0007: Power supply, 0008: du/dt, 0009: TEMP1) - Contact your local ABB representative.
A5EB PU board powerfail	Cause: Power unit power supply failure. Remedy: Contact your local ABB representative.
A5ED Measurement circuit ADC	Cause: Measurement circuit fault. Remedy: Contact your local ABB representative.
A5EE Measurement circuit DFF	Cause: Measurement circuit fault. Remedy: Contact your local ABB representative.
A5EF PU state feedback	Cause: State feedback from output phases does not match control signals. Remedy: Contact your local ABB representative.
A5F0 Charging feedback	Cause: Charging feedback signal missing. Remedy: Check the feedback signal coming from the charging system.
A682 Flash erase speed exceeded	Cause: The flash memory (in the memory unit) has been erased too frequently, compromising the lifetime of the memory. Remedy: Avoid forcing unnecessary parameter saves by parameter 96.07 or cyclic parameter writes. Check the auxiliary code (format XYYY YZZZ) to identify source.
A686 Checksum mismatch	Cause: The calculated parameter checksum does not match any enabled reference checksum. Remedy: Check that all necessary approved (reference) checksums (96.71…96.72) are enabled in 96.55 Checksum control word. Check the parameter configuration. Using 96.55 Checksum control word, enable a checksum parameter and copy the actual checksum into that parameter.
A687 Checksum configuration	Cause: An action has been defined for a parameter checksum mismatch but the feature has not been configured. Remedy: Contact your local ABB representative for configuring the feature. Or disable the feature in 96.54 Checksum action.
A6A4 Motor nominal value	Cause: The motor parameters are set incorrectly or the drive is not dimensioned correctly. Remedy: Check the auxiliary code: 0001: Slip frequency is too small. 0002: Synchronous and nominal speeds differ too much. 0003: Nominal speed is higher than synchronous speed with 1 pole pair. 0004: Nominal current is outside limits. 0005: Nominal voltage is outside limits. 0006: Nominal power is higher than apparent power. 0007: Nominal power not consistent with nominal speed and torque. 0008: Motor nominal power factor is not within limits. Check the settings of the motor configuration parameters in groups 98 and 99. Check that the drive is sized correctly for the motor.
A6A5 No motor data	Cause: Parameters in group 99 have not been set. Remedy: Check that all the required parameters in group 99 have been set. Note: It is normal for this warning to appear during the start-up and continue until the motor data is entered.
A6A6 Voltage category unselected	Cause: The voltage category has not been defined. Remedy: Set voltage category in parameter 95.01 Supply voltage.
A6A7 System time not set	Cause: System time is not set. Timed functions cannot be used and fault log dates are not correct. Remedy: Set the system time manually or connect the control panel to the drive to synchronize the clock. If basic control panel is used, synchronize the clock through the EFB or a fieldbus module. Set parameter 34.10 Timed functions enable to Disabled to disable the timed functions if they are not used.
A6B0 User lock is open	Cause: The user lock is open, ie, user lock configuration parameters 96.100…96.102 are visible. Remedy: Close the user lock by entering an invalid pass code in parameter 96.02 Pass code. See section Parameter checksum calculation.
A6B1 User pass code not confirmed	Cause: A new user pass code has been entered in parameter 96.100 but not confirmed in 96.101. Remedy: Confirm the new pass code by entering the same code in 96.101. To cancel, close the user lock without confirming the new code.
A6D1 FBA A parameter conflict	Cause: The drive does not have a functionality requested by a PLC, or requested functionality has not been activated. Remedy: Check PLC programming. Check settings of parameter group 50 Fieldbus adapter (FBA).
A6E5 AI parametrization	Cause: The current/voltage hardware setting of an analog input does not correspond to parameter settings. Check event log for auxiliary code identifying the input. Remedy: Adjust either the hardware setting (on the drive control unit) or parameter 12.15/12.25. Note: Control board reboot (cycling power or parameter 96.08) is required to validate hardware changes.
A6E6 ULC configuration	Cause: User load curve configuration error. Check auxiliary code: 0000: Speed points inconsistent. 0001: Frequency points inconsistent. 0002: Underload point above overload point. 0003: Overload point below underload point. Remedy: Check that each speed point (37.11…37.15) has a higher value than the previous point. Check that each frequency point (37.20…37.16) has a higher value than the previous point. Check that each overload point has a higher value than the corresponding underload point.
A6E7 IPC configuration warning	Cause: IPC configuration error. 0001: IPC incorrectly configured for EFB. 0002: IPC incorrectly configured for FBA. Remedy: If 0001: Check if param 76.21 is IPC and 58.01 is None/IPC. Ensure if 58.01 is None, 76.21 is IPC and 76.24 is EFB. If 0002: Check if param 76.21 is none of IPC, param 50.01 FBA A enable is set to Disable.
A6E8 IPC version mismatch	Cause: The master and follower(s) do not have the same IPC version and will not run in IPC mode. Remedy: Check 07.05 Firmware version of all drives on the IPC network. Load the drive(s) as needed with the desired firmware version.
A780 Motor stall	Cause: Motor is operating in stall region because of, for example, excessive load or insufficient motor power. Remedy: Check motor load and drive ratings. Check fault function parameters.
A783 Motor overload	Cause: Motor current is too high. Remedy: Check for overloaded motor. Adjust the parameters used for the motor overload function (35.51…35.53) and 35.55…35.56.
A784 Motor disconnect	Cause: All three output phases are disconnected from motor. Remedy: Check that switches between drive and motor are closed. Check that all cables between drive and motor are connected and secured. If no issue was detected and drive output was actually connected to motor, contact ABB.
A792 Brake resistor wiring	Cause: Brake resistor short circuit or brake chopper control fault. For drive frames R6 or larger. Remedy: Check brake chopper and brake resistor connection. Ensure brake resistor is not damaged.
A793 BR excess temperature	Cause: Brake resistor temperature has exceeded warning limit defined by parameter 43.12 Brake resistor warning limit. Remedy: Stop drive. Let resistor cool down. Check resistor overload protection function settings (parameter group 43 Brake chopper). Check warning limit setting, parameter 43.12. Check that the resistor has been dimensioned correctly.
A794 BR data	Cause: Brake resistor data has not been given. One or more of the resistor data settings (parameters 43.08…43.10) is incorrect. Aux Codes: 0001: Resistance value too low. 0002: Thermal time constant not given. 0003: Max continuous power not given. Remedy: Check value of 43.10 Brake resistance. Check value of 43.08 Brake resistor thermal tc. Check value of 43.09 Brake resistor Pmax cont.
A79C BC IGBT excess temperature	Cause: Brake chopper IGBT temperature has exceeded internal warning limit. Remedy: Let chopper cool down. Check for excessive ambient temperature. Check for cooling fan failure or obstructions in air flow. Check dimensioning and cooling of the cabinet. Check resistor overload protection function settings (43.06…43.10). Check minimum allowed resistor value for the chopper being used. Check that drive supply AC voltage is not excessive.
A7AB Extension I/O configuration failure	Cause: Installed extension module is not the same as configured. Remedy: Check that the installed extension module (shown by parameter 15.02) is the same as selected by parameter 15.01.
A7C1 FBA A communication	Cause: Cyclical communication between drive and fieldbus adapter module A or between PLC and fieldbus adapter module A is lost. Remedy: Check status of fieldbus communication. See user documentation of fieldbus interface. Check settings of parameter groups 50 Fieldbus adapter (FBA), 51, 52, and 53. Check cable connections. Check if communication master is able to communicate.
A7CE EFB comm loss	Cause: Communication break in embedded fieldbus (EFB) communication. Remedy: Check the status of the fieldbus master (online/offline/error etc.). Check cable connections to the EIA-485/X5 terminals 29, 30 and 31 on the control unit.
A7EE Panel loss	Cause: Control panel or PC tool selected as active control location for drive has ceased communicating. Remedy: Check PC tool or control panel connection. Check control panel connector and mounting platform. Disconnect and reconnect the control panel.
A88F Cooling fan	Cause: Maintenance timer limit exceeded. Remedy: Consider changing the cooling fan. Parameter 05.04 Fan on-time counter shows the running time of the cooling fan.
A8A0 AI supervision	Cause: An analog signal is outside the limits specified for the analog input. Remedy: Check signal level at the analog input. Check the wiring connected to the input. Check the minimum and maximum limits of the input in parameter group 12 Standard AI.
A8A1 RO life warning	Cause: The relay has changed states more than the recommended number of times. Remedy: Change the control board or stop using the relay output. Check the auxiliary code to identify the specific relay (0001: RO1, 0002: RO2, 0003: RO3).
A8A2 RO toggle warning	Cause: The relay output is changing states faster than recommended (e.g., fast changing frequency signal connected). Remedy: Replace the signal connected to the relay output source with a less frequently changing signal. Select a different signal with parameters 10.24 (RO1), 10.27 (RO2), or 10.30 (RO3).
A8B0 ABB Signal supervision 1	Cause: Warning generated by the signal supervision function 1. Remedy: Check the source of the warning (parameter 32.07 Supervision 1 signal).
A8B1 ABB Signal supervision 2	Cause: Warning generated by the signal supervision function 2. Remedy: Check the source of the warning (parameter 32.17 Supervision 2 signal).
A8B2 ABB Signal supervision 3	Cause: Warning generated by the signal supervision function 3. Remedy: Check the source of the warning (parameter 32.27 Supervision 3 signal).
A8B3 ABB Signal supervision 4	Cause: Warning generated by the signal supervision function 4. Remedy: Check the source of the warning (parameter 32.37 Supervision 4 signal).
A8B4 ABB Signal supervision 5	Cause: Warning generated by the signal supervision function 5. Remedy: Check the source of the warning (parameter 32.47 Supervision 5 signal).
A8B5 ABB Signal supervision 6	Cause: Warning generated by the signal supervision function 6. Remedy: Check the source of the warning (parameter 32.57 Supervision 6 signal).
A8BE ULC overload warning	Cause: Selected signal has exceeded the user overload curve. Remedy: Check for any operating conditions increasing the monitored signal (e.g., motor loading, torque, current). Check the definition of the load curve (parameter group 37 User load curve).
A8BF ULC underload warning	Cause: Selected signal has fallen below the user underload curve. Remedy: Check for any operating conditions decreasing the monitored signal (e.g., loss of load). Check the definition of the load curve (parameter group 37 User load curve).
A981 External warning 1	Cause: Fault in external device 1. Remedy: Check the external device. Check setting of parameter 31.01 External event 1 source.
A982 External warning 2	Cause: Fault in external device 2. Remedy: Check the external device. Check setting of parameter 31.03 External event 2 source.
A983 External warning 3	Cause: Fault in external device 3. Remedy: Check the external device. Check setting of parameter 31.05 External event 3 source.
A984 External warning 4	Cause: Fault in external device 4. Remedy: Check the external device. Check setting of parameter 31.07 External event 4 source.
A985 External warning 5	Cause: Fault in external device 5. Remedy: Check the external device. Check setting of parameter 31.09 External event 5 source.
AF80 INU-LSU comm loss	Cause: DDCS (fiber optic) communication between converters (e.g., inverter unit and supply unit) is lost. Remedy: Only for ACH580-31 and ACH580-34: Check status of other converter (parameters 06.36 and 06.39). Check settings of parameter group 60 DDCS communication. Check corresponding settings in the control program of the other converter. Check cable connections. If necessary, replace cables.
AF85 Line side unit warning	Cause: The supply unit (or other converter) has generated a warning. Remedy: Only for ACH580-31 and ACH580-34: Check the auxiliary code specifying the original warning. Refer to section "Auxiliary codes for the LSU supply unit warnings" For full information, see chapter "Fault tracing" in ACS880 IGBT supply control program firmware manual.
AF88 Season configuration warning	Cause: You have configured a season which starts before the previous season. Remedy: Configure the seasons with increasing start dates. See parameters 34.60 Season 1 start date ... 34.63 Season 4 start date.
AF90 Speed controller autotuning	Cause: The speed controller autotune routine did not complete successfully. Remedy: Check the auxiliary code and see actions for each code below.
AF90 (Aux: 0000) Autotune stopped	Cause: Drive was stopped before the autotune was complete. Remedy: Start the drive and repeat autotune until successful.
AF90 (Aux: 0001) Drive not ready	Cause: The drive was started and it was not ready to follow the autotune command. Remedy: Make sure the prerequisites of the autotune run are fulfilled. See section "Before activating the autotune routine"
AF90 (Aux: 0002) Torque ref not reached	Cause: Required torque reference could not be reached before the drive reached maximum speed. Remedy: Decrease the torque step (parameter 25.38). Or increase the speed step (parameter 25.39).
AF90 (Aux: 0003) Acceleration fail	Cause: Motor could not accelerate to maximum speed. Remedy: Increase the torque step (parameter 25.38). Or decrease the speed step (parameter 25.39).
AF90 (Aux: 0004) Deceleration fail	Cause: Motor could not decelerate to minimum speed. Remedy: Increase the torque step (parameter 25.38). Or decrease the speed step (parameter 25.39).
AF90 (Aux: 0005) Decel with full torque fail	Cause: Motor could not decelerate with full autotune torque. Remedy: Decrease the torque step (parameter 25.38). Or the speed step (parameter 25.39).
AF90 (Aux: 0006) Write error	Cause: Autotune could not write a parameter. Remedy: Run the drive one more time.
AF90 (Aux: 0007) Ramping down	Cause: Drive was ramping down when the autotune was activated. Remedy: Run the drive to the set point and start the autotune one more time.
AF90 (Aux: 0008) Ramping up	Cause: Drive was ramping up when the autotune was activated. Remedy: Wait until the drive reaches the set point and start autotune.
AF90 (Aux: 0009) Speed limits	Cause: Drive was running outside of autotune speed limits during the autotune activation. Remedy: Check the limits. Set the correct setpoint and repeat the autotune.
AFAA Autoreset	Cause: A fault is about to be autoreset. Remedy: Informative warning. See the settings in parameter group 31 Fault functions.
AFE1 Emergency stop (off2)	Cause: Drive has received an emergency stop (mode selection off2) command. Remedy: Check that it is safe to continue operation. Return emergency stop push button to normal position. Restart drive. If unintentional, check the source selected by parameter 21.05 Emergency stop source.
AFE2 Emergency stop (off1 or off3)	Cause: Drive has received an emergency stop (mode selection off1 or off3) command. Remedy: Check that it is safe to continue operation. Return emergency stop push button to normal position. Restart drive. If unintentional, check the source selected by parameter 21.05 Emergency stop source.
AFE9 Start delay	Cause: The start delay is active and the drive will start the motor after a predefined delay. Remedy: Informative warning. See parameter 21.22 Start delay.
AFED Run permissive	Cause: Run permissive is keeping the drive from running the motor. Remedy: Check the setting of (and source selected by) parameter 20.40 Run permissive.
AFEE Start interlock 1	Cause: Start interlock 1 is keeping the drive from starting. Remedy: Check the signal source selected for parameter 20.41 Start interlock 1.
AFEF Start interlock 2	Cause: Start interlock 2 is keeping the drive from starting. Remedy: Check the signal source selected for parameter 20.42 Start interlock 2.
AFF0 Start interlock 3	Cause: Start interlock 3 is keeping the drive from starting. Remedy: Check the signal source selected for parameter 20.43 Start interlock 3.
AFF1 Start interlock 4	Cause: Start interlock 4 is keeping the drive from starting. Remedy: Check the signal source selected for parameter 20.44 Start interlock 4.
AFF2 Run permissive forced warning	Cause: A forced DI is used as a source for parameter 20.40 Run permissive. Remedy: If 20.40 uses DIx as source, check if the bit corresponding to DIx in parameter 10.03 DI force selection is 1.
AFF3 Start interlock forced warning	Cause: One or more forced DIs is used as a source for one or more of parameters 20.41 ... 20.44. Remedy: Check all parameters 20.41 Start interlock 1 … 20.44 Start interlock 4. If any use DIx, check if the bit corresponding to DIx in parameter 10.03 DI force selection is 1.
AFF5 Override new start required	Cause: The Safe torque off function was active and has been reset while in Override. Remedy: A new start signal is required to start the drive again.
AFF6 Identification run	Cause: Motor ID run will occur at next start. Remedy: Informative warning.
AFF8 Motor heating active	Cause: Pre-heating is being performed. Remedy: Informative warning. Motor pre-heating is active. Current specified by parameter 21.16 Pre-heating current is being passed through the motor.
AFFE Override active	Cause: Drive is in Override mode. Remedy: Informative warning.
B5A0 STO event (Programmable: 31.22)	Cause: Safe torque off function is active (safety circuit signal connected to connector STO is lost). Remedy: Informative warning. Check safety circuit connections. See chapter "The Safe torque off function" in the Hardware manual. See description of parameter 31.22 STO indication run/stop
B5A2 Power applied	Cause: The drive was powered up or the control board was rebooted successfully. Remedy: Informative event.
B681 Hand mode selected	Cause: The drive was placed in Hand mode. Remedy: Informative event. Check the control panel to ensure that the current control location is correct.
B682 Off mode selected	Cause: The drive was placed in Off mode. Remedy: Informative event. Check the control panel to ensure that the current control location is correct.
B683 Auto mode selected	Cause: The drive was placed in Auto mode. Remedy: Informative event. Check the control panel to ensure that the current control location is correct.
B686 Checksum mismatch	Cause: The calculated parameter checksum does not match any enabled reference checksum. Remedy: See A686 Checksum mismatch
B687 Auto start command	Cause: The drive received a start command while in Auto mode. Remedy: Informative event.
B688 Auto stop command	Cause: The drive received a stop command while in Auto mode. Remedy: Informative event.
B689 Modulating started	Cause: The drive started modulating. Remedy: Informative event.
B68A Modulating stopped	Cause: The drive stopped modulating. Remedy: Informative event.
D501 No more available PFC motors	Cause: No more PFC motors can be started because they can be interlocked or in the Hand mode. Remedy: Check that there are no interlocked PFC motors, see parameters: 76.81…76.84. If all motors are in use, the PFC system is not adequately dimensioned to handle the demand.
D502 All motors interlocked	Cause: All the motors in the PFC system are interlocked. Remedy: Check that there are no interlocked PFC motors, see parameters 76.81…76.84.
D503 VSD controlled PFC motor interlocked	Cause: The motor connected to the drive is interlocked (unavailable). Remedy: Motor connected to the drive is interlocked and thus cannot be started. Remove the corresponding interlock to start the drive controlled PFC motor. See parameters 76.81…76.84.
D504 Damper timeout	Cause: Discharge air or outside air damper has timed out. Remedy: Check the auxiliary code, which identifies the parameter to be checked.
D504 (Aux: 0001) Discharge opening timeout	Cause: Discharge air damper was commanded to open and it timed out while opening. Remedy: See parameter 84.05.
D504 (Aux: 0002) Discharge closing timeout	Cause: Discharge air damper was commanded to close and it timed out while closing. Remedy: See parameter 84.08.
D504 (Aux: 0003) Outside opening timeout	Cause: Outside air damper was commanded to open and it timed out while opening. Remedy: See parameter 84.15.
D504 (Aux: 0004) Outside closing timeout	Cause: Outside air damper was commanded to close and it timed out while closing. Remedy: See parameter 84.18.
D50A Running dry (Prog: 82.20)	Cause: Dry run protection is activated. Remedy: Check the pump inlet for sufficient water level. Check dry run protection settings in parameters 82.20 Dry run protection and 82.21 Dry run source.
D50B Pipe fill-timeout (Prog: 82.25)	Cause: Soft pipe fill is reached the timeout limit. PID output not reached setpoint after ramping ended. Remedy: Check the pipe for possible leakage. See parameter 82.25 Soft pipe fill supervision and 82.26 Time-out limit.
D50C Maximum flow protection (Prog: 80.17)	Cause: Actual flow is exceeded the defined warning level. Remedy: Check the system for leakages. Check flow protection settings in parameters 80.15 Maximum flow, 80.17 Maximum flow protection, and 80.19 Flow check delay.
D50D Minimum flow protection (Prog: 80.18)	Cause: Actual flow is below the defined warning level. Remedy: Check that the inlet and outlet valves are open. Check flow protection settings in parameters 80.16 Minimum flow, 80.18 Minimum flow protection, and 80.19 Flow check delay.
D50E Outlet minimum pressure (Prog: 82.30)	Cause: Measured outlet pressure is below the defined warning limit. Remedy: Check the pump outlet for leakages. Check the configuration of outlet pressure protection. See parameters 82.30 Outlet minimum pressure protection and 82.31 Outlet minimum pressure warning level.
D50F Outlet maximum pressure (Prog: 82.35)	Cause: Measured outlet pressure is above the defined warning limit. Remedy: Check the pump outlet for blockages or closed valve. Check the configuration of outlet pressure protection. See parameters 82.35 Outlet maximum pressure protection and 82.37 Outlet maximum pressure warning level.
D510 Inlet minimum pressure (Prog: 82.40)	Cause: Measured inlet pressure is below the defined warning level. Remedy: Check the pump inlet for blockages or closed valve. Check the configuration of inlet pressure protection. See parameters 82.40 Inlet minimum pressure protection and 82.41 Inlet minimum pressure warning level.
D590 Restart delay	Cause: The restart delay is active. Remedy: Check parameter 21.40 Restart delay. The drive cannot be started until the restart delay has elapsed. The restart delay can be bypassed by setting parameter 21.42 Restart delay remaining to 0.
D590 (Aux: 0000) Unknown Aux	Cause: Auxiliary code 0000. Remedy: Contact your local ABB representative.
D590 (Aux: 0001) Unknown Aux	Cause: Auxiliary code 0001. Remedy: (No action specified in manual).
D590 (Aux: 0002) Pump short cycle	Cause: Pump short cycle protection. Remedy: (No action specified in manual, implied check pump cycling settings).
1080 Backup/Restore timeout	Cause: Control panel or PC tool has failed to communicate with the drive when backup was being made or restored. Remedy: Request backup or restore again.
1081 Rating ID fault	Cause: Drive software has not been able to read the rating ID of the drive. Remedy: Reset the fault to make the drive try to reread the rating ID. If the fault reappears, cycle the power to the drive. You may have to repeat this. If the fault persists, contact your local ABB representative.
2281 Calibration	Cause: Measured offset of output phase current measurement or difference between output phase U2 and W2 current measurement is too great (the values are updated during current calibration). Auxiliary codes: 0001 (U-phase), 0002 (V-phase), 0003 (W-phase), 0004 (Gain difference). Remedy: Try performing the current calibration again (select Current measurement calibration at parameter 99.13 ID run requested). If the fault persists, contact your local ABB representative.
2310 Overcurrent	Cause: Output current has exceeded internal fault limit. In addition to an actual overcurrent situation, this fault may also be caused by an earth fault or supply phase loss. (Aux code format XXXYYYZZ indicates phase/type). Remedy: Check the received auxiliary code to identify the phase (bit0=U, bit1=V, bit2=W). Check the motor load. Check acceleration times in parameter group 23 Speed reference ramp or 28 Frequency reference chain. Check parameters 46.01 Speed scaling, 46.02 Frequency scaling and 46.03 Torque scaling. Check the motor and motor cable (including phasing and delta/star connection). Check there are no contactors opening and closing in motor cable. Check that the start-up data in parameter group 99 Motor data corresponds to the motor rating plate. Check that there are no power factor correction capacitors or surge absorbers in motor cable. Check for an earth fault in motor or motor cables by measuring the insulation resistances.
2330 Earth leakage	Cause: Drive has detected load unbalance typically due to earth fault in motor or motor cable. Remedy: Check there are no power factor correction capacitors or surge absorbers in motor cable. Check for an earth fault in motor or motor cables by measuring the insulation resistances of motor and motor cable. Try running the motor in scalar control mode if allowed (See parameter 99.04 Motor control mode). If no earth fault can be detected, contact your local ABB representative.
2340 Short circuit	Cause: Short-circuit in motor cable(s) or motor. Remedy: Check motor and motor cable for cabling errors. Check there are no power factor correction capacitors or surge absorbers in motor cable. Cycle the power to the drive.
2381 IGBT overload	Cause: Excessive IGBT junction to case temperature. This fault protects the IGBT(s) and can be activated by a short circuit in the motor cable. Remedy: Check motor cable. Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up. Check motor power against drive power.
3130 Input phase loss	Cause: Intermediate circuit DC voltage is oscillating due to missing input power line phase or blown fuse. (Programmable fault: 31.21). Remedy: Check input power line fuses. Check for loose power cable connections. Check for input power supply imbalance.
3181 Wiring or earth fault	Cause: Incorrect input power and motor cable connection (ie. input power cable is connected to drive motor connection). (Programmable fault: 31.23). Remedy: Check input power connections.
3210 DC link overvoltage	Cause: Excessive intermediate circuit DC voltage. Remedy: Check that overvoltage control is on (parameter 30.30 Overvoltage control). Check that the supply voltage matches the nominal input voltage of the drive. Check the supply line for static or transient overvoltage. Check brake chopper and resistor (if present). Check deceleration time. Use coast-to-stop function (if applicable). Retrofit drive with brake chopper and brake resistor. Check that the brake resistor is dimensioned properly.
3220 DC link undervoltage	Cause: Intermediate circuit DC voltage is not sufficient because of a missing supply phase, blown fuse or fault in the rectifier bridge. Remedy: Check supply cabling, fuses and switchgear.
3385 Autophasing	Cause: Autophasing routine (see section Autophasing on page 194) has failed. Remedy: Try other autophasing modes (see parameter 21.13 Autophasing mode) if possible. Check that the motor ID run has been successfully completed. Check that the motor is not already turning when the autophasing routine starts. Check the setting of parameter 99.03 Motor type is Permanent magnet motor.
3381 Output phase loss	Cause: Motor circuit fault due to missing motor connection (all three phases are not connected). Remedy: Connect motor cable.
4110 Control board temperature	Cause: Control board temperature is too high. Remedy: Check proper cooling of the drive. Check the auxiliary cooling fan.
4210 IGBT overtemperature	Cause: Estimated drive IGBT temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up. Check motor power against drive power.
4290 Cooling	Cause: Drive module temperature is excessive. Remedy: Check ambient temperature. If it exceeds 40 °C/104 °F (IP21 frames R4…R9) or if it exceeds 50 °C /122 °F (IP21 frames R1…R9), ensure that load current does not exceed derated load capacity of drive. Check drive module cooling air flow and fan operation. Check inside of cabinet and heatsink of drive module for dust pick-up. Clean whenever necessary.
42F1 IGBT temperature	Cause: Drive IGBT temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up. Check motor power against drive power.
4310 Excess temperature	Cause: Power unit module temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up. Check motor power against drive power. Check the auxiliary code (FA Ambient temperature).
4380 Excess temperature difference	Cause: High temperature difference between the IGBTs of different phases. Remedy: Check the motor cabling. Check cooling of drive module(s).
4981 External temperature 1	Cause: Measured temperature 1 has exceeded fault limit. (Editable message text). Remedy: Check the value of parameter 35.02 Measured temperature 1. Check the cooling of the motor (or other equipment whose temperature is being measured).
4982 External temperature 2	Cause: Measured temperature 2 has exceeded fault limit. (Editable message text). Remedy: Check the value of parameter 35.03 Measured temperature 2. Check the cooling of the motor (or other equipment whose temperature is being measured).
4990 CPTC-02 not found	Cause: CPTC-02 extension module is not detected in option slot 2. Remedy: Power down the drive and check that the module is properly inserted in option slot 2. See also CPTC-02 user's manual.
4991 Safe motor temperature	Cause: The CPTC-02 module indicates overtemperature: motor temperature is too high, or the thermistor is in short-circuit or disconnected. Remedy: Check the cooling of the motor. Check the motor load and drive ratings. Check the wiring of the temperature sensor. Repair wiring if faulty. Measure the resistance of the sensor. Replace the sensor if faulty.
5080 Fan	Cause: Cooling fan feedback missing. Remedy: See A581 Fan (page 242).
5081 Auxiliary fan broken	Cause: An auxiliary cooling fan (connected to the fan connectors on the control unit) is stuck or disconnected. Remedy: Check the auxiliary code (0001 Fan 1, 0002 Fan 2) which identifies the broken fan. Check auxiliary fan(s) and connection(s). Replace fan if faulty. Make sure the front cover of the drive is in place and tightened. If cover is off for commissioning, set parameter 31.36 Aux fan fault function temporarily to 'No action'. Reboot the control unit (parameter 96.08) or cycle power.
5089 SMT circuit malfunction	Cause: Fault 4991 Safe motor temperature is generated but drive STO is not activated. Note: If only one STO channel is opened, fault FA81 or FA82 is generated. Remedy: Check connection between the relay output of the CPTC-02 module and the STO terminal. Check CPTC-02 module. Replace if faulty. See also CPTC-02 user's manual.
5090 STO hardware failure	Cause: STO hardware diagnostics has detected hardware failure. Remedy: Contact your local ABB representative for hardware replacement.
5091 Safe torque off	Cause: Safe torque off function is active, ie, safety circuit signal(s) connected to connector STO is broken during start or run. Remedy: Check safety circuit connections. For more information, see chapter 'The Safe torque off function' in the Hardware manual. Check description of parameter 31.22 STO indication run/stop. Check the value of parameter 95.04 Control board supply.
5092 PU logic error	Cause: Power unit memory has cleared. Remedy: Contact your local ABB representative.
5093 Rating ID mismatch	Cause: The hardware of the drive does not match the information stored in the memory. This may occur, for example, after a firmware update. Remedy: Cycle the power to the drive. You may have to be repeat this.
5094 Measurement circuit temperature	Cause: Problem with internal temperature measurement of the drive. Remedy: Contact your local ABB representative.
5098 I/O communication loss	Cause: Internal standard I/O communication failure. Remedy: Try resetting the fault or reboot the drive.
50A0 Fan	Cause: Cooling fan stuck or disconnected. Remedy: Check fan operation and connection. Replace fan if faulty.
5681 PU communication	Cause: Communication errors detected between the drive control unit and the power unit. Remedy: Check the connection between the drive control unit and the power unit. Check the value of parameter 95.04 Control board supply.
5682 Power unit lost	Cause: Connection between the drive control unit and the power unit is lost. Remedy: Check the connection between the control unit and the power unit.
5691 Measurement circuit ADC	Cause: Measurement circuit fault. Remedy: Contact your local ABB representative.
5692 PU board powerfail	Cause: Power unit power supply failure. Remedy: Contact your local ABB representative.
5693 Measurement circuit DFF	Cause: Measurement circuit fault. Remedy: Contact your local ABB representative.
5697 Charging feedback	Cause: Charging feedback signal missing. Remedy: Check the feedback signal coming from the charging system.
5698 Unknown PU fault	Cause: The power unit logic has generated a fault which is not known by the software. Remedy: Check the logic and software compatibility.
5E1A Charging circuit failure	Cause: Charging circuit is non-operational. Remedy: Only for ACH580-31. Contact your local ABB representative.
6181 FPGA version incompatible	Cause: Firmware and FPGA versions are incompatible. Remedy: Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power. If the problem persists, contact your local ABB representative.
6200 Checksum mismatch	Cause: The calculated parameter checksum does not match any enabled reference checksum. Remedy: See A686 Checksum mismatch (in manual page 244).
6306 FBA A mapping file	Cause: Fieldbus adapter A mapping file read error. Remedy: Contact your local ABB representative.
6481 Task overload	Cause: Internal fault. Remedy: Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power. If the problem persists, contact your local ABB representative.
6487 Stack overflow	Cause: Internal fault. Remedy: Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power. If the problem persists, contact your local ABB representative.
64A1 Internal file load	Cause: File read error. Remedy: Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power. If the problem persists, contact your local ABB representative.
64A4 Rating ID fault	Cause: Rating ID load error. Remedy: Contact your local ABB representative.
64A6 Adaptive program	Cause: Error running the adaptive program.
64B1 Internal SSW fault	Cause: Internal fault. Remedy: Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power. If the problem persists, contact your local ABB representative.
64B2 User set fault	Cause: Loading of user parameter set failed because: requested set does not exist, set is not compatible, or drive was switched off during loading. Remedy: Ensure that a valid user parameter set exists. Reload if uncertain.
64B3 Macro parameterization error	Cause: Loading of macro parameter set failed. Remedy: Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power. If the problem persists, contact your local ABB representative.
64E1 Kernel overload	Cause: Operating system error. Remedy: Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power. If the problem persists, contact your local ABB representative.
64FF Fault reset	Cause: A fault has been reset from the control panel, Drive composer PC tool, fieldbus or I/O. Remedy: Event. Informative only.
6581 Parameter system	Cause: Parameter load or save failed. Remedy: Try forcing a save using parameter 96.07 Parameter save manually. Retry.
6591 Backup/Restore timeout	Cause: During backup creating or restoring operation a control panel or PC tool has failed to communicate with the drive. Remedy: Check control panel or PC tool communication and if it is still in backup or restore state.
65A1 FBA A parameter conflict	Cause: The drive does not have a functionality requested by PLC, or requested functionality has not been activated. Remedy: Check PLC programming. Check settings of parameter groups 50 Fieldbus adapter (FBA) and 51 FBA A settings.
6681 EFB comm loss	Cause: Communication break in embedded fieldbus (EFB) communication. Remedy: Check the status of the fieldbus master (online/offline/error etc.). Check cable connections to the EIA-485/X5 terminals 29, 30 and 31 on the control unit.
6682 EFB config file	Cause: Embedded fieldbus (EFB) configuration file could not be read. Remedy: Contact your local ABB representative.
6683 EFB invalid parameterization	Cause: Embedded fieldbus (EFB) parameter settings inconsistent or not compatible with selected protocol. Remedy: Check the settings in parameter group 58 Embedded fieldbus.
6684 EFB load fault	Cause: Embedded fieldbus (EFB) protocol firmware could not be loaded. Version mismatch. Remedy: Contact your local ABB representative.
6685 EFB fault 2	Cause: Fault reserved for the EFB protocol application. Remedy: Check the documentation of the protocol.
6686 EFB fault 3	Cause: Fault reserved for the EFB protocol application. Remedy: Check the documentation of the protocol.
6882 Text 32-bit table overflow	Cause: Internal fault. Remedy: Reset the fault. Contact your local ABB representative if the fault persists.
6885 Text file overflow	Cause: Internal fault. Remedy: Reset the fault. Contact your local ABB representative if the fault persists.
7081 Control panel loss	Cause: Control panel or PC tool selected as active control location for drive has ceased communicating. Remedy: Check PC tool or control panel connection. Check control panel connector. Disconnect and reconnect the control panel.
7085 Incompatible option module	Cause: Fieldbus option module not supported. Remedy: Replace the module with a supported type.
7086 AI Overvoltage	Cause: An overvoltage has been detected on an analog input. AI signal level is beyond acceptable limits. Remedy: Check AI signal levels.
7100 Excitation current	Cause: Excitation current feedback low or missing. Remedy: (No specific remedy listed in source; usually implies checking motor/exciter connections).
7121 Motor stall	Cause: Motor is operating in stall region because of, for example, excessive load or insufficient motor power. Remedy: Check motor load and drive ratings. Check fault function parameters.
7122 Motor overload	Cause: Motor current is too high. Remedy: Check for overloaded motor. Adjust the parameters used for the motor overload function (35.51…35.53) and 35.55…35.56.
7181 Brake resistor	Cause: Brake resistor broken or not connected. Remedy: Check that a brake resistor has been connected. Check the condition of the brake resistor. Check the dimensioning of the brake resistor.
7183 BR excess temperature	Cause: Brake resistor temperature has exceeded fault limit defined by parameter 43.11. Remedy: Stop drive. Let resistor cool down. Check resistor overload protection function settings (parameter group 43 Brake chopper). Check fault limit setting, parameter 43.11 Brake resistor fault limit. Check that braking cycle meets allowed limits.
7184 Brake resistor wiring	Cause: Brake resistor short circuit or brake chopper control fault. Remedy: Check brake chopper and brake resistor connection. Ensure brake resistor is not damaged.
7191 BC short circuit	Cause: Short circuit in brake chopper IGBT. Remedy: Ensure brake resistor is connected and not damaged. Check the electrical specifications of the brake resistor. Replace brake chopper (if replaceable).
7192 BC IGBT excess temperature	Cause: Brake chopper IGBT temperature has exceeded internal fault limit. Remedy: Let chopper cool down. Check for excessive ambient temperature. Check for cooling fan failure. Check for obstructions in the air flow. Check resistor overload protection function settings (group 43). Check that braking cycle meets allowed limits. Check that drive supply AC voltage is not excessive.
7310 Overspeed	Cause: Motor is turning faster than highest allowed speed due to incorrectly set min/max speed, insufficient braking torque or load changes. Remedy: Check minimum/maximum speed settings, parameters 30.11 and 30.12. Check adequacy of motor braking torque. Check applicability of torque control. Check need for brake chopper and resistor(s).
73B0 Emergency ramp failed	Cause: Emergency stop did not finish within expected time. Remedy: Check the settings of parameters 31.32 Emergency ramp supervision and 31.33 Delay. Check the predefined ramp times (23.11…23.15 for mode Off1, 23.23 for mode Off3).
73F0 Overfrequency	Cause: Maximum allowed output frequency exceeded. Remedy: Check the auxiliary code.
7510 FBA A communication	Cause: Cyclical communication between drive and fieldbus adapter module A or PLC is lost. Remedy: Check status of fieldbus communication. See user documentation. Check settings of parameter groups 50 Fieldbus adapter, 51 FBA A settings, 52 Data in, 53 Data out. Check cable connections. Check if communication master is able to communicate.
7580 INU-LSU comm loss	Cause: DDCS communication between the inverter unit and the supply unit is lost. Remedy: Check status of the supply unit (parameter group 06). Check settings of parameter group 60 DDCS communication. Check cable connections. If necessary, replace cables.
7583 Line side unit faulted	Cause: The supply unit connected to the inverter unit has generated a fault. Remedy: The auxiliary code specifies the original fault code in the supply unit control program. See "Auxiliary codes for the LSU supply unit warnings" (page 269) or Firmware Manual.
7584 LSU charge failed	Cause: The supply unit was not ready (main contactor/breaker could not be closed) within expected time. Remedy: Check settings of parameter 94.10 LSU max charging time. Check that the supply unit is enabled, allowed to start, and can be controlled by the inverter.
8001 ULC underload fault	Cause: User load curve: Signal has been too long under the underload curve. Remedy: See parameter 37.04 ULC underload actions.
8002 ULC overload fault	Cause: User load curve: Signal has been too long over the overload curve. Remedy: See parameter 37.03 ULC overload actions.
80A0 AI supervision	Cause: An analog signal is outside the limits specified for the analog input. Remedy: Check signal level at the analog input. Check the auxiliary code. Check the wiring connected to the input. Check the minimum and maximum limits of the input in parameter group 12 Standard AI.
80B0 Signal supervision 1	Cause: Fault generated by the signal supervision function 1. Remedy: Check the source of the fault (parameter 32.07 Supervision 1 signal).
80B1 Signal supervision 2	Cause: Fault generated by the signal supervision function 2. Remedy: Check the source of the fault (parameter 32.17 Supervision 2 signal).
80B2 Signal supervision 3	Cause: Fault generated by the signal supervision function 3. Remedy: Check the source of the fault (parameter 32.27 Supervision 3 signal).
80B3 Signal supervision 4	Cause: Fault generated by the signal supervision function 4. Remedy: Check the source of the fault (parameter 32.37 Supervision 4 signal).
80B4 Signal supervision 5	Cause: Fault generated by the signal supervision function 5. Remedy: Check the source of the fault (parameter 32.47 Supervision 5 signal).
80B5 Signal supervision 6	Cause: Fault generated by the signal supervision function 6. Remedy: Check the source of the fault (parameter 32.57 Supervision 6 signal).
9081 External fault 1	Cause: Fault in external device 1. Remedy: Check the external device. Check setting of parameter 31.01 External event 1 source.
9082 External fault 2	Cause: Fault in external device 2. Remedy: Check the external device. Check setting of parameter 31.03 External event 2 source.
9083 External fault 3	Cause: Fault in external device 3. Remedy: Check the external device. Check setting of parameter 31.05 External event 3 source.
9084 External fault 4	Cause: Fault in external device 4. Remedy: Check the external device. Check setting of parameter 31.07 External event 4 source.
9085 External fault 5	Cause: Fault in external device 5. Remedy: Check the external device. Check setting of parameter 31.09 External event 5 source.
D404 Running dry	Cause: Dry run protection is activated. Remedy: Check the pump inlet for sufficient water level. Check dry run protection settings in parameters 82.20 Dry run protection and 82.21 Dry run source.
D405 Pipe fill-timeout	Cause: Soft pipe fill has reached timeout limit. The PID output is not reached the setpoint after reference ramping is ended and the timeout limit is elapsed. Remedy: Check the pipe for possible leakage. See parameter 82.25 Soft pipe fill supervision and 82.26 Time-out limit.
D406 Maximum flow protection	Cause: Actual flow is exceeded the defined fault level. Remedy: Check the system for leakages. Check flow protection settings in parameters 80.15 Maximum flow, 80.17 Maximum flow protection and 80.19 Flow check delay.
D407 Minimum flow protection	Cause: Actual flow is below the defined fault level. Remedy: Check that the inlet and outlet valves are open. Check flow protection settings in parameters 80.16 Minimum flow, 80.18 Minimum flow protection and 80.19 Flow check delay.
D408 Outlet minimum pressure	Cause: The measured outlet pressure is below the defined fault limit. Remedy: Check the pump outlet for leakages. Check the configuration of outlet pressure protection. See parameters 82.30 Outlet minimum pressure protection and 82.32 Outlet minimum pressure fault level.
D409 Outlet maximum pressure	Cause: The measured outlet pressure is above the defined fault limit. Remedy: Check the pump outlet for blockages or closed valve. Check the configuration of outlet pressure protection. See parameters 82.35 Outlet maximum pressure protection and 82.38 Outlet maximum pressure fault level.
D40A Inlet minimum pressure	Cause: The measured inlet pressure is below the defined fault level. Remedy: Check the pump inlet for blockages or closed valve. Check the configuration of inlet pressure protection. See parameters 82.40 Inlet minimum pressure protection and 82.42 Inlet minimum pressure fault level.
D40B Damper timeout (General)	Cause: Discharge air or outside air damper has timed out. Remedy: Check the auxiliary code, which identifies the parameter to be checked (see specific codes below).
D40B (Aux: 0001) Discharge air open timeout	Cause: Discharge air damper was commanded to open and it timed out while opening. Remedy: See parameter 84.05.
D40B (Aux: 0002) Discharge air close timeout	Cause: Discharge air damper was commanded to close and it timed out while closing. Remedy: See parameter 84.08.
D40B (Aux: 0003) Outside air open timeout	Cause: Outside air damper was commanded to open and it timed out while opening. Remedy: See parameter 84.15.
D40B (Aux: 0004) Outside air close timeout	Cause: Outside air damper was commanded to close and it timed out while closing. Remedy: See parameter 84.18.
D40C Multipump run permissive timeout	Cause: The run permissive setting configured with parameter 20.40 Run permissive was not satisfied within the time set in parameter 76.64 Run permissive timeout. Remedy: Check the signal source selected for parameter 20.40 Run permissive.
FA81 Safe torque off 1	Cause: Safe torque off function is active, that is, STO circuit 1 is broken. Remedy: Check safety circuit connections. See chapter "The Safe torque off function" in the Hardware manual. Check parameter 31.22 STO indication run/stop. Check the value of parameter 95.04 Control board supply.
FA82 Safe torque off 2	Cause: Safe torque off function is active, that is, STO circuit 2 is broken. Remedy: Refer to remedy for FA81.
FF61 ID run (General)	Cause: Motor ID run was not completed successfully. Remedy: Check nominal motor values in parameter group 99 Motor data. Check that no external control system is connected to the drive. Cycle the power to the drive. Check that no operation limits prevent completion. Check that the motor shaft is not locked.
FF63 STO diagnostics failure	Cause: SW internal malfunction. Remedy: Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power.
FF81 FB A force trip	Cause: A fault trip command has been received through fieldbus adapter A. Remedy: Check the fault information provided by the PLC.
FF8E EFB force trip	Cause: A fault trip command has been received through the embedded fieldbus interface. Remedy: Check the fault information provided by the PLC.
AE01 Overcurrent	Cause: Line side current has exceeded internal fault limit. Remedy: Check supply voltage. Check that there are no power factor correction capacitors or surge absorbers in supply cable. Check motor load and acceleration times. Check power semiconductors (IGBTs) and current transducers.
AE02 Earth leakage	Cause: IGBT supply has detected load unbalance (Programmable warning 31.120). Remedy: Check AC fuses. Check for earth leakages. Check supply cabling. Check power modules. Check there are no power factor correction capacitors or surge absorbers in supply cable. If no earth fault can be detected, contact your local ABB representative.
AE09 DC link overvoltage	Cause: Excessive intermediate circuit DC voltage. Note: This warning can be shown only when the IGBT supply unit is not modulating. Remedy: Check that parameter 95.01 Supply voltage is set according to the supply voltage in use.
AE0A DC link undervoltage	Cause: Intermediate circuit DC voltage is not sufficient due to missing phase in supply voltage, blown fuse or rectifier bridge internal fault. Note: This warning can be shown only when the IGBT supply unit is not modulating. Remedy: Check supply cabling, fuses and switchgear. Check that parameter 95.01 Supply voltage is set according to the supply voltage in use.
AE0B DC not charged	Cause: The voltage of the intermediate DC circuit has not yet risen to operating level. Remedy: Check the input voltage setting in parameter 95.01 Supply voltage. Check the input voltage. If the problem persists, contact your local ABB representative.
AE14 Excess temperature	Cause: Power unit temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up.
AE16 IGBT temperature	Cause: IGBT temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up.
AE19 Measurement circuit temperature	Cause: Problem with internal temperature measurement of the drive. Remedy: Contact your local ABB representative.
AE24 Voltage category unselected	Cause: The supply voltage range has not been defined. Remedy: Define the supply voltage range (parameter 95.01 Supply voltage).
AE56 INU-LSU comm loss	Cause: The communication to the inverter unit is lost. Remedy: Check the settings of parameter group 60 DDCS communication.
AE58 Emergency stop (off2)	Cause: IGBT supply unit has received an emergency stop (mode selection off2) command. Remedy: Check that it is safe to continue operation. Return emergency stop push button to normal position. Restart the IGBT supply unit.
AE78 Fan	Cause: Cooling fan is stuck or disconnected. Remedy: Check the auxiliary code in the line-side converter program to identify the fan. Check fan operation and connection. If the problem persists, contact your local ABB representative.
AE80 Auxiliary fan missing	Cause: Auxiliary fan is not connected or it is broken. Remedy: Contact your local ABB representative.
BE02 MCB maintenance notice	Cause: Main circuit breaker should be maintained. Remedy: Maintain the main circuit breaker.
2E00 Overcurrent	Cause: Line side current has exceeded internal fault limit. Remedy: Check supply voltage. Check that there are no power factor correction capacitors or surge absorbers in supply cable. Check motor load and acceleration times. Check power semiconductors (IGBTs) and current transducers.
2E01 Earth leakage	Cause: IGBT supply unit has detected an earth fault (Programmable warning 31.120). Remedy: Check AC fuses. Check for earth leakages. Check supply cabling. Check power modules. Check there are no power factor correction capacitors or surge absorbers in supply cable. If no earth fault can be detected, contact your local ABB representative.
2E02 Short circuit	Cause: IGBT supply unit has detected short circuit. Remedy: Check supply cable. Check there are no power factor correction capacitors or surge absorbers in supply cable. After correcting the cause of the fault, reboot the control unit (using parameter 96.108 LSU control board boot) or by cycling power.
3E00 Input phase loss	Cause: Input phase loss detected by the IGBT bridge (Programmable warning 31.121). Remedy: Check the AC fuses. Check for input power supply imbalance.
3E04 DC link overvoltage	Cause: Excessive intermediate circuit DC voltage. Remedy: Check that parameter 95.01 Supply voltage is set according to the supply voltage in use. Check that parameter 30.30 Overvoltage control is enabled.
3E05 DC link undervoltage	Cause: Intermediate circuit DC voltage is not sufficient because of a missing supply phase or blown fuse. Remedy: Check supply cabling, fuses and switchgear. Check that parameter 95.01 Supply voltage is set according to the supply voltage in use.
4E02 IGBT temperature	Cause: IGBT temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up.
5E01 Aux fan missing	Cause: Broken fan detected. Remedy: Replace the fan.
5E05 Rating ID mismatch	Cause: The hardware of the supply unit does not match the information stored in the memory unit. This may occur eg, after a firmware update or memory unit replacement. Remedy: Cycle the power to the supply unit. If the control unit is externally powered, reboot the control unit (using parameter 96.108 LSU control board boot) or by cycling its power. If the problem persists, contact your local ABB representative.
5E06 Main contactor fault	Cause: Control program does not receive main contactor on acknowledgement. Main contactor / main breaker is not functioning properly, or there is a loose / bad connection. Remedy: Check main contactor / main breaker control circuit wiring. Contact your local ABB representative.
5E08 Power unit lost	Cause: Connection between the control unit and power unit is lost. Remedy: Contact your local ABB representative.
5E09 PU board powerfail	Cause: Power unit power supply failure. Remedy: Contact your local ABB representative.
5E10 Charging feedback	Cause: Charging feedback signal missing. Remedy: Check charge contactor control circuit wiring. Contact your local ABB representative.
5E14 Measurement circuit temperature	Cause: Problem with internal temperature measurement of the drive. Remedy: Contact your local ABB representative.
7E11 DDCS controller comm loss	Cause: DDCS communication between supply unit and inverter unit has been lost. Remedy: Check the settings of parameter group 60 DDCS communication.

How to Read ACH580 Faults via Panel & BMS

The ACH580 is built for facility managers, offering multiple ways to diagnose issues without needing complex electrical tools:

• Hand-Off-Auto Panel (Primary Settings): The local panel is intuitive. Navigate to Menu > Diagnostics > Active Faults. The drive provides a “Help” button for each fault, offering possible causes (e.g., “Check inlet filters” or “Inspect belt tension”) directly on the screen.
• QR Code Diagnostics: For complex hardware trips, the ACH580 panel generates a dynamic QR code. Scanning this with your smartphone directs you to the specific troubleshooting page for that error, providing schematics and parts lists.
• BMS Integration (BACnet/IP): In large facilities, faults are monitored remotely. The ACH580 maps specific fault codes to BACnet objects. Ensure your BMS engineer checks the “Fault Word” to distinguish between a “Critical Trip” (stopping the fan) and a “Maintenance Warning” (dirty filter).

---

Frequently Asked Questions (FAQ)

Q: What is the difference between a Warning and a Fault on the ACH580?

A:

• Warning (A-Codes, e.g., A780): The drive detects an anomaly (like a “Broken Belt” detection based on torque loss) but continues to run to prevent air stagnation.
• Fault (Numeric Codes): The drive stops modulation immediately to protect the equipment or because safety interlocks (like a Freeze Stat) have tripped. The HOA panel LED turns solid red.

Q: How do I reset an ABB ACH580 fault?

A:

1. Press the Reset softkey on the Hand-Off-Auto panel.
2. Send a reset command via BACnet, Modbus, or N2 protocols.
3. Cycle the “Start/Stop” signal if configured for edge-triggered reset.
4. Note: Check for “Auto-Reset” configurations (Group 31) which may be masking recurring issues.

Q: What is “Fireman’s Override” and why does it generate a fault?

A: The ACH580 features an Override Mode (typically triggered by the fire alarm system) to run smoke extraction fans. When active, the drive ignores most non-critical faults (like Overload or Overheat) to keep the fan running at all costs. An “Override Active” message is logged to prove the drive was forced into this state, which is critical for post-incident insurance audits.