ABB FSO-21 - Page 499

Fault tracing 499
BAA7 FSO SLS4 hit FSO module detected an
SLS4 speed trip limit
violation.
Investigate the reason for trip from
the application point of view. If
application is OK, then make sure
that SLS is configured properly.
Make sure that SLS trip limits are
defined properly.
Check that transient mute time values
are defined properly (FSOGEN.31 or
SLSx.47 if enabled, and
FSOGEN.33).
2) 6)
BAA8 FSO SMS hit FSO module detected an
SMS speed trip limit
violation.
Investigate the reason for trip from
the application point of view. If
application is OK, then make sure
that SMS is configured properly.
Make sure that SMS trip limits are
defined properly.
Check that transient mute time values
are defined properly (FSOGEN.31 or
SMS.17 if enabled).
2) 6)
BAA9 FSO SAR0 hit FSO module detected an
SAR0 limit violation.
Make sure that the drive can
decelerate the load using the ramp
time (200.102 SAR0 ramp time to
zero).
2)
BAAA FSO SAR1 hit FSO module detected an
SAR1 limit violation.
Make sure that the drive can
decelerate the load using the ramp
time (200.112 SAR1 ramp time to
zero).
2)
BAB0 FSO SDI positive
hit
SDI positive exceeded the
tolerance limit to the
forbidden direction.
Make sure that SDI tolerance values
are defined properly.
Check limits of the drive. For
example, see the usage of DC hold
from the drive firmware manual.
2)
BAB1 FSO SDI negative
hit
SDI negative exceeded
the tolerance limit to the
forbidden direction.
Make sure that SDI tolerance values
are defined properly.
Check limits of the drive. For
example, see the usage of DC hold
from the drive firmware manual.
2)
Code
(hex)
Name Cause What to do