ABB ACH480 Drive

ABB ACH480 Drive Fault Codes:

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. See also aux codes: 0001 (U-phase upper), 0002 (U-phase lower), 0004 (V-phase upper), etc. 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 may cause the motor to rush uncontrollably. Check for overloads on the brake chopper or resistor.
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: If the problem persists, 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 (Editable message text)	Cause: Measured temperature 1 has exceeded warning limit. 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 (Editable message text)	Cause: Measured temperature 2 has exceeded warning limit. 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. Aux codes: – (none): Temperature above warning limit – 0001: Thermistor broken Remedy: Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up. For code 0001: 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 it exceeds 50 °C /122 °F, ensure that load current does not exceed derated load capacity. 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.
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.
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” = state (1: ID run, 2: normal). “Z” = index (1: Main fan 1, 2: Main fan 2, 3: Main fan 3). Check fan operation and connection. Replace fan if faulty.
A5A0 Safe torque off (Programmable warning 31.22)	Cause: Safe torque off function is active, i.e., safety circuit signal(s) connected to connector STO is lost. Remedy: Check safety circuit connections. See chapter “The Safe torque off function” in Hardware manual. 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…R4: Contact your local ABB representative. Frames R6…R11: Check specific aux codes (0001: U-phase IGBT, 0002: V-phase, etc.) and contact your local ABB representative. FAh code (1111 1010): Ambient temperature.
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). “X” specifies source (1: generic). “ZZZ” specifies the flash subsector number.
A686 Checksum mismatch	Cause: The calculated parameter checksum does not match any enabled reference checksum. Programmable warning: 96.54 Checksum action. 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. The drive is not dimensioned correctly. Aux codes: 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 [0.5…0.97]. Remedy: Check the auxiliary code. 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 start-up until 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 (page 214).
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. Remedy: Check the event log for an auxiliary code to identify the analog input in conflict. Adjust either the hardware setting (on the drive control unit) or parameter 12.15/12.25. Note: Control board reboot (via power cycle or param 96.08) is required to validate hardware changes.
A6E6 ULC configuration	Cause: User load curve configuration error. Aux codes: 0000: Speed points inconsistent. 0001: Frequency points inconsistent. 0002: Underload point above overload point. 0003: Overload point below underload point. Remedy: Check the auxiliary code and see actions below. 0000: Check speed points (37.11…37.15) increase in value. 0001: Check frequency points (37.20…37.16) increase in value. 0002/0003: Check overload points (37.31…37.35) vs underload points (37.21…37.25).
A6E7 IPC configuration warning	Cause: IPC configuration error. Aux codes: 0001: IPC incorrectly configured for EFB. 0002: IPC incorrectly configured for FBA. Remedy: Check the auxiliary code. 0001: Check parameters 76.21, 58.01, and 76.24. 0002: Check parameters 76.21 and 50.01.
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. Programmable warning: 31.24 Stall function. 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.
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. Check that braking cycle meets allowed limits.
A794 BR data	Cause: Brake resistor data has not been given. Aux codes: 0000 0001: Resistance value too low. 0000 0002: Thermal time constant not given. 0000 0003: Maximum continuous power not given. Remedy: Check settings in parameters 43.08…43.10 based on aux code. 0001: Check value of 43.10 Brake resistance. 0002: Check value of 43.08 Brake resistor thermal tc. 0003: 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. Check for obstructions in the air flow. Check the dimensioning and cooling of the cabinet. Check resistor overload protection function settings (parameters 43.06…43.10). Check minimum allowed resistor value for the chopper being used. Check that braking cycle meets allowed limits. 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. Programmable warning: 50.02. Remedy: Check status of fieldbus communication. See user documentation of fieldbus interface. Check settings of parameter groups 50 Fieldbus adapter (FBA), 51 FBA A settings, 52 FBA A data in and 53 FBA A data out. Check cable connections. Check if communication master is able to communicate.
A7CE EFB comm loss	Cause: Communication break in embedded fieldbus (EFB) communication. Programmable warning: 58.14. 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. Programmable warning: 49.05. Remedy: Check PC tool or control panel connection. Check control panel connector. Check mounting platform if being used. 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. Programmable warning: 12.03. 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. Aux code 0001: Relay output 1 Aux code 0002: Relay output 2 Aux code 0003: Relay output 3 Remedy: Change the control board or stop using the relay output. Check the auxiliary code to identify the specific relay output (1, 2, or 3).
A8A2 RO toggle warning	Cause: The relay output is changing states faster than recommended. Remedy: Replace the signal connected to the relay output source with a less frequently changing signal. Check the auxiliary code (e.g., 0001 for Relay output 1). Select a different signal with parameter 10.24 RO1 source.
A8B0 ABB Signal supervision 1 (Programmable warning: 32.06)	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 (Programmable warning: 32.16)	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 (Programmable warning: 32.26)	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 (Programmable warning: 32.36)	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 (Programmable warning: 32.46)	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 (Programmable warning: 32.56)	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 (Programmable fault: 37.03)	Cause: Selected signal has exceeded the user overload curve. Remedy: Check for any operating conditions increasing the monitored signal (for example, the loading of the motor if the torque or current is being monitored). Check the definition of the load curve (parameter group 37 User load curve).
A8BF ULC underload warning (Programmable fault: 37.04)	Cause: Selected signal has fallen below the user underload curve. Remedy: Check for any operating conditions decreasing the monitored signal (for example, loss of load if the torque or current is being monitored). Check the definition of the load curve (parameter group 37 User load curve).
A981 External warning 1 (Programmable warning: 31.01)	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 (Programmable warning: 31.03)	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 (Programmable warning: 31.05)	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 (Programmable warning: 31.07)	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 (Programmable warning: 31.09)	Cause: Fault in external device 5. Remedy: Check the external device. Check setting of parameter 31.09 External event 5 source.
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.
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. Then return emergency stop push button to normal position. Restart drive. If the emergency stop was 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. Then return emergency stop push button to normal position. Restart drive. If the emergency stop was 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 Run permissive uses DIx as the 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 Start interlock 1 … 20.44 Start interlock 4. Remedy: Check all parameters 20.41 Start interlock 1 … 20.44 Start interlock 4. If any of these parameters uses DIx as the source, 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 event: 31.22)	Cause: Safe torque off function is active, ie, safety circuit signal(s) connected to connector STO is lost. Remedy: Informative warning. Check safety circuit connections. For more information, 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 (Programmable event: 96.54)	Cause: The calculated parameter checksum does not match any enabled reference checksum. Remedy: See A686 Checksum mismatch (page 226).
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 (see below).
D504 (Aux: 0001) Damper timeout	Cause: Discharge air damper was commanded to open and it timed out while opening. Remedy: See parameter 84.05.
D504 (Aux: 0002) Damper timeout	Cause: Discharge air damper was commanded to close and it timed out while closing. Remedy: See parameter 84.08.
D504 (Aux: 0003) Damper timeout	Cause: Outside air damper was commanded to open and it timed out while opening. Remedy: See parameter 84.15.
D504 (Aux: 0004) Damper timeout	Cause: Outside air damper was commanded to close and it timed out while closing. Remedy: See parameter 84.18.
D50A Running dry (Programmable warning: 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 (Programmable warning: 82.25)	Cause: Soft pipe fill is reached the timeout limit. The PID output is not reached the setpoint after reference ramping is ended and 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.
D50C Maximum flow protection (Programmable warning: 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 (Programmable warning: 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 (Programmable warning: 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 (Programmable warning: 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 (Programmable warning: 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) Restart delay	Cause: Contact your local ABB representative. Remedy: Contact your local ABB representative.
D590 (Aux: 0002) Restart delay	Cause: Pump short cycle protection. Remedy: Wait for the delay to expire or check protection 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.
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. Remedy: Check the received auxiliary code (format XXXYYYZZ). The ZZ part indicates the overcurrent type and the phase (bit0=U, bit1=V, bit2=W). Bit7=1 indicates SW overcurrent. 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. Try running the motor in scalar control mode if allowed (See parameter 99.04). If no earth fault can be detected, contact your local ABB representative.
2340 Short circuit	Cause: Short-circuit in motor cable(s) or motor. Auxiliary codes: 0001: Short U-phase upper (R6-R11) 0002: Short U-phase lower (R6-R11) 0004: Short V-phase upper (R6-R11) 0008: Short V-phase lower (R6-R11) 0010: Short W-phase upper (R6-R11) 0020: Short W-phase lower (R6-R11) 0040: DC capacitor short circuit (R6-R11) 0080: State feedback mismatch (R6-R7) 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 (i.e. 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). 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 and the resistance is between acceptable range.
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.
3381 Output phase loss	Cause: Motor circuit fault due to missing motor connection (all three phases are not connected). (Programmable fault 31.19). 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 50 °C / 122 °F, ensure that load current does not exceed derated load capacity. 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.
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).
5080 Fan	Cause: Cooling fan feedback missing. Remedy: See A581 Fan (page 224 of 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, i.e., safety circuit signal(s) connected to connector STO is broken during start or run. (Programmable fault 31.22). Remedy: Check safety circuit connections. Check 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 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.
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 (page 226).
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. Check the auxiliary code (format XXYY ZZZZ). Remedy: “XX” specifies the number of the state (00=base program). “YY” specifies the number of the function block (0000=generic error). “ZZZZ” indicates the problem.
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 with control program 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. Check 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 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 between EFB protocol firmware and drive firmware. 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.
7082 I/O module comm loss	Cause: Communication between IO module and drive is not working properly. Remedy: Check the IO module installation.
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. Remedy: Check AI signal levels.
7087 I/O module configuration fault	Cause: I/O module configuration not supported or illegal. Remedy: See the auxiliary code.
7100 Excitation current	Cause: Excitation current feedback low or missing. Remedy: (No remedy specified in source)
7121 Motor stall	Cause: Motor is operating in stall region (e.g. 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 or obstructions. 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. Remedy: Check minimum/maximum speed settings (30.11, 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 and 31.33 (Ramp supervision). 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 between PLC and fieldbus adapter module A is lost. Remedy: Check status of fieldbus communication (see fieldbus user docs). Check settings of parameter groups 50 Fieldbus adapter (FBA), 51 FBA A settings, 52 FBA A data in, and 53 FBA A data out. Check cable connections. Check if communication master is able to communicate.
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 wiring connected to the input. Check minimum/maximum limits in parameter group 12 Standard AI. Aux Codes: 0001: AI1 Less MIN 0002: AI1 Greater MAX 0003: AI2 Less MIN 0004: AI2 Greater MAX
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 has not reached the setpoint after reference ramping ended. 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	Cause: Discharge air or outside air damper has timed out. Remedy: Check the auxiliary code to identify the parameter: 0001: Discharge air damper open fail (See 84.05). 0002: Discharge air damper close fail (See 84.08). 0003: Outside air damper open fail (See 84.15). 0004: Outside air damper close fail (See 84.18).
D40C Multipump run permissive timeout	Cause: The run permissive setting (20.40) was not satisfied within the time set in parameter 20.40 or 76.64. 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 Hardware manual. See parameter 31.22 STO indication run/stop. Check 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: Check safety circuit connections (See remedy for FA81).
FF61 ID run	Cause: Motor ID run was not completed successfully. Remedy: Check the 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. Restore default settings and try again. Check that the motor shaft is not locked. Auxiliary Codes: 0001: Max current limit too low (Check 99.06, 30.17). 0002: Max speed limit/field weakening too low (Check 30.11, 30.12, 99.07-99.09). 0003: Max torque limit too low (Check 99.12, Group 30). 0004: Current measurement calibration failed (Contact ABB). 0005-0008: Internal error (Contact ABB). 0009: Acceleration didn’t finish (Async motors). 000A: Deceleration didn’t finish (Async motors). 000B: Speed dropped to zero (Async motors). 000C: First accel fail (PM motors). 000D: Second accel fail (PM motors). 000E-0010: Internal error (Contact ABB). 0011: Pulse test error (Sync reluctance motors). 0012: Motor too large for advanced standstill ID run. 0013: Motor data error (Async motors).
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.