474 Verification and validation
3. If you made any changes, download and validate the configuration with the Drive
composer pro PC tool.
Note: SAR1 is common with the SS1, SLS and SDI functions. Any changes to the
SAR1 values will have impact on these functions.
4. Make sure that you can run and stop the motor freely. Start the drive and
accelerate to the maximum speed of the application.
5. Activate the SS1 function. For example, press an emergency stop button which is
wired to FSO module input for the SS1 function.
6. Remove the SS1 function user request.
7. a) If manual acknowledgement (or safebus acknowledgement) is in use:
Try to
acknowledge the function and verify, that it is not possible before the motor is in
safe state (the motor speed is not dangerously high for the application):
• With safe speed estimation: Safety zero speed limit for FSOGEN.51 Zero
speed without encoder
• With safety encoder: FSOGEN.52 Zero speed with encoder
OR
b) If automatic acknowledgement is in use:
Verify that the function is not
acknowledged before the motor speed is low enough. See the conditions above.
8. Make sure that the motor speed decelerates as it is designed, and the FSO
module does not trip to the monitoring limit (ramp or time).
9. After the motor is in safe state and the function is acknlowledged, start the drive
again and accelerate to the maximum speed of the application.
10. Activate the SS1 function. For example, by pressing the emergency stop button
which is wired to FSO module input for the SS1 function.
11. Remove the SS1 function user request.
12. Activate the coast stop.
You can, for example, cause an external fault trip in the drive. For more
information, see the drive firmware manual (Group 31 Fault functions).
13. Make sure that the FSO module trips the drive and activates the STO function
according to the application requirements.
14. Make sure that the acknowledgement of the STO function is not possible before
the motor is in safe state.
To Next Page
Loading...
