Fault tracing
307
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.
Check for excessive ambient temperature.
Check for cooling fan failure.
Check for obstructions in the air flow.
Check the dimensioning and cooling of the
cabinet.
2015
BC MOD OVERTEMP
(0x7183)
Input bridge or braking chopper
temperature has exceeded
internal alarm limit.
Let drive cool down.
Check for excessive ambient temperature.
Check for cooling fan failure.
Check for obstructions in the air flow.
Check the dimensioning and cooling of the
cabinet.
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:
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 fieldbus parameter settings. See
parameter group
on page
.
Check cable connections.
Check if communication master can
communicate.
2018
LOCAL CTRL LOSS
(0x5300)
Programmable fault:
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:
Analogue input AI1 or AI2 signal
has reached limit defined by
parameter
Check analogue input AI1/2 source and
connections.
Check analogue input AI1/2 minimum and
maximum limit settings, parameters
and
and
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 fieldbus parameter settings. See
parameter group
on page
.
Code
Alarm
(fieldbus code)
Cause
What to do
Summary of Contents for ACSM1 Series
Page 1: ...ABB motion control drives Firmware manual ACSM1 motion control program ...
Page 4: ......
Page 34: ...Drive programming using PC tools 34 ...
Page 86: ...Drive control and features 86 ...
Page 265: ...Parameters and firmware blocks 265 1 100 us 100 µs 2 1 ms 1 ms 3 50 ms 50 ms ...
Page 302: ...Parameter data 302 ...
Page 422: ...Application program template 422 ...
Page 430: ...Appendix A Fieldbus control 430 ...
Page 500: ...Appendix D Application examples 500 ...
Page 508: ...Appendix E Control chain and drive logic diagrams 508 ...
Page 510: ...3AFE68848270 REV H EN 2015 06 26 Contact us www abb com drives www abb com drivespartners ...