Sửa chữa Servo Abb

Code

Alarm

(fieldbus code)

Cause

What to do

2000

BRAKE START

TORQUE

(0x7185)

Programmable fault:

42.12 Brake fault func

Mechanical brake alarm. Alarm

is activated if required motor

starting torque (42.08 Brake

open torq) is not achieved.

Check brake open torque setting,

parameter 42.08.

Check drive torque and current limits.

See parameter group 20 Limits.

2001

BRAKE NOT

CLOSED

(0x7186)

Programmable fault:

42.12 Brake fault func

Mechanical brake control

alarm. Alarm is activated e.g. if

brake acknowledgement is not

as expected during brake

closing.

Check mechanical brake connection.

Check mechanical brake settings in

parameter group 42 Mech brake ctrl.

To determine whether problem is with

acknowledgement signal or brake, check

if brake is closed or open.

2002

BRAKE NOT OPEN

(0x7187)

Programmable fault:

42.12 Brake fault func

Mechanical brake control

alarm. Alarm is activated e.g. if

brake acknowledgement is not

as expected during brake

opening.

Check mechanical brake connection.

Check mechanical brake settings in

parameter group 42 Mech brake ctrl.

To determine whether problem is with

acknowledgement signal or brake, check

if brake is closed or open.

2003

SAFE TORQUE OFF

(0xFF7A)

Programmable fault:

30.07 Sto diagnostic

Safe Torque Off function is

active, i.e. safety circuit

signal(s) connected to

connector X6 is lost while drive

is stopped and parameter

30.07 Sto diagnostic is set to

Alarm.

Check safety circuit connections. For

more information, see appropriate drive

hardware manual.

2004

STO MODE CHANGE

(0xFF7A)

Error in changing Safe Torque

Off supervision, i.e. parameter

30.07 Sto diagnostic setting

could not be changed to value

Alarm.

Contact your local ABB representative.

2005

MOTOR

TEMPERATURE

(0x4310)

Programmable fault:

31.01 Mot temp1 prot

Estimated motor temperature

(based on motor thermal

model) has exceeded alarm

limit defined by parameter

31.03 Mot temp1 almLim.

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

(parameters 31.09…31.14).

Measured motor temperature

has exceeded alarm limit

defined by parameter 31.03

Mot temp1 almLim.

Check that actual number of sensors

corresponds to value set by parameter

31.02 Mot temp1 src.

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.

2006

EMERGENCY OFF

(0xF083)

Drive has received emergency

OFF2 command.

To restart drive, activate Run enable

signal (source selected by parameter

10.11 Run enable) and start drive.

2007

RUN ENABLE

(0xFF54)

No Run enable signal is

received.

Check setting of parameter 10.11 Run

enable. Switch signal on (e.g. in the

fieldbus Control Word) or check wiring of

selected source.

2008

ID-RUN

(0xFF84)

Motor identification run is on.

This alarm belongs to normal start-up

procedure. Wait until drive indicates that

motor identification is completed.

Motor identification is required.

This alarm belongs to normal start-up

procedure.

Select how motor identification should be

performed, parameter 99.13 Idrun mode.

Start identification routines by pressing

Start key.

2009

EMERGENCY STOP

(0xF081)

Drive has received emergency

stop command (OFF1/OFF3).

Check that it is safe to continue

operation.

Return emergency stop push button to

normal position (or adjust the fieldbus

Control Word accordingly).

Restart drive.

2011

BR OVERHEAT

(0x7112)

Brake resistor temperature has

exceeded alarm limit defined

by parameter 48.07 Br temp

alarmlim.

Stop drive. Let resistor cool down.

Check resistor overload protection

function settings (parameters

48.01…48.05).

Check alarm limit setting, parameter

48.07 Br temp alarmlim.

Check that braking cycle meets allowed

limits.

2012

BC OVERHEAT

(0x7181)

Brake chopper IGBT

temperature has exceeded

internal alarm limit.

Let chopper cool down.

Check resistor overload protection

function settings (parameters

48.01…48.05).

Check that braking cycle meets allowed

limits.

Check that drive supply AC voltage is not

excessive.

Code

Alarm

(fieldbus code)

Cause

What to do

2013

DEVICE OVERTEMP

(0x4210)

Measured drive temperature

has exceeded internal alarm

limit.

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)

Interface board (between

power unit and control unit)

temperature has exceeded

internal alarm limit.

Let drive cool down.

2015

BC MOD OVERTEMP

(0x7183)

Input bridge or brake chopper

temperature has exceeded

internal alarm limit.

Let drive cool down.

2016

IGBT OVERTEMP

(0x7184)

Drive temperature based on

thermal model has exceeded

internal alarm limit.

Check ambient conditions.

Check air flow and fan operation.

Check heatsink fins for dust pick-up.

Check motor power against unit power.

2017

FIELDBUS COMM

(0x7510)

Programmable fault:

50.02 Comm loss func

Cyclical communication

between drive and fieldbus

adapter module or between

PLC and fieldbus adapter

module is lost.

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

LOCAL CTRL LOSS

(0x5300)

Programmable fault:

30.03 Local ctrl loss

Control panel or PC tool

selected as active control

location for drive has ceased

communicating.

Check PC tool or control panel

connection.

Check control panel connector.

Replace control panel in mounting

platform.

2019

AI SUPERVISION

(0x8110)

Programmable fault:

13.32 AI superv func

An analogue input has reached

limit defined by parameter

13.33 AI superv cw.

Check analogue input source and

connections.

Check analogue input minimum and

maximum limit settings.

2020

FB PAR CONF

(0x6320)

The drive does not have a

functionality requested by

PLC, or requested functionality

has not been activated.

Check PLC programming.

Check settings of parameter group 50

Fieldbus.

2021

NO MOTOR DATA

(0x6381)

Parameters in group 99 have

not been set.

Check that all the required parameters in

group 99 have been set.

2022

ENCODER 1

FAILURE (0x7301)

Encoder 1 has been activated

by parameter but the encoder

interface (FEN-xx) cannot be

found.

Check parameter 90.01 Encoder 1 sel

setting corresponds to actual encoder

interface 1 (FEN-xx) installed in drive

Slot 1/2 (parameter 09.20 Option slot1 /

09.21 Option slot2).

Note: The new setting will only take

effect after parameter 90.10 Enc par

refresh is used or after the JCU Control

Unit is powered up the next time.

Code

Alarm

(fieldbus code)

Cause

What to do

2023

ENCODER 2

FAILURE (0x7381)

Encoder 2 has been activated

by parameter but the encoder

interface (FEN-xx) cannot be

found.

Check parameter 90.02 Encoder 2 sel

setting corresponds to actual encoder

interface 1 (FEN-xx) installed in drive

Slot 1/2 (parameter 09.20 Option slot1 /

09.21 Option slot2).

Note: The new setting will only take

effect after parameter 90.10 Enc par

refresh is used or after the JCU Control

Unit is powered up the next time.

2027

FEN TEMP MEAS

FAILURE

(0x7385)

Error in temperature

measurement when

temperature sensor (KTY or

PTC) connected to encoder

interface FEN-xx is used.

Check that parameter 31.02 Mot temp1

src / 31.06 Mot temp2 src setting

corresponds to actual encoder interface

installation (09.20 Option slot1 / 09.21

Option slot2):

If one FEN-xx module is used:

– Parameter 31.02 Mot temp1 src / 31.06

Mot temp2 src must be set either to KTY

1st FEN or PTC 1st FEN. The FEN-xx

module can be in either Slot 1 or Slot 2.

If two FEN-xx modules are used:

– When parameter 31.02 Mot temp1 src /

31.06 Mot temp2 src is set to KTY 1st

FEN or PTC 1st FEN, the encoder

installed in drive Slot 1 is used.

– When parameter 31.02 Mot temp1 src /

31.06 Mot temp2 src is set to KTY 2nd

FEN or PTC 2nd FEN, the encoder

installed in drive Slot 2 is used.

Error in temperature

measurement when KTY

sensor connected to encoder

interface FEN-01 is used.

FEN-01 does not support temperature

measurement with KTY sensor. Use PTC

sensor or other encoder interface

module.

2030

RESOLVER

AUTOTUNE ERR

(0x7388)

Resolver autotuning routines,

which are automatically started

when resolver input is

activated for the first time,

have failed.

Check cable between resolver and

resolver interface module (FEN-21) and

order of connector signal wires at both

ends of cable.

Check resolver parameter settings.

For resolver parameters and information,

see parameter group 92 Resolver conf.

Note: Resolver autotuning routines

should always be performed after

resolver cable connection has been

modified. Autotuning routines can be

activated by setting parameter 92.02 Exc

signal ampl or 92.03 Exc signal freq, and

then setting parameter 90.10 Enc par

refresh to Configure.

2031

ENCODER 1 CABLE

(0x7389)

Encoder 1 cable fault detected.

Check cable between FEN-xx interface

and encoder 1. After any modifications in

cabling, re-configure interface by

switching drive power off and on, or by

activating parameter 90.10 Enc par

refresh.

Code

Alarm

(fieldbus code)

Cause

What to do

2032

ENCODER 2 CABLE

(0x738A)

Encoder 2 cable fault detected.

Check cable between FEN-xx interface

and encoder 2. After any modifications in

cabling, re-configure interface by

switching drive power off and on, or by

activating parameter 90.10 Enc par

refresh.

2033

D2D

COMMUNICATION

(0x7520)

Programmable fault:

57.02 Comm loss func

On the master drive: The drive

has not been replied to by an

activated follower for five

consecutive polling cycles.

Check that all drives that are polled

(parameters 57.04 Follower mask 1 and

57.05 Follower mask 2) on the drive-to

drive link are powered, properly

connected to the link, and have the

correct node address.

Check the drive-to-drive link wiring.

On a follower drive: The drive

has not received new

reference 1 and/or 2 for five

consecutive reference

handling cycles.

Check the settings of parameters 57.06

Ref 1 src and 57.07 Ref 2 src) on the

master drive.

Check the drive-to-drive link wiring.

2034

D2D BUFFER

OVERLOAD

(0x7520)

Programmable fault:

57.02 Comm loss func

Transmission of drive-to-drive

references failed because of

message buffer overflow.

Contact your local ABB representative.

2035

PS COMM

(0x5480)

Communication errors

detected between the JCU

Control Unit and the power unit

of the drive.

Check the connections between the JCU

Control Unit and the power unit.

2036

RESTORE

(0x6300)

Restoration of backed-up

parameters failed.

Contact your local ABB representative.

2037

CUR MEAS

CALIBRATION

(0x2280)

Current measurement

calibration will occur at next

start.

Informative alarm.

2038

AUTOPHASING

(0x3187)

Autophasing will occur at next

start.

Informative alarm.

2039

EARTH FAULT

(0x2330)

Programmable fault:

30.05 Earth fault

Drive has detected load

unbalance typically due to

earth fault in motor or motor

cable.

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 no earth fault can be detected, contact

your local ABB representative.

2040

AUTORESET

(0x6080)

A fault is to be autoreset.

Informative alarm. See parameter group

32 Automatic reset.

2041

MOTOR NOM VALUE

(0x6383)

The motor configuration

parameters are set incorrectly.

Check the settings of the motor

configuration parameters in group 99.

The drive is not dimensioned

correctly.

Check that the drive is sized correctly for

the motor.

2042

D2D CONFIG

(0x7583)

The settings of drive-to-drive

link configuration parameters

(group 57) are incompatible.

Check the settings of the parameters in

group 57 D2D communication.

Code

Alarm

(fieldbus code)

Cause

What to do

2043

STALL

(0x7121)

Programmable fault:

30.09 Stall function

Motor is operating in stall

region because of e.g.

excessive load or insufficient

motor power.

Check motor load and drive ratings.

Check fault function parameters.

2044

LCURVE

(0x2312)

Programmable fault:

34.01 Overload func /

34.02 Underload func

Overload or underload limit

has been exceeded.

Check the settings of the parameters in

group 34 User load curve.

2045

LCURVE PAR

(0x6320)

The load curve has been

incorrectly or inconsistently

defined.

Check the settings of the parameters in

group 34 User load curve.

2046

FLUX REF PAR

(0x6320)

The U/f (voltage/frequency)

curve has been incorrectly or

inconsistently defined.

Check the settings of the parameters in

group 38 Flux ref.

2047

SPEED FEEDBACK

(0x8480)

No speed feedback is

received.

Check the settings of the parameters in

group 19 Speed calculation.

Check encoder installation. See the

description of fault 0039 for more

information.

2048

OPTION COMM

LOSS

(0x7000)

Communication between drive

and option module (FEN-xx

and/or FIO-xx) is lost.

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

determine whether module or connector

is damaged: Test each module

individually in Slot 1 and Slot 2.

2049

MOTTEMPAL2

(0x4313)

Programmable fault:

31.05 Mot temp2 prot

Estimated motor temperature

(based on motor thermal

model) has exceeded alarm

limit defined by parameter

31.07 Mot temp2 almLim.

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

(parameters 31.09…31.14).

Measured motor temperature

has exceeded alarm limit

defined by parameter 31.07

Mot temp2 almLim.

Check that actual number of sensors

corresponds to value set by parameter

31.06 Mot temp2 src.

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.

2050

IGBTOLALARM

(0x5482)

Excessive IGBT junction to

case temperature. This fault

protects the IGBT(s) and can

be activated by a short circuit

in the motor cable.

Check motor cable.

2051

IGBTTEMPALARM

(0x4210)

Drive IGBT temperature is

excessive. Fault trip limit is

100%.

Check ambient conditions.

Check air flow and fan operation.

Check heatsink fins for dust pick-up.

Check motor power against drive power.

Code

Alarm

(fieldbus code)

Cause

What to do

2052

COOLALARM

(0x4290)

Drive module temperature is

excessive.

Check ambient temperature. If it exceeds

40 °C (104 °F), ensure that load current

does not exceed derated load capacity of

drive. See appropriate Hardware Manual.

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.

2053

MENU CHG

PASSWORD REQ

(0x6F81)

Loading a parameter listing

requires a password.

Enter password at parameter 16.03 Pass

code.

2054

MENU CHANGED

(0x6F82)

A different parameter listing is

being loaded.

Informative alarm.

2055

DEVICE CLEAN

(0x5080)

Maintenance alarm.

See parameter group 44 Maintenance.

2056

COOLING FAN

(0x5081)

Maintenance alarm.

See parameter group 44 Maintenance.

2057

ADD COOLING

(0x5082)

Maintenance alarm.

See parameter group 44 Maintenance.

2058

CABINET FAN

(0x5083)

Maintenance alarm.

See parameter group 44 Maintenance.

2059

DC CAPACITOR

(0x5084)

Maintenance alarm.

See parameter group 44 Maintenance.

2060

MOTOR BEARING

(0x738C)

Maintenance alarm.

See parameter group 44 Maintenance.

2061

MAIN CONTACTOR

(0x548D)

Maintenance alarm.

See parameter group 44 Maintenance.

2062

RELAY OUTPUT SW

(0x548E)

Maintenance alarm.

See parameter group 44 Maintenance.

2063

MOTOR START

COUNT

(0x6180)

Maintenance alarm.

See parameter group 44 Maintenance.

2064

POWER UP COUNT

(0x6181)

Maintenance alarm.

See parameter group 44 Maintenance.

2065

DC CHARGE COUNT

(0x6182)

Maintenance alarm.

See parameter group 44 Maintenance.

2066

ONTIME1 ALARM

(0x5280)

Maintenance alarm.

See parameter group 44 Maintenance.

2067

ONTIME2 ALARM

(0x5281)

Maintenance alarm.

See parameter group 44 Maintenance.

2068

EDGE1 ALARM

(0x5282)

Maintenance alarm.

See parameter group 44 Maintenance.

2069

EDGE2 ALARM

(0x5283)

Maintenance alarm.

See parameter group 44 Maintenance.

2070

VALUE1 ALARM

(0x5284)

Maintenance alarm.

See parameter group 44 Maintenance.

2071

VALUE2 ALARM

(0x5285)

Maintenance alarm.

See parameter group 44 Maintenance.

Code

Alarm

(fieldbus code)

Cause

What to do

2400

SOLUTION ALARM

(0x6F80)

Alarm generated by custom

application program.

Check custom application program.

Code

Alarm

(fieldbus code)

Cause

What to do

Code

Fault

(fieldbus code)

Cause

What to do

0001

OVERCURRENT

(0x2310)

Output current has exceeded

internal fault limit.

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.

Check encoder cable (including

phasing).

0002

DC OVERVOLTAGE

(0x3210)

Excessive intermediate circuit

DC voltage

Check that overvoltage controller is on,

parameter 47.01 Overvolt ctrl.

Check mains for static or transient

overvoltage.

Check brake chopper and resistor (if

used).

Check deceleration time.

Use coast-to-stop function (if applicable).

Retrofit frequency converter with brake

chopper and brake resistor.

0003

DEVICE OVERTEMP

(0x4210)

Measured drive temperature

has exceeded internal fault

limit.

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)

Short-circuit in motor cable(s)

or motor

Check motor and motor cable.

Check there are no power factor

correction capacitors or surge absorbers

in motor cable.

0005

DC UNDERVOLTAGE

(0x3220)

Intermediate circuit DC voltage

is not sufficient due to missing

mains phase, blown fuse or

rectifier bridge internal fault.

Check mains supply and fuses.

0006

EARTH FAULT

(0x2330)

Programmable fault:

30.05 Earth fault

Drive has detected load

unbalance typically due to

earth fault in motor or motor

cable.

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:

– measure insulation resistances of motor

and motor cable.

If no earth fault can be detected, contact

your local ABB representative.

0007

FAN FAULT

(0xFF83)

Fan is not able to rotate freely

or fan is disconnected. Fan

operation is monitored by

measuring fan current.

Check fan operation and connection.

0008

IGBT OVERTEMP

(0x7184)

Drive temperature based on

thermal model has exceeded

internal fault limit.

Check ambient conditions.

Check air flow and fan operation.

Check heatsink fins for dust pick-up.

Check motor power against unit power.

0009

BC WIRING

(0x7111)

Brake resistor short circuit or

brake chopper control fault

Check brake chopper and brake resistor

connection.

Ensure brake resistor is not damaged.

0010

BC SHORT CIRCUIT

(0x7113)

Short circuit in brake chopper

IGBT

Replace brake chopper.

Ensure brake resistor is connected and

not damaged.

0011

BC OVERHEAT

(0x7181)

Brake chopper IGBT

temperature has exceeded

internal alarm limit.

Let chopper cool down.

Check resistor overload protection

function settings (parameters

48.01…48.05).

Check that braking cycle meets allowed

limits.

Check that drive supply AC voltage is not

excessive.

0012

BR OVERHEAT

(0x7112)

Brake resistor temperature has

exceeded fault limit defined by

parameter 48.06 Br temp

faultlim.

Stop drive. Let resistor cool down.

Check resistor overload protection

function settings (parameters

48.01…48.05).

Check fault limit setting, parameter 48.06

Br temp faultlim.

Check that braking cycle meets allowed

limits.

0013

CURR MEAS GAIN

(0x3183)

Difference between output

phase U2 and W2 current

measurement gain is too great.

Contact your local ABB representative.

0014

CABLE CROSS CON

(0x3181)

Programmable fault:

30.08 Cross

connection

Incorrect input power and

motor cable connection (i.e.

input power cable is connected

to drive motor connection).

Check input power connections.

0015

SUPPLY PHASE

(0x3130)

Programmable fault:

30.06 Suppl phs loss

Intermediate circuit DC voltage

is oscillating due to missing

input power line phase or

blown fuse.

Check input power line fuses.

Check for input power supply imbalance.

0016

MOTOR PHASE

(0x3182)

Programmable fault:

30.04 Mot phase loss

Motor circuit fault due to

missing motor connection (all

three phases are not

connected).

Connect motor cable.

0017

ID-RUN FAULT

(0xFF84)

Motor ID Run is not completed

successfully.

Check motor settings (parameters

99.04…99.13).

Check that no limits prevent ID run. The

following must apply:

20.05 Maximum current > 99.06 Mot nom

current

For Reduced and Normal ID run:

– 20.01 Maximum speed > 55% of 99.09

Mot nom speed

– 20.02 Minimum speed < 0

– Supply voltage > 65% of 99.07 Mot

nom voltage

– Maximum torque (selected by 20.06

Torq lim sel) > 100% (only for Normal ID

run).

Retry.

Code

Fault

(fieldbus code)

Cause

What to do

0018

CURR U2 MEAS

(0x3184)

Measured offset error of U2

output phase current

measurement is too great.

(Offset value is updated during

current calibration.)

Contact your local ABB representative.

0019

CURR V2 MEAS

(0x3185)

Measured offset error of V2

output phase current

measurement is too great.

(Offset value is updated during

current calibration.)

Contact your local ABB representative.

0020

CURR W2 MEAS

(0x3186)

Measured offset error of W2

output phase current

measurement is too great.

(Offset value is updated during

current calibration.)

Contact your local ABB representative.

0021

STO1 LOST

(0x8182)

Safe Torque Off function is

active, i.e. safety circuit signal

1 connected between X6:1 and

X6:3 is lost while drive is at

stopped state and parameter

30.07 Sto diagnostic is set to

Alarm or No.

Check safety circuit connections. For

more information, see appropriate drive

hardware manual.

0022

STO2 LOST

(0x8183)

Safe Torque Off function is

active, i.e. safety circuit signal

2 connected between X6:2 and

X6:4 is lost while drive is at

stopped state and parameter

30.07 Sto diagnostic is set to

Alarm or No.

Check safety circuit connections. For

more information, see appropriate drive

hardware manual.

0023

STO MODE CHANGE

(0xFF7A)

Error in changing Safe Torque

Off supervision, i.e. parameter

30.07 Sto diagnostic setting

could not be changed to value

Fault.

Contact your local ABB representative.

0024

INTBOARD

OVERTEMP

(0x7182)

Interface board (between

power unit and control unit)

temperature has exceeded

internal fault limit.

Let drive cool down.

0025

BC MOD OVERTEMP

(0x7183)

Input bridge or brake chopper

temperature has exceeded

internal fault limit.

Let drive cool down.

0026

AUTOPHASING

(0x3187)

Autophasing routine (see

section Autophasing on page

30) failed.

Try other autophasing modes (see

parameter 11.07 Autophasing mode) if

possible.

0027

PU LOST

(0x5400)

Connection between the JCU

Control Unit and the power unit

of the drive is lost.

Check the connections between the JCU

Control Unit and the power unit.

0028

PS COMM

(0x5480)

Communication errors

detected between the JCU

Control Unit and the power unit

of the drive.

Check the connections between the JCU

Control Unit and the power unit.

0029

IN CHOKE TEMP

(0xFF81)

Temperature of internal AC

choke excessive.

Check cooling fan.

Code

Fault

(fieldbus code)

Cause

What to do

0030

EXTERNAL

(0x9000)

Fault in external device. (This

information is configured

through one of programmable

digital inputs.)

Check external devices for faults.

Check parameter 30.01 External fault

setting.

0031

SAFE TORQUE OFF

(0xFF7A)

Programmable fault:

Programmable fault:

30.07 Sto diagnostic

Safe Torque Off function is

active, i.e. safety circuit

signal(s) connected to

connector X6 is lost during

start or run, or while drive is

stopped and parameter 30.07

Sto diagnostic is set to Fault.

Check safety circuit connections. For

more information, see appropriate drive

hardware manual.

0032

OVERSPEED

(0x7310)

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.

Check minimum/maximum speed

settings, parameters 20.01 Maximum

speed and 20.02 Minimum speed.

Check adequacy of motor braking torque.

Check applicability of torque control.

Check need for brake chopper and

resistor(s).

0033

BRAKE START

TORQUE

(0x7185)

Programmable fault:

42.12 Brake fault func

Mechanical brake fault. Fault is

activated if required motor

starting torque (42.08 Brake

open torq) is not achieved.

Check brake open torque setting,

parameter 42.08.

Check drive torque and current limits.

See parameter group 20 Limits.

0034

BRAKE NOT

CLOSED

(0x7186)

Programmable fault:

42.12 Brake fault func

Mechanical brake control

alarm. Fault is activated e.g. if

brake acknowledgement is not

as expected during brake

closing.

Check mechanical brake connection.

Check mechanical brake settings in

parameter group 42 Mech brake ctrl.

To determine whether problem is with

acknowledgement signal or brake, check

if brake is closed or open.

0035

BRAKE NOT OPEN

(0x7187)

Programmable fault:

42.12 Brake fault func

Mechanical brake control

alarm. Fault is activated e.g. if

brake acknowledgement is not

as expected during brake

opening.

Check mechanical brake connection.

Check mechanical brake settings in

parameter group 42 Mech brake ctrl.

To determine whether problem is with

acknowledgement signal or brake, check

if brake is closed or open.

0036

LOCAL CTRL LOSS

(0x5300)

Programmable fault:

30.03 Local ctrl loss

Control panel or PC tool

selected as active control

location for drive has ceased

communicating.

Check PC tool or control panel

connection.

Check control panel connector.

Replace control panel in mounting

platform.

0037

NVMEM

CORRUPTED

(0x6320)

Drive internal fault

Note: This fault cannot be

reset.

Contact your local ABB representative.

0038

OPTIONCOMM LOSS

(0x7000)

Communication between drive

and option module (FEN-xx

and/or FIO-xx) is lost.

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

determine whether module or connector

is damaged: Test each module

individually in Slot 1 and Slot 2.

Code

Fault

(fieldbus code)

Cause

What to do

0039

ENCODER1

(0x7301)

Encoder 1 feedback fault

If fault appears during first start-up before

encoder feedback is used:

– Check cable between encoder and

encoder interface module (FEN-xx) and

order of connector signal wires at both

ends of cable.

If fault appears after encoder feedback

has already been used or during drive

run:

– Check that encoder connection wiring

or encoder is not damaged.

– Check that encoder interface module

(FEN-xx) connection or module is not

damaged.

– Check earthings (when disturbances

are detected in communication between

encoder interface module and encoder).

For more information on encoders, see

parameter groups 90 Enc module sel, 92

Resolver conf and 93 Pulse enc conf.

0040

ENCODER 2

(0x7381)

Encoder 2 feedback fault.

See fault 0039.

0045

FIELDBUS COMM

(0x7510)

Programmable fault:

50.02 Comm loss func

Cyclical communication

between drive and fieldbus

adapter module or between

PLC and fieldbus adapter

module is lost.

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)

Drive internal fault

Contact your local ABB representative.

0047

MOTOR OVERTEMP

(0x4310)

Programmable fault:

31.01 Mot temp1 prot

Estimated motor temperature

(based on motor thermal

model) has exceeded fault limit

defined by parameter 31.04

Mot temp1 fltLim.

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

(parameters 31.09…31.14).

Measured motor temperature

has exceeded fault limit

defined by parameter 31.04

Mot temp1 fltLim.

Check that actual number of sensors

corresponds to value set by parameter

31.02 Mot temp1 src.

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.

0049

AI SUPERVISION

(0x8110)

Programmable fault:

13.32 AI superv func

An analogue input has reached

limit defined by parameter

13.33 AI superv cw.

Check analogue input source and

connections.

Check analogue input minimum and

maximum limit settings.

Code

Fault

(fieldbus code)

Cause

What to do

0050

ENCODER 1 CABLE

(0x7389)

Programmable fault:

90.05 Enc cable fault

Encoder 1 cable fault detected.

Check cable between FEN-xx interface

and encoder 1. After any modifications in

cabling, re-configure interface by

switching drive power off and on, or by

activating parameter 90.10 Enc par

refresh.

0051

ENCODER 2 CABLE

(0x738A)

Programmable fault:

90.05 Enc cable fault

Encoder 2 cable fault detected.

Check cable between FEN-xx interface

and encoder 2. After any modifications in

cabling, re-configure interface by

switching drive power off and on, or by

activating parameter 90.10 Enc par

refresh.

0052

D2D CONFIG

(0x7583)

Configuration of the drive-to

drive link has failed for a

reason other than those

indicated by alarm A-2042, for

example start inhibition is

requested but not granted.

Contact your local ABB representative.

0053

D2D COMM

(0x7520)

Programmable fault:

57.02 Comm loss func

On the master drive: The drive

has not been replied to by an

activated follower for five

consecutive polling cycles.

Check that all drives that are polled

(parameters 57.04 Follower mask 1 and

57.05 Follower mask 2) on the drive-to

drive link are powered, properly

connected to the link, and have the

correct node address.

Check the drive-to-drive link wiring.

On a follower drive: The drive

has not received new

reference 1 and/or 2 for five

consecutive reference

handling cycles.

Check the settings of parameters 57.06

Ref 1 src and 57.07 Ref 2 src) on the

master drive.

Check the drive-to-drive link wiring.

0054

D2D BUF OVLOAD

(0x7520)

Programmable fault:

90.05 Enc cable fault

Transmission of drive-to-drive

references failed because of

message buffer overflow.

Contact your local ABB representative.

0055

TECH LIB

(0x6382)

Resettable fault generated by

a technology library.

Refer to the documentation of the

technology library.

0056

TECH LIB CRITICAL

(0x6382)

Permanent fault generated by

a technology library.

Refer to the documentation of the

technology library.

0057

FORCED TRIP

(0xFF90)

Generic Drive Communication

Profile trip command.

Check PLC status.

0058

FB PAR ERROR

(0x6320)

The drive does not have a

functionality requested by

PLC, or requested functionality

has not been activated.

Check PLC programming.

Check settings of parameter group 50

Fieldbus.

0059

STALL

(0x7121)

Programmable fault:

30.09 Stall function

Motor is operating in stall

region because of e.g.

excessive load or insufficient

motor power.

Check motor load and drive ratings.

Check fault function parameters.

0060

LOAD CURVE

(0x2312)

Programmable fault:

34.01 Overload func /

34.02 Underload func

Overload or underload limit

has been exceeded.

Check the settings of the parameters in

group 34 User load curve.

Code

Fault

(fieldbus code)

Cause

What to do

0061

SPEED FEEDBACK

(0x8480)

No speed feedback is

received.

Check the settings of the parameters in

group 19 Speed calculation.

Check encoder installation. See the

description of fault 0039 (ENCODER1)

for more information.

0062

D2D SLOT COMM

(0x7584)

Drive-to-drive link is set to use

an FMBA module for

communication, but no module

is detected in specified slot.

Check the settings of parameters 57.01

and 57.15. Ensure that the FMBA

module has been detected by checking

parameters 09.20…09.22.

Check that the FMBA module is correctly

wired.

Try installing the FMBA module into

another slot. If the problem persists,

contact your local ABB representative.

0063

MOTOR TEMP2

(0x4313)

Programmable fault:

31.05 Mot temp2 prot

Estimated motor temperature

(based on motor thermal

model) has exceeded fault limit

defined by parameter 31.08

Mot temp2 fltLim.

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

(parameters 31.09…31.14).

Measured motor temperature

has exceeded fault limit

defined by parameter 31.08

Mot temp2 fltLim.

Check that actual number of sensors

corresponds to value set by parameter

31.06 Mot temp2 src.

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.

0064

IGBT OVERLOAD

(0x5482)

Excessive IGBT junction to

case temperature. This fault

protects the IGBT(s) and can

be activated by a short circuit

in the motor cable.

Check motor cable.

0065

IGBT TEMP

(0x4210)

Drive IGBT temperature is

excessive. Fault trip limit is

100%.

Check ambient conditions.

Check air flow and fan operation.

Check heatsink fins for dust pick-up.

Check motor power against drive power.

0066

COOLING

(0x4290)

Drive module temperature is

excessive.

Check ambient temperature. If it exceeds

40 °C (104 °F), ensure that load current

does not exceed derated load capacity of

drive. See appropriate Hardware Manual.

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.

0201

T2 OVERLOAD

(0x0201)

Firmware time level 2 overload

Note: This fault cannot be

reset.

Contact your local ABB representative.

0202

T3 OVERLOAD

(0x6100)

Firmware time level 3 overload

Note: This fault cannot be

reset.

Contact your local ABB representative.

Code

Fault

(fieldbus code)

Cause

What to do

0203

T4 OVERLOAD

(0x6100)

Firmware time level 4 overload

Note: This fault cannot be

reset.

Contact your local ABB representative.

0204

T5 OVERLOAD

(0x6100)

Firmware time level 5 overload

Note: This fault cannot be

reset.

Contact your local ABB representative.

0205

A1 OVERLOAD

(0x6100)

Application time level 1 fault

Note: This fault cannot be

reset.

Contact your local ABB representative.

0206

A2 OVERLOAD

(0x6100)

Application time level 2 fault

Note: This fault cannot be

reset.

Contact your local ABB representative.

0207

A1 INIT FAULT

(0x6100)

Application task creation fault

Note: This fault cannot be

reset.

Contact your local ABB representative.

0208

A2 INIT FAULT

(0x6100)

Application task creation fault

Note: This fault cannot be

reset.

Contact your local ABB representative.

0209

STACK ERROR

(0x6100)

Drive internal fault

Note: This fault cannot be

reset.

Contact your local ABB representative.

0210

FPGA ERROR

(0xFF61)

Drive internal fault

Note: This fault cannot be

reset.

Contact your local ABB representative.

0301

UFF FILE READ

(0x6300)

File read error

Note: This fault cannot be

reset.

Contact your local ABB representative.

0302

APPL DIR CREATION

(0x6100)

Drive internal fault

Note: This fault cannot be

reset.

Contact your local ABB representative.

0303

FPGA CONFIG DIR

(0x6100)

Drive internal fault

Note: This fault cannot be

reset.

Contact your local ABB representative.

0304

PU RATING ID

(0x5483)

Drive internal fault

Note: This fault cannot be

reset.

Contact your local ABB representative.

0305

RATING DATABASE

(0x6100)

Drive internal fault

Note: This fault cannot be

reset.

Contact your local ABB representative.

0306

LICENSING

(0x6100)

Drive internal fault

Note: This fault cannot be

reset.

Contact your local ABB representative.

0307

DEFAULT FILE

(0x6100)

Drive internal fault

Note: This fault cannot be

reset.

Contact your local ABB representative.

0308

APPLFILE PAR

(0x6300)

Corrupted application file

Note: This fault cannot be

reset.

Reload application.

If fault is still active, contact your local

ABB representative.

Code

Fault

(fieldbus code)

Cause

What to do

0309

APPL LOADING

(0x6300)

Corrupted application file

Note: This fault cannot be

reset.

Reload application.

If fault is still active, contact your local

ABB representative.

0310

USERSET LOAD

(0xFF69)

Loading of user set is not

successfully completed

because:

– requested user set does not

exist

– user set is not compatible

with drive program

– drive has been switched off

during loading.

Reload.

0311

USERSET SAVE

(0xFF69)

User set is not saved because

of memory corruption.

Check the setting of parameter 95.01 Ctrl

boardSupply.

If the fault still occurs, contact your local

ABB representative.

0312

UFF OVERSIZE

(0x6300)

UFF file is too big.

Contact your local ABB representative.

0313

UFF EOF

(0x6300)

UFF file structure failure

Delete faulty file or contact your local

ABB representative.

0314

TECH LIB

INTERFACE

(0x6100)

Incompatible firmware

interface

Note: This fault cannot be

reset.

Contact your local ABB representative.

0315

RESTORE FILE

(0x630D)

Restoration of backed-up

parameters failed.

Contact your local ABB representative.

0316

DAPS MISMATCH

(0x5484)

Mismatch between JCU

Control Unit firmware and

power unit logic versions.

Contact your local ABB representative.

0317

SOLUTION FAULT

(0x6200)

Fault generated by function

block SOLUTION_FAULT in

the solution program.

Check the usage of the

SOLUTION_FAULT block in the solution

program.

0318

MENU HIDING

(0x6200)

Menu hiding file missing or

corrupted.

Reload application.

Contact your local ABB representative.