ABB ACS280 Drive

ABB ACS280 Drive Fault Codes:

Fault Code and Meaning	Cause 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), 26 Torque reference chain (torque control) or 28 Frequency reference chain (frequency control). Check parameters 46.01 Speed scaling, 46.02 Frequency scaling and 46.03 Torque scaling. Check motor and motor cable (including phasing and delta/star connection). Check for an earth fault in motor or motor cables by measuring the insulation resistances. Check there are no contactors opening and closing in motor cable. Check that the start-up data in parameter group 99 Motor data corresponds to the motor rating plate. Check that there are no power factor correction capacitors or surge absorbers in motor cable.
A2B3 Earth leakage	Cause: Drive has detected load unbalance typically due to earth fault in motor or motor cable. Remedy: Check there are no power factor correction capacitors or surge absorbers in motor cable. Check for an earth fault in motor or motor cables by measuring the insulation resistances of motor and motor cable. If an earth fault is found, fix or change the motor cable and/or motor. If no earth fault can be detected, contact your local ABB representative.
A2B4 Short circuit	Cause: Short-circuit in motor cable(s) or motor. Remedy: Check motor and motor cable for cabling errors. Check motor and motor cable (including phasing and delta/star connection). Check for an earth fault in motor or motor cables by measuring 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, 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: Sensor type mismatch. Remedy: Check the settings of temperature source parameters 35.11.
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.
A4A1 IGBT overtemperature	Cause: Estimated drive IGBT temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up. Check motor power against drive power.
A4A9 Cooling	Cause: Drive module temperature is excessive. Remedy: Check ambient temperature. If it exceeds 50 °C / 122 °F, ensure that load current does not exceed derated load capacity 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 detected between the drive control unit and the power unit. Remedy: Check the connections between the drive control unit and the power unit.
A591 Drive HW initialization	Cause: Initialization of the drive hardware. Remedy: Check the auxiliary code. 0000: Wait for the setup to initialize (Drive hardware setup is initializing). 0001: Wait for the setup to initialize (Initializing HW settings for the first time).
A5A0 Safe torque off	Cause: Safe torque off function is active, ie safety circuit signal(s) connected to connector STO is lost. (Programmable warning: 31.22 STO indication run/stop). 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.
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.
A5EC PU communication internal	Cause: Communication errors detected between the drive control unit and the power unit. Remedy: Check the connections between the drive control unit and the power unit.
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.
A686 Checksum mismatch	Cause: The calculated parameter checksum does not match any enabled reference checksum. Remedy: Check that all necessary approved (reference) checksums (96.71…96.72) are enabled in 96.55 Checksum control word. Check the parameter configuration. Using 96.55 Checksum control word, enable a checksum parameter and copy the actual checksum into that parameter.
A687 Checksum configuration	Cause: An action has been defined for a parameter checksum mismatch but the feature has not been configured. Remedy: Contact your local ABB representative for configuring the feature, or disable the feature in 96.54 Checksum action.
A6A4 Motor nominal value	Cause: The motor parameters are set incorrectly. The drive is not dimensioned correctly. Remedy: Check the settings of the motor configuration parameters in group 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.
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.
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 parameter 12.15/12.25. Note: Control board 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. See actions for each code below: 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.16…37.20) 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. 0003: Overload point below underload point.
A783 Motor overload	Cause: Motor current is too high. Remedy: Check the motor, and the machinery coupled to motor, for overload. 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 if parameter 95.26 enables the use of a motor disconnect switch. If not, check the following: All switches between drive and motor are closed. 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.
A780 Motor stall	Cause: Motor is operating in stall region because of e.g. excessive load or insufficient motor power. (Programmable warning: 31.24 Stall function). Remedy: Check motor load and drive ratings. Check fault function parameters.
A791 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.
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 Brake resistor warning limit. 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: Check the resistor data settings (parameters 43.08…43.10).
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.
A7CE EFB comm loss	Cause: Communication break in embedded fieldbus (EFB) communication. (Programmable warning: 58.14 Communication loss action). Remedy: Check the status of the fieldbus master (online/offline/error etc.). Check cable connections to the EIA-485 terminals 25, 26, 27 and 28 on the control unit.
A7EE Panel loss	Cause: Control panel or PC tool selected as active control location for drive has ceased communicating. (Programmable warning: 49.05 Communication loss action). Remedy: Check PC tool or control panel connection. Check control panel connector. Check mounting platform if being used. Disconnect and reconnect the control panel.
A7AC Main IOMCU internal error	Cause: Calibration data is not stored in the main IOMCU. Analog signals are not working with full accuracy. Remedy: Contact ABB.
A8A0 AI supervision	Cause: An analog signal is outside the limits specified for the analog input. (Programmable warning: 12.03 AI supervision function). Remedy: Check signal level at the analog input. Check the wiring connected to the input. Check the minimum and maximum limits of the input in parameter group 12 Standard AI.
A8A1 RO life warning	Cause: The relay has changed states more than the recommended number of times. Remedy: Change the control board or stop using the relay output. If 0001 Relay output 1: Change the control board or stop using relay output 1.
A8A2 RO toggle warning	Cause: The relay output is changing states faster than recommended, e.g. if a fast changing frequency signal is connected to it. The relay lifetime will be exceeded shortly. Remedy: Replace the signal connected to the relay output source with a less frequently changing signal. For 0001 Relay output 1: Select a different signal with parameter 10.24 RO1 source.
A8B0 Signal supervision (Editable message text)	Cause: Warning generated by a signal supervision function. (Programmable warning: 32.06 Supervision 1 action). Remedy: Check the source of the warning (parameter 32.07 Supervision 1 signal).
A8B1 Signal supervision (Editable message text)	Cause: Warning generated by a signal supervision function. (Programmable warning: 32.16 Supervision 2 action). Remedy: Check the source of the warning (parameter 32.17 Supervision 2 signal).
A8B2 Signal supervision (Editable message text)	Cause: Warning generated by a signal supervision function. (Programmable warning: 32.26 Supervision 3 action). Remedy: Check the source of the warning (parameter 32.27 Supervision 3 signal).
A8B3 Signal supervision (Editable message text)	Cause: Warning generated by a signal supervision function. (Programmable warning: 32.36 Supervision 4 action). Remedy: Check the source of the warning (parameter 32.37 Supervision 4 signal).
A8B4 Signal supervision (Editable message text)	Cause: Warning generated by a signal supervision function. (Programmable warning: 32.46 Supervision 5 action). Remedy: Check the source of the warning (parameter 32.47 Supervision 5 signal).
A8B5 Signal supervision (Editable message text)	Cause: Warning generated by a signal supervision function. (Programmable warning: 32.56 Supervision 6 action). Remedy: Check the source of the warning (parameter 32.57 Supervision 6 signal).
A8C0 ULC invalid speed table	Cause: User load curve: X-axis points (speed) are not valid. Remedy: Check that points fulfill conditions. See parameter 37.11 ULC speed table point 1.
A8C1 ULC overload warning	Cause: User load curve: Signal has been too long over the overload curve. Remedy: See parameter 37.03 ULC overload actions.
A8C4 ULC underload warning	Cause: User load curve: Signal has been too long under the underload curve. Remedy: See parameter 37.04 ULC underload actions.
A8C5 ULC invalid underload table	Cause: User load curve: Underload curve points are not valid. Remedy: Check that points fulfill conditions. See parameter 37.21 ULC underload point 1.
A8C6 ULC invalid overload table	Cause: User load curve: Overload curve points are not valid. Remedy: Check that points fulfill conditions. See parameter 37.31 ULC overload point 1.
A8C8 ULC invalid frequency table	Cause: User load curve: X-axis points (frequency) are not valid. Remedy: Check that points fulfill conditions (-500.0 Hz to 500.0 Hz range). See parameter 37.16 ULC frequency table point 1.
A981 External warning 1 (Editable message text)	Cause: Fault in external device 1. (Programmable warning: 31.01 External event 1 source). Remedy: Check the external device. Check setting of parameter 31.01 External event 1 source.
A982 External warning 2 (Editable message text)	Cause: Fault in external device 2. (Programmable warning: 31.03 External event 2 source). Remedy: Check the external device. Check setting of parameter 31.03 External event 2 source.
A983 External warning 3 (Editable message text)	Cause: Fault in external device 3. (Programmable warning: 31.05 External event 3 source). Remedy: Check the external device. Check setting of parameter 31.05 External event 3 source.
A984 External warning 4 (Editable message text)	Cause: Fault in external device. (Programmable warning: 31.07 External event 4 source). Remedy: Check the external device. Check setting of parameter 31.07 External event 4 source.
A985 External warning 5 (Editable message text)	Cause: Fault in external device 5. (Programmable warning: 31.09 External event 5 source). Remedy: Check the external device. Check setting of parameter 31.09 External event 5 source.
AF8C Process PID sleep mode	Cause: The drive is entering sleep mode. Remedy: Informative warning. See section “Sleep and boost functions for process PID control” and parameters 40.43…40.48.
AF90 Autotune	Cause: The autotune routine has been interrupted. Remedy: The code contains an auxiliary value that specifies the reason for the abortion. For details, see section “Speed controller autotune”.
AFAA Autoreset	Cause: A fault is about to be autoreset. Remedy: Informative warning. See the settings in parameter group 31 Fault functions.
AFE1 Emergency stop (off2)	Cause: Drive has received an emergency stop (mode selection off2) command. Remedy: Check that it is safe to continue operation. Return emergency stop push button to normal position. Restart drive. If the emergency stop was unintentional, check the source selected by parameter 21.05 Emergency stop source.
AFE2 Emergency stop (off1 or off3)	Cause: Drive has received an emergency stop (mode selection off1 or off3) command. Remedy: Check that it is safe to continue operation and restart drive. Check the source of the emergency stop command.
AFEA Enable start signal missing (Editable message text)	Cause: No enable start signal received. Remedy: Check the setting of (and the source selected by) parameter 20.19 Enable start command.
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 (e.g. in the fieldbus Control Word) or check wiring of selected source.
AFED Enable to rotate	Cause: Signal enable to rotate has not been received within a fixed time delay of 240s. 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.
AFF7 Autophasing	Cause: Autophasing will occur at next start. Remedy: Informative warning.
B5A0 STO event	Cause: Safe torque off function is active, i.e. safety circuit signal(s) connected to connector STO is lost. (Programmable event: 31.22 STO indication run/stop). Remedy: Check safety circuit connections. For more information, see chapter “The Safe torque off function” in the hardware manual of the drive. See description of parameter 31.22 STO indication run/stop.
B686 Checksum mismatch	Cause: The calculated parameter checksum does not match any enabled reference checksum. (Programmable event: 96.54 Checksum action). Remedy: See A686 Checksum mismatch.
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 has not been able to read the rating ID of the drive. Remedy: Reset the fault to make the drive try to reread the rating ID. If the fault reappears, cycle the power to the drive. You may have to repeat this. If the fault persists, contact your local ABB representative.
2281 Calibration	Cause: Measured offset of output phase current measurement or difference between output phase U2 and W2 current measurement is too great (the values are updated during current calibration). 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), 26 Torque reference chain (torque control) or 28 Frequency reference chain (frequency control). Check parameters 46.01 Speed scaling, 46.02 Frequency scaling and 46.03 Torque scaling. Check motor and motor cable (including phasing and delta/star connection). Check there are no contactors opening and closing in motor cable. Check that the start-up data in parameter group 99 Motor data corresponds to the motor rating plate. Check that there are no power factor correction capacitors or surge absorbers in motor cable. Check for an earth fault in motor or motor cables by measuring the insulation resistances.
2330 Earth leakage	Cause: Drive has detected load unbalance typically due to earth fault in motor or motor cable. (Programmable fault: 30.20 Earth fault). Remedy: Check there are no power factor correction capacitors or surge absorbers in motor cable. Check for an earth fault in motor or motor cables by measuring the insulation resistances of motor and motor cable. Try running the motor in scalar control mode if allowed. (See parameter 99.04 Motor control mode.) If no earth fault can be detected, contact your local ABB representative.
2340 Short circuit	Cause: Short-circuit in motor cable(s) or motor. Aux code 0x0080 indicates that the state feedback from output phases does not match the control signals. Remedy: Check motor and motor cable for cabling errors. Check there are no power factor correction capacitors or surge absorbers in motor cable. Cycle the power to the drive.
2381 IGBT overload	Cause: Excessive IGBT junction to case temperature. This fault protects the IGBT(s) and can be activated by a short circuit in the motor cable. Remedy: Check motor cable. Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up. Check motor power against drive power.
3130 Input phase loss	Cause: Intermediate circuit DC voltage is oscillating due to missing input power line phase or blown fuse. Remedy: Check input power line fuses. Check for loose power cable connections. Check for input power supply imbalance.
3181 Cross connection	Cause: Incorrect input power and motor cable connection (ie. input power cable is connected to drive motor connection). (Programmable fault: 31.23 Wiring or earth fault). Remedy: Check input power connections.
3210 DC link overvoltage	Cause: Excessive intermediate circuit DC voltage. Remedy: Check that overvoltage control is on (parameter 30.30 Overvoltage control). Check that the supply voltage matches the nominal input voltage of the drive. Check the supply line for static or transient overvoltage. Check deceleration time. Use coast-to-stop function (if applicable). Retrofit drive with brake chopper and brake resistor. Check that the brake resistor is dimensioned properly and the resistance is between acceptable range.
3220 DC link undervoltage	Cause: Intermediate circuit DC voltage is not sufficient because of a missing supply phase, blown fuse or fault in the rectifier bridge. Remedy: Check supply cabling, fuses and switchgear.
3385 Autophasing	Cause: Autophasing routine has failed (see section Autophasing). Remedy: Check that the motor ID run has been successfully completed. Check that the motor is not already turning when the autophasing routine starts. Check the setting of parameter 99.03 Motor type.
3381 Output phase loss	Cause: Motor circuit fault due to missing motor connection (any of the three phases not connected). In scalar control mode, the drive detects fault only when the output frequency is above 10% of the motor nominal frequency. (Programmable fault: 31.19 Motor phase loss). Remedy: Connect motor cable. If the drive is in scalar mode and nominal current of the motor is less than 1/6 of the nominal output current of the drive, set parameter 31.19 Motor phase loss to No action.
4110 Control board temperature	Cause: Control board temperature is too high. Remedy: Check proper cooling of the drive. Check the auxiliary cooling fan.
4210 IGBT overtemperature	Cause: Estimated drive IGBT temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up. Check motor power against drive power.
4290 Cooling	Cause: Drive module temperature is excessive. Remedy: Check ambient temperature. If it exceeds 50 °C /122 °F, ensure that load current does not exceed derated load capacity of drive. Check drive module cooling air flow and fan operation. Check inside of cabinet and heatsink of drive module for dust pick-up. Clean whenever necessary.
42F1 IGBT temperature	Cause: Drive IGBT temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up. Check motor power against drive power.
4310 Excess temperature	Cause: Power unit module temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heatsink fins for dust pick-up. Check motor power against drive power.
4180 Excess temperature difference	Cause: High temperature difference between the IGBTs of different phases. Remedy: Check the motor cabling. Check cooling of drive module(s).
4981 External temperature 1	Cause: Measured temperature 1 has exceeded fault limit. (Editable message text). Remedy: Check the value of parameter 35.02 Measured temperature 1. Check the cooling of the motor (or other equipment whose temperature is being measured). Check the value of parameter 35.12 Temperature 1 fault limit.
5090 STO hardware failure	Cause: STO hardware diagnostics has detected hardware failure. Remedy: Contact your local ABB representative for hardware replacement.
5091 Safe torque off	Cause: Safe torque off function is active, ie. safety circuit signal(s) connected to connector STO is broken during start or run. (Programmable fault: 31.22 STO indication run/stop). Remedy: Check safety circuit connections. For more information, see chapter The Safe torque off function in the hardware manual and parameter 31.22.
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 eg. after a firmware update. Remedy: Cycle the power to the drive. You may have to repeat this.
5094 Measurement circuit temperature	Cause: Problem with internal temperature measurement of the drive. Remedy: Contact your local ABB representative.
5098 I/O communication loss	Cause: Communication failure to standard I/O. Remedy: Try resetting the fault or cycle the power to the drive.
50A0 Fan	Cause: Cooling fan stuck or disconnected. Remedy: Check fan operation and connection. Replace fan if faulty.
5681 PU communication	Cause: Communication errors detected between the drive control unit and the power unit. Remedy: Check the connection between the drive control unit and the power unit.
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.
5696 PU state feedback	Cause: State feedback from output phases does not match control signals. Remedy: Contact your local ABB representative.
5697 Charging feedback	Cause: Charging feedback signal missing. Remedy: Check the feedback signal coming from the charging system.
6181 FPGA version incompatible	Cause: Firmware and FPGA versions are incompatible. Remedy: Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power. If the problem persists, contact your local ABB representative.
6200 Checksum mismatch	Cause: The calculated parameter checksum does not match any enabled reference checksum. (Programmable event: 96.54 Checksum action). Remedy: See A686 Checksum mismatch (page 333).
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.
64A6 Adaptive program file incompatible or corrupted	Cause: Adaptive program has faulted. Remedy: Check the auxiliary code. See actions for each code below: 000A: Program corrupted or block non-existent. -> Restore the template program or download the program to the drive. 000C: Required block input missing. -> Check the inputs of the block. 000E: Program corrupted or block non-existent. -> Restore the template program or download the program to the drive. 0011: Program too large. -> Remove blocks until the error stops. 0012: Program is empty. -> Correct the program and download it to the drive. 001C: A non-existing parameter or block is used in the parameter. -> Edit the program to correct the parameter reference, or use an existing block. 001E: Output to parameter failed because the parameter was write-protected. -> Check the parameter reference in the program. Check for other sources affecting the target parameter. 0023: Program file incompatible with current firmware version. -> Adapt the program to current block library and firmware version. 0024: Program file incompatible with current firmware version. -> Adapt the program to current block library and firmware version. Other: Contact your local ABB representative, quoting the auxiliary code.
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.
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.
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 terminals 25, 26, 27 and 28 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: Replace the drive.
7086 I/O module AI Over voltage	Cause: Overvoltage detected in AI. AI is changed to voltage mode. AI will return automatically back to mA mode when the AI signal level is in accepted limits. Remedy: Check AI signal levels.
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 the motor, and the machinery coupled to motor, for overload. Adjust the parameters used for the motor overload function (35.51…35.53) and 35.55…35.56.
7183 BR excess temperature	Cause: Brake resistor temperature has exceeded fault limit defined by parameter 43.11 Brake resistor fault limit. Remedy: Stop drive. Let resistor cool down. Check resistor overload protection function settings (parameter group 43 Brake chopper). Check fault limit setting, parameter 43.11 Brake resistor fault limit. Check that braking cycle meets allowed limits.
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 and 30.12. 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 minimum/maximum frequency settings, parameters 30.13 and 30.14. Check adequacy of motor braking torque. Check applicability of torque control. Check need for brake chopper and resistor(s).
00FA Aux Code (Overspeed/freq)	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 and 30.14. Check used supply voltage and voltage selection parameter 95.01 Supply voltage.
Aux Other	Cause: – Remedy: Contact your local ABB representative, quoting the auxiliary code.
73B0 Emergency ramp failed	Cause: Emergency stop did not finish within expected time. Remedy: Check the settings of parameters 31.32 Emergency ramp supervision and 31.33 Emergency ramp supervision delay. Check the predefined ramp times (23.11…23.15 for mode Off1, 23.23 for mode Off3).
8001 ULC underload fault	Cause: User load curve: Signal has been too long under the underload curve. Remedy: See parameter 37.04 ULC underload actions.
8002 ULC overload fault	Cause: User load curve: Signal has been too long over the overload curve. Remedy: See parameter 37.03 ULC overload actions.
80A0 AI supervision	Cause: An analog signal is outside the limits specified for the analog input. Remedy: Check signal level at the analog input. Check the wiring connected to the input. Check 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 1 function. Remedy: Check the source of the fault (parameter 32.07 Supervision 1 signal).
80B1 Signal supervision 2	Cause: Fault generated by the signal supervision 2 function. Remedy: Check the source of the fault (parameter 32.17 Supervision 2 signal).
80B2 Signal supervision 3	Cause: Fault generated by the signal supervision 3 function. Remedy: Check the source of the fault (parameter 32.27 Supervision 3 signal).
80B3 Signal supervision 4	Cause: Fault generated by the signal supervision 4 function. Remedy: Check the source of the fault (parameter 32.37 Supervision 4 signal).
80B4 Signal supervision 5	Cause: Fault generated by the signal supervision 5 function. Remedy: Check the source of the fault (parameter 32.47 Supervision 5 signal).
80B5 Signal supervision 6	Cause: Fault generated by the signal supervision 6 function. 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 5 (per manual text). 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	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 and description of parameter 31.22.
FA82 Safe torque off 2	Cause: Safe torque off function is active, ie. STO circuit 2 is broken. Remedy: Check safety circuit connections.
FF61 ID run	Cause: Motor ID run was not completed successfully. Remedy: Check the nominal motor values in parameter group 99 Motor data. Check that no external control system is connected to the drive. Cycle the power to the drive. Check that no operation limits prevent the completion of the ID run. Restore parameters to default settings and try again. Check that the motor shaft is not locked.
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.