ABB FSO-21 - Page 496

496 Fault tracing
AAB1 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)
AAB2 FSO ramp time hit FSO module detected a
violation of a time
monitored ramp.
Make sure that the drive can
decelerate the load within the time
defined for ramp time monitoring.
• Check the drive ramp time settings.
• Check that the drive can in fact
accomplish the deceleration along
the ramp defined.
Make sure that the limit for ramp time
monitoring of the FSO module
exceeds the actual drive ramp time.
The parameter varies depending on
the safety function. For the SS1
function it is SS1.14 SS1-t delay for
STO.
2)
AAB3 FSO zero spd hit Drive speed rushed
during zero speed delay
(SSE.16 SSE ramp zero
speed delay for STO or
SS1.15 SS1-r ramp zero
speed delay for STO).
Check the drive.
2)
AAB4 FSO speed sync
fail
FSO module detected a
difference between the
two monitored motor
speed values (200.01
FSO speed ch1 and
200.02 FSO speed ch2).
Restart the drive and FSO module.
2)
AAB5 FSO varSLS hit FSO module detected a
Variable SLS speed trip
limit violation.
Investigate the reason for trip from
the application point of view. If
application is OK, then make sure
that Variable SLS is configured
properly.
Make sure that Variable SLS trip
limits are defined properly.
Check that mute time values are
defined properly (FSOGEN.31 or
SLSx.57 if enabled, and
FSOGEN.33).
2) 6)
AAB6 FSO safebus
passivation
FSO module was
passivated due to
communication problems.
Check the fieldbus connection and
fieldbus controller for passivation
cause.
5)
Code
(hex)
Name Cause What to do