ABB ACQ80 Drive

ABB ACQ80 Drive Fault Codes:

Fault Code and MeaningCause and Remedy
64FF
Fault reset
Cause: A fault has been reset from the panel, Drive composer PC tool, fieldbus or I/O.



Remedy:

  • Event. Informative only.
A2A1
Current calibration
Cause: Current offset and gain measurement calibration will occur at next start.



Remedy:

  • Informative warning. (See parameter 99.13 ID run requested).
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) (torque control) or 28 Frequency reference chain (frequency control).

  • Check parameter 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 startup 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.

Aux codes:

01: Upper IGBT U-phase

02: Lower IGBT U-phase

04: Upper IGBT V-phase

08: Lower IGBT V-phase

10: Upper IGBT W-phase

20: Lower IGBT W-phase

40: DC capacitor short circuit



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 may cause the motor to rush uncontrollably.

  • 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:

  • If the problem persists, contact your local ABB representative.
A490
Incorrect temperature sensor setup
Cause: Sensor type mismatch.



Remedy:

  • Check the settings of temperature source parameters 35.11 and 35.21 against 91.21 and 91.25.
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 excessive. (1 – Sensor fault).



Remedy:

  • Check the sensor and change the control board.
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 40%/104 °F (frames R4…R8) or if it exceeds 50%/122 °F (frames R0…R8), 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.
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.
A580
PU communication
Cause: Communication errors between drive control unit and power unit.



Remedy:

  • Check connections between drive control unit and power unit.

  • Check value of parameter 95.04 Control board supply.
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 code. “Z” specifies index of the fan.

  • Check fan operation and connection.

  • Replace fan if faulty.
A582
Auxiliary fan missing
Cause: An auxiliary cooling fan (connected to the fan connectors on the control board) is stuck or disconnected.

0001: Auxiliary fan 1 missing

0002: Auxiliary fan 2 missing



Remedy:

  • Check the auxiliary code.

  • Check auxiliary fan(s) and connection(s).

  • Replace faulty fan.

  • Make sure the front cover of the drive is in place and tightened.
A591
Drive HW initialization
Cause: Drive hardware setup is initializing. (1 – Initializing HW settings for the first time).



Remedy:

  • See auxiliary code.
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 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:

  • 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.
A5F1
Redundant measurement
Cause: Duplicated measurements are beyond limits.



Remedy:

  • Contact your local ABB representative.
A5F2
Overtemperature hw
Cause: Excessive hardware temperature.



Remedy:

  • Contact your local ABB representative.
A682
Flash erase speed
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 (Parameter save manually) or cyclic parameter writes.

  • Check the auxiliary code (format XYYY YZZZ). “X” specifies warning source (1: generic). “ZZZ” specifies the flash subsector.
A6A4
Motor nominal value
Cause: The motor parameters are set incorrectly or the drive is not dimensioned correctly.



Remedy:
Check the auxiliary code:

  • Code 1: Slip frequency is too small. Check settings in groups 98 and 99. Check drive sizing.

  • Code 2: Synchronous and nominal speeds differ too much.

  • Code 3: Nominal speed is higher than synchronous speed with 1 pole pair.

  • Code 4: Nominal current is outside limits.

  • Code 5: Nominal voltage is outside limits.

  • Code 6: Nominal power is higher than apparent power.

  • Code 7: Nominal power not consistent with nominal speed and torque.
A6A5
No motor data
Cause: Parameters in group 99 have not been set.



Remedy:

  • Check that all required parameters in group 99 have been set.

  • Note: This warning is normal during startup 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.



Remedy:

  • Set the system time.
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.
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 groups 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 conflicting input.

  • Adjust either the hardware setting (on the control unit) or parameter 12.15/12.25.

  • Note: Control board reboot (power cycle or param 96.08) is required to validate hardware changes.
A780
Motor stall
Cause: Motor is operating in stall region. (Programmable warning 31.24).



Remedy:

  • Check motor load, drive ratings and 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, 35.55, 35.56).
A784
Motor disconnect
Cause: All three output phases are disconnected from motor.



Remedy:

  • Check if parameter 95.26 enables the use of a motor disconnect switch.

  • Check that all switches between drive and motor are closed.

  • Check that all cables between drive and motor are connected and secured.

  • If no issue detected, contact ABB.
A7AB
Built in/Extension I/O configuration failure
Cause: The I/O built in/extension module is not connected to the device properly.



Remedy:

  • Make sure that the I/O built in/extension module is connected to the device.
A7AC
I/O Module internal error
Cause: Calibration data is not stored in the I/O module. Analog signals are not working with full accuracy.



Remedy:

  • Replace I/O module.
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.

  • Check settings of parameter groups 50 (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).

  • Check cable connections to the EIA-485/X5 terminals 29, 30 and 31.
A7EE
Panel loss
Cause: Control panel or PC tool selected as active control location 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: Cooling fan failure or end of life.



Remedy:

  • Replace the drive cooling fan.
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.

  • Aux code 0001: Relay output 1

  • Aux code 0002: Relay output 2

  • Aux code 0003: Relay output 3
A8A0
AI supervision
Cause: Analog signal is beyond limits.



Remedy:

  • Check the signal level, input wiring, and the defined limits.

  • Aux code 1: AI1 less minimum

  • Aux code 2: AI1 greater maximum

  • Aux code 3: AI2 less minimum

  • Aux code 4: AI2 greater maximum
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.

  • Aux code 0001: Change signal source (Param 10.24)

  • Aux code 0002: Change signal source (Param 10.27)

  • Aux code 0003: Change signal source (Param 10.30)
A8B0
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
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
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
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
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
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).
A8B6
Current limit warning
Cause:

Motor actual current exceeded the limit defined in parameter 30.17 Maximum current.



Remedy:


  • Reduce the motor load.

  • Check for any jam or stall in motor.
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.
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:

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.
AFE2
Emergency stop (off1 or off3)
Cause:

Emergency stop (mode selection off1 or off3) command.



Remedy:

(Refer to drive documentation for specific restart procedure based on off1/off3 mode).
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.
AFEC
External power signal missing
Cause:

95.04 Control board supply is set to External 24V but no voltage is connected to the control unit.



Remedy:


  • Check the external 24 V DC power supply to the control unit.

  • Or change the setting of parameter 95.04.
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.
AF90
Speed controller autotuning
Cause:

The speed controller autotune routine did not complete successfully.



Remedy:

Check the auxiliary code below. See actions for each code.
B5F6
Identification run
Cause:

Motor ID run completed successfully.



Remedy:

Informative warning.
B5A0
STO event
Cause:

Safe torque off function is active, ie. safety circuit signal(s) connected to connector STO is lost.



Remedy:


  • Check safety circuit connections.

  • For more information, see chapter The Safe torque off function in the Hardware manual.

  • Check parameter 31.22 STO indication run/stop.
D505
Max cleaning warning
Cause:

Maximum number of cleanings are reached in defined time. The Pump cleaning is unable to clean the pump and hence, manual cleaning is required.



Remedy:


  • Check the pump for blockages.

  • Clean the pump manually if needed.

  • Check parameters 83.35 Cleaning count fault to 83.37 Maximum cleaning count.
D506
Pump cleaning not possible
Cause:

Pump cleaning not started as the drive is not in remote control.



Remedy:

Set the drive to remote control mode.
D507
Pump cleaning needed
Cause:

Dirt detection indicates that the pump needs cleaning but automatic pump cleaning is not allowed.



Remedy:


  • Perform pump cleaning manually.

  • Start pump cleaning by changing parameter 83.12 Start pump cleaning to Start cleaning now.
D50C
Maximum flow protection
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
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 Maximum flow, 80.18 Minimum flow protection, and 80.19 Flow check delay.
D50E
Outlet minimum pressure
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
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
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.
D5B0
Pump min speed
Cause:

This alarm occurs when the start command is provided and the actual speed of the motor (01.01) is not increasing above 79.51 Pump minimum speed within the time calculated by the drive software internally.



Remedy:


  • Check the pump minimum speed set in 79.51 Pump minimum speed.
D5B1
Start delay active
Cause:

This alarm occurs if more than three start occurs within one minute.



Remedy:

This warning resets automatically after five minutes and if start command is present, drive starts automatically.
FA90
STO diagnostics failure
Cause:

The software is not working properly.



Remedy:

Restart the control unit.
1080
Backup/Restore timeout
Cause: 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 is not 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).



Remedy:

  • Try performing the current calibration again.

  • 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 motor load.

  • Check acceleration times in parameter group 23 Speed reference ramp (speed control) or 28 Frequency reference chain (frequency control). Also check parameter 46.03 Torque scaling.

  • Check motor and motor cable (including phasing and delta/star connection).

  • Check there are no contactors opening and closing in motor cable.

  • Check that the startup data in parameter group 99 corresponds to the motor rating plate.

  • 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.
2330
Earth leakage
(Prog: 31.20 Earth fault)
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. Aux code 0x0080 indicates that the state feedback from output phases does not match the control signals.

Sub-codes:

01: U-phase upper IGBT

02: U-phase lower IGBT

04: V-phase upper IGBT

08: V-phase lower IGBT

10: W-phase upper IGBT

20: W-phase lower IGBT

40: DC capacitor short circuit



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.
2392
BU earth leakage
Cause: Total earth leakage of inverter modules is excessive.



Remedy:

  • Check there are no power factor correction capacitors or surge absorbers in motor cable.

  • Measure insulation resistances of motor cables and motor.

  • Contact your local ABB representative.
3130
Input phase loss
(Prog: 31.21 Supply phase loss)
Cause: Intermediate circuit DC voltage is oscillating due to missing input power line phase or blown fuse.



Remedy:

  • Check input power line fuses.

  • Check for loose power cable connections.

  • Check for input power supply imbalance.
3181
Wiring or earth fault
(Prog: 31.23)
Cause: Incorrect input power and motor cable connection (i.e. input power cable is connected to drive motor connection).



Remedy:

  • Check input power connections.
3210
DC link overvoltage
Cause: Excessive intermediate circuit DC voltage.



Remedy:

  • 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.
3291
DC voltage difference
Cause: Difference in DC voltages between parallel-connected inverter modules.



Remedy:

  • Contact your local ABB representative.
3293
DC unbalance fault
Cause: DC unbalance.



Remedy:

  • Contact your local ABB representative.
3381
Output phase loss
(Prog: 31.19 Motor 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 limit (40°C/104°F for R4-R8 or 50°C/122°F for R0-R8), ensure load current does not exceed derated 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.


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.


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).
4991
Safe motor temperature
Cause: The CPTC-02 module indicates overtemperature: motor temperature is too high, or the thermistor is in shortcircuit.


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 is stuck or disconnected.


Remedy:

  • Check fan operation and connection.

  • Replace fan if faulty.
5081
Auxiliary fan broken
Cause: An auxiliary cooling fan is stuck or disconnected (1 = Aux fan 1, 2 = Aux fan 2).


Remedy:

  • Check auxiliary fan(s) and connection(s).

  • Replace fan if faulty.
5089
SMT circuit malfunction
Cause: Safe motor temperature fault is generated and STO event/fault/warning is not generated.


Remedy:

  • Check connection between the relay output of the module and the STO terminal.

  • If Aux code 0001: Auxiliary fan 1 broken.

  • If Aux code 0002: Auxiliary fan 2 broken.
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.


Remedy:

  • Check safety circuit connections.

  • See chapter ‘The Safe torque off function’ in the Hardware manual.

  • 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 e.g. 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.
5095
Redundant measurement
Cause: Duplicated measurements are beyond limits.


Remedy:

  • Contact ABB.
5096
Overtemperature hw
Cause: Excessive hardware temperature.


Remedy:

  • Contact your local ABB representative.
5098
I/O communication loss
Cause: Communication failure to standard I/O.


Remedy:

  • Try resetting the fault or cycle the power to the drive.
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.
5690
PU communication internal
Cause: Internal communication error.


Remedy:

  • Contact your local ABB representative.
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.
5695
Reduced run
Cause: Configured power units not found.


Remedy:

  • Configure the power units.
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 generated a fault which is not known by software.


Remedy:

  • Check the logic and software compatibility.
50A0
Fan
Cause: Cooling fan stuck or disconnected.


Remedy:

  • Check fan operation and connection.

  • Replace fan if faulty.
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.
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.
64A3
Application loading
Cause: Application file incompatible or corrupted.


Remedy:

  • Check the auxiliary code. See actions for each code below.
8006
Not enough memory for the application
Cause: Not enough memory for the application.


Remedy:

  • Reduce the size of the application. Reduce the number of parameter mappings.

  • See the drive-specific log generated by Automation Builder.
8007
Wrong system library version
Cause: The application contains the wrong system library version.


Remedy:

  • Update the system library or reinstall Automation Builder.

  • See the drive-specific log generated by Automation Builder.
8008
Application is empty
Cause: The application is empty.


Remedy:

  • In Automation Builder, give a “Clean” command and reload the application.
8009
Application contains invalid tasks
Cause: The application contains invalid tasks.


Remedy:

  • In Automation Builder, check application task configuration, give a “Clean all” command, and reload the application.
800A
Unknown target library function
Cause: The application contains an unknown target (system) library function.


Remedy:

  • Update the system library or reinstall Automation Builder.

  • See the drive-specific log generated by Automation Builder.
64A4
Rating ID fault
Cause: Rating ID load error.


Remedy:

  • Contact ABB.
64A6
Adaptive program
Cause: Error running the adaptive program.


Remedy:

  • Check the auxiliary code (format XXYY ZZZZ).

  • “XX” specifies state (00=base program).

  • “YY” specifies function block (0000=generic error).

  • ”ZZZZ” indicates the problem (see specific ZZZZ codes below).
64A6 Aux: 000A
Program corrupted
Cause: Program corrupted or block non-existent.


Remedy:

  • Restore the template program or download the program to the drive.
64A6 Aux: 000C
Required block input missing
Cause: Required block input missing.


Remedy:

  • Check the inputs of the block.
64A6 Aux: 000E
Program corrupted
Cause: Program corrupted or block non-existent.


Remedy:

  • Restore the template program or download the program to the drive.
64A6 Aux: 0011
Program too large
Cause: Program too large.


Remedy:

  • Remove blocks until the error stops.
64A6 Aux: 0012
Program is empty
Cause: Program is empty.


Remedy:

  • Correct the program and download it to the drive.
64A6 Aux: 001C
Non-existing parameter/block
Cause: A non-existing parameter or block is used in the program.


Remedy:

  • Edit the program to correct the parameter reference, or to use an existing block.
64A6 Aux: 001D
Parameter type invalid
Cause: Parameter type invalid for selected pin.


Remedy:

  • Edit the program to correct the parameter reference.
64A6 Aux: 001E
Parameter write-protected
Cause: Output to parameter failed because the parameter was write-protected.


Remedy:

  • Check the parameter reference in the program.

  • Check for other sources affecting the target parameter.
64A6 Aux: 0023
Program file incompatible
Cause: Program file incompatible with current firmware version.


Remedy:

  • Adapt the program to current block library and firmware version.
64A6 Aux: 0024
Other
Cause: Other error.


Remedy:

  • Contact your local ABB representative, quoting the auxiliary code.
64B1
Internal SSW fault
Cause: A fatal error in the power-up phase of System Software (SSW). SSW runs in partial functionality mode.

Sub-codes:

1 – Starting OS time tick failed

2 – Creating system tasks failed

3 – Initializing file system failed

4 – Checking file system failed

5 – Initializing WoRm volumes failed

6 – Loading FPGA configuration failed

7 – Loading application program failed


Remedy:

  • 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: Macro parameterization failed (e.g., attempt to write a default value that cannot be changed).


Remedy:

  • Check parameter settings.
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.
6581
Parameter system
Cause: Parameter load or save failed.


Remedy:

  • Try forcing a save using parameter 96.07 (Parameter save manually).

  • Retry the operation.
6591
Backup/Restore timeout
Cause: During backup creating or restoring operation a panel or PC-tool has failed to communicate with the drive as part of this operation.


Remedy:

  • Check 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 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 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 installation of IO module.
7085
Incompatible option module
Cause: Fieldbus option module not supported.


Remedy:

  • Replace the module with a supported type.
7086
I/O module AI overvoltage
Cause: Overvoltage detected in AI. AI is changed to voltage mode from mA mode. AI will return automatically back to mA mode when the AI signal level is within acceptable limits.


Remedy:

  • Check AI signal levels.
7100
Excitation current
Cause: Excitation current feedback low or missing.


Remedy:

  • Contact your local ABB representative.
7121
Motor stall
Cause: Motor is operating in stall region because of 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, 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.
7310
Overspeed
Cause: Motor is turning faster than highest allowed speed due to incorrectly set minimum/maximum speed, insufficient braking torque or changes in load when using torque reference.


Remedy:

  • Check minimum/maximum speed settings, parameters 30.11 Minimum speed and 30.12 Maximum speed.

  • Check adequacy of motor braking torque.

  • Check applicability of torque control.

  • Check need for brake chopper and resistor(s).
73F0
Overfrequency
Cause: Maximum allowed output frequency exceeded.


Remedy:

  • Check the auxiliary code.
00FA
(Aux Code for Overfrequency)
Cause: Motor is turning faster than the highest allowed frequency due to incorrectly set minimum/maximum frequency or the motor rushes because of too high supply voltage or incorrect supply voltage selection in parameter 95.01.


Remedy:

  • Check minimum/maximum frequency settings, parameters 30.13 Minimum frequency and 30.14 Maximum frequency.

  • Check used supply voltage and voltage selection parameter 95.01 Supply voltage.
Other
(Aux Code)
Cause: –


Remedy:

  • Contact your local ABB representative, quoting 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 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.
8000
Unicos system error
Cause: System fault.


Remedy:

  • Power cycle.
8009
Current limit
Cause: Motor actual current exceeded the limit defined in parameter 30.17 Maximum current.


Remedy:

  • Reduce the motor load.

  • Check for any jam or stall in motor.

  • See parameter 30.17 Maximum current.
80A0
AI supervision
Cause: An analog signal is outside the limits specified for the analog input.

Aux Codes:

1 – AI1LessMIN

2 – AI1GreaterMAX

3 – AI2LessMIN

4 – AI2GreaterMAX


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.
FA81

Safe torque off 1 loss
Cause: Safe torque off function is active, ie. STO circuit 1 is broken.



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.
FA82

Safe torque off 2 loss
Cause: Safe torque off function is active, ie. STO circuit 2 is broken.



Remedy:



  • Check safety circuit connections.

  • For more information, see chapter The Safe torque off function in the Hardware manual.
D401

Max cleaning fault
(Aux: 83.35 Cleaning count fault)
Cause: The maximum number of cleanings are reached in the defined time. The pump cleaning is unable to clean the pump and hence, manual cleaning is required.



Remedy:



  • Check the pump for blockages.

  • Clean the pump manually if needed.

  • Check parameters 83.35 Cleaning count fault to 83.37 Maximum cleaning count.
D406

Maximum flow protection
(Aux: 80.17 Maximum flow protection)
Cause: Actual flow has 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

    • 80.19 Flow check delay
D407

Minimum flow protection
(Aux: 80.18 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 Maximum flow (Note: context implies min flow settings)

    • 80.18 Minimum flow protection

    • 80.19 Flow check delay
D408

Outlet minimum pressure
(Aux: 82.30 Outlet minimum pressure protection)
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
(Aux: 82.35 Outlet maximum pressure protection)
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
(Aux: 82.40 Inlet minimum pressure protection)
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.
D4B0

Running dry
Cause: Dry run protection is activated.



Remedy:



  • Check the pump inlet for sufficient water level.

  • Check dry run protection settings in parameter group 82 Pump protections.
D4B1

PV max volt
Cause: The DC bus voltage in the inverter is above the voltage set in 79.43 PV cell max voltage.



Remedy:



  • Check the number of PV cells connected in series.

  • Ensure that voltage is less than the voltage set in 79.43 PV cell max voltage.
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 (and its control unit, if powered separately).

  • Check that no operation limits prevent the completion of the ID run.

  • Restore parameters to default settings and try again.

  • 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.