Siemens SINAMICS G120 Drive Fault Codes List (2026) – Access the complete 2026 reference guide for Siemens SINAMICS G120 fault codes. Learn to diagnose Fxxxxx faults and Axxxxx alarms via IOP-2, Startdrive (TIA Portal), and Smart Access Modules.
The Siemens SINAMICS G120 is a modular inverter system consisting of a Control Unit (CU) and a Power Module (PM). It is the backbone of automation in automotive, logistics, and manufacturing. When a malfunction occurs, the system generates a 5-digit code prefixed with “F” (Fault) or “A” (Alarm), which can be read via the operator panel or TIA Portal.
This guide provides the most updated reference for 2026 to help you interpret these codes and utilize Siemens’ advanced diagnostic tools.
Siemens G120 Fault Codes Reference Table
Use the search bar below or browse the table to identify your specific error code.
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| F01000 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01001 Floating Point exception | Cause: An exception occurred during an operation with the Floating Point data type. The error may be caused by the basic system or an OA application (e.g., FBLOCKS, DCC). Note: Refer to r9999 for further information. r9999[2]: Cause of the Floating Point exception.
Remedy:
|
| F01002 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01003 Acknowledgement delay when accessing the memory | Cause: A memory area was accessed that does not return a ‘READY’. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| N01004 (F, A) Internal software error | Cause: An internal software error has occurred. Fault value (r0949, hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01005 File upload/download error | Cause: The upload or download of EEPROM data was unsuccessful. Fault value (r0949, interpret hexadecimal): yyxxxx hex: yy = component number, xxxx = fault cause
Remedy: Save a suitable firmware file or EEPROM file for upload or download in folder ‘/ee_sac/’ on the memory card. |
| A01009 (N) CU: Control module overtemperature | Cause: The temperature (r0037[0]) of the control module (Control Unit) has exceeded the specified limit value. Remedy:
|
| F01010 Drive type unknown | Cause: An unknown drive type was found. Remedy:
|
| F01015 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01016 (F) Firmware changed | Cause: At least one firmware file in the directory was illegally changed on the non-volatile memory with respect to the version when shipped from the factory. Alarm value (r2124, interpret decimal):
Remedy: For the non-volatile memory for the firmware, restore the delivery condition. Note: The file involved can be read out using parameter r9925. The status of the firmware check is displayed using r9926. See also: r9925, r9926. |
| A01017 Component lists changed | Cause: On the memory card, one file in the directory /SIEMENS/SINAMICS/DATA or /ADDON/SINAMICS/DATA has been illegally changed with respect to that supplied from the factory. No changes are permitted in this directory. Alarm value (r2124, interpret decimal): zyx dec: x = Problem, y = Directory, z = File name
Remedy: For the file on the memory card involved, restore the status originally supplied from the factory. |
| F01018 Booting has been interrupted several times | Cause: Module booting was interrupted several times. As a consequence, the module boots with the factory setting. Possible reasons:
Remedy:
|
| A01019 Writing to the removable data medium unsuccessful | Cause: The write access to the removable data medium was unsuccessful. Remedy: Remove and check the removable data medium. Then run the data backup again. |
| A01020 Writing to RAM disk unsuccessful | Cause: A write access to the internal RAM disk was unsuccessful. Remedy: Adapt the file size for the system logbook to the internal RAM disk (p9930). See also: p9930 (System logbook activation) |
| A01021 Removable data medium as USB data storage medium from the PC used | Cause: The removable data medium is used as USB data storage medium from a PC. As a consequence, the drive cannot access the removable data medium. Fault value (r0949, interpret decimal):
Remedy: Deactivate the USB connection to the PC and back up the configuration data. Note: The alarm is automatically canceled when disconnecting the USB connection or when removing the removable data medium. |
| F01023 Software timeout (internal) | Cause: An internal software timeout has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01028 Configuration error | Cause: The parameterization that was downloaded was generated with a different module type (Order No., MLFB). Remedy: Save parameters in a non-volatile fashion (p0971 = 1). |
| F01030 Sign-of-life failure for master control | Cause: For active PC master control, no sign-of-life was received within the monitoring time. The master control was returned to the active BICO interconnection. Remedy: Set the monitoring time higher at the PC or, if required, completely disable the monitoring function. For the commissioning software, the monitoring time is set as follows: Notice: The monitoring time should be set as short as possible. A long monitoring time means a late response when the communication fails! |
| F01033 Units changeover: Reference parameter value invalid | Cause: When changing over the units to the referred representation type, it is not permissible for any of the required reference parameters to be equal to 0.0. Fault value (r0949, parameter): Reference parameter whose value is 0.0. See also: p0505, p0595. Remedy: Set the value of the reference parameter to a number different than 0.0. See also: p0304, p0305, p0310, p0596, p2000, p2001, p2002, p2003, r2004. |
| F01034 Units changeover: Calculation parameter values after reference value change unsuccessful | Cause: The change of a reference parameter meant that for an involved parameter the selected value was not able to be re-calculated in the per unit representation. The change was rejected and the original parameter value restored. Fault value (r0949, parameter): Parameter whose value was not able to be re-calculated. See also: p0304, p0305, p0310, p0596, p2000, p2001, p2002, p2003, r2004. Remedy: Select the value of the reference parameter such that the parameter involved can be calculated in the per unit representation. See also: p0304, p0305, p0310, p0596, p2000, p2001, p2002, p2003, r2004. |
| A01035 (F) ACX: Parameter back-up file corrupted | Cause: When the Control Unit is booted, no complete data set was found from the parameter back-up files. The last time that the parameterization was saved, it was not completely carried out. It is possible that the backup was interrupted by switching off or withdrawing the memory card. Alarm value (r2124, interpret hexadecimal):
Remedy:
|
| F01036 (A) ACX: Parameter back-up file missing | Cause: When downloading the device parameterization, a parameter back-up file PSxxxyyy.ACX associated with a drive object cannot be found. Fault value (r0949, interpret hexadecimal):
Remedy: If you have saved the project data using the commissioning software, carry out a new download for your project. Save using the function ‘Copy RAM to ROM’ or with P0971 = 1. This means that the parameter files are again completely written into the non-volatile memory. Note: If the project data have not been backed up, then a new first commissioning is required. |
| F01038 (A) ACX: Loading the parameter back-up file unsuccessful | Cause: An error has occurred when downloading PSxxxyyy.ACX or PTxxxyyy.ACX files from the non-volatile memory. Fault value (r0949, interpret hexadecimal):
Remedy:
|
| F01039 (A) ACX: Writing to the parameter back-up file was unsuccessful | Cause: Writing to at least one parameter back-up file PSxxxyyy.*** in the non-volatile memory was unsuccessful.
Remedy:
|
| F01040 Save parameter settings and carry out a POWER ON | Cause: A parameter has been changed that requires the parameters to be backed up and the Control Unit to be switched OFF and ON again. Remedy:
|
| F01042 Parameter error during project download | Cause: An error was detected when downloading a project using the commissioning software (e.g. incorrect parameter value). For the specified parameter, it was detected that dynamic limits were exceeded. Fault value (r0949, interpret hexadecimal): ccbbaaaa hex, aaaa = Parameter, bb = Index, cc = fault cause. Remedy:
|
| F01043 Fatal error at project download | Cause: A fatal error was detected when downloading a project using the commissioning software. Fault value (r0949, interpret decimal):
Remedy:
|
| F01044 CU: Descriptive data error | Cause: An error was detected when loading the descriptive data saved in the non-volatile memory. Remedy: Replace the memory card or Control Unit. |
| A01045 Configuring data invalid | Cause: An error was detected when evaluating the parameter files saved in the non-volatile memory. Because of this, under certain circumstances, several of the saved parameter values were not able to be accepted. Also see r9406 up to r9408. Remedy:
|
| A01049 It is not possible to write to file | Cause: It is not possible to write into a write-protected file (PSxxxxxx.acx). The write request was interrupted. Alarm value (r2124, interpret decimal): Drive object number. Remedy: Check whether the ‘write protected’ attribute has been set for the files in the non-volatile memory under …/USER/SINAMICS/DATA/… When required, remove write protection and save again (e.g. set p0971 to 1). |
| F01054 CU: System limit exceeded | Cause: At least one system overload has been identified. Fault value (r0949, interpret decimal):
Remedy: Re fault value = 1, 5: reduce the computing time load of the drive unit (r9976[1] and r9976[5]) to under 100 %. |
| A01064 (F) CU: Internal error (CRC) | Cause: CRC error in the Control Unit program memory. Remedy:
|
| A01066 Buffer memory: 70% fill level reached or exceeded | Cause: The non-volatile buffer memory for parameter changes is filled to at least 70%. This can also occur if the buffer memory is active (p0014 = 1) and parameters are continually changed via a fieldbus system. Remedy: If required, de-activate and clear the buffer memory (p0014 = 0 or 2). In the following cases, the entries in the buffer memory are transferred into the ROM and then the buffer memory is cleared:
|
| A01067 Buffer memory: 100% fill level reached | Cause: The non-volatile buffer memory for parameter changes is filled to 100%. All additional parameter changes will no longer be taken into account in the non-volatile buffer memory. However, parameter changes can still be made in the volatile memory (RAM). Remedy: If required, de-activate and clear the buffer memory (p0014 = 0 or 2). In the following cases, the entries in the buffer memory are transferred into the ROM and then the buffer memory is cleared:
|
| F01068 CU: Data memory memory overflow | Cause: The utilization for a data memory area is too large. Fault value (r0949, interpret binary):
Remedy:
|
| A01069 Parameter backup and device incompatible | Cause: The parameter backup on the memory card and the drive unit do not match. The module boots with the factory settings. Example: Devices A and B are not compatible and a memory card with the parameter backup for device A is inserted in device B. Remedy:
|
| F01072 Memory card restored from the backup copy | Cause: The Control Unit was switched-off while writing to the memory card. This is why the visible partition became defective. After switching on, the data from the non-visible partition (backup copy) were written to the visible partition. Remedy: Check that the firmware and parameterization is up-to-date. |
| A01073 POWER ON required for backup copy on memory card | Cause: The parameter assignment on the visible partition of the memory card has changed. In order that the backup copy on the memory card is updated on the non-visible partition, it is necessary to carry out a POWER ON or hardware reset (p0972) of the Control Unit. Note: It is possible that a new POWER ON is requested via this alarm (e.g. after saving with p0971 = 1). Remedy:
|
| F01105 (A) CU: Insufficient memory | Cause: Too many data sets are configured on this Control Unit. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: reduce the number of data sets. |
| F01107 Save to memory card unsuccessful | Cause: A data save to the memory card was not able to be successfully carried out.
Remedy:
|
| F01112 CU: Power unit not permissible | Cause: The connected power unit cannot be used together with this Control Unit. Fault value (r0949, interpret decimal): 1: Power unit is not supported (e.g. PM340). Remedy: Replace the power unit that is not permissible by a component that is permissible. |
| F01120 (A) Terminal initialization has failed | Cause: An internal software error occurred while the terminal functions were being initialized. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01122 (A) Frequency at the measuring probe input too high | Cause: The frequency of the pulses at the measuring probe input is too high. Fault value (r0949, interpret decimal):
Remedy: Reduce the frequency of the pulses at the measuring probe input. |
| F01205 CU: Time slice overflow | Cause: Insufficient computation time. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: Contact the Hotline. |
| F01250 CU: CU-EEPROM incorrect read-only data | Cause: Error when reading the read-only data of the EEPROM in the Control Unit. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01251 CU: CU-EEPROM incorrect read-write data | Cause: Error when reading the read-write data of the EEPROM in the Control Unit. Alarm value (r2124, interpret decimal): Only for internal Siemens troubleshooting. Remedy: For alarm value r2124 < 256, the following applies:
|
| F01257 CU: Firmware version out of date | Cause: The Control Unit firmware is too old. Fault value (r0949, interpret hexadecimal): bbbbbbaa hex: aa = unsupported component
Remedy: Re fault value = 1, 2, 4:
|
| F01340 Topology: Too many components on one line | Cause: For the selected communications clock cycle, too many DRIVE-CLiQ components are connected to one line of the Control Unit. Fault value (r0949, interpret hexadecimal): xyy hex: x = fault cause, yy = component number or connection number.
Remedy:
|
| F01505 (A) BICO: Interconnection cannot be established | Cause: A PROFIdrive telegram has been set (p0922). An interconnection contained in the telegram was not able to be established. Fault value (r0949, interpret decimal): Parameter receiver that should be changed. Remedy: Establish another interconnection. |
| F01510 BICO: Signal source is not float type | Cause: The requested connector output does not have the correct data type. This interconnection is not established. Fault value (r0949, interpret decimal): Parameter number to which an interconnection should be made (connector output). Remedy: Interconnect this connector input with a connector output having a float data type. |
| F01511 (A) BICO: Interconnection with different scalings | Cause: The requested BICO interconnection was established. However, a conversion is made between the BICO output and BICO input using the reference values.
Parameter number of the BICO input (signal sink). Remedy: Not necessary. |
| F01512 BICO: No scaling available | Cause: An attempt was made to determine a conversion factor for a scaling that does not exist. Fault value (r0949, interpret decimal): Unit (e.g. corresponding to SPEED) for which an attempt was made to determine a factor. Remedy: Apply scaling or check the transfer value. |
| F01513 (N, A) BICO: Interconnection cross DO with different scalings | Cause: The requested BICO interconnection was established. However, a conversion is made between the BICO output and BICO input using the reference values. An interconnection is made between different drive objects and the BICO output has different normalized units than the BICO input or the normalized units are the same but the reference values are different. Fault value (r0949, interpret decimal): Parameter number of the BICO input (signal sink). Remedy: Not necessary. |
| A01514 (F) BICO: Error when writing during a reconnect | Cause: During a reconnect operation (e.g. while booting or downloading) a parameter was not able to be written to. Alarm value (r2124, interpret decimal): Parameter number of the BICO input (signal sink). Remedy: Not necessary. |
| F01515 (A) BICO: Writing to parameter not permitted as the master control is active | Cause: When changing the number of CDS or when copying from CDS, the master control is active. Remedy: If required, return the master control and repeat the operation. |
| A01590 (F) Drive: Motor maintenance interval expired | Cause: The selected service/maintenance interval for this motor was reached. Alarm value (r2124, interpret decimal): Motor data set number. See also: p0650, p0651 Remedy: carry out service/maintenance and reset the service/maintenance interval (p0651). |
| F01600 SI P1: STOP A initiated | Cause: The drive-integrated ‘Safety Integrated’ function on processor 1 has detected an error and initiated a STOP A.
0: Stop request from processor 2. 1005: Pulses suppressed although STO not selected and there is no internal STOP A present. Remedy:
|
| F01611 (A) SI P1: Defect in a monitoring channel | Cause: The drive-integrated ‘Safety Integrated’ function on processor 1 has detected a fault in the crosswise data comparison between the two monitoring channels and has initiated a STOP F. Fault F01600 is output as a consequence of this fault. Fault value (r0949, interpret decimal): Indicates the number or type of cross-compared data that resulted in the fault, including various PROFIsafe fault values. Remedy: Remedy depends on the specific fault value. General steps include:
|
| N01620 (F, A) SI P1: Safe Torque Off active | Cause: The ‘Safe Torque Off’ (STO) function has been selected on processor 1 using the input terminal and is active. This message does not result in a safety stop response. Remedy: Not necessary. |
| F01625 SI P1: Sign-of-life error in safety data | 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.
Remedy:
|
| F01649 SI P1: Internal software error | Cause: An internal error in the Safety Integrated software on processor 1 has occurred. This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| F01650 SI P1: Acceptance test required | Cause: The drive-integrated ‘Safety Integrated’ function on processor 1 requires an acceptance test. This fault results in a STOP A that can be acknowledged. Fault value (r0949, interpret decimal): Indicates the reason for the test, such as first-time commissioning, checksum mismatch, safety parameter change, or project download. Remedy: Remedy depends on the fault value. General steps include:
|
| F01651 SI P1: Synchronization safety time slices unsuccessful | Cause: The ‘Safety Integrated’ function requires synchronization of the safety time slices between processor 1 and processor 2. This synchronization was unsuccessful. This fault results in a STOP A that cannot be acknowledged. Remedy: Carry out a POWER ON (power off/on). |
| F01653 SI P1: PROFIBUS/PROFINET configuration error | Cause: There is a PROFIBUS/PROFINET configuration error for using Safety Integrated monitoring functions with a higher-level control. This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret decimal): Specific codes indicate issues like safety slot for receive/send data not configured, unknown format, or incorrect length. Remedy: The following generally applies:
|
| A01654 (F) SI P1: Deviating PROFIsafe configuration | Cause: The configuration of a PROFIsafe telegram in the higher-level control (F-PLC) does not match the parameterization in the drive. Alarm value (r2124, interpret decimal): 1: A PROFIsafe telegram is configured in the F-PLC, but PROFIsafe is not enabled in the drive (p9601.3). 2: PROFIsafe is parameterized in the drive, but a PROFIsafe telegram has not been configured in the F-PLC. Remedy: The following generally applies:
|
| F01655 SI P1: Align monitoring functions | Cause: An error has occurred when aligning the Safety Integrated monitoring functions on processor 1 and processor 2. No common set of supported SI monitoring functions was able to be determined. There is a communication error between processor 1 and processor 2. Note: This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| F01656 SI P1: Parameter processor 2 parameter error | Cause: When accessing the Safety Integrated parameters for the processor 2 in the non-volatile memory, an error has occurred. This fault results in a STOP A that can be acknowledged. Fault value (r0949, interpret decimal):
Remedy:
|
| F01658 SI P1: PROFIsafe telegram number not suitable | Cause: The PROFIsafe telegram number in p60022 is unsuitable for the enabled safety functions. Possible causes:
Remedy: Select the telegram number that matches the Safety functions that have been enabled. See also: p9501, p9601, p60022 |
| F01659 SI P1: Write request for parameter rejected | Cause: The write request for one or several Safety Integrated parameters on processor 1 was rejected. Fault value (r0949, interpret decimal):
Remedy: Remedy depends on the fault value:
|
| F01660 SI P1: Safety-related functions not supported | Cause: The Power Module does not support the safety-related functions. Safety Integrated cannot be commissioned. Note: This fault does not result in a safety stop response. Remedy: use a Power Module that supports the safety-related functions. |
| F01661 SI P1: Simulation of the safety inputs active | Cause: The simulation of the digital inputs of the Control Unit (p0795) is active. It is not permissible that safety inputs are simulated. Fault value (r0949, interpret binary): The displayed bits indicate which digital inputs must not be simulated. Remedy:
|
| F01662 Error internal communications | Cause: A module-internal communication error has occurred. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01663 SI P1: Copying the SI parameters rejected | Cause: One of the following values is saved in p9700 or was entered offline: 87 or 208. This is the reason that when booting, an attempt is made to copy SI parameters from processor 1 to processor 2. However, no safety-relevant function has been selected on processor 1 (p9501 = 0, p9601 = 0). Note: This fault does not result in a safety stop response. Remedy:
|
| F01665 SI P1: System is defective | Cause: A system defect was detected before the last boot or in the actual one. The system might have been rebooted (reset). Fault value (r0949, interpret hexadecimal): 200000 hex, 400000 hex, 8000yy hex (yy any): Fault in the actual booting/operation. Additional values: defect before the last time that the system booted. Remedy:
|
| A01666 (F) SI Motion P1: Steady-state (static) 1 signal at the F-DI for safety-relevant acknowledgement | Cause: A logical 1 signal is present at the F-DI configured in p10006 for more than 10 seconds. If, at the F-DI no acknowledgment was performed for safe acknowledgment, then a steady-state logical and 0 signal must be present. This avoids unintentional safety-relevant acknowledgement if a wire breaks. Remedy: Set the fail-safe digital input (F-DI) to a logical 0 signal (p10006). Note: F-DI: Failsafe Digital Input |
| A01669 (F, N) SI Motion: Unfavorable combination of motor and power unit | Cause: The combination of motor and power unit used is not suitable for using safe motion monitoring functions without an encoder. The ratio between the power unit rated current (r0207[0]) and rated motor current (p0305) is greater than 5. Alarm value (r2124, interpret decimal): Number of the motor data set, which caused the fault. Notice: If this alarm is not observed, then message C01711 or C30711 – with the value 1041 … 1044 – can sporadically occur. Remedy: Use a suitable power unit with a lower power rating or a motor with a higher power rating. |
| F01680 SI Motion P1: Checksum error safety monitoring functions | Cause: The actual checksum calculated by the drive and entered in r9728 via the safety-relevant parameters does not match the reference checksum saved in p9729 at the last machine acceptance. Safety-relevant parameters have been changed or a fault is present. Note: This fault results in a STOP A that can be acknowledged. Fault value (r0949, interpret decimal): 0: Checksum error for SI parameters for motion monitoring. 1: Checksum error for SI parameters for actual values. 2: Checksum error for SI parameters for component assignment. Remedy:
|
| F01681 SI Motion P1: Incorrect parameter value | Cause: The parameter cannot be parameterized with this value. Note: This fault does not result in a safety stop response. Fault value (r0949, interpret decimal): yyyyxxxx dec: yyyy = supplementary information, xxxx = parameter. yyyy = 0: No information available. xxxx = 9501: It is not permissible to enable the function ‘n < nx hysteresis and filtering' (p9501.16) in conjunction with 'Extended functions without selection' (p9601.5). Remedy: Correct the parameter value. If xxxx = 9547: With hysteresis/filtering enabled (p9501.16 = 1), set parameters p9546/p9346 and p9547/p9347 according to the rule: p9546 >= 2 x p9547; p9346 >= 2 x p9347. If xxxx = 9522 and 9585: Correct parameters. |
| F01682 SI Motion P1: Monitoring function not supported | Cause: The monitoring function enabled in p9501, p9601 or p9801 is not supported in this firmware version. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret decimal): Lists various monitoring functions that are not supported (e.g., SLP, SCA, SLS override, etc.). Remedy: De-select the monitoring function involved (p9501, p9601, p9801). |
| F01683 SI Motion P1: SLS enable missing | Cause: The safety-relevant function ‘SLS’ is not enabled in p9501 although other safety-relevant monitoring functions are enabled. Note: This fault does not result in a safety stop response. Remedy: Enable the function ‘SLS’ (p9501.0) and carry out a POWER ON. Note: Save the changes before POWER ON (copy from RAM to ROM). |
| F01690 SI Motion: Data save problem for the NVRAM | Cause: There is not sufficient memory space in the NVRAM on the drive to save parameters r9781 and r9782 (safety logbook). Note: This fault does not result in a safety stop response. Fault value (r0949, interpret decimal): 0: There is no physical NVRAM available in the drive. 1: There is no longer any free memory space in the NVRAM. Remedy: For fault value = 0:
|
| F01692 SI Motion P1: Parameter value not permitted for encoderless | Cause: For encoderless motion monitoring functions, the parameter cannot be parameterized with this value. Note: This fault does not result in a safety stop response. Fault value (r0949, interpret decimal): Parameter number with the incorrect value. Remedy: Correct the parameter specified in the fault value. See also: p9501 (SI Motion enable safety functions (processor 1)) |
| A01693 (F) SI Motion P1: Safety parameter setting changed, POWER ON required | Cause: Safety parameters have been changed; these will only take effect following a POWER ON. Notice: All changed parameters of the safety motion monitoring functions will only take effect following a POWER ON. Alarm value (r2124, interpret decimal): Parameter number of the safety parameter which has changed, necessitating a POWER ON. Remedy:
|
| A01696 (F) SI Motion: Testing of the motion monitoring functions selected when booting | Cause: The test of the motion monitoring functions was already illegally active when booting. This is the reason that the test is only carried out again after selecting the forced checking procedure parameterized in p9705. Note: This message does not result in a safety stop response. Remedy: De-select the forced checking procedure of the safety motion monitoring functions and then select again. The signal source for initiation is parameterized in binector input p9705. See also: p9705 (SI Motion: Test stop signal source) |
| A01697 (F) SI Motion: Motion monitoring functions must be tested | Cause: The time set in p9559 for the forced checking procedure of the safety motion monitoring functions has been exceeded. A new test is required. After next selecting the forced checking procedure, the message is withdrawn. Note: This message does not result in a safety stop response. The test must be performed within a defined maximum time interval (p9559, max 9000 hours). Remedy: Carry out the forced checking procedure of the safety motion monitoring functions. The signal source for initiation is parameterized in binector input p9705. See also: p9705 (SI Motion: Test stop signal source) |
| A01698 (F) SI P1: Commissioning mode active | Cause: The commissioning of the ‘Safety Integrated’ function is selected. This message is withdrawn after the safety functions have been commissioned. Note: This message does not result in a safety stop response. In the safety commissioning mode, the ‘STO’ function is internally selected. Remedy: Not necessary. See also: p0010 (Drive commissioning parameter filter) |
| A01699 (F) SI P1: Shutdown path must be tested | Cause: The time set in p9659 for the forced checking procedure of the safety shutdown paths has been exceeded. The safety shutdown paths must be re-tested. After the next time the ‘STO’ function is de-selected, the message is withdrawn. Note: This message does not result in a safety stop response. The test must be performed within a defined maximum time interval (p9659, max 9000 hours). Remedy: Select STO and then de-select again. |
| C01700 SI Motion P1: STOP A initiated | Cause: The drive is stopped via a STOP A (pulses are suppressed via the safety shutdown path of processor 1). Possible causes:
Remedy:
|
| C01701 SI Motion P1: STOP B initiated | Cause: The drive is stopped via a STOP B (braking along the OFF3 deceleration ramp). As a result of this fault, after the speed threshold in p9560 is fallen below, message C01700 ‘STOP A initiated’ is output. Possible causes:
Remedy:
|
| C01706 SI Motion P1: SAM/SBR limit exceeded | Cause: For motion monitoring functions with set acceleration monitoring (SAM, p9506 = 3) or brake ramp monitoring (SBR, p9506 = 1), after initiating STOP B (SS1) or SLS changeover, the velocity has exceeded the selected tolerance. The drive is shut down by the message C01700 ‘SI Motion: STOP A initiated’. Remedy: Check the braking behavior and, if necessary, adapt the parameterization of the ‘SAM’ or ‘SBR’ function. This message can be acknowledged without a POWER ON as follows: motion monitoring functions integrated in the drive: via F-DI or PROFIsafe. See also: p9548, p9581, p9582, p9583. |
| C01711 SI Motion P1: Defect in a monitoring channel | Cause: When cross-comparing the two monitoring channels, the drive detected a difference between the input data or results of the monitoring functions and initiated a STOP F. One of the monitoring functions no longer reliably functions. If at least one monitoring function is active, then message C01701 ‘SI Motion: STOP B initiated’ is output. Message value (r2124, interpret decimal): Indicates the specific cross-compared data that resulted in the fault, ranging from status images, position values, limit values, to various internal checks and PROFIsafe errors. Remedy: Remedy is highly dependent on the message value. General steps include:
|
| C01712 SI Motion P1: Defect in F-IO processing | Cause: When cross checking and comparing the two monitoring channels, the drive detected a difference between parameters or results of the F-IO processing and initiated a STOP F. Safe operation is no longer possible. The safety message C01711 with message value 0 is also displayed. If at least one monitoring function is active, then safety message C01701 ‘SI Motion: STOP B initiated’ is output. Message value (r2124, interpret decimal): Number of the cross-compared data that resulted in this message (e.g., discrepancy times, input terminals, debounce times). Remedy:
|
| C01714 SI Motion P1: Safely-Limited Speed exceeded | Cause: The drive has moved faster than that specified by the velocity limit value (p9531). The drive is stopped as a result of the configured stop response (p9563). Message value (r2124, interpret decimal): 100: SLS1 exceeded. 200: SLS2 exceeded. 300: SLS3 exceeded. 400: SLS4 exceeded. Remedy:
|
| C01716 SI Motion P1: Tolerance for safe motion direction exceeded | Cause: The tolerance for the ‘safe motion direction’ function was exceeded. The drive is stopped as a result of the configured stop response (p9566). Message value (r9749, interpret decimal): 0: Tolerance for the ‘safe motion direction positive’ function exceeded. 1: Tolerance for the ‘safe motion direction negative’ function exceeded. Remedy:
|
| C01770 SI Motion P1: Discrepancy error of the failsafe inputs | Cause: The fail-safe digital inputs (F-DI) show a different state longer than that parameterized in p10002 / p10102. Fault value (r0949, interpret binary): Bit 0: Discrepancy error for F-DI 0 Bit 1: Discrepancy error for F-DI 1 Note: If several discrepancy errors occur consecutively, then this fault is only signaled for the first error that occurs. Remedy: check the wiring of the F-DI (contact problems). Note: This message can be acknowledged via F-DI or PROFIsafe. Discrepancy errors can only be fully acknowledged after the cause is resolved and safe acknowledgement is performed. For cyclic switching, it may be necessary to adapt the discrepancy time based on the switching frequency and debounce time. |
| A01796 (F, N) SI P1: Wait for communication | Cause: The drive waits for communication to be established to execute the safety-relevant motion monitoring functions. Note: In this state, the pulses are safely suppressed. Alarm value (r2124, interpret decimal): 3: Wait for communication to be established to PROFIsafe F-Host. Remedy: If, after a longer period of time, the message is not automatically withdrawn, the following checks have to be made:
|
| C01798 SI Motion P1: Test stop running | Cause: The test stop is active. Remedy: Not necessary. The message is withdrawn when the test stop is finished. |
| C01799 SI Motion P1: Acceptance test mode active | Cause: The acceptance test mode is active. Remedy: Not necessary. The message is withdrawn when exiting the acceptance test mode. |
| A01900 (F) PROFIBUS: Configuration telegram error | Cause: A PROFIBUS master attempts to establish a connection using an incorrect configuring telegram. Alarm value (r2124, interpret decimal):
Remedy: Check the bus configuration on the master and slave sides. Re alarm value = 2: Check the number of data words for input and output. Re alarm value = 211: Ensure offline version <= online version. Re alarm value = 501: Check the set PROFIsafe address (p9610). Re alarm value = 502: Check the enable of F-DI (p9501.30). |
| F01910 (N, A) Fieldbus interface setpoint timeout | Cause: The reception of setpoints from the fieldbus interface has been interrupted.
Remedy: Ensure bus connection has been established and switch on communication peer.
|
| A01920 (F) PROFIBUS: Interruption cyclic connection | Cause: The cyclic connection to the PROFIBUS master is interrupted. Remedy: Establish the PROFIBUS connection and activate the PROFIBUS master in the cyclic mode. |
| A01945 PROFIBUS: Connection to the Publisher failed | Cause: For PROFIBUS peer-to-peer data transfer, the connection to at least one Publisher has failed. Alarm value (r2124, interpret binary): Bit 0 to 15 indicates which publisher connection failed. Remedy: Check the PROFIBUS cables. See also: r2077 (PROFIBUS diagnostics peer-to-peer data transfer addresses) |
| F01946 (A) PROFIBUS: Connection to the Publisher aborted | Cause: The connection to at least one Publisher for PROFIBUS peer-to-peer data transfer in cyclic operation has been aborted. Fault value (r0949, interpret binary): Bit 0 to 15 indicates which publisher connection was aborted. Remedy:
|
| F01951 CU SYNC: Synchronization application clock cycle missing | Cause: Internal synchronization of the application cycles unsuccessful. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01953 CU SYNC: Synchronization not completed | Cause: After the drive system was powered up, synchronization between the basic clock cycle and application clock cycle was started but was not completed within the selected time tolerance. Alarm value (r2124, interpret decimal): Only for internal Siemens troubleshooting. Remedy: Carry out a POWER ON (power off/on). |
| A02050 Trace: Start not possible | Cause: The trace has already been started. Remedy: Stop the trace and, if necessary, start again. |
| A02055 Trace: Recording time too short | Cause: The trace duration is too short. The minimum is twice the value of the trace clock cycle. Remedy: Check the selected recording time and, if necessary, adjust. |
| A02056 Trace: Recording cycle too short | Cause: The selected recording clock cycle is lower than the basic clock cycle 500μs. Remedy: Increase the value for the trace cycle. |
| A02057 Trace: Time slice clock cycle invalid | Cause: The time slice clock cycle selected does not match any of the existing time slices. Remedy: Enter an existing time slice clock cycle. The existing time slices can be read out via p7901. See also: r7901 (Sampling times) |
| A02058 Trace: Time slice clock cycle for endless trace not valid | Cause: The selected time slice clock cycle cannot be used for the endless trace. Remedy: Enter the clock cycle of an existing time slice with a cycle time >= 2 ms for up to 4 recording channels or >= 4 ms from 5 recording channels per trace. The existing time slices can be read out via p7901. See also: r7901 (Sampling times) |
| A02059 Trace: Time slice clock cycle for 2 x 8 recording channels not valid | Cause: The selected time slice clock cycle cannot be used for more than 4 recording channels. Remedy: Enter the clock cycle of an existing time slice with a cycle time >= 4 ms or reduce the number of recording channels to 4 per trace. The existing time slices can be read out via p7901. See also: r7901 (Sampling times) |
| A02060 Trace: Signal to be traced missing | Cause:
Remedy:
|
| A02061 Trace: Invalid signal | Cause:
Remedy:
|
| A02062 Trace: Invalid trigger signal | Cause:
Remedy: Specify a valid trigger signal. |
| A02063 Trace: Invalid data type | Cause: The specified data type to select a signal using a physical address is invalid. Remedy: Use a valid data type. |
| A02070 Trace: Parameter cannot be changed | Cause: The trace parameter settings cannot be changed when the trace is active. Remedy:
|
| A02075 Trace: Pretrigger time too long | Cause: The selected pretrigger time must be shorter than the trace time. Remedy: Check the pretrigger time setting and change if necessary. |
| F02080 Trace: Parameterization deleted due to unit changeover | Cause: The trace parameterization in the drive unit was deleted due to a unit changeover or a change in the reference parameters. Remedy: Restart trace. |
| A02097 MTrace: multiple trace cannot be activated | Cause: The following functions or settings are not permissible in conjunction with a multiple trace:
Remedy:
|
| A02098 MTrace: cannot be saved | Cause: It is not possible to save the measurement results of a multiple trace on the memory card. A multiple trace is not started or is canceled. Alarm value (r2124, interpret decimal):
Remedy:
|
| A02099 Trace: Insufficient Control Unit memory | Cause: The memory space still available on the Control Unit is no longer sufficient for the trace function. Remedy: Reduce the memory required, e.g. as follows:
|
| A02150 OA: Application cannot be loaded | Cause: The system was not able to load an OA application. Alarm value (r2124, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F02151 (A) OA: Internal software error | Cause: An internal software error has occurred within an OA application. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F02152 (A) OA: Insufficient memory | Cause: Too many functions have been configured on this Control Unit (e.g. too many drives, function modules, data sets, OA applications, blocks, etc). Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| F03000 NVRAM fault on action | Cause: A fault occurred during execution of action p7770 = 1 or 2 for the NVRAM data. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = fault cause, xx = application ID. Causes include unsupported action, incorrect data length, or wrong checksum. Remedy:
|
| F03001 NVRAM checksum incorrect | Cause: A checksum error occurred when evaluating the non-volatile data (NVRAM) on the Control Unit. The NVRAM data affected was deleted. Remedy: Carry out a POWER ON (power off/on) for all components. |
| F03505 (N, A) CU: Analog input wire breakage | Cause: The wire-break monitoring for an analog input has responded. The input current of the analog input has undershot the threshold value parameterized in p0761[0…3]. Note: For the analog input type, p0756[0…1] = 1 (2 … 10 V with monitoring), the wire breakage monitoring is active. Remedy:
|
| A03510 (F, N) CU: Calibration data not plausible | Cause: During booting, the calibration data for the analog inputs is read and checked with respect to plausibility. At least one calibration data point was determined to be invalid. Remedy:
|
| A05000 (N) Power unit: Overtemperature heat sink AC inverter | Cause: The alarm threshold for overtemperature at the inverter heat sink has been reached. The response is set using p0290. If the temperature of the heat sink increases by an additional 5 K, then fault F30004 is initiated. Remedy: Check the following:
|
| A05001 (N) Power unit: Overtemperature depletion layer chip | Cause: Alarm threshold for overtemperature of the power semiconductor in the AC converter has been reached. If the depletion layer temperature increases by an additional 15 K, then fault F30025 is triggered. Remedy: Check the following:
|
| A05002 (N) Power unit: Air intake overtemperature | Cause: For chassis power units, the alarm threshold for the air intake overtemperature has been reached. For air-cooled power units, the threshold is 42 °C. If the temperature increases by an additional 13 K, then fault F30035 is output. Remedy: Check the following:
|
| A05004 (N) Power unit: Rectifier overtemperature | Cause: The alarm threshold for the overtemperature of the rectifier has been reached. If the temperature of the rectifier increases by an additional 5 K, then fault F30037 is triggered. Remedy: Check the following:
|
| A05006 (N) Power unit: Overtemperature thermal model | Cause: The temperature difference between the chip and heat sink has exceeded the permissible limit value (blocksize power units only). Depending on p0290, an appropriate overload response is initiated. Note: If the alarm does not disappear and temperature continues to rise, this can result in fault F30024. Remedy: Not necessary. The alarm disappears automatically once the limit value is undershot. |
| F06310 (A) Supply voltage (p0210) incorrectly parameterized | Cause: The measured DC voltage lies outside the tolerance range after pre-charging has been completed. The tolerance range is: 1.16 * p0210 < r0070 < 1.6 * p0210. Note: The fault can only be acknowledged when the drive is powered down. Remedy:
|
| A06921 (N) Braking resistor phase unsymmetry | Cause: The three resistors of the braking chopper are not symmetrical. Remedy:
|
| F06922 Braking resistor phase failure | Cause: A phase failure for the brake resistor was detected. Fault value (r0949, interpret decimal): 11: Phase U, 12: Phase V, 13: Phase W Remedy: Check the feeder cables to the braking resistors. |
| F07011 Drive: Motor overtemperature | Cause: KTY: The motor temperature has exceeded the fault threshold (p0605) or the timer (p0606) after the alarm threshold was exceeded (p0604) has expired. PTC or bimetallic NC contact: The response threshold of 1650 Ohm was exceeded or the NC contact opened and the timer (p0606) has expired. Possible causes: Motor is overloaded, motor ambient temperature too high, Wire break or sensor not connected. Remedy:
|
| A07012 (N) Drive: Motor temperature model 1 overtemperature | Cause: The thermal I2t motor model for synchronous motors identified that the alarm threshold was exceeded. Remedy:
|
| A07014 (N) Drive: Motor temperature model configuration alarm | Cause: A fault has occurred in the configuration of the motor temperature model. Alarm value (r2124, interpret decimal): 1: It is not possible to save the model temperature. Remedy: set the response for motor overtemperature to ‘Alarm and fault, no reduction of I_max’ (p0610 = 2). |
| A07015 Drive: Motor temperature sensor alarm | Cause: An error was detected when evaluating the temperature sensor set in p0601. With the fault, the time in p0607 is started. If the fault is still present after this time has expired, then fault F07016 is output. Possible causes:
Remedy:
|
| F07016 Drive: Motor temperature sensor fault | Cause: An error was detected when evaluating the temperature sensor set in p0601. Possible causes: wire breakage or sensor not connected, or measured resistance too low. Note: If alarm A07015 is present, the time in p0607 is started. If the fault is still present after this time has expired, then fault F07016 is output. Remedy:
|
| F07080 Drive: Incorrect control parameter | Cause: The closed-loop control parameters have been parameterized incorrectly (e.g. p0356 = L_spread = 0). Fault value (r0949, interpret decimal): The fault value includes the parameter number involved. Remedy: Modify the parameter indicated in the fault value (r0949) (e.g. p0640 = current limit > 0). |
| F07082 Macro: Execution not possible | Cause: The macro cannot be executed. Fault value (r0949, interpret hexadecimal): ccccbbaa hex, where cccc = preliminary parameter number, bb = supplementary information, aa = fault cause. Various fault causes are listed, including invalid file, incorrect data type, recursive calls, and write protection. Remedy:
|
| F07083 Macro: ACX file not found | Cause: The ACX file (macro) to be executed was not able to be found in the appropriate directory. Fault value (r0949, interpret decimal): Parameter number with which the execution was started. Remedy: check whether the file is saved in the appropriate directory on the memory card. |
| F07084 Macro: Condition for WaitUntil not fulfilled | Cause: The WaitUntil condition set in the macro was not fulfilled in a certain number of attempts. Fault value (r0949, interpret decimal): Parameter number for which the condition was set. Remedy: Check and correct the conditions for the WaitUntil loop. |
| F07086 Units changeover: Parameter limit violation due to reference value change | Cause: A reference parameter was changed in the system. This resulted in the fact that for the parameters involved, the selected value was not able to be written in the per unit notation. The values of the parameters were set to the corresponding violated limit or to the factory setting. Possible causes: the steady-state minimum limit/maximum limit or that defined in the application was violated. Remedy: Check the adapted parameter value and if required correct. |
| F07088 Units changeover: Parameter limit violation due to units changeover | Cause: A changeover of units was initiated. This resulted in a violation of a parameter limit. Possible causes:
Remedy: Check the adapted parameter values and if required correct. See also: r9451 (Units changeover adapted parameters) |
| A07089 Changing over units: Function module activation is blocked because the units have been changed over | Cause: An attempt was made to activate a function module. This is not permissible if the units have already been changed over. Remedy: Restore units that have been changed over to the factory setting. |
| A07200 Drive: Master control ON command present | Cause: The ON/OFF1 command is present (no 0 signal). The command is either influenced via binector input p0840 (current CDS) or control word bit 0 via the master control. Remedy: Switch the signal via binector input p0840 (current CDS) or control word bit 0 via the master control to 0. |
| F07220 (N, A) Drive: Master control by PLC missing | Cause: The ‘master control by PLC’ signal was missing in operation.
Remedy:
|
| F07300 (A) Drive: Line contactor feedback signal missing | Cause:
Remedy:
|
| F07320 Drive: Automatic restart interrupted | Cause:
Remedy:
|
| A07321 Drive: Automatic restart active | Cause: The automatic restart (AR) is active. When the line supply returns and/or the causes of the existing faults are removed the drive is automatically restarted. The pulses are enabled and the motor starts to rotate. For p1210 = 26, the alarm after the line supply returns is also displayed if there is no fault and there is no ON command. Remedy:
|
| F07330 Flying restart: Measured search current too low | Cause: During a flying restart, it was identified that the search current reached is too low. It is possible that the motor is not connected. Remedy: Check the motor feeder cables. |
| F07331 Flying restart: Function not supported | Cause: It is not possible to power up with the motor rotating (no flying restart). In the following cases, the ‘flying restart’ function is not supported: Perm.-magnet synch. motors (PEM): operation with U/f char. and sensorless vector control. Remedy: De-activate the ‘flying restart’ function (p1200 = 0). |
| A07400 (N) Drive: DC link voltage maximum controller active | Cause: The DC link voltage controller has been activated because the upper switch-in threshold has been exceeded (r1242, r1282). The ramp-down times are automatically increased in order to maintain the DC link voltage (r0070) within the permissible limits. There is a system deviation between the setpoint and actual speeds. Remedy: If the controller is not to intervene:
|
| A07401 (N) Drive: DC link voltage maximum controller de-activated | Cause: The Vdc_max controller can no longer maintain the DC link voltage (r0070) below the limit value (r1242, r1282) and was therefore switched out (disabled).
Remedy:
|
| A07402 (N) Drive: DC link voltage minimum controller active | Cause: The DC link voltage controller has been activated as the lower switch-in threshold has been undershot (r1246, r1286). The kinetic energy of the motor is used to buffer the DC link. The drive is therefore braked. Remedy: The alarm disappears when power supply returns. |
| F07404 Drive: DC link voltage monitoring Vdc_Max | Cause: The monitoring of the DC link voltage p1284 has responded (only U/f control). Remedy:
|
| F07405 (N, A) Drive: Kinetic buffering minimum speed not reached | Cause: During kinetic buffering the speed fell below minimum speed (p1257 or p1297 for vector drives with U/f control) and the line supply did not return. Remedy: Check the speed threshold for the Vdc_min controller (kinetic buffering) (p1257, p1297). |
| F07406 (N, A) Drive: Kinetic buffering maximum time exceeded | Cause: The maximum buffer time (p1255 and p1295 for vector drives with U/f control) has been exceeded without the line supply having returned. Remedy: Check the time threshold for Vdc-min controller (kinetic buffering) (p1255, p1295). |
| A07409 Drive: U/f control, current limiting controller active | Cause: The current limiting controller of the U/f control was activated because the current limit was exceeded. Remedy: The alarm automatically disappears after one of the following measures:
|
| F07410 Drive: Current controller output limited | Cause: The condition ‘l_act = 0 and Uq_set_1 longer than 16 ms at its limit’ is present and can be caused by the following:
Remedy:
|
| F07411 Drive: Flux controller output limited | Cause: When quick magnetizing is configured (p1401.6 = 1) the specified flux setpoint is not reached although 90% of the maximum current is specified.
Remedy:
|
| A07416 Drive: Flux controller configuration | Cause: The configuration of the flux control (p1401) is contradictory. Alarm value (r2124, interpret hexadecimal): ccbbaaaa hex. aaaa = Parameter, bb = Index, cc = fault cause 1: Quick magnetizing (p1401.6) for soft starting (p1401.0). 2: Quick magnetizing for flux build-up control (p1401.2). 3: Quick magnetizing (p1401.6) for Rs identification after restart (p0621 = 2). Remedy: Re fault cause = 1:
|
| F07426 (A) Technology controller actual value limited | Cause: The actual value for the technology controller, interconnected via connector input p2264, has reached a limit. Fault value (r0949, interpret decimal):
Remedy:
|
| A07428 (N) Technology controller parameterizing error | Cause: The technology controller has a parameterizing error. Alarm value (r2124, interpret decimal): 1: The upper output limit in p2291 is set lower than the lower output limit in p2292. Remedy: Set the output limit in p2291 higher than in p2292. |
| F07435 (N) Drive: Setting the ramp-function generator for sensorless vector control | Cause: During operation with sensorless vector control (r1407.1) the ramp-function generator was stopped (p1141). An internal setting command of the ramp-function generator output caused the set setpoint speed to be frozen. Remedy:
|
| A07530 Drive: Drive Data Set DDS not present | Cause: The selected drive data set is not available (p0837 > p0180). The drive data set was not changed over. Remedy:
|
| A07531 Drive: Command Data Set CDS not present | Cause: The selected command data set is not available (p0836 > p0170). The command data set was not changed over. Remedy:
|
| F07563 (A) Drive encoder: XIST1_ERW configuration incorrect | Cause: An incorrect configuration was identified for the ‘Absolute position for incremental encoder’ function. Fault value (r0949, interpret decimal): 1 (= 01 hex): The ‘Absolute value for incremental encoder’ function is not supported (r0459.13 = 0). Remedy: For fault value = 1:
|
| F07800 Drive: No power unit present | Cause: The power unit parameters cannot be read or no parameters are stored in the power unit. It is possible that the DRIVE-CLiQ cable between the Control Unit and power unit is interrupted or defective. Note: This fault also occurs if an incorrect topology was selected in the commissioning software and this parameterization is then downloaded to the Control Unit. Remedy:
|
| F07801 Drive: Motor overcurrent | Cause: The permissible motor limit current was exceeded.
Remedy:
|
| F07802 Drive: Infeed or power unit not ready | Cause: After an internal power-on command, the infeed or drive does not signal ready.
Remedy:
|
| A07805 (N) Drive: Power unit overload I2t | Cause: Alarm threshold for I2t overload (p0294) of the power unit exceeded. The response parameterized in p0290 becomes active. Remedy:
|
| F07806 Drive: Regenerative power limit exceeded (F3E) | Cause: For blocksize power units, types PM250 and PM260, the regenerative rated power r0206[2] was exceeded for more than 10 s. Remedy:
|
| F07807 Drive: Short-circuit/ground fault detected | Cause: A phase-phase short-circuit or ground fault was detected at the motor-side output terminals of the converter. Fault value (r0949, interpret decimal): Values indicate short-circuit between specific phases or a ground fault with current details. Remedy:
|
| F07808 (A) HF damping module: damping not ready | Cause: When switching on or in the switched-on state, the HF damping module does not return a ready signal. Remedy:
|
| F07810 Drive: Power unit EEPROM without rated data | Cause: No rated data are stored in the power unit EEPROM. Remedy: Replace the power unit or inform Siemens Customer Service. |
| A07850 (F) External alarm 1 | Cause: The BICO signal for ‘external alarm 1’ was triggered. The condition for this external alarm is fulfilled. Remedy: Eliminate the causes of this alarm. |
| A07851 (F) External alarm 2 | Cause: The BICO signal for ‘external alarm 2’ was triggered. The condition for this external alarm is fulfilled. Remedy: Eliminate the causes of this alarm. |
| A07852 (F) External alarm 3 | Cause: The BICO signal for ‘external alarm 3’ was triggered. The condition for this external alarm is fulfilled. Remedy: Eliminate the causes of this alarm. |
| F07860 (A) External fault 1 | Cause: The BICO signal ‘external fault 1’ was triggered. Remedy: Eliminate the causes of this fault. |
| F07861 (A) External fault 2 | Cause: The BICO signal ‘external fault 2’ was triggered. Remedy: Eliminate the causes of this fault. |
| F07862 (A) External fault 3 | Cause: The BICO signal ‘external fault 3’ was triggered. Remedy: Eliminate the causes of this fault. |
| F07900 (N, A) Drive: Motor blocked | Cause: Motor has been operating at the torque limit longer than the time specified in p2177 and below the speed threshold set in p2175. This can also be triggered if the speed is oscillating or if thermal monitoring of the power unit reduces the current limit. Remedy:
|
| F07901 Drive: Motor overspeed | Cause: The maximum permissible speed was either positively or negatively exceeded. The maximum permissible speed is formed based on p1082, CI:p1085, CI:1088 and p2162. Remedy:
|
| F07902 (N, A) Drive: Motor stalled | Cause: The system has identified that the motor has stalled for a time longer than is set in p2178. Fault value (r0949, interpret decimal): 2: Stall detection using r1408.12 (p1745) or via (r0084 – r0083). Remedy:
|
| A07903 Drive: Motor speed deviation | Cause: The absolute value of the speed difference from the setpoint (p2151) and the speed actual value (r2169) exceeds the tolerance threshold (p2163) longer than tolerated (p2164, p2166). The alarm is only enabled for p2149.0 = 1. Possible causes:
Remedy:
|
| A07910 (N) Drive: Motor overtemperature | Cause: KTY or no sensor: The measured motor temperature or the temperature of the motor temperature model 2 has exceeded the alarm threshold (p0604). PTC or bimetallic NC contact: The response threshold of 1650 Ohm was exceeded or the NC contact opened. Alarm value (r2124, interpret decimal): 11: No output current reduction. 12: Output current reduction active. Remedy:
|
| A07920 Drive: Torque/speed too low | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic (too low). For p2193 = 2: The speed signal from the external encoder (refer to p3230) deviates from the speed (r2169) (too low). Remedy:
|
| A07921 Drive: Torque/speed too high | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic (too high). For p2193 = 2: The speed signal from the external encoder (refer to p3230) deviates from the speed (r2169) (too high). Remedy:
|
| A07922 Drive: Torque/speed out of tolerance | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic. For p2193 = 2: The speed signal from the external encoder (refer to p3230) deviates from the speed (r2169). Remedy:
|
| F07923 Drive: Torque/speed too low | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic (too low). For p2193 = 2: The speed signal from the external encoder (refer to p3230) deviates from the speed (r2169) (too low). Remedy:
|
| F07924 Drive: Torque/speed too high | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic (too high). For p2193 = 2: The speed signal from the external encoder (refer to p3230) deviates from the speed (r2169) (too high). Remedy:
|
| F07925 Drive: Torque/speed out of tolerance | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic. For p2193 = 2: The speed signal from the external encoder (refer to p3230) deviates from the speed (r2169). Remedy:
|
| A07927 DC braking active | Cause: The motor is braked with DC current. DC braking is active. 1) A message with response DCBRK is active. The motor is braked with the braking current set in p1232 for the duration set in in p1233. If the standstill threshold p1226 is undershot, then braking is prematurely canceled. 2) DC braking has been activated at binector input p1230 with the DC braking set (p1230 = 4). Braking current p1232 is injected until this binector input becomes inactive. Remedy: Not necessary. The alarm automatically disappears once DC braking has been executed. |
| A07929 (F) Drive: No motor detected | Cause: The absolute current value is so small after enabling the inverter pulses that no motor is detected. Note: In the case of vector control and an induction motor, this alarm is followed by the fault F07902. Remedy:
|
| F07936 Drive: load failure | Cause: The load monitoring has detected a load failure. Remedy:
|
| F07950 (A) Motor parameter incorrect | Cause: The motor parameters were incorrectly entered while commissioning (e.g. p0300 = 0, no motor) Fault value (r0949, interpret decimal): Parameter number involved. Remedy: Compare the motor data with the rating plate data and if required, correct. |
| F07967 Drive: Pole position identification internal fault | Cause: A fault has occurred during the pole position identification routine. Only for internal Siemens troubleshooting. Remedy: Carry out a POWER ON. |
| A07927 DC braking active | Cause: The motor is braked with DC current. DC braking is active. 1) A message with response DCBRK is active. The motor is braked with the braking current set in p1232 for the duration set in p1233. If the standstill threshold p1226 is undershot, then braking is prematurely canceled. 2) DC braking has been activated at binector input p1230 with the DC braking set (p1230 = 4). Braking current p1232 is injected until this binector input becomes inactive. Remedy: Not necessary. The alarm automatically disappears once DC braking has been executed. |
| A07929 (F) Drive: No motor detected | Cause: The absolute current value is so small after enabling the inverter pulses that no motor is detected. Note: In the case of vector control and an induction motor, this alarm is followed by the fault F07902. Remedy:
|
| F07936 Drive: load failure | Cause: The load monitoring has detected a load failure. Remedy:
|
| F07950 (A) Motor parameter incorrect | Cause: The motor parameters were incorrectly entered while commissioning (e.g. p0300 = 0, no motor) Fault value (r0949, interpret decimal): Parameter number involved. Remedy: Compare the motor data with the rating plate data and if required, correct. |
| F07967 Drive: Pole position identification internal fault | Cause: A fault has occurred during the pole position identification routine. Only for internal Siemens troubleshooting. Remedy: Carry out a POWER ON. |
| F07968 Drive: Lq-Ld measurement incorrect | Cause: A fault has occurred during the Lq-Ld measurement. Fault value (r0949, interpret decimal):
Remedy: For fault value = 10:
|
| F07969 Drive: Incorrect pole position identification | Cause: A fault has occurred during the pole position identification routine. Fault value (r0949, interpret decimal):
Remedy: Remedy depends on the fault value:
|
| A07976 Drive: Fine encoder calibration activated | Cause: The alarm indicates the phases of the fine encoder calibration using the alarm value. Alarm value (interpret decimal):
Remedy: Re alarm value = 10:
|
| A07980 Drive: Rotating measurement activated | Cause: The rotating measurement (automatic speed controller optimization) is activated. The rotating measurement is carried out at the next power-on command. Note: During the rotating measurement it is not possible to save the parameters (p0971). Remedy: Not necessary. The alarm disappears automatically after the speed controller optimization has been successfully completed or for the setting p1900 = 0. |
| A07981 Drive: Enable signals for the rotating measurement missing | Cause: The rotating measurement cannot be started due to missing enable signals. For p1959.13 = 1, the following applies:
Remedy:
|
| F07983 Drive: Rotating measurement saturation characteristic | Cause: A fault has occurred while determining the saturation characteristic. Fault value (r0949, interpret decimal):
Remedy: Remedy depends on fault value:
|
| F07984 Drive: Speed controller optimization, moment of inertia | Cause: A fault has occurred while identifying the moment of inertia. Fault value (r0949, interpret decimal):
Remedy: Remedy depends on fault value:
|
| F07985 Drive: Speed controller optimization (oscillation test) | Cause: A fault has occurred during the vibration test. Fault value (r0949, interpret decimal):
Remedy: Remedy depends on fault value:
|
| F07986 Drive: Rotating measurement ramp-function generator | Cause: During the rotating measurements, problems with the ramp-function generator occurred. Fault value (r0949, interpret decimal): 1: The positive and negative directions are inhibited. Remedy: Enable the direction (p1110 or p1111). |
| F07988 Drive: Rotating measurement, no configuration selected | Cause: When configuring the rotating measurement (p1959), no function was selected. Remedy: Select at least one function for automatic optimization of the speed controller (p1959). |
| F07990 Drive: Incorrect motor data identification | Cause: A fault has occurred during the identification routine. Fault value (r0949, interpret decimal): Indicates various issues like current limit reached, identified parameter out of expected range, motor incorrectly connected, shaft rotates, or ground fault detected. Remedy:
|
| A07991 (N) Drive: Motor data identification activated | Cause: The motor data identification routine is activated. The motor data identification routine is carried out at the next power-on command. If rotating measurement is selected (see p1900, p1960), it will not be possible to save the parameter assignment. Remedy: Not necessary. The alarm automatically disappears after the motor data identification routine has been successfully completed or for the setting p1900 = 0. |
| A07994 (F, N) Drive: motor data identification not performed | Cause: The ‘vector control’ mode has been selected and a motor data identification has still not been performed. The alarm is initiated when changing the drive data set in the following cases: vector control is parameterized in the actual drive data set (p1300 >= 20) and motor data identification has still not been performed in the actual drive data set. Remedy:
|
| F08010 (N, A) CU: Analog-to-digital converter | Cause: The analog-to-digital converter on the Control Unit has not supplied any converted data. Remedy:
|
| F08501 (N, A) PROFINET: Setpoint timeout | Cause: The reception of setpoints from PROFINET has been interrupted.
Remedy:
|
| F08502 (A) PROFINET: Monitoring time sign-of-life expired | Cause: The monitoring time for the sign-of-life counter has expired. The connection to the PROFINET interface was interrupted. Remedy:
|
| A08511 (F) PROFINET: Receive configuration data invalid | Cause: The drive unit did not accept the receive configuration data. Alarm value (r2124, interpret decimal):
Remedy: Check the receive configuration data. Re alarm value = 2: Check the number of data words for output and input to a drive object. Re alarm value = 501: Check the set PROFIsafe address (p9610). |
| A08526 (F) PROFINET: No cyclic connection | Cause: There is no connection to a PROFINET controller. Remedy: Establish the cyclic connection and activate the controller with cyclic operation. Check the parameters ‘Name of Station’ and ‘IP of Station’ (r61000, r61001). |
| A08565 PROFINET: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration (p8925 = 1) for the PROFINET interface. The currently set configuration has not been activated. Possible causes:
Remedy: Check the required interface configuration (p8920 and following), correct if necessary, and activate (p8925 = 1). |
| F08700 (A) CAN: Communications error | Cause: A CAN communications error has occurred. Fault value (r0949, interpret decimal):
Remedy:
|
| F08701 CAN: NMT state change | Cause: A CANopen NMT state transition from ‘operational’ to ‘pre-operational’ or after ‘stopped’. Fault value (r0949, interpret decimal): 1: CANopen NMT state transition from ‘operational’ to ‘pre-operational’. 2: CANopen NMT state transition from ‘operational’ to ‘stopped’. Remedy: Not necessary. Acknowledge the fault and continue operation. |
| F08702 (A) CAN: RPDO Timeout | Cause: The monitoring time of the CANopen RPDO telegram has expired because the bus connection was either interrupted or the CANopen Master was switched-off. Remedy:
|
| A08751 (N) CAN: Telegram loss | Cause: The CAN controller has lost a receive message (telegram). Remedy: Reduce the cycle times of the receive messages. |
| A08752 CAN: Error counter for error passive exceeded | Cause: The error counter for the send or receive telegrams has exceeded the value 127. Remedy:
|
| A08753 CAN: Message buffer overflow | Cause: A message buffer overflow. Alarm value (r2124, interpret decimal): 1: Non-cyclic send buffer (SDO response buffer) overflow. 2: Non-cyclic receive buffer (SDO receive buffer) overflow. 3: Cyclic send buffer (PDO send buffer) overflow. Remedy:
|
| A08754 CAN: Incorrect communications mode | Cause: In the ‘operational’ mode, an attempt was made to change parameters p8700 … p8737. Remedy: Change to the ‘pre-operational’ or ‘stopped’ mode. |
| A08755 CAN: Obj cannot be mapped | Cause: The CANopen object is not provided for the Process Data Object (PDO) Mapping. Remedy: Use a CANopen object intended for the PDO mapping or enter 0. The list of mappable objects is provided in the manual. |
| A08756 CAN: Number of mapped bytes exceeded | Cause: The number of bytes of the mapped objects exceeds the telegram size for net data. A max. of 8 bytes is permissible. Remedy: Map fewer objects or objects with a smaller data type. |
| A08757 CAN: Set COB-ID invalid | Cause: For online operation, the appropriate COB-ID must be set invalid before mapping. Remedy: Set the COB-ID to invalid. Example: set p8700[0] = C00006E0 hex (invalid COB-ID), set p8710[0] as required, then enter a valid COB-ID for p8700[0]. |
| A08759 CAN: PDO COB-ID already available | Cause: An existing PDO COB-ID was allocated. Remedy: Select another PDO COB-ID. |
| A08760 CAN: maximum size of the PZD IF exceeded | Cause: The maximum size of the PZD interface exceeded. Fault value 1: receiving, Fault value 2: sending Remedy: Deleting the alarm:
|
| A08800 PROFlenergy energy-saving mode active | Cause: The PROFlenergy energy-saving mode is active. Alarm value (r2124, interpret decimal): Mode ID of the active PROFlenergy energy-saving mode. Remedy: The alarm automatically disappears when the energy-saving mode is exited. |
| A08802 PROFlenergy not possible to switch off incremental encoder supply | Cause: The incremental encoder is used for the closed-loop position control. This means that its power supply cannot be switched off during the PROFlenergy energy-saving mode, otherwise it would lose its position actual value. Alarm value (r2124, interpret decimal): Encoder number Remedy: The alarm automatically disappears when the energy-saving mode is exited. |
| F13009 Licensing OA application not licensed | Cause: At least one OA application which is under license does not have a license. Remedy:
|
| F13100 Know-how protection: Copy protection error | Cause: The know-how protection with copy protection for the memory card is active. An error has occurred when checking the memory card. Fault value (r0949, interpret decimal):
Remedy: Re fault value = 0, 1: Insert the correct memory card and carry out POWER ON. Re fault value = 2, 3, 12, 13:
|
| F13101 Know-how protection: Copy protection cannot be activated | Cause: An error occurred when attempting to activate the copy protection for the memory card. Fault value (r0949, interpret decimal):
Remedy:
|
| F13102 Know-how protection: Consistency error of the protected data | Cause: An error was identified when checking the consistency of the protected files. As a consequence, the project on the memory card cannot be run. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex: yyyy = object number, xxxx = fault cause. xxxx = 1: A file has a checksum error. xxxx = 2: The files are not consistent with one another. xxxx = 3: The project files are inconsistent. Remedy:
|
| F30001 Power unit: Overcurrent | Cause: The power unit has detected an overcurrent condition.
Remedy:
|
| F30002 Power unit: DC link voltage overvoltage | Cause: The power unit has detected an overvoltage condition in the DC link.
Remedy:
|
| F30003 Power unit: DC link voltage undervoltage | Cause: The power unit has detected an undervoltage condition in the DC link.
Remedy:
|
| F30004 Power unit: Overtemperature heat sink AC inverter | Cause: The temperature of the power unit heat sink has exceeded the permissible limit value.
Remedy:
|
| F30005 Power unit: Overload I2t | Cause: The power unit was overloaded (r0036 = 100%).
Remedy:
|
| F30011 Power unit: Line phase failure in main circuit | Cause: At the power unit, the DC link voltage ripple has exceeded the permissible limit value. Possible causes:
Remedy:
|
| F30012 Power unit: Temperature sensor heat sink wire breakage | Cause: The connection to a heat sink temperature sensor in the power unit is interrupted. Remedy: Contact the manufacturer. |
| F30013 Power unit: Temperature sensor heat sink short-circuit | Cause: The heat sink temperature sensor in the power unit is short-circuited. Remedy: Contact the manufacturer. |
| F30015 (N, A) Power unit: Phase failure motor cable | Cause: A phase failure in the motor feeder cable was detected. The signal can also be output in the following cases:
Remedy:
|
| A30016 (N) Power unit: Load supply switched out | Cause: The DC link voltage is too low. Alarm value (r2124, interpret decimal): DC link voltage at the time of trip [0.1 V]. Remedy: Under certain circumstances, the AC line supply is not switched on. |
| F30017 Power unit: Hardware current limit has responded too often | Cause: The hardware current limitation in the relevant phase has responded too often.
Remedy:
|
| F30021 Power unit: Ground fault | Cause: Power unit has detected a ground fault.
Remedy:
|
| F30022 Power unit: Monitoring U_ce | Cause: In the power unit, the monitoring of the collector-emitter voltage (U_ce) of the semiconductor has responded. Possible causes:
Remedy:
|
| F30024 Power unit: Overtemperature thermal model | Cause: The temperature difference between the heat sink and chip has exceeded the permissible limit value.
Remedy:
|
| F30025 Power unit: Chip overtemperature | Cause: The chip temperature of the semiconductor has exceeded the permissible limit value.
Remedy:
|
| F30027 Power unit: Precharging DC link time monitoring | Cause: The power unit DC link was not able to be pre-charged within the expected time.
Remedy: In general:
Re 6): check the capacitance of the DC link. Re 7): check the DC link for a ground fault or short circuit. |
| A30030 Power unit: Internal overtemperature alarm | Cause: The temperature inside the converter has exceeded the permissible limit value of the alarm threshold.
Remedy:
|
| A30031 Power unit: Hardware current limiting in phase U | Cause: Hardware current limit for phase U responded. The pulsing in this phase is inhibited for one pulse period.
Remedy:
|
| A30032 Power unit: Hardware current limiting in phase V | Cause: Hardware current limit for phase V responded. The pulsing in this phase is inhibited for one pulse period.
Remedy:
|
| A30033 Power unit: Hardware current limiting in phase W | Cause: Hardware current limit for phase W responded. The pulsing in this phase is inhibited for one pulse period.
Remedy:
|
| A30034 Power unit: Internal overtemperature | Cause: The alarm threshold for internal overtemperature has been reached. If the temperature inside the unit continues to increase, fault F30036 may be triggered.
Remedy:
|
| F30035 Power unit: Air intake overtemperature | Cause: The air intake in the power unit has exceeded the permissible temperature limit. For air-cooled power units, the temperature limit is at 55 °C.
Remedy:
|
| F30036 Power unit: Internal overtemperature | Cause: The temperature inside the drive converter has exceeded the permissible temperature limit.
Remedy:
|
| F30037 Power unit: Rectifier overtemperature | Cause: The temperature in the rectifier of the power unit has exceeded the permissible temperature limit.
Remedy:
|
| A30042 Power unit: Fan has reached the maximum operating hours | Cause: The maximum operating time of at least one fan will soon be reached, or has already been exceeded. Fault value (r0949, interpret binary):
Remedy: For the fan involved, carry out the following:
|
| A30049 Power unit: Internal fan faulty | Cause: The internal fan has failed. Remedy: Check the internal fan and replace if necessary. |
| F30052 EEPROM data error | Cause: EEPROM data error of the power unit module. Fault value (r0949, interpret decimal):
Remedy: Replace power unit module. |
| A30054 (F) Power unit: Undervoltage when opening the brake | Cause: When the brake is being opened, it is detected that the power supply voltage is less than 24 V – 10% = 21.6V. Alarm value (r2124, interpret decimal): Supply voltage fault [0.1 V]. Remedy: Check the 24 V voltage for stability and value. |
| F30055 Power unit: Braking chopper overcurrent | Cause: An overcurrent condition has occurred in the braking chopper.
Remedy: The braking chopper is only enabled again at pulse enable after the fault has been acknowledged. |
| A30057 Power unit: Line asymmetry | Cause: Frequencies have been detected on the DC link voltage that would suggest line asymmetry or failure of a line phase. It is also possible that a motor phase has failed. Fault F30011 is output if the alarm is present and at the latest after 5 minutes. Remedy:
|
| F30059 Power unit: Internal fan faulty | Cause: The internal power unit fan has failed and is possibly defective. Remedy: Check the internal fan and replace if necessary. |
| F30071 No new actual values received from the Power Module | Cause: More than one actual value telegram from the power unit module has failed. Remedy: Check the interface (adjustment and locking) to the power unit module. |
| F30072 Setpoints can no longer be transferred to the Power Module | Cause: More than one setpoint telegram was not able to be transferred to the power unit module. Remedy: Check the interface (adjustment and locking) to the power unit module. |
| F30074 (A) Communication error between the Control Unit and Power Module | Cause: Communications between the Control Unit (CU) and Power Module (PM) via the interface no longer possible. The CU may have been withdrawn or is incorrectly inserted. Fault value (r0949, interpret hexadecimal):
Remedy: For fault value = 0 and 20A hex: Insert the Control Unit on an appropriate Power Module and continue operation. If required, carry out a POWER ON of the Control Unit. For fault value = 1 hex: Carry out a POWER ON of the Control Unit. |
| F30080 Power unit: Current increasing too quickly | Cause: The power unit has detected an excessive rate of rise in the overvoltage range.
Remedy:
|
| F30081 Power unit: Switching operations too frequent | Cause: The power unit has executed too many switching operations for current limitation.
Remedy:
|
| F30105 PU: Actual value sensing fault | Cause: At least one incorrect actual value channel was detected on the Power Stack Adapter (PSA). The incorrect actual value channels are displayed in the following diagnostic parameters. Remedy: Evaluate the diagnostic parameters. If the actual value channel is incorrect, check the components and if required, replace. |
| A30502 Power unit: DC link overvoltage | Cause: The power unit has detected overvoltage in the DC link on a pulse inhibit.
Remedy:
|
| F30600 SI P2: STOP A initiated | Cause: The drive-integrated ‘Safety Integrated’ function on processor 2 has detected an error and initiated a STOP A.
Remedy:
|
| F30611 (A) SI P2: Defect in a monitoring channel | Cause: The drive-integrated ‘Safety Integrated’ function on processor 2 has detected a fault in the crosswise data comparison between the two monitoring channels and has initiated a STOP F. As a consequence of this fault, fault F30600 is output. Fault value (r0949, interpret decimal): Indicates the specific cross-compared data that resulted in this fault, including various PROFIsafe errors. Remedy: Remedy is dependent on the fault value. General remedies include:
|
| N30620 (F, A) SI P2: Safe Torque Off active | Cause: The ‘Safe Torque Off’ (STO) function has been selected on processor 2 using the input terminal and is active. This message does not result in a safety stop response. Remedy: Not necessary. |
| F30625 SI P2: Sign-of-life error in safety data | Cause: The drive-integrated ‘Safety Integrated’ function on processor 2 has detected an error in the sign-of-life of the safety data and initiated a STOP A.
Remedy:
|
| F30649 SI P2: Internal software error | Cause: An internal error in the Safety Integrated software on processor 2 has occurred. This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| F30650 SI P2: Acceptance test required | Cause: The drive-integrated ‘Safety Integrated’ function on processor 2 requires an acceptance test. This fault results in a STOP A that can be acknowledged. Fault value (r0949, interpret decimal): Indicates the reason for the test, such as first-time commissioning, checksum mismatch, or safety parameter change. Remedy: Remedy depends on the fault value:
|
| F30651 SI P2: Synchronization with Control Unit unsuccessful | Cause: The drive-integrated ‘Safety Integrated’ function requires synchronization of the safety time slices on processor 1 and processor 2. This synchronization was unsuccessful. This fault results in a STOP A that cannot be acknowledged. Remedy: carry out a POWER ON (power off/on). |
| F30655 SI P2: Align monitoring functions | Cause: An error has occurred when aligning the Safety Integrated monitoring functions on processor 1 and processor 2. No common set of supported SI monitoring functions was able to be determined.
Remedy:
|
| F30656 SI P2: Parameter processor 2 parameter error | Cause: When accessing the Safety Integrated parameters for the processor 2 in the non-volatile memory, an error has occurred. This fault results in a STOP A that can be acknowledged. Fault value (r0949, interpret decimal):
Remedy:
|
| F30659 SI P2: Write request for parameter rejected | Cause: The write request for one or several Safety Integrated parameters on processor 2 was rejected. This fault does not result in a safety stop response. Fault value (r0949, interpret decimal): Indicates attempts to enable unsupported functions (STO, motion monitoring, PROFIsafe). Remedy:
|
| F30662 Error in internal communications | Cause: A module-internal communication error has occurred. Remedy:
|
| F30664 Error while booting | Cause: An error has occurred during booting. Remedy:
|
| F30665 SI P2: System is defective | Cause: A system defect was detected before the last boot or in the actual one. The system might have been rebooted (reset). Fault value (r0949, interpret hexadecimal):
Remedy:
|
| A30666 (F) SI Motion P2: Steady-state (static) 1 signal at the F-DI for safety-relevant acknowledgement | Cause: A logical 1 signal is present at the F-DI configured in p10106 for more than 10 seconds. If no acknowledgment was performed, a steady-state logical 0 signal must be present to avoid unintentional acknowledgement. Remedy: Set the fail-safe digital input (F-DI) to a logical 0 signal (p10106). |
| F30680 SI Motion P2: Checksum error safety monitoring functions | Cause: The actual checksum calculated by processor 2 and entered in r9398 over the safety-relevant parameters does not match the reference checksum saved in p9399 at the last machine acceptance. Safety-relevant parameters have been changed or a fault is present. Remedy:
|
| F30681 SI Motion P2: Incorrect parameter value | Cause: The parameter cannot be parameterized with this value. Fault value (r0949, interpret decimal):
Remedy: Correct the parameter value. Note: For different values in the two monitoring channels, start the copy function for SI parameters on the drive (p9700 = 57 hex). |
| F30682 SI Motion P2: Monitoring function not supported | Cause: The monitoring function enabled in p9301, p9501, p9601 or p9801 is not supported in this firmware version. This message does not result in a safety stop response. Fault value (r0949, interpret decimal): Lists various unsupported monitoring functions like SLP, SCA, SLS override, etc. Remedy: Deselect the monitoring function involved. |
| F30683 SI Motion P2: SLS enable missing | Cause: The safety-relevant function ‘SLS’ is not enabled in p9301 although other safety-relevant monitoring functions are enabled. This message does not result in a safety stop response. Remedy: Enable the function ‘SLS’ (p9301.0) and carry out a POWER ON. Note: Save the changes before POWER ON (copy from RAM to ROM). |
| F30692 SI Motion P2: Incorrect parameter value encoderless | Cause: For encoderless motion monitoring functions, the parameter cannot be parameterized with this value. This message does not result in a safety stop response. Fault value (r0949, interpret decimal): Parameter number with the incorrect value. Remedy: Correct the parameter specified in the fault value. |
| A30693 (F) SI P2: Safety parameter settings changed, POWER ON required | Cause: Safety parameters have been changed; these will only take effect following a POWER ON. Alarm value (r2124, interpret decimal): Parameter number of the safety parameter which has changed, necessitating a POWER ON. Remedy:
|
| C30700 SI Motion P2: STOP A initiated | Cause: The drive is stopped via a STOP A (pulses are suppressed via the safety shutdown path of processor 1). Possible causes:
Remedy:
|
| C30701 SI Motion P2: STOP B initiated | Cause: The drive is stopped via a STOP B (braking along the OFF3 deceleration ramp). As a result of this fault, after the speed threshold is fallen below, message C30700 ‘STOP A initiated’ is output. Possible causes:
Remedy:
|
| C30706 SI Motion P2: SAM/SBR limit exceeded | Cause: Motion monitoring functions with set acceleration monitoring (SAM, p9306 = 3) or brake ramp monitoring (SBR, p9306 = 1) have exceeded the selected tolerance after initiating STOP B (SS1) or SLS changeover. The drive is shut down by message C30700 ‘SI Motion P2: STOP A initiated’. Remedy: Check the braking behavior and, if necessary, adapt the parameterization of the ‘SAM’ or the ‘SBR’ function. This message can be acknowledged without a POWER ON as follows: motion monitoring functions integrated in the drive: via F-DI or PROFIsafe. |
| C30711 SI Motion P2: Defect in a monitoring channel | Cause: When cross-comparing the two monitoring channels, the drive detected a difference between the input data or results and initiated a STOP F. One of the monitoring functions no longer reliably functions. Message value (r2124, interpret decimal): Number of the cross-compared data that resulted in this message. The significance of the individual message values is described in safety message C01711. Remedy: Remedy depends on the message value.
|
| C30712 SI Motion P2: Defect in F-IO processing | Cause: When cross checking and comparing the two monitoring channels, the drive detected a difference between parameters or results of the F-IO processing and initiated a STOP F. One of the monitoring functions no longer reliably functions. Message value (r2124, interpret decimal): See safety message C01712 for a description of the message values. Remedy:
|
| C30714 SI Motion P2: Safely-Limited Speed exceeded | Cause: The drive had moved faster than that specified by the velocity limit value (p9331). The drive is stopped as a result of the configured stop response (p9363). Message value (r2124, interpret decimal): 100: SLS1 exceeded, 200: SLS2 exceeded, etc. Remedy:
|
| C30716 SI Motion P2: Tolerance for safe motion direction exceeded | Cause: The tolerance for the ‘safe motion direction’ function was exceeded. The drive is stopped as a result of the configured stop response (p9366). Message value (r9749, interpret decimal): 0: Tolerance for the ‘safe motion direction positive’ function exceeded. 1: Tolerance for the ‘safe motion direction negative’ function exceeded. Remedy:
|
| C30770 SI Motion P2: Discrepancy error affecting the failsafe inputs | Cause: The fail-safe digital inputs (F-DI) show a different state longer than that parameterized in p10002 / p10102. Fault value (r0949, interpret binary): Bit 0: Discrepancy error for F-DI 0, Bit 1: Discrepancy error for F-DI 1. Remedy: check the wiring of the F-DI (contact problems). Note: This message can be acknowledged via F-DI or PROFIsafe. Discrepancy errors of an F-DI can only be completely acknowledged if safe acknowledgement was carried out once the cause of the error was resolved. For cyclic switching operations, it may be necessary to adapt the discrepancy time. |
| C30798 SI Motion P2: Test stop running | Cause: The test stop is active. Remedy: Not necessary. The message is withdrawn when the test stop is finished. |
| C30799 SI Motion P2: Acceptance test mode active | Cause: The acceptance test mode is active. Remedy: Not necessary. The message is withdrawn when exiting the acceptance test mode. |
| N30800 (F) Power unit: Group signal | Cause: The power unit has detected at least one fault. Remedy: Evaluate the other messages that are presently available. |
| F30802 Power unit: Time slice overflow | Cause: A time slice overflow has occurred. Remedy:
|
| F30804 (N, A) Power unit: CRC | Cause: A CRC error has occurred for the power unit. Remedy:
|
| F30805 Power unit: EPROM checksum error | Cause: Internal parameter data is corrupted. Fault value (r0949, interpret hexadecimal):
Remedy: Replace the module. |
| F30809 Power unit: Switching information not valid | Cause: For 3P gating unit, the following applies: The last switching status word in the setpoint telegram is identified by the end ID. Such an end ID was not found. Remedy:
|
| A30810 (F) Power unit: Watchdog timer | Cause: When booting it was detected that the cause of the previous reset was an SAC watchdog timer overflow. Remedy:
|
| F30850 Power unit: Internal software error | Cause: An internal software error has occurred in the power unit. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| F30875 Power unit DRIVE-CLIQ (CU): Supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage has failed. Fault cause: 9 (= 09 hex): The power supply voltage for the components has failed. Remedy:
|
| F30903 Power unit: I2C bus error occurred | Cause: Communications error with an EEPROM or A/D converter. Fault value (r0949, interpret hexadecimal):
Remedy: Re fault value = 80000000 hex:
|
| A30920 (F) Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal):
Remedy:
|
| F30950 Power unit: Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Information about the fault source. Only for internal Siemens troubleshooting. Remedy:
|
| A30999 (F, N) Power unit: Unknown alarm | Cause: An alarm occurred on the power unit that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Alarm value (r2124, interpret decimal): Alarm number. Remedy:
|
| F31152 (N, A) Encoder 1: Maximum input frequency exceeded | Cause: The maximum input frequency of the encoder evaluation has been exceeded. Fault value (r0949, interpret decimal): Actual input frequency in Hz. Remedy:
|
| F31160 (N, A) Encoder 1: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Fault value (r0949, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside the measuring range set in (p4673). 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy: For fault value = 1: check the output voltage of the analog sensor. For fault value = 2: check the voltage setting for each encoder period (p4673). For fault value = 3: check the range limit setting and increase it if necessary (p4676). |
| F31161 (N, A) Encoder 1: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Fault value (r0949, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside the measuring range set in (p4675). 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy: For fault value = 1: check the output voltage of the analog sensor. For fault value = 2: check the voltage setting for each encoder period (p4675). For fault value = 3: check the range limit setting and increase it if necessary (p4676). |
| F31163 (N, A) Encoder 1: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Fault value (r0949, interpret decimal): 1: Position value from the LVDT sensor. 2: Position value from the encoder characteristic. Remedy: For fault value = 1: Check the LVDT ratio (p4678) and reference signal connection at track B. For fault value = 2: check the coefficients of the characteristic (p4663 … p4666). |
| A31442 (F, N) Encoder 1: Battery voltage pre-alarm | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The battery voltage is no longer sufficient. Remedy: Replace battery. |
| A31460 (N) Encoder 1: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Alarm value (r2124, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside measuring range set in p4673. 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy: Re alarm value = 1: check the output voltage of the analog sensor. Re alarm value = 2: check the voltage setting for each encoder period (p4673). Re alarm value = 3: check the range limit setting and increase it if necessary (p4676). |
| A31461 (N) Encoder 1: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Alarm value (r2124, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside the measuring range set in (p4675). 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy: Re alarm value = 1: check the output voltage of the analog sensor. Re alarm value = 2: check the voltage setting for each encoder period (p4675). Re alarm value = 3: check the range limit setting and increase it if necessary (p4676). |
| A31462 (N) Encoder 1: Analog sensor no channel active | Cause: Channel A and B are not activated for the analog sensor. Remedy:
|
| A31463 (N) Encoder 1: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Alarm value (r2124, interpret decimal): 1: Position value from the LVDT sensor. 2: Position value from the encoder characteristic. Remedy: Re alarm value = 1: Check the LVDT ratio (p4678) and reference signal connection. Re alarm value = 2: check the coefficients of the characteristic (p4663 … p4666). |
| A31470 (F, N) Encoder 1: Soiling detected | Cause: In the case of the alternative encoder system interface on the Sensor Module Cabinet 30 (SMC30), encoder soiling is signaled via a 0 signal at terminal X521.7. Remedy:
|
| F31912 Encoder 1: Device combination is not permissible | Cause: The selected device combination is not supported. Fault value (r0949, interpret decimal): 1003: The connected measuring unit cannot be operated with the EnDat 2.2 converter (e.g., pulse number of 2^n). 1005: The type of measuring unit (incremental) is not supported. 1006: The maximum duration (31.25 µs) of the EnDat transfer was exceeded. 2001: The set combination of cycle times is not supported. 2002: The resolution of the linear measuring unit does not match the pole pair width of the linear motor. Remedy: Re fault value = 1003, 1005, 1006: Use a measuring unit that is permissible. For fault value = 2001: Set a permissible cycle combination. For fault value = 2002: Use a measuring unit with a lower resolution (p0422). |
| A31915 (F, N) Encoder 1: Configuration error | Cause: The configuration for encoder 1 is incorrect. Alarm value (r2124, interpret decimal): 1: Re-parameterization between fault/alarm is not permissible. 419: When the fine resolution Gx_XIST2 is configured, the encoder identifies a maximum possible absolute position actual value (r0483) that can no longer be represented within 32 bits. Remedy: Re alarm value = 1: No re-parameterization between fault/alarm. Re alarm value = 419: Reduce the fine resolution (p0419) or deactivate the monitoring (p0437.25), if the complete multiturn range is not required. |
| A31930 (N) Encoder 1: Data logger has saved data | Cause: For the activated function ‘Data logger’ (p0437.0 = 1) a fault has occurred with the Sensor Module. This alarm indicates that the diagnostics data corresponding to the fault was saved on the memory card. Remedy: Not necessary. The alarm disappears automatically. The data logger is ready to record the next fault case. |
| A31940 (F, N) Encoder 1: Spindle sensor S1 voltage incorrect | Cause: The voltage of analog sensor S1 is outside the permissible range. Fault value (r0949, interpret decimal): Signal level from sensor S1. Remedy: Check the clamped tool. Check the tolerance and if required, adapt (p5040). Check the thresholds and if required, adapt (p5041). Check analog sensor S1 and connections. |
| F32152 (N, A) Encoder 2: Maximum input frequency exceeded | Cause: The maximum input frequency of the encoder evaluation has been exceeded. Fault value (r0949, interpret decimal): Actual input frequency in Hz. Remedy:
|
| F32160 (N, A) Encoder 2: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Fault value (r0949, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside the measuring range set in (p4673). 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy: For fault value = 1: check the output voltage of the analog sensor. For fault value = 2: check the voltage setting for each encoder period (p4673). For fault value = 3: check the range limit setting and increase it if necessary (p4676). |
| F32161 (N, A) Encoder 2: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Fault value (r0949, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside the measuring range set in (p4675). 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy: For fault value = 1: check the output voltage of the analog sensor. For fault value = 2: check the voltage setting for each encoder period (p4675). For fault value = 3: check the range limit setting and increase it if necessary (p4676). |
| F32163 (N, A) Encoder 2: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Fault value (r0949, interpret decimal): 1: Position value from the LVDT sensor. 2: Position value from the encoder characteristic. Remedy: For fault value = 1: Check the LVDT ratio (p4678) and check the reference signal connection at track B. For fault value = 2: check the coefficients of the characteristic (p4663 … p4666). |
| A32442 (F, N) Encoder 2: Battery voltage pre-alarm | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The battery voltage is no longer sufficient to check the multiturn information. Remedy: Replace battery. |
| A32460 (N) Encoder 2: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Alarm value (r2124, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside measuring range set in p4673. 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy: Re alarm value = 1: check the output voltage of the analog sensor. Re alarm value = 2: check the voltage setting for each encoder period (p4673). Re alarm value = 3: check the range limit setting and increase it if necessary (p4676). |
| A32461 (N) Encoder 2: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Alarm value (r2124, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside the measuring range set in (p4675). 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy: Re alarm value = 1: check the output voltage of the analog sensor. Re alarm value = 2: check the voltage setting for each encoder period (p4675). Re alarm value = 3: check the range limit setting and increase it if necessary (p4676). |
| A32462 (N) Encoder 2: Analog sensor no channel active | Cause: Channel A and B are not activated for the analog sensor. Remedy:
|
| A32463 (N) Encoder 2: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Alarm value (r2124, interpret decimal): 1: Position value from the LVDT sensor. 2: Position value from the encoder characteristic. Remedy: Re alarm value = 1: Check the LVDT ratio (p4678) and the reference signal connection at track B. Re alarm value = 2: check the coefficients of the characteristic (p4663 … p4666). |
| A32470 (F, N) Encoder 2: Soiling detected | Cause: In the case of the alternative encoder system interface on the Sensor Module Cabinet 30 (SMC30), encoder soiling is signaled via a 0 signal at terminal X521.7. Remedy:
|
| F32912 Encoder 2: Device combination is not permissible | Cause: The selected device combination is not supported. Fault value (r0949, interpret decimal): 1003: The connected measuring unit cannot be operated with the EnDat 2.2 converter. 1005: The type of measuring unit (incremental) is not supported. 1006: The maximum duration (31.25 µs) of the EnDat transfer was exceeded. 2001: The set combination of current controller cycle, DP cycle and Safety cycle is not supported. 2002: The resolution of the linear measuring unit does not match the pole pair width of the linear motor. Remedy: Re fault value = 1003, 1005, 1006: Use a measuring unit that is permissible. For fault value = 2001: Set a permissible cycle combination. For fault value = 2002: Use a measuring unit with a lower resolution (p0422). |
| A32915 (F, N) Encoder 2: Configuration error | Cause: The configuration for encoder 2 is incorrect. Alarm value (r2124, interpret decimal): 1: Re-parameterization between fault/alarm is not permissible. 419: When the fine resolution Gx_XIST2 is configured, the encoder identifies a maximum possible absolute position actual value (r0483) that can no longer be represented within 32 bits. Remedy: Re alarm value = 1: No re-parameterization between fault/alarm. Re alarm value = 419: Reduce the fine resolution (p0419) or deactivate the monitoring (p0437.25), if the complete multiturn range is not required. |
| A32930 (N) Encoder 2: Data logger has saved data | Cause: For the activated function ‘Data logger’ (p0437.0 = 1) a fault has occurred with the Sensor Module. This alarm indicates that the diagnostics data corresponding to the fault was saved on the memory card. Remedy: Not necessary. The alarm disappears automatically. The data logger is ready to record the next fault case. |
| A32940 (F, N) Encoder 2: Spindle sensor S1 voltage incorrect | Cause: The voltage of analog sensor S1 is outside the permissible range. Fault value (r0949, interpret decimal): Signal level from sensor S1. Remedy:
|
| F33152 (N, A) Encoder 3: Maximum input frequency exceeded | Cause: The maximum input frequency of the encoder evaluation has been exceeded. Fault value (r0949, interpret decimal): Actual input frequency in Hz. Remedy:
|
| F33160 (N, A) Encoder 3: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Fault value (r0949, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside the measuring range set in (p4673). 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy: For fault value = 1: check the output voltage of the analog sensor. For fault value = 2: check the voltage setting for each encoder period (p4673). For fault value = 3: check the range limit setting and increase it if necessary (p4676). |
| F33161 (N, A) Encoder 3: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Fault value (r0949, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside the measuring range set in (p4675). 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy: For fault value = 1: check the output voltage of the analog sensor. For fault value = 2: check the voltage setting for each encoder period (p4675). |
| F33163 (N, A) Encoder 3: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Fault value (r0949, interpret decimal): 1: Position value from the LVDT sensor. 2: Position value from the encoder characteristic. Remedy: For fault value = 1: Check the LVDT ratio (p4678) and check the reference signal connection at track B. For fault value = 2: check the coefficients of the characteristic (p4663 … p4666). |
| A33442 (F, N) Encoder 3: Battery voltage pre-alarm | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The battery voltage is no longer sufficient to check the multiturn information. Remedy: Replace battery. |
| A33460 (N) Encoder 3: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Alarm value (r2124, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside measuring range set in p4673. 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy: Re alarm value = 1: check the output voltage of the analog sensor. Re alarm value = 2: check the voltage setting for each encoder period (p4673). Re alarm value = 3: check the range limit setting and increase it if necessary (p4676). |
| A33461 (N) Encoder 3: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Alarm value (r2124, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside the measuring range set in (p4675). 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy: Re alarm value = 1: check the output voltage of the analog sensor. Re alarm value = 2: check the voltage setting for each encoder period (p4675). Re alarm value = 3: check the range limit setting and increase it if necessary (p4676). |
| A33462 (N) Encoder 3: Analog sensor no channel active | Cause: Channel A and B are not activated for the analog sensor. Remedy:
|
| A33463 (N) Encoder 3: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Alarm value (r2124, interpret decimal): 1: Position value from the LVDT sensor. 2: Position value from the encoder characteristic. Remedy: Re alarm value = 1: Check the LVDT ratio (p4678) and check the reference signal connection at track B. Re alarm value = 2: check the coefficients of the characteristic (p4663 … p4666). |
| A33470 (F, N) Encoder 3: Soiling detected | Cause: In the case of the alternative encoder system interface on the Sensor Module Cabinet 30 (SMC30), encoder soiling is signaled via a 0 signal at terminal X521.7. Remedy:
|
| F33912 Encoder 3: Device combination is not permissible | Cause: The selected device combination is not supported. Fault value (r0949, interpret decimal): 1003: The connected measuring unit cannot be operated with the EnDat 2.2 converter. 1005: The type of measuring unit (incremental) is not supported. 1006: The maximum duration (31.25 µs) of the EnDat transfer was exceeded. 2001: The set combination of cycle times is not supported. 2002: The resolution of the linear measuring unit does not match the pole pair width of the linear motor. Remedy: Re fault value = 1003, 1005, 1006: Use a measuring unit that is permissible. For fault value = 2001: Set a permissible cycle combination. For fault value = 2002: Use a measuring unit with a lower resolution (p0422). |
| A33915 (F, N) Encoder 3: Configuration error | Cause: The configuration for encoder 3 is incorrect. Alarm value (r2124, interpret decimal): 1: Re-parameterization between fault/alarm is not permissible. 419: When the fine resolution Gx_XIST2 is configured, the encoder identifies a maximum possible absolute position actual value (r0483) that can no longer be represented within 32 bits. Remedy: Re alarm value = 1: No re-parameterization between fault/alarm. Re alarm value = 419: Reduce the fine resolution (p0419) or deactivate the monitoring (p0437.25), if the complete multiturn range is not required. |
| A33930 (N) Encoder 3: Data logger has saved data | Cause: For the activated function ‘Data logger’ (p0437.0 = 1) a fault has occurred with the Sensor Module. This alarm indicates that the diagnostics data corresponding to the fault was saved on the memory card. Remedy: Not necessary. The alarm disappears automatically. The data logger is ready to record the next fault case. |
| A33940 (F, N) Encoder 3: Spindle sensor S1 voltage incorrect | Cause: The voltage of analog sensor S1 is outside the permissible range. Fault value (r0949, interpret decimal): Signal level from sensor S1. Remedy:
|
| F34950 VSM: Internal software error | Cause: An internal software error in the Voltage Sensing Module (VSM) has occurred. Fault value (r0949, interpret decimal): Information about the fault source. Only for internal Siemens troubleshooting. Remedy:
|
| F35950 TM: Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Information about the fault source. Only for internal Siemens troubleshooting. Remedy:
|
| F36950 Hub: Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Information about the fault source. Only for internal Siemens troubleshooting. Remedy:
|
| A50001 (F) PROFINET configuration error | Cause: A PROFINET controller attempts to establish a connection using an incorrect configuring telegram. The ‘Shared Device’ function has been activated (p8929 = 2). Alarm value (r2124, interpret decimal):
Remedy: Check the configuration of the PROFINET controllers as well as the p8929 setting. |
| A50010 (F) PROFINET Name of Station invalid | Cause: PROFINET Name of Station is invalid. Remedy: Correct the name of the station (p8920) and activate (p8925 = 2). |
| A50020 (F) PROFINET: Second controller missing | Cause: The PROFINET function ‘Shared Device’ has been activated (p8929 = 2). However, only the connection to a PROFINET controller is present. Remedy: Check the configuration of the PROFINET controllers as well as the p8929 setting. |
| F50510 FBLOCKS: Logon of the run-time group rejected | Cause: When the run-time groups of the free function blocks attempted to log on with the sampling time management, the logon of at least one run-time group was rejected. Too many different hardware sampling times may have been assigned to the free function blocks. Remedy: Check number of available hardware sampling times (T_sample < 8 ms) (r7903). |
| F50511 FBLOCKS: Memory no longer available for free function blocks | Cause: When the free function blocks were activated, more memory was requested than was available on the Control Unit. Remedy: Not necessary. |
| A50513 (F) FBLOCKS: Run sequence value already assigned | Cause: An attempt was made to assign a run sequence value already assigned to a function block on this drive object to another additional function block on the same drive object. A run sequence value can only be precisely assigned to one function block on one drive object. Remedy: Set another value that is still available on this drive object for the run sequence. |
| A50517 FBLOCKS: Int. meas. active | Cause: A Siemens internal measurement has been activated. Remedy: Carry out a POWER ON (power off/on) for the Control Unit involved. |
| F50518 FBLOCKS: Sampling time of free run-time group differs at download | Cause: In the STARTER/SCOUT project that was downloaded, the hardware sampling time of a free run-time group (1 <= p20000[i] <= 256) was set to a value that was either too low or too high. The sampling time must be between 1 ms and the value r20003 - r20002. Remedy:
|
How to Read G120 Faults via IOP-2 & Startdrive
Siemens provides multiple layers of diagnostics. In 2026, troubleshooting usually moves away from the basic LED blink codes to text-based analysis:
- Intelligent Operator Panel (IOP-2): Unlike the basic BOP-2, the IOP-2 features a high-resolution color screen. When a fault occurs (e.g., F30001), pressing the INFO or HELP button provides a full text description and a list of possible causes directly on the screen.
- Startdrive (TIA Portal): Connect your PC via PROFINET (Ethernet) or USB. The “Diagnostics” buffer in TIA Portal is the most powerful tool available. It allows you to:
- View the Fault History (last 64 events) with Real-Time Clock stamps.
- Use the Trace Function to record motor current and DC bus voltage milliseconds before a trip to catch intermittent spikes.
- Smart Access Module (SAM): The G120 now supports a Wi-Fi module (G120 Smart Access). This allows you to view faults and check parameters wirelessly using your smartphone or tablet, which is ideal for drives mounted in hard-to-reach areas.
Frequently Asked Questions (FAQ)
Q: What is the difference between a Fault (F) and an Alarm (A)?
A:
- Fault (Fxxxxx, e.g., F07860): The drive trips immediately. The motor coasts to a stop or brakes. You must acknowledge (reset) the fault to restart.
- Alarm (Axxxxx, e.g., A07400): The drive continues to run, but a limit has been reached (e.g., DC Link Voltage High). If the condition persists, it may turn into a Fault.
Q: How do I reset a Siemens G120 fault?
A:
- Keypad: Press the FN (Function) or OK button on the BOP-2/IOP-2.
- Digital Input: Pulse the input configured as “Acknowledge Fault” (p2103).
- Fieldbus: Send the acknowledgment bit (Bit 7 of Control Word 1) via PROFINET or PROFIBUS.
- Safety Faults: For STO faults (F01600), you may need to cycle the 24V safety power or perform a specific “Safe Reset” procedure.
Q: Why do I get “F30001” (Overcurrent) on startup?
A: F30001 is the most common hardware trip.
- Check the motor data in Quick Commissioning (Motor ID) to ensure it matches the nameplate.
- Check for a short circuit in the motor cable or a ground fault.
- If the load is high inertia, increase the Ramp-Up Time (p1120).