ABB ACS560 Drive

Download Links

📥 Download Catalog 📥 Download Manual
📥 Download Hardware Manual  

Wiring Details

Below image show terminal details:

Brake Resistance Details

Model no.R. MinR. MaxP.BR Max
3-phase, 380 to 480 VohmohmKW
ACS560-01-01A8-4999330.56
ACS560-01-02A6-4996280.83
ACS560-01-03A3-4994281.13
ACS560-01-04A0-4992851.65
ACS560-01-05A6-4992062.25
ACS560-01-07A2-4531393.3
ACS560-01-09A4-4531024.5
ACS560-01-12A6-432766
ACS560-01-017A-432548.25
ACS560-01-025A-4233911.25
ACS560-01-033A-4163715
ACS560-01-039A-4102720
ACS560-01-046A-4102225

Faults & Alarms

Search from below list for ACS560 drive faults & alarms:

Fault CodeCause & Solution
64FF
Fault reset		Cause: A fault has been reset from the panel, Drive composer PC tool, fieldbus or I/O.
Solution: This is an Informative only.
A2B1
Overcurrent 		Cause: Output current has exceeded internal fault limit. In addition to an actual overcurrent situation, this warning may also be caused by an earth fault or supply
phase loss.

Solution:

1. Check motor load.
2. Check acceleration times in parameter group
23 Speed reference ramp (speed control),
26 Torque reference chain (torque control) or
28 Frequency reference chain (frequency control).
3. Also check parameters 46.01 Speed scaling,
46.02 Frequency scaling and
46.03 Torque scaling.
4.Check motor and motor cable (including phasing and delta/star connection).
5. Check for an earth fault in motor or
motor cables by measuring the insulation resistances of motor and motor cable. See chapter Electrical installation, section
6. Checking the insulation of the assembly in the hardware manual of the drive.
7. Check there are no contactors opening
and closing in motor cable.
8. Check that the start-up data in parameter group 99 Motor data corresponds to the motor rating plate.
9. Check that there are no power factor
correction capacitors or surge absorbers in motor cable.
A2B3
Earth leakage 		Cause: Drive has detected load unbalance typically due to earth fault in motor or motor cable.

Solution

1. Check there are no power factor correction capacitors or surge absorbers in motor cable.
2. Check for an earth fault in motor or motor cables by measuring the insulation resistances of motor and motor cable.
3. Check the insulation of the assembly in the hardware manual of the drive. If an earth fault is found, fix or change the motor cable and/or motor.
4. If no earth fault can be detected then hardware issue in drive.
A2B4
Short circuit		Cause: Short-circuit in motor cable(s) or motor.

Solution:

1. Check motor and motor cable for cabling errors.
2. Check motor and motor cable (including phasing and delta/star connection).
3. Check for an earth fault in motor or motor cables by measuring the insulation resistances of motor and motor cable.
4. 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.

Solution:

1. Check motor cable.
2. Check ambient conditions.
3. Check air flow and fan operation.
4. Check heatsink fins for dust pick-up.
5. Check motor power against drive power.
A3A1
DC link overvoltage 		Cause: Intermediate circuit DC voltage too high (when the drive is stopped).

Solution:

1. Check the supply voltage setting (parameter 95.01 Supply voltage).
Note that the wrong setting of the parameter may cause the motor to rush uncontrollably, or may overload the brake chopper or resistor.
2. Check the supply voltage.
3. If the problem persists, then hardware issue in drive or other issue in drive.
A3A2
DC link undervoltage 		Cause: Intermediate circuit DC voltage too low (when the drive is stopped).

Solution:

1. Check the supply voltage setting (parameter 95.01 Supply voltage).
Note that the wrong setting of the parameter may cause the motor to rush uncontrollably, or may overload the brake chopper or resistor.
2. Check the supply voltage.
3. If the problem persists, then hardware issue in drive or other issue in drive.
A3AA
DC not charged 		Cause: The voltage of the intermediate DC circuit has not yet risen to operating level.

Solution:

1. Check the supply voltage setting (parameter 95.01 Supply voltage).
Note that the wrong setting of the parameter may cause the motor to rush uncontrollably, or may overload the brake chopper or resistor.
2. Check the supply voltage.
3. If the problem persists, then hardware issue in drive or other issue in drive.
A490
Incorrect temperature
sensor setup		Cause: Sensor type mismatch.

Solution: Check the settings of temperature source parameters 35.11.
A491
External temperature 1		Cause: Measured temperature 1 has exceeded warning limit.

Solution

1. Check the value of parameter 35.02 Measured temperature 1.
2. Check the cooling of the motor (or other equipment whose temperature is being measured).
3. Check the value of 35.13 Temperature 1 warning limit.
A492
External
temperature 2		Cause: Measured temperature 2 has exceeded warning limit.

Solution:

1. Check the value of parameter 35.03 Measured temperature 2.
2. Check the cooling of the motor (or other equipment whose temperature is being measured).
Check the value of 35.23 Temperature 2 warning limit
A4A0
Control board
temperature.		Cause: Control board temperature is excessive.
1 – Sensor fault.

Solution:

1. Check the sensor and change the control board.
A4A1
IGBT
overtemperature		Cause: Estimated drive IGBT temperature is excessive.

Solution:

1. Check ambient conditions.
2. Check air flow and fan operation.
3. Check heatsink fins for dust pick-up.
4. Check motor power against drive power.
A4A9
Cooling 		Cause: Drive module temperature is excessive.

Solution:

1. Check ambient temperature. If it exceeds 50 °C /122 °F, ensure that load current does not exceed derated load capacity of drive.
2. Check drive module cooling air flow and fan operation.
3. 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.

Solution:

Check ambient conditions.
Check air flow and fan operation.
Check heatsink fins for dust pick-up.
Check motor power against drive power.
A4B1
Excess temperature
difference		Cause: High temperature difference between the IGBTs of different phases.

Solution:

1. Check the motor cabling.
2. Check cooling of drive module(s).
A4F6
IGBT temperature		Cause: Drive IGBT temperature is excessive.

Solution:

Check ambient conditions.
Check air flow and fan operation.
Check heatsink fins for dust pick-up.
Check motor power against drive power.
A580
PU communication 		Cause: Communication errors detected between the drive control unit and the power unit.

Solution:

1. Check the connections between the drive control unit and the power unit.
A581
Fan 		Cause: Cooling fan feedback missing.

Solution:

1. Check the auxiliary code to identify the fan.
Code 0 denotes main fan 1. Other codes (format XYZ): “X” specifies state code (1: ID run, 2: normal). “Y” = 0, “Z” specifies the index of the fan (1: Main fan 1, 2: Main fan 2, 3: Main fan 3).
2. Check fan operation and connection.
3. Replace fan if faulty.
A582
Auxiliary
fan missing 		Cause: An auxiliary cooling fan (connected to the fan connectors on the control board) is stuck or disconnected.

Solution:

Check the auxiliary code.
Check auxiliary fan(s) and connection(s).
Replace faulty fan.
Make sure the front cover of the drive is in place and tightened.
If the commissioning of the drive requires that the cover is off, this warning will be generated even if the corresponding fault is defeated.

0001 Auxiliary fan 1 missing.

0002 Auxiliary fan 2 missing.
A590
Drive HW
initialization		Cause: Drive hardware setup is initializing.

Solution: See auxiliary code.

1 – Initializing HW settings for the first time.
A591
Drive HW
initialization		Cause: Initialization of the drive hardware.

Solutions:

Check the auxiliary code. See actions for each code below.

0000 Drive hardware setup is initializing. Wait for the setup to initialize.
0001 Initializing HW settings for the first time. Wait for the setup to initialize.
A5A0
Safe torque off		Cause: Safe torque off function is active, ie safety circuit signal(s) connected to connector STO is lost.

Solution:

1. Check safety circuit connections.
2. Check parameter 31.22 STO indication run/stop.
A5EA
Measurement circuit
temperature		Cause: Problem with internal temperature measurement of the drive.

Solution:

1. Check drive hardware.
2. May be hardware issue in drive.
A5EB
PU board
powerfail 		Cause: Power unit power supply failure.

Solution:

1. Check drive hardware.
2. May be hardware issue in drive.
A5ED
Measurement
circuit ADC		Cause: Measurement circuit fault.

Solution:

1. Check drive hardware.
2. May be hardware issue in drive.
A5EE
Measurement
circuit DFF		Cause: Measurement circuit fault.

Solution:

1. Check drive hardware.
2. May be hardware issue in drive.
A5EF
PU state
feedback		Cause: State feedback from output phases does not match control signals.

Solution:

1. Check drive hardware.
2. May be hardware issue in drive.
A5F0
Charging feedback 		Cause: Charging feedback signal missing.

Solution:

1. Check the feedback signal coming from the charging system.
A5F1
Redundant
measurement		Cause: Duplicated measurements are beyond limits.

Solution: There is hardware or software issue in drive need to repair or replace drive.
A5F2
Overtemperature
Hardware		Cause: Excessive hardware temperature.

Solution: There is hardware or software issue in drive need to repair or replace drive.
A682
Flash erase
speed 		Cause: The flash memory (in the memory unit) has been erased too frequently, compromising the lifetime of the memory.

Solution:

1. Avoid forcing unnecessary parameter saves by parameter 96.07 Parameter save manually or cyclic parameter writes (such as user logger triggering through parameters).
2. Check the auxiliary code (format XYYY YZZZ). “X” specifies the source of warning (1: generic flash erase supervision). “ZZZ” specifies the flash subsector number that generated the warning.
A6A4
Motor nominal
value		Cause: The motor parameters are set incorrectly. The drive is not dimensioned
correctly.

Solution:

1. Check the settings of the motor configuration parameters in group 99.
2. Check that the drive is sized correctly for the motor.
A6A5
No motor data 		Cause: Parameters in group 99 have not been set.


Solution:

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

Note: It is normal for this warning to appear during the start-up and continue until the motor data is
entered.
A6A6
Voltage category
unselected		Cause: The voltage category has not been defined.


Solution: Set voltage category in parameter 95.01 Supply voltage.
A6A7
System time
not set 		Cause: System time is not set.
A6B0
User lock
is open		Cause: The user lock is open, ie. user lock configuration parameters 96.100… 96.102 are visible.


Solution: Close the user lock by entering an invalid pass code in parameter 96.02 Pass code.

A6B1
User pass
code not
confirmed		Cause: A new user pass code has been entered in parameter 96.100 but not confirmed in 96.101.

Solution: Confirm the new pass code by entering the same code in 96.101. To cancel, close the user lock without confirming the new code. See section User lock.
A6D1
FBA A
parameter
conflict		Cause: The drive does not have a functionality requested by a PLC, or requested functionality has not been activated.

Solution:

1. Check PLC programming.
2. Check settings of parameter groups 50 Fieldbus adapter (FBA).
A6E5
AI parametrization 		Cause: The current/voltage hardware setting of an analog input does not correspond to parameter settings.


Solution:

1. Check the event log for an auxiliary code. The code identifies the analog input whose settings are in conflict. Adjust parameter 12.15/ 12.25.

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


Solution: Check the auxiliary code. See actions
for each code below.

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

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

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

0003 – Overload point below underload point. Check that each overload point (37.31…37.35) has a higher value than the corresponding underload point (37.21… 37.25).
AFFE
Override
active		Cause: Drive is in override mode.

Solution:

1. This is an informative warnin.
A780
Motor stall		Cause: Motor is operating in stall region because of e.g. excessive load or insufficient motor power.


Solution:

1. Check motor load and drive ratings.
2. Check fault function parameters.
3. This is a programmable warning check parameter 31.24 Stall function.
A783
Motor overload		Cause: Motor current is too high.

Solution:

1. Check the motor, and the machinery coupled to motor, for overload.
2. Adjust the parameters used for the motor overload function (35.51…35.53) and 35.55…35.56.
A784
Motor disconnect 		Cause: All three output phases are disconnected from motor.

Solution:

1. Check if parameter 95.26 enables the use of a motor disconnect switch. If not, check the following:
• All switches between drive and motor are closed.
• All cables between drive and motor are connected and secured.

If no issue was detected and drive output was actually connected to motor, contact your supplier.
A791
Brake resistor 		Cause: Brake resistor broken or not connected.


Solution:

1. Check that a brake resistor has been connected.
2. Check the condition of the brake resistor.
A792
Brake resistor
wiring 		Cause: Brake resistor short circuit or fault in brake chopper.

Solution:

1. Check brake chopper and brake resistor connections.
A793
BR excess
temperature		Cause: Brake resistor temperature has exceeded warning limit defined by parameter 43.12 Brake resistor warning limit.


Solution:

1. Stop drive. Let resistor cool down.
2. Check resistor overload protection function settings (parameter group 43 Brake chopper).
3. Check warning limit setting, parameter 43.12 Brake resistor warning limit.
4. Check that the resistor has been dimensioned correctly.
5. Check that braking cycle meets allowed limits.
A794
BR data		Cause: Brake resistor data has not been given.

Solution: Check the resistor data settings (parameters 43.08…43.10).

0000 0001 Resistance value too low. Check value of 43.10.

0000 0002 Thermal time constant not given.
Check value of 43.08.

0000 0003 Maximum continuous power not given. Check value of 43.09.
A79C
BC IGBT excess
temperature		Cause: Brake chopper IGBT temperature has exceeded internal warning limit.

Solution:

1. Let chopper cool down.
2. Check for excessive ambient temperature.
3. Check for cooling fan failure.
4. Check for obstructions in the air flow.
5 Check the dimensioning and cooling of the cabinet.
6. Check resistor overload protection function settings (parameters 43.06… 43.10).
7. Check minimum allowed resistor value for the chopper being used.
9. Check that braking cycle meets allowed limits.
10 Check that drive supply AC voltage is not excessive.
A7AB
Extension I/O
configuration
failure		Cause: The I/O module is not connected to the device or parameterization conflict with currently connected I/O-module.

For example, if the drive is connected to an I/O & Modbus module and removed later, the drive displays a warning if connection between any of the parameter and the configured digital/analog output signal is lost.

Solution:

1. Make sure that the I/O module is connected to the device and no parameters are connected to non- existing I/O parameters.
2. Make sure that the actual installed options match the values of parameters 07.35 (Drive configuration), 07.36 (Drive configuration 2), and 15.01 (Extension module type)
A7AC
I/O module
internal
error		Cause: Calibration data is not stored in the IO module. Analog signals are not working with full accuracy.

Solution:

1. Replace the IO module.
A7A1
Mechanical brake
closing failed		Cause: Mechanical brake control warning.

Solution:

1. Check mechanical brake connection.
2. Check mechanical brake settings in parameter group 44 Mechanical brake control.
3. Check that acknowledgment signal matches the actual status of the brake.
A7A2
Mechanical brake
opening failed		Cause: Status of mechanical brake acknowledgment is not as expected during brake open.

Solution:

1. Check mechanical brake connection.
2. Check mechanical brake settings in parameter group 44 Mechanical brake control.
3. Check that acknowledgment signal matches the actual status of brake.
A7A5
Mechanical brake
opening not allowed		Cause: Open conditions of mechanical brake cannot be fulfilled (e.g., brake has been prevented from opening by parameter 44.11)

Solution:

1. Check mechanical brake settings in parameter group 44 Mechanical brake control (especially 44.11).
2. Check that the acknowledgment signal (if used) matches the actual status of the brake.
A7C1
FBA A
communication		Cause: Cyclical communication between drive and fieldbus adapter module A or between PLC and fieldbus adapter module A is lost.

Solution:

1. Check status of fieldbus communication.
2. Check settings of parameter groups 50 Fieldbus adapter (FBA), 51 FBA A settings, 52 FBA A data in and 53 FBA A data out.
3. Check cable connections.
4. Check if communication master is able to communicate.
5. This is a Programmable warning: check parameter 50.02 FBA A comm loss function.
A7CE
EFB comm loss		Cause: Communication loss action Communication break in embedded fieldbus (EFB) communication.

Solution:

1. Check the status of the fieldbus master (online/offline/error etc.).
2. Check cable connections to the EIA-485 terminals 25, 26, 27 and 28 on the control unit.
3. This is a programmable warning check parameter 58.14.
A7EE
Panel loss		Cause: Control panel or PC tool selected as active control location for drive has ceased communicating.

Solution:

1. Check PC tool or control panel connection.
2. Check control panel connector.
3. Check mounting platform if being used. Disconnect and reconnect the control panel.
4. This is a programmable warning check parameter 49.05 Communication loss action.
A88F
Cooling fan 		Cause: Maintenance timer limit exceeded.

Solution:

1. Replace the drive cooling fan.
2. Parameter 05.04 Fan on-time counter shows the running time of the cooling fan.
A8A0
AI supervision		Cause: An analog signal is outside the limits specified for the analog input.

Solution:

1. Check signal level at the analog input.
2. Check the wiring connected to the input.
3. Check the minimum and maximum limits of the input in parameter group 12 Standard AI.
4. This is a programmable warning check parameter 12.03 AI supervision function.
A8A1
RO life
warning 		Cause: The relay has changed states more than the recommended number of times.

Solution:

1. Change the control board or stop using the relay output.
A8A2
RO toggle
warning		Cause: The relay output is changing states faster than recommended, eg. if a fast changing frequency signal is connected to it. The relay lifetime will be exceeded shortly.

Solution: Replace the signal connected to the relay output source with a less frequently changing signal.
A8B0
Signal supervision		Cause: Warning generated by a signal supervision function.

Solution:
1. Check the source of the warning (parameter 32.07 Supervision 1 signal).
2. This is a programmable warning check parameter 32.06 Supervision 1 action
A8B1
Signal supervision		Cause: Warning generated by a signal supervision function.

Soultion:

1. Check the source of the warning (parameter 32.17 Supervision 2 signal).
2. This is a programmable warning check parameter 32.16 Supervision 2 action.
A8B2
Signal supervision		Cause: Warning generated by a signal supervision function.

Soultion:

1. Check the source of the warning (parameter 32.27 Supervision 3 signal).
2. This is a programmable warning check parameter 32.26 Supervision 3 action.
A8B3
Signal supervision		Cause: Warning generated by a signal supervision function.

Soultion:

1. Check the source of the warning (parameter 32.37 Supervision 4 signal).
2. This is a programmable warning check parameter 32.36 Supervision 4 action.
A8B4
Signal supervision		Cause: Warning generated by a signal supervision function.

Soultion:

1. Check the source of the warning (parameter 32.47 Supervision 5 signal).
2. This is a programmable warning check parameter 32.46 Supervision 5 action.
A8B5
Signal supervision		Cause: Warning generated by a signal supervision function.

Soultion:

1. Check the source of the warning (parameter 32.57 Supervision 6 signal).
2. This is a programmable warning check parameter 32.56 Supervision 6 action.
A8B6
Current limit 		Cause: Motor actual current exceeded the limit defined in parameter 30.17 Maximum current.

Solution:

1. Reduce the motor load.
2. Check for any jam or stall in motor.
A8BE
ULC overload
warning 		Cause: User load curve: Signal has been too long over the overload curve.

Solution:

See parameter 37.03 ULC overload actions.

001 Overload occurred between speed point 37.11 ULC speed table point 1 and 37.12 ULC speed table point 2. Check the load.

002 Overload occurred between speed point 37.12 ULC speed table point 2 and 37.13 ULC speed table point 3. Check the load.

003 Overload occurred between speed point 37.13 ULC speed table point 3 and 37.14 ULC speed table point 4. Check the load.

004 Overload occurred between speed point 37.14 ULC speed table point 4 and 37.15 ULC speed table point 5. Check the load.
A8BF
ULC underload
warning		Cause: User load curve: Signal has been too long under the underload curve.

Solution:

See parameter 37.04 ULC underload actions.

001 Underload occurred between speed point 37.11 ULC speed table point 1 and 37.12 ULC speed table point 2. Check the load.

002 Underload occurred between speed point 37.12 ULC speed table point 2 and 37.13 ULC speed table point 3. Check the load.

003 Underload occurred between speed point 37.13 ULC speed table point 3 and 37.14 ULC speed table point 4. Check the load.

004 Underload occurred between speed point 37.14 ULC speed table point 4 and 37.15 ULC speed table point 5. Check the load.
A8C0
ULC invalid
speed table		Cause: User load curve: X-axis points (speed) are not valid.

Soultion:

Check that points fulfill conditions. See parameter
37.11 ULC speed table point 1.
A8C5
ULC invalid
underload table		Cause: User load curve: Underloadcurve points are not valid.

Soultion: Check that points fulfill conditions. See parameter 37.21 ULC underload point 1.
A8C6
ULC invalid
overload table		Cause: User load curve- Overload curve points are not valid.

Soultion: Check that points fulfill conditions. See parameter 37.31 ULC overload point 1.

A981
External warning 1		Cause: Fault in external device 1.

Soultion:

1. Check the external device.
2. Check setting of parameter 31.01 External event 1 source.
3. This is a Programmable warning: check parameter – 31.01 External event 1 source 31.02 External event 1 type
A982
External warning 2		Cause: Fault in external device 2.

Soultion:

1. Check the external device.
2. Check setting of parameter 31.03 External event 2 source.
3. This is a Programmable warning: Check parameter 31.03 External event 2 source, 31.04 External event 2 type
A983
External warning 3		Cause: Fault in external device 3.

Soultion:

Check the external device.
Check setting of parameter 31.05 External event 3 source.
This is a Programmable warning: check parameter 31.05 External event 3 source, 31.06 External event 3 type.
A984
External warning 4		Cause: Fault in external device 5.

Soultion:

1. Check the external device.
2. Check setting of parameter 31.07 External event 4 source.
3. This is a Programmable warning: check parameter 31.07 External event 4 source 31.08 External event 4 type.
A985
External warning 5		Cause: Fault in external device 5.

Solution:

Check the external device.
Check setting of parameter 31.09 External event 5 source.
This is a Programmable warning: check parameter 31.09 External event 5 source 31.10 External event 5 type.
A991
Safe motor
temperature		Cause: You have configured a season which starts before the previous season.

Solution: Configure the seasons with increasing start dates, see parameters 34.60 Season 1 start date 34.63 Season 4 start date.
AF88
Season
configuration
warning		Cause: You have configured a season which starts before the previous season.

Solution:

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

Solution:

Check the auxiliary code (format XXXX YYYY). “YYYY” indicates the problem (see actions for each code below).

0000 The drive was stopped before the autotune routine finished. Repeat autotune until successful.

0001 The drive was started but was not ready to follow the autotune command. Make sure the prerequisites of the autotune run are fulfilled

0002 Required torque reference could not be reached before the drive reached maximum speed. Decrease torque step

0003 Motor could not accelerate to the maximum/minimum speed. Increase torque step or decrease speed step.

0004 Motor could not decelerate to the maximum/minimum speed. Increase torque step or decrease speed step.

0005 Motor could not decelerate with full autotune torque. Decrease torque stepor speed step.

AFAA
Autoreset 		Cause: A fault is about to be autoreset.

Solution:

1. This is a informative warning no need to take any action.
2. See the settings in parameter group 31 Fault functions.

AFE1
Emergency stop
(off2)		Cause: Drive has received an emergency stop (mode selection off2) command.

Solution:

1. Check that it is safe to continue operation. Then return emergency stop push button to normal position. Restart drive.
2. 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.

Solution:

1. Check that it is safe to continue operation. Then return emergency stop push button to normal position. Restart drive.
2. If the emergency stop was unintentional, check the source selected by parameter 21.05 Emergency stop source.

AFE9
Start delay		Cause: The start delay is active and the drive will start the motor after a predefined delay.

Solution:

1. This is a informative warning no need to take any action.
2. See parameter 21.22 Start delay.
AFF5
Override
new start
required		Cause: The Safe torque off function was active and has been reset while in Override.

Solution: A new start signal is required to start the drive again.
AFF8
Motor
heating
active 		Cause: Pre-heating is being performed.

Solution:

1. Informative warning.
2. Motor pre-heating is active.
3. Current specified by parameter 21.16 Pre-heating current is being passed through the motor.
AFEB
Run enable
missing		Cause: No run enable signal is received.

Solution:

1. Check setting of parameter 20.12 Run enable 1 source.
2. 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.

Solution:

1. 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 of 240s.

Solution:

1. Switch enable to rotate signal on (eg. in digital inputs).
2. Check the setting of (and source selected by) parameter 20.22 Enable to rotate.
AFF6
Identification run		Cause: Motor ID run will occur at next start.

Solution:

1. This is a informative warning no need to take any action.
B5F6
Identification
run 		Cause: Motor ID run completed successfully.

Solution: This is a informative warning.
B5A0
STO event		Cause: Safe torque off function is active, ie. safety circuit signal(s) connected to connector STO is lost.

Solution:

1. Check safety circuit connections.
2. This is programmable event check parameter 31.22 STO indication run/stop.
D501
No more
available
PFC motors		Cause: No more PFC motors can be started because they can be interlocked or in the Hand mode.

Solution: Check that there are no interlocked PFC motors, see parameters: 76.81…76.84. If all motors are in use, the PFC system is not adequately dimensioned to handle the demand.
D502
All motors
interlocked		Cause: All the motors in the PFC system are interlocked.

Solution: Check that there are no interlocked PFC motors, see parameters 76.81…76.84.
D503
VSD controlled PFC
motor interlocked		Cause: The motor connected to the drive is interlocked (unavailable).

Solution:

1. Motor connected to the drive is interlocked and thus cannot be started.
2. Remove the corresponding interlock to start the drive controlled PFC motor.
3. See parameters 76.81…76.84.
FA90
STO diagnostics
failure		Cause: The software is not working properly.

Solution: Restart the control unit.
1080
Backup/Restore
timeout		Cause: Panel or PC tool has failed to communicate with the drive when backup was being made or restored.

Solution:

1. Request backup or restore again.
1081
Rating ID
fault 		Cause: Drive software is not able to read the rating ID of the drive.

Solution:

1. Reset the fault to make the drive try to reread the rating ID.
2. If the fault reappears, cycle the power to the drive.
2281
Calibration		Cause: Measured offset of output phase current measurement or difference between output phase U2 and W2 current measurement is too great (the values are updated during current calibration).

Solution:

1. Try performing the current calibration again.
2. If problem not resolved then need to repair or replace drive.
2310
Overcurrent		Cause: Output current has exceeded internal fault limit. In addition to an actual overcurrent situation, this fault may also be caused by an earth fault or supply phase loss.

Solution:

1. Check motor load.
2. Check acceleration times in parameter group 23 Speed reference ramp (speed control), 26 Torque reference chain (torque control) or 28 Frequency reference chain (frequency control).
3. Also check parameters 46.01 Speed scaling, 46.02 Frequency scaling and 46.03 Torque scaling.
4. Check motor and motor cable (including phasing and delta/star connection).
5. Check there are no contactors opening and closing in motor cable.
6. Check that the start-up data in parameter group 99 Motor data corresponds to the motor rating plate.
7. Check that there are no power factor correction capacitors or surge absorbers in motor cable.
8. Check for an earth fault in motor or motor cables by measuring the insulation resistances of motor and motor cable.
2330
Earth leakage		Cause: Drive has detected load unbalance typically due to earth fault in motor or motor cable.

Solution:

1. Check there are no power factor correction capacitors or surge absorbers in motor cable.
2. Check for an earth fault in motor or motor cables by measuring the insulation resistances of motor and motor cable.
3. Try running the motor in scalar control mode if allowed. (See parameter 99.04 Motor control mode.)
4. After this if problem not resolved then need to repair or replace drive.
2340
Short circuit 		Cause: Short-circuit in motor cable(s) or motor. Aux code 0x0080 indicates that the state feedback from output phases does not match the control signals.

Solution:

1. Check motor and motor cable for cabling errors.
2. Check there are no power factor correction capacitors or surge absorbers in motor cable.
3. 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.

Solution:

1. Check motor cable.
2. Check ambient conditions.
3. Check air flow and fan operation.
4. Check heatsink fins for dust pick-up.
5. Check motor power against drive power.
2392
BU earth
leakage 		Cause: Total earth leakage of inverter modules is excessive.

Solution:

1. Check there are no power factor correction capacitors or surge absorbers in motor cable.
2. Measure insulation resistances of motor cables and motor.
3130
Input phase
loss 		Cause: Intermediate circuit DC voltage is oscillating due to missing input power line phase or blown fuse.

Solution:

1. Check input power line fuses.
2. Check for loose power cable connections.
3. Check for input power supply imbalance.
3181
Wiring or
earth fault		Cause: Incorrect input power and motor cable connection (ie. input power cable is connected to drive motor connection).

Solution:

1. Check input power connections.
3210
DC link
overvoltage 		Cause: Excessive intermediate circuit DC voltage.

Solution:

1. Check that overvoltage control is on (parameter 30.30 Overvoltage control).
2. Check that the supply voltage matches the nominal input voltage of the drive.
3. Check the supply line for static or transient overvoltage.
4. Check deceleration time. Use coast-to-stop function (if applicable).
5. Retrofit drive with brake chopper and brake resistor.
6. Check that the brake resistor is dimensioned properly and the resistance is between acceptable range for the drive.
3220
DC link
undervoltage 		Cause: Intermediate circuit DC voltage is not sufficient because of a missing supply phase, blown fuse or fault in the rectifier bridge.

Solution:

1. Check supply cabling, fuses and switchgear.
3291
BU DC
link
difference		Cause: Difference in DC voltages between parallel connected inverter modules.

Solution:

Check the auxiliary code (format XXXY YYZZ). “XXX” specifies the source of the first error (see “YYY”). “YYY” specifies the module through which BCU control unit channel the fault was received (1: Channel 1, 2: Channel 2, 4: Channel 3, 8: Channel 4, …, 800: Channel 12).
3381
Output phase
loss		Cause: Motor circuit fault due to missing motor connection (any of the three phases not connected).
In scalar control mode, the drive detects fault only when the output frequency is above 10% of the motor nominal frequency.


Solution:

1. Connect motor cable.
2. If the drive is in scalar mode and nominal current of the motor is less than 1/6 of the nominal output current of the drive, set parameter 31.19 Motor phase loss to No action.
4110
Control board
temperature		Cause: Control board temperature is too high.

Solution:

1. Check proper cooling of the drive.
2. Check the auxiliary cooling fan.
4210
IGBT
overtemperature		Cause: Estimated drive IGBT temperature is excessive.

Solution:

1. Check air flow and fan operation.
2. Check heatsink fins for dust pick-up.
3. Check motor power against drive power.
4. Check ambient conditions.
4290
Cooling 		Cause: Drive module temperature is excessive.

Solution:

1. Check ambient temperature. If it exceeds 50 °C /122 °F, ensure that load current does not exceed derated load capacity of drive.
2. Check drive module cooling air flow and fan operation.
3. 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.

Solution:

1. Check ambient conditions.
2. Check air flow and fan operation.
3. Check heatsink fins for dust pick-up.
4. Check motor power against drive power.
4310
Excess
temperature 		Cause: Power unit module temperature is excessive.

Solution:

1. Check ambient conditions.
2. Check air flow and fan operation.
3. Check heatsink fins for dust pick-up.
4. Check motor power against drive power.
4380
Excess
temperature
difference		Cause: High temperature difference between the IGBTs of different phases.

Solution:

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

Solution:

1. Check the value of parameter 35.02 Measured temperature 1.
2. Check the cooling of the motor (or other equipment whose temperature is being measured).
3. Check the value of parameter 35.12 Temperature 1 fault limit.
4982
External
temperature 2		Cause: Measured temperature 2 has exceeded fault limit.

Solution:

1. Check the value of parameter 35.03 Measured temperature 2.
2. Check the cooling of the motor (or other equipment whose temperature is being measured).
3. Check the value of parameter 35.22 Temperature 2 fault limit.
4991
Safe motor
temperature		Cause: The CPTC-02 module indicates overtemperature:
• motor temperature is too high, or
• the thermistor is in shortcircuit.

Solution:

Check the cooling of the motor.
Check the motor load and drive ratings.
Check the wiring of the temperature sensor.
Repair wiring if faulty.
Measure the resistance of the sensor.
Replace the sensor if faulty.
5080
Fan 		Cause: Cooling fan is stuck or disconnected.

Solution:

1. Check fan operation and connection.
2. Replace fan if faulty.
5081
Auxiliary
fan broken		Cause: An auxiliary cooling fan is stuck or disconnected.

Solution:

1. Check auxiliary fan(s) and connection(s).
2. Replace fan if faulty.

0001 Auxiliary fan 1 broken.
0002 Auxiliary fan 2 broken.
5089
SMT circuit
malfunction		Cause: Safe motor temperature fault is generated and STO
event/fault/warning is not generated.

Solution:

Check connection between the relay output of the module and the STO terminal.
5090
STO hardware
failure		Cause: STO hardware diagnostics has detected hardware failure.


Solution: There is an hardware issue in drive. Need to repair or replace drive.
5091
Safe
torque off		Cause: Safe torque off function is active, ie. safety circuit signal(s) connected to connector STO is broken during start or run.

Solution:

1. Check safety circuit connections.
2. This is a Programmable fault: check parameter 31.22 STO indication run/stop.
5092
PU logic
error 		Cause: Power unit memory has cleared.

Solution: There is an hardware or software issue in drive. Need to repair or replace drive.
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.

Solution:

1. Cycle the power to the drive.
2. You may have to be repeat this.
3. If fault not resolved after this then need to repair or replace drive.
5094
Measurement
circuit
temperature		Cause: Problem with internal temperature measurement of the drive.

Solution: There is an hardware or software issue in drive. Need to repair or replace drive.
5095
Redundant
measurement		Cause: Duplicated measurements are beyond limits.

Solution: There is hardware or software issue in drive need to repair or replace drive.
5096
Overtemperature
hardware 		Cause: Excessive hardware temperature.

Solution: There is an hardware or software issue in drive need to repair or replace drive.

5098
I/O
communication
loss		Cause: Communication failure to standard I/O.

Solution: Try resetting the fault or cycle the power to the drive.
5681
PU
communication 		Cause: Communication errors detected between the drive control unit and the power unit.

Solution: Check the connection between the drive control unit and the power unit.
5682
Power unit
lost 		Cause: Connection between the drive control unit and the power unit is lost.

Solution: Check the connection between the control unit and the power unit.
5690
PU communication
internal		Cause: Internal communication error.

Solution: There is an hardware or software issue in drive. Need to repair or replace drive.
5691
Measurement
circuit ADC		Cause: Measurement circuit fault.

Solution: There is an hardware or software issue in drive. Need to repair or replace drive.
5692
PU board
powerfail 		Cause: Power unit power supply failure.

Solution: There is an hardware or software issue in drive. Need to repair or replace drive.
5693
Measurement
circuit DFF		Cause: Measurement circuit fault.

Solution: There is an hardware or software issue in drive. Need to repair or replace drive.
5695
Reduced run 		Cause: Configured power units not found.

Solution: Configure the power units.
5697
Charging
feedback 		Cause: Charging feedback signal missing.

Solution: Check the feedback signal coming from the charging system.
5698
Unknown PU
fault 		Cause: The power unit logic generated a fault which is not known by software.

Solution: Check the logic and software compatibility.
50A0
Fan 		Cause: Cooling fan stuck or disconnected.

Solution:

1. Check fan operation and connection.
2. Replace fan if faulty.
6181
FPGA version
incompatible		Cause: Firmware and FPGA versions are incompatible.

Solution:

1. Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power.
2. After this same problem comes then need to repair or replace drive.
6306
FBA A
mapping file		Cause: Fieldbus adapter A mapping file read error.

Solution: There is an hardware or software issue in drive need to repair or replace drive.
6481
Task
overload 		Cause: Internal fault. There is an internal issue in drive

Solution:

1. Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power.
2. After this same problem then need to repair or replace drive.
6487
Stack overflow		Cause: Internal fault. There is an internal issue in drive

Solution:

1. Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power.
2. After this same problem then need to repair or replace drive.
64A3
Application
loading 		Cause: Application file incompatible or corrupted.

Check the auxiliary code. See actions for each code below.

Solution:

8006 Not enough memory for the application. Reduce the size of the application. Reduce the number of parameter mappings. See the drive-specific log generated by Automation Builder.

8007 The application contains the wrong system library version. Update the system library or reinstall Automation Builder. See the drive-specific log generated by Automation Builder.

8008 The application is empty. In Automation Builder, give a “Clean” command and reload the application.

8009 The application contains invalid tasks. In Automation Builder, check application task configuration, give a “Clean all” command, and reload the application.

800A The application contains an unknown target (system) library function. Update the system library or reinstall Automation Builder. See the drive-specific log generated by Automation Builder.
64A1
Internal
file load 		Cause: File read error. There is an internal issue in drive

Solution:

1. Reboot the control unit (using parameter 96.08 Control board boot) or by cycling power.
2. After this same problem then need to repair or replace drive.
64A4
Rating ID
fault 		Cause: Rating ID load error.

Solution: There is a hardware or software issue in drive need to repair or replace drive.
64A6
Adaptive program		Cause: Adaptive program has faulted.

Solution: There is an hardware or software issue in drive need to repair or replace drive.
64B1
Internal
SSW fault 		Cause: A fatal error in the power-up phase of System Software (SSW).

Solution:

SSW runs in partial functionality mode.

1 – Starting OS time tick failed
2 – Creating system tasks failed
3 – Initializing file system failed
4 – Checking file system failed
5 – Initializing WoRm volumes failed
6 – Loading FPGA configuration failed
7 – Loading application program failed
64B2
User set
fault 		Cause: Loading of user parameter set failed because
• requested set does not exist
• set is not compatible with control program
• drive was switched off during loading.

Solution: Ensure that a valid user parameter set exists. Reload if uncertain.
64B3 Macro
parameterization
error		Cause: Macro parameterization failed, eg. Parameter default value that cannot be changed has been attempted to write.
64E1
Kernel
overload		Cause: Operating system error.

Solution:

1. Reboot the control unit(using parameter 96.08 Control board boot) or by cycling power.
2. After this same problem then need to repair or replace drive.
6581
Parameter
system 		Cause: Parameter load or save failed.

Solution: Try forcing a save using parameter 96.07 Parameter save manually. Retry.
6591
Backup/Restore
timeout		Cause: During backup creating or restoring operation a panel or PC-tool has failed to communicate with the drive as part of this operation.

Solution: Check panel or PC-tool communication and if it is still in backup or restore state.
65A1
FBA A
parameter
conflict		Cause: The drive does not have a functionality requested by PLC, or requested functionality has not been activated.

Solution:

1. Check PLC programming.
2. Check settings of parameter groups 50 Fieldbus adapter (FBA) and 51 FBA A settings.
6681
EFB comm
loss		Cause: Communication break in embedded fieldbus (EFB) communication.

Solution:

1. Check the status of the fieldbus master (online/offline/error etc.).
2. Check cable connections to the EIA-485/X5 terminals 29, 30 and 31 on the control unit.
3. This is a Programmable fault: check parameter 58.14 Communication loss action.
6682
EFB config
file 		Cause: Embedded fieldbus (EFB) configuration file could not be read.

Solution: There is an hardware or software issue in drive. Need to repair or replace drive.
6683
EFB invalid
parameterization		Cause: Embedded fieldbus (EFB) parameter settings inconsistent or not compatible with selected protocol.

Solution: Check the settings in parameter group 58 Embedded fieldbus.
6684
EFB load
fault 		Cause: Embedded fieldbus (EFB) protocol firmware could not be loaded or version mismatch between EFB protocol firmware and drive firmware.

Solution: There is an hardware or software issue in drive need to repair or replace drive.
6685
EFB fault 2 		Cause: Fault reserved for the EFB protocol application.

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

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

Solution: Reset the fault. If fault not reset then need to repair or replace drive.
6885
Text file
overflow		Cause: Internal fault.

Solution: Reset the fault. If fault not reset then need to repair or replace drive.
7081
Control panel
loss		Cause: Control panel or PC tool selected as active control location for drive has ceased communicating.

Solution:

1. Check PC tool or control panel connection.
2. Check control panel connector.
3. Disconnect and reconnect the control panel.
4. This is a Programmable fault: check parameter 49.05 Communication loss action.
7082
I/O module
comm loss		Cause: Communication between IO module and drive is not working properly.

Solution: There is an hardware issue in drive. need to repair or replace the drive.
7085
Incompatible
option
module		Cause: Fieldbus option module not supported.

Solution: Replace the module with a supported type.
7086
I/O module
AI Over
voltage		Cause: Overvoltage detected in AI. AI is changed to voltage mode. AI will return automatically back to mA mode when the AI signal level is in accepted limits.

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

Solution:

Check the auxiliary code. See actions for each code below.

0001 S1/S2 DIP switch position on BIO-01 has changed after power up. Reboot control unit either by cycling the power or through parameter 96.08 Control board boot to activate new DIP switch position.

0002 S1/S2 DIP switch positions are such that DO1 would be in both S1 and S2 pins. This is not a supported combination. Change S1/S2 DIP switch positions to a supported combination, see parameter 05.99 BIO-01 DIP switch status.
71A2
Mechanical brake
closing failed		Cause: Mechanical brake control fault. Activated e.g., if brake acknowledgment is not as expected during brake closing.

Solution:

1. Check mechanical brake connection.
2. Check mechanical brake settings in parameter group 44 Mechanical brake control.
3. Check that the acknowledgment signal matches the actual status of the brake.
4. This is a Programmable fault: check parameter 44.17 Brake fault function
71A5
Mechanical brake
opening not
allowed		Cause: Open conditions of mechanical brake cannot be fulfilled (e.g., the brake has been prevented from opening by parameter 44.11).

Solution:

1. Check mechanical brake settings in parameter group 44 Mechanical brake control (especially 44.11).
2. Check that the acknowledgment signal (if used) matches the actual status of the brake.
7100
Excitation
current 		Cause: Excitation current feedback low or missing.
7121
Motor stall		Cause: Motor is operating in stall region because of e.g. excessive load or insufficient motor power.

Solution:

1. Check motor load and drive ratings.
2. Check fault function parameters.
7122
Motor
overload 		Cause: Motor current is too high.

Solution:

1. Check the motor, and the machinery coupled to motor, for overload.

2. Adjust the parameters used for the motor overload function ( 35.51…35.53) and 35.55…35.56.
7181
Brake resistor		Cause: Brake resistor broken or not connected.

Solution:

1. Check that a brake resistor has been
connected.heck the condition of the brake
resistor.
2. Check the dimensioning of the brake
resistor.
7183
BR excess
temperature		Cause: Brake resistor temperature has exceeded fault limit defined by parameter 43.11 Brake resistor fault limit.

Solution:

Stop drive.
Let resistor cool down.
Check resistor overload protection function settings (parameter group 43 Brake chopper).
Check fault limit setting, parameter 43.11 Brake resistor fault limit.
Check that braking cycle meets allowed limits.
7184
Brake resistor
wiring		Cause: Brake resistor short circuit or brake chopper control fault.

Solution:

1. Check brake chopper and brake resistor connection.
2. Ensure brake resistor is not damaged.
7191
BC short
circuit		Cause: Short circuit in brake chopper IGBT.

Solution:

1. Ensure brake resistor is connected and not damaged.
2. Check the electrical specifications of the brake resistor.
7192
BC IGBT
excess temp		Cause: Brake chopper IGBT temperature has exceeded internal fault limit.

Solution:

1. Let chopper cool down.Check for excessive ambient temperature.
2. Check for cooling fan failure.
3. Check for obstructions in the air flow.
4. Check the dimensioning and cooling of the cabinet.
5. Check that braking cycle meets allowed limits.
6. Check that drive supply AC voltage is not excessive.
71A3
Mechanical brake
opening failed		Cause: Mechanical brake control fault. Activated e.g. if brake acknowledgment is not as expected during brake opening.

Solution:

1. Check mechanical brake connection.
2. Check mechanical brake settings in parameter group 44 Mechanical brake control.
3. Check that acknowledgment signal matches actual status of brake.
4. This is a Programmable fault: check parameter 44.17 Brake fault function
7310
Overspeed 		Cause: Motor is turning faster than highest allowed speed due to incorrectly set minimum/maximum speed, insufficient braking torque or changes in load when using torque reference.

Solution:

1. Check minimum/maximum speed settings, parameters 30.11 Minimum speed and 30.12 Maximum speed.
2. Check adequacy of motor braking torque.
3. Check applicability of torque control.
4. Check need for brake chopper and resistor(s).
73B0
Emergency
ramp failed		Cause: Emergency stop did not finish within expected time.

Solution:

1. Check the settings of parameters 31.32 Emergency ramp supervision and 31.33 Emergency ramp supervision delay.
2. Check the predefined ramp times (23.11…23.15 for mode Off1, 23.23 for mode Off3).
73F0
Overfrequency 		Cause: Maximum allowed output frequency exceeded.

Solution:

1. Check minimum/maximum frequency settings, parameters 30.13 Minimum frequency and 30.14 Maximum frequency.
2. Check adequacy of motor braking torque.
3. Check applicability of torque control.
4. Check need for brake chopper and resistor(s).
7510
FBA A
communication		Cause: Cyclical communication between drive and fieldbus adapter module A or between PLC and fieldbus adapter module A is lost.

Solution:

1. Check status of fieldbus communication.
2. Check settings of parameter groups 50 Fieldbus adapter (FBA), 51 FBA A settings, 52 FBA A data in and 53 FBA A data out.
3. Check cable connections.
4. Check if communication master is able to communicate.
5. This is a Programmable fault: check parameter 50.02 FBA A comm loss function.
Note: If the module has been changed from FieldBus (for example FPBA) to some other option module (for example BMIO), the factory defaults need to be applied (see parameter 96.06).
8000
Unicos
system
error 		Cause: System fault.

Solution: Power cycle.
8001
ULC
underload
fault 		Cause: User load curve- Signal has been too long under the underload curve.

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

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

Solution:

1. Check signal level at the analog input.
2. Check the wiring connected to the input.
3. Check the minimum and maximum limits of the input in parameter group 12 Standard AI.
4. This is a Programmable fault: check parameter 12.03 AI supervision function.
80B0
Signal
supervision		Cause: Fault generated by the signal supervision 1 function.

Solution:

1. Check the source of the fault (parameter 32.07 Supervision 1 signal).
2. This is a Programmable fault: check parameter 32.06 Supervision 1 action
80B1
Signal
supervision		Cause: Fault generated by the signal supervision 2 function.

Solution:

1. Check the source of the fault (parameter 32.17 Supervision 2 signal).
2. This is a Programmable fault: check parameter 32.16 Supervision 2 action
80B2
Signal
supervision		Cause: Fault generated by the signal supervision 3 function.

Solution:

1. Check the source of the fault (parameter32.27 Supervision 3 signal).
2. This is a Programmable fault: check parameter 32.26 Supervision 3 action
80B3
Signal
supervision		Cause: Fault generated by the signal supervision 4 function.

Solution:

1. Check the source of the fault (parameter 32.37 Supervision 4 signal).
2. This is a Programmable fault: check parameter 32.36 Supervision 4 action
80B4
Signal
supervision		Cause: Fault generated by the signal supervision 5 function.

Solution:

1. Check the source of the fault (parameter 32.47 Supervision 5 signal).
2. This is a Programmable fault: check parameter 32.46 Supervision 5 action
80B5
Signal
supervision		Cause: Fault generated by the signal supervision 6 function.

Solution:

1. Check the source of the fault (parameter 32.57 Supervision 6 signal).
2. This is a Programmable fault: check parameter 32.56 Supervision 6 action
9081
External
fault 1		Cause: Fault in external device 1.

Solution:

Check the external device.
Check setting of parameter 31.01 External event 1 source.
This is a Programmable fault: check parameter 31.01 External event 1 source 31.02 External event 1 type.
9082
External
fault 2		Cause: Fault in external device 2.

Solution:

Check the external device.
Check setting of parameter 31.03 External event 2 source.
This is a Programmable fault: check parameter 31.03 External event 2 source 31.04 External event 2 type.
9083
External
fault 3		Cause: Fault in external device 3.

Solution:

Check the external device.
Check setting of parameter 31.05 External event 3 source.
This is a Programmable fault: check parameter 31.05 External event 3 source 31.06 External event 3 type.
9084
External
fault 4		Cause: Fault in external device 4.

Solution:

Check the external device.
Check setting of parameter 31.07 External event 4 source.
This is a Programmable fault: check parameter 31.07 External event 4 source 31.08 External event 4 type.
9085
External
fault 5		Cause: Fault in external device 5.

Solution:

Check the external device.
Check setting of parameter 31.09 External event 5 source.
This is a Programmable fault: check parameter 31.09 External event 5 source 31.10 External event 5 type.
A2A1
Current
calibration 		Cause: Current offset and gain measurement calibration will occur at next start.

Solution: Informative warning. (See parameter 99.13 ID run requested).
FA81
Safe torque
off 1		Cause: Safe torque off function is active, ie. STO circuit 1 is broken.

Solution: Check safety circuit connections.
FA82
Safe torque
off 2		Cause: Safe torque off function is active, ie. STO circuit 2 is broken.

Solution: Check safety circuit connections.
FF61
ID run		Cause: Motor ID run was not completed successfully.

Solution:

1. Check the nominal motor values in parameter group 99 Motor data.
2. Check that no external control system is connected to the drive.
3. Cycle the power to the drive (and its control unit, if powered separately).
4. Check that no operation limits prevent the completion of the ID run. Restore parameters to default settings and try again.
5. Check that the motor shaft is not locked.
FF63
STO
diagnostics
failure		Cause: SW internal malfunction.

Solution: Reboot the control unit (using parameter 96.08 Control board boot or by cycling power.
FF81
FB A force
trip 		Cause: A fault trip command has been received through fieldbus adapter A.

Solution:

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.

Solution: Check the fault information provided by the PLC.