ABB DCS550 Series, Manual

Page: 296 / 316

296
Fault tracing
3ADW000379R0501 DCS550 Manual e e
7-segment
display
Text on DCS
Control Panel
and DWL
Definition / Action Alarm-
word
Alarm is
active when
A
lar
m
level
A107 107 M1OverLoad Motor calculated overload:
Check:
M1AlarmLimLoad (31.03)
9.06,
bit 6 always 2
A108 108
MotCurReduce
Motor current reduced:
Is shown, when the I
2
T-function is active and the motor
current is reduced. Check:
−
M1LoadCurMax (31.10), M1OvrLoadTime (31.11) and
M1RecoveryTime (31.12)
9.06,
bit 7 always 4
A111 111
MainsLowVolt
Mains low (under-) voltage (AC):
α
is set to 150°; single firing pulses. Check:
−
PwrLossTrip (30.21), UNetMin1 (30.22), UNetMin2
(30.23),
−
If all 3 phases are present
−
if the mains voltage is within the set tolerance
−
if the main contactor closes and opens
−
if the mains voltage scaling is correct [NomMainsVolt
(99.10)]
−
connector X12 and X13 on SDCS-CON-F
−
connector X12 and X13 on SDCS-PIN-F
−
In case the On command [UsedMCW (7.04) bit 0] is
given and the measured mains voltage is too low for
more than 500 ms A111 MainsLowVolt [AlarmWord1
(9.06) bit 10] is set. If the problem persist for more than
10 s F512 MainsLowVolt [FaultWord1 (9.01) bit 11] is
generated.
9.06,
bit 10 RdyRun = 1 3
A113 113 COM8Com SDCS-COM-8 com. loss:
Check:
−
Change SDCS-COM-8 and / or SDCS-CON-F
9.06,
bit 12 always 4
A114 114 ArmCurDev Armature Current Deviation:
Is shown, if the current reference [CurRefUsed (3.12)]
differs from current actual [MotCur (1.06)] for longer than 5
sec by more than 20% of nominal motor current.
In other words if the current controller cannot match the
given reference, the alarm signal is created. Normally the
reason is a too small incoming voltage compared to the
motor EMF. Check:
−
DC fuses blown
−
ratio between mains voltage and armature voltage
(either the mains voltage is too low or the motor’s
armature voltage is too high)
−
ArmAlphaMin (20.15) is set too high
9.06,
bit 13 RdyRef = 1 4
A115 115 TachoRange Tacho range:
If A115 TachoRange comes up for longer than 10
seconds, there is an overflow of the AITacho input. Check:
−
for the right connections (X1:1 to X1:4) on the SDCS-
CON-F
If A115 TachoRange comes up for 10 seconds and
vanishes again M1OvrSpeed (30.16) has been changed.
In this case a new tacho fine tuning has to be done
[ServiceMode (99.06) = TachFineTune].
9.06,
bit 14 always 4
A117 117 Armature current ripple: 9.07, RdyRef = 1 4