ABB ACS530 Drive

ABB ACS530 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.
A2B1 Over current	Cause: Output current has exceeded internal fault limit. In addition to an actual overcurrent situation, this warning may also be caused by a ground fault or supply phase loss. Remedy: Check motor load. Check acceleration time in frequency reference chain (frequency control). Check parameters 46.01 Speed fieldbus scaled value, 46.02 Frequency fieldbus scaled value and 46.03 Torque fieldbus scaled value. Check motor and motor cable (including phasing and delta/star connection). Check for a ground 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 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 ground fault in motor or motor cable. Remedy: Check there are no power factor correction capacitors or surge absorbers in motor cable. Check for a ground fault in motor or motor cables by measuring the insulation resistances. If a ground fault is found, fix or change the motor cable and/or motor. If no ground 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 a ground 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 heat sink fins for dust pick-up. Check motor power against drive power.
A3A1 DC bus over voltage	Cause: Intermediate circuit DC voltage too high (when the drive is stopped). Remedy: Check the supply voltage setting (parameter 95.01 Supply volt). Note that the wrong setting may cause the motor to rush uncontrollably or overload the brake chopper. Check supply voltage. If the problem persists, contact your local ABB representative.
A3A2 DC bus under voltage	Cause: Intermediate circuit DC voltage too low (when the drive is stopped). Remedy: Check supply voltage. If the problem persists, contact your local ABB representative.
A3AA DC not charged	Cause: The voltage of the intermediate DC circuit has not yet risen to operating level. Remedy: If the problem persists, contact your local ABB representative.
A480 Motor cable overload	Cause: Calculated motor cable temperature has exceeded warning limit. Remedy: Check settings of parameters 35.61 and 35.62. Check the motor cable size against necessary load.
A490 Incorrect temperature sensor setup	Cause: Sensor type mismatch or faulty wiring between encoder interface module and temperature sensor. Remedy: Check the settings of temperature source parameters 35.11 and 35.21 corresponding to 91.24 and 91.21. Check the wiring of the sensor. Auxiliary code may identify interface module (0 = module 1, 1 = module 2).
A491 Ext Tmp1 (Editable message)	Cause: Measured temperature 1 has exceeded warning limit. Remedy: Check the value of parameter 35.02 Measured temperature 1. Check the cooling of the motor (or other equipment whose temperature is being measured).
A492 Ext Tmp2 (Editable message)	Cause: Measured temperature 2 has exceeded warning limit. Remedy: Check the value of parameter 35.03 Measured temperature 2. Check the cooling of the motor (or other equipment whose temperature is being measured).
A4A0 Control board temperature	Cause: Control unit overtemperature. (Aux code N/A: Temp exceeded limit; Aux code 1: Thermistor broken). Remedy: 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 heat sink 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 (R5…R9) or 50°C/122°F (B0…R9), ensure load current does not exceed derated capacity. Check drive module cooling air flow and fan operation. Check inside of cabinet and heatsink of drive module for dust pick-up. Clean whenever necessary.
A4B0 Excess temperature	Cause: Power unit module temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heat sink 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 motor cabling. Check cooling of the drive module(s).
A4B2 PCB plate cooling	Cause: Temperature difference between ambient and drive module PCB space is excessive. Remedy: Check the cooling fan inside PCB plate.
A4F6 IGBT temperature	Cause: Drive IGBT temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heat sink 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 connection between the drive control unit and the power unit.
A581 Fan	Cause: Cooling fan is stuck or disconnected. Remedy: Check auxiliary code to identify fan. Code 0: Main fan 1. Other codes (Format XYZ): X=Status (1:ID, 2:Normal), Y=BCU Index, Z=Fan Index (0-2: Main fans, 3-5: Aux fans, 6-8: Filter fans). Check fan operation and connection. Replace faulty fan.
A582 Auxiliary fan lost	Cause: Auxiliary cooling fan (connected to fan connector of control unit) is stuck or disconnected. Remedy: Check auxiliary fan(s) and connection(s). Replace faulty fan. Ensure the front cover of transmission module is correctly positioned and fastened.
A5A0 Delete safe torque (STO indication)	Cause: Delete safe torque function is active, i.e. safety circuit signal(s) connected to connector STO is lost. Remedy: Check safety circuit connections. See chapter Delete safe torque function and 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 internal 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.
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.
A5F3 Switch frequency is below requirement	Cause: Due to limited switch frequency (e.g. param 95.15), sufficient motor control cannot be reached under required output frequency. Remedy: Informative warning.
A683 Data saving to power unit	Cause: An error in saving data to the power unit. Remedy: Contact local ABB representative.
A684 SD card	Cause: Error related to SD card used to store data (BCU control unit only). Remedy: Code 1 (No SD card): Insert a compatible and writeable SD card. Code 2: SD card write-protected. Code 3: SD card is non-writeable.
A685 Power fail saving	Cause: Power fail saving is requested too frequently due to oscillating power supply. Remedy: Check the power supply of the control unit. If powered internally, check the supply voltage of the transmission.
A6A4 Motor nominal value	Cause: Motor parameters are set incorrectly or drive not dimensioned correctly. Remedy: Check motor configuration parameters in group 99. Check that the drive is sized correctly for the motor. Aux 1: Slip frequency too small (Check Grp 98/99). Aux 2: Synchronous speed differs too much. Aux 3: Nominal speed higher than sync speed with 1 pole pair. Aux 4: Nominal current outside limits. Aux 5: Nominal voltage outside limits. Aux 6: Nominal power higher than apparent power.
A6A5 No motor data	Cause: Parameters in group 99 have not been set. Remedy: Set motor parameters in group 99.
A6A6 Voltage category unselected	Cause: The voltage category has not been defined. Remedy: Set voltage category in parameter 95.01 Supply volt.
A6D1 FBA A parameter conflict	Cause: Drive does not have functionality requested by PLC, or functionality not activated. Remedy: Check PLC programming. Check settings of parameter groups 50 Fieldbus adapter (FBA).
A6E5 AI parameterization	Cause: The current/voltage hardware setting of an analog input does not correspond to parameter settings. Remedy: Check event record of auxiliary code to identify the conflicting analog input. Adjust hardware setting (on control unit) or parameter 12.15/12.25. Reboot control board (Cycle power or Param 96.08) to validate changes.
A6E6 ULC configuration	Cause: User load curve configuration error. (See auxiliary codes below). Remedy: Check the auxiliary code (format XXXX ZZZZ). See specific actions below.
A6E6 (Aux: 0000) Speed points inconsistent	Cause: Speed points inconsistent. Remedy: Check that each speed point (parameters 37.11…37.15) has a higher value than the previous point.
A6E6 (Aux: 0001) Frequency points inconsistent	Cause: Frequency points inconsistent. Remedy: Check that each frequency point (37.20…37.16) has a higher value than the previous point.
A6E6 (Aux: 0002) Underload point above overload	Cause: Underload point above overload point. Remedy: Check that each overload point (37.31…37.25) has a higher value than the corresponding underload point (37.21…37.25).
A6E6 (Aux: 0003) Overload point below underload	Cause: Overload point below underload point. Remedy: Check parameters for overload/underload points.
A780 Motor stall	Cause: Motor is operating in stall region because of, e.g., excessive load or insufficient motor power. Remedy: Check the motor load and drive ratings. Check fault function parameters.
A781 Motor fan	Cause: Feedback from external fan is not received. Remedy: Check external fan one by one (or other controllable equipment).
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.
A791 Brake resistors	Cause: Brake resistor broken or not connected. Remedy: Check that a brake resistor has been connected. Check the condition of the brake resistor.
A793 Brake resistor temperature is excessive	Cause: Brake resistor temperature has exceeded warning limit defined by parameter 43.12. Remedy: Stop the 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).
A79B Short circuit in brake chopper	Cause: Short circuit in brake chopper IGBT. Remedy: Replace brake chopper (if external). Drives with internal choppers will need to be returned to ABB. Ensure connection and no damages to brake resistor.
A79C BC IGBT excess temperature	Cause: Brake chopper IGBT temperature has exceeded internal warning limit. Remedy: Let chopper cool down. Check for excessive ambient temperature. Check for cooling fan failure. Check for obstructions in the air flow. Check the dimensioning and cooling of the cabinet. Check resistor overload protection function settings (parameters 43.06…43.10). Check minimum allowed resistor value for the chopper being used. Check that braking cycle meets allowed limits. Check that drive supply AC voltage is not excessive.
A7AB Failure of I/O configuration extension	Cause: It is mainly used for B0…B2 module. For example, if B0…B2 does not have RIIO-01 extension module inserted while the inverter adopts parameters of extended IO (DI3, DI4), the drive will give an alarm. Remedy: View whether the inverter parameter adopts signals related to DI3 – DI6, AI1, AI2, AO1, AO2, RO2, RO3. Note: These signals come from external IO boards.
A7C1 FBA A communication (Prog. warning: 50.02)	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 group 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 (Prog. warning: 58.14)	Cause: Communication break in embedded fieldbus (EFB) communication. Remedy: Check the status of the fieldbus master (online/offline/error etc.). Check the cable connections to the EIA-485/X5 terminals 29, 30 and 31 on the control unit.
A7EE Control Panel loss (Prog. warning: 49.05)	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 the control panel connector. Check the mounting platform (if being used). Disconnect and reconnect the control panel.
A8A0 AI supervision (Prog. warning: 12.03)	Cause: Analog signal exceeds the limit specified by the analog input. Remedy: Check the auxiliary code (format XYY). “X” specifies location (0: Control unit, 1: I/O expansion). “YY” specifies input/limit (01: AI1 lower min, 02: AI1 higher max, 03: AI2 lower min, 04: AI2 higher max). 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.
A880 Motor bearing	Cause: Warning generated by an ontime timer or a value counter. Remedy: Check the auxiliary code. Check warning signal source according to relevant code.
A881 Output relay	Cause: Warning generated by an edge counter. Remedy: Check the auxiliary code. Check warning signal source according to relevant code.
A882 Motor start	Cause: Warning generated by counter/timer. Remedy: Check the auxiliary code. Check warning signal source according to relevant code.
A883 Energized	Cause: Warning generated by counter/timer. Remedy: Check the auxiliary code. Check warning signal source according to relevant code.
A886 real time 1	Cause: Warnings generated by 1 realtime timer. Remedy: Check the warning signal source.
A887 real time 2	Cause: Warnings generated by 2 realtime timer. Remedy: Check the warning signal source.
A888 Edge counter 1	Cause: Warnings generated by 1 edge counter. Remedy: Check the warning signal source.
A889 Edge counter 2	Cause: Warnings generated by 2 edge counter. Remedy: Check the warning signal source.
A88A Value counter 1	Cause: Warnings generated by 1 value counter. Remedy: Check the warning signal source.
A88B Value counter 2	Cause: Warnings generated by 2 value counter. Remedy: Check the warning signal source.
A88C Device clear	Cause: Warnings generated by realtime timer. Remedy: Warnings generated by realtime timer.
A8B0 Signal supervision (Prog. warning: 32.06/16/26)	Cause: Warning generated by a signal supervision function. Remedy: Check the warning signal source (parameter 32.07, 32.17 or 32.27).
A8BE ULC overload warning (Prog. fault: 37.03)	Cause: Selected signal has exceeded the user overload curve. Remedy: Check for any operating conditions increasing the monitored signal (e.g., motor loading, torque, current). Check the definition of the load curve (parameter group 37 User load curve).
A8BF ULC underload warning (Prog. fault: 37.03)	Cause: Selected signal has fallen below the user underload curve. Remedy: Check for any operating conditions decreasing the monitored signal (e.g., loss of load). Check the definition of the load curve (parameter group 37 User load curve).
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. 0001: Relay output 1 – Change control board or stop using output 1. 0002: Relay output 2 – Change control board or stop using output 2. 0003: Relay output 3 – Change control board or stop using output 3.
A8A2 RO toggle warning	Cause: The relay output is changing states faster than recommended (e.g. fast changing frequency signal). 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 – Select a different signal with parameter 10.24 RO1 source. 0002: Relay output 2 – Select a different signal with parameter 10.27 RO2 source. 0003: Relay output 3 – Select a different signal with parameter 10.30 RO3 source.
A981 External warning 1 (Prog. warning: 31.01)	Cause: Fault in external device 1. Remedy: Check the external device. Check setting of the parameter 31.01 External event 1 source.
A982 External warning 2 (Prog. warning: 31.03)	Cause: Fault in external device 2. Remedy: Check the external device. Check setting of the parameter 31.03 External event 2 source.
A983 External warning 3 (Prog. warning: 31.05)	Cause: Fault in external device 3. Remedy: Check the external device. Check setting of the parameter 31.05 External event 3 source.
A984 External warning 4 (Prog. warning: 31.07)	Cause: Fault in external device 4. Remedy: Check the external device. Check setting of the parameter 31.07 External event 4 source.
A985 External warning 5 (Prog. warning: 31.09)	Cause: Fault in external device 5. Remedy: Check the external device. Check setting of the 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.
AF8C Process PID sleep mode	Cause: The drive is entering sleep mode. Remedy: Informative warning. See section of Sleep and boost functions for process PID control. See parameters 40.43…40.48.
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 whether it can continue to operate safely. 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.
AFF5 Override new start required	Cause: The Safe torque off function was active and has been reset while in Override. Remedy: A new start signal is required to start the drive again.
AFF7 Autophasing	Cause: Autophasing routine will be performed at next start to determine the angular position of the magnetic flux (with a permanent magnet synchronous motor) or the magnetic axis (with a synchronous reluctance motor). Remedy: Informative warning.
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 the parameter 20.12 Run enable 1 source. Switch signal on (e.g., in the fieldbus Control Word) or check wiring of selected source.
AFEC External power signal missing	Cause: 95.04 Control board supply is set to External 24V but no voltage is connected to the control unit. Remedy: Check the external 24 V DC power supply to the control unit, or change the setting of parameter 95.04.
AFED Enable to rotate	Cause: Signal enable to rotate has not been received within a fixed time delay. 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.
B5A0 STO event (Programmable event: 31.22 STO indication run/stop)	Cause: Delete safe torque function is active, i.e. safety circuit signal(s) connected to connector STO is lost. Remedy: Check safety circuit connections. For more information, see description in chapter Delete safe torque function as well as parameter 31.22 STO indication run/stop (page 207) of drive hardware manual.
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.
2310 Over current	Cause: Output current has exceeded internal fault limit. In addition to an actual overcurrent situation, this fault may also be caused by a ground fault or supply phase loss. Remedy: Check motor load. 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 corresponds to the motor rating plate. Check there are no power factor correction capacitors or surge absorbers in motor cable. Check for a ground fault in motor or motor cables by measuring the insulation resistances.
2330 Earth leakage (Programmable fault: 31.20 Ground fault)	Cause: Drive has detected load unbalance typically due to ground fault in motor or motor cable. Remedy: Check there are no power factor correction capacitors or surge absorbers in motor cable. Check for a ground fault in motor or motor cables by measuring the insulation resistances of motor and motor cable. If no ground fault can be detected, contact your local ABB representative.
2340 Short circuit	Cause: Short-circuit in motor cable(s) or motor. Remedy: Check motor and motor cable for cabling errors. Check there are no power factor correction capacitors or surge absorbers in motor cable. Cycle the power to the drive.
2381 IGBT overload	Cause: Excessive IGBT junction to case temperature. This fault protects the IGBT(s) and can be activated by a short circuit in the motor cable. Remedy: Check motor cable. Check ambient conditions. Check air flow and fan operation. Check heat sink fins for dust pick-up. Check motor power against drive power.
3130 Supply phase loss (Programmable fault: 31.21 Supply phase loss)	Cause: Intermediate circuit DC voltage is oscillating due to missing input power line phase or blown fuse. Remedy: Check input power line fuses. Check for loose power cable connections. Check for input power supply imbalance.
3181 Cross connection (Programmable fault: 31.23)	Cause: Incorrect input power and motor cable connection (i.e. input power cable is connected to drive motor connection). Remedy: Check input power connections.
3210 DC bus overvoltage	Cause: Excessive intermediate circuit DC voltage. Remedy: Check that overvoltage control is on (parameter 30.30). Check that the supply voltage matches the nominal input voltage of the drive. Check the supply line for static or transient overvoltage. Check brake chopper and resistor (if present). Check deceleration time. Use coast-to-stop function (if applicable). Retrofit the drive with brake chopper and brake resistor.
3220 DC bus 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.
3280 Standby time-out	Cause: Automatic restart failed. Remedy: Check power condition (voltage, cable, fuse, switch).
3381 Output phase loss (Programmable fault: 31.19)	Cause: Motor circuit fault due to missing motor connection (None of the three phases is connected). Remedy: Connect motor cable.
4000 Motor cable overload	Cause: Calculated motor cable temperature has exceeded warning limit. Remedy: Check the settings of 35.61 and 35.62. Check the motor cable size against necessary load.
4110 Control board temperature	Cause: Control board temperature is excessive. 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 heat sink fins for dust pick-up. Check motor power against drive power.
4290 Cooling	Cause: Drive module temperature is excessive. Remedy: Check ambient temperature. If it exceeds 40°C/104°F (frames R5…R9) or 50°C/122°F (frames B0…R9), ensure that load current does not exceed derated load capacity. Check drive module cooling air flow and fan operation. Check inside of cabinet and heatsink of drive module for dust pick-up. Clean whenever necessary.
42F1 IGBT temperature	Cause: Drive IGBT temperature is excessive. Remedy: Check ambient conditions. Check air flow and fan operation. Check heat sink 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 heat sink fins for dust pick-up. Check motor power against drive power.
4380 Excess temperature difference	Cause: High temperature difference between the IGBTs of different phases. Remedy: Check motor cabling. Check cooling of the drive module(s).
4381 PCB plate cooling	Cause: Temperature difference between ambient and drive module PCB space is excessive. Remedy: See A4B2 PCB plate cooling (page 355).
4981 Ext Tmp 1 (Editable message text)	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 Ext Tmp 2 (Editable message text)	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 is stuck or disconnected. Remedy: See A581 Fan (page 356).
5081 Auxiliary fan broken	Cause: An auxiliary cooling fan (connected to the fan connectors on the control unit) is stuck or disconnected. Remedy: Check auxiliary fan(s) and connection(s). Replace faulty fan. Make sure the front cover of the drive module is in place and tightened. Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power.
5090 STO hardware failure	Cause: STO hardware diagnostics has detected hardware failure. Remedy: Contact your local ABB representative for hardware replacement.
5091 Delete safe torque (Programmable fault: 31.22)	Cause: Delete safe torque function is active, i.e. safety circuit signal(s) connected to connector XSTO is missing during start or run. Remedy: Check safety circuit connections. See description in chapter Delete safe torque function as well as parameter 31.22 STO indication run/stop (page 207) of drive hardware manual. Check the value of parameter 95.04 Control board supply.
5092 PU logic error	Cause: Power unit memory has cleared. Remedy: Contact your local ABB representative.
5093 Rating ID mismatch	Cause: The hardware of the drive does not match the information stored in the memory. This may occur 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.
5095 Redundant measurement	Cause: Redundant measurement supervision has indicated a difference in the duplicated measurements that is outside the limits. Remedy: Contact your local ABB representative.
50A0 Fan	Cause: Cooling fan is stuck or disconnected. Remedy: Check fan operation and connection. Replace faulty fan.
5681 PU communication	Cause: Communication errors detected between the drive control unit and the power unit. Remedy: Check the connection between the drive control unit and the power unit. Check the value of parameter 95.04 Control board supply.
5682 Power unit lost	Cause: Connection between the drive control unit and the power unit is lost. Remedy: Check the connection between the control unit and the power unit.
5690 PU internal communication	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.
5698 Unknown power fault	Cause: Unidentified power unit logic fault. Remedy: Check power unit logic and firmware compatibility. Contact local ABB representative.
6000 Internal software error	Cause: Internal error. Remedy: Contact local ABB representative. Quote the auxiliary code (check the event details in the event log).
6181 FPGA version incompatible	Cause: Firmware and FPGA versions are incompatible. Remedy: Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power. If the problem persists, contact your local ABB representative.
6306 FBA A mapping file	Cause: Fieldbus adapter A mapping file read error. Remedy: Contact your local ABB representative.
6481 Task overload	Cause: Internal fault. Remedy: Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power. If the problem persists, contact your local ABB representative.
6487 Stack overflow	Cause: Internal fault. Remedy: Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power. If the problem persists, contact your local ABB representative.
64A1 Internal file load	Cause: File read error. Remedy: Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power. If the problem persists, contact your local ABB representative.
64B2 User group fault	Cause: Loading of user parameter group failed because: Requested group does not exist Set is not compatible with control program Drive switches off during the load process Remedy: Ensure that a valid user parameter group exists. Reload if uncertain.
64E1 Kernel overload	Cause: Operating system error. Remedy: Reboot the control unit (using parameter 96.08 Control board boot). If the problem persists, contact your local ABB representative.
AFF7 Fault reset	Cause: A fault has been reset from the control panel, Drive composer PC tool, fieldbus or I/O. Remedy: Event. Informative only.
6581 Parameter system	Cause: Unable to load or save parameter. Remedy: Try forcing a save using parameter 96.07 Parameter save manually. Retry.
65A1 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) and 51 FBA A settings.
64B3 Macro parameterization error	Cause: Macro parameterization failed, because parameter default value that cannot be changed has been attempted to write. Remedy: Check macro settings and parameters.
6681 EFB Communication loss	Cause: Communication break in embedded fieldbus (EFB) communication. (Programmable fault: 58.14 Communication loss action) Remedy: Check the status of the fieldbus master (online/offline/error etc.). Check the cable connections to the EIA-485/X5 terminals 29, 30 and 31 on the control unit.
6682 EFB profile	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. If the fault persists contact your local ABB representative.
6885 Text file overflow	Cause: Internal fault. Remedy: Reset the fault. If the fault persists contact your local ABB representative.
7081 Control panel loss	Cause: Control panel or PC tool selected as active control location for drive has ceased communicating. (Programmable fault: 49.05 Communication loss action) Remedy: Check PC tool or control panel connection. Check the control panel connector. Disconnect and reconnect the control panel.
7082 Expansion I/O communication lost	Cause: The I/O extension module types specified by parameters do not match the detected configuration. Remedy: Check auxiliary code (format XXYY YYYY). “XX” specifies I/O number of the I/O extension module. “YY YYYY” indicates problem: 00 0001: Communication between modules failed. Check installation and connectors. 00 0002: Module is not found. Check module type and position settings (15.01/14.02 etc). Check installation. 00 0003 / 00 0004: Configuration of module failed. Check if correctly installed. Try another slot.
7121 Motor stall	Cause: Motor is operating in stall region because of, e.g., excessive load or insufficient motor power. (Programmable fault: 31.24 Stall function) Remedy: Check the motor load and drive ratings. Check fault function parameters.
7181 Brake resistors	Cause: Brake resistor broken or not connected. Remedy: Check that a brake resistor has been connected. Check the condition of the brake resistor. Check the size of the brake resistor.
7183 Brake resistor temperature is excessive	Cause: Brake resistor temperature has exceeded fault limit defined by parameter 43.11 Brake resistor fault limit. Remedy: Stop the drive. Let resistor cool down. Check resistor overload protection function settings (parameter group 43 Brake chopper). Check fault limit setting, parameter 43.11 Brake resistor fault limit. Check that braking cycle meets allowed limits.
7184 Brake resistor wiring	Cause: Brake resistor short circuit or brake chopper control fault. Brake resistor temperature is excessive. Remedy: Check brake chopper and brake resistor connection. Ensure brake resistor is not damaged.
7086 AI Overvoltage	Cause: An overvoltage has been detected on an analog input. The analog input has temporarily been changed to voltage mode and will be changed back to current mode when the AI signal level is back within acceptable limits. Remedy: Check AI signal levels.
7191 Short circuit in brake chopper	Cause: Short circuit in brake chopper IGBT. Remedy: Ensure the brake resistor is connected and not damaged. Check the electrical specifications of the brake resistor against chapter Resistor brake of drive hardware manual. Replace brake chopper (if replaceable).
7192 Brake chopper IGBT temperature is excessive	Cause: Brake chopper IGBT temperature has exceeded internal fault limit. Remedy: Let chopper cool down. Check for excessive ambient temperature. Check for cooling fan failure. Check for obstructions in the air flow. Check resistor overload protection function settings (parameter group 43 Brake chopper). Check that braking cycle meets allowed limits. Check that drive supply AC voltage is not excessive.
71B1 Motor fan	Cause: No feedback signals of external fan have been received. Remedy: Check external fan one by one (or other controllable equipment).
73B0 Emergency ramp failed	Cause: Emergency stop did not finish within expected time. Remedy: Check the predefined ramp times 23.11…23.15, for (mode Off1, 23.23 for mode Off3).
7510 FBA A communication	Cause: Cyclical communication between drive and fieldbus adapter module A or between PLC and fieldbus adapter module A is lost. (Programmable fault: 50.02 FBA A communication loss function) Remedy: Check status of fieldbus communication. See user documentation of fieldbus interface. Check settings of parameter group 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 overload actions.
8002 ULC overload fault	Cause: User load curve: Signal has been too long over the overload curve. Remedy: See parameter 37.04 ULC overload actions.
80A0 AI supervision	Cause: An analog signal is outside the limits specified for the analog input. (Programmable fault: 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.
80B0 Signal supervision	Cause: Fault generated by a signal supervision function. (Programmable fault: 32.06, 32.16, 32.26 Supervision action) Remedy: Check the source of the fault (parameter 32.07, 32.17 or 32.27).
9081 External fault 1	Cause: Fault in external device 1. (Programmable fault: 31.01 External event 1 source) Remedy: Check the external device. Check setting of the parameter 31.01 External event 1 source.
9082 External fault 2	Cause: Fault in external device 2. (Programmable fault: 31.03 External event 2 source) Remedy: Check the external device. Check setting of the parameter 31.03 External event 2 source.
9083 External fault 3	Cause: Fault in external device 3. (Programmable fault: 31.05 External event 3 source) Remedy: Check the external device. Check setting of the parameter 31.05 External event 3 source.
9084 External fault 4	Cause: Fault in external device 4. (Programmable fault: 31.07 External event 4 source) Remedy: Check the external device. Check setting of the parameter 31.07 External event 4 source.
9085 External fault 5	Cause: Fault in external device 5. (Programmable fault: 31.09 External event 5 source) Remedy: Check the external device. Check setting of the parameter 31.09 External event 5 source.
FA81 Delete safe torque 1	Cause: Safe torque off function is active, ie, STO circuit 1 is broken. Remedy: Check safety circuit connections. For detailed information, see the description of parameter 31.22 STO indication run/stop. Check the value of parameter 95.04 Control board supply.
FA82 Delete safe torque 2	Cause: Safe torque off function is active, ie, STO circuit 2 is broken. Remedy: Check the value of parameter 95.04 Control board supply. (Implied: Check safety circuit connections similar to FA81).
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.