ABB FSO-21, User Manual

Page: 476 / 540

476 Verification and validation
• SLSx.03 SLS activation monitoring method = Time
• drive parameter 23.13 deceleration time 1 (or 23.15 deceleration time 2 )
• SLSx.04 SLS time delay .
Indication:
•
SLSx.15 SLS1 output A
• SLSx.16 SLS1 output B (only available for SLS1).
Test the SLS function as it is used in the application. Pay attention to the testing of the
relevant fault situations for the application, for example, tripping fault in the drive,
safety encoder fault, etc.
3. Start the drive and accelerate it to a suitable speed. Activate the SLS function with
an FSO module input, or via the safety bus.
If you activate the function at a speed higher than the SLS limit (
200.23 or
200.22 ), make sure that the deceleration ramp operates as required and no
tripping fault occurs during the deceleration.
4. Make sure that SLS function limits the motor speed to the required limit. Give a
speed reference higher than the SLS limit. Make sure that the drive does not
follow speed references that are higher than the SLS limit.
5. Make sure that the SLS indication output ( SLSx.15 or SLSx.16 ) indicates safe
speed when motor speed is within SLS limits.
6. Deactivate the SLS function. Make sure that the SLS indication ( SLSx.15 or
SLSx.16 ) goes off, and the drive runs the motor according to the given user
reference (outside the SLS speed limits).
Note: If the SLS function can be activated at a higher motor speed than the SLS limit
( 200.23 or 200.22 ), validate the correct operation as follows:
7. Activate SLS function at a motor speed above the SLS limit ( 200.23 or 200.22 ).
8. Activate the coast stop of the drive.
9. Make sure that the FSO module reacts according to your application
requirements. For example, it trips the drive with the STO.
10. Make sure that the following events occur only after the motor is in safe state:
• the SLS indication ( SLSx.15 ) goes on, if it is configured.
• Acknowledgement of the stopping function (SSE or STO) is possible in case a
stopping function was triggered earlier. See step
9 .