Code F01600: Passivated STO with drive fault

Reaction: OFF 2 (OFF 3) Acknowledge: Quit fault eg. via DI2 Cause: A passivated safe torque off (passivated STO) has been initiated by hardware due to a drive fault: - r0949 = 33: passivated STO acknowledge after a drive fault requires the OFF first and then an acknowledge (ACK) to remove the safety fault! If however ACK is given first and then the OFF command, the alarm handler clears the fault but the passivated STO is still active. - r0949 = 100: The signals for the STO signal are not consistent on P1. - r0949 = 101: Maximum speed exceeded on P1 during activation of the SS1. The estimated speed deviates from the SBR monitoring ramp. When the drive is in VECTOR mode (with p1300 > 19): - r0949 = 104: Communication timeout of processor P2 during forced dynamisation. The handshaking via hard- ware lines has failed. - r0949 = 106: Error in the mechanical brake or in the brake feedback path of P1. - r0949 = 107: Error in the gate driver or feedback path of P1. Can happen when either the hardware measure- ment circuit on the PM is faulty or when P1 and P2 are not synchronised. - r0949 = 108: Signal debounce error on P1. The safety signals are not consistent for a longer time than parame- terised in p9650/p9850. - r0949 = 109: Hardware detection fault on P1. The hardware type (safety or non-safety module) has not been recognised correctly. - r0949 = 200: The STO signals are not consistent on P2. Avoid fast periodic activation and deactivation of the STO. - r0949 = 201: Maximum frequency exceeded on activation of SS1 on P2. - r0949 = 202: Maximum frequency exceeded on activation of SLS in P2. - r0949 = 204: Communication timeout of processor P2 during forced dynamisation. The handshaking via hard- ware lines has failed. - r0949 = 206: Error in the mechanical brake or in the brake feedback path of P2 - r0949 = 207: Error in gate driver or feedback path on P2. - r0949 = 208: Signal debounce error on P2. The safety signals are not consistent for a longer time than parame- terised in p9650/p9850. - r0949 = 209: Hardware type could not be detected correctly on P2. Remedy: - r0949 = 100 or 200 Increase the ramping times p1120/p1121 or the safety tolerance p9691/p9891, check the motor parameters (p0394 - p0311) or run the motor identification (p1910) again. Decrease the rate of switching the safety signals or lower the cycle time of the PLC. - r0949 = 101 or 201 Increase the ramping times p1120/p1121 or the safety tolerance p9691/p9891, check the motor parameters (p0394 - p0311) or run the motor identification (p1910) again. - r0949 = 102 or 202 Increase the ramping times (p1120, p1121) so that deviation between reference and actual frequency is mini- mized. Increase the safety tolerance p9691/p9891 or run the motor identification (p1910) again for better tuning of the observer and controllers. - r0949 = 104 or 204 Acknowledge the fault once more Power cycle the CU - r0949 = 106 or 206 Check connection with safe brake module and mechanical brake Check the 24 V power supply for safe brake module - r0949 = 107 or 207 Check connection between CU and power module Power cycle the CU - r0949 =, 108, or 208 Decrease the rate of switching the safe digital inputs or increase debounce delay time p9650/p9850. - r0949 = 109 or 209 Power cycle the CU Change CU