ABB FSO-21 - Page 494

494 Fault tracing
AA96 FSO out of SDI SDI positive or 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)
AA97 FSO POUS
request
FSO module received an
external POUS request
and activated POUS.
-
AA99 FSO passivated FSO module was
passivated due to safety
fieldbus problems.
Check the fieldbus connection and
fieldbus controller for passivation
cause.
5)
AAA1 FSO STO request FSO module received an
external STO request.
-
1)
AAA2 FSO SSE request FSO module received an
external SSE request.
-
1)
AAA3 FSO SS1 request FSO module received an
external SS1 request.
-
1)
AAA4 FSO SLS1 hit FSO module detected an
SLS1 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 mute time values are
defined properly (FSOGEN.31 or
SLSx.17 if enabled, and
FSOGEN.33).
2) 6)
AAA5 FSO SLS2 hit FSO module detected an
SLS2 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 mute time values are
defined properly (FSOGEN.31 or
SLSx.27 if enabled, and
FSOGEN.33).
2) 6)
Code
(hex)
Name Cause What to do