Siemens G120D Drive Fault Codes:
| 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 FloatingPoint exception | Cause: An exception occurred for an operation with the FloatingPoint data type. The error may be caused by the basic system or an OA application (e.g. FBLOCKS, DCC). Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. See r9999 for further info. Bit 0 = 1: Operation invalid Bit 1 = 1: Division by zero Bit 2 = 1: Overflow Bit 3 = 1: Underflow Bit 4 = 1: Inaccurate result Remedy:
|
| F01002 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01003 Acknowledgment 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 xxxx = 000B hex = 11 dec: Power unit component has detected a checksum error. xxxx = 000F hex = 15 dec: The selected power unit will not accept the content of the EEPROM file. xxxx = 0011 hex = 17 dec: Power unit component has detected an internal access error. xxxx = 0012 hex = 18 dec: After several communication attempts, no response from the power unit component. xxxx = 008B hex = 140 dec: EEPROM file for the power unit component not available on the memory card. xxxx = 008D hex = 141 dec: An inconsistent length of the firmware file was signaled. xxxx = 0090 hex = 144 dec: When checking the file that was loaded, the component detected a fault (checksum). xxxx = 0092 hex = 146 dec: This SW or HW does not support the selected function. xxxx = 009C hex = 156 dec: Component with the specified component number is not available (p7828). Remedy:
|
| A01009 (N) CU: Control module overtemperature | Cause: The temperature on the control module (Control Unit) has exceeded the specified temperature limit value. Remedy:
Note: The alarm is automatically withdrawn once the limit value has been fallen below. |
| 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 (memory card/device memory) with respect to the version when shipped from the factory. Alarm value (r2124, interpret decimal): 0: Checksum of one file is incorrect. 1: File missing. 2: Too many files. 3: Incorrect firmware version. 4: Incorrect checksum of the back-up file. Remedy:
Note: The file involved can be read out using parameter r9925. |
| 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. No changes are permitted in this directory. Alarm value (r2124, interpret decimal): zyx dec: x = Problem, y = Directory, z = File name x = 1: File does not exist. x = 2: Firmware version of the file does not match the software version. x = 3: File checksum is incorrect. (See manual for y and z codes) Remedy:
|
| 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: Power supply interrupted, CPU crashed, Parameterization invalid. Remedy:
Note: If the fault situation is repeated, then this fault is again output after several interrupted boots. |
| A01019 Writing to the removable data medium unsuccessful | Cause: The write access to the removable data medium was unsuccessful. Remedy:
|
| A01020 Writing to RAM disk unsuccessful | Cause: A write access to the internal RAM disk was unsuccessful. Remedy:
|
| 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. Drive cannot access it. Alarm value (r2124): 1: Know-how protection/copy protection active. 2: Configuration data only backed up in Control Unit. Remedy:
|
| F01023 Software timeout (internal) | Cause: An internal software timeout has occurred. Fault value (r0949): Only for internal Siemens troubleshooting. Remedy:
|
| A01028 (F) Configuration error | Cause: The parameterization that was downloaded was generated with a different module type (Order No., MLFB). Remedy:
|
| 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:
Notice: The monitoring time should be set as short as possible. |
| 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): Reference parameter whose value is 0.0. Remedy:
|
| 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. Remedy:
|
| 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. Alarm value (r2124): aa = 01 hex: Power up was realized without data backup. aa = 02 hex: Last available internal backup loaded. Parameterization must be checked. aa = 03 hex: Last available data record from memory card loaded. aa = 04 hex: Invalid data backup loaded from memory card. 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): Byte codes indicating file/drive object. Remedy:
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): Byte codes indicating file type and specific error (e.g., 255: Incorrect drive object type). 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. Reasons: Read-only file, insufficient memory, defective memory. Fault value (r0949): Diagnostic codes. 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). Dynamic limits may have been exceeded. Fault value (r0949): Parameter/Index/Fault cause codes (e.g., 0: Parameter number illegal, 1: Value cannot be changed). Remedy:
|
| F01043 Fatal error at project download | Cause: A fatal error was detected when downloading a project using the commissioning software. Fault value (r0949): Diagnostic codes (e.g., 1: Device status cannot be changed to Device Download, 20: Configuration inconsistent). Remedy:
|
| F01044 CU: Descriptive data error | Cause: An error was detected when loading the descriptive data saved in the non-volatile memory. Remedy:
|
| A01045 Configuring data invalid | Cause: An error was detected when evaluating the parameter files saved in the non-volatile memory. Several saved parameter values were not able to be accepted. 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. Remedy:
|
| F01054 CU: System limit exceeded | Cause: At least one system overload has been identified. Fault value (r0949): 1: Computing time load too high. 5: Peak load too high. Remedy:
|
| A01064 (F) CU: Internal error (CRC) | Cause: A checksum error (CRC error) has occurred 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%. Remedy:
|
| 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. Remedy:
|
| F01068 CU: Data memory memory overflow | Cause: The utilization for a data memory area is too large. Fault value (r0949): Bit fields indicating specific memory overloaded. 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 factory settings. Remedy:
|
| F01072 Memory card restored from the backup copy | Cause: The Control Unit was switched-off while writing to the memory card. The visible partition became defective and was restored from the backup copy. Remedy:
|
| A01073 (N) POWER ON required for backup copy on memory card | Cause: The parameter assignment on the visible partition of the memory card has changed. To update the backup copy on the non-visible partition, a POWER ON is needed. Remedy:
|
| N01101 (A) CU: memory card not available | Cause: The memory card is not available for the drive. Remedy:
|
| F01105 (A) CU: Insufficient memory | Cause: Too many data sets are configured on this Control Unit. Remedy:
|
| F01107 Save to memory card unsuccessful | Cause: A data save to the memory card was not able to be successfully carried out (defective, insufficient space, file locked). Remedy:
|
| F01112 CU: Power unit not permissible | Cause: The connected power unit cannot be used together with this Control Unit. Remedy:
|
| F01120 (A) Terminal initialization has failed | Cause: An internal software error occurred while the terminal functions were being initialized. 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. Remedy:
|
| F01152 CU: Invalid constellation of drive object types | Cause: It is not possible to simultaneously operate drive object types SERVO, VECTOR and HLA. Max 2 of these types allowed. Remedy:
|
| F01205 CU: Time slice overflow | Cause: Insufficient computation time. Remedy:
|
| F01250 CU: CU-EEPROM incorrect read-only data | Cause: Error when reading the read-only data of the EEPROM in the Control Unit. Remedy:
|
| A01251 CU: CU-EEPROM incorrect read-write data | Cause: Error when reading the read-write data of the EEPROM in the Control Unit. Remedy:
|
| F01257 CU: Firmware version out of date | Cause: The Control Unit firmware is too old. Fault value (r0949): 1: Firmware does not support Control Unit. 3: Firmware does not support Power Module. Remedy:
|
| 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. 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. Remedy:
|
| F01510 BICO: Signal source is not float type | Cause: The requested connector output does not have the correct data type (float). Remedy:
|
| F01511 (A) BICO: Interconnection with different scalings | Cause: The requested BICO interconnection was established, but a conversion is made due to different normalized units or message only for interconnections within a drive object. Remedy:
|
| F01512 BICO: No scaling available | Cause: An attempt was made to determine a conversion factor for a scaling that does not exist. Remedy:
|
| F01513 (N, A) BICO: Interconnection cross DO with different scalings | Cause: The requested BICO interconnection was established between different drive objects, but scalings differ. Remedy:
|
| 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. Remedy:
|
| 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:
|
| A01590 (F) Drive: Motor maintenance interval expired | Cause: The selected service/maintenance interval for this motor was reached. Remedy:
|
| F01600 SI P1 (CU): STOP A initiated | Cause: The drive-integrated “Safety Integrated” function on processor 1 has detected an error and initiated a STOP A. – Forced checking procedure (test stop) unsuccessful. – Subsequent response to fault F01611. Fault value (r0949): 0: Stop request from processor 2. 1005: Pulses suppressed although STO not selected. 9999: Subsequent response to fault F01611. Remedy:
|
| F01611 (A) SI P1 (CU): Defect in a monitoring channel | Cause: The drive-integrated “Safety Integrated” function on processor 1 has detected a fault in the data cross-check between the two monitoring channels and has initiated a STOP F. Fault value (r0949): 0: Stop request from the other monitoring channel. 1…999: Number of cross-compared data with fault. 1000: Watchdog timer has expired. (See manual for detailed list of codes 2000-6166 regarding PROFIsafe and parameters) Remedy:
|
| N01620 (F, A) SI P1 (CU): Safe Torque Off active | Cause: The “Safe Torque Off” (STO) function has been selected on processor 1 using the input terminal and is active. Note: This message does not result in a safety stop response. Remedy: Not necessary. Note: STO: Safe Torque Off |
| F01625 SI P1 (CU): 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.
Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01640 SI P1 (CU): component replacement identified and acknowledgment/save required | Cause: The “Safety Integrated” function integrated in the drive has identified that a component has been replaced. It is no longer possible to operate the drive. When safety functions are active, after a component has been replaced it is necessary to carry out a partial acceptance test. Fault value (r0949, interpret binary):
Remedy:
Note: In addition to the fault, diagnostics bits r9776.2 and r9776.3 are set. See also: r9776 (SI diagnostics). |
| F01641 SI P1 (CU): component replacement identified and save required | Cause: The “Safety Integrated” function integrated in the drive has identified that a component has been replaced. No additional fault response is initiated, therefore operation of the particular drive is not restricted. When safety functions are active, after a component has been replaced it is necessary to carry out a partial acceptance test. Fault value (r0949, interpret binary):
Remedy:
See also: r9776 (SI diagnostics). |
| F01649 SI P1 (CU): Internal software error | Cause: An internal error in the Safety Integrated software on processor 1 has occurred. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01650 SI P1 (CU): Acceptance test required | Cause: The drive-integrated “Safety Integrated” function on processor 1 requires an acceptance test. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret decimal):
Remedy:
|
| F01651 SI P1 (CU): 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 routine was unsuccessful. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: Carry out a POWER ON (switch-off/switch-on). |
| F01653 SI P1 (CU): PROFIBUS/PROFINET configuration error | Cause: There is a PROFIBUS/PROFINET configuration error for using Safety Integrated monitoring functions with a higher-level control. Note: For safety functions that have been enabled, this fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret decimal):
Remedy: The following generally applies:
Specific values:
|
| A01654 (F) SI P1 (CU): 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):
Remedy:
|
| F01655 SI P1 (CU): 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 or communication has failed. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01656 SI P1 (CU): Parameter processor 2 error | Cause: When accessing the Safety Integrated parameters for the processor 2 in the non-volatile memory, an error has occurred. Note: This fault results in a STOP A that can be acknowledged. Fault value (r0949, interpret decimal):
Remedy:
Specific values:
|
| F01658 SI P1 (CU): 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. |
| F01659 SI P1 (CU): 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:
|
| F01660 SI P1 (CU): 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 (CU): 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 (CU): Copying the SI parameters rejected | Cause: In p9700, the value 87 or 208 is saved or was entered offline. This is the reason that when booting, an attempt is made to copy Safety Integrated parameters from processor 1 to processor 2. However, no safety-relevant function has been selected on processor 1 (p9501 = 0, p9601 = 0). This is the reason that copying is not possible. Note: This fault does not result in a safety stop response. Remedy:
|
| F01665 SI P1 (CU): 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:
|
| A01666 (F) SI Motion P1 (CU): Steady-state (static) 1 signal at the F-DI for safe acknowledgment | 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 acknowledgment. Remedy: Set the Failsafe Digital Input (F-DI) to a logical 0 signal (p10006). |
| 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. Remedy: Use a suitable power unit with a lower power rating or a motor with a higher power rating. |
| F01680 SI Motion P1 (CU): 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. Fault value (r0949, interpret decimal):
Remedy:
|
| F01681 SI Motion P1 (CU): Incorrect parameter value | Cause: The parameter cannot be parameterized with this value. Fault value (r0949, interpret decimal): yyyyxxxx dec (yyyy = supplementary information, xxxx = parameter)
Remedy: Correct the parameter value.
|
| F01682 SI Motion P1 (CU): Monitoring function not supported | Cause: The monitoring function enabled in p9501, p9601 or p9801 is not supported in this firmware version. Fault value (r0949, interpret decimal) indicates specific function (e.g. SLP, SCA, SLS override, external ESR, F-DI in PROFIsafe, etc.). Remedy: De-select the monitoring function involved (p9501, p9601, p9801). |
| F01683 SI Motion P1 (CU): SLS enable missing | Cause: The safety-relevant function “SLS” is not enabled in p9501 although other safety-relevant monitoring functions are enabled. 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). Fault value (r0949, interpret decimal):
Remedy:
|
| F01692 SI Motion P1 (CU): Parameter value not permitted for encoderless | Cause: For encoderless motion monitoring functions, the parameter cannot be parameterized with this value. Fault value (r0949, interpret decimal): Parameter number with the incorrect value. Remedy: Correct the parameter specified in the fault value. |
| A01693 (F) SI P1 (CU): Safety parameter setting 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. Remedy:
|
| A01696 (F) SI Motion: Test stop for the motion monitoring functions selected when booting | Cause: The forced checking procedure (test stop) for the safe motion monitoring functions is already selected when booting, which is not permissible. The test is only carried out again after first selecting the forced checking procedure. Remedy: De-select the forced checking procedure of the safety motion monitoring functions and then select again. |
| A01697 (F) SI Motion: Test stop for motion monitoring functions required | Cause: The time set in p9559 for the forced checking procedure (test stop) for the safe motion monitoring functions has been exceeded. A new forced checking procedure is required. Remedy: Carry out the forced checking procedure of the safety motion monitoring functions. The signal source to select the forced checking procedure is set via binector input p9705. |
| A01698 (F) SI P1 (CU): 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: In the safety commissioning mode, the “STO” function is internally selected. Remedy: Not necessary. |
| A01699 (F) SI P1 (CU): Test stop for STO required | Cause: The time set in p9659 for the forced checking procedure (test stop) for the “STO” function has been exceeded. A new forced checking procedure is required. Remedy: Select STO and then de-select again. |
| F01700 SI Motion P1 (CU): STOP A initiated | Cause: The drive is stopped via a STOP A (pulse cancellation via the safety switch-off signal path of processor 1). Possible causes: Stop request from processor 2; pulses not suppressed after test stop selection; subsequent response to messages C01706, C01714, or C01701. Remedy:
|
| F01701 SI Motion P1 (CU): 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 p9560 is fallen below, message C01700 “STOP A initiated” is output. Possible causes: Stop request from processor 2; subsequent response to messages C01714, C01711, or C01707. Remedy:
|
| A01706 SI Motion P1 (CU): SAM/SBR limit exceeded | Cause: Motion monitoring functions with set acceleration monitoring (SAM): velocity exceeded tolerance after STOP B (SS1). Motion monitoring functions with set brake ramp monitoring (SBR): speed exceeded tolerance after STOP B (SS1) or SLS changeover. Remedy: Check the braking behavior and, if necessary, adapt the parameterization of the parameter settings of the “SAM” or the “SBR” function. |
| A01711 SI Motion P1 (CU): 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. Message value (r2124, interpret decimal) details the specific discrepancy (e.g., 0-999 cross-compared data, 1 status image SLS/SAM, 2 status image n < nx, 4 synchronization error, etc.). Remedy:
|
| A01712 SI Motion P1 (CU): 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. Message value (r2124) indicates the specific discrepancy (e.g. 1: monitoring time inputs, 2: internal event input, 3: STO input, etc.). Remedy:
|
| A01714 SI Motion P1 (CU): 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): 100: SLS1, 200: SLS2, 300: SLS3, 400: SLS4 exceeded. Remedy:
|
| A01716 SI Motion P1 (CU): 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). Remedy:
|
| F01770 SI Motion P1 (CU): Discrepancy error of the failsafe inputs | Cause: The Failsafe Digital Inputs (F-DI) show a different state longer than that parameterized in p10002 / p10102. Fault value (r0949) indicates the bit causing the discrepancy. Remedy:
|
| A01772 SI Motion P1 (CU): Test stop for Failsafe Digital Outputs running | Cause: The forced checking procedure (test stop) for the Failsafe Digital Outputs is currently in progress. Remedy: The alarm is automatically withdrawn after successfully ending or canceling the test stop. |
| F01773 SI Motion P1 (CU): Test stop Failsafe Digital Output error | Cause: A fault has occurred on processor 1 during the forced checking procedure (test stop) of the Failsafe Digital Output. Fault value (r0949) indicates the details of the error (RRRVWXYZ hex) including state of DO channel, required state, reason for fault, and test stop state. Remedy: Refer to detailed cause information (bit patterns) to diagnose the specific stage of the test stop failure. |
| A01774 SI Motion P1 (CU): Test stop for Failsafe Digital Outputs required | Cause: The time set in p10003 for the forced checking procedure (test stop) for the Failsafe Digital Outputs has been exceeded. A new forced checking procedure is required. After the next time the forced checking procedure is selected, the message is withdrawn and the monitoring time is reset. Remedy: Carry out the forced checking procedure for the digital outputs. The signal source to select the forced checking procedure is set via binector input p10007. |
| A01788 SI: Automatic test stop waits for STO deselection via motion monitoring functions | Cause: The automatic test stop (forced checking procedure) was not able to be carried out after powering up. Possible causes:
Remedy:
|
| A01790 SI: Power up stopped due to STO via terminals | Cause: When powering up, the automatic internal self test of the Control Unit was not able to be completed as the pulses were not enabled. It is possible that the “STO via terminals at the Power Module” function is being used, and STO is selected in at least one hardware switch-off signal path at the Power Module. Remedy:
|
| A01796 (F, N) SI P1 (CU): Wait for communication | Cause: The drive waits for communication to be established to execute the safety-relevant motion monitoring functions. 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:
|
| A01798 SI Motion P1 (CU): Test stop for motion monitoring functions running | Cause: The forced checking procedure (test stop) for the safe motion monitoring functions is currently in progress. Remedy: Not necessary. The message is automatically withdrawn when the test stop has been completed. |
| A01799 SI Motion P1 (CU): 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 device sides.
|
| 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 partner.
|
| 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. Note: If there is no communication to a higher-level control system, then p2030 should be set = 0 to suppress this message. |
| 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 = 1: Publisher with address in r2077[0], connection failed. … Bit 15 = 1: Publisher with address in r2077[15], 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. Remedy:
|
| F01951 CU SYNC: Synchronization application clock cycle missing | Cause: Internal synchronization of the application cycles unsuccessful. Only for internal Siemens troubleshooting. Remedy:
|
| A01953 CU SYNC: Synchronization not completed | Cause: After the drive system was switched on, synchronization between the basic clock cycle and application clock cycle was started but was not completed within the selected time tolerance. Remedy: Carry out a POWER ON (switch-off/switch-on). |
| A02050 Trace: Start not possible | Cause: The trace has already been started. Remedy: Stop the trace and, if necessary, start again. |
| A02051 Trace: recording not possible as a result of know-how protection | Cause: TRACE recording is not possible as at least one signal or trigger signal being used is under know-how protection. Remedy:
|
| 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 cycle is shorter than the selected basic clock cycle 0 (p0110[0]). 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. |
| 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. |
| 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. |
| 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. |
| A02095 MTrace 0: multiple trace cannot be activated | Cause: The following functions or settings are not permissible in conjunction with a multiple trace (trace recorder 0):
Remedy:
|
| A02096 MTrace 0: cannot be saved | Cause: It is not possible to save the measurement results of a multiple trace on the memory card (trace recorder 0). Remedy:
|
| A02097 MTrace 1: multiple trace cannot be activated | Cause: The following functions or settings are not permissible in conjunction with a multiple trace (trace recorder 1):
Remedy:
|
| A02098 MTrace 1: cannot be saved | Cause: It is not possible to save the measurement results of a multiple trace on the memory card (trace recorder 1). 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. Remedy:
|
| F02151 (A) OA: Internal software error | Cause: An internal software error has occurred within an OA application. 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.). Remedy:
|
| F03000 NVRAM fault on action | Cause: A fault occurred during execution of action p7770 = 1 or 2 for the NVRAM data. 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 (switch-off/switch-on) for all components. |
| F03505 (N, A) Analog input wire breakage | Cause: The wire-break monitoring for an analog input has responded. Remedy:
|
| A03510 (F, N) 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. 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. 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. Remedy: Check the following:
|
| A05004 (N) Power unit: Rectifier overtemperature | Cause: The alarm threshold for the overtemperature of the rectifier has been reached. 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). Remedy: Not necessary. The alarm disappears automatically once the limit value is undershot. |
| A05065 (F, N) Voltage measured values not plausible | Cause: The voltage measurement does not supply any plausible values and is not used. Remedy: The following parameterization must be made in order to deactivate the alarm:
|
| F06310 (A) Supply voltage (p0210) incorrectly parameterized | Cause: The measured DC voltage lies outside the tolerance range after precharging has been completed. Remedy:
|
| A06921 (N) Braking resistor phase asymmetry | Cause:
Remedy:
|
| F06922 Braking resistor phase failure | Cause: A phase failure for the brake resistor was detected. Remedy: Check the feeder cables to the braking resistors. |
| F07011 Drive: Motor overtemperature | Cause: The motor temperature has exceeded the fault threshold (p0605) or the timer (p0606) after the alarm threshold was exceeded (p0604) has expired. Possible causes:
Remedy:
|
| A07012 (N) Drive: Motor temperature model 1/3 overtemperature | Cause: The motor temperature model 1/3 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. 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. Possible causes:
Remedy:
|
| F07016 Drive: Motor temperature sensor fault | Cause: An error was detected when evaluating the temperature sensor set in p0601. Possible causes:
Remedy:
|
| F07080 Drive: Incorrect control parameter | Cause: The closed-loop control parameters have been parameterized incorrectly (e.g. p0356 = L_spread = 0). 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. 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. 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. 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. 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. Remedy: Check the adapted parameter values and if required correct. |
| 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. |
| A07092 Drive: moment of inertia estimator still not ready | Cause: The moment of inertia estimator still has no valid values. The acceleration cannot be calculated. Remedy: Repeat the operation when the moment of inertia estimator is ready (r1407.26 = 1). |
| A07094 General parameter limit violation | Cause: As a result of the violation of a parameter limit, the parameter value was automatically corrected. Remedy: Check the adapted parameter values and if required correct. |
| A07200 Drive: Master control ON command present | Cause: The ON/OFF1 command is present (no 0 signal). 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: The line contactor was not able to be closed or opened within the time in p0861, or dropped out during operation. Remedy:
|
| F07320 Drive: Automatic restart interrupted | Cause: The specified number of restart attempts (p1211) has been completely used up. Remedy:
|
| A07321 Drive: Automatic restart active | Cause: The automatic restart (AR) is active. 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. 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). PMSM operation with U/f characteristic and sensorless vector control is not supported. Remedy: Deactivate the “flying restart” function (p1200 = 0). |
| F07332 Flying restart: maximum speed reduced | Cause: The maximum speed that can be reached is reduced; at very high speeds problems associated with the flying restart can be encountered. Remedy: Parameter changes are not required. A flying restart at speeds above 3000 rpm should be avoided. |
| A07352 Drive: Limit switch signals not plausible | Cause: Limit switch signals are not plausible. Remedy:
|
| F07404 Drive: DC link voltage monitoring Vdc_max | Cause: The monitoring of the DC link voltage p1284 has responded (only U/f control). Remedy:
|
| A07409 (N) 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 is automatically withdrawn after one of the following measures:
|
| F07410 Drive: Current controller output limited | Cause: The condition “I_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 setpoint not reached when building up excitation | 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: For fault cause = 1:
For fault cause = 2:
For fault cause = 3:
|
| 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): 1: upper limit reached. 2: lower limit reached. Remedy:
See also: p0595 (Technological unit selection), p0596 (Technological unit reference quantity), p2264 (Technology controller actual value), p2267, p2268. |
| 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: For alarm value = 1: Set the output limit in p2291 higher than in p2292. See also: p2291, 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:
|
| A07440 EPOS: Jerk time is limited | Cause: The calculation of the jerk time Tr = max(p2572, p2573) / p2574 resulted in an excessively high value so that the jerk time is internally limited to 1000 ms. Note: The alarm is also output if jerk limiting is not active. Remedy:
See also: p2572, p2573, p2574. |
| A07441 LR: Save the position offset of the absolute encoder adjustment | Cause: The status of the absolute encoder adjustment has changed. In order to permanently save the determined position offset (p2525) it must be saved in a non-volatile fashion (p0971). Remedy: Not necessary. This alarm automatically disappears after the offset has been saved. See also: p2507, p2525. |
| F07442 (A) LR: Multiturn does not match the modulo range | Cause: The ratio between the multiturn resolution and the modulo range (p2576) is not an integer number. This results in the adjustment being set back, as the position actual value cannot be reproduced after switch-off/switch-on. Remedy: Make the ratio between the multiturn resolution and the modulo range an integer number. The ratio v is calculated as follows: 1. Motor encoder: v = (p0421 * p2506 * p2505) / (p2504 * p2576) 2. Direct encoder: v = (p0421 * p2506) / p2576 See also: p0412, p0432, p0433, p2504, p2505, p2506, p2576. |
| F07443 (A) LR: Reference point coordinate not in the permissible range | Cause: The reference point coordinate received when adjusting the encoder via connector input p2599 lies outside the half of the encoder range and cannot be set as actual axis position. Fault value (r0949, interpret decimal): Maximum permissible value for the reference point coordinate. Remedy: Set the reference point coordinate to a lower value than specified in the fault value. See also: p2598, p2599. |
| F07450 (A) LR: Standstill monitoring has responded | Cause: After the standstill monitoring time (p2543) expired, the drive left the standstill window (p2542).
Remedy: Check the causes and resolve. |
| F07451 (A) LR: Position monitoring has responded | Cause: When the position monitoring time (p2545) expired, the drive had still not reached the positioning window (p2544).
Remedy: Check the causes and resolve. |
| F07452 (A) LR: Following error too high | Cause: The difference between the position setpoint position actual value (following error dynamic model, r2563) is higher than the tolerance (p2546).
Remedy: Check the causes and resolve. |
| F07453 LR: Position actual value preprocessing error | Cause: An error has occurred during the position actual value preprocessing. Remedy: Check the encoder for the position actual value preprocessing. See also: p2502 (LR encoder assignment). |
| A07454 LR: Position actual value preprocessing does not have a valid encoder | Cause: One of the following problems has occurred with the position actual value preprocessing:
Remedy: Check the drive data sets, encoder data sets and encoder assignment. See also: p0187, p0188, p0400, p2502. |
| A07455 EPOS: Maximum velocity limited | Cause: The maximum velocity (p2571) is too high to correctly calculate the modulo correction. Within the sampling time for positioning (8 ms), with the maximum velocity, a maximum of the half modulo length must be moved through. p2571 was limited to this value. Remedy: Reduce the maximum velocity (p2571). |
| A07456 EPOS: Setpoint velocity limited | Cause: The actual setpoint velocity is greater than the parameterized maximum velocity (p2571) and is therefore limited. Remedy:
|
| A07457 EPOS: Combination of input signals illegal | Cause: An illegal combination of input signals that are simultaneously set was identified. Alarm value (r2124, interpret decimal): 0: Jog 1 and jog 2 (p2589, p2590). 1: Jog 1 or jog 2 and direct setpoint input/MDI (p2589, p2590, p2647). 2: Jog 1 or jog 2 and start referencing (p2589, p2590, p2595). 3: Jog 1 or jog 2 and activate traversing task (p2589, p2590, p2631). 4: Direct setpoint input/MDI and starting referencing (p2647, p2595). 5: Direct setpoint input/MDI and activate traversing task (p2647, p2631). 6: Start referencing and activate traversing task (p2595, p2631). Remedy: Check the appropriate input signals and correct. |
| F07458 EPOS: Reference cam not found | Cause: After starting the search for reference, the axis moved through the maximum permissible distance to search for the reference cam without actually finding the reference cam. Remedy:
See also: p2606, p2607, p2612. |
| F07459 EPOS: No zero mark | Cause: After leaving the reference cam, the axis has traversed the maximum permissible distance between the reference cam and zero mark without finding the zero mark. Remedy:
See also: p0494, p2609. |
| F07460 EPOS: End of reference cam not found | Cause: During the search for reference, when the axis reached the zero mark it also reached the end of the traversing range without detecting an edge at the binector input “reference cam” (BI: p2612). Maximum traversing range: -2147483648 [LU] … -2147483647 [LU] Remedy:
See also: p2612. |
| A07461 EPOS: Reference point not set | Cause: When starting a traversing block/direct setpoint input, a reference point is not set (r2684.11 = 0). Remedy: Reference the system (search for reference, flying referencing, set reference point). |
| A07462 EPOS: Selected traversing block number does not exist | Cause: A traversing block selected via binector input p2625 … p2630 was started via binector input p2631 = 0/1 edge “Activate traversing task”. – the number of the started traversing block is not contained in p2616[0…n]. – the started traversing block is suppressed. Alarm value (r2124, interpret decimal): Number of the selected traversing block that is also not available. Remedy:
|
| A07463 (F) EPOS: External block change not requested in the traversing block | Cause: For a traversing block with the block change enable CONTINUE_EXTERNAL_ALARM, the external block change was not requested. Alarm value (r2124, interpret decimal): Number of the traversing block. Remedy: Resolve the reason as to why the edge is missing at binector input (BI: p2632). |
| F07464 EPOS: Traversing block is inconsistent | Cause: The traversing block does not contain valid information. Fault value (r0949, interpret decimal): Number of the traversing block with invalid information. Remedy: Check the traversing block and where relevant, take into consideration alarms that are present. |
| A07465 EPOS: Traversing block does not have a subsequent block | Cause: There is no subsequent block in the traversing block. Alarm value (r2124, interpret decimal): Number of the traversing block with the missing subsequent block. Remedy:
|
| A07466 EPOS: Traversing block number assigned a multiple number of times | Cause: The same traversing block number was assigned a multiple number of times. Alarm value (r2124, interpret decimal): Number of the traversing block that was assigned a multiple number of times. Remedy: Correct the traversing blocks. |
| A07467 EPOS: Traversing block has illegal task parameters | Cause: The task parameter in the traversing block contains an illegal value. Alarm value (r2124, interpret decimal): Number of the traversing block with an illegal task parameter. Remedy: Correct the task parameter in the traversing block. |
| A07468 EPOS: Traversing block jump destination does not exist | Cause: In a traversing block, a jump was programmed to a non-existent block. Alarm value (r2124, interpret decimal): Number of the traversing block with a jump destination that does not exist. Remedy:
|
| A07469 EPOS: Traversing block < target position < software limit switch minus | Cause: In the traversing block the specified absolute target position lies outside the range limited by the software limit switch minus. Alarm value (r2124, interpret decimal): Number of the traversing block with illegal target position. Remedy:
|
| A07470 EPOS: Traversing block > target position > software limit switch plus | Cause: In the traversing block the specified absolute target position lies outside the range limited by the software limit switch plus. Alarm value (r2124, interpret decimal): Number of the traversing block with illegal target position. Remedy:
|
| A07471 EPOS: Traversing block target position outside the modulo range | Cause: In the traversing block the target position lies outside the modulo range. Alarm value (r2124, interpret decimal): Number of the traversing block with illegal target position. Remedy:
|
| A07472 EPOS: Traversing block ABS_POS/ABS_NEG not possible | Cause: In the traversing block the positioning mode ABS_POS or ABS_NEG were parameterized with the modulo correction not activated. Alarm value (r2124, interpret decimal): Number of the traversing block with the illegal positioning mode. Remedy: Correct the traversing block. |
| A07473 (F) EPOS: Beginning of traversing range reached | Cause: When traversing, the axis has moved to the traversing range limit. Remedy: Move away in the positive direction. |
| A07474 (F) EPOS: End of traversing range reached | Cause: When traversing, the axis has moved to the traversing range limit. Remedy: Move away in the negative direction. |
| F07475 (A) EPOS: Target position < start of traversing range | Cause: The target position for relative traversing lies outside the traversing range. Remedy: Correct the target position. |
| F07476 (A) EPOS: Target position > end of the traversing range | Cause: The target position for relative traversing lies outside the traversing range. Remedy: Correct the target position. |
| A07477 (F) EPOS: Target position < software limit switch minus | Cause: In the actual traversing operation, the target position is less than the software limit switch minus. Remedy:
See also: p2578, p2580, p2582. |
| A07478 (F) EPOS: Target position > software limit switch plus | Cause: In the actual traversing operation, the target position is greater than the software limit switch plus. Remedy:
See also: p2579, p2581, p2582. |
| A07479 EPOS: Software limit switch minus reached | Cause: The axis is at the position of the software limit switch minus. An active traversing block was interrupted. Remedy:
See also: p2578, p2580, p2582. |
| A07480 EPOS: Software limit switch plus reached | Cause: The axis is at the position of the software limit switch plus. An active traversing block was interrupted. Remedy:
See also: p2579, p2581, p2582. |
| F07481 (A) EPOS: Axis position < software limit switch minus | Cause: The actual position of the axis is less than the position of the software limit switch minus. Remedy:
See also: p2578, p2580, p2582. |
| F07482 (A) EPOS: Axis position > software limit switch plus | Cause: The actual position of the axis is greater than the position of the software limit switch plus. Remedy:
See also: p2579, p2581, p2582. |
| A07483 EPOS: Travel to fixed stop clamping torque not reached | Cause: The fixed stop in the traversing block was reached without the clamping torque/clamping force having been achieved. Remedy:
|
| F07484 EPOS: Fixed stop outside the monitoring window | Cause: In the “fixed stop reached” state, the axis has moved outside the defined monitoring window (p2635). Remedy:
|
| F07485 (A) EPOS: Fixed stop not reached | Cause: In a traversing block with the task FIXED STOP, the end position was reached without detecting a fixed stop. Remedy:
|
| A07486 EPOS: Intermediate stop missing | Cause: In the modes “traversing blocks” or “direct setpoint input/MDI” at the start of motion, the binector input “no intermediate stop/intermediate stop” (BI: p2640) did not have a 1 signal. Remedy: Connect a 1 signal to the binector input “no intermediate stop/intermediate stop” (BI: p2640) and re-start motion. See also: p2640. |
| A07487 EPOS: Reject traversing task missing | Cause: In the modes “traversing blocks” or “direct setpoint input/MDI” at the start of motion, the binector input “do not reject traversing task/reject traversing task” (BI: p2641) does not have a 1 signal. Remedy: Connect a 1 signal to the binector input “do not reject traversing task/reject traversing task” (BI: p2641) and restart motion. See also: p2641. |
| F07488 EPOS: Relative positioning not possible | Cause: In the mode “direct setpoint input/MDI”, for continuous transfer (p2649 = 1) relative positioning was selected (BI: p2648 = 0 signal). Remedy: Check the control. |
| A07489 EPOS: Reference point correction outside the window | Cause: For the function “flying referencing” the difference between the measured position at the measuring probe and the reference point coordinate lies outside the parameterized window. Remedy:
|
| F07490 (N) EPOS: Enable signal withdrawn while traversing | Cause:
Remedy:
|
| F07491 (A) EPOS: STOP cam minus reached | Cause: A 0 signal was detected at binector input BI: p2569, i.e. the STOP cam minus was reached. For a positive traversing direction, the STOP cam minus was reached – i.e. the wiring of the STOP cam is incorrect. Remedy:
See also: p2569. |
| F07492 (A) EPOS: STOP cam plus reached | Cause: A 0 signal was detected at binector input BI: p2570, i.e. the STOP cam plus was reached. For a negative traversing direction, the STOP cam plus was reached – i.e. the wiring of the STOP cam is incorrect. Remedy:
See also: p2570. |
| F07493 LR: Overflow of the value range for position actual value | Cause: The value range (-2147483648 … 2147483647) for the position actual value representation was exceeded. When the overflow occurs, the “referenced” or “adjustment absolute measuring system” status is reset. Fault value (r0949, interpret decimal): 1: The position actual value (r2521) has exceeded the value range. 2: The encoder position actual value Gn_XIST2 (r0483) or the absolute value after the load gear (r2723) has exceeded the value range. 3: The maximum encoder value times the factor to convert the absolute position (r0483 and/or r2723) from increments to length units (LU) has exceeded the value range for displaying the position actual value. Remedy:
See also: p2506, p0419. |
| F07494 LR: Drive Data Set changeover in operation | Cause: A Drive Data Set changeover (DDS) with a change of the mechanical relationships (p2503 … 2506), direction of rotation (p1821) or the encoder assignment (p2502) was requested in operation. Remedy: To changeover the drive data set, initially, exit the “operation” mode. |
| A07495 (F) LR: Reference function interrupted | Cause: An activated reference function (reference mark search or measuring probe evaluation) was interrupted. Possible causes:
Remedy:
|
| A07496 EPOS: Enable not possible | Cause: It is not possible to enable the basic positioner because at least one signal is missing. Alarm value (r2124, interpret decimal): 1: EPOS enable missing (BI: p2656). 2: Position actual value, valid feedback signal missing (BI: p2658). Remedy: Check the appropriate binector inputs and signals. See also: p2656, p2658. |
| A07497 (N) LR: Position setting value activated | Cause: The position actual value is set to the value received via CI: p2515 while BI: p2514 = 1 signal. A possible system deviation cannot be corrected. Remedy: Not necessary. The alarm automatically disappears with BI: p2514 = 0 signal. |
| A07498 (F) LR: Measuring probe evaluation not possible | Cause: When evaluating the measuring probe, an error occurred. Alarm value (r2124, interpret decimal): 6: The input terminal for the measuring probe is not set. 4098: Error when initializing the measuring probe. 4100: The measuring pulse frequency is too high. > 50000: The measuring clock cycle is not a multiple integer of the position controller clock cycle. Remedy: Deactivate the measuring probe evaluation (BI: p2509 = 0 signal).
|
| F07499 (A) EPOS: Reversing cam approached with the incorrect traversing direction | Cause: The reversing cam MINUS was approached in the positive traversing direction or the reversing cam PLUS was approached in the negative traversing direction. Remedy:
|
| F07503 EPOS: STOP cam approached with the incorrect traversing direction | Cause: The STOP cam MINUS was approached in the positive traversing direction or the STOP cam PLUS was approached in the negative traversing direction. Remedy:
|
| A07505 EPOS: Task fixed stop not possible in the U/f/SLVC mode | Cause: In the U/f/SLVC mode, an attempt was made to execute a traversing block with the “fixed stop” task. This is not possible. Remedy:
|
| A07507 EPOS: reference point cannot be set | Cause: After the reference point correction, the position setpoint lies outside the traversing range limits. 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:
|
| A07550 (F, N) Drive: Not possible to reset encoder parameters | Cause: When carrying out a factory setting (e.g. using p0970 = 1), it was not possible to reset the encoder parameters. Remedy: Repeat the operation. |
| F07552 (A) Drive encoder: Encoder configuration not supported | Cause: The requested encoder configuration is not supported. Only bits may be requested in p0404 that are signaled as being supported by the encoder evaluation in r0456. Fault value (r0949, interpret decimal): ccccbbaa hex. Remedy:
|
| F07553 (A) Drive encoder: Sensor Module configuration not supported | Cause: The Sensor Module does not support the requested configuration. Remedy:
|
| A07557 (F) Encoder 1: Reference point coordinate not in the permissible range | Cause: The reference point coordinate received when adjusting the encoder via connector input CI:p2599 lies outside the half of the encoder range and cannot be set as actual axis position. The maximum permissible value is displayed in the supplementary information. Remedy: Set the reference point coordinate less than the value from the supplementary information. See also: p2598. |
| A07558 (F) Encoder 2: Reference point coordinate not in the permissible range | Cause: The reference point coordinate received when adjusting the encoder via connector input CI:p2599 lies outside the half of the encoder range and cannot be set as actual axis position. The maximum permissible value is displayed in the supplementary information. Remedy: Set the reference point coordinate less than the value from the supplementary information. See also: p2598. |
| 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:
|
| A07565 (F, N) Drive: Encoder error in PROFIdrive encoder interface 1 | Cause: An encoder error was signaled for encoder 1 via the PROFIdrive encoder interface (G1_ZSW.15). Alarm value (r2124, interpret decimal): Error code from G1_XIST2. Remedy: Acknowledge the encoder error using the encoder control word (G1_STW.15 = 1). |
| A07566 (F, N) Drive: Encoder error in PROFIdrive encoder interface 2 | Cause: An encoder error was signaled for encoder 2 via the PROFIdrive encoder interface (G2_ZSW.15). Alarm value (r2124, interpret decimal): Error code from G2_XIST2. Remedy: Acknowledge the encoder error using the encoder control word (G2_STW.15 = 1). |
| A07569 (F) Enc identification active | Cause: During encoder identification (waiting) with p0400 = 10100, the encoder could still not be identified. Remedy:
|
| N07570 (F) Encoder identification data transfer running | Cause: The encoder type was automatically determined using p0400 = 10100. Note: This fault causes the pulses to be cancelled – this is necessary to transfer the encoder parameterization to p0400 and the following. Remedy: Acknowledge the fault without taking additional measures. |
| A07577 (F) Encoder 1: Measuring probe evaluation not possible | Cause: When evaluating the measuring probe, an error occurred. Alarm value (r2124, interpret decimal): 6: The input terminal for the measuring probe is not set. 4098: Error when initializing the measuring probe. 4100: The measuring pulse frequency is too high. 4200: The PROFIBUS clock cycle is not a multiple of integer of the position controller clock cycle. Remedy: Deactivate the measuring probe evaluation (BI: p2509 = 0 signal).
|
| A07578 (F) Encoder 2: Measuring probe evaluation not possible | Cause: When evaluating the measuring probe, an error occurred. Alarm value (r2124, interpret decimal): 6: The input terminal for the measuring probe is not set. 4098: Error when initializing the measuring probe. 4100: The measuring pulse frequency is too high. 4200: The PROFIBUS clock cycle is not a multiple of integer of the position controller clock cycle. Remedy: Deactivate the measuring probe evaluation (BI: p2509 = 0 signal).
|
| A07581 (F) Encoder 1: Position actual value preprocessing error | Cause: An error has occurred during the position actual value preprocessing. Remedy: Check the encoder for the position actual value preprocessing. See also: p2502 (LR encoder assignment). |
| A07582 (F) Encoder 2: Position actual value preprocessing error | Cause: An error has occurred during the position actual value preprocessing. Remedy: Check the encoder for the position actual value preprocessing. See also: p2502 (LR encoder assignment). |
| A07584 Encoder 1: Position setting value activated | Cause: The position actual value is set to the value received via CI: p2515 while BI: p2514 = 1 signal. A possible system deviation cannot be corrected. Remedy: Not necessary. The alarm automatically disappears with BI: p2514 = 0 signal. |
| A07585 Encoder 2: Position setting value activated | Cause: The position actual value is set to the value received via CI: p2515 while BI: p2514 = 1 signal. A possible system deviation cannot be corrected. Remedy:
|
| A07587 Encoder 1: Position actual value preprocessing does not have a valid encoder | Cause: The following problem has occurred during the position actual value preprocessing. – an encoder data set has been assigned, however, the encoder data set does not contain any encoder data (p0400 = 0) or invalid data (e.g. p0408 = 0). Remedy:
|
| A07588 Encoder 2: Position actual value preprocessing does not have a valid encoder | Cause: The following problem has occurred during the position actual value preprocessing. – an encoder data set has been assigned, however, the encoder data set does not contain any encoder data (p0400 = 0) or invalid data (e.g. p0408 = 0). Remedy:
|
| A07590 (F) Encoder 1: Drive Data Set changeover in operation | Cause: A Drive Data Set changeover (DDS) with a change of the mechanical relationships and the encoder assignment (p2502) was requested in operation. Remedy:
|
| A07591 (F) Encoder 2: Drive Data Set changeover in operation | Cause: A Drive Data Set changeover (DDS) with a change of the mechanical relationships and the encoder assignment (p2502) was requested in operation. Remedy:
|
| A07593 (F, N) Encoder 1: Value range for position actual value exceeded | Cause: The value range (-2147483648 … 2147483647) for the position actual value representation was exceeded. When the overflow occurs, the “referenced” or “absolute encoder adjusted” status is reset. Alarm value (r2124, interpret decimal): 1: The position actual value (r2521) has exceeded the value range. 2: The encoder position actual value Gn_XIST2 (r0483) or the absolute value after the load gear (r2723) has exceeded the value range. 3: The maximum encoder value multiplied by the factor to convert the absolute position has exceeded the value range. Remedy:
|
| A07594 (F, N) Encoder 2: Value range for position actual value exceeded | Cause: The value range (-2147483648 … 2147483647) for the position actual value representation was exceeded. Alarm value (r2124, interpret decimal): 1: The position actual value (r2521) has exceeded the value range. 2: The encoder position actual value Gn_XIST2 (r0483) or the absolute value after the load gear (r2723) has exceeded the value range. 3: The maximum encoder value times the factor to convert the absolute position has exceeded the value range. Remedy:
|
| A07596 (F) Encoder 1: Reference function interrupted | Cause: An activated reference function (reference mark search or measuring probe evaluation) was interrupted. – an encoder fault has occurred (Gn_ZSW.15 = 1). – position actual value was set during an activated reference function. – simultaneously activate reference mark search and measuring probe evaluation. – activated reference function was deactivated. Remedy:
|
| A07597 (F) Encoder 2: Reference function interrupted | Cause: An activated reference function (reference mark search or measuring probe evaluation) was interrupted. – an encoder fault has occurred (Gn_ZSW.15 = 1). – position actual value was set during an activated reference function. – simultaneously activate reference mark search and measuring probe evaluation. – activated reference function was deactivated. Remedy:
|
| F07599 (A) Encoder 1: Adjustment not possible | Cause: The maximum encoder value times the factor to convert the absolute position (r0483 and/or r2723) from increments to length units (LU) has exceeded the value range. Remedy:
|
| F07600 (A) Encoder 2: Adjustment not possible | Cause: The maximum encoder value times the factor to convert the absolute position (r0483 and/or r2723) from increments to length units (LU) has exceeded the value range. Remedy:
|
| F07754 Drive: Incorrect shutoff valve configuration | Cause: An incorrect shutoff valve configuration was detected. Fault value (r0949, interpret decimal): 100: Enable Safety Integrated (p9601/p9801), but p0218.0 = 0 (shutoff valve not available). 101: The manipulated variable inhibit time is set less than the wait time (switching on). 102: The manipulated variable inhibit time is set less than the wait time (switching off). Remedy:
|
| F07800 Drive: No power unit present | Cause: The power unit parameters cannot be read or no parameters are stored in the power unit. Note: This fault also occurs if an incorrect topology was selected in the commissioning software. Remedy:
|
| F07801 Drive: Motor overcurrent | Cause: The permissible motor limit current was exceeded. – effective current limit set too low. – current controller not correctly set. – U/f operation: Up ramp too short or load too high. – Short-circuit in motor cable or ground fault. – Motor current does not match power unit. – Switch to rotating motor without flying restart (p1200). Remedy:
|
| F07802 Drive: Infeed or power unit not ready | Cause: After an internal switch-on command, the infeed or drive does not signal ready. – monitoring time is too short. – DC link voltage is not present. – associated infeed or drive of the signaling component is defective. – supply voltage incorrectly set. 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 (PM250, 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. Fault value (r0949): 1-3: Short-circuit phases UV, UW, VW. 4: Ground fault with overcurrent. 5-7: Motor cable phase U, V, W interrupted. 8: Short-circuit with hardware shutdown. 1yxxx/2yxxx: Ground fault detected in phase U/V. Remedy:
|
| F07810 Drive: Power unit EEPROM without rated data | Cause: No rated data are stored in the power unit EEPROM. Remedy:
|
| A07850 (F) External alarm 1 | Cause: The condition for “External alarm 1” is satisfied. Initiated by a 1/0 edge via binector input p2112. Remedy:
|
| A07851 (F) External alarm 2 | Cause: The condition for “External alarm 2” is satisfied. Initiated by a 1/0 edge via binector input p2116. Remedy:
|
| A07852 (F) External alarm 3 | Cause: The condition for “External alarm 3” is satisfied. Initiated by a 1/0 edge via binector input p2117. Remedy:
|
| F07860 (A) External fault 1 | Cause: The condition for “External fault 1” is satisfied. Initiated by a 1/0 edge via binector input p2106. Remedy:
|
| F07861 (A) External fault 2 | Cause: The condition for “External fault 2” is satisfied. Initiated by a 1/0 edge via binector input p2107. Remedy:
|
| F07862 (A) External fault 3 | Cause: The condition for “External fault 3” is satisfied. Initiated by a 1/0 edge via parameters (p2108, p3111, p3112). Remedy:
|
| A07891 Drive: Load monitoring pump/fan blocked | Cause: The load monitoring is configured for a pump or fan (p2193 = 4, 5). The monitoring function detects when the pump/fan is blocked. Remedy:
|
| A07892 Drive: Load monitoring pump/fan no load condition | Cause: The load monitoring is configured for a pump or fan (p2193 = 4, 5). The monitoring function detects when the pump/fan is operating under no load conditions (dry run or broken belt). Remedy:
|
| A07893 Drive: Load monitoring pump leakage | Cause: The load monitoring is configured for a pump (p2193 = 4). The monitoring function detects a leak in the pump circuit. Remedy:
|
| F07894 Drive: Load monitoring pump/fan blocked | Cause: The load monitoring is configured for a pump or fan (p2193 = 4, 5). The monitoring function detects when the pump/fan is blocked. Remedy:
|
| F07895 Drive: Load monitoring pump/fan no load condition | Cause: The load monitoring is configured for a pump or fan (p2193 = 4, 5). The monitoring function detects when the pump/fan is operating under no load conditions. Remedy:
|
| F07896 Drive: Load monitoring pump leakage | Cause: The load monitoring is configured for a pump (p2193 = 4). The monitoring function detects a leak in the pump circuit. Remedy:
|
| 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. Remedy:
|
| F07901 Drive: Motor overspeed | Cause: The maximum permissible speed was either positively or negatively exceeded. Remedy:
|
| F07902 (N, A) Drive: Motor stalled | Cause: For a vector drive the system has identified that the motor has stall for a time longer than is set in p2178. Fault value (r0949): 1: Stall detection using r1408.11 (vector control with encoder). 2: Stall detection using r1408.12. 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). Remedy:
|
| A07910 (N) Drive: Motor overtemperature | Cause: KTY84/PT1000 or no sensor: The measured motor temperature or the model temperature has exceeded the alarm threshold (p0604). PTC or bimetallic NC contact: Threshold exceeded or contact opened. Remedy:
|
| A07920 Drive: Torque/speed too low | Cause: For p2193 = 1: Torque deviates from envelope characteristic (too low). For p2193 = 2: Speed signal from external encoder deviates from speed (r2169) (too low). Remedy:
|
| A07921 Drive: Torque/speed too high | Cause: For p2193 = 1: Torque deviates from envelope characteristic (too high). For p2193 = 2: Speed signal from external encoder deviates from speed (r2169) (too high). Remedy:
|
| A07922 Drive: Torque/speed out of tolerance | Cause: Torque or speed signal deviates from envelope or external encoder value. Remedy:
|
| F07923 Drive: Torque/speed too low | Cause: Torque deviates from envelope (too low) or speed signal deviates (too low). Remedy:
|
| F07924 Drive: Torque/speed too high | Cause: Torque deviates from envelope (too high) or speed signal deviates (too high). Remedy:
|
| F07925 Drive: Torque/speed out of tolerance | Cause: Torque or speed signal deviates from envelope or external encoder value. Remedy:
|
| A07926 Drive: Envelope curve parameter invalid | Cause: Invalid parameter values were entered for the envelope characteristic of the load monitoring. Rules: p2182 < p2183 < p2184, p2185 > p2186, etc. Remedy:
|
| A07927 DC braking active | Cause: The motor is braked with DC current. DC braking is active. 1) DCBRK response active. 2) DC braking activated at binector input p1230. Remedy:
|
| A07929 (F) Drive: No motor detected | Cause: The absolute current value is so small after enabling the inverter pulses that no motor is detected. 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). Remedy:
|
| A07960 Drive: Incorrect friction characteristic | Cause: The friction characteristic is incorrect. Fault values (r0949) indicate specific issues (1538: torque > limit, 1539: torque < min, etc). Remedy:
|
| A07961 Drive: Friction characteristic record activated | Cause: The automatic friction characteristic record is activated. Remedy:
|
| F07963 Drive: Friction characteristic record interrupted | Cause: The conditions to record the friction characteristic are not fulfilled. Fault value (r0949): 0046: Missing enable signals. 1082/1084/1087: Highest speed value issues. 1110/1111/1198: Direction inhibited. 1300: Control mode not set to closed-loop. 1755: Encoderless control speed issues. Remedy:
|
| F07967 Drive: Incorrect pole position identification | Cause: A fault has occurred during the pole position identification routine. Only for internal Siemens troubleshooting. Remedy:
|
| F07968 Drive: Lq-Ld measurement incorrect | Cause: A fault has occurred during the Lq-Ld measurement. Fault value (r0949): 10: Current ratio too low. 12: Maximum current exceeded. 15: Second harmonic too low. 16: Drive converter too small. Remedy:
|
| F07969 Drive: Incorrect pole position identification | Cause: A fault has occurred during the pole position identification routine. Fault value (r0949): 1: Current controller limited. 2: Motor shaft locked. 10-18: Measurement issues (current too low, harmonic too low, etc). 20: Pole position ID requested with rotating motor. Remedy:
|
| A07975 (N) Drive: Travel to the zero mark – setpoint input expected | Cause: The zero mark must be evaluated in order to adjust the encoder. It is expected that a speed or torque setpoint is entered. Remedy:
|
| A07980 Drive: Rotating measurement activated | Cause: The rotating measurement (automatic speed controller optimization) is activated. The rotating measurement is carried out at the next switch-on command. Remedy:
|
| A07981 Drive: Enable signals for the rotating measurement missing | Cause: The rotating measurement cannot be started due to missing enable signals. – enable signals for the ramp-function generator missing. – enable signals for the speed controller integrator missing. Remedy:
|
| F07982 Drive: Rotating measurement encoder test | Cause: A fault has occurred during the encoder test. Fault value (r0949): 1: Speed did not reach steady-state. 2-4: Speed setpoint not reached (limits active). 5: Encoder does not supply signal. 6-8: Polarity, pulse number, or noise issues. Remedy:
|
| F07983 Drive: Rotating measurement saturation characteristic | Cause: A fault has occurred while determining the saturation characteristic. Fault value (r0949): 1-2: Speed/Flux did not reach steady-state. 3-4: Adaptation circuit issues. 6-8: Speed setpoint not approached due to limits. Remedy:
|
| F07984 Drive: Speed controller optimization, moment of inertia | Cause: A fault has occurred while identifying the moment of inertia. Fault value (r0949): 1: Speed did not reach steady-state. 2-7: Speed setpoint not approached due to limits. 8-11: Torque difference/Data issues. Remedy:
|
| F07985 Drive: Speed controller optimization (oscillation test) | Cause: A fault has occurred during the vibration test. Fault value (r0949): 1: Speed did not reach steady-state. 2-4: Speed setpoint not approached due to limits. 5: Torque limits too low. 6: No suitable speed controller setting found. Remedy:
|
| 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: For fault value = 1: 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). See also: p1959 (Rotating measurement configuration). |
| F07990 Drive: Incorrect motor data identification | Cause: A fault has occurred during the identification routine. Fault value (r0949, interpret decimal): 1: Current limit value reached. 2: Identified stator resistance lies outside the expected range 0.1 … 100% of Zn. 3: Identified rotor resistance lies outside the expected range 0.1 … 100% of Zn. 4: identified stator reactance lies outside the expected range 50 … 500 % of Zn. 5: identified magnetizing reactance lies outside the expected range 50 … 500 % of Zn. 6: Identified rotor time constant lies outside the expected range 10 ms … 5 s. 7: identified total leakage reactance lies outside the expected range 4 … 50 % of Zn. 8: Identified stator leakage reactance lies outside the expected range 2 … 50% of Zn. 9: Identified rotor leakage reactance lies outside the expected range 2 … 50% of Zn. 10: Motor has been incorrectly connected. 11: Motor shaft rotates. 12: Ground fault detected. 15: Pulse inhibit occurred during motor data identification. 20: Identified threshold voltage of the semiconductor devices lies outside the expected range 0 … 10 V. 30: Current controller in voltage limiting. 40: At least one identification contains errors. Remedy: For fault value = 1 … 40:
For fault value = 4, 7:
For fault value = 11:
For fault value = 12:
|
| 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 switch-on command. If rotating measurement is selected, it will not be possible to save parameter assignment until completed. 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 (see r0051) if vector control is parameterized (p1300 >= 20) and motor data ID is pending. 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. – bus connection interrupted. – controller switched off. – controller set into the STOP state. 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): 2: Too many PZD data words. 3: Uneven number of bytes. 501: PROFIsafe parameter error (e.g. F_dest). 502: PROFIsafe telegram does not match. Remedy: Check the receive configuration data. For alarm value = 2: – check the number of data words for output and input. For alarm value = 501: – check the set PROFIsafe address (p9610). For alarm value = 502: – Check the enable of F-DI (p9501.30). |
| 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). |
| A08564 PN/COMM BOARD: syntax error in the configuration file | Cause: A syntax error has been detected in the ASCII configuration file for the Communication Board Ethernet. The saved configuration file has not been loaded. Remedy:
|
| A08565 PROFINET: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration (p8925). Alarm value (r2124): 0: general consistency error 1: error in IP configuration 2: Error in station names 3: DHCP not able to be activated 4: cyclic PROFINET connection not possible as DHCP is activated. Remedy:
|
| A08760 CAN: maximum size of the IF PZD exceeded | Cause: The maximum size of the IF PZD was exceeded. 1: error for IF PZD receive. 2: error for IF PZD send. Remedy: Map fewer process data in PDO. Apply one of the following options to delete the alarm:
|
| A08800 PROFIenergy energy-saving mode active | Cause: The PROFIenergy energy-saving mode is active. See also: r5600 (Pe energy-saving mode ID). Remedy: The alarm is automatically withdrawn when the energy-saving mode is exited. The energy-saving mode is exited after:
|
| A08802 PROFIenergy not possible to switch off incremental encoder supply | Cause: The incremental encoder is used for the closed-loop position control. It cannot be switched off during PROFIenergy mode or it would lose position. Remedy: The alarm is automatically withdrawn 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 and an error occurred. Fault value (r0949): 0: Memory card not inserted. 1: Invalid memory card (not SIEMENS). 2: Invalid memory card. 3: Memory card used in another Control Unit. 12: Invalid memory card (OEM input incorrect). 13: Memory card used in another Control Unit (OEM input incorrect). Remedy: For fault value = 0, 1:
For 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. 0: A memory card is not inserted. 1: An invalid memory card is inserted (not SIEMENS). Remedy:
|
| F13102 Know-how protection: Consistency error of the protected data | Cause: An error was identified when checking the consistency of the protected files. The project on the memory card cannot be run. xxxx = 1: A file has a checksum error. xxxx = 2: The files are not consistent with one another. xxxx = 3: The project files loaded into the file system are inconsistent. Remedy:
|
| F30001 Power unit: Overcurrent | Cause: The power unit has detected an overcurrent condition. – closed-loop control is incorrectly parameterized. – motor has a short-circuit or fault to ground. – U/f operation: Up ramp set too low. – U/f operation: rated current of motor much greater than that of power unit. – missing line reactor. – power cables not correctly connected. – power unit defective. Remedy:
|
| F30002 Power unit: DC link voltage overvoltage | Cause: The power unit has detected an overvoltage condition in the DC link. – motor regenerates too much energy. – line supply voltage too high. – DC link voltage control switched off. – dynamic response of DC link voltage controller excessive or insufficient. Remedy:
|
| F30003 Power unit: DC link voltage undervoltage | Cause: The power unit has detected an undervoltage condition in the DC link. – line supply failure. – line supply voltage below the permissible value. – line phase interrupted. Remedy:
See also: p0210 (Drive unit line supply voltage). |
| F30004 Power unit: Overtemperature heat sink AC inverter | Cause: The temperature of the power unit heat sink has exceeded the permissible limit value. – Insufficient cooling, fan failure. – Overload. – Ambient temperature too high. – pulse frequency too high. Remedy:
|
| F30005 Power unit: Overload I2t | Cause: The power unit was overloaded (r0036 = 100 %). – the permissible rated power unit current was exceeded for an inadmissibly long time. – the permissible load duty cycle was not maintained. 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: – a line phase has failed. – the 3 line phases are inadmissibly asymmetrical. – the fuse of a phase of a main circuit has ruptured. – a motor phase has failed. Remedy:
|
| F30015 (N, A) Power unit: Phase failure motor cable | Cause: A phase failure in the motor feeder cable was detected. Can occur if the motor is correctly connected but drive stalled in U/f control, or control is unstable. Remedy:
|
| A30016 (N) Power unit: Load supply switched off | Cause: The DC link voltage is too low. 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. – closed-loop control is incorrectly parameterized. – fault in the motor or in the power cables. – the power cables exceed the maximum permissible length. – motor load too high. – power unit defective. Remedy:
|
| F30021 Power unit: Ground fault | Cause: The power has detected a ground fault. – ground fault in the power cables. – ground fault at the motor. – CT defective. – short-circuit at the braking resistor. Remedy:
See also: p0287 (Ground fault monitoring thresholds). |
| 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. – fiber-optic cable interrupted. – power supply of the IGBT gating module missing. – short-circuit at the power unit output. – defective semiconductor in the power unit. Remedy:
|
| F30024 Power unit: Overtemperature thermal model | Cause: The temperature difference between the heat sink and chip has exceeded the permissible limit value. – the permissible load duty cycle was not maintained. – Insufficient cooling, fan failure. – Overload. – Ambient temperature too high. – pulse frequency too high. Remedy:
|
| F30025 Power unit: Chip overtemperature | Cause: The chip temperature of the semiconductor has exceeded the permissible limit value. (Similar causes to F30024: overload, cooling, pulse frequency). Remedy:
|
| F30027 Power unit: Precharging DC link time monitoring | Cause: The power unit DC link was not able to be precharged within the expected time. 1) There is no line supply voltage connected. 2) The line contactor/line side switch has not been closed. 3) The line supply voltage is too low. 4) Line supply voltage incorrectly set (p0210). 5) The precharging resistors are overheated. 6) The precharging resistors are overheated (DC link capacitance too high). 7) The DC link has either a ground fault or a short-circuit. 8) Precharging circuit may be defective. Remedy: In general:
For 5): Observe permissible precharging frequency. For 6): Check the capacitance of the DC link and reduce if necessary. For 7): Check the DC link for a ground fault or short circuit. |
| 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. – closed-loop control is incorrectly parameterized. – fault in the motor or in the power cables. – motor load too high. – power unit defective. 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. (Same causes as A30031). Remedy: (Same remedy as A30031). |
| 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. (Same causes as A30031). Remedy: (Same remedy as A30031). |
| A30034 Power unit: Internal overtemperature | Cause: The alarm threshold for internal overtemperature has been reached. – ambient temperature might be too high. – Insufficient cooling, fan failure. 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. Alarm value (r2124): Bit 0: heat sink fan Bit 8: internal device fan Remedy: For the fan involved, carry out the following:
|
| F30051 Power unit: Motor holding brake short circuit detected | Cause: A short-circuit at the motor holding brake terminals has been detected. Remedy:
|
| F30052 EEPROM data error | Cause: EEPROM data error of the power unit module. The EEPROM data read in from the power unit module is inconsistent or not compatible. Remedy: Replace power unit module. |
| A30054 (F, N) 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 21.4 V. Remedy: Check the 24 V voltage for stability and value. |
| 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. Remedy:
|
| A30065 (F, N) Voltage measured values not plausible | Cause: The voltage measurement is not supplying any plausible values. Remedy:
|
| F30068 Power unit: undertemperature inverter heat sink | Cause: The actual inverter heat sink temperature is below the permissible minimum value. Remedy:
|
| 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. Fault value (r0949): 0: CU with external 24 V supply withdrawn during operation. 1: CU withdrawn during operation (with encoderless safe motion monitoring enabled). 20A: CU inserted on a PM with another code number. 20B: CU inserted on a PM with the same code number but different serial number. Remedy:
|
| F30075 Configuration of the power unit unsuccessful | Cause: A communication error has occurred while configuring the power unit using the Control Unit. Remedy:
|
| F30080 Power unit: Current increasing too quickly | Cause: The power unit has detected an excessive rate of rise in the overvoltage range. – closed-loop control is incorrectly parameterized. – motor has a short-circuit or fault to ground. – power unit defective. Remedy:
|
| F30081 Power unit: Switching operations too frequent | Cause: The power unit has executed too many switching operations for current limitation. – closed-loop control is incorrectly parameterized. – motor has a short-circuit or fault to ground. – U/f operation: Up ramp set too low. Remedy:
|
| F30105 PU: Actual value sensing fault | Cause: At least one incorrect actual value channel was detected on the Power Stack Adapter (PSA). 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. – device connection voltage too high. – line reactor incorrectly dimensioned. 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. – forced checking procedure (test stop) unsuccessful. – subsequent response to fault F30611. 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 data cross-check between the two monitoring channels and has initiated a STOP F. Fault value (r0949) indicates detailed cause (e.g. 1000 = Watchdog timer expired, 2000 = Status of STO selection diff). Remedy: For fault values 1 … 999: Check cross data comparison. For fault value = 1000: Check wiring of F-DI. For fault value = 1001, 1002: Carry out POWER ON. For fault value = 2000, 2001, 2002, 2003: Check discrepancy time and wiring of F-DI. Refer to the description of the message values in safety fault F01611. |
| 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. Note: This message does not result in a safety stop response. Remedy:
Note: STO: Safe Torque Off |
| 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. – there is a communication error between processor 1 and processor 2 or communication has failed. – a time slice overflow of the safety software has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| F30649 SI P2: Internal software error | Cause: An internal error in the Safety Integrated software on processor 2 has occurred. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F30650 SI P2: Acceptance test required | Cause: The drive-integrated “Safety Integrated” function on processor 2 requires an acceptance test. Note: This fault results in a STOP A that can be acknowledged. Fault value (r0949, interpret decimal): 130: Safety parameters for processor 2 not available. 1000: Reference and actual checksum on processor 2 are not identical (booting). 2000: Reference and actual checksum on processor 2 are not identical (commissioning mode). 2003: Acceptance test is required as a safety parameter has been changed. 2010: Enable of safety-related brake control between the two monitoring channels differ. 9999: Subsequent response of another safety-related fault. Remedy:
|
| 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 routine was unsuccessful. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| 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. – there is a communication error between processor 1 and processor 2 or communication has failed. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. 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. Note: This fault results in a STOP A that can be acknowledged. Fault value (r0949, interpret decimal): 129: Safety parameters for processor 2 corrupted. 131: Internal software error on processor 1. 255: Internal software error on processor 2. 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. Fault value (r0949, interpret decimal): 10: Attempt to enable STO function although not supported. 15: Attempt to enable motion monitoring functions although not supported. 16: Attempt to enable PROFIsafe communications although not supported. 18: Attempt to enable PROFIsafe function for Basic Functions although not supported. 20: Attempt to simultaneously enable drive-integrated motion monitoring via integrated F-DI and STO via terminals. 28: Attempt to enable “STO via terminals at the Power Module” although not supported. Remedy:
Note: F-DI: Failsafe Digital Input, STO: Safe Torque Off. |
| F30662 Error in internal communications | Cause: A module-internal communication error has occurred. Fault value (r0949): Only for internal Siemens troubleshooting. Remedy:
|
| F30664 Error while booting | Cause: An error has occurred during booting. Fault value (r0949): Only for internal Siemens troubleshooting. 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): 200000 hex, 400000 hex (fault in actual booting/operation, defect before last boot). Remedy:
|
| A30666 (F) SI Motion P2: Steady-state (static) 1 signal at the F-DI for safe acknowledgment | Cause: A logical 1 signal is present at the F-DI configured in p10106 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. Remedy:
|
| F30680 SI Motion P2: Checksum error safety monitoring functions | Cause: The actual checksum calculated by processor 2 and entered in r9398 does not match the reference checksum saved in p9399. Fault value (r0949): 0: Checksum error for SI parameters for motion monitoring. 1: Checksum error for SI parameters for component assignment. Remedy:
|
| F30681 SI Motion P2: Incorrect parameter value | Cause: The parameter cannot be parameterized with this value. Fault value (r0949): yyyyxxxx dec (yyyy = supplementary info, xxxx = parameter) xxxx = 9301: Not permissible to enable function “n < nx hysteresis and filtering". xxxx = 9385: For Safety without encoder and synchronous motor, p9385 must be set to 4. Remedy:
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. Fault value (r0949): 1: SLP not supported. 2: SCA not supported. 3: SLS override not supported. 4: External ESR activation not supported. 5: F-DI in PROFIsafe not supported. 6: Enable actual value synchronization not supported. 9: Monitoring function not supported by firmware or enable bit not used. 24: Monitoring function SDI not supported. Remedy:
|
| 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. Remedy:
|
| F30692 SI Motion P2: Parameter value not permitted for encoderless | Cause: For encoderless motion monitoring functions, the parameter cannot be parameterized with this value. Fault value (r0949): Parameter number with the incorrect value. Remedy:
|
| 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): Parameter number of the safety parameter which has changed. Remedy:
|
| F30700 SI Motion P2: STOP A initiated | Cause: The drive is stopped via a STOP A (pulse cancellation via the safety switch-off signal path of processor 1). Possible causes: Stop request from processor 1, Pulses not suppressed after test stop selection, Subsequent response to other messages (C30706, C30714, C30701). Remedy:
|
| F30701 SI Motion P2: STOP B initiated | Cause: The drive is stopped via a STOP B (braking along the OFF3 deceleration ramp). As a result, after speed threshold in p9360 is fallen below, message C30700 “STOP A initiated” is output. Possible causes: Stop request from processor 1, Subsequent response to C30714, C30711, C30707. Remedy:
|
| A30706 SI Motion P2: SAM/SBR limit exceeded | Cause: SAM (Safe Acceleration Monitor): velocity exceeded tolerance after STOP B (SS1). SBR (Safe Brake Ramp): speed exceeded tolerance after STOP B (SS1) or SLS changeover. Drive is shut down by message C30700 “SI Motion P2: STOP A initiated”. Remedy:
|
| A30711 SI Motion P2: Defect in a monitoring channel | Cause: When cross-comparing the two monitoring channels, the drive detected a difference. Message value (r2124): 0…999: Number of cross-compared data. 1000: Watchdog timer expired. 1040: Pulses suppressed with active encoderless monitoring functions. 1041: Current absolute value too low (encoderless). (See manual for full list) Remedy:
|
| A30712 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. Safety message C30711 with value 0 is also displayed. Remedy:
|
| A30714 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. Message value (r2124): 100: SLS1 exceeded, 200: SLS2 exceeded, etc. Remedy:
|
| A30716 SI Motion P2: Tolerance for safe motion direction exceeded | Cause: The tolerance for the “safe motion direction” function was exceeded. The drive is stopped. Message value (r2124): 0: Positive direction exceeded, 1: Negative direction exceeded. Remedy:
|
| F30770 SI Motion P2: Discrepancy error affecting the failsafe inputs | Cause: The Failsafe Digital Inputs (F-DI) show a different state longer than that parameterized in p10002 / p10102. Fault value (r0949): Bit 0: Discrepancy error for F-DI 0, Bit 1: Discrepancy error for F-DI 1. Remedy:
Note: Check p10102 (discrepancy time) settings relative to cyclic switching pulse and debounce time (p10117). |
| A30772 SI Motion P2: Test stop for Failsafe Digital Outputs running | Cause: The forced checking procedure (test stop) for the Failsafe Digital Outputs is currently in progress. Remedy:
|
| F30773 SI Motion P2: Test stop Failsafe Digital Output error | Cause: A fault has occurred on processor 2 during the forced checking procedure (test stop) of the Failsafe Digital Output. Fault value (r0949): RRRVWXYZ hex (Diagnostic codes for Reserved, Actual State, Required State, Channel, Reason, State). (See manual for detailed breakdown of hex codes) Remedy:
|
| A30788 Automatic test stop: wait for STO deselection via SMM | Cause: The automatic test stop was not able to be carried out after powering up because STO is selected or a safety message is present. Remedy:
|
| A30798 SI Motion P2: Test stop for motion monitoring functions running | Cause: The forced checking procedure (test stop) for the safe motion monitoring functions is currently in progress. Remedy:
|
| A30799 SI Motion P2: Acceptance test mode active | Cause: The acceptance test mode is active. Remedy:
|
| N30800 (F) Power unit: Group signal | Cause: The power unit has detected at least one fault. Remedy:
|
| F30802 Power unit: Time slice overflow | Cause: A time slice overflow has occurred. Fault value (r0949): xx = Time slice number. Remedy:
|
| F30804 (N, A) Power unit: CRC | Cause: A checksum error (CRC error) has occurred for the power unit. Remedy:
|
| F30805 Power unit: EEPROM checksum error | Cause: Internal parameter data is corrupted. Fault value (r0949): 01: EEPROM access error, 02: Too many blocks. Remedy:
|
| F30809 Power unit: Switching information not valid | Cause: For 3P gating unit: Last switching status word in setpoint telegram not identified by end ID. 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. Remedy:
|
| F30903 Power unit: I2C bus error occurred | Cause: Communications error with an EEPROM or an analog/digital converter. Fault value (r0949): 80000000 hex (internal sw error), 00000001…0000FFFF hex (module fault). Remedy:
|
| A30920 (F) Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124): 1: Wire breakage/sensor not connected, 2: Measured resistance too low. Remedy:
|
| F30950 Power unit: Internal software error | Cause: An internal software error has occurred. Fault value (r0949): Information about the fault source. 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 (firmware on component is more recent). Remedy:
|
| F31100 (N, A) Encoder 1: Zero mark distance error | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. Fault value (r0949): Last measured zero mark distance in increments. Remedy:
|
| F31101 (N, A) Encoder 1: Zero mark failed | Cause: The 1.5 x parameterized zero mark distance was exceeded. Remedy:
|
| F31103 (N, A) Encoder 1: Amplitude error track R | Cause: The amplitude of the reference track signal (track R) does not lie within the tolerance bandwidth for encoder 1. Fault value (r0949): Signal level, track R. Remedy:
|
| F31118 (N, A) Encoder 1: Speed difference outside the tolerance range | Cause: For an HTL/TTL encoder, the speed difference has exceeded the value in p0492 over several sampling cycles. Remedy:
|
| F31131 (N, A) Encoder 1: Deviation position incremental/absolute too large | Cause: When cyclically reading the absolute position, an excessively high difference to the incremental position was detected. Fault value (r0949): Deviation in quadrants. Remedy:
|
| F31150 (N, A) Encoder 1: Initialization error | Cause: Encoder functionality selected in p0404 is not operating correctly. Fault value (r0949): Bit assignment corresponds to p0404 (e.g. bit 5 set: Error track C/D). Remedy:
|
| F31153 (N, A) Encoder 1: Identification error | Cause: An error has occurred when identifying the encoder (waiting) p0400 = 10100. Remedy:
|
| A31400 (F, N) Encoder 1: Alarm threshold zero mark distance error | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. Alarm value (r2124): Last measured zero mark distance in increments. Remedy:
|
| A31401 (F, N) Encoder 1: Alarm threshold zero mark failed | Cause: The 1.5 x parameterized zero mark distance was exceeded. Alarm value (r2124): Number of increments after POWER ON. Remedy:
|
| A31418 (F, N) Encoder 1: Speed difference per sampling rate exceeded | Cause: For an HTL/TTL encoder, the speed difference between two sampling cycles has exceeded the value in p0492. Remedy:
|
| A31422 (F, N) Encoder 1: Pulses per revolution square-wave encoder outside tolerance bandwidth | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. Triggered with active square-wave encoder PPR correction. Remedy:
|
| A31431 (F, N) Encoder 1: Deviation position incremental/absolute too large | Cause: When the zero pulse is passed, a deviation in the incremental position was detected. Remedy:
|
| F31802 (N, A) Encoder 1: Time slice overflow | Cause: A time slice overflow has occurred in encoder 1. Remedy:
Note: For a current controller sampling time = 31.25 µs, use an SMx20 with order number 6SL3055-0AA00-5xA3. |
| F31805 (N, A) Encoder 1: EEPROM checksum error | Cause: Internal parameter data is corrupted. Fault value (r0949): 01: EEPROM access error, 02: Too many blocks. Remedy:
|
| F31850 (N, A) Encoder 1: Encoder evaluation internal software error | Cause: An internal software error has occurred in the Sensor Module of encoder 1. Fault value (r0949, interpret decimal):
See also: p0491 (Motor encoder fault response ENCODER) Remedy:
|
| F31899 (N, A) Encoder 1: Unknown fault | Cause: A fault occurred on the Sensor Module for encoder 1 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. Fault value (r0949, interpret decimal): Fault number. See also: p0491 (Motor encoder fault response ENCODER) Remedy:
|
| F31905 (N, A) Encoder 1: Parameterization error | Cause: A parameter of encoder 1 was detected as being incorrect. It is possible that the parameterized encoder type does not match the connected encoder. Fault value (r0949, interpret decimal):
See also: p0491 (Motor encoder fault response ENCODER) Remedy:
|
| A31915 (F, N) Encoder 1: Configuration error | Cause: The configuration for encoder 1 is incorrect. Alarm value (r2124, interpret decimal):
Remedy:
|
| 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. The diagnostics data is saved in the folder: /USER/SINAMICS/DATA/… Remedy: Not necessary. The alarm disappears automatically. The data logger is ready to record the next fault case. |
| F31950 Encoder 1: Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal) contains information regarding the fault source. Only for internal Siemens troubleshooting. Remedy:
|
| A31999 (F, N) Encoder 1: Unknown alarm | Cause: A alarm has occurred on the Sensor Module for encoder 1 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. Remedy:
|
| F32110 (N, A) Encoder 2: Serial communications error | Cause: Serial communication protocol transfer error between the encoder and evaluation module. Fault value (r0949, interpret binary):
Remedy:
|
| F32111 (N, A) Encoder 2: Absolute encoder internal fault | Cause: The absolute encoder fault word supplies fault bits that have been set. Fault value (r0949, interpret binary): yyyyxxxx hex. yyyy = 0:
yyyy = 1:
Remedy:
|
| F32112 (N, A) Encoder 2: Error bit set in the serial protocol | Cause: The encoder sends a set error bit via the serial protocol. Fault value (r0949, interpret binary): Bit 0 = Fault bit in the position protocol. Remedy: In the case of an EnDat encoder, F31111 may provide further details. |
| F32150 (N, A) Encoder 2: Initialization error | Cause: Encoder functionality selected in p0404 is not operating correctly. Fault value (r0949): Encoder malfunction. Remedy:
|
| F32153 (N, A) Encoder 2: Identification error | Cause: An error has occurred when identifying the encoder (waiting) p0400 = 10100. The connected encoder was not able to be identified. Remedy: Manually configure the encoder according to the data sheet. |
| A32410 (F, N) Encoder 2: Serial communications | Cause: Serial communication protocol transfer error between the encoder and evaluation module. Alarm value (r2124, interpret binary): Bits 0-12 (similar to F32110). Remedy:
|
| A32411 (F, N) Encoder 2: Absolute encoder signals internal alarms | Cause: The absolute encoder fault word includes alarm bits that have been set. Alarm value (r2124):
Remedy: Replace encoder. |
| A32412 (F, N) Encoder 2: Error bit set in the serial protocol | Cause: The encoder sends a set error bit via the serial protocol. Alarm value (r2124): Bit 0: Fault bit; Bit 1: Alarm bit. Remedy:
|
| 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 multiturn information can no longer be buffered if the battery voltage drops even further. Remedy: Replace battery. |
| F32802 (N, A) Encoder 2: Time slice overflow | Cause: A time slice overflow has occurred in encoder 2. Fault value (r0949):
Remedy: Increase the current controller sampling time. Note: For a current controller sampling time = 31.25 µs, use an SMx20 with order number 6SL3055-0AA00-5xA3. |
| F32805 (N, A) Encoder 2: EEPROM checksum error | Cause: Internal parameter data is corrupted. Remedy: Replace the module. |
| F32850 (N, A) Encoder 2: Encoder evaluation internal software error | Cause: An internal software error has occurred in the Sensor Module of encoder 2. Fault value (r0949): (Same codes as F31850). Remedy:
|
| F32899 (N, A) Encoder 2: Unknown fault | Cause: A fault occurred on the Sensor Module for encoder 2 that cannot be interpreted by the Control Unit firmware. Remedy:
|
| F32905 (N, A) Encoder 2: Parameterization error | Cause: A parameter of encoder 2 was detected as being incorrect. Fault value (r0949): (Same codes as F31905). Remedy:
|
| A32915 (F, N) Encoder 2: Configuration error | Cause: The configuration for encoder 2 is incorrect. Alarm value (r2124): 1: Re-parameterization not permissible; 419: Fine resolution issue. Remedy:
|
| A32930 (N) Encoder 2: Data logger has saved data | Cause: Data logger saved data to memory card. Remedy: Not necessary. |
| F32950 Encoder 2: Internal software error | Cause: An internal software error has occurred. Remedy:
|
| A32999 (F, N) Encoder 2: Unknown alarm | Cause: Alarm on Sensor Module cannot be interpreted by Control Unit firmware. Remedy: Replace/upgrade firmware. |
| 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):
Remedy: Check the configuration of the PROFINET controllers as well as the p8929 setting. |
| A50010 (F) PROFINET: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration (p8925) for the PROFINET interface. Alarm value (r2124): 0: general error; 1: IP config error; 2: Station name error; 3: DHCP not activated (connection exists); 4: Cyclic connection not possible (DHCP activated). Remedy:
|
| A50011 (F) Ethernet/IP: configuration error | Cause: An EtherNet/IP controller attempts to establish a connection using an incorrect configuring telegram. The telegram length set in the controller does not match the parameterization in the drive device. Remedy: Check the set telegram length. For p0922 not equal to 999, the length of the selected telegram applies. For p0922 = 999, the maximum interconnected PZD (r2067) applies. |
| 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 runtime group rejected | Cause: When the runtime groups of the free function blocks attempted to log on with the sampling time management, the logon of at least one runtime group was rejected. 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. 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 (switch-off/switch-on) for the Control Unit involved. |
| F50518 FBLOCKS: Sampling time of free runtime group differs at download | Cause: In the STARTER/SCOUT project that was downloaded, the hardware sampling time of a free runtime group was set to a value that was either too low or too high. Remedy:
|