ABB ACQ810 Drive

ABB ACQ810 Drive Fault Codes:

Fault Code and MeaningCause and Remedy

2003

SAFE TORQUE OFF

(0xFF7A)

Cause: Safe torque off function is active, i.e. safety circuit signal(s) connected to connector XSTO is lost.


Remedy:

  • Check safety circuit connections.

  • See appropriate drive hardware manual.

  • See description of parameter 30.07.

  • Refer to Application guide – Safe torque off function.

2004

STO MODE CHANGE

(0xFF7A)

Cause: Error in changing Safe torque off supervision, i.e. parameter 30.07 Sto diagnostic setting could not be changed to value Alarm.


Remedy:

  • Contact your local ABB representative.

2005

MOTOR TEMPERATURE

(0x4310)

Cause: Estimated motor temperature (based on thermal model) OR Measured motor temperature has exceeded alarm limit.


Remedy:

  • Check motor ratings and load.

  • Let motor cool down.

  • Ensure proper motor cooling: Check cooling fan, clean cooling surfaces, etc.

  • Check value of alarm limit (parameter 31.03).

  • Check motor thermal model settings (parameters 31.09…31.14).

  • Check that actual number of sensors corresponds to value set by parameter 31.02.

2006

EMERGENCY OFF

(0xF083)

Cause: Drive has received emergency OFF2 command.


Remedy:

  • To restart drive, activate Run enable signal (source selected by parameter 10.11).

  • Start drive.

2007

RUN ENABLE

(0xFF54)

Cause: No Run enable signal is received.


Remedy:

  • Check setting of parameter 10.11 Run enable.

  • Switch signal on (e.g. in the fieldbus Control Word).

  • Check wiring of selected source.

2008

MOTOR ID-RUN

(0xFF84)

Cause: Motor identification run is on OR Motor identification is required.


Remedy:

  • Wait until drive indicates that motor identification is completed.

  • Select how motor identification should be performed (parameter 99.13).

  • Start identification routines by pressing Start key.

2009

EMERGENCY STOP

(0xF081)

Cause: Drive has received emergency stop command (OFF3).


Remedy:

  • Check that it is safe to continue operation.

  • Return emergency stop push button to normal position.

  • Adjust the fieldbus Control Word accordingly.

  • Restart drive.

2013

DEVICE OVERTEMP

(0x4210)

Cause: Measured drive temperature has exceeded internal alarm limit.


Remedy:

  • Check ambient conditions.

  • Check air flow and fan operation.

  • Check heatsink fins for dust pick-up.

  • Check motor power against unit power.

2014

INTBOARD OVERTEMP

(0x7182)

Cause: Interface board (between power unit and control unit) temperature has exceeded internal alarm limit.


Remedy:

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

2017

FIELDBUS COMM

(0x7510)

Cause: Cyclical communication between drive and fieldbus adapter module or between PLC and fieldbus adapter module is lost.


Remedy:

  • Check status of fieldbus communication.

  • See appropriate User’s Manual of fieldbus adapter module.

  • Check settings of parameter group 50 Fieldbus.

  • Check cable connections.

  • Check if communication master is able to communicate.

2018

PANEL CTRL LOSS

(0x5300)

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.

  • Replace control panel in mounting platform.

2019

AI SUPERVISION

(0x8110)

Cause: An analog input has reached limit defined by parameter 13.33.


Remedy:

  • Check analog input source and connections.

  • Check analog input minimum and maximum limit settings.

2020

FB PAR CONF

(0x6320)

Cause: The drive does not have a functionality requested by PLC, or requested functionality has not been activated.


Remedy:

  • Check PLC programming.

  • Check settings of parameter group 50 Fieldbus.

2021

NO MOTOR DATA

(0x6381)

Cause: Parameters in group 99 have not been set.


Remedy:

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

2035

PS COMM

(0x5480)

Cause: Communication errors detected between the JCU Control Unit and the power unit of the drive.


Remedy:

  • Check the connections between the JCU Control Unit and the power unit.

2036

RESTORE

(0x6300)

Cause: Restoration of backed-up parameters failed.


Remedy:

  • Repeat the restore procedure.

  • Use another back-up file, if possible.

  • If the problem persists, contact your local ABB representative.

2037

CUR MEAS CALIBRATION

(0x2280)

Cause: Current measurement calibration will occur at next start.


Remedy:

  • Informative alarm (no action required).

2039

EARTH FAULT

(0x2330)

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.

  • If no earth fault can be detected, contact your local ABB representative.

2040

AUTORESET

(0x6080)

Cause: A fault is to be autoreset.


Remedy:

  • Informative alarm. See parameter group 32 Automatic reset.

2041

MOTOR NOM VALUE

(0x6383)

Cause: The motor configuration parameters are set incorrectly OR 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.

2043

STALL

(0x7121)

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.

2044

LOAD CURVE

(0x2312)

Cause: Overload or underload limit has been exceeded.


Remedy:

  • Check the settings of the parameters in group 34 User load curve.

2045

LOAD CURVE PAR

(0x6320)

Cause: The load curve has been incorrectly or inconsistently defined.


Remedy:

  • Check the settings of the parameters in group 34 User load curve.

2046

U/f-curve par

(0x6320)

Cause: The U/f (voltage/frequency) curve has been incorrectly or inconsistently defined.


Remedy:

  • Check the settings of the parameters in group 38 Flux ref.

2048

OPTION COMM LOSS

(0x7000)

Cause: Communication between drive and option module (FEN-xx and/or FIO-xx) is lost.


Remedy:

  • Check that option modules are properly connected to Slot 1 or Slot 2.

  • Check that option modules or Slot 1/2 connectors are not damaged.

  • Test each module individually in Slot 1 and Slot 2.

2049

MOTOR TEMP2

(0x4313)

Cause: Estimated motor temperature (based on thermal model) OR Measured motor temperature has exceeded alarm limit.


Remedy:

  • Check motor ratings and load.

  • Let motor cool down. Ensure proper motor cooling.

  • Check cooling fan, clean cooling surfaces, etc.

  • Check value of alarm limit.

  • Check motor thermal model settings.

  • Check that actual number of sensors corresponds to value set.

2050

IGBT OVERLOAD

(0x5482)

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.

2051

IGBT TEMP

(0x4210)

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.

2052

COOLING

(0x4290)

Cause: Drive module temperature is excessive.


Remedy:

  • Check ambient temperature. If it exceeds 40 °C, ensure load current does not exceed derated capacity.

  • Check drive module cooling air flow and fan operation.

  • Check inside of cabinet and heatsink for dust pick-up.

  • Clean whenever necessary.

2053

MENU CHG PASSWORD REQ

(0x6F81)

Cause: Loading a parameter listing requires a password.


Remedy:

  • Enter password at parameter 16.03 Pass code.

2054

MENU CHANGED

(0x6F82)

Cause: A different parameter listing is being loaded.


Remedy:

  • Informative alarm.
2055
DEVICE CLEAN
(0x5080)
Cause: Maintenance counter alarm.



Remedy:
See parameter group 44 Maintenance.

Note: Any maintenance counter alarm sets bit 8 of 08.08 Alarm logger4.
2056
COOLING FAN
(0x5081)
Cause: Maintenance counter alarm (Cooling Fan).



Remedy: See parameter group 44 Maintenance.
2057
ADD COOLING
(0x5082)
Cause: Maintenance counter alarm (Additional Cooling).



Remedy: See parameter group 44 Maintenance.
2058
CABINET FAN
(0x5083)
Cause: Maintenance counter alarm (Cabinet Fan).



Remedy: See parameter group 44 Maintenance.
2059
DC CAPACITOR
(0x5084)
Cause: Maintenance counter alarm (DC Capacitor).



Remedy: See parameter group 44 Maintenance.
2060
MOTOR BEARING
(0x738C)
Cause: Maintenance counter alarm (Motor Bearing).



Remedy: See parameter group 44 Maintenance.
2072
DC NOT CHARGED
(0x3250)
08.08 Alarm logger4 b9
Cause: The voltage of the intermediate DC circuit has not yet risen to operating level.



Remedy: Wait for the DC voltage to rise.
2073
AUTOTUNE FAILED
(0x8481)
08.08 Alarm logger4 b10
Cause: Speed controller autotune routine did not finish successfully.



Remedy: See parameter 23.20 PI tune mode.
2074
START INTERLOCK
(0xF082)
08.08 Alarm logger4 b11
Cause: No Start interlock signal received.



Remedy: Check circuit connected to DIIL input.
2076
TEMP MEAS FAILURE
(0x4211)
08.08 Alarm logger4 b7
Cause: Problem with internal temperature measurement of the drive.



Remedy: Contact your local ABB representative.
2077
EFB COMM LOSS
(0x7540)
08.08 Alarm logger4 b12
Cause: Embedded fieldbus interface has been taken into use, and there is a communication break between the drive and the master station.



Remedy:
Check:

  • selection of the parameter which enables/disables EFB communication (58.01 Protocol ena sel)

  • EFB connection at terminal XD2D on the JCON board

  • status of the fieldbus master (online/offline)

  • settings of the communication supervision function (parameter 58.09 Comm loss action).
2081
AO CALIBRATION
(0x7380)
Cause: Analog output calibration has failed.



Remedy:

  • Check that the analog output to be calibrated is connected to the corresponding analog input (AO1 to AI1, AO2 to AI2). See the description of parameter 15.30 AO calibration.

  • Check that the analog input has been set to current using the jumper on the control unit. Refer to the Hardware manual of the drive for the settings.

  • Check the functioning of the analog output and input.
2201
PIPEFILL TIMEOUT
(0xC000)
08.09 Alarm logger5 b0
Cause: Maximum allowed time for the Pipefill function exceeded.



Remedy:

  • Check the pump system.

  • Check parameters 81.28….81.35.
2202
MIN FLOW
(0xC001)
08.09 Alarm logger5 b1
Cause: Measured flow below minimum limit.



Remedy:

  • Check the pump system for reasons such as leaks that might cause a loss of measured flow.

  • Check parameters 81.18….81.24.
2203
MAX FLOW
(0xC002)
08.09 Alarm logger5 b2
Cause: Measured flow above maximum limit.



Remedy:

  • Check the pump system for reasons that might cause an increase in measured flow.

  • Check parameters 81.18….81.24.
2204
LOW PRESSURE
(0xC003)
08.09 Alarm logger5 b3
Cause: Pressure at pump inlet too low.



Remedy:

  • Check for a closed valve on the inlet side of the pump.

  • Check piping for leaks.
2205
HIGH PRESSURE
(0xC004)
08.09 Alarm logger5 b4
Cause: Pressure at pump outlet too high.



Remedy: Check piping for blocks.
2206
VERY LOW PRESS
(0xC005)
08.09 Alarm logger5 b5
Cause: Pressure at pump inlet too low.



Remedy:

  • Check for a closed valve on the inlet side of the pump.

  • Check piping for leaks.
2207
VERY HIGH PRESS
(0xC006)
08.09 Alarm logger5 b6
Cause: Pressure at pump outlet too high.



Remedy: Check piping for blocks.
2208
PROFILE HIGH
(0xC007)
08.09 Alarm logger5 b7
Cause: Application profile protection limit exceeded (see parameters 81.25…81.27).



Remedy:

  • Check the piping for leaks.

  • Check the general condition of the components of the pumping station.
2209
MAX CLEANINGS
(0xC008)
08.09 Alarm logger5 b8
Cause: Maximum number of cleaning sequences exceeded (see parameter group 82 Pump cleaning).



Remedy: Check for reasons that might have had an increasing effect on the monitored signal (parameter 82.09). For example, increased viscosity of the fluid, or faulty pump bearings may increase the current drawn by the motor, and trigger the cleaning sequence more frequently.
2210
ALL PUMPS INLOCKD
(0xC009)
08.09 Alarm logger5 b9
Cause: All interlock signals are off, indicating no pumps are available.



Remedy:

  • Check the interlock settings in parameter group 78 Pump autochange.

  • Check that the pumps are switched on.

  • Check the interlock wiring from the pumps.
2211
ENERGY LIMIT
(0xC00A)
08.09 Alarm logger5 b10
Cause: Energy consumption limit exceeded (see parameter group 83 Energy monitoring).



Remedy: Check for reasons for increased energy consumption.
2212
DATE WRONG
(0xC00B)
08.09 Alarm logger5 b11
Cause: Date has not been set.



Remedy: Set the date and time (page 37).
2215
BOOSTING
(0xC00E)
08.09 Alarm logger5 b14
Cause: Sleep boost is active.



Remedy: Informative alarm.
2216
PIPE FILLING
(0xC00F)
08.09 Alarm logger5 b15
Cause: The soft pipefill function is being performed.



Remedy: Informative alarm.
2217
NO MORE PUMPS
(0xC010)
08.10 Alarm logger6 b0
Cause: No further pumps are available for starting.



Remedy: Check that all appropriate pumps are switched on.
2218
CLEANING
(0xC011)
08.10 Alarm logger6 b1
Cause: A pump cleaning sequence is in progress.



Remedy: Informative alarm.
2219
AUTOCHANGE
(0xC012)
08.10 Alarm logger6 b2
Cause: The Autochange function is being performed.



Remedy: Informative alarm.
2220
SLEEPING
(0xC013)
08.10 Alarm logger6 b3
Cause: The drive has entered sleep mode.



Remedy: Informative alarm.
2221
START DELAY
(0xC014)
08.10 Alarm logger6 b4
Cause: A pump will start after the start delay has elapsed.



Remedy: Informative alarm.
2222
LC TANK FULL
(0xC016)
08.10 Alarm logger6 b5
Cause: The level of the liquid in the container is very high (the source selected by parameter 79.15 High switch is 1).



Remedy: Informative alarm.
2223
LC TANK EMPTY
(0xC017)
08.10 Alarm logger6 b6
Cause: The level of the liquid in the container is very low (the source selected by parameter 79.04 Low switch is 1).



Remedy: Informative alarm.
2224
MF MASTER LOST
(0xC018)
08.10 Alarm logger6 b7
Cause: The drive cannot detect a master on the drive-to-drive link, and is not itself allowed to become master.



Remedy:

  • Check that there are drives on the drive-to-drive link that are allowed to become master.

  • Check the wiring of the drive-to-drive link.
2225
MF NO SHARED DATA
(0xC019)
08.10 Alarm logger6 b8
Cause: Shared signals not received.



Remedy:

  • Check that at least one drive has signal sharing enabled (parameter 76.12 Set as source).

  • Check the status, communication settings and wiring of the drive that is sharing its signals.
2400
SOLUTION ALARM
(0x6F80)
08.08 Alarm logger4 b1
Cause: Alarm generated by custom application program.



Remedy: Check custom application program.
0001
OVERCURRENT
(0x2310)
Cause: Output current has exceeded internal fault limit.



Remedy:

  • Check motor load.

  • Check acceleration times in parameter group 22 Speed ref ramp.

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

  • Check that the start-up data in parameter group 99 corresponds to the motor rating plate.

  • Check that there are no power factor correction capacitors or surge absorbers in motor cable.
0002
DC OVERVOLTAGE
(0x3210)
Cause: Excessive intermediate circuit DC voltage.



Remedy:

  • Check that overvoltage controller is on, parameter 47.01 Overvolt ctrl.

  • Check mains for static or transient overvoltage.

  • Check deceleration time.

  • Use coast-to-stop function (if applicable).
0003
DEVICE OVERTEMP
(0x4210)
Cause: Measured drive temperature has exceeded internal fault limit.



Remedy:

  • Check ambient conditions.

  • Check air flow and fan operation.

  • Check heatsink fins for dust pick-up.

  • Check motor power against unit power.
0004
SHORT CIRCUIT
(0x2340)
Cause: Short-circuit in motor cable(s) or motor.



Remedy:

  • Check motor and motor cable.

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

  • Check the fault logger for a fault code extension (1-32 indicates specific transistor phase U/V/W).

  • If extension exists: Contact your local ABB representative.
0005
DC UNDERVOLTAGE
(0x3220)
Cause: Intermediate circuit DC voltage is not sufficient due to missing mains phase, blown fuse or rectifier bridge internal fault.



Remedy:

  • Check mains supply and fuses.
0006
EARTH FAULT
(0x2330)
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 that there is no earth fault in motor or motor cables by measuring insulation resistances.

  • If no earth fault can be detected, contact your local ABB representative.
0007
FAN FAULT
(0xFF83)
Cause: Fan is not able to rotate freely or fan is disconnected. Fan operation is monitored by measuring fan current.



Remedy:

  • Check fan operation and connection.
0013
CURR MEAS GAIN
(0x3183)
Cause: Difference between output phase U2 and W2 current measurement gain is too great.



Remedy:

  • Contact your local ABB representative.
0014
WIRING OR EARTH FAULT
(0x3181)
Cause: Incorrect input power and motor cable connection, or ground (earth) fault in the motor cable or motor.



Remedy:

  • Check input power and motor cable connections.

  • Check the insulation resistance of the motor cable and motor.
0015
SUPPLY PHASE
(0x3130)
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 input power supply imbalance.
0016
MOTOR PHASE
(0x3182)
Cause: Motor circuit fault due to missing motor connection (all three phases are not connected).



Remedy:

  • Connect motor cable.
0017
ID-RUN FAULT
(0xFF84)
Cause: Motor ID run is not completed successfully.



Remedy:

  • Check the fault logger for a fault code extension.

  • Ext 1: Check setting of parameters 99.06 Mot nom current and 20.05 Maximum current. Check drive dimensioning.

  • Ext 2: Check parameters 99.07, 99.08, 99.09, 20.01, 20.02. Check supply voltage.

  • Ext 3: Check parameter 99.12 and group 20 Limits.

  • Ext 4-16: Contact your local ABB representative.
0018
CURR U2 MEAS
(0x3184)
Cause: Measured offset error of U2 output phase current measurement is too great.



Remedy:

  • Contact your local ABB representative.
0019
CURR V2 MEAS
(0x3185)
Cause: Measured offset error of V2 output phase current measurement is too great.



Remedy:

  • Contact your local ABB representative.
0020
CURR W2 MEAS
(0x3186)
Cause: Measured offset error of W2 output phase current measurement is too great.



Remedy:

  • Contact your local ABB representative.
0021
STO1 LOST
(0x8182)
Cause: Safe torque off function is active, i.e. safety circuit signal 1 connected between XSTO:1 and XSTO:3 is lost.



Remedy:

  • Check safety circuit connections.

  • See appropriate drive hardware manual and description of parameter 30.07.
0022
STO2 LOST
(0x8183)
Cause: Safe torque off function is active, i.e. safety circuit signal 2 connected between XSTO:2 and XSTO:4 is lost.



Remedy:

  • Check safety circuit connections.

  • See appropriate drive hardware manual and description of parameter 30.07.
0023
STO MODE CHANGE
(0xFF7A)
Cause: Error in changing Safe torque off supervision.



Remedy:

  • Contact your local ABB representative.
0024
INTBOARD OVERTEMP
(0x7182)
Cause: Interface board (between power unit and control unit) temperature has exceeded internal fault limit.



Remedy:

  • Let drive 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.
0027
PU LOST
(0x5400)
Cause: Connection between the JCU Control Unit and the power unit of the drive is lost.



Remedy:

  • Check the connections between the JCU Control Unit and the power unit.

  • Check setting of parameter 95.01 Ctrl boardSupply.
0028
PS COMM
(0x5480)
Cause: Communication errors detected between the JCU Control Unit and the power unit of the drive.



Remedy:

  • Check the connections between the JCU Control Unit and the power unit.
0030
EXTERNAL
(0x9000)
Cause: Fault in external device. (Configured through programmable digital inputs).



Remedy:

  • Check external devices for faults.

  • Check parameter 30.01 External fault setting.
0031
SAFE TORQUE OFF
(0xFF7A)
Cause: Safe torque off function is active; safety circuit signal lost during start/run or while stopped (and param 30.07 is set to Fault).



Remedy:

  • Check safety circuit connections.

  • Refer to appropriate drive hardware manual and Application guide.
0032
OVERSPEED
(0x7310)
Cause: Motor is turning faster than highest allowed speed.



Remedy:

  • Check minimum/maximum speed settings, parameters 20.01 Maximum speed and 20.02 Minimum speed.
0036
PANEL CTRL LOSS
(0x5300)
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.

  • Replace control panel in mounting platform.
0037
NVMEM CORRUPTED
(0x6320)
Cause: Drive internal fault. Note: This fault cannot be reset.



Remedy:

  • Contact your local ABB representative.
0038
OPTION COMM LOSS
(0x7000)
Cause: Communication between drive and option module (FIO-xx) is lost.



Remedy:

  • Check that option modules are properly connected to Slot 1 and (or) Slot 2.

  • Check that option modules or Slot 1/2 connectors are not damaged.

  • Test each module individually in Slot 1 and Slot 2.
0045
FIELDBUS COMM
(0x7510)
Cause: Cyclical communication between drive and fieldbus adapter module or between PLC and fieldbus adapter module is lost.



Remedy:

  • Check status of fieldbus communication.

  • See appropriate User’s Manual of fieldbus adapter module.

  • Check settings of parameter group 50 Fieldbus.

  • Check cable connections.

  • Check if communication master is able to communicate.
0046
FB MAPPING FILE
(0x6306)
Cause: Drive internal fault.



Remedy:

  • Contact your local ABB representative.
0047
MOTOR OVERTEMP
(0x4310)
Cause: Estimated motor temperature (thermal model) OR Measured motor temperature has exceeded fault limit, OR Faulty temperature sensor.



Remedy:

  • Check motor ratings and load.

  • Let motor cool down. Ensure proper motor cooling (fan, surfaces).

  • Check value of alarm limit.

  • Check motor thermal model settings (parameters 31.09…31.14).

  • Check that actual number of sensors corresponds to value set by parameter 31.02.

  • Check the sensor and its wiring.
0049
AI SUPERVISION
(0x8110)
Cause: An analog input has reached limit defined by parameter 13.33 AI superv cw.



Remedy:

  • Check analog input source and connections.

  • Check analog input minimum and maximum limit settings.
0055
TECH LIB
(0x6382)
Cause: Resettable fault generated by a technology library.



Remedy:

  • Refer to the documentation of the technology library.
0056
TECH LIB CRITICAL
(0x6382)
Cause: Permanent fault generated by a technology library.



Remedy:

  • Refer to the documentation of the technology library.
0057
FORCED TRIP
(0xFF90)
Cause: Generic Drive Communication Profile trip command.



Remedy:

  • Check PLC status.
0058
FIELDBUS PAR ERROR
(0x6320)
Cause: The drive does not have a functionality requested by PLC, or requested functionality has not been activated.



Remedy:

  • Check PLC programming.

  • Check settings of parameter group 50 Fieldbus.
0059
STALL
(0x7121)
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.
0060
LOAD CURVE
(0x2312)
Cause: Overload or underload limit has been exceeded.



Remedy:

  • Check the settings of the parameters in group 34 User load curve.
0063
MOTOR TEMP2
Cause: Estimated motor temperature (based on thermal model) or Measured motor temperature has exceeded fault limit (31.08). Potential faulty sensor or wiring.



Remedy:

  • Check motor ratings and load.

  • Let motor cool down. Ensure proper motor cooling (fan, surfaces).

  • Check value of alarm limit.

  • Check motor thermal model settings (parameters 31.09…31.14).

  • Check that actual number of sensors corresponds to parameter 31.06.

  • Check the sensor and its wiring.
0064
IGBT OVERLOAD
Cause: Excessive IGBT junction to case temperature. Can be activated by a short circuit in the motor cable.



Remedy:

  • Check motor cable.
0065
IGBT TEMP
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.
0066
COOLING
Cause: Drive module temperature is excessive.



Remedy:

  • Check setting of parameter 95.03 Temp inu ambient.

  • Check ambient temperature. If > 40 °C, ensure load does not exceed derated capacity.

  • Check drive module cooling air flow and fan operation.

  • Check inside of cabinet and heatsink for dust. Clean if necessary.
0067
FPGA ERROR1
Cause: Drive internal fault.



Remedy:

  • Contact your local ABB representative.
0068
FPGA ERROR2
Cause: Drive internal fault.



Remedy:

  • Contact your local ABB representative.
0069
ADC ERROR
Cause: Drive internal fault.



Remedy:

  • Contact your local ABB representative.
0070
TEMP MEAS FAILURE
Cause: Problem with internal temperature measurement of the drive.



Remedy:

  • Contact your local ABB representative.
0071
EFB COMM
Cause: Embedded fieldbus interface communication break between drive and master.



Remedy:

  • Check selection of parameter 58.01 Protocol ena sel.

  • Check EFB connection at terminal XD2D on JCON board.

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

  • Check settings of communication supervision (parameter 58.09).
0201
T2 OVERLOAD
Cause: The drive CPU is overloaded. Firmware time level 2 overload. (Cannot be reset).



Remedy:

  • Try to reduce the load (lower fieldbus speed, optimize application program).

  • If problem persists, contact your local ABB representative.
0202
T3 OVERLOAD
Cause: The drive CPU is overloaded. Firmware time level 3 overload. (Cannot be reset).



Remedy:

  • Try to reduce the load (lower fieldbus speed, optimize application program).

  • If problem persists, contact your local ABB representative.
0203
T4 OVERLOAD
Cause: The drive CPU is overloaded. Firmware time level 4 overload. (Cannot be reset).



Remedy:

  • Try to reduce the load (lower fieldbus speed, optimize application program).

  • If problem persists, contact your local ABB representative.
0204
T5 OVERLOAD
Cause: The drive CPU is overloaded. Firmware time level 5 overload. (Cannot be reset).



Remedy:

  • Try to reduce the load (lower fieldbus speed, optimize application program).

  • If problem persists, contact your local ABB representative.
0205
A1 OVERLOAD
Cause: Application time level 1 fault. (Cannot be reset).



Remedy:

  • Contact your local ABB representative.
0206
A2 OVERLOAD
Cause: Application time level 2 fault. (Cannot be reset).



Remedy:

  • Contact your local ABB representative.
0207
A1 INIT FAULT
Cause: Application task creation fault. (Cannot be reset).



Remedy:

  • Reload the application program into the drive.

  • If problem persists, contact your local ABB representative.
0208
A2 INIT FAULT
Cause: Application task creation fault. (Cannot be reset).



Remedy:

  • Reload the application program into the drive.

  • If problem persists, contact your local ABB representative.
0209
STACK ERROR
Cause: Drive internal fault. (Cannot be reset).



Remedy:

  • Contact your local ABB representative.
0210
JMU MISSING
Cause: JMU Memory Unit is missing or broken.



Remedy:

  • Check that the JMU is properly installed.

  • If problem persists, replace the JMU.
0301
UFF FILE READ
Cause: File read error. (Cannot be reset).



Remedy:

  • Update the drive firmware.

  • If problem persists, contact your local ABB representative.
0302
APPL DIR CREATION
Cause: Drive internal fault. (Cannot be reset).



Remedy:

  • Contact your local ABB representative.
0303
FPGA CONFIG DIR
Cause: Drive internal fault. (Cannot be reset).



Remedy:

  • Contact your local ABB representative.
0304
PU RATING ID
Cause: Drive internal fault. (Cannot be reset).



Remedy:

  • Contact your local ABB representative.
0305
RATING DATABASE
Cause: Drive internal fault. (Cannot be reset).



Remedy:

  • Contact your local ABB representative.
0306
LICENSING
Cause: Drive internal fault. (Cannot be reset).



Remedy:

  • Check that the memory unit contains the correct firmware.

  • If problem persists, contact your local ABB representative.
0307
DEFAULT FILE
Cause: Drive internal fault. (Cannot be reset).



Remedy:

  • Contact your local ABB representative.
0308
APPL FILE PAR CONF
Cause: Corrupted application file. (Cannot be reset).



Remedy:

  • Reload application.

  • If fault is still active, contact your local ABB representative.
0309
APPL LOADING
Cause: Application file incompatible or corrupted. (Cannot be reset).

Ext 8: Template incompatible with FW.

Ext 10: Parameter conflict.

Ext 35: Memory full.

Ext Other: Corrupt file.



Remedy:

  • Reload application.

  • If Extension 8: Change template of application in DriveSPC.

  • If Extension 10: Check application for conflicting parameters.

  • If Extension 35: Reduce application size.

  • If fault is still active, contact your local ABB representative.
0310
USERSET LOAD
Cause: Loading of user set not successful (set does not exist, incompatible, or drive switched off during load).



Remedy:

  • Reload.
0311
USERSET SAVE
Cause: User set is not saved because of memory corruption.



Remedy:

  • Check the setting of parameter 95.01 Ctrl boardSupply.

  • If fault still occurs, contact your local ABB representative.
0312
UFF OVERSIZE
Cause: UFF file is too big.



Remedy:

  • Contact your local ABB representative.
0313
UFF EOF
Cause: UFF file structure failure.



Remedy:

  • Update the drive firmware.

  • If problem persists, contact your local ABB representative.
0314
TECH LIB INTERFACE
Cause: Incompatible firmware interface. (Cannot be reset).



Remedy:

  • Check the compatibility of the firmware version.

  • If problem persists, contact your local ABB representative.
0315
RESTORE FILE
Cause: Restoration of backed-up parameters failed.



Remedy:

  • Contact your local ABB representative.
0316
DAPS MISMATCH
Cause: Mismatch between JCU Control Unit firmware and power unit logic versions.



Remedy:

  • Contact your local ABB representative.
0317
SOLUTION FAULT
Cause: Fault generated by function block SOLUTION_FAULT in the solution program.



Remedy:

  • Check the usage of the SOLUTION_FAULT block in the application program.
0318
MENU HIDING
Cause: Menu hiding file missing or corrupted.



Remedy:

  • Reload application.

  • Contact your local ABB representative.
0401
PIPEFILL TOUT
Cause: Maximum allowed time for the Pipefill function exceeded.



Remedy:

  • Check the pump system.

  • Check parameters 81.28…81.35.
0402
MIN FLOW
Cause: Measured flow below minimum limit.



Remedy:

  • Check the pump system for reasons such as leaks.

  • Check parameters 81.18…81.24.
0403
MAX FLOW
Cause: Measured flow above maximum limit.



Remedy:

  • Check the pump system for reasons that might cause an increase in measured flow.

  • Check parameters 81.18…81.24.
0404
LOW PRESSURE
Cause: Pressure at pump inlet too low.



Remedy:

  • Check for a closed valve on the inlet side of the pump.

  • Check piping for leaks.
0405
HIGH PRESSURE
Cause: Pressure at pump outlet too high.



Remedy:

  • Check piping for blocks.
0406
VERY LOW PRESS
Cause: Pressure at pump inlet too low.



Remedy:

  • Check for a closed valve on the inlet side of the pump.

  • Check piping for leaks.
0407
VERY HIGH PRESS
Cause: Pressure at pump outlet too high.



Remedy:

  • Check piping for blocks.
0408
MAX CLEANINGS
Cause: Maximum number of cleaning sequences exceeded.



Remedy:

  • Check for reasons that might have increased the monitored signal (parameter 82.09).

  • Check for increased fluid viscosity or faulty pump bearings.
0409
MF MASTER LOST
Cause: Drive cannot detect a master on the drive-to-drive link and is not allowed to become master.



Remedy:

  • Check that there are drives on the link allowed to become master.

  • Check the wiring of the drive-to-drive link.
0410
MF NO SHARED DATA
Cause: Shared signals not received.



Remedy:

  • Check that at least one drive has signal sharing enabled (parameter 76.12).

  • Check status, comms settings, and wiring of the drive sharing signals.
06xx
Custom Application
Cause: Faults generated by custom application program.



Remedy:

  • Check custom application program.