ABB ACS480 Drive Fault Codes & Troubleshooting List (2026)

Categories: Drives, PLC & HMI, Faults & Alarm

ABB ACS480 Drive Fault Codes & Troubleshooting List (2026) – Access the complete 2026 reference guide for ABB ACS480 fault codes. Learn to diagnose errors using the Primary Settings menu, Drive Composer, and the Drivetune App.

The ABB ACS480 is a compact “General Purpose” drive optimized for cabinet installations, widely used for pumps, fans, and compressors. Because it shares the same firmware architecture as the ACS580, it offers powerful diagnostic capabilities in a smaller footprint. When the drive trips, the Assistant Control Panel displays a 4-digit code (Hexadecimal or Decimal) alongside a text description.

This guide provides the most updated reference for 2026 to help you interpret these codes and restore your HVAC or pumping systems efficiently.

ACS480 Fault Codes Reference Table

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

Fault Code and MeaningCause and Remedy
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.
B686
Checksum mismatch
Cause: Parameter checksum 96.68 Actual checksumA does not match 96.71 Approved checksum A and/ or parameter checksum 96.69 Actual checksumB does not match 96.72 Approved checksum B.



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), 28 Frequency reference chain (frequency control). Also 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 of motor and motor cable. See chapter Electrical installation, section Checking the insulation of the assembly in the Hardware manual of the drive.

  • 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. See chapter Electrical installation, section Checking the insulation of the assembly in the Hardware manual.

  • 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 of motor and motor cable.

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

  • For frames R6 to R11, check the auxiliary code.
A2BA
IGBT overload
Cause: Excessive IGBT junction to case temperature. This warning protects the IGBT(s) and can be activated by a short circuit in the motor cable.



Remedy:

  • Check motor cable.

  • Check ambient conditions.

  • Check air flow and fan operation.

  • Check heatsink fins for dust pick-up.

  • Check motor power against drive power.
A3A1
DC link overvoltage
Cause: Intermediate circuit DC voltage too high (when the drive is stopped).



Remedy:

  • Check the supply voltage setting (parameter 95.01 Supply voltage). Note that the wrong setting of the parameter may cause the motor to rush uncontrollably, or may overload the brake chopper or resistor.

  • Check the supply voltage.

  • If the problem persists, contact your local ABB representative.
A3A2
DC link undervoltage
Cause: Intermediate circuit DC voltage too low (when the drive is stopped).



Remedy:

  • Check the supply voltage.

  • If the problem persists, contact your local ABB representative.
A3AA
DC not charged
Cause: The voltage of the intermediate DC circuit has not yet risen to operating level.



Remedy:

  • Check the supply voltage.

  • If the problem persists, contact your local ABB representative.
A490
Incorrect temperature sensor setup
Cause: Temperature cannot be supervised due to incorrect adapter setup. AO settings do not match with 35.11 and 35.21.



Remedy:

  • Check the settings of temperature source parameters 35.11 and 35.21.

  • Check the settings of temperature source parameters 35.11 and 35.21 against AO parameters 13.12 and 13.22.
A491
External temperature 1
Cause: Measured temperature 1 has exceeded warning limit. (Editable message text)



Remedy:

  • Check the value of parameter 35.02 Measured temperature 1.

  • Check the cooling of the motor (or other equipment whose temperature is being measured).

  • Check the value of 35.13 Temperature 1 warning limit.
A492
External temperature 2
Cause: Measured temperature 2 has exceeded warning limit. (Editable message text)



Remedy:

  • Check the value of parameter 35.03 Measured temperature 2.

  • Check the cooling of the motor (or other equipment whose temperature is being measured).

  • Check the value of 35.23 Temperature 2 warning limit.
A4A0
Control board temperature
Cause: Control unit temperature is too high.

Aux code (none): Temperature above warning limit.

Aux code 1: Thermistor broken.



Remedy:

  • Check the auxiliary code.

  • Check ambient conditions.

  • Check air flow and fan operation.

  • Check heatsink fins for dust pick-up.

  • If Aux code 1: Contact an ABB service representative for control unit 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 40 °C/104 °F or if it exceeds 50 °C /122 °F, ensure that load current does not exceed derated load capacity of drive. For all P55 frames, check the derating temperatures.

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

  • Check Aux code for location: 1: U-phase, 2: V-phase, 3: W-phase, 4: INT board, 6: Air inlet, 7: PCB compartment fan or power supply board, FA: Ambient temperature.
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. For frame sizes R6 or larger.



Remedy:

  • Check the auxiliary code to identify the fan. Code 0 denotes main fan 1. Other codes (format XYZ): “X” specifies state code (1: ID run, 2: normal). “Y” = 0, “Z” specifies the index of the fan (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
Cause: Safe torque off function is active, that is, safety circuit signal(s) connected to connector STO is lost.



Remedy:

  • Check safety circuit connections. For more information, chapter The Safe torque off function in the Hardware manual of the drive and 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. Aux code depends on control unit type.

Aux codes: 0001 (IGBT), 0003 (Board), 0006 (Power supply).



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.
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 (such as user logger triggering through parameters).

  • Check the auxiliary code (format XYYY YZZZ). “X” specifies the source of warning (1: generic flash erase supervision). “ZZZ” specifies the flash subsector number that generated the warning.
A686
Checksum mismatch
Cause: Parameter checksum 96.68 Actual checksumA does not match 96.71 Approved checksum A etc.



Remedy:

  • Revert parameter changes made after approving the checksum.

  • If parameter changes are valid, approve new checksum by setting parameter 96.55 Checksum control word bit 12 (Set approved checksum A) and/or 13 (Set approved checksum B) to 1 = Set.
A6A4
Motor nominal value
Cause: The motor parameters are set incorrectly. The drive is not dimensioned correctly.

Aux codes:

0001: Slip frequency too small.

0002: Sync and nominal speeds differ too much.

0003: Nom speed higher than sync speed.

0004: Nom current outside limits.

0005: Nom voltage outside limits.

0006: Nom power higher than apparent power.

0007: Nom power not consistent with speed/torque.



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 the start-up and continue until the motor data is entered.
A6A6
Voltage category unselected
Cause: The voltage category has not been defined.



Remedy:

  • Set voltage category in parameter 95.01 Supply voltage.
A6A7
System time not set
Cause: System time is not set. Timed functions cannot be used and fault log dates are not correct.



Remedy:

  • Set the system time manually or connect the control panel to the drive to synchronize the clock.

  • If basic control panel is used, synchronize the clock through the EFB or a fieldbus module.

  • Set parameter 34.10 Timed functions enable to Disabled to disable the timed functions if they are not used.
A6B0
User lock is open
Cause: The user lock is open, ie. user lock configuration parameters 96.100…96.102 are visible.



Remedy:

  • Close the user lock by entering an invalid pass code in parameter 96.02 Pass code. See section User lock (page 215).
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. See section User lock.
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. The code identifies the analog input whose settings are in conflict.

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

  • Note: Control unit reboot (either by cycling the power or through parameter 96.08 Control board boot) is required to validate any changes in the hardware settings.
A6E6
ULC configuration
Cause: User load curve configuration error.


Remedy:
Check the auxiliary code (format XXXX ZZZZ). “ZZZZ” indicates the problem:

  • 0000: Speed points inconsistent. Check that each speed point (37.11…37.15) has a higher value than the previous point.

  • 0001: Frequency points inconsistent. Check that each frequency point (37.20…37.16) has a higher value than the previous point.

  • 0002: Underload point above overload point. Check that each overload point (37.31…37.35) has a higher value than the corresponding underload point (37.21…37.25).

  • 0003: Overload point below underload point.
A780
Motor stall
Cause: Motor is operating in stall region because of, for example, excessive load or insufficient motor power.


Remedy:

  • Check motor load and drive ratings.

  • Check fault function parameters (31.24 Stall function).
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.


Remedy:
One or more of the resistor data settings (parameters 43.08…43.10) is incorrect. The parameter is specified by the auxiliary code:

  • 0001: Resistance value too low. Check value of 43.10.

  • 0002: Thermal time constant not given. Check value of 43.08.

  • 0003: Maximum continuous power not given. Check value of 43.09.
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.
A7A2
Mechanical brake opening failed
Cause: Status of mechanical brake acknowledgement is not as expected during brake open.


Remedy:

  • Check mechanical brake connection.

  • Check mechanical brake settings in parameter group 44 Mechanical brake control.

  • Check that acknowledgement signal matches the actual status of brake.
A7AB
Extension I/O configuration failure
Cause: I/O module is not connected to the device or parameterization conflict with connected I/O module.


Remedy:

  • Check that the I/O module is connected to the device.

  • Check that no parameters are connected to non-existing I/O parameters.
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 the 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. 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.


Remedy:

  • Check the status of the fieldbus master (online/offline/error etc.).

  • Check cable connections to the EIA-485/X5 terminals 29, 30 and 31 on the control unit.
A7EE
Panel loss
Cause: Control panel or PC tool selected as active control location for drive has ceased communicating.


Remedy:

  • Check PC tool or control panel connection.

  • Check control panel connector.

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


Remedy:

  • Check signal level at the analog input.

  • Check the wiring connected to the input.

  • Check the minimum and maximum limits of the input in parameter group 12 Standard AI.
A8A1
RO life warning
Cause: The relay has changed states more than the recommended number of times.


Remedy:
Change the control unit or stop using the relay output.

  • 0001: Relay output 1.

  • 0002: Relay output 2.

  • 0003: Relay output 3.
A8A2
RO toggle warning
Cause: The relay output is changing states faster than recommended (e.g., fast changing frequency signal connected). The relay lifetime will be exceeded shortly.


Remedy:
Replace the signal connected to the relay output source with a less frequently changing signal.

  • 0001: Relay output 1 (Check 10.24 RO1 source).

  • 0002: Relay output 2 (Check 10.27 RO2 source).

  • 0003: Relay output 3 (Check 10.30 RO3 source).
A8B0
ABB Signal supervision 1
Cause: Warning generated by the signal supervision function 1.


Remedy:

  • Check the source of the warning (parameter 32.07 Supervision 1 signal).
A8B1
ABB Signal supervision 2
Cause: Warning generated by the signal supervision function 2.


Remedy:

  • Check the source of the warning (parameter 32.17 Supervision 2 signal).
A8B2
ABB Signal supervision 3
Cause: Warning generated by the signal supervision function 3.


Remedy:

  • Check the source of the warning (parameter 32.27 Supervision 3 signal).
A8B3
ABB Signal supervision 4
Cause: Warning generated by the signal supervision function 4.


Remedy:

  • Check the source of the warning (parameter 32.37 Supervision 4 signal).
A8B4
ABB Signal supervision 5
Cause: Warning generated by the signal supervision function 5.


Remedy:

  • Check the source of the warning (parameter 32.47 Supervision 5 signal).
A8B5
ABB Signal supervision 6
Cause: Warning generated by the signal supervision function 6.


Remedy:

  • Check the source of the warning (parameter 32.57 Supervision 6 signal).
A8BE
ULC overload warning
Cause: Selected signal has exceeded the user overload curve.


Remedy:

  • Check for any operating conditions increasing the monitored signal (e.g., loading of the motor if torque/current is monitored).

  • Check the definition of the load curve (parameter group 37 User load curve).
A8BF
ULC underload warning
Cause: Selected signal has fallen below the user underload curve.


Remedy:

  • Check for any operating conditions decreasing the monitored signal (e.g., loss of load if torque/current is monitored).

  • Check the definition of the load curve (parameter group 37 User load curve).
A981
External warning 1
Cause: Fault in external device 1.


Remedy:

  • Check the external device.

  • Check setting of parameter 31.01 External event 1 source.
A982
External warning 2
Cause: Fault in external device 2.


Remedy:

  • Check the external device.

  • Check setting of parameter 31.03 External event 2 source.
A983
External warning 3
Cause: Fault in external device 3.


Remedy:

  • Check the external device.

  • Check setting of parameter 31.05 External event 3 source.
A984
External warning 4
Cause: Fault in external device 4.


Remedy:

  • Check the external device.

  • Check setting of parameter 31.07 External event 4 source.
A985
External warning 5
Cause: Fault in external device 5.


Remedy:

  • Check the external device.

  • Check setting of parameter 31.09 External event 5 source.
AF88
Season configuration warning
Cause: You have configured a season which starts before the previous season.


Remedy:

  • Configure the seasons with increasing start dates, see parameters 34.60 Season 1 start date…34.63 Season 4 start date.
AF90
Speed controller autotuning
Cause: The speed controller autotune routine did not complete successfully.


Remedy:
Check the auxiliary code:

  • 0000: Drive was stopped before autotune complete. Start drive and repeat until successful.

  • 0001: Drive started but not ready to follow autotune. Make sure prerequisites are fulfilled.

  • 0002: Required torque reference could not be reached. Decrease torque step (25.38) or increase speed step (25.39).

  • 0003: Motor could not accelerate to max speed. Increase torque step (25.38) or decrease speed step (25.39).

  • 0004: Motor could not decelerate to min speed. Increase torque step (25.38) or decrease speed step (25.39).

  • 0005: Motor could not decelerate with full autotune torque. Decrease torque step (25.38) or speed step (25.39).

  • 0006: Autotune could not write a parameter. Run the drive one more time.

  • 0007: Drive was ramping down when autotune activated. Run to set point and start autotune one more time.

  • 0008: Drive was ramping up when autotune activated. Wait until drive reaches set point and start autotune.

  • 0009: Drive was running outside of autotune speed limits. Check limits, set correct setpoint and repeat.
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:

  • 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.
AFEB
Run enable missing
Cause: No run enable signal is received.


Remedy:

  • Check setting of parameter 20.12 Run enable 1 source.

  • Switch signal on (for example, in the fieldbus Control Word) or check wiring of selected source.
AFED
Enable to rotate
Cause: Signal to rotate has not been received within a fixed time delay of 240 s.


Remedy:

  • Switch enable to rotate signal on (e.g. in digital inputs).

  • Check the setting of (and source selected by) parameter 20.22 Enable to rotate.
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.
B5A0
STO event
Cause: Safe torque off function is active, i.e. safety circuit signal(s) connected to connector STO is lost.



Remedy:

  • Informative warning. 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.
D50A
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.
D50B
Pipe fill-timeout
Cause: Soft pipe fill has reached the timeout limit. The PID output reached the setpoint after reference ramping ended and timeout limit elapsed.



Remedy:

  • Check the pipe for possible leakage.

  • See parameter 82.25 Soft pipe fill supervision and 82.26 Time-out limit.
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 (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.
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 cannot be started. The drive needs to be in remote control and start signal is activated.



Remedy:

  • Change control location to Auto.
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 ‘Manually force cleaning’ to ‘Start cleaning now’.
D511
Cavitation control
Cause: Cavitation control warning.



Remedy:

  • Check the auxiliary code. See actions for each code below.
0001
Cavitation detected warning
Cause: The pump is not getting enough liquid. Check the system.



Remedy:

  • Confirm that cavitation is occurring.

  • Check the fluid level in the system.

  • Adjust the parameters used for the cavitation detection function (86.12 – 86.30) if needed.
0002
Cavitation tune required
Cause: Cavitation control has been selected (86.11); however, there is missing data in 86.21 – 86.25.



Remedy:

  • Perform a cavitation curve autotune (86.20).

  • Manually enter the data used for the cavitation detection function (86.21 – 86.25) if autotune is not an option.

  • Disable cavitation control (86.11) if the above cannot be accomplished.
0003
Cavitation curve autotune
Cause: Cavitation curve autotune has been selected and will be performed on next start (in Hand).



Remedy:

  • Press Hand to run the autotune.

  • De-select the cavitation curve autotune (86.20) if tune is not desired.
D58B
Gas pressure outside limits
Cause: The compressor gas pressure is outside the limits.



Remedy:

  • Check the compressor gas pressure limits configured as AI min and max values.
D590
Restart delay
Cause: Compressor Restart delay.



Remedy:

  • Check parameter 21.40 Restart delay.

  • The drive cannot be started until the restart delay has elapsed.
001
Compressor short cycle protection
Cause: Short cycle protection active.



Remedy:

  • Wait until the restart delay has passed.
D591
Min. run time
Cause: Compressor minimum run time.



Remedy:

  • Check parameter 21.41 Minimum run time.

  • During the minimum run time the drive runs at the minimum speed/frequency.
D602
Cavitation tune completed
Cause: Cavitation auto tune has finished and stopped the drive.



Remedy:

  • Information only.
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.
2340
Short circuit
Cause: Short-circuit in motor cable(s) or motor.



Remedy:

  • Check motor and motor cable for cabling errors.

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

  • Cycle the power to the drive.

  • Auxiliary codes are shown below.
2310
Overcurrent
Cause: Output current has exceeded internal fault limit. Can be caused by earth fault or supply phase loss.



Remedy:

  • Check the auxiliary code (format XXXYYYZZ).

  • Check motor load.

  • Check acceleration times in parameter group 23 or 28.

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

  • Check for earth fault in motor or motor cables by measuring 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.

  • If no earth fault can be detected, contact your local representative.
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.



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



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



Remedy:

  • Connect motor cable.
4110
Control board temperature
Cause: Control unit 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.

  • Ensure that load current does not exceed derated load capacity of drive.

  • Check drive module cooling air flow and fan operation.

  • Check inside of cabinet and heatsink of drive module for dust pick-up. Clean whenever necessary.
42F1
IGBT temperature
Cause: Drive IGBT temperature is excessive.



Remedy:

  • Check ambient conditions.

  • Check air flow and fan operation.

  • Check heatsink fins for dust pick-up.

  • Check motor power against drive power.
4310
Excess temperature
Cause: Power unit module temperature is excessive.



Remedy:

  • See A4B0 Excess temperature.
4380
Excess temperature difference
Cause: High temperature difference between the IGBTs of different phases.



Remedy:

  • Check the motor cabling.

  • Check cooling of drive module(s).
4981
External temperature 1
Cause: Measured temperature 1 has exceeded fault limit.



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).
5080
Fan
Cause: Cooling fan feedback missing.



Remedy:

  • See A581 Fan.
5090
STO hardware failure
Cause: STO hardware diagnostics has detected hardware failure.



Remedy:

  • Contact your local ABB representative quoting the auxiliary code.

  • The code contains location information (especially with parallel-connected modules).

  • Check auxiliary binary bits (31…28 for inverter module number, etc).
5091
Safe torque off
(STO indication run/stop)
Cause: Safe torque off function is active; safety circuit signal connected to connector STO is broken during start or run.



Remedy:

  • Check safety circuit connections.

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

  • 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 (may occur after 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.
5089
SMT circuit malfunction
Cause: Safe motor temperature fault generated but STO event/fault not generated.



Remedy:

  • Check connection between the relay output of the module and the STO terminal.
5098
I/O communication loss
Cause: Communication failure to standard I/O.



Remedy:

  • Try resetting the fault.

  • Cycle the power to the drive.
50A0
Fan
Cause: Cooling fan stuck or disconnected.



Remedy:

  • Check fan operation and connection.

  • Replace fan if faulty.
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 problem persists, contact your local ABB representative.
6200
Checksum mismatch
Cause: Parameter checksum 96.68 (Actual A) != 96.71 (Approved A) or 96.69 (Actual B) != 96.72 (Approved B).



Remedy:

  • Revert parameter changes made after approving the checksum.

  • If changes are valid, approve new checksum by setting parameter 96.55 Checksum control word bit 12 (or 13) to 1.
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 (parameter 96.08) or cycle power.

  • If problem persists, contact your local ABB representative.
6487
Stack overflow
Cause: Internal fault.



Remedy:

  • Reboot the control unit (parameter 96.08) or cycle power.

  • If problem persists, contact your local ABB representative.
64A1
Internal file load
Cause: File read error.



Remedy:

  • Reboot the control unit (parameter 96.08) or cycle power.

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



Remedy:

  • Check the auxiliary code (format XXYY ZZZZ).

  • XX = State, YY = Function block, ZZZZ = Problem.

  • See specific sub-codes below.
64A6 (Aux: 000A)
Adaptive program
Cause: Program corrupted or block non-existent.



Remedy:

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



Remedy:

  • Check the inputs of the block.
64A6 (Aux: 0011)
Adaptive program
Cause: Program too large.



Remedy:

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



Remedy:

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



Remedy:

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



Remedy:

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



Remedy:

  • Check the parameter reference in the program.

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



Remedy:

  • Adapt the program to current block library and firmware version.
64B1
Internal SSW fault
Cause: Internal fault.



Remedy:

  • Reboot the control unit (parameter 96.08) or cycle power.

  • If problem persists, contact your local ABB representative.
64B2
User set fault
Cause: Loading of user parameter set failed (set missing, incompatible, or drive switched off during load).



Remedy:

  • Ensure that a valid user parameter set exists.

  • Reload if uncertain.
64E1
Kernel overload
Cause: Operating system error.



Remedy:

  • Reboot the control unit (parameter 96.08) or cycle power.

  • If 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.
6591
Backup/Restore timeout
Cause: Control panel or PC-tool failed to communicate during backup/restore.



Remedy:

  • Check control panel or PC-tool communication.
65A1
FBA A parameter conflict
Cause: Drive lacks functionality requested by PLC, or functionality not 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).



Remedy:

  • Check status of fieldbus master.

  • Check cable connections to EIA-485/X5 terminals 29, 30, 31.
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: EFB parameter settings inconsistent or not compatible with protocol.



Remedy:

  • Check the settings in parameter group 58 Embedded fieldbus.
6684
EFB load fault
Cause: EFB protocol firmware could not be loaded or version mismatch.



Remedy:

  • Contact your local ABB representative.
6685
EFB fault 2
Cause: Fault reserved for the EFB protocol application.



Remedy:

  • Check the documentation of the protocol.
6686
EFB fault 3
Cause: Fault reserved for the EFB protocol application.



Remedy:

  • Check the documentation of the protocol.
6882
Text 32-bit table overflow
Cause: Internal fault.



Remedy:

  • Reset the fault.

  • Contact your local ABB representative if fault persists.
6885
Text file overflow
Cause: Internal fault.



Remedy:

  • Reset the fault.

  • Contact your local ABB representative if fault persists.
7081
Control 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.

  • 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 (switched to voltage mode temporarily).



Remedy:

  • Check AI signal levels.
7087
I/O module configuration
Cause: I/O module configuration not supported or illegal.



Remedy:

  • Check the auxiliary code (see specific sub-codes below).
7087 (Aux: 0001)
I/O config
Cause: S1/S2 DIP switch position on BIO-01 has changed after power up.



Remedy:

  • Reboot control unit (cycle power or parameter 96.08) to activate new DIP switch position.
7087 (Aux: 0002)
I/O config
Cause: S1/S2 DIP switch positions are invalid (DO1 would be in both S1 and S2 pins).



Remedy:

  • Change S1/S2 DIP switch positions to a supported combination.

  • See parameter 05.99 BIO-01 DIP switch status.
7121
Motor stall
Cause: Motor is operating in stall region (excessive load or insufficient 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 parameters used for motor overload function (35.51…35.53 and 35.55…35.56).
7183
BR excess temperature
Cause: Brake resistor temperature has exceeded fault limit (param 43.11).



Remedy:

  • Stop drive. Let resistor cool down.

  • Check resistor overload protection settings (Group 43).

  • Check fault limit setting 43.11.

  • Check that braking cycle meets allowed limits.
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/obstructions.

  • Check resistor overload protection settings (Group 43).

  • Check braking cycle and drive supply AC voltage.
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 need for brake chopper and resistor.
73B0
Emergency ramp failed
Cause: Emergency stop did not finish within expected time.



Remedy:

  • Check settings of parameters 31.32 and 31.33 (Supervision).

  • Check predefined ramp times (23.11…23.15, 23.23).
73F0
Overfrequency
Cause: Maximum allowed output frequency exceeded.



Remedy:

  • Check the auxiliary code.
73F0 (Aux: 0xFA)
Overfrequency
Cause: Motor turning faster than allowed due to min/max freq settings or high supply voltage.



Remedy:

  • Check min/max frequency settings (30.13, 30.14).

  • Check used supply voltage and voltage selection parameter 95.01 Supply voltage.
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.
8001
ULC underload fault
Cause: User load curve: Signal has been too long under the underload curve.


Remedy:

  • See parameter 37.04 ULC underload actions.
8002
ULC overload fault
Cause: User load curve: Signal has been too long over the overload curve.


Remedy:

  • See parameter 37.03 ULC overload actions.
80A0
AI supervision
Cause: An analog signal is outside the limits specified for the analog input.


Remedy:

  • Check signal level at the analog input.

  • Check the auxiliary code (below).

  • Check the wiring connected to the input.

  • Check the minimum and maximum limits of the input in parameter group 12 Standard AI.
80A0: 0001
AI1LessMIN
Cause: Analog Input 1 value is less than minimum setting.


Remedy:

  • Check signal wiring and limits for AI1.
80A0: 0002
AI1GreaterMAX
Cause: Analog Input 1 value is greater than maximum setting.


Remedy:

  • Check signal wiring and limits for AI1.
80A0: 0003
AI2LessMIN
Cause: Analog Input 2 value is less than minimum setting.


Remedy:

  • Check signal wiring and limits for AI2.
80A0: 0004
AI2GreaterMAX
Cause: Analog Input 2 value is greater than maximum setting.


Remedy:

  • Check signal wiring and limits for AI2.
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.
D401
Max cleaning 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.
D404
Running dry
Cause: Dry run protection is activated.


Remedy:

  • Check the pump inlet for sufficient water level.

  • Check dry run protection settings in parameters 82.20 Dry run protection and 82.21 Dry run source.
D405
Pipe fill-timeout
Cause: Soft pipe fill has reached timeout limit. The PID output is not reached the setpoint after reference ramping is ended and the timeout limit is elapsed.


Remedy:

  • Check the pipe for possible leakage.

  • See parameter 82.25 Soft pipe fill supervision and 82.26 Time-out limit.
D40C
Cavitation detected
Cause: The pump is not getting enough liquid.


Remedy:

  • Check the fluid level in the system.

  • Restart the pump and confirm if cavitation is still occurring.

  • Adjust the parameters used for the cavitation detection function (86.12 – 86.30) if needed.
FA81
Safe torque off 1
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
Cause: Safe torque off function is active, ie. STO circuit 2 is broken.


Remedy:

  • Check safety circuit connections (same as FA81).

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

  • Check the auxiliary code below for specific causes.
FF61: 0001
Maximum current limit too low
Cause: Current limit restriction during ID run.


Remedy:

  • Check settings of parameters 99.06 Motor nominal current and 30.17 Maximum current.

  • Make sure that 30.17 > 99.06.

  • Check that the drive is dimensioned correctly according to the motor.
FF61: 0002
Maximum speed limit or calculated field weakening point too low
Cause: Speed/Frequency limits restricted.


Remedy:

  • Check settings of parameters: 30.11 Minimum speed, 30.12 Maximum speed, 99.07 Motor nominal voltage, 99.08 Motor nominal frequency, 99.09 Motor nominal speed.

  • Make sure that 30.12 > (0.55 × 99.09) > (0.50 × synchronous speed).

  • Make sure 30.11 ≤ 0.

  • Make sure supply voltage ≥ (0.66 × 99.07).
FF61: 0003
Maximum torque limit too low
Cause: Torque limit restricted.


Remedy:

  • Check settings of parameter 99.12 Motor nominal torque, and the torque limits in group 30 Limits.

  • Make sure that the maximum torque limit in force is greater than 100%.
FF61: 0004
Current measurement calibration
Cause: Calibration did not finish within reasonable time.


Remedy:

  • Contact your local ABB representative.
FF61: 0005…0008
Internal error
Cause: Internal software/hardware error during ID run.


Remedy:

  • Contact your local ABB representative.
FF61: 0009
Acceleration fail (Async motors)
Cause: Acceleration did not finish within reasonable time.


Remedy:

  • Contact your local ABB representative.
FF61: 000A
Deceleration fail (Async motors)
Cause: Deceleration did not finish within reasonable time.


Remedy:

  • Contact your local ABB representative.
FF61: 000B
Speed drop (Async motors)
Cause: Speed dropped to zero during ID run.


Remedy:

  • Contact your local ABB representative.
FF61: 000C
First accel fail (PM motors)
Cause: First acceleration did not finish within reasonable time.


Remedy:

  • Contact your local ABB representative.
FF61: 000D
Second accel fail (PM motors)
Cause: Second acceleration did not finish within reasonable time.


Remedy:

  • Contact your local ABB representative.
FF61: 000E…0010
Internal error
Cause: Internal error.


Remedy:

  • Contact your local ABB representative.
FF61: 0011
Pulse test error (Synch Reluctance)
Cause: Pulse test error.


Remedy:

  • Contact your local ABB representative.
FF61: 0012
Motor too large for advanced standstill ID run
Cause: Motor size incompatibility.


Remedy:

  • Check that the motor and drive sizes are compatible.

  • Contact your local ABB representative.
FF61: 0013
Motor data error (Async motors)
Cause: Motor data error.


Remedy:

  • Check that the motor nominal value settings in the drive are the same as in the motor nameplate.

  • Contact your local ABB representative.
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.

How to Read ACS480 Faults via Drive Composer

Diagnostics for the ACS480 in 2026 are intuitive thanks to the “All-Compatible” interface. You can access detailed fault data using the local panel or PC tools:

  • Primary Settings Menu: The ACS480 features a user-friendly “Primary Settings” menu on the control panel. Navigate to Diagnostics > Active Faults to see not just the code, but often a suggested remedy directly on the screen.
  • Drive Composer (PC Tool): Connect your laptop via the USB port on the panel. The “Event Logger” provides a timeline of the last 50 events. This is critical for identifying if faults coincide with specific times of day (e.g., morning startup spikes).
  • Bluetooth Connectivity: If using the Bluetooth Assistant Panel, the Drivetune App allows you to troubleshoot the drive without opening the cabinet door—a major safety advantage in 2026.

Frequently Asked Questions (FAQ)

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

A:

  • Warning (Codes starting with ‘A’): The drive notifies you of an issue (e.g., A793 “No Motor Load”) but continues running. This is common in pump applications where the line might be dry.
  • Fault (Numeric/Hex Codes): The drive stops modulation immediately (trips) to protect the equipment. The panel LED turns solid red.

Q: How do I reset an ABB ACS480 fault?

A:

  1. Press the Reset softkey on the control panel.
  2. Toggle the configured Digital Input (Parameter 20.01 defines the Reset command).
  3. Send a reset signal via the embedded Modbus RTU or Ethernet adapter.

Q: What should I check if I get an “Overcurrent” (2310) fault?

A: Overcurrent is the most common trip on ACS480 units.

  • Check the motor acceleration time (Group 23); if it’s too fast, the drive cannot supply enough current.
  • Inspect the motor and cable for insulation failure (earth fault).
  • Verify the mechanical load isn’t jammed.