Siemens SINAMICS G120D - F01625 SI P1: Sign-of-life error in safety data; F01649 SI P1: Internal software error; F01650 SI P1: Acceptance test required

List of faults and alarms
Faults and alarms
3-793
© Siemens AG 2012 - 2013 All Rights Reserved
SINAMICS G120D List Manual (LH14), 01/2013
Remedy: Not necessary.
Note:
STO: Safe Torque Off
F01625 SI P1: Sign-of-life error in safety data
Reaction: OFF2
Acknowledge: IMMEDIATELY (POWER ON)
Cause: The drive-integrated "Safety Integrated" function on processor 1 has detected an error in the sign-of-life of the safety
data and initiated a STOP A.
- there is a communication error between processor 1 and processor 2 or communication has failed.
- a time slice overflow of the safety software has occurred.
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
Remedy: - select Safe Torque Off and de-select again.
- carry out a POWER ON (power off/on).
- check whether additional faults are present and if required, perform diagnostics.
- check the electrical cabinet design and cable routing for EMC compliance
F01649 SI P1: Internal software error
Reaction: OFF2
Acknowledge: IMMEDIATELY (POWER ON)
Cause: An internal error in the Safety Integrated software on processor 1 has occurred.
Note:
This fault results in a STOP A that cannot be acknowledged.
Fault value (r0949, interpret hexadecimal):
Only for internal Siemens troubleshooting.
Remedy: - carry out a POWER ON (power off/on).
- re-commission the "Safety Integrated" function and carry out a POWER ON.
- contact the Hotline.
- replace Control Unit.
F01650 SI P1: Acceptance test required
Reaction: OFF2
Acknowledge: IMMEDIATELY (POWER ON)
Cause: The drive-integrated "Safety Integrated" function on processor 1 requires an acceptance test.
Note:
This fault results in a STOP A that can be acknowledged.
Fault value (r0949, interpret decimal):
130: Safety parameters for processor 2 not available.
Note:
This fault value is always output when Safety Integrated is commissioned for the first time.
1000: Reference and actual checksum on processor 1 are not identical (booting).
- at least one checksum-checked piece of data is defective.
- Safety parameters set offline and loaded into the Control Unit.
2000: Reference and actual checksum on processor 1 are not identical (commissioning mode).
- reference checksum incorrectly entered on processor 1 (p9799 not equal to r9798).
- when de-activating the safety functions, p9501 was not deleted.
2001: Reference and actual checksum on processor 2 are not identical (commissioning mode).
- reference checksum incorrectly entered on processor 2 (p9899 not equal to r9898).
- when de-activating the safety functions, p9501 was not deleted.
2002: Enable of safety-related functions between the processor 1 and processor 2 differ (p9601 not equal to p9801).
2003: Acceptance test is required as a safety parameter has been changed.
2004: An acceptance test is required because a project with enabled safety-functions has been downloaded.
2005: The Safety logbook has identified that a functional safety checksum has changed. An acceptance test is
required.
2020: Error when saving the safety parameters for the processor 2.
9999: Subsequent response of another safety-related fault that occurred when booting that requires an acceptance
test.
Remedy: For fault value = 130:
- carry out safety commissioning routine.