Verification and validation 463
b) If you have configured FSE diagnostic failure reaction (S_ENCGEN.11) to be
No STO:
1. Cause an encoder failure by disconnecting the one encoder signal channel
wire from the FSE module.
2. Activate any safety function except POUS or SSM.
3. Make sure the FSO module goes into the Fail-safe state, FSO general fault
(7A8B) and FSO safety encoder fault (A7D8) are indicated in the event log,
the STO function of the drive is activated, and the drive trips for the encoder
failure.
Repeat steps 1…3 after step 13 with no safety functions active to make sure that
the system does not trip to encoder fault.
14. Make sure that there are no unwanted faults in the drive event log.
15. Reconnect the encoder signal channel.
16. Re-boot the FSO module to exit the Fail-safe mode.
17. Restart the drive and make sure that the motor runs normally.
If you have configured FSE diagnostic failure reaction (S_ENCGEN.11) to be Est
switch not active load, follow the steps below to validate the safety encoder interface:
12. Make sure that you can run and stop the motor freely.
13. Start the drive to the motor speed typical for the application.
14. Cause an encoder failure by disconnecting the one encoder signal channel wire
from the FSE module.
15. Make sure that the correct warnings are generated: Encoder warning (A7D8),
FSO general warning (A7D0), FSE Ch1 diag event (B793) and FSE Ch12 diag
event (B794).
16. Activate a safety function (any other safety function except SDI, POUS or SSM).
17. Make sure that the system does not trip to encoder fault.
18. Reconnect the encoder signal channel.
All safety functions that are in use, must be validated both with the safe speed
estimation and with the safety encoder when S_ENCGEN.11 FSE diagnostic failure
reaction = Est switch not active load. Validation test about the transition from the
encoder to the safe speed estimate must be done by disconnecting the encoder
signal.
To Next Page
Loading...
