Safe torque off (STO) was activated by hardware due to a drive fault. The manual's first action is: “OFF 2 (OFF 3). Quit fault eg. via DI2 • r0948 = 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. • r0948 = 100: The signals for the STO signal are not consistent on P1. • r0948 = 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); • r0948 = 104: Communication timeout of processor P2 during forced dynamisation. The handshaking via hardware lines has failed. • r0948 = 106: Error in the mechanical brake or in the brake feedback path of P1. • r0948 = 107: Error in the gate driver or feedback path of P1. Can happen when either the hardware measurement circuit on the PM is faulty or when P1 and P2 are not synchronised. • r0948 = 108: Signal debounce error on P1. The safety signals are not consistent for a longer time than parameterised in p9650/p9850. • r0948 = 109: Hardware detection fault on P1. The hardware type (safety or non-safety module) has not been recognised correctly. • r0948 = 200: The STO signals are not consistent on P2. Avoid fast periodic activation and deactivation of the STO. • r0948 = 201: Maximum frequency exceeded on activation of SS1 on P2. • r0948 = 202: Maximum frequency exceeded on activation of SLs in P2. • r0948 = 204: Communication timeout of processor P2 during forced dynamisation. The handshaking via hardware lines has failed. • r0948 = 206: Error in the mechanical brake or in the brake feedback path of P2 • r0948 = 207: Error in gate driver or feedback path on P2. • r0948 = 208: Signal debounce error on P2. The safety signals are not consistent for a longer time than parameterised in p9650/p9850. • r0948 = 209: Hardware type could not be detected correctly on P2.”
- Model
- Siemens CU240S
- Display shows
- Passivated STO with drive fault (F01600)
- Type
- Fault code
- Source
- Manual p. 397
What F01600 means
Passivated STO with drive fault p. 397
Common causes
- A passivated safe torque off (passivated STO) has been initiated by hardware due to a drive fault: p. 397
What to do
- OFF 2 (OFF 3). Quit fault eg. via DI2 • r0948 = 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. • r0948 = 100: The signals for the STO signal are not consistent on P1. • r0948 = 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); • r0948 = 104: Communication timeout of processor P2 during forced dynamisation. The handshaking via hardware lines has failed. • r0948 = 106: Error in the mechanical brake or in the brake feedback path of P1. • r0948 = 107: Error in the gate driver or feedback path of P1. Can happen when either the hardware measurement circuit on the PM is faulty or when P1 and P2 are not synchronised. • r0948 = 108: Signal debounce error on P1. The safety signals are not consistent for a longer time than parameterised in p9650/p9850. • r0948 = 109: Hardware detection fault on P1. The hardware type (safety or non-safety module) has not been recognised correctly. • r0948 = 200: The STO signals are not consistent on P2. Avoid fast periodic activation and deactivation of the STO. • r0948 = 201: Maximum frequency exceeded on activation of SS1 on P2. • r0948 = 202: Maximum frequency exceeded on activation of SLs in P2. • r0948 = 204: Communication timeout of processor P2 during forced dynamisation. The handshaking via hardware lines has failed. • r0948 = 206: Error in the mechanical brake or in the brake feedback path of P2 • r0948 = 207: Error in gate driver or feedback path on P2. • r0948 = 208: Signal debounce error on P2. The safety signals are not consistent for a longer time than parameterised in p9650/p9850. • r0948 = 209: Hardware type could not be detected correctly on P2. p. 397
If F01600 is still not resolved
The manual gives no further instruction for this code. Open the code table in the PDF or contact Siemens service.
This page summarises what the manufacturer’s manual says about F01600; each statement links to the page it comes from, and quoted lines are copied word for word. It is not a substitute for the manual or for a qualified installer. ManualLib is not affiliated with Siemens. Found a mistake? Report an error.