ABB FSO-21, Руководство пользователя

Страница: 500 / 540

500 Fault tracing
1)
This is a user-selectable event for a function request. See parameter FSOGEN.61 STO indication ext
request and section User-selectable events for function requests on page 501 .
2)
This is a user-selectable event for a limit hit or a special event. See parameter FSOGEN.62 STO indication
safety limit and section User-selectable events for limit hits and special events on page 501 .
3)
For more information, see the tips in the Drive Composer PC tool.
4)
This warning indicates a fault actually. However, the FSO module generates a warning indication first to
BAB2 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)
BAB3 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)
BAB4 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)
BAB5 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 transient mute time values
are defined properly (
FSOGEN.31 or
SLSx.57 if enabled, and
FSOGEN.33 ).
2) 6)
BAB6 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