Siemens G130-G150 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 during an operation with the FloatingPoint data type. The error may be caused by the basic system or a technology function (e.g. FBLOCKS, DCC, TEC). Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. 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 Firmware download for DRIVE-CLiQ component unsuccessful | Cause: It was not possible to download the firmware to a DRIVE-CLiQ component. Fault value (r0949, interpret hexadecimal): yyxxxx hex: yy = component number, xxxx = fault cause Remedy:
|
| A01006 Firmware update for DRIVE-CLiQ component required | Cause: The firmware of a DRIVE-CLiQ component must be updated as there is no suitable firmware or firmware version in the component for operation with the Control Unit. Remedy: Firmware update using the commissioning software or via parameter. |
| A01007 POWER ON for DRIVE-CLiQ component required | Cause: A DRIVE-CLiQ component must be switched on again (POWER ON) (e.g. due to a firmware update). Remedy:
|
| A01009 (N) CU: Control module overtemperature | Cause: The temperature (r0037[0]) of the control module (Control Unit) has exceeded the specified limit value. Remedy:
|
| F01010 Drive type unknown | Cause: An unknown drive type was found. Remedy:
|
| F01011 (N) Download interrupted | Cause: The project download was interrupted. Remedy:
|
| F01012 (N) Project conversion error | Cause: When converting the project of an older firmware version, an error occurred. Remedy: Check the parameter indicated in the fault value and correctly adjust it accordingly. |
| F01015 Internal software error | Cause: An internal software error has occurred. Remedy:
|
| A01016 (F) Firmware changed | Cause: At least one firmware file in the directory was illegally changed on the non-volatile memory with respect to the version when shipped from the factory. Remedy: For the non-volatile memory for the firmware (memory card/device memory), restore the delivery condition. |
| A01017 Component lists changed | Cause: On the memory card, one file in the directory /SIEMENS/SINAMICS/DATA or /ADDON/SINAMICS/DATA has been illegally changed with respect to that supplied from the factory. Remedy: For the file on the memory card involved, restore the status originally supplied from the factory. |
| A01020 Writing to RAM disk unsuccessful | Cause: A write access to the internal RAM disk was unsuccessful. Remedy: Adapt the file size for the system logbook to the internal RAM disk (p9930). |
| F01023 Software timeout (internal) | Cause: An internal software timeout has occurred. 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. Remedy: Set the monitoring time higher at the PC or, if required, completely disable the monitoring function. |
| F01031 Sign-of-life failure for OFF in REMOTE | Cause: With the “OFF in REMOTE” mode active, no sign-of-life was received within 3 seconds. Remedy:
|
| A01032 (F) ACX: all parameters must be saved | Cause: The parameters of an individual drive object were saved (p0971 = 1), although there is still no backup of all drive system parameters. Remedy: Save all parameters (p0977 = 1 or “copy RAM to ROM”). |
| 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. Remedy: Set the value of the reference parameter to a number different than 0.0. |
| 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. 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. Remedy: If you have saved the project data using the commissioning software, carry out a new download for your project. Save using the function “Copy RAM to ROM” or with p0977 = 1. |
| 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. Remedy:
|
| F01039 (A) ACX: Writing to the parameter back-up file was unsuccessful | Cause: Writing to at least one parameter back-up file PSxxxyyy.*** in the non-volatile memory was unsuccessful. Remedy:
|
| F01040 Save parameter settings and carry out a POWER ON | Cause: A parameter was changed in the drive system which means that it is necessary to save the parameters and re-boot. Remedy:
|
| F01041 Parameter save necessary | Cause: Defective or missing files were detected on the memory card when booting. 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). Remedy:
|
| F01043 Fatal error at project download | Cause: A fatal error was detected when downloading a project using the commissioning software. Remedy:
|
| F01044 CU: Descriptive data error | Cause: An error was detected when loading the descriptive data saved in the non-volatile memory. Remedy: Replace the memory card or Control Unit. |
| A01045 CU: Configuring data invalid | Cause: An error was detected when evaluating the parameter files saved in the non-volatile memory. Remedy:
|
| A01049 CU: It is not possible to write to file | Cause: It is not possible to write into a write-protected file (PSxxxxxx.acx). Remedy: Check whether the “write protected” attribute has been set for the files in the non-volatile memory. When required, remove write protection and save again. |
| F01050 Memory card and device incompatible | Cause: The memory card and the device type do not match. Remedy:
|
| F01054 CU: System limit exceeded | Cause: At least one system overload has been identified. Remedy: For fault value = 1, 5:
|
| F01055 CU: Internal error (SYNO of port and application not identical) | Cause: All applications that operate with slaves at one port must be derived from the same SYNO clock cycle. Remedy: Contact Technical Support. |
| F01056 CU: Internal error (clock cycle of parameter group already assigned differently) | Cause: The requested parameter group is already being used in a different clock cycle. Remedy: Contact Technical Support. |
| F01057 CU: Internal error (different DRIVE-CLiQ type for the slave) | Cause: The requested DRIVE-CLiQ type has been specified differently for the same slave component. Remedy: Contact Technical Support. |
| F01058 CU: Internal error (slave missing in topology) | Cause: The requested slave component does not exist in the topology. Remedy: Contact Technical Support. |
| F01059 CU: Internal error (port does not exist) | Cause: The port object assigned according to the topology of the requested slave component does not exist. Remedy: Contact Technical Support. |
| F01060 CU: Internal error (parameter group not available) | Cause: The requested parameter group is not offered by this slave type. Remedy: Contact Technical Support. |
| F01061 CU: Internal error (application not known) | Cause: An application that is not registered with TSM has attempted to register with registerSlaves(). Remedy: Contact Technical Support. |
| F01063 CU: Internal error (PDM) | Cause: An internal software error has occurred. Remedy: Contact Technical Support. |
| A01064 (F) CU: Internal error (CRC) | Cause: A checksum error (CRC error) has occurred in the Control Unit program memory. Remedy:
|
| F01068 CU: Data memory memory overflow | Cause: The utilization for a data memory area is too large. Remedy:
|
| A01069 Parameter backup and device incompatible | Cause: The parameter backup on the memory card and the drive unit do not match. Remedy:
|
| F01070 Project/firmware is being downloaded to the memory card | Cause: An upgrade (project/firmware download) was initiated on the memory card. Remedy: Not necessary. The fault is automatically withdrawn after the upgrade has been completed. |
| F01072 Memory card restored from the backup copy | Cause: The Control Unit was switched-off while writing to the memory card. Remedy: Check that the firmware and parameterization is up-to-date. |
| 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. Remedy:
|
| F01082 Parameter error when powering up from data backup | Cause: Parameterizing errors have been detected (e.g. incorrect parameter value). Remedy:
|
| A01099 (N) UTC synchronization tolerance violated | Cause: The tolerance (p3109) set for UTC synchronization was violated. Remedy: Select the synchronization intervals shorter so that the deviation lies within the tolerance. |
| A01100 CU: Memory card withdrawn | Cause: The memory card (non-volatile memory) was withdrawn during operation. Remedy:
|
| F01105 (A) CU: Insufficient memory | Cause: Too many functions have been configured on this Control Unit. Remedy:
|
| F01106 CU: Insufficient memory | Cause: There is not sufficient free memory space available. Remedy: Not necessary. |
| F01107 CU: Save to memory card unsuccessful | Cause: A data save in the non-volatile memory was not able to be successfully carried out. Remedy:
|
| F01110 CU: More than one SINAMICS G on one Control Unit | Cause: More than one SINAMICS G type power unit is being operated from the Control Unit. Remedy: Only one SINAMICS G drive type is permitted. |
| F01111 CU: Mixed operation of drive units illegal | Cause: Illegal operation of various drive units on one Control Unit. Remedy: Only power units of one particular drive type may be operated with one Control Unit. |
| F01112 CU: Power unit not permissible | Cause: The connected power unit cannot be used together with this Control Unit. Remedy: Replace the power unit that is not permissible by a component that is permissible. |
| F01120 (A) Terminal initialization has failed | Cause: An internal software error occurred while the terminal functions were being initialized. 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: Reduce the frequency of the pulses at the measuring probe input. |
| F01150 CU: Number of instances of a drive object type exceeded | Cause: The maximum permissible number of instances of a drive object type was exceeded. Remedy:
|
| F01151 CU: Number of drive objects of a category exceeded | Cause: The maximum permissible number of drive objects of a category was exceeded. Remedy:
|
| F01152 CU: Invalid constellation of drive object types | Cause: It is not possible to simultaneously operate drive object types SERVO, VECTOR and HLA. Remedy:
|
| F01200 CU: Time slice management internal software error | Cause: A time slice management error has occurred. Remedy:
|
| F01205 CU: Time slice overflow | Cause: Insufficient processing time is available for the existing topology. Remedy:
|
| F01221 CU: Bas clk cyc too low | Cause: The closed-loop control / monitoring cannot maintain the envisaged clock cycle. Remedy: Increase the basic clock cycle of DRIVE-CLiQ communication. |
| F01222 CU: Basic clock cycle too low (computing time for communication not available) | Cause: A time slice has not been defined that fulfills the requirements. Remedy: Contact Technical Support. |
| A01223 CU: Sampling time inconsistent | Cause: When changing a sampling time, inconsistency between the clock cycles has been identified. Remedy:
|
| A01224 CU: Pulse frequency inconsistent | Cause: When changing the minimum pulse frequency (p0113) inconsistency between the pulse frequencies was identified. Remedy: Set a valid pulse frequency. |
| 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: For alarm value r2124 < 256, carry out a POWER ON and/or replace the Control Unit. For alarm value >=256, clear the fault memory or replace the Control Unit. |
| F01255 CU: Option Board EEPROM read-only data error | Cause: Error when reading the read-only data of the EEPROM in the Option Board. Remedy:
|
| A01256 CU: Option Board EEPROM read-write data error | Cause: Error when reading the read-write data of the EEPROM in the Option Board. Remedy:
|
| A01302 Error in the component trace | Cause: An error has occurred in the component trace. Remedy: For alarm value = 1: Upgrade the firmware of the DRIVE-CLiQ component involved. |
| F01303 Component does not support the required function | Cause: A function requested by the Control Unit is not supported by a DRIVE-CLiQ component. Remedy: Upgrade the firmware of the DRIVE-CLiQ component involved. Specific remedies apply for different fault values. |
| A01304 (F) Firmware version of DRIVE-CLiQ component is not up-to-date | Cause: The non-volatile memory has a more recent firmware version than the one in the connected DRIVE-CLiQ component. Remedy: Update the firmware (p7828, p7829 and commissioning software). |
| F01305 Topology: Component number missing | Cause: The component number from the topology was not parameterized (p0121, p0131, etc.). Remedy:
|
| A01306 Firmware of the DRIVE-CLiQ component being updated | Cause: Firmware update is active for at least one DRIVE-CLiQ component. Remedy: Not necessary. This alarm automatically disappears after the firmware has been updated. |
| A01314 Topology: Component must not be present | Cause: For a component, “deactivate and not present” is set but this component is still in the topology. Remedy:
|
| A01317 (N) Deactivated component again present | Cause: If a component of the target topology for an active drive object is inserted and the associated parameter of the component is set to “deactivate”. Remedy: The alarm automatically disappears with the following actions:
|
| A01318 BICO: Deactivated interconnections present | Cause: This alarm is used if an inactive drive object is active again or if there are items in the list of BI/CI parameters that have been changed. Remedy: Reset alarm:
|
| A01319 Inserted component not initialized | Cause: Initialization is required for at least one inserted component. This is only possible if the pulses are inhibited for all the drive objects. Remedy: Activate pulse inhibit for all drive objects. |
| A01320 Topology: Drive object number does not exist in configuration | Cause: A drive object number is missing in p0978. Remedy: Set p0009 to 1 and change p0978 according to the documented rules. |
| A01321 Topology: Drive object number does not exist in configuration | Cause: p0978 contains a drive object number that does not exist. Remedy: Set p0009 to 1 and change p0978 according to the documented rules. |
| A01322 Topology: Drive object number present twice in configuration | Cause: A drive object number is present more than once in p0978. Remedy: Set parameter p0009 = 1 and change p0978 according to the documented rules. |
| A01323 Topology: More than two partial lists created | Cause: Partial lists are available more than twice in p0978. After the second 0, all must be 0. Remedy: Set p0009 to 1 and change p0978 according to the documented rules. |
| A01324 Topology: Dummy drive object number incorrectly created | Cause: In p0978, dummy drive object numbers (255) are only permitted in the first partial list. Remedy: Set p0009 to 1 and change p0978 according to the documented rules. |
| F01325 Topology: Component number not present in target topology | Cause: The component configured in a parameter (e.g. p0121, p0131, etc.) is not present in the target topology. Remedy: Establish topology and DO configuration consistency. |
| A01330 Topology: Quick commissioning not possible | Cause: Unable to carry out a quick commissioning. The existing actual topology does not fulfill the requirements. This could be due to illegal connections, too many components, impermissible combinations, or illegal EEPROM data. Remedy: Adapt the output topology to the permissible requirements and carry out commissioning using the commissioning software. Correct the specific issue indicated by the fault value. |
| A01331 Topology: At least one component not assigned to a drive object | Cause: At least one component is not assigned to a drive object, either because it could not be automatically assigned or the data sets are incorrect. Remedy: Assign this component to a drive object and check the parameters for the data sets. |
| 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:
|
| F01341 Topology: Maximum number of DRIVE-CLiQ components exceeded | Cause: Too many DRIVE-CLiQ components were defined in the actual topology. Remedy:
|
| F01354 Topology: Actual topology indicates an illegal component | Cause: The actual topology indicates at least one illegal component. Remedy: Remove the illegal components and restart the system. |
| F01355 Topology: Actual topology changed | Cause: The device target topology (p0099) does not correspond to the device actual topology (r0098). Remedy:
|
| F01356 Topology: There is a defective DRIVE-CLiQ component | Cause: The actual topology indicates at least one defective DRIVE-CLiQ component. Remedy: Replace the defective component and restart the system. |
| F01357 Topology: Two Control Units identified on the DRIVE-CLiQ line | Cause: In the actual topology, 2 Control Units are connected with one another through DRIVE-CLiQ. This is not permitted unless the Technology Extension OALINK is installed. Remedy:
|
| A01358 Topology: Line termination not available | Cause: At least one line with distributed drives is not terminated. The last participant on the line must be terminated with a line termination connector. Remedy: Install the line terminating connector for the last distributed drive. |
| F01359 Topology: DRIVE-CLiQ performance not sufficient | Cause: The DRIVE-CLiQ performance is not sufficient at one line in order to identify an inserted component. Remedy:
|
| F01360 Topology: Actual topology not permissible | Cause: The detected actual topology is not permissible due to reasons like too many components, unknown component type, illegal combinations, or out-of-date firmware. Remedy: The remedy depends on the specific fault cause. General actions include changing the configuration, removing components, or upgrading firmware. |
| A01361 Topology: Actual topology contains SINUMERIK and SIMOTION components | Cause: The detected actual topology contains both SINUMERIK and SIMOTION components. Remedy:
|
| A01362 Topology: Topology rule(s) broken | Cause: At least one topology rule for the SINAMICS S120 Combi has been broken. Remedy: Evaluate the alarm value and ensure compliance with the corresponding topology rule(s). |
| F01375 Topology: Connection duplicated between two components | Cause: When checking the actual topology, a ring-type connection was detected. Remedy: Output the fault value and remove the specified connection. |
| F01380 Topology: Actual topology EEPROM defective | Cause: When detecting the actual topology, a component with a defective EEPROM was detected. Remedy: Output the fault value and remove the defected component. |
| A01381 Topology: power unit / Motor Module / Line Module incorrectly inserted | Cause: The topology comparison has detected a power unit, Motor Module, or Line Module in the actual topology that has been incorrectly inserted with respect to the target technology. Remedy: Adapting topologies:
|
| A01382 Topology: Sensor Module incorrectly inserted | Cause: The topology comparison has detected a Sensor Module in the actual topology that has been incorrectly inserted. Remedy: Adapting topologies:
|
| A01383 Topology: Terminal Module incorrectly inserted | Cause: The topology comparison has detected a Terminal Module in the actual topology that has been incorrectly inserted. Remedy: Adapting topologies: insert the components at the right connection, adapt the project, or automatically remove the topology error. |
| A01384 Topology: DRIVE-CLiQ Hub Module incorrectly inserted | Cause: The topology comparison has detected a DRIVE-CLiQ Hub Module in the actual topology that has been incorrectly inserted. Remedy: Adapting topologies: insert the components at the right connection, adapt the project, or automatically remove the topology error. |
| A01385 Topology: Controller Extension incorrectly inserted | Cause: The topology comparison has detected a controller extension (CX32) in the actual topology that has been incorrectly inserted. Remedy: Adapting topologies: insert the components at the right connection, adapt the project, or automatically remove the topology error. |
| A01386 Topology: DRIVE-CLiQ component incorrectly inserted | Cause: The topology comparison has detected a DRIVE-CLiQ component in the actual topology that has been incorrectly inserted. Remedy: Adapting topologies: insert the components at the right connection, adapt the project, or automatically remove the topology error. |
| A01389 Topology: Motor with DRIVE-CLiQ incorrectly inserted | Cause: The topology comparison has detected a motor with DRIVE-CLiQ in the actual topology that has been incorrectly inserted. Remedy: Adapting topologies: insert the components at the right connection, adapt the project, or automatically remove the topology error. |
| A01416 Topology: Component additionally inserted | Cause: The topology comparison has found a component in the actual topology which is not specified in the target topology. Remedy: Adapting topologies: remove the additional component, or adapt the project/parameterization. |
| A01420 Topology: Component different | Cause: The topology comparison has detected differences in the actual topology and target topologies (e.g., component type, article number, manufacturer). Remedy: Adapting topologies: connect the expected component, or adapt the project/parameterization. |
| A01425 Topology: Serial number different | Cause: The topology comparison has detected differences in the serial number between the actual and target topologies. Remedy: Adapting topologies: change over the actual topology to match the target topology, or download the target topology that matches the actual topology. |
| A01428 Topology: Incorrect connection used | Cause: The topology comparison has detected that a component is connected to a different port than specified in the target topology. Remedy: Adapting topologies: reinsert the DRIVE-CLiQ cable to the component correctly, adapt the project, or automatically remove the error. |
| F01451 Topology: Target topology is invalid | Cause: An error was detected in the target topology. The target topology is invalid. Remedy: Reload the target topology using the commissioning software. |
| A01481 (N) Topology: power unit / Motor Module / Line Module not connected | Cause: The topology comparison has detected a component (power unit, motor module, or line module) that is missing in the actual topology with respect to the target topology. Remedy: Adapting topologies (insert component or adapt project) and checking hardware (24V supply, cables, component function). |
| A01482 Topology: Sensor Module not connected | Cause: A Sensor Module is missing in the actual topology. Remedy: Adapting topologies (insert or adapt project) and checking hardware. |
| A01483 Topology: Terminal Module not connected | Cause: A Terminal Module is missing in the actual topology. Remedy: Adapting topologies (insert or adapt project) and checking hardware. |
| A01484 Topology: DRIVE-CLiQ Hub Module not connected | Cause: A DRIVE-CLiQ Hub Module is missing in the actual topology. Remedy: Adapting topologies (insert or adapt project) and checking hardware. |
| A01485 Topology: Controller Extension not connected | Cause: A Control Extension (CX32) is missing in the actual topology. Remedy: Adapting topologies (insert or adapt project) and checking hardware. |
| A01486 Topology: DRIVE-CLiQ component not connected | Cause: A DRIVE-CLiQ component is missing in the actual topology. Remedy: Adapting topologies (insert or adapt project) and checking hardware. |
| A01487 Topology: Option slot component not inserted | Cause: An option slot component is missing in the actual topology. Remedy: Adapting topologies (insert or adapt project) and checking hardware. |
| A01489 Topology: motor with DRIVE-CLiQ not connected | Cause: A motor with DRIVE-CLiQ is missing in the actual topology. Remedy: Adapting topologies (insert or adapt project) and checking hardware. |
| A01507 (F, N) BICO: Interconnections to inactive objects present | Cause: There are BICO interconnections to an inactive/inoperable drive object. Remedy:
|
| A01508 BICO: Interconnections to inactive objects exceeded | Cause: The maximum number of BICO interconnections (signal sinks) when deactivating a drive object was exceeded. Remedy: The alarm automatically disappears as soon as no BICO interconnection is entered in the list. |
| F01510 BICO: Signal source is not float type | Cause: The requested connector output does not have the correct data type. This interconnection is not established. Remedy: Interconnect this connector input with a connector output having a float data type. |
| F01511 (A) BICO: Interconnection with different scalings | Cause: The requested BICO interconnection was established. However, a conversion is made between the BICO output and BICO input using the reference values because the BICO output has different normalized units than the BICO input. Remedy: Not necessary. |
| F01512 BICO: No scaling available | Cause: An attempt was made to determine a conversion factor for a scaling that does not exist. Remedy: Apply scaling or check the transfer value. |
| F01513 (N, A) BICO: Interconnection cross DO with different scalings | Cause: An interconnection is made between different drive objects and the BICO output has different normalized units or the reference values are different. Remedy: Not necessary. |
| A01514 (F) BICO: Error when writing during a reconnect | Cause: During a reconnect operation a parameter was not able to be written to. Remedy: Not necessary. |
| F01515 (A) BICO: Writing to parameter not permitted as the master control is active | Cause: When changing the number of CDS or when copying from CDS, the master control is active. Remedy: If required, return the master control and repeat the operation. |
| A01590 (F) Drive: Motor maintenance interval expired | Cause: The selected service/maintenance interval for this motor was reached. Remedy: Carry out service/maintenance and reset the service/maintenance interval (p0651). |
| F01600 SI P1 (CU): STOP A initiated | Cause: The drive-integrated “Safety Integrated” function on the Control Unit (CU) has detected a fault and initiated a STOP A. 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 crosswise data comparison between the two monitoring channels and has initiated a STOP F. A multitude of specific checks are performed, and a failure in any of them can trigger this fault. Remedy: The remedy is highly dependent on the specific fault value indicated. General steps include:
|
| F01612 SI P1 (CU): STO inputs for power units connected in parallel different | Cause: The drive-integrated “Safety Integrated” function on the Control Unit (CU) has identified different states of the AND’ed STO inputs for power units connected in parallel and has initiated a STOP F. Remedy:
|
| N01620 (F, A) SI P1 (CU): Safe Torque Off active | Cause: The “Safe Torque Off” (STO) function of the basic functions has been selected on the Control Unit (CU) using the input terminal and is active. Remedy: Not necessary. |
| N01621 (F, A) SI P1 (CU): Safe Stop 1 active | Cause: The “Safe Stop 1” (SS1) function has been selected on the Control Unit (CU) and is active. Remedy: Not necessary. |
| F01625 SI P1 (CU): Sign-of-life error in safety data | Cause: The drive-integrated “Safety Integrated” function on the Control Unit (CU) has detected an error in the sign-of-life of the safety data between the two monitoring channels and has initiated a STOP A. Remedy:
|
| F01630 SI P1 (CU): Brake control error | Cause: The drive-integrated “Safety Integrated” function on the Control Unit (CU) has detected a brake control fault and initiated a STOP A. Various specific faults such as “open holding brake” or “brake open” state can be the cause. Remedy:
|
| A01631 (F, N) SI P1 (CU): motor holding brake/SBC configuration not practical | Cause: A configuration of motor holding brake and SBC was detected that is not practical. For example, “No motor holding brake available” is set while “SBC” is enabled. Remedy: Check the parameterization of the motor holding brake and SBC and correct. |
| 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 particular drive without fault. Remedy:
|
| F01641 SI P1 (CU): component replacement identified and save required | Cause: The “Safety Integrated” function has identified that a component (e.g., Control Unit, Power Module, Sensor Module, or Terminal Module) has been replaced. Remedy:
|
| F01649 SI P1 (CU): Internal software error | Cause: An internal error in the Safety Integrated software on the Control Unit has occurred. This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| F01650 SI P1 (CU): Acceptance test required | Cause: The drive-integrated “Safety Integrated” function on monitoring channel 1 requires an acceptance test. This can be for various reasons, such as initial commissioning, checksum errors, parameter changes, or project downloads. Remedy: The remedy depends on the fault value:
|
| F01651 SI P1 (CU): Synchronization safety time slices unsuccessful | Cause: The “Safety Integrated” function requires a synchronization of the safety time slices between the two monitoring channels and between the Control Unit and the higher-level control. This synchronization routine was unsuccessful. Remedy: The remedy depends on the fault value:
|
| F01652 SI P1 (CU): Illegal monitoring clock cycle | Cause: One of the Safety Integrated monitoring clock cycles is not permissible. This can be due to communication conditions, incorrect parameterization for safe motion monitoring, or unsupported sampling times. Remedy: The remedy is highly dependent on the fault value:
|
| 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 (e.g. safety slot not configured, incorrect format/length, PROFIsafe not enabled). Remedy:
|
| A01654 (F, N) 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. Remedy: Check and, if necessary, correct the PROFIsafe configuration in the higher-level control.
|
| F01655 SI P1 (CU): Align monitoring functions | Cause: An error has occurred when aligning the Safety Integrated monitoring functions of both monitoring channels. No common set of supported SI monitoring functions was able to be determined. Remedy:
|
| F01656 SI CU: Parameter monitoring channel 2 error | Cause: When accessing the Safety Integrated parameters for monitoring channel 2 in the non-volatile memory, an error has occurred (e.g. parameters corrupted, software error, communication error). Remedy:
|
| F01657 SI P1 (CU): PROFIsafe telegram number invalid | Cause: The PROFIsafe telegram number set in p9611 is not valid. When PROFIsafe is enabled, a telegram number greater than zero must be entered. Remedy: Check the telegram number setting (p9611). |
| F01658 SI P1 (CU): PROFIsafe telegram number differ | Cause: The PROFIsafe telegram number is set differently in p9611 and p60022. The numbers must be identical. Remedy: Match the telegram number in both parameters so that they are the same (p9611, p60022). |
| F01659 SI P1 (CU): Write request for parameter rejected | Cause: The write request for one or several Safety Integrated parameters on the Control Unit (CU) was rejected. This can happen for a multitude of reasons, such as the password not being set, or attempting to enable an unsupported function. Remedy: The remedy is specific to the fault value:
|
| F01660 SI P1 (CU): Safety-related functions not supported | Cause: The Motor Module/Hydraulic Module does not support the safety-related functions. Safety Integrated cannot be commissioned. Remedy:
|
| 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. Remedy:
|
| F01663 SI P1 (CU): Copying the SI parameters rejected | Cause: When booting, an attempt to copy Safety Integrated parameters from monitoring channel 1 to 2 was rejected because no safety-relevant function has been selected in monitoring channel 1. Remedy:
|
| F01664 SI P1 (CU): No automatic firmware update | Cause: During booting, the system detected that the “Firmware update automatic” function (p7826 = 1) was not activated, which is required when safety functions are enabled. Remedy: When safety functions are enabled:
When deactivating the safety functions, the fault can be acknowledged after exiting the safety commissioning mode. |
| 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). 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. Remedy: Set the fail-safe 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 and rated motor current is greater than 5. Remedy: Use a suitable power unit with a lower power rating or a motor with a higher power rating. |
| F01670 SI Motion: Invalid parameterization Sensor Module | Cause: The parameterization of a Sensor Module used for Safety Integrated is not permissible (e.g., no encoder parameterized, wrong encoder type, communication error). Remedy: The remedy depends on the specific fault value. Examples include:
|
| F01671 SI Motion: Parameterization encoder error | Cause: The parameterization of the encoder used by Safety Integrated is different to the parameterization of the standard encoder. Remedy: Align the encoder parameterization between the safety encoder and the standard encoder. |
| F01672 SI P1 (CU): Motor Module software/hardware incompatible | Cause: The existing Motor Module software/hardware is incompatible, does not support safe motion monitoring, or there is a communications error. Remedy:
|
| F01673 SI Motion: Sensor Module software/hardware incompatible | Cause: The existing Sensor Module software and/or hardware does not support the safe motion monitoring function with the higher-level control. Remedy:
|
| F01674 SI Motion P1 (CU): Safety function not supported by PROFIsafe telegram | Cause: The monitoring function enabled in p9501 and p9601 is not supported by the currently set PROFIsafe telegram (p9611). Remedy:
|
| F01679 SI CU: Safety parameter settings and topology changed, warm restart/POWER ON required | Cause: Safety parameters have been changed; these will only take effect following a warm restart or POWER ON. A partial power up with modified configuration was then performed. Remedy:
|
| F01680 SI Motion P1 (CU): Checksum error safety monitoring functions | Cause: The actual checksum calculated by the drive does not match the reference checksum saved at the last machine acceptance. Safety-relevant parameters have been changed or a fault is present. Remedy:
|
| F01681 SI Motion P1 (CU): Incorrect parameter value | Cause: The parameter cannot be parameterized with this value due to a wide range of specific conflicts with other safety settings. Remedy: Correct the parameter based on the specific fault value provided. This involves actions like aligning clock cycles, correcting dependencies between functions, or adjusting limit values. |
| F01682 SI Motion P1 (CU): Monitoring function not supported | Cause: The monitoring function enabled in p9501, p9601, p9801, p9307 or p9507 is not supported in this firmware version or hardware combination. Remedy:
|
| F01683 SI Motion P1 (CU): SOS/SLS enable missing | Cause: The safety-relevant basic function “SOS/SLS” is not enabled in p9501 although other safety-relevant monitoring functions are enabled. Remedy: Enable the function “SOS/SLS” (p9501.0) and carry out a POWER ON. |
| F01684 SI Motion P1 (CU): Safely limited position limit values interchanged | Cause: For the function “Safely Limited Position” (SLP), a lower value is in p9534 than in p9535. Remedy:
|
| F01685 SI Motion P1 (CU): Safely limited speed limit value too high | Cause: The limit value for the function “Safely Limited Speed” (SLS) is greater than the speed that corresponds to an encoder limit frequency of 500 kHz. Remedy: Correct the limit values for SLS and carry out a POWER ON. |
| F01686 SI Motion: Illegal parameterization cam position | Cause: At least one enabled “Safety Cam” (SCA) is parameterized too close to the tolerance range around the modulo position. Remedy: Correct the cam position and carry out a POWER ON. |
| F01687 SI Motion: Illegal parameterization modulo value SCA (SN) | Cause: The parameterized modulo value for the “Safe Cam” (SCA) function is not a multiple of 360 000 mDegrees. Remedy: Correct the modulo value for SCA and carry out a POWER ON. |
| F01688 SI Motion CU: Actual value synchronization not permissible | Cause: Actual value synchronization is not permissible for a 1-encoder system, or is impermissibly combined with other functions like SCA/SLP or “Safe position via PROFIsafe”. Remedy:
|
| C01689 SI Motion: Axis re-configured | Cause: The axis configuration was changed (e.g. changeover between linear axis and rotary axis). Remedy: After the changeover, exit safety commissioning, save parameters, and POWER ON. Then, reactivate and complete safety commissioning, save again, and POWER ON. |
| F01690 SI Motion: Data save problem for the NVRAM | Cause: There is not sufficient memory space in the NVRAM on the drive to save the safety logbook. Remedy:
|
| A01691 (F) SI Motion: Ti and To unsuitable for DP cycle | Cause: The configured times for PROFIBUS communication are not permitted, and the DP cycle is used as the actual value acquisition cycle for safe movement monitoring. Remedy: Configure Ti and To low so that they are suitable for the DP cycle or increase the DP cycle time. Alternatively, use the actual value acquisition cycle p9511/p9311. |
| F01692 SI Motion P1 (CU): Parameter value not permitted for encoderless | Cause: The parameter cannot be set to this value if encoderless motion monitoring functions have been selected in p9506. Remedy:
|
| A01693 (F) SI P1 (CU): Safety parameter setting changed, warm restart/POWER ON required | Cause: Safety parameters have been changed; these will only take effect following a warm restart or POWER ON. Remedy:
|
| F01694 (A) SI Motion CU: Firmware version Motor Module/Hydraulic Module older Control Unit | Cause: The firmware version of the Motor Module/Hydraulic Module is older than the version of the Control Unit. Remedy: Upgrade the firmware of the Motor Module/Hydraulic Module to a later version. |
| A01695 (F) SI Motion: Sensor Module was replaced | Cause: A Sensor Module, which is used for safe motion monitoring functions, was replaced. The hardware replacement must be acknowledged. An acceptance test must be subsequently performed. Remedy: Carry out the steps using the STARTER commissioning software, such as pressing the “Acknowledge hardware replacement” button, executing “Copy RAM to ROM”, and carrying out a POWER ON. An acceptance test must follow. |
| 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. Remedy: De-select the forced checking procedure for the safe 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. 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. |
| C01700 SI Motion P1 (CU): STOP A initiated | Cause: The drive is stopped via a STOP A (STO via the safety switch-off signal path of the Control Unit). This can be a subsequent response to other safety messages. Remedy:
|
| C01701 SI Motion P1 (CU): STOP B initiated | Cause: The drive is stopped via a STOP B (braking along the OFF3 deceleration ramp). This can be a subsequent response to other safety messages. Remedy:
|
| C01706 SI Motion P1 (CU): SAM/SBR limit exceeded | Cause: After initiating STOP B (SS1) or STOP C (SS2), the speed has exceeded the selected tolerance for SAM or SBR functions. Remedy: Check the braking behavior and, if necessary, adapt the parameterization of the “SAM” or the “SBR” function. This message can be acknowledged without a POWER ON. |
| C01707 SI Motion P1 (CU): Tolerance for safe operating stop exceeded | Cause: The actual position has distanced itself further from the target position than the standstill tolerance. The drive is shut down by the message C01701 “SI Motion: STOP B initiated”. Remedy:
|
| C01708 SI Motion P1 (CU): STOP C initiated | Cause: The drive is stopped via a STOP C (braking along the OFF3 deceleration ramp). “Safe Operating Stop” (SOS) is activated after the parameterized time has expired. Remedy:
|
| C01709 SI Motion P1 (CU): STOP D initiated | Cause: The drive is stopped via a STOP D (braking along the path). “Safe Operating Stop” (SOS) is activated after the parameterized time has expired. Remedy:
|
| C01710 SI Motion P1 (CU): STOP E initiated | Cause: The drive is stopped via a STOP E (retraction motion). “Safe Operating Stop” (SOS) is activated after the parameterized time has expired. Remedy:
|
| C01711 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. This can be caused by a vast number of specific parameter mismatches or hardware/communication issues. Remedy: The remedy is highly dependent on the specific message value (0-7002) which indicates the exact parameter or condition that failed the cross-comparison. General troubleshooting includes:
|
| C01712 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. Remedy: The remedy depends on the specific message value, which points to the exact parameter mismatch (e.g., discrepancy time, input/output terminals, debounce times). Correct the parameterization to ensure both monitoring channels are identical. |
| C01714 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 (r9749, interpret decimal):
Remedy:
Note: SI: Safety Integrated SLS: Safely Limited Speed / SG: Safely reduced speed See also: p9531 (SI Motion SLS (SG) limit values (Control Unit)), p9563 (SI Motion SLS (SG)-specific stop response (Control Unit)) |
| C01715 SI Motion P1 (CU): Safely Limited Position exceeded | Cause: The axis has moved past a parameterized position that is monitored by the “SLP” function. Message value (r9749, interpret decimal):
Remedy:
Note: SI: Safety Integrated SLP: Safely Limited Position / SE: Safe software limit switches See also: p9534 (SI Motion SLP (SE) upper limit values (Control Unit)), p9535 (SI Motion SLP (SE) lower limit values (Control Unit)) |
| C01716 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). Message value (r9749, interpret decimal):
Remedy:
Note: SDI: Safe Direction (safe motion direction) SI: Safety Integrated See also: p9564 (SI Motion SDI tolerance (Control Unit)), p9565 (SI Motion SDI delay time (Control Unit)), p9566 (SI Motion SDI stop response (Control Unit)) |
| C01730 SI Motion P1 (CU): Reference block for dynamic safely limited speed invalid | Cause: The reference block transferred via PROFIsafe is negative. A reference block is used to generate a referred velocity limit value based on the reference quantity “Velocity limit value SLS1” (p9531[0]). The drive is stopped as a result of the configured stop response (p9563[0]). Message value (r9749, interpret decimal): requested, invalid reference block. Remedy: In the PROFIsafe telegram, input data S_SLS_LIMIT_IST must be corrected. This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
Note: SI: Safety Integrated SLS: Safely Limited Speed / SG: Safely reduced speed |
| C01745 SI Motion P1 (CU): Checking braking torque for the brake test | Cause: The scaling of the brake torque for the brake test can be changed using parameter p2003. An acceptance test must be carried out again for the braking test. This determines whether the braking test is still carried out with the correct braking torque. Remedy:
See also: p2003 (Reference torque) |
| C01750 SI Motion P1 (CU): Hardware fault safety-relevant encoder | Cause: The encoder that is used for the safety-relevant motion monitoring functions signals a hardware fault. Message value (r9749, interpret decimal): Encoder status word 1, encoder status word 2 that resulted in the message. Remedy:
Note regarding encoder replacement for a third-party motor: The serial number of the encoder must be copied in order to acknowledge this safety message. This can be realized using p0440 = 1 or p1990 = 1. |
| C01751 SI Motion P1 (CU): Effectivity test fault safety-relevant encoder | Cause: The DRIVE-CLiQ encoder for safe motion monitoring signals an error for the effectivity tests. Message value (r9749, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| C01752 SI Motion P1 (CU): reference position invalid | Cause: The transferred reference position is invalid. Message value (r9749, interpret decimal):
Remedy:
|
| C01770 SI Motion P1 (CU): Discrepancy error of the fail-safe inputs/outputs | Cause: The fail-safe digital inputs/digital outputs (F-DI/F-DO) show a different state longer than that parameterized in p10002 / p10102. Fault value (r0949, interpret bitwise binary): yyyyxxxx bin xxxx: Discrepancy error for fail-safe digital inputs (F-DI). Bit 0: Discrepancy error for F-DI 0 Bit 1: Discrepancy error for F-DI 1 … yyyy: Discrepancy error for fail-safe digital outputs (F-DO). Bit 0: Discrepancy error for F-DO 0 … Note: If several discrepancy errors occur consecutively, then this message is only signaled for the first error that occurs. Remedy: – check the wiring of the F-DI (contact problems). Note: This message can be acknowledged via F-DI or PROFIsafe (safe acknowledgment). Discrepancy errors of an F-DI can only be acknowledged if safe acknowledgment was carried out once after the cause of the error was resolved (p10006, acknowledgment via PROFIsafe, extended message acknowledgment). As long as safety acknowledgment was not carried out, the corresponding F-DI stays in the safe state internally. |
| A01772 SI Motion P1 (CU): Test stop for fail-safe digital outputs running | Cause: The forced checking procedure (test stop) for the fail-safe digital inputs is currently in progress. Remedy: The alarm is automatically withdraw after successfully ending or canceling (when a fault condition occurs) the test stop. Note: F-DO: Failsafe Digital Output |
| F01773 SI Motion P1 (CU): Test stop fail-safe digital output error | Cause: A fault has occurred on processor 1 during the forced checking procedure (test stop) of the fail-safe digital output. Fault value (r0949, interpret hexadecimal): RRRVWXYZ hex:
Remedy: Check the wiring of the fail-safe digital output (F-DO) and restart the test stop. Note:
F-DO: Failsafe Digital Output |
| A01774 SI Motion P1 (CU): Test stop for fail-safe digital outputs required | Cause: The time set in p10003 for the forced checking procedure (test stop) for the fail-safe 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. Note: F-DO: Failsafe Digital Output See also: p10007 (SI TM54F forced checking procedure F-DI/F-DO signal source) |
| A01780 SBT When selected, the brake is closed | Cause: When selecting the brake test or starting the brake test, not all of the brakes were open. Alarm value (r2124, interpret binary):
Note: The alarm is also issued, if a brake has not been configured in p10202. Remedy: Open all brakes and reselect the brake test (p10230.0, p10235.0). |
| A01781 SBT brake opening time exceeded | Cause: The maximum time (11 s) to open the brake during the brake test was exceeded. Possible causes:
Alarm value (r2124, interpret binary):
Remedy:
|
| A01782 SBT brake test incorrect control | Cause: The brake test was canceled as a result of incorrect control. Alarm value (r2124, evaluate binary):
Remedy:
|
| A01783 SBT brake closing time exceeded | Cause: The maximum time (11 s) to close the brake during the brake test was exceeded. Alarm value (r2124, interpret binary):
Remedy:
|
| A01784 SBT brake test canceled with fault | Cause: The safe brake test was canceled as a result of a fault. Alarm value (r2124, interpret binary):
Remedy:
|
| A01785 SBT brake test configuration error | Cause: Error when parameterizing the brake test. In this configuration, the brake test cannot be started or cannot be started without error. Alarm value (r2124, interpret decimal):
Remedy: Check parameterization of the brake test. |
| F01786 SCC signal source changed | Cause: The signal source in p10235 or p10250 was changed. The new signal source is effective immediately. Remedy: Acknowledge fault. |
| F01787 SBT motor type different | Cause: The motor type set for the safe brake test (p10204) does not match the motor type set via the function module (r0108.12). Remedy: Adapt the motor type set for the safe brake test. |
| 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:
|
| A01789 SI: Automatic test stop and brake test when test stop is selected not permitted | Cause: The parameterization of the automatic test stop (p9507.6/p9307.6) and the brake test when a test stop is selected (p10203 = 2) are not permissible. The test stop is not automatically carried out when the powering up. Remedy:
|
| A01794 (N) SI Motion: check modulo value for safe position via PROFIsafe | Cause: When parameterizing the modulo value for safe position via PROFIsafe (p9505) the position actual value can jump when the range that can be represented overflows. Range that can be represented:
Remedy: Correct the parameter assignment. Set p9505 to 2^n revolutions – and to complete revolutions (i.e. a multiple of 360 °). |
| A01795 SI Motion P1 (CU): Wait time after exiting the safe pulse cancellation expired | Cause: After exiting safe pulse cancellation, within the wait time of 5 seconds, encoderless actual value sensing was not able to be activated for the extended functions without selection. A change is again made into the “safe pulse cancellation” state. 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):
Remedy: If, after a longer period of time, the message is not automatically withdrawn, the following checks have to be made as appropriate. |
| C01797 SI Motion P1 (CU): Axis not safely referenced | Cause: The standstill position saved before switching off does not match the actual position determined at switch-on. Message value (r9749, interpret decimal):
Remedy: If safe automatic referencing is not possible the user must issue a user agreement for the new position using the softkey. This mean that this position is then designated as safety-relevant. |
| C01798 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. |
| C01799 SI Motion P1 (CU): Acceptance test mode active | Cause: The acceptance test mode is active. This means the following:
Remedy: Not necessary. The message is withdrawn when exiting the acceptance test mode. |
| F01800 DRIVE-CLiQ: Hardware/configuration error | Cause: A DRIVE-CLiQ connection fault has occurred. Fault value (r0949, interpret decimal):
Remedy:
|
| A01839 DRIVE-CLiQ diagnostics: cable fault to the component | Cause: The fault counter (r9936[0…199]) to monitor the DRIVE-CLiQ connections/cables has been incremented. Remedy:
|
| A01840 SMI: Component found without motor data | Cause: An SMI/DQI without motor data has been found (e.g. SMI installed as replacement part). Remedy:
|
| A01900 (F) PB/PN: Configuration telegram error | Cause: A controller attempts to establish a connection using an incorrect configuring telegram. Alarm value (r2124, interpret decimal):
Remedy: Check the bus configuration on the master and the slave sides. |
| A01902 PB/PN: clock cycle synchronous operation parameterization not permissible | Cause: Parameterization for isochronous operation is not permissible. Alarm value (r2124, interpret decimal):
Remedy:
|
| F01910 (N, A) Fieldbus: setpoint timeout | Cause: The reception of setpoints from the fieldbus interface has been interrupted.
Remedy: Restore the bus connection and set the controller to RUN. |
| F01911 (N, A) PB/PN: clock cycle synchronous operation clock cycle failure | Cause: The global control telegram to synchronize the clock cycles has failed. Remedy:
|
| F01912 (N, A) PB/PN: clock cycle synchronous operation sign-of-life failure | Cause: The maximum permissible number of errors in the controller sign-of-life has been exceeded. Remedy:
|
| 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. |
| A01921 (F) PROFIBUS: Receive setpoints after To | Cause: Output data of PROFIBUS master (setpoints) received at the incorrect instant in time within the PROFIBUS clock cycle. Remedy:
|
| A01925 (F) Modbus TCP: connection interrupted | Cause: The Ethernet connection to the Modbus controller is interrupted. Remedy:
|
| A01930 PB/PN: current controller sampling time clock cycle synch. not equal | Cause: The current controller sampling time of all drives must be set the same for the clock cycle synchronous operation. Remedy: Set current controller sampling time to identical values (p0115[0]). |
| A01931 PB/PN: speed controller sampling time clock cycle synch. not equal | Cause: The speed controller sampling time of all drives must be set the same for the clock cycle synchronous operation. Remedy: Set the speed controller sampling times to identical values (p0115[1]). |
| A01932 PB/PN: clock cycle synchronization missing for DSC | Cause: There is no clock synchronization or clock synchronous sign of life and DSC is selected. Remedy: Set clock synchronization across the bus configuration and transfer clock synchronous sign-of-life. |
| A01940 PB/PN: clock cycle synchronism not reached | Cause: It was not possible to synchronize to the clock cycle specified by the master. Remedy:
|
| A01941 PB/PN: clock cycle signal missing when establishing bus communication | Cause: The global control telegram for synchronization is not being received. Remedy: Check the master application and bus configuration. |
| A01943 PB/PN: clock cycle signal error when establishing bus communication | Cause: The global control telegram for synchronization is being irregularly received. Remedy:
|
| A01944 PB/PN: sign-of-life synchronism not reached | Cause: Synchronization with the master sign-of-life could not be completed. Remedy:
|
| A01945 PROFIBUS: Connection to the Publisher failed | Cause: For PROFIBUS peer-to-peer data transfer, the connection to at least one Publisher has failed. Remedy:
|
| F01946 (A) PROFIBUS: Connection to the Publisher aborted | Cause: The connection to at least one Publisher for PROFIBUS peer-to-peer data transfer has been aborted. Remedy:
|
| F01950 (N, A) PB/PN: clock cycle synchronous operation synchronization unsuccessful | Cause: Synchronization of the internal clock cycle to the global control telegram has failed. Remedy: Only for internal Siemens troubleshooting. |
| F01951 CU SYNC: Synchronization application clock cycle missing | Cause: Synchronization with the Control Unit was unsuccessful. Remedy:
|
| F01952 CU DRIVE-CLIQ: Synchronization of component not supported | Cause: The existing system configuration requires that the connected DRIVE-CLiQ components support the synchronization between the basic clock cycle, DRIVE-CLiQ clock cycle and the application clock cycle. However, not all DRIVE-CLiQ components have this functionality. Fault value (r0949, interpret decimal): Component number of the first faulty DRIVE-CLiQ component. Remedy:
|
| A01953 CU SYNC: Synchronization not completed | Cause: After the drive system is switched on, the synchronization between the basic clock cycle, DRIVE-CLiQ clock cycle and application clock cycle was started but was not completed within the selected time tolerance. Alarm value (r2124, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01954 CU DRIVE-CLIQ: Synchronization unsuccessful | Cause: Synchronization between the basic clock cycle, DRIVE-CLiQ clock cycle and application clock cycle was started and was not able to be successfully completed (e.g. after switch-on). Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01955 CU DRIVE-CLIQ: Synchronization DO not completed | Cause: After the drive system is switched on, the synchronization between the basic clock cycle, DRIVE-CLiQ clock cycle and application clock cycle was started but was not completed within the selected time tolerance. Alarm value (r2124, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01980 PN: cyclic connection interrupted | Cause: The cyclic connection to the PROFINET controller is interrupted. See also: r8936 (PN cyclic connection state) Remedy:
|
| A01981 PN: Maximum number of controllers exceeded | Cause: A controller attempts to establish a connection to the drive, and as a consequence exceeds the permitted number of PROFINET connections. The alarm disappears automatically after approx. 30 seconds. Alarm value (r2124, interpret hexadecimal): yyyyxxxx hex: yyyy = info. 1, xxxx = info. 2 Info 1 = 0: number of RT connections exceeded Info 1 > 0: number of IRT connections exceeded Info 2: permitted number of connections Remedy:
|
| A01982 PN: second controller missing | Cause: Connections to two PROFINET controllers are expected. However, only the connection to a PROFINET controller is present.
Remedy:
|
| A01983 PN: system redundancy switchover running | Cause: The “PROFINET system redundancy” function is configured and the connection between the primary control and drive device is interrupted. The backup controller assumes control of the drive device. Remedy:
|
| A01989 PN: internal cyclic data transfer error | Cause: The cyclic actual values and/or setpoints were not transferred within the specified times. Alarm value (r2124, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01990 (F) USS: PZD configuration error | Cause: The configuration of the process data (PZD) for the USS protocol is incorrect. Alarm value (r2124, interpret decimal): 2: PZD amount (p2022) too great for the first drive object (p978[0]). The number of possible PZD items in a drive object is determined by the number of indices in r2050/p2051. Remedy:
|
| A02000 Function generator: Start not possible | Cause: The function generator has already been started. Remedy:
|
| A02005 Function generator: Drive does not exist | Cause: The drive object specified for connection does not exist. See also: p4815 (Function generator drive number) Remedy:
|
| A02006 Function generator: No drive specified for connection | Cause: No drive specified for connection in p4815. See also: p4815 (Function generator drive number) Remedy:
|
| A02007 Function generator: Drive not SERVO / VECTOR / DC_CTRL | Cause: The drive object specified for connection is not a SERVO / VECTOR or DC_CTRL. See also: p4815 (Function generator drive number) Remedy:
|
| A02008 Function generator: Drive specified a multiple number of times | Cause: The drive object specified for connection is already specified. Alarm value (r2124, interpret decimal): Drive object number of the drive object that is specified a multiple number of times. Remedy:
|
| A02009 Function generator: Illegal mode | Cause: The set operating mode (p1300) of the drive object is not permissible when using the function generator. Alarm value (r2124, interpret decimal): Number of the drive object involved. Remedy:
|
| A02010 Function generator: Speed setpoint from the drive is not zero | Cause: The speed setpoint of a drive selected for connection is greater than the value for the standstill detection set using p1226. Remedy:
|
| A02011 Function generator: The actual drive speed is not zero | Cause: The speed actual value of a drive selected for connection is greater than the value for the standstill detection set using p1226. Remedy:
|
| A02015 Function generator: Drive enable signals missing | Cause: The master control and/or enable signals are missing to connect to the specified drive. See also: p4815 (Function generator drive number) Remedy:
|
| A02016 Function generator: Magnetizing running | Cause: Magnetizing has not yet been completed on a drive object specified for connection. Alarm value (r2124, interpret decimal): Number of the drive object involved. See also: p4815 (Function generator drive number) Remedy:
|
| A02020 Function generator: Parameter cannot be changed | Cause: This parameter setting cannot be changed when the function generator is active (p4800 = 1). See also: p4810, p4812, p4813, p4815, p4820, p4821, p4822, p4823, p4824, p4825, p4826, p4827, p4828, p4829 Remedy:
|
| A02025 Function generator: Period too short | Cause: The value for the period is too short. See also: p4821 (Function generator period) Remedy:
|
| A02026 Function generator: Pulse width too high | Cause: The selected pulse width is too high. The pulse width must be less than the period duration. See also: p4822 (Function generator pulse width) Remedy:
|
| A02030 Function generator: Physical address equals zero | Cause: The specified physical address is zero. See also: p4812 (Function generator physical address) Remedy:
|
| A02040 Function generator: Illegal value for offset | Cause: The value for the offset is higher than the value for the upper limit or lower than the value for the lower limit. See also: p4826 (Function generator offset) Remedy:
|
| A02041 Function generator: Illegal value for bandwidth | Cause: The bandwidth referred to the time slice clock cycle of the function generator has either been set too low or too high. Depending on the time slice clock cycle, the bandwidth is defined as follows: Bandwidth_max = 1 / (2 x time slice clock cycle) Bandwidth_min = Bandwidth_max / 100000 Example: Assumption: p4830 = 125 µs –> Bandwidth_max = 1 / (2 x 125 µs) = 4000 Hz –> Bandwidth_min = 4000 Hz / 100000 = 0.04 Hz Note: p4823: Function generator bandwidth p4830: Function generator time slice clock cycle Remedy:
|
| A02047 Function generator: Time slice clock cycle invalid | Cause: The time slice clock cycle selected does not match any of the existing time slices. See also: p4830 (Function generator time slice cycle) Remedy:
|
| A02050 Trace: Start not possible | Cause: The trace has already been started. See also: p4700 (Trace control) Remedy:
|
| 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. Alarm value (r2124, interpret decimal): 1: Recorder 0 2: Recorder 1 3: Recorders 0 and 1 See also: p4700, p4711, p4730, p4731, p4732, p4733, p4734, p4735, p4736, p4737 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. See also: p4721 (Trace recording time) Remedy:
|
| A02056 Trace: Recording cycle too short | Cause: The selected recording cycle is shorter than the selected basic clock cycle 0 (p0110[0]). See also: p4720 (Trace recording cycle) Remedy:
|
| A02057 Trace: Time slice clock cycle invalid | Cause: The time slice clock cycle selected does not match any of the existing time slices. See also: p4723 (Trace time slice cycle) Remedy:
|
| 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 See also: p4723 (Trace time slice cycle) Remedy:
|
| 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. See also: p4723 (Trace time slice cycle) Remedy:
|
| A02060 Trace: Signal to be traced missing | Cause:
See also: p4730 (Trace record signal 0), p4731 (Trace record signal 1), p4732 (Trace record signal 2), p4733 (Trace record signal 3) Remedy:
|
| A02061 Trace: Invalid signal | Cause:
See also: p4730 (Trace record signal 0), p4731 (Trace record signal 1), p4732 (Trace record signal 2), p4733 (Trace record signal 3) Remedy:
|
| A02062 Trace: Invalid trigger signal | Cause:
See also: p4711 (Trace trigger signal) Remedy:
|
| A02063 Trace: Invalid data type | Cause: The specified data type to select a signal using a physical address is invalid. See also: p4711 (Trace trigger signal), p4730 (Trace record signal 0), p4731 (Trace record signal 1), p4732 (Trace record signal 2), p4733 (Trace record signal 3) Remedy:
|
| A02070 Trace: Parameter cannot be changed | Cause: The trace parameter settings cannot be changed when the trace is active. See also: p4700, p4710, p4711, p4712, p4713, p4714, p4715, p4716, p4720, p4721, p4722, p4730, p4731, p4732, p4733, p4780, p4781, p4782, p4783, p4789, p4795 Remedy:
|
| A02075 Trace: Pretrigger time too long | Cause: The selected pretrigger time must be shorter than the trace time. See also: p4721 (Trace recording time), p4722 (Trace trigger delay) Remedy:
|
| 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:
|
| 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). A multiple trace is not started or is canceled. Alarm value (r2124, interpret decimal): 1: Memory card cannot be accessed. – card is not inserted or is blocked by a mounted USB drive. 3: data save operation to slow. – a second trace has been completed before the measurement results of the first trace were able to be saved. – writing the measurement result files to the card is blocked by the parameter save. 4: Data save operation canceled. – for instance, the file required for the data save operation was not able to be found. See also: p4840 (MTrace cycle number setting) 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). A multiple trace is not started or is canceled. Alarm value (r2124, interpret decimal): 1: Memory card cannot be accessed. – card is not inserted or is blocked by a mounted USB drive. 3: data save operation to slow. – a second trace has been completed before the measurement results of the first trace were able to be saved. – writing the measurement result files to the card is blocked by the parameter save. 4: Data save operation canceled. – for instance, the file required for the data save operation was not able to be found. See also: p4840 (MTrace cycle number setting) 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:
|
| A02100 Drive: Computing dead time current controller too short | Cause: The value in p0118 produces a dead time of one clock cycle because it is prior to setpoint availability. Possible causes:
Alarm value (r2134, floating point): Minimum value for p0118 where dead time no longer occurs. Remedy:
|
| A02150 TEC: Technology Extension cannot be loaded | Cause: The system was not able to load a Technology Extension. Alarm value (r2124, interpret hexadecimal): 10 hex (16 dec): The interface version in the DCB user library is not compatible to the DCC standard library that has been loaded. 12 hex (18 dec): A technology package was not able to be downloaded to a Control Unit because the warm restart necessary was not able to be performed. Only for internal Siemens troubleshooting. Remedy:
|
| F02151 (A) TEC: internal software error | Cause: An internal software error has occurred within a Technology Extension. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F02152 (A) TEC: insufficient memory | Cause: Too many functions have been configured on this Control Unit (e.g. too many drives, function modules, data sets, Technology Extensions, blocks, etc). Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| F02153 TEC: technology function does not exist | Cause: A technology function (e.g. Technology Extension, DCB library) does not exist on the drive device. When configuring, a technology function is activated, which does not exist on the drive device. This can occur when downloading a project or when powering up. Remedy:
|
| F03000 NVRAM fault on action | Cause: A fault occurred during execution of action p7770 = 1 or 2 for the NVRAM data. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = fault cause, xx = application ID yy = 1: The action p7770 = 1 is not supported by this version if Drive Control Chart (DCC) is activated for the drive object concerned. yy = 2: The data length of the specified application is not the same in the NVRAM and the backup. yy = 3: The data checksum in p7774 is not correct. yy = 4: No data available to load. See also: p7770 (NVRAM action) 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:
|
| F03500 (A) TM: Initialization | Cause: When initializing the Terminal Modules, the terminals of the Control Unit or the Terminal Board 30, an internal software error has occurred. Fault value (r0949, interpret decimal): yxxx dex y = Only for internal Siemens troubleshooting xxx = component number (p0151) Remedy:
|
| A03501 TM: Sampling time change | Cause: The sampling times of the inputs/outputs were changed. This change only becomes valid after the next boot. Remedy:
|
| F03505 (N, A) Analog input wire breakage | Cause: The wire-break monitoring for an analog input has responded. The input value of the analog input has exceeded the threshold value parameterized in p0761[0]. p0756[0]: analog input 0 (X131.7/X131.8) Fault value (r0949, interpret decimal): Note: For the following analog input type, the wire breakage monitoring is active: p0756[0] = 3 (4 … 20 mA with monitoring) Remedy:
|
| F03505 (N, A) TB: Analog input wire breakage | Cause: The wire-break monitoring for an analog input has responded. Remedy:
|
| F03505 (N, A) TM: Analog input wire breakage | Cause: The wire-break monitoring for an analog input has responded. The input value of the analog input has exceeded the threshold value parameterized in p4061[x]. Index x = 0: Analog input 0 (X521.1/X521.2) Index x = 1: Analog input 1 (X521.3/X521.4) Fault value (r0949, interpret decimal): yxxx dec y = analog input (0 = analog input 0 (AI 0), 1 = analog input 1 (AI 1)) xxx = component number (p0151) Remedy:
|
| A03506 (F, N) 24 V power supply missing | Cause: The 24 V power supply for the digital outputs (X124) is missing. Remedy:
|
| A03507 (F, N) Digital output not set | Cause: Despite specification by the signal source the digital output has not been set. Possible causes:
Alarm value (r2124, interpret bitwise binary): Digital output involved (structured the same as r0747). Remedy:
|
| A03510 (F, N) Calibration data not plausible | Cause: During ramp-up, the Terminal Module 31 (TM31) calibration data is read in and checked for plausibility. At least one calibration data point was determined to be invalid. Alarm value (r2124, interpret binary): Bit 1: 10 V value, analog input 0 invalid. Bit 3: 10 V value, analog input 1 invalid. Bit 4: Offset, analog output 0 invalid. Bit 5: 10 V value, analog output 0 invalid. Bit 6: Offset, analog output 1 invalid. Bit 7: 10 V value, analog input 1 invalid. Remedy:
|
| A03550 TM: Speed setpoint filter natural frequency > Shannon frequency | Cause: The natural filter frequency of the speed setpoint filter (p1417) is greater than or equal to the Shannon frequency. The Shannon frequency is calculated according to the following formula: 0.5 / p4099[3] Remedy:
|
| F03590 (N, A) TM: Module not ready | Cause: The Terminal Module involved does not send a ready signal and no valid cyclic data. Fault value (r0949, interpret decimal): Drive object number of the Terminal Module involved. Remedy:
|
| A05000 (N) Power unit: Overtemperature heat sink AC inverter | Cause: The alarm threshold for overtemperature at the inverter heat sink has been reached. The response is set using p0290. If the temperature of the heat sink increases by an additional 5 K, then fault F30004 is initiated. Remedy:
|
| A05001 (N) Power unit: Overtemperature depletion layer chip | Cause: Alarm threshold for overtemperature of the power semiconductor in the AC converter has been reached. Note: the response is set using p0290. – if the depletion layer temperature increases by an additional 15 K, then fault F30025 is triggered. Remedy:
|
| A05002 (N) Power unit: Air intake overtemperature | Cause: The alarm threshold for the air intake overtemperature has been reached. For air-cooled power units, the threshold is 42 °C (hysteresis 2 K). The response is set using p0290. If the air intake temperature increases by an additional 13 K, then fault F30035 is output. Remedy:
|
| A05003 (N) Power unit: Internal overtemperature | Cause: The alarm threshold for internal overtemperature has been reached. If the temperature inside the power unit increases by an additional 5 K, then fault F30036 is triggered. Remedy:
|
| A05004 (N) Power unit: Rectifier overtemperature | Cause: The alarm threshold for the overtemperature of the rectifier has been reached. The response is set using p0290. If the temperature of the rectifier increases by an additional 5 K, then fault F30037 is triggered. Remedy:
|
| A05005 Cooling unit: Cooling medium flow rate too low | Cause: Cooling unit: Alarm – flow rate has fallen below the alarm value Remedy:
|
| A05006 (N) Power unit: Overtemperature thermal model | Cause: The temperature difference between the chip and heat sink has exceeded the permissible limit value (blocksize power units only). Depending on p0290, an appropriate overload response is initiated. See also: r0037 Remedy:
|
| N05007 (A) Power unit: Overtemperature thermal model (chassis PU) | Cause: The temperature difference between the chip and heat sink has exceeded the permissible limit value (r0293) (chassis power units only). Depending on p0290, an appropriate overload response is initiated. See also: r0037, r0293 (Power unit alarm threshold model temperature) Remedy:
|
| F05050 Parallel circuit: Pulse enable in spite of pulse inhibit | Cause: A power unit signals that the pulses are enabled although the pulses are inhibited. Fault value (r0949, interpret decimal): Number of the power unit involved. Remedy:
|
| F05051 Parallel circuit: Power unit pulse enable missing | Cause: For one or several power units, the pulses were not able to be enabled. Fault value (r0949, interpret decimal): Number of the power unit involved. Remedy:
|
| A05052 (F) Parallel circuit: Illegal current asymmetry | Cause: The deviation of the individual currents of the power units exceeds the alarm threshold specified in p7010. Alarm value (r2124, interpret decimal): 1: Phase U. 2: Phase V. 3: Phase W. Remedy:
|
| A05053 (F) Parallel circuit: Inadmissible DC link voltage asymmetry | Cause: The deviation of the DC link voltage measured values exceeds the alarm threshold specified in p7011. Remedy:
|
| A05054 Parallel circuit: Power unit deactivated | Cause: For the drive object involved, fewer power units connected in parallel are active than exist in the target topology. Operation is only possible at reduced power (power derating). Remedy:
|
| F05055 Parallel connection: Power units with illegal code numbers | Cause: The code numbers of the power units do not match. For parallel circuit configurations, only power units with identical power unit data may be used. Fault value (r0949, interpret decimal): Parameter in which the first different power unit code number was detected. Possible causes:
Remedy:
|
| F05056 Parallel circuit: Power unit EEPROM versions differ | Cause: The EEPROM versions of the power units do not match. Fault value (r0949, interpret decimal): Parameter in which the first different version number was detected. Remedy:
|
| F05057 Parallel circuit: Power unit firmware versions differ | Cause: The firmware versions of the power units connected in parallel do not match. Fault value (r0949, interpret decimal): Parameter in which the first different version number was detected. Remedy:
|
| F05058 Parallel circuit: VSM EEPROM versions differ | Cause: The EEPROM versions of the Voltage Sensing Modules (VSM) do not match. Fault value (r0949, interpret decimal): Parameter in which the first different version number was detected. Remedy:
|
| F05059 Parallel circuit: VSM firmware versions differ | Cause: The firmware versions of the Voltage Sensing Module (VSM) do not match. Fault value (r0949, interpret decimal): Parameter in which the first different version number was detected. Remedy:
|
| F05060 Parallel circuit: Power unit firmware version does not match | Cause: Firmware from version V02.30.01.00 is required when connecting the power units in parallel. Remedy:
|
| F05061 Infeed VSM count | Cause: The number of active Voltage Sensing Modules (VSM) for the drive object infeed with chassis power units is not correct. For A_Infeed, each active power unit must be assigned an active VSM also for a parallel circuit configuration. For S_Infeed, the active drive object, must be assigned at least one active VSM. Fault value (r0949, interpret decimal): Number of VSMs that are currently assigned to the drive object. Remedy:
|
| F05064 Parallel connection: Pulse synchronization error | Cause: The pulse synchronization of at least one of the power units connected in parallel is incorrect. Remedy:
|
| A05065 (F, N) Voltage measured values not plausible | Cause: The voltage measurement does not supply any plausible values and is not used. Alarm value (r2124, interpret bitwise binary): Bit 1: Phase U Bit 2: Phase V Bit 3: Phase W Remedy:
|
| F05118 (A) Precharging contactor simultaneity monitoring time exceeded | Cause: A feedback signal for the precharging contactor (ALM, SLM, BLM diode) or the line contactor (BLM thyristor) interconnected and the simultaneity monitoring (p0255[4, 6]) activated. After opening or closing a contactor of the parallel connection, after a monitoring time has elapsed, not all of the contactors have assumed the same state. Fault value (r0949, interpret binary): yyyyxxxx hex: yyyy = supplementary information, xxxx = fault cause Fault cause:
Supplementary information:
Note: ALM: Active Line Module, BLM: Basic Line Module, PDS: Power unit Data Set, SLM: Smart Line Module Remedy:
|
| F05119 (A) Bypass contactor simultaneity monitoring time exceeded | Cause: A feedback signal for the bypass contactor is interconnected and the simultaneity monitoring (p0255[5, 7]) activated. After opening or closing a contactor of the parallel connection, after a monitoring time has elapsed, not all of the contactors have assumed the same state. Fault value (r0949, interpret binary): yyyyxxxx hex: yyyy = supplementary information, xxxx = fault cause Fault cause:
Supplementary information:
Note: PDS: Power unit Data Set Remedy:
|
| F06000 Infeed: Precharging monitoring time expired | Cause: After the line contactor closes the power unit does not signal the READY state within the monitoring time (p0857). The end of the DC link precharging was not able to be completed for one of the following reasons:
See also: p0210 (Drive unit line supply voltage), p0857 (Power unit monitoring time) Remedy:
|
| F06010 Infeed: Power unit EP 24 V missing in operation | Cause: In operation, the pulse enable via terminal EP at the Line Module (X21.3, X21.4) was withdrawn. Note: EP: Enable Pulses (pulse enable) Remedy:
|
| F06100 Infeed: Shutdown due to line supply undervoltage condition | Cause: The filtered (steady-state) value of the line supply voltage is less than the fault threshold (p0283). Fault condition: Vrms < p0283 * p0210 Fault value (r0949, floating point): Actual steady-state line supply voltage. Note: The occurrence of this fault is delayed by the time in p3492. If the fault is removed during this design time, then the power unit is not tripped (shut down). Remedy:
|
| A06105 (F) Infeed: Line supply undervoltage | Cause: The filtered (steady-state) value of line supply voltage is lower than the alarm threshold (p0282). Alarm condition: Vrms < p0282 * p0210 Alarm value (r2124, floating point): Actual steady-state line supply voltage. Remedy:
|
| F06211 Infeed: Summation current impermissibly high | Cause: The smoothed sum of the phase currents (i1 + i2 + i3) is impermissibly high. The summed current has exceeded the parameterized threshold for the ground fault monitoring (p0287). Possible causes:
Fault value (r0949, floating point): Smoothed total of the phase currents. Remedy:
|
| A06301 (F) Infeed: Line supply overvoltage | Cause: The filtered (steady-state) value of the rms line supply voltage Vrms is higher than the alarm threshold (p0281). Alarm condition: Vrms > p0281 * p0210. Alarm value (r2124, floating point): Actual steady-state line supply voltage. Remedy:
|
| F06310 (A) Supply voltage (p0210) incorrectly parameterized | Cause: For AC/AC drive units, the measured DC voltage lies outside the tolerance range after precharging has been completed. The following applies for the tolerance range: 1.16 * p0210 < r0070 < 1.6 * p0210 Note: The fault can only be acknowledged when the drive is switched off. See also: p0210 (Drive unit line supply voltage) Remedy:
|
| F06311 Infeed: Supply voltage (p0210) incorrect | Cause: The line voltage nominal value indicated in p0210 is outside the nominal voltage range of the power unit. After precharging was completed, the actual line supply voltage Vrms was calculated using the measured DC link voltage. This voltage Vrms does not lie within the extended tolerance range of the supply voltage set in p0210. The following applies for the extended tolerance range: 75 % * p0210 < Vrms < 120 % * p0210 Alarm value (r2124, floating point): Line supply voltage Vrms present. See also: p0210 (Drive unit line supply voltage) Remedy:
|
| F06700 (A) Infeed: Switch line contactor for load condition | Cause: For an ON command, the infeed line contactor should be switched under load. Remedy:
|
| A06810 (F) Infeed: DC link voltage alarm threshold | Cause: In operation, the DC link voltage has dropped to below the alarm threshold. The alarm threshold is obtained from the sum of p0279 and r0296. The status is also displayed in r3405.bit7. Possible causes include:
See also: p0279 (DC link voltage offset alarm threshold), r0296 (DC link voltage undervoltage threshold), r3405 Remedy:
|
| A06900 (F) Braking Module: Fault (1 -> 0) | Cause: The Braking Module signals a fault (1 -> 0) via X21.4 (“booksize” format) or X21.5 (“chassis” format). This signal is wired to a system digital input and correspondingly interconnected using binector input p3866[0…7]. Possible causes:
See also: p3866 (Braking Module fault) Remedy:
|
| A06901 Braking Module: Pre-alarm I2t shutdown | Cause: The Braking Module “Booksize” format signals “Pre-alarm I2t shutdown” via terminal X21.3. This signal is wired to a system digital input and correspondingly interconnected using binector input p3865[0…7]. Note: This function is not supported for the “chassis” format. Remedy:
|
| A06904 (N) Braking Module internal is inhibited | Cause: The internal Braking Module was inhibited via binector input p3680 = 1 signal. In the inhibited state, energy cannot be dissipated using the braking resistor. See also: p3680 (Braking Module internal inhibit) Remedy:
|
| A06905 Braking Module internal I2t shutdown alarm | Cause: The internal Braking Module outputs an alarm due to the high I2t value. 80% of the maximum switch-on duration of the braking resistor has been reached. Note: This message is also displayed via BO: p3685. See also: r3685 (Digital Braking Module: Pre-alarm I2t shutdown) Remedy:
|
| F06906 (A) Braking Module internal fault | Cause: The internal Braking Module outputs a fault due to overcurrent or an excessively high I2t value and is therefore inhibited. Note: This message is also displayed via BO: p3686. Fault value (r0949, interpret bitwise binary):
See also: r3686 (Digital Braking Module fault) Remedy:
|
| F06907 Braking Module internal overtemperature | Cause: The temperature sensor connected to the braking resistor signals an overtemperature. The Braking Module is still active. If the overtemperature persists for more than 60 s, fault F06908 is output, and the braking module is switched off. See also: r3687 (Digital Braking Module pre-alarm overtemperature) Remedy:
|
| F06908 Braking Module internal overtemperature shutdown | Cause: Braking module shut down due to overtemperature at the temperature sensor of the braking resistor. The overtemperature is detected by the sensor for longer than 60 s. See also: r3688 (Braking Module internal overtemperature shutdown) Remedy:
|
| F06909 Braking Module internal Vce fault | Cause: In the power unit, the monitoring of the collector-emitter voltage (U_ce) of the power semiconductor to control the braking resistor has responded. Possible causes:
Note: Under certain circumstances, this alarm is also output if a braking resistor has not been connected and power is fed back into the Braking Module. See also: r3689 (Digital Braking Module Uce fault) Remedy:
|
| A06921 (N) Braking resistor phase unsymmetry | Cause:
Remedy:
|
| F06922 Braking resistor phase failure | Cause: A phase failure for the brake resistor was detected. Fault value (r0949, interpret decimal):
See also: p3235 (Phase failure signal motor monitoring time) Remedy:
|
| F07011 Drive: Motor overtemperature | Cause: KTY84/PT1000 or no sensor: The measured motor temperature or model temperature has exceeded the fault threshold (p0605) or the timer (p0606) has elapsed following the alarm threshold (p0604) being exceeded. The response parameterized in p0610 becomes active. PTC or bimetallic NC contact: The response threshold of 1650 Ohm was exceeded or the NC contact opened and the timer (p0606) has expired. The response parameterized in p0610 becomes active. Possible causes:
Fault value (r0949, interpret decimal): 200: The motor temperature model 1 (I2t) signals an overtemperature (p0612.0 = 1, p0611 > 0, p0615 reached). Number of the temperature channel leading to the message (for SME/TM120 (p0601 = 10, 11)). See also: p0604, p0605, p0606, p0612, p0613, p0625, p0626, p0627, p0628 Remedy:
|
| A07012 (N) Drive: Motor temperature model 1/3 overtemperature | Cause: The motor temperature model 1/3 identified that the alarm threshold was exceeded. Hysteresis:2K. Alarm value (r2124, interpret decimal): 200: Motor temperature model 1 (I2t): Temperature too high (p0605). 300: Motor temperature model 3: Temperature too high (p5398). See also: r0034 (Motor utilization thermal), p0605 (Mot_temp_mod 1/2 sensor threshold and temperature value), p0611 (I2t motor model thermal time constant), p0612 (Mot_temp_mod activation), p0613 (Mot_temp_mod 1/3 ambient temperature) Remedy:
|
| A07014 (N) Drive: Motor temperature model configuration alarm | Cause: A fault has occurred in the configuration of the motor temperature model. Alarm value (r2124, interpret decimal): 1: All motor temperature models: It is not possible to save the model temperature See also: p0610 (Motor overtemperature response) Remedy:
|
| A07015 Drive: Motor temperature sensor alarm | Cause: An error was detected when evaluating the temperature sensor set in p0600 and p0601. With the fault, the time in p0607 is started. If the fault is still present after this time has expired, then fault F07016 is output; however, at the earliest, 50 ms after alarm A07015. Possible causes:
Alarm value (r2124, interpret decimal): – if SME/TM120 is selected (p0601 = 10, 11), this is the number of the temperature channel leading to the message. Remedy:
|
| F07016 Drive: Motor temperature sensor fault | Cause: An error was detected when evaluating the temperature sensor set in p0600 and p0601. Possible causes:
Note: If alarm A07015 is present, the time in p0607 is started. If the fault is still present after this time has expired, then fault F07016 is output; however, at the earliest, 50 ms after alarm A07015. Fault value (r0949, interpret decimal): – if SME/TM120 is selected (p0601 = 10, 11), this is the number of the temperature channel leading to the message. See also: p0607 (Temperature sensor fault timer) Remedy:
|
| F07080 Drive: Incorrect control parameter | Cause: The closed-loop control parameters have been parameterized incorrectly (e.g. p0356 = L_spread = 0). Fault value (r0949, interpret decimal): The fault value includes the parameter number involved. See also: p0310, p0311, p0341, p0344, p0350, p0354, p0356, p0357, p0358, p0360, p0400, p0404, p0408, p0640, p1082, p1300 Remedy:
|
| F07082 Macro: Execution not possible | Cause: The macro cannot be executed. Fault value (r0949, interpret hexadecimal): ccccbbaa hex: cccc = preliminary parameter number, bb = supplementary information, aa = fault cause Fault causes for the trigger parameter itself: 19: Called file is not valid for the trigger parameter. … 61: The setting of a value was unsuccessful. Remedy:
|
| F07083 Macro: ACX file not found | Cause: The ACX file (macro) to be executed was not able to be found in the appropriate directory. Fault value (r0949, interpret decimal): Parameter number with which the execution was started. See also: p0015, p0700, p1000, p1500 Remedy:
|
| F07084 Macro: Condition for WaitUntil not fulfilled | Cause: The WaitUntil condition set in the macro was not fulfilled in a certain number of attempts. Fault value (r0949, interpret decimal): Parameter number for which the condition was set. Remedy:
|
| F07085 Drive: Open-loop/closed-loop control parameters changed | Cause: Open-loop/closed-loop control parameters have had to be changed. Possible causes:
Fault value (r0949, interpret decimal): Changed parameter number. 340: The motor and control parameters were automatically calculated (p0340 = 1), because the vector control was subsequently activated as configuration (r0108.2). 611: The time constant for thermal motor model 1 was estimated. 612: Thermal motor model 1 was activated (p0612.0 = 1). See also: p0640 (Current limit), p1082 (Maximum speed), p1300 (Open-loop/closed-loop control operating mode), p1800 (Pulse frequency setpoint) Remedy:
|
| F07086 Units changeover: Parameter limit violation due to reference value change | Cause: A reference parameter was changed in the system. This resulted in the fact that for the parameters involved, the selected value was not able to be written in the per unit notation. The values of the parameters were set to the corresponding violated minimum limit/maximum limit or to the factory setting. Possible causes: the steady-state minimum limit/maximum limit or that defined in the application was violated. Fault value (r0949, parameter): Diagnostics parameter to display the parameters that were not able to be re-calculated. See also: p0304, p0305, p0310, p0596, p2000, p2001, p2002, p2003, r2004 Remedy:
|
| F07088 Units changeover: Parameter limit violation due to units changeover | Cause: A changeover of units was initiated. This resulted in a violation of a parameter limit Possible causes for the violation of a parameter limit:
Fault value (r0949, interpret decimal): Diagnostics parameter r9451 to display all parameters whose value had to be adapted. See also: p0100 (IEC/NEMA mot stds), p0349 (System of units motor equivalent circuit diagram data), p0505 (Selecting the system of units), p0595 (Technological unit selection) Remedy:
|
| 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. See also: p0100 (IEC/NEMA mot stds), p0349 (System of units motor equivalent circuit diagram data), p0505 (Selecting the system of units) Remedy:
|
| A07092 Drive: moment of inertia estimator still not ready | Cause: The moment of inertia estimator has still not determined any valid values. The acceleration cannot be calculated. The moment of inertia estimator has stabilized, if the frictional values (p1563, p1564) as well as the moment of inertia value (p1493) have been determined and the appropriate status signal is set (r1407.26 = 1). The following parameters influence the response of the moment of the inertia estimator: p1560, p1561, p1562 Remedy:
|
| A07094 General parameter limit violation | Cause: As a result of the violation of a parameter limit, the parameter value was automatically corrected. Minimum limit violated –> parameter is set to the minimum value. Maximum limit violated –> parameter is set to the maximum value. Alarm value (r2124, interpret decimal): Parameter number, whose value had to be adapted. Remedy:
|
| F07100 Drive: Sampling times cannot be reset | Cause: When resetting drive parameter (p0976) sampling times cannot be reset using p0111, p0112, p0115. Fault value (r0949, interpret decimal): Parameter whose setting prevents the sampling times being reset. See also: r0110 (Basic sampling times) Remedy:
|
| F07110 Drive: Sampling times and basic clock cycle do not match | Cause: The parameterized sampling times do not match the basic clock cycle. Fault value (r0949, interpret decimal): The fault value specifies the parameter involved. See also: r0110, r0111, p0115 Remedy:
|
| A07200 Drive: Master control ON command present | Cause: The ON/OFF1 command is present (no 0 signal). The command is either influenced via binector input p0840 (current CDS) or control word bit 0 via the master control. Remedy:
|
| F07220 (N, A) Drive: Master control by PLC missing | Cause: The “master control by PLC” signal was missing in operation.
Remedy:
|
| F07300 (A) Drive: Line contactor feedback signal missing | Cause:
Remedy:
|
| F07311 Bypass motor switch | Cause: Fault value (r0949, interpret bitwise binary):
See also: p1260 (Bypass configuration), r1261 (Bypass control/status word), p1266 (Bypass control command), p1267 (Bypass changeover source configuration), p1269 (Bypass switch feedback signal), p1274 (Bypass switch monitoring time) Remedy:
|
| F07312 Bypass LSS: | Cause: Fault value (r0949, interpret bitwise binary):
See also: p1260 (Bypass configuration), r1261 (Bypass control/status word), p1266 (Bypass control command), p1267 (Bypass changeover source configuration), p1269 (Bypass switch feedback signal), p1274 (Bypass switch monitoring time) Remedy:
|
| F07320 Drive: Automatic restart interrupted | Cause:
Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| A07321 Drive: Automatic restart active | Cause: The automatic restart (AR) is active. When the line supply returns and/or the causes of the existing faults are removed the drive is automatically restarted. The pulses are enabled and the motor starts to rotate. Remedy:
|
| F07330 Flying restart: Measured search current too low | Cause: During a flying restart, it was identified that the search current reached is too low. It is possible that the motor is not connected. Remedy:
|
| F07331 Flying restart: Function not supported | Cause: It is not possible to power up with the motor rotating (no flying restart). In the following cases, the “flying restart” function is not supported: Permanent-magnet synchronous motor (PMSM):
Separately excited synchronous motor (SESM):
Remedy:
|
| N07332 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. Possible causes: power ratio, power unit/motor too high Remedy:
|
| A07350 (F) Drive: Measuring probe parameterized to a digital output | Cause: The measuring probe is connected to a bi-directional digital input/output and the terminal is set as output. Alarm value (r2124, interpret decimal):
Regarding the terminal designation: The first designation is valid for CU320, the second for CU305. Remedy:
|
| A07400 (N) Drive: DC link voltage maximum controller active | Cause: The DC link voltage controller has been activated because the upper switch-in threshold has been exceeded (r1242, r1282). The ramp-down times are automatically increased in order to maintain the DC link voltage (r0070) within the permissible limits. There is a system deviation between the setpoint and actual speeds. When the DC link voltage controller is switched out (disabled), this is the reason that the ramp-function generator output is set to the speed actual value. See also: r0056 (Status word, closed-loop control), p1240 (Vdc controller or Vdc monitoring configuration), p1280 (Vdc controller or Vdc monitoring configuration (U/f)) Remedy:
|
| A07401 (N) Drive: DC link voltage maximum controller deactivated | Cause: The Vdc_max controller can no longer maintain the DC link voltage (r0070) below the limit value (r1242, r1282) and was therefore switched out (disabled).
Remedy:
|
| A07402 (N) Drive: DC link voltage minimum controller active | Cause: The DC link voltage controller has been activated as the lower switch-in threshold has been undershot (r1246, r1286). The kinetic energy of the motor is used to buffer the DC link. The drive is therefore braked. See also: r0056 (Status word, closed-loop control), p1240 (Vdc controller or Vdc monitoring configuration), p1280 (Vdc controller or Vdc monitoring configuration (U/f)) Remedy:
|
| F07403 (N, A) Drive: Lower DC link voltage threshold reached | Cause: The DC link voltage monitoring is active (p1240, p1280 = 5, 6) and the lower DC link voltage threshold (r1246, r1286) was reached in the “Operation” state. Remedy:
|
| F07404 Drive: Upper DC link voltage threshold reached | Cause:
Remedy:
|
| F07405 (N, A) Drive: Kinetic buffering minimum speed fallen below | Cause: During kinetic buffering the speed fell below minimum speed (p1257 or p1297 for vector drives with U/f control) and the line supply did not return. Remedy: Check the speed threshold for the Vdc_min controller (kinetic buffering) (p1257, p1297). See also: p1257 (Vdc_min controller speed threshold), p1297 (Vdc_min controller speed threshold (U/f)) |
| F07406 (N, A) Drive: Kinetic buffering maximum time exceeded | Cause: The maximum buffer time (p1255 and p1295 for vector drives with U/f control) has been exceeded without the line supply having returned. Remedy: Check the time threshold for Vdc-min controller (kinetic buffering) (p1255, p1295). See also: p1255 (Vdc_min controller time threshold), p1295 (Vdc_min controller time threshold (U/f)) |
| F07407 Drive: Vdc reduction not permissible | Cause: For chassis power units, the reduction of the line voltage (see r0212.0) is only possible for closed-loop control of the DC link voltage. Remedy:
See also: p0212 (Power unit configuration) |
| 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 “l_act = 0 and Uq_set_1 longer than 16 ms at its limit” is present and can be caused by the following:
Remedy:
|
| F07411 Drive: Flux 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:
|
| F07412 Drive: Commutation angle incorrect (motor model) | Cause: An incorrect commutation angle was detected that can result in a positive coupling in the speed controller. Possible causes:
Remedy:
Note: For High Dynamic Motors (1FK7xxx-7xxx), for applications with a higher current, if necessary, the monitoring should be disabled. |
| F07413 Drive: Commutation angle incorrect (pole position identification) | Cause: An incorrect commutation angle was detected that can result in a positive coupling in the speed controller. Within the pole position identification routine (p1982 = 2): – a difference of > 45 ° electrical to the encoder angle was determined. For VECTOR, within the encoder adjustment (p1990 = 2): – a difference of > 6 ° electrical to the encoder angle was determined. Remedy:
|
| A07416 Drive: Flux controller configuration | Cause: The configuration of the flux control (p1401) is contradictory. Remedy: For fault cause = 1:
For fault cause = 2:
For fault cause = 3:
|
| F07417 Drive: Pulse technique not plausible (motor model) | Cause: The evaluation of the test pulse response indicated incorrect values. Remedy: For fault value = 0:
For fault value = 10:
For fault value = 20:
|
| F07422 Drive: Reference model natural frequency > Shannon frequency | Cause: The natural filter frequency of the PT2 element for the reference model (p1433) is greater than the Shannon frequency. The Shannon frequency is calculated according to the following formula: 0.5 / p0115[1]. Remedy:
|
| F07426 (A) Technology controller actual value limited | Cause: The actual value for the technology controller, interconnected via connector input p2264, has reached a limit. Remedy:
|
| A07428 (N) Technology controller parameterizing error | Cause: The technology controller has a parameterizing error. Alarm value (r2124, interpret decimal): 1: The upper output limit in p2291 is set lower than the lower output limit in p2292. Remedy: For alarm value = 1: Set the output limit in p2291 higher than in p2292. |
| F07434 Drive: It is not possible to change the direction of rotation with the pulses enabled | Cause: A drive data set was selected – with the pulses enabled – which has a different parameterized direction of rotation (p1821). It is only possible to change the motor direction of rotation using p1821 when the pulses are inhibited. Remedy:
|
| 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) or bypassed (p1122). An internal setting command of the ramp-function generator output caused the set setpoint speed to be frozen or was not able to be realized. The drive is switched-on with flying restart activated (p1200), and at the same time the ramp-function generator is bypassed (p1122). 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. Remedy:
|
| 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) and the determined number of the drive data set (p2733), they must be saved in a non-volatile fashion (p0971, p0977). Possible causes:
Remedy: Readjust the encoder. |
| 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. |
| 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. Remedy: Set the reference point coordinate to a lower value than specified in the fault value. |
| F07446 (A) Load gear: Position tracking cannot be reset | Cause: The position tracking cannot be reset. Remedy: Reset the position tracking as follows:
Then acknowledge the fault and, if necessary, re-adjust the absolute encoder (p2507). |
| F07447 Load gear: Position tracking, maximum actual value exceeded | Cause: When the position tracking of the load gear is configured, the drive/encoder (motor encoder) identifies a maximum possible absolute position actual value (r2723) that can no longer be represented within 32 bits. Remedy:
|
| F07448 (A) Load gear: Position tracking, linear axis has exceeded the maximum range | Cause: For a configured linear axis/no modulo axis, the currently effective motor encoder (encoder 1) has exceeded the maximum possible traversing range. Remedy: The fault should be resolved as follows:
The fault should then be acknowledged and the absolute encoder adjusted. |
| F07449 (A) Load gear: Position tracking actual position outside tolerance window | Cause: When switched off, the currently effective motor encoder was moved through a distance greater than was parameterized in the tolerance window. It is possible that there is no longer any reference between the mechanical system and encoder. Remedy: Reset the position tracking as follows:
The fault should then be acknowledged and, if necessary, the absolute encoder adjusted (p2507). |
| 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. |
| 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. |
| A07455 EPOS: Maximum velocity limited | Cause: The maximum velocity (p2571) is too high to correctly calculate the modulo correction. Remedy:
|
| A07456 EPOS: Setpoint velocity limited | Cause: The actual setpoint velocity is greater than the parameterized maximum velocity (p2571) and is therefore limited. Remedy:
|
| F07500 Drive: Power unit data set PDS not configured | Cause: Only for controlled line supply infeed/regenerative feedback units: The power unit data set was not configured – this means that a data set number was not entered into the drive data set. Remedy: The index of the power unit data set associated with the drive data set should be entered into p0185. |
| F07501 Drive: Motor Data Set MDS not configured | Cause: Only for power units: The motor data set was not configured – this means that a data set number was not entered into the associated drive data set. Remedy: The index of the motor data set associated with the drive data set should be entered into p0186. See also: p0186 (Motor Data Sets (MDS) number) |
| F07502 Drive: Encoder Data Set EDS not configured | Cause: Only for power units: The encoder data set was not configured – this means that a data set number was not entered into the associated drive data set. Remedy: The index of the encoder data set associated with the drive data set should be entered into p0187 (1st encoder), p0188 (2nd encoder) and p0189 (3rd encoder). |
| 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:
|
| A07504 Drive: Motor data set is not assigned to a drive data set | Cause: A motor data set is not assigned to a drive object. All of the existing motor data sets in the drive data sets must be assigned using the MDS number (p0186[0…n]). There must be at least as many drive data sets as motor data sets. Remedy: In the drive data sets, assign the non-assigned motor data set using the MDS number (p0186[0…n]).
|
| 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:
|
| A07506 EPOS: check BICO interconnection between EPOS and position controller | Cause: The BICO interconnections to transfer setpoints between EPOS and LR (position control) have not been set, although the BICO interconnections to transfer the fine resolutions have been set. Remedy: 1. Disconnect BICO interconnections for the fine resolutions (CI: p2694 = 0, CI: p2695 = 0). 2. Set BICO interconnections for the setpoints (CI: p2530 = r2665, CI: p2531 = r2666). 3. Set BICO interconnections for the fine resolutions (CI: p2694 = r2696, CI: p2695 = r2697). |
| F07509 Drive: Component assignment missing | Cause: A Drive Data Set (DDS) is assigned to a Motor Data Set (MDS) or Encoder Data Set (EDS) that does not have a component number. Remedy: In the drive data sets, no longer assign MDS/EDS using p0186, p0187, p0188, p0189 or set a valid component number. |
| F07510 Drive: Identical encoder in the drive data set | Cause: More than one encoder with identical component number is assigned to a single drive data set. In one drive data set, it is not permissible that identical encoders are operated together. Remedy: Assign the drive data set to different encoders. |
| F07511 Drive: Encoder used a multiple number of times | Cause: Each encoder may only be assigned to one drive and within a drive must – in each drive data set – either always be encoder 1, always encoder 2 or always encoder 3. This unique assignment has been violated. Remedy: Correct the double use of a component number using the two parameters coded in the fault value. |
| F07512 Drive: Encoder data set changeover cannot be parameterized | Cause: Using p0141, a changeover of the encoder data set is prepared that is illegal. In this firmware release, an encoder data set changeover is only permitted for the components in the actual topology. Remedy: Every encoder data set must be assigned its own dedicated DRIVE-CLiQ socket. The component numbers of the encoder interfaces (p0141) must have different values within a drive object. |
| A07514 (N) Drive: Data structure does not correspond to the interface module | Cause: The interface mode “SIMODRIVE 611 universal” was set (p2038 = 1) and the data structure does not correspond to this mode. Remedy:
|
| F07515 Drive: Power unit and motor incorrectly connected | Cause: A power unit (via PDS) was assigned to a motor (via MDS) in a drive data set that is not connected in the target topology. It is possible that a motor has not been assigned to the power unit (p0131). Remedy:
|
| F07516 Drive: Re-commission the data set | Cause: The assignment between the drive data set and motor data set (p0186) or between the drive data set and the encoder data set was modified (p0187). This is the reason that the drive data set must re-commissioned. Remedy: Commission the drive data set specified in the fault value (r0949). |
| F07517 Drive: Encoder data set changeover incorrectly parameterized | Cause: An MDS cannot have different motor encoders in two different DDS. Remedy: If you wish to operate a motor once with one motor encoder and then another time with the other motor encoder, then you must set up two different MDSs, in which the motor data are the same. |
| F07518 Drive: Motor data set changeover incorrectly parameterized | Cause: The system has identified that two motor data sets were incorrectly parameterized. It is not possible to toggle between motor data sets. Remedy: Correct the parameterization of the motor data sets. |
| A07519 Drive: Motor changeover incorrectly parameterized | Cause: With the setting p0833.0 = 1, a motor changeover via the application is selected. This is the reason that p0827 must have different values in the appropriate motor data set. Remedy:
|
| A07520 Drive: Motor cannot be changed over | Cause: The motor cannot be changed over. Remedy: For alarm value = 1: Set the speed lower than the speed at the start of field weakening (r0063 < p0348). For alarm value = 2, 3: Check the feedback signals of the contactor involved. |
| 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:
|
| A07541 Drive: Data set changeover not possible | Cause: The selected drive data set changeover and the assigned motor changeover are not possible and are not carried out. For synchronous motors, the motor contactor may only be switched for actual speeds less than the speed at the start of field weakening (r0063 < p0348). Remedy: Reduce the speed to below the speed at the start of field weakening (r0063 < p0348). |
| 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. The encoder parameters are directly read out of the encoder via DRIVE-CLiQ. Remedy:
|
| F07551 Drive encoder: No commutation angle information | Cause: The commutation angle information is missing. This means that synchronous motors cannot be controlled (closed-loop control). Remedy: For fault cause = 1:
For fault cause = 2:
|
| 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. Remedy:
|
| F07553 (A) Drive encoder: Sensor Module configuration not supported | Cause: The Sensor Module does not support the requested configuration. Remedy:
|
| F07555 (A) Drive encoder: Configuration position tracking | Cause: For position tracking, the configuration is not supported. Position tracking can only be activated for absolute encoders. For linear axes, it is not possible to simultaneously activate the position tracking for load and measuring gears. Remedy: For fault value 0: use an absolute encoder. For fault value 1: use a Control Unit with sufficient NVRAM. For fault value = 2, 4: if necessary, de-select the position tracking (p0411 for the measuring gear, p2720 for the load gear). For fault value 3: Only activate position tracking of the load gear in the same encoder data set if the gear ratio (p2504, p2505), axis type (p2720.1) and tolerance window (p2722) are also the same. |
| F07556 Measuring gear: Position tracking, maximum actual value exceeded | Cause: When the position tracking of the measuring gear is configured, the drive/encoder identifies a maximum possible absolute position actual value (r0483) that cannot be represented within 32 bits. 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. |
| F07575 Drive: Motor encoder not ready | Cause: The motor encoder signals that it is not ready.
Remedy: Evaluate other queued faults via encoder 1. |
| F07800 Drive: No power unit present | Cause: The power unit parameters cannot be read or no parameters are stored in the power unit. It is possible that the DRIVE-CLiQ cable between the Control Unit and power unit is interrupted or defective. Remedy:
|
| F07801 Drive: Motor overcurrent | Cause: The permissible motor limit current was exceeded.
Remedy:
|
| F07802 Drive: Infeed or power unit not ready | Cause: After an internal switch-on command, the infeed or drive does not signal ready.
Remedy:
|
| A07805 (N) Drive: Power unit overload I2t | Cause: Alarm threshold for I2t overload (p0294) of the power unit exceeded. The response parameterized in p0290 becomes active. Remedy:
|
| A07805 (N) Infeed: Power unit overload I2t | Cause: Alarm threshold for I2t overload (p0294) of the power unit exceeded. Remedy:
|
| F07807 Drive: Short-circuit/ground fault detected | Cause: A phase-phase short-circuit or ground fault was detected at the motor-side output terminals of the converter. Fault value (r0949, interpret decimal): 1: Short-circuit, phase UV. 2: Short-circuit, phase UW. 3: Short-circuit, phase VW. 4: Ground fault with overcurrent. Remedy:
|
| F07808 (A) HF Damping Module: damping not ready | Cause: When switching on or in the switched-on state, the HF Damping Module does not return a ready signal. Remedy:
|
| F07810 Drive: Power unit EEPROM without rated data | Cause: No rated data are stored in the power unit EEPROM. Remedy: Replace the power unit or inform Siemens Customer Service. |
| F07815 Drive: Power unit has been changed | Cause: The code number of the actual power unit does not match the saved number. This only occurs if the comparator in p9906 or p9908 is not at 2 (low) or 3 (minimum). Remedy: Connect the original power unit and switch on the Control Unit again (POWER ON) or set p0201 to r0200 and exit commissioning with p0010 = 0. For infeeds, the following applies: Line reactors or line filters must be used that are specified for the new power unit. A line supply and DC link identification routine (p3410 = 5) must then be carried out. It is not possible to change the power unit without re-commissioning the system if the type of infeed, construction/design or the voltage class differ between old and new power units. |
| A07820 Drive: Temperature sensor not connected | Cause: The temperature sensor for monitoring the motor temperature, specified in p0600, is not available. Remedy:
|
| A07821 Monitoring underspeed threshold fallen below alarm | Cause: The alarm threshold for the lower speed was fallen below. Remedy:
|
| F07822 (N) Monitoring underspeed threshold fallen below fault | Cause: The fault threshold for the lower speed was fallen below. Remedy:
|
| A07823 I2t monitoring alarm threshold exceeded | Cause: For the freely parameterizable I2t monitoring, the alarm threshold (p3243) was exceeded. Remedy:
|
| F07824 I2t monitoring fault threshold exceeded | Cause: For the freely parameterizable I2t monitoring, the fault threshold (100 %) was exceeded. Remedy:
|
| A07825 (N) Drive: Simulation mode activated | Cause: The simulation mode is activated. The drive can only be switched on if the DC link voltage is less than 40 V. Remedy: Not necessary. The alarm automatically disappears if simulation mode is deactivated with p1272 = 0. |
| F07826 Drive: DC link voltage for simulation operation too high | Cause: The simulation mode is activated and the DC link voltage is greater than the permissible value of 40 V. Remedy:
|
| F07840 Drive: Infeed operation missing | Cause: The signal “infeed operation” is not present although the enable signals for the drive have been present for longer than the parameterized monitoring time (p0857). Remedy:
|
| F07841 (A) Drive: Infeed operation withdrawn | Cause: The signal “infeed operation” was withdrawn in operation. Remedy:
|
| A07850 (F) External alarm 1 | Cause: The condition for “External alarm 1” is satisfied. Remedy: Eliminate the causes of this alarm. |
| A07851 (F) External alarm 2 | Cause: The condition for “External alarm 2” is satisfied. Remedy: Eliminate the causes of this alarm. |
| A07852 (F) External alarm 3 | Cause: The condition for “External alarm 3” is satisfied. Remedy: Eliminate the causes of this alarm. |
| F07860 (A) External fault 1 | Cause: The condition for “External fault 1” is satisfied. Remedy:
|
| F07861 (A) External fault 2 | Cause: The condition for “External fault 2” is satisfied. Remedy:
|
| F07862 (A) External fault 3 | Cause: The condition for “External fault 3” is satisfied. Remedy:
|
| F07890 Internal voltage protection / internal armature short-circuit with STO active | Cause: The internal armature short-circuit (p1231 = 4) is not possible as Safe Torque Off (STO) is enabled. The pulses cannot be enabled. Remedy: Switch out the internal armature short-circuit (p1231=0) or deactivate Safe Torque Off (p9501 = p9561 = 0). |
| F07898 Drive: flying restart unsuccessful due to excessively low flux | Cause: While identifying the rotor position of a separately excited synchronous motor based on voltage measurement, after the excitation time had elapsed, the flux was too low. Remedy: Increase the excitation time (p0346). |
| A07899 (N) Drive: Stall monitoring not possible | Cause: Stall monitoring is not possible, because a change was made into the open-loop speed controlled mode before the wait time p2177 had expired. Remedy: – Deactivate the changeover into open-loop speed controlled operation when operating at the torque limit (p1750.6 = 0). – shorten the stall detection wait time (p2177 < p1758). – Activate closed-loop controlled operation from standstill and higher (p1750.2 = 1). – Use an operating mode with encoder (p1300 = 21). |
| 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 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: The system has identified that the motor has stalled for a time longer than is set in p2178. Remedy:
|
| A07903 Drive: Motor speed deviation | Cause: The absolute value of the speed difference from the setpoints (p2151, p2154) and the actual speed (r2169) exceeds the tolerance threshold (p2163) longer than tolerated (p2164, p2166). Remedy:
|
| F07904 (N, A) External armature short-circuit: Contactor feedback signal “Closed” missing | Cause: When closing, the contactor feedback signal (p1235) did not issue the signal “Closed” (r1239.1 = 1) within the monitoring time (p1236). Remedy:
|
| F07905 (N, A) External armature short-circuit: Contactor feedback signal “Open” missing | Cause: When opening, the contactor feedback signal (p1235) did not issue the signal “Open” (r1239.1 = 0) within the monitoring time (p1236). Remedy:
|
| F07906 Armature short-circuit / internal voltage protection: Parameterization error | Cause: The armature short-circuit is incorrectly parameterized. Remedy:
|
| F07907 Internal armature short-circuit: Motor terminals are not at zero potential after pulse suppression | Cause: The function “Internal voltage protection” (p1231 = 3) was activated. Remedy: Not necessary. This is a note for the user. The following must be observed:
|
| A07908 Internal armature short-circuit active | Cause: The Motor Module signals that the motor is short-circuited through the power semiconductors (r1239.5 = 1). The internal armature short-circuit is selected (p1231 = 4). Remedy: For synchronous motors, the armature short-circuit braking is activated with binector input p1230 = 1 signal. |
| F07909 Internal voltage protection: Deactivation only effective after POWER ON | Cause: The deactivation of the internal voltage protection (p1231 not equal to 3) only becomes effective after POWER ON. Remedy: Not necessary. This is a note for the user. |
| A07910 (N) Drive: Motor overtemperature | Cause: The measured motor temperature or temperature from model 2 has exceeded the alarm threshold (p0604, p0616). For PTC, the response threshold of 1650 Ohm was exceeded or the NC contact opened. Remedy:
|
| F07913 Excitation current outside the tolerance range | Cause: The difference between the excitation current actual value and setpoint has exceeded the tolerance. Remedy:
|
| F07914 Flux out of tolerance | Cause: The difference between the flux actual value and setpoint has exceeded the tolerance. The fault is only issued after the delay time in p3206 has expired. Remedy:
|
| A07918 (N) Three-phase setpoint generator operation selected/active | Cause: Only for separately excited synchronous motors (p0300 = 5): The actual open-loop/closed-loop control mode is I/f control (open-loop) with a fixed current (p1300 = 18). Remedy: Select another open-loop/closed-loop control mode. |
| A07920 Drive: Torque/speed too low | Cause: The torque deviates from the torque/speed envelope characteristic (too low). Remedy:
|
| A07921 Drive: Torque/speed too high | Cause: The torque deviates from the torque/speed envelope characteristic (too high). Remedy:
|
| A07922 Drive: Torque/speed out of tolerance | Cause: The torque deviates from the torque/speed envelope characteristic. Remedy:
|
| F07923 Drive: Torque/speed too low | Cause: The torque deviates from the torque/speed envelope characteristic (too low). Remedy:
|
| F07924 Drive: Torque/speed too high | Cause: The torque deviates from the torque/speed envelope characteristic (too high). Remedy:
|
| F07925 Drive: Torque/speed out of tolerance | Cause: The torque deviates from the torque/speed envelope characteristic. Remedy:
|
| A07926 Drive: Envelope curve parameter invalid | Cause: Invalid parameter values were entered for the envelope characteristic of the load monitoring. Remedy:
|
| A07927 DC braking active | Cause: The motor is braked with DC current. DC braking is active. Remedy: Not necessary. The alarm automatically disappears once DC braking has been executed. |
| F07928 Internal voltage protection initiated | Cause: The Motor Module signals that the motor is short-circuited through the power semiconductors (r1239.5 = 1). The internal voltage protection is selected (p1231 = 3). Remedy: The armature short-circuit is activated and response OFF2 is initiated if the DC link voltage exceeds 800 V. If the DC link voltage falls below 450 V, then the armature short-circuit is withdrawn. If the autonomous internal voltage protection is active and the line supply returns, the armature short-circuit is withdrawn after 3 minutes. |
| F07930 Drive: Brake control error | Cause: The Control Unit has detected a brake control error. Possible causes include: motor cable not shielded correctly, or a defect in the control circuit of the Motor Module. Remedy:
|
| A07931 (F, N) Brake does not open | Cause: This alarm is output for r1229.4 = 1. Remedy:
|
| A07932 Brake does not close | Cause: This alarm is output for r1229.5 = 1. Remedy:
|
| F07934 (N) Drive: S120 Combi motor holding brake configuration | Cause: A connected motor holding brake has been detected with an S120 Combi. However, this brake has not been assigned to just one Combi feed drive and, therefore, brake control is not configured (correctly). Remedy: Check whether the motor holding brake has been assigned to one S120 Combi feed drive exclusively (p1215 = 1 or 2). The fault will only be withdrawn once the motor holding brake has been assigned to just one of the S120 Combi feed drives. |
| F07935 (N) Drive: Incorrect motor holding brake configuration | Cause: An incorrect motor holding brake configuration was detected. Remedy:
|
| F07937 (N) Drive: Speed deviation between motor model and external speed | Cause: The absolute value of the speed difference from the two actual values (r2169, r1443) exceeds the tolerance threshold (p3236) for longer than permitted (p3238). Remedy:
|
| F07940 Sync-line-drive: Synchronizing error | Cause: After synchronization has been completed, the phase difference (r3808) is greater than the threshold value, phase synchronism (p3813). Remedy: If required increase the threshold value phase synchronism (p3813) for synchronizing the line supply to the drive. Before OFF1 or OFF3, complete synchronizing (r03819.0 = 0). |
| A07941 Sync-line-drive: Target frequency not permissible | Cause: The target frequency is outside the permissible value range. Remedy: Fulfill the conditions for the target frequency for line-drive synchronization. See also: r1084 (Speed limit positive effective), r1087 (Speed limit negative effective). |
| A07942 Sync-line-drive: Setpoint frequency is completely different than the target frequency | Cause: There is a considerable difference between the setpoint frequency and the target frequency. The deviation that can be tolerated is set in p3806. Remedy: Not necessary. The alarm is automatically withdrawn after the difference that can be tolerated is reached. |
| A07943 Sync-line-drive: Synchronization not permitted | Cause: Synchronization is not permitted due to various active functions or incorrect settings (e.g., control mode, active motor ID, VSM not found). Remedy: Fulfill the conditions for the line-drive synchronization. For example, set the control mode (p1300) to encoderless closed-loop speed control (p1300 = 20) or U/f characteristic, exit motor data identification, connect the Voltage Sensing Module (VSM), etc. |
| F07950 (A) Drive: Incorrect motor parameter | Cause: The motor parameters were incorrectly entered while commissioning (e.g. p0300 = 0, no motor) or the braking resistor has not been parameterized. Remedy: Compare the motor data with the rating plate data and if required, correct. For fault value = 300 (CU250S-2): Operate a motor type supported by the selected control mode. |
| F07955 Drive: Motor has been changed | Cause: The code number of the actual motor with DRIVE-CLiQ does not match the saved number. Remedy: Connect the original motor, switch on the Control Unit again (POWER ON) and exit quick commissioning with p0010 = 0. Or set p0300 = 10000 (load the parameters from the motor with DRIVE-CLiQ) and re-commission. |
| F07956 (A) Drive: Motor code does not match the list (catalog) motor | Cause: The motor code of the connected motor with DRIVE-CLiQ does not match the possible list motor types (see selection in p0300). Remedy: Use a motor with DRIVE-CLiQ and the matching motor code. |
| A07960 Drive: Incorrect friction characteristic | Cause: The friction characteristic is incorrect. Remedy: Fulfill the conditions for the friction characteristic. Check the upper and lower effective torque limits. Fulfill the conditions to set the parameters of the friction characteristic. |
| A07961 Drive: Friction characteristic record activated | Cause: The automatic friction characteristic record is activated. The friction characteristic is recorded at the next switch-on command. Remedy: Not necessary. The alarm disappears automatically after the friction characteristic record has been successfully completed or the record is deactivated (p3845 = 0). |
| F07963 Drive: Friction characteristic record interrupted | Cause: The conditions to record the friction characteristic are not fulfilled. Remedy: Fulfill the conditions to record the friction characteristic. For example: establish missing enable signals, select the highest speed value to be approached less than or equal to the maximum speed, enable the permitted direction, set the control mode on the closed-loop speed control, etc. |
| F07967 Drive: Automatic encoder adjustment/pole position identification incorrect | Cause: A fault has occurred during the automatic encoder adjustment or the pole position identification. Remedy: Only for internal Siemens troubleshooting. Carry out a POWER ON. |
| F07968 Drive: Lq-Ld measurement incorrect | Cause: A fault has occurred during the Lq-Ld measurement. Remedy:
|
| F07969 Drive: Incorrect pole position identification | Cause: A fault has occurred during the pole position identification routine. Remedy: Remedy depends on the fault value (r0949). For example:
|
| F07970 Drive: Automatic encoder adjustment incorrect | Cause: A fault has occurred during the automatic encoder adjustment. Remedy: Remedy depends on the fault value (r0949). For example:
|
| A07971 (N) Drive: Angular commutation offset determination activated | Cause: The automatic determination of the angular commutation offset (encoder adjustment) is activated (p1990 = 1, 3). Remedy: Not necessary. The alarm automatically disappears after determination or for the setting p1990 = 0. |
| 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: Not necessary. The alarm disappears once the zero mark has been detected. |
| A07976 Drive: Fine encoder calibration activated | Cause: The alarm indicates the phases of the fine encoder calibration using the alarm value. 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: Not necessary. The alarm disappears automatically after the speed controller optimization has been successfully completed or for the setting p1900 = 0. |
| A07981 Drive: Enable signals for the rotating measurement missing | Cause: The rotating measurement cannot be started due to missing enable signals. Remedy: Establish missing enable signals. Acknowledge faults that are present. |
| F07982 Drive: Rotating measurement encoder test | Cause: A fault has occurred during the encoder test. Remedy: Remedy depends on fault value (r0949). For example:
|
| F07983 Drive: Rotating measurement saturation characteristic | Cause: A fault has occurred while determining the saturation characteristic. Remedy: Remedy depends on the fault value (r0949). For example:
|
| F07984 Drive: Speed controller optimization, moment of inertia | Cause: A fault has occurred while identifying the moment of inertia. Remedy: Remedy depends on the fault value (r0949). For example:
|
| F07985 Drive: Speed controller optimization (oscillation test) | Cause: A fault has occurred during the vibration test. Remedy: Remedy depends on the fault value (r0949). For example:
|
| F07986 Drive: Rotating measurement ramp-function generator | Cause: During the rotating measurements, problems with the ramp-function generator occurred. The positive and negative directions are inhibited. Remedy: Enable the direction (p1110 or p1111). |
| A07987 Drive: Rotating measurement, no encoder available | Cause: No encoder available. The rotating measurement was carried out without encoder. Remedy: Connect encoder or select p1960 = 1, 3. |
| 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). |
| F07989 Drive: Rotating measurement leakage inductance (q-axis) | Cause: An error has occurred while measuring the dynamic leakage inductance. Remedy: Remedy depends on the fault value (r0949). For example:
|
| F07990 Drive: Incorrect motor data identification | Cause: A fault has occurred during the identification routine. Remedy: Remedy depends on the fault value (r0949). For example:
|
| A07991 (N) Drive: Motor data identification activated | Cause: The motor data identification routine is activated and will be carried out at the next switch-on command. Remedy: Not necessary. The alarm automatically disappears after the routine has been successfully completed or deactivated. |
| 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. Remedy:
|
| F08000 (N, A) TB: +/-15 V power supply faulted | Cause: Terminal Board 30 detects an incorrect internal power supply voltage. Remedy:
|
| F08010 (N, A) TB: Analog-digital converter | Cause: The analog/digital converter on Terminal Board 30 has not supplied any converted data. Remedy:
|
| F08500 (A) COMM BOARD: Monitoring time configuration expired | Cause: The monitoring time for the configuration has expired. The transfer time of the send or receive configuration data has been exceeded. Remedy: Check communications link. |
| F08501 (N, A) PN/COMM BOARD: Setpoint timeout | Cause: The reception of setpoints from the COMM BOARD has been interrupted (e.g., bus connection interrupted, controller switched off). Remedy: Restore the bus connection and set the controller to RUN. If the error is repeated, check the update time set in the bus configuration. |
| F08502 (A) PN/COMM BOARD: Monitoring time sign-of-life expired | Cause: The monitoring time for the sign-of-life counter has expired. The connection to the COMM BOARD was interrupted. Remedy:
|
| A08504 (F) PN/COMM BOARD: Internal cyclic data transfer error | Cause: The cyclic actual and/or setpoint values were not transferred within the specified times. Remedy: Check the parameterizing telegram (Ti, To, Tdp, etc.). |
| F08510 (A) PN/COMM BOARD: Send configuration data invalid | Cause: COMM BOARD did not accept the send-configuration data. Remedy: Check the send configuration data. |
| A08511 (F) PN/COMM BOARD: Receive configuration data invalid | Cause: The drive unit did not accept the receive configuration data. Remedy: Check the receive configuration data. For alarm value = 1, 2: check the list of the drive objects with process data exchange (p0978). For alarm value = 17: CBE20 Shared Device: Unplug/plug A-CPU. |
| A08520 (F) PN/COMM BOARD: Non-cyclic channel error | Cause: The memory or the buffer status of the non-cyclic channel has an error. Remedy: Check communications link. |
| A08526 (F) PN/COMM BOARD: No cyclic connection | Cause: There is no cyclic connection to the control. Remedy: Establish the cyclic connection and activate the control with cyclic operation. For PROFINET, check parameters “Name of Station” and “IP of Station”. |
| A08530 (F) PN/COMM BOARD: Message channel error | Cause: The memory or the buffer status of the message channel has an error. Remedy: Check communications link. |
| A08531 (F) CBE20 POWER ON required | Cause: At least one parameter of the CBE20 was changed as a result of a project download. A POWER ON is required to activate the values. Remedy: Back up the parameters and carry out a POWER ON (switch-off/switch-on). |
| A08550 PZD Interface Hardware assignment error | Cause: The assignment of the hardware to the PZD interface has been incorrectly parameterized. Remedy: Check the parameterization and if required, correct (p8839). |
| A08555 Modbus TCP: commissioning error | Cause: A setting for the “Modbus TCP” protocol is incorrect. Remedy:
|
| A08560 IE: Syntax error in configuration file | Cause: A syntax error has been detected in the ASCII configuration file for the Industrial Ethernet interface (X127). The saved configuration file has not been loaded. Remedy: Check the interface configuration (p8900 and following), correct if necessary, and activate (p8905 = 1). Or reconfigure the station via the “Edit Ethernet node” screen form. |
| A08561 IE: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration (p8905) for the Industrial Ethernet interface (X127). Remedy: Check the required interface configuration (p8900 and following), correct if necessary, and activate (p8905). Or reconfigure the station via the “Edit Ethernet node” screen form. |
| A08562 PROFINET: Syntax error in configuration file | Cause: A syntax error has been detected in the ASCII configuration file for the onboard PROFINET interface. The saved configuration file has not been loaded. Remedy: Check the interface configuration (p8920 and following), correct if necessary, and activate (p8925 = 1). Or reconfigure the station via the “Edit Ethernet node” screen form. |
| A08563 PROFINET: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration (p8925) for the PROFINET interface. Remedy: Check the required interface configuration (p8940 and following), correct if necessary, and activate (p8945). Or reconfigure the station via the “Edit Ethernet node” screen form. |
| 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 20 (CBE20). The saved configuration file has not been loaded. Remedy: check the CBE20 configuration (p8940 and following), correct if necessary, and activate (p8945 = 2). Or reinitialize the CBE20. |
| A08565 PNCOMM BOARD: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration (p8945) for the Communication Board Ethernet 20 (CBE20). Remedy: Check the required interface configuration (p8940 and following), correct if necessary, and activate (p8945). Or reconfigure the station via the “Edit Ethernet node” screen form. |
| F08700 (A) CAN: Communications error | Cause: A CAN communications error has occurred. For fault value = 1: The error counter for send telegrams has exceeded the BUS OFF value 255. For fault value = 2: The master no longer interrogated the CAN node status longer than for its “life time”. Remedy:
|
| F08701 CAN: NMT state change | Cause: A CANopen NMT state transition from “operational” to “pre-operational” or after “stopped”. Remedy: Not necessary. Acknowledge the fault and continue operation. |
| F08702 (A) CAN: RPDO Timeout | Cause: The monitoring time of the CANopen RPDO telegram has expired because the bus connection was either interrupted or the CANopen Master was switched-off. Remedy:
|
| F08703 (A) CAN: Maximum number of drive objects exceeded | Cause: The maximum number of 8 drive objects with the “CAN” function module was exceeded. Remedy: New commissioning of maximum 8 drive objects with the “CAN” function module in the topology. For the drive objects, if required, deselect the “CAN” function module (r0108.29). |
| A08751 (N) CAN: Telegram loss | Cause: The CAN controller has lost a receive message (telegram). Remedy: Reduce the cycle times of the receive messages. |
| A08752 CAN: Error counter for error passive exceeded | Cause: The error counter for the send or receive telegrams has exceeded the value 127. Remedy:
|
| A08753 CAN: Message buffer overflow | Cause: A message buffer overflow has occurred. Remedy: Check the bus cable. Set a higher baud rate (p8622). For alarm value = 2: reduce the cycle times of the SDO receive messages. |
| A08754 CAN: Incorrect communications mode | Cause: In the “operational” mode, an attempt was made to change parameters p8700 … p8737. Remedy: Change to the “pre-operational” or “stopped” mode. |
| A08755 CAN: Obj cannot be mapped | Cause: The CANopen object is not provided for the Process Data Object (PDO) Mapping. Remedy: Use a CANopen object intended for the PDO mapping or enter 0. |
| A08756 CAN: Number of mapped bytes exceeded | Cause: The number of bytes of the mapped objects exceeds the telegram size for net data. A max. of 8 bytes is permissible. Remedy: Map fewer objects or objects with a smaller data type. |
| A08757 CAN: Set COB-ID invalid | Cause: For online operation, the appropriate COB-ID must be set invalid before mapping. Remedy: Set the COB-ID to invalid. |
| A08758 CAN: Maximum number of valid PDO exceeded | Cause: An attempt was made to exceed the maximum number of valid PDO. Remedy: Comply with the limit for the maximum number of valid RPDO or TPDO. Apply one of the specified options to delete the alarm (e.g., write to COB ID index, change NMT state, POWER ON). |
| A08759 CAN: PDO COB-ID already available | Cause: An existing PDO COB-ID was allocated. Remedy: Select another PDO COB-ID. |
| A08760 CAN: maximum size of the IF PZD exceeded | Cause: The maximum size of the IF PZD was exceeded. Remedy: Map fewer process data in PDO. Apply one of the specified options to delete the alarm. |
| A08800 PROFlenergy energy-saving mode active | Cause: The PROFIenergy energy-saving mode is active. Remedy: The alarm is automatically withdrawn when the energy-saving mode is exited. |
| A09000 Webserver security: password for “Administrator” user not set | Cause: Webserver security: password for “Administrator” user not set. Remedy: Enter the password for user “Administrator”. |
| A13000 License not adequate | Cause: For the drive unit, the options that require a license are being used but the licenses are not sufficient, or an error occurred when checking the existing licenses. Remedy: Remedy depends on the alarm value (r2124). For example:
|
| A13001 Error in license checksum | Cause: When checking the checksum of the license key, an error was detected. Remedy: Compare the license key (p9920) entered with the license key on the certificate of license. Re-enter the license key and activate (p9920, p9921). |
| F13009 Licensing Technology Extension not licensed | Cause: At least one Technology Extension that requires a license does not have a license. Remedy:
|
| F13010 Licensing function module not licensed | Cause: At least one function module which is under license does not have a license. Fault value (r0949, interpret hexadecimal): Bit x = 1: The corresponding function module does not have a license. Remedy:
|
| F13100 Know-how protection: Copy protection error | Cause: The know-how protection with copy protection for the memory card is active. An error has occurred when checking the memory card. Fault value (r0949, interpret decimal):
See also: p7765 (KHP configuration) Remedy:
|
| F13101 Know-how protection: Copy protection cannot be activated | Cause: An error occurred when attempting to activate the copy protection for the memory card. Fault value (r0949, interpret decimal):
Remedy:
|
| F13102 Know-how protection: Consistency error of the protected data | Cause: An error was identified when checking the consistency of the protected files. As a consequence, the project on the memory card cannot be run. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex: yyyy = object number, xxxx = fault cause
Remedy:
|
| F30001 Power unit: Overcurrent | Cause: The power unit has detected an overcurrent condition.
Remedy:
|
| F30002 Power unit: DC link voltage overvoltage | Cause: The power unit has detected overvoltage in the DC link.
Fault value (r0949, interpret decimal): DC link voltage at the time of trip [0.1 V]. Remedy:
|
| F30003 Power unit: DC link voltage undervoltage | Cause: The power unit has detected an undervoltage condition in the DC link.
Remedy:
|
| F30004 Power unit: Overtemperature heat sink AC inverter | Cause: The temperature of the power unit heat sink has exceeded the permissible limit value.
Fault value (r0949, interpret decimal): Temperature [0.01 °C]. Remedy:
|
| F30005 Power unit: Overload I2t | Cause: The power unit was overloaded (r0036 = 100 %).
Fault value (r0949, interpret decimal): I2t [100 % = 16384]. Remedy:
|
| F30006 Power unit: Thyristor Control Board | Cause: The Thyristor Control Board (TCB) of the Basic Line Module signals a fault.
Remedy:
|
| F30008 Power unit: Sign-of-life error cyclic data | Cause: The Control Unit has not punctually updated the cyclic setpoint telegram. The number of consecutive sign-of-life errors has exceeded the fault threshold (p7789). Remedy:
|
| A30010 (F) Power unit: Sign-of-life error cyclic data | Cause: A DRIVE-CLiQ communication error has occurred between the Control Unit and the power unit involved. The cyclic setpoint telegrams of the Control Unit were not received on time by the power unit for at least one clock cycle. Remedy:
|
| F30011 Power unit: Line phase failure in main circuit | Cause: At the power unit, the DC link voltage ripple has exceeded the permissible limit value. Possible causes:
Remedy:
|
| F30012 Power unit: Temperature sensor heat sink wire breakage | Cause: The connection to a heat sink temperature sensor in the power unit is interrupted. Remedy:
|
| F30013 Power unit: Temperature sensor heat sink short-circuit | Cause: The heat sink temperature sensor in the power unit is short-circuited. Remedy:
|
| F30015 (N, A) Power unit: Phase failure motor cable | Cause: A phase failure in the motor feeder cable was detected. The signal can also be output in the following cases:
Remedy:
|
| A30016 (N) Power unit: Load supply switched out | Cause: The DC link voltage is too low. Remedy:
|
| F30017 Power unit: Hardware current limit has responded too often | Cause: The hardware current limitation in the relevant phase has responded too often. For infeed units, the following applies:
The following applies to Motor Modules:
Remedy: For infeed units, the following applies:
The following applies to Motor Modules:
|
| F30020 Power unit: Configuration not supported | Cause: A configuration is requested that is not supported by the power unit. Remedy:
|
| F30021 Power unit: Ground fault | Cause: The power has detected a ground fault. Possible causes:
Remedy:
|
| F30022 Power unit: Monitoring U_ce | Cause: In the power unit, the monitoring of the collector-emitter voltage (U_ce) of the semiconductor has responded. Possible causes:
Remedy:
|
| F30024 Power unit: Overtemperature thermal model | Cause: The temperature difference between the heat sink and chip has exceeded the permissible limit value.
Remedy:
|
| F30025 Power unit: Chip overtemperature | Cause: The chip temperature of the semiconductor has exceeded the permissible limit value.
Remedy:
|
| F30027 Power unit: Precharging DC link time monitoring | Cause: The power unit DC link was not able to be precharged within the expected time.
Remedy: In general:
For booksize drive units, the following applies:
|
| A30030 Power unit: Internal overtemperature alarm | Cause: The temperature inside the drive converter has exceeded the permissible temperature limit.
Remedy:
|
| A30031 Power unit: Hardware current limiting in phase U | Cause: Hardware current limit for phase U responded. The pulsing in this phase is inhibited for one pulse period.
Remedy:
|
| A30032 Power unit: Hardware current limiting in phase V | Cause: Hardware current limit for phase V responded. The pulsing in this phase is inhibited for one pulse period.
Remedy:
|
| A30033 Power unit: Hardware current limiting in phase W | Cause: Hardware current limit for phase W responded. The pulsing in this phase is inhibited for one pulse period.
Remedy:
|
| A30034 Power unit: Internal overtemperature | Cause: The alarm threshold for internal overtemperature has been reached. If the temperature inside the unit continues to increase, fault F30036 may be triggered.
Remedy:
|
| F30035 Power unit: Air intake overtemperature | Cause: The air intake in the power unit has exceeded the permissible temperature limit. For air-cooled power units, the temperature limit is at 55 °C.
Remedy:
|
| F30036 Power unit: Internal overtemperature | Cause: The temperature inside the drive converter has exceeded the permissible temperature limit.
Remedy:
|
| F30037 Power unit: Rectifier overtemperature | Cause: The temperature in the rectifier of the power unit has exceeded the permissible temperature limit.
Remedy:
|
| A30038 Power unit: Capacitor fan monitoring | Cause: The capacitor fan signals a fault. Remedy:
|
| F30039 Power unit: Failure capacitor fan | Cause: The capacitor fan has failed. Remedy:
|
| F30040 Power unit: Undervolt 24 V | Cause: The undervoltage threshold of the 24 V power supply for the power unit was fallen below for longer than 3 ms. Remedy:
|
| A30041 (F) Power unit: Undervoltage 24 V alarm | Cause: For the power unit power supply, the lower threshold has been violated. 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. Remedy: For the fan involved, carry out the following:
|
| F30043 Power unit: Overvolt 24 V | Cause: For the power unit power supply, the upper threshold has been violated. Remedy:
|
| A30044 (F) Power unit: Overvoltage 24 V alarm | Cause: For the power unit power supply, the upper threshold has been violated. Remedy:
|
| F30045 Power unit: Supply undervoltage | Cause: Power supply fault in the power unit. The voltage monitor signals an undervoltage fault on the module. Remedy:
|
| A30046 (F) Power unit: Undervoltage alarm | Cause: Before the last restart, a problem occurred at the power unit power supply. The voltage monitor in the internal FPGA of the PSA signals an undervoltage fault on the module. Remedy:
|
| F30047 Cooling unit: Cooling medium flow rate too low | Cause: The flowrate of the cooling unit has fallen below the fault threshold. Remedy:
|
| A30048 Power unit: External fan faulty | Cause: The feedback signal from the external fan indicates a fault.
Remedy:
|
| A30049 Power unit: Internal fan faulty | Cause: The internal fan has failed. Remedy:
|
| F30050 Power unit: 24 V supply overvoltage | Cause: The voltage monitor signals an overvoltage fault on the module. Remedy:
|
| 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 are incorrect or not compatible with the firmware. Remedy:
|
| F30053 FPGA data faulty | Cause: The FPGA data of the power unit are faulty. For example, this can be caused when a firmware update is canceled. Remedy:
|
| 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:
|
| F30055 Power unit: Braking chopper overcurrent | Cause: An overcurrent condition has occurred in the braking chopper.
Remedy: The braking chopper is only enabled again at pulse enable after the fault has been acknowledged. |
| A30057 Power unit: Line asymmetry | Cause: Frequencies have been detected on the DC link voltage that would suggest line asymmetry or failure of a line phase. It is also possible that a motor phase has failed. Remedy:
|
| F30059 Power unit: Internal fan faulty | Cause: The internal power unit fan has failed and is possibly defective. Remedy:
|
| F30060 (A) Precharge contactor state monitoring | Cause: A feedback signal for the precharging contactor interconnected and the monitoring activated. After switching-in/switching-out the contactor, a correct feedback signal was not received within the monitoring time. Remedy:
|
| F30061 (A) Bridging contactor monitoring | Cause: A feedback signal for the bypass contactor is interconnected and the monitoring activated. After switching-in/switching-out the contactor, a correct feedback signal was not received within the monitoring time. Remedy:
|
| A30065 (F, N) Voltage measured values not plausible | Cause: The voltage measurement is not supplying any plausible values. Remedy:
|
| F30070 Cycle requested by the power unit module not supported | Cause: A cycle is requested that is not supported by the power unit. The power unit only supports specific cycles (e.g., 62.5 µs, 125 µs, etc.). Remedy:
|
| F30071 No new actual values received from the power unit | Cause: The number of actual value telegrams from the power unit module that have failed has exceeded the permissible number. Remedy:
|
| F30072 Setpoints can no longer be transferred to the power unit | Cause: More than one setpoint telegram was not able to be transferred to the power unit module. Remedy:
|
| A30073 (N) Actual value/setpoint preprocessing no longer synchronous | Cause: Communication with the power unit module is no longer in synchronism with the current control cycle. Remedy:
|
| F30074 (A) Communication error between the Control Unit and Power Module | Cause: Communications between the Control Unit (CU) and Power Module (PM) via the interface no longer possible. The CU may have been withdrawn or is incorrectly inserted. Remedy:
|
| F30075 Configuration of the power unit unsuccessful | Cause: A communication error has occurred while configuring the power unit using the Control Unit. The cause is not clear. Remedy:
|
| F30080 Power unit: Current increasing too quickly | Cause: The power unit has detected an excessive rate of rise in the overvoltage range.
Remedy:
|
| F30081 Power unit: Switching operations too frequent | Cause: The power unit has executed too many switching operations for current limitation.
Remedy:
|
| F30105 PU: Actual value sensing fault | Cause: At least one incorrect actual value channel was detected on the Power Stack Adapter (PSA). Remedy:
|
| F30314 Power unit: 24 V power supply overloaded by PM | Cause: The 24 V power supply through the Power Module (PM) is overloaded. An external 24 V power supply via X124 on the Control Unit is not connected. Remedy:
|
| A30315 (F) Power unit: 24 V power supply overloaded by PM | Cause: The 24 V power supply through the Power Module (PM) is overloaded. An external 24 V power supply via X124 on the Control Unit is not connected. Remedy:
|
| A30502 Power unit: DC link overvoltage | Cause: The power unit has detected overvoltage in the DC link on a pulse inhibit.
Remedy:
|
| F30600 SI P2: STOP A initiated | Cause: The drive-integrated “Safety Integrated” function in monitoring channel 2 has detected a fault and initiated a STOP A.
Remedy:
|
| F30611 (A) SI P2: Defect in a monitoring channel | Cause: The drive-integrated “Safety Integrated” function on processor 2 has detected a fault in the crosswise data comparison between the two monitoring channels and has initiated a STOP F. Remedy:
|
| N30620 (F, A) SI P2: Safe Torque Off active | Cause: The “Safe Torque Off” (STO) function of the basic functions has been selected in monitoring channel 2 using the input terminal and is active. Remedy: Not necessary. |
| N30621 (F, A) SI P2: Safe Stop 1 active | Cause: The “Safe Stop 1” function (SS1) was selected in monitoring channel 2 and is active. Remedy: Not necessary. |
| F30625 SI P2: Sign-of-life error in safety data | Cause: The drive-integrated “Safety Integrated” function in monitoring channel 2 has detected an error in the sign-of-life of the safety data between the two monitoring channels and initiated a STOP A.
Remedy:
|
| F30630 SI P2: Brake control error | Cause: The “Safety Integrated” function integrated in the drive on the Motor Module (MM) has detected a brake control error and initiated a STOP A.
Remedy:
|
| F30631 Brake control: External release active | Cause: For mounting purposes, the brake is supplied with voltage via terminal X4.1 and released. Remedy:
|
| A30640 (F) SI P2: Fault in the switch-off signal path of the second channel | Cause: The Motor Module has detected a communication error with the higher-level control or the TM54F to transfer the safety-relevant information or there is a communication error between Motor Modules connected in parallel. Remedy: For the higher-level control:
For TM54F:
For a parallel connection:
General remedy:
|
| F30649 SI P2: Internal software error | Cause: An internal error in the Safety Integrated software in monitoring channel 2 has occurred. This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| F30650 SI P2: Acceptance test required | Cause: The “Safety Integrated” function on monitoring channel 2 requires an acceptance test. This fault results in a STOP A that can be acknowledged. Possible reasons: Safety parameters not available, checksums not identical, safety parameter changed, etc. Remedy:
|
| F30651 SI P2: Synchronization with Control Unit unsuccessful | Cause: The “Safety Integrated” function requires synchronization of the safety time slices in both monitoring channels. This synchronization routine was unsuccessful. This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| F30652 SI P2: Illegal monitoring clock cycle | Cause: The Safety Integrated monitoring clock cycle cannot be maintained due to the communication conditions requested in the system. This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| F30655 SI P2: Align monitoring functions | Cause: An error has occurred when aligning the Safety Integrated monitoring functions. No common set of supported SI monitoring functions was able to be determined.
Remedy:
|
| F30656 SI P2: Motor Module parameter error | Cause: When accessing the Safety Integrated parameters for monitoring channel 2 in the non-volatile memory, an error has occurred. This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| F30657 SI P2: PROFIsafe telegram number invalid | Cause: The PROFIsafe telegram number set in p9811 is not valid. When PROFIsafe is enabled, a telegram number greater than zero must be entered. Remedy:
|
| F30659 SI P2: Write request for parameter rejected | Cause: The write request for one or several Safety Integrated parameters in monitoring channel 2 was rejected (e.g., attempting to enable an unsupported function). Remedy:
|
| F30664 Error while booting | Cause: An error has occurred during booting. Remedy:
|
| F30665 SI P2: System is defective | Cause: A system defect was detected before the last boot or in the actual one. The system might have been rebooted (reset). 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, which can avoid unintentional safety-relevant acknowledgment. Remedy:
|
| F30672 SI P2: Control Unit software incompatible | Cause: The existing Control Unit software does not support the safe drive-based motion monitoring function. This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| F30674 SI Motion P2: Safety function not supported by PROFIsafe telegram | Cause: The monitoring function enabled in p9301 and p9801 is not supported by the currently set PROFIsafe telegram (p9811). Remedy:
|
| F30680 SI Motion P2: Checksum error safety monitoring functions | Cause: The actual checksum calculated by the Motor Module/Hydraulic Module does not match the reference checksum saved at the last machine acceptance. Safety-relevant parameters have been changed or a fault is present. Remedy:
|
| F30681 SI Motion P1: Incorrect parameter value | Cause: The parameter cannot be parameterized with this value due to an invalid combination or setting. Remedy:
|
| F30682 SI Motion P2: Monitoring function not supported | Cause: The monitoring function enabled is not supported in this firmware version. Remedy:
|
| F30683 SI Motion P2: SOS/SLS enable missing | Cause: The safety-relevant basic function “SOS/SLS” is not enabled in p9301 although other safety-relevant monitoring functions are enabled. Remedy:
|
| F30684 SI Motion P2: Safely limited position limit values interchanged | Cause: For the function “Safely Limited Position” (SLP), a lower value is in p9334 than in p9335. Remedy:
|
| F30685 SI Motion P2: Safely Limited Speed limit value too high | Cause: The limit value for the function “Safely Limited Speed” (SLS) is greater than the speed that corresponds to an encoder limit frequency of 500 kHz. Remedy:
|
| F30688 SI Motion P2: Actual value synchronization not permissible | Cause: It is not permissible to enable actual value synchronization in certain configurations (e.g., for a 1-encoder system, with absolute reference functions, or with safe position via PROFIsafe). Remedy:
|
| F30692 SI Motion P2: Parameter value not permitted for encoderless | Cause: The parameter cannot be parameterized with this value if encoderless motion monitoring functions have been parameterized in p9306. Remedy:
|
| A30693 (F) SI P2: Safety parameter settings changed, warm restart/POWER ON required | Cause: Safety parameters have been changed; these will only take effect following a warm restart or POWER ON. Remedy:
|
| C30700 SI Motion P2: STOP A initiated | Cause: The drive is stopped via a STOP A. Possible causes include a stop request from the Control Unit or as a subsequent response to other safety messages (SAM/SBR limit exceeded, SLS exceeded, etc.). Remedy:
|
| C30701 SI Motion P2: STOP B initiated | Cause: The drive is stopped via a STOP B (braking along the OFF3 ramp). Possible causes include a stop request from the Control Unit or subsequent response to other safety messages. Remedy:
|
| C30706 SI Motion P2: SAM/SBR limit exceeded | Cause: After initiating STOP B (SS1) or STOP C (SS2), the speed has exceeded the selected tolerance. The drive is shut down by message C30700 “SI Motion MM: STOP A initiated”. Remedy:
|
| C30707 SI Motion P2: Tolerance for safe operating stop exceeded | Cause: The actual position has distanced itself further from the target position than the standstill tolerance. The drive is shut down by the message C30701 “SI Motion MM: STOP B initiated”. Remedy:
|
| C30708 SI Motion P2: STOP C initiated | Cause: The drive is stopped via a STOP C (braking along the OFF3 ramp). “Safe Operating Stop” (SOS) is activated after the parameterized time has expired. Remedy:
|
| C30709 SI Motion P2: STOP D initiated | Cause: The drive is stopped via a STOP D (braking along the path). “Safe Operating Stop” (SOS) is activated after the parameterized time has expired. Remedy:
|
| C30710 SI Motion P2: STOP E initiated | Cause: The drive is stopped via a STOP E (retraction motion). “Safe Operating Stop” (SOS) is activated after the parameterized time has expired. Remedy:
|
| C30711 SI Motion P2: Defect in a monitoring channel | Cause: When cross-comparing the two monitoring channels, the drive detected a difference between the input data or results of the monitoring functions and initiated a STOP F. One of the monitoring functions no longer reliably functions – i.e. safe operation is no longer possible. If at least one monitoring function is active, then after the parameterized timer has expired, the message C30701 “SI Motion: STOP B initiated” is output. The message is output with message value 1031 when the Sensor Module hardware is replaced. The following message values may also occur in the following cases if the cause that is explicitly mentioned does not apply:
Message value (r9749, interpret decimal):
Remedy:
|
| C30712 SI Motion P2: Defect in F-IO processing | Cause: When cross checking and comparing the two monitoring channels, the drive detected a difference between parameters or results of the F-IO processing and initiated a STOP F. One of the monitoring functions no longer reliably functions – i.e. safe operation is no longer possible. Remedy:
|
| C30714 SI Motion P2: Safely Limited Speed exceeded | Cause: The drive had moved faster than that specified by the velocity limit value (p9331). The drive is stopped as a result of the configured stop response (p9363). Remedy:
|
| C30715 SI Motion P2: Safely Limited Position exceeded | Cause: The axis has moved past a parameterized position that is monitored by the “SLP” function. Remedy:
|
| C30716 SI Motion P2: Tolerance for safe motion direction exceeded | Cause: The tolerance for the “safe motion direction” function was exceeded. The drive is stopped as a result of the configured stop response (p9366). Remedy:
|
| C30730 SI Motion P2: Reference block for dynamic safely limited speed invalid | Cause: The reference block transferred via PROFIsafe is negative. A reference block is used to generate a referred velocity limit value based on the reference quantity “Velocity limit value SLS1” (p9331[0]). The drive is stopped as a result of the configured stop response (p9363[0]). Remedy:
|
| C30770 SI Motion P2: Discrepancy error of the fail-safe inputs/outputs | Cause: The fail-safe digital inputs/digital outputs (F-DI/F-DO) show a different state longer than that parameterized in p10002 / p10102. Remedy:
|
| A30772 SI Motion P2: Test stop for fail-safe digital outputs running | Cause: The forced checking procedure (test stop) for the fail-safe digital inputs is currently in progress. Remedy: The alarm is automatically withdraw after successfully ending or canceling (when a fault condition occurs) the test stop. |
| F30773 SI Motion P2: Test stop fail-safe digital output error | Cause: A fault has occurred on processor 2 during the forced checking procedure (test stop) of the fail-safe digital output. 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. Possible causes: the STO function is selected via Safety Extended Functions. a safety message is present, that resulted in a STO. Remedy:
|
| C30797 SI Motion P2: Axis not safely referenced | Cause: The standstill position saved before switching off does not match the actual position determined at switch-on. Remedy: If safe automatic referencing is not possible the user must issue a user agreement for the new position using the softkey. This mean that this position is then designated as safety-relevant. |
| C30798 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: Not necessary. The message is automatically withdrawn when the test stop has been completed. |
| C30799 SI Motion P2: Acceptance test mode active | Cause: The acceptance test mode is active. Remedy: Not necessary. The message is withdrawn when exiting the acceptance test mode. |
| N30800 (F) Power unit: Group signal | Cause: The power unit has detected at least one fault. Remedy: Evaluate the other messages that are presently available. |
| F30801 Power unit DRIVE-CLiQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. The computing time load might be too high. Remedy:
|
| F30802 Power unit: Time slice overflow | Cause: A time slice overflow has occurred. 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. Remedy: Replace the module. |
| F30809 Power unit: Switching information not valid | Cause: For 3P gating unit, the following applies: The last switching status word in the setpoint telegram is identified by the end ID. Such an end ID was not found. Remedy:
|
| A30810 (F) Power unit: Watchdog timer | Cause: When booting it was detected that the cause of the previous reset was an SAC watchdog timer overflow. Remedy:
|
| F30820 Power unit DRIVE-CLiQ: Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. Remedy:
|
| F30835 Power unit DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. The nodes do not send and receive in synchronism. Remedy:
|
| F30836 Power unit DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. Data were not able to be sent. Remedy: Carry out a POWER ON. |
| F30837 Power unit DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLIQ component concerned. Faulty hardware cannot be excluded. Remedy:
|
| F30845 Power unit DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. Remedy: Carry out a POWER ON (switch-off/switch-on). |
| F30850 Power unit: Internal software error | Cause: An internal software error has occurred in the power unit. Remedy:
|
| F30851 Power unit DRIVE-CLiQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the power unit to the Control Unit involved. The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit. Remedy:
|
| A30853 Power unit: Sign-of-life error cyclic data | Cause: The power unit has detected that the cyclic setpoint telegrams of the Control Unit have not been updated on time. At least two sign-of-life errors have occurred within the window set in p7788. Remedy:
|
| F30860 Power unit DRIVE-CLiQ (CU): Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the power unit to the Control Unit involved. Remedy:
|
| F30875 Power unit: power supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage has failed. Remedy:
|
| F30885 CU DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the power unit to the Control Unit involved. The nodes do not send and receive in synchronism. Remedy:
|
| F30886 PU DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLIQ communication error has occurred from the power unit to the Control Unit involved. Data were not able to be sent. Remedy: Carry out a POWER ON. |
| F30887 Power unit DRIVE-CLiQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLiQ component (power unit) involved. Faulty hardware cannot be excluded. Remedy:
|
| F30895 PU DRIVE-CLiQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the power unit to the Control Unit involved. Remedy: Carry out a POWER ON. |
| F30896 Power unit DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (power unit), specified by the fault value, have changed in an incompatible fashion with respect to the properties when booted. One cause can be, e.g. that a DRIVE-CLiQ cable or DRIVE-CLiQ component has been replaced. Remedy:
|
| F30899 (N, A) Power unit: Unknown fault | Cause: A fault occurred on the power unit that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Remedy:
|
| F30903 Power unit: I2C bus error occurred | Cause: Communications error with an EEPROM or an analog/digital converter. Remedy:
|
| F30907 Power unit: FPGA configuration unsuccessful | Cause: During initialization within the power unit, an internal software error has occurred. Remedy:
|
| A30920 (F) Power unit: Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred. Remedy:
|
| A30930 (N) Power unit: Component trace has saved data | Cause: Trace data was saved in the component. Remedy: Not necessary. |
| F30950 Power unit: Internal software error | Cause: An internal software error has occurred. Remedy:
|
| A30999 (F, N) Power unit: Unknown alarm | Cause: An alarm occurred on the power unit that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. 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. 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. Remedy:
|
| F31110 (N, A) Encoder 1: Serial communications error | Cause: Serial communication protocol transfer error between the encoder and evaluation module. Remedy:
|
| F31111 (N, A) Encoder 1: Absolute encoder internal error | Cause: The absolute encoder fault word supplies fault bits that have been set. Remedy:
|
| F31112 (N, A) Encoder 1: Error bit set in the serial protocol | Cause: The encoder sends a set error bit via the serial protocol. Remedy: In the case of an EnDat encoder, F31111 may provide further details. |
| F31115 (N, A) Encoder 1: Amplitude error track A or B (A^2 + B^2) | Cause: The amplitude (root of A^2 + B^2) for encoder 1 exceeds the permissible tolerance. Remedy:
|
| F31116 (N, A) Encoder 1: Amplitude error monitoring track A + B | Cause: The amplitude of the rectified encoder signals A and B and the amplitude from the roots of A^2 + B^2 for encoder 1 are not within the tolerance bandwidth. Remedy:
|
| F31117 (N, A) Encoder 1: Inversion error signals A/B/R | Cause: For a square-wave encoder (bipolar, double ended) signals A*, B* and R* are not inverted with respect to signals A, B and 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:
|
| F31120 (N, A) Encoder 1: Power supply voltage fault | Cause: A power supply fault was detected for encoder 1. Remedy:
|
| F31121 (N, A) Encoder 1: Coarse position error | Cause: For the actual value sensing, an error was detected on the module. As a result of this error, it must be assumed that the actual value sensing supplies an incorrect coarse position. Remedy: Replace the motor with DRIVE-CLiQ or the appropriate Sensor Module. |
| F31122 Encoder 1: Internal power supply voltage faulty | Cause: Fault in internal reference voltage of ASICs for encoder 1. Remedy: Replace the motor with DRIVE-CLiQ or the appropriate Sensor Module. |
| F31123 (N, A) Encoder 1: Signal level A/B unipolar outside tolerance | Cause: The unipolar level (AP/AN or BP/BN) for encoder 1 is outside the permissible tolerance. Remedy:
|
| F31125 (N, A) Encoder 1: Amplitude error track A or B overcontrolled | Cause: The amplitude of track A or B for encoder 1 exceeds the permissible tolerance band. Remedy:
|
| F31126 (N, A) Encoder 1: Amplitude AB too high | Cause: The amplitude (root of A^2 + B^2 or |A| + |B|) for encoder 1 exceeds the permissible tolerance. Remedy:
|
| F31129 (N, A) Encoder 1: Position difference hall sensor/track C/D and A/B too large | Cause: The error for track C/D is greater than +/-15° mechanical or +/-60° electrical or the error for the Hall signals is greater than +/-60° electrical. One period of track C/D corresponds to 360 ° mechanical. One period of the Hall signal corresponds to 360 ° electrical. Remedy:
|
| F31130 (N, A) Encoder 1: Zero mark and position error from the coarse synchronization | Cause: After initializing the pole position using track C/D, Hall signals or pole position identification routine, the zero mark was detected outside the permissible range. For distance-coded encoders, the test is carried out after passing 2 zero marks. Fine synchronization was not carried out. 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. The absolute position that was read is rejected. When the zero pulse is passed, a deviation in the incremental position was detected. Remedy:
|
| F31135 Encoder 1: Fault when determining the position | Cause: The encoder supplies status information bit by bit in an internal status/fault word. Some of these bits cause this fault to be triggered. Other bits are status displays. The status/fault word is displayed in the fault value. Remedy:
|
| F31136 Encoder 1: Error when determining multiturn information | Cause: The encoder supplies status information bit by bit in an internal status/fault word. Some of these bits cause this fault to be triggered. Other bits are status displays. The status/fault word is displayed in the fault value. Remedy:
|
| F31137 Encoder 1: Internal fault when determining the position | Cause: A position determination fault has occurred in the DRIVE-CLIQ encoder. Remedy:
|
| F31138 Encoder 1: Internal error when determining multiturn information | Cause: A position determination fault has occurred in the DRIVE-CLIQ encoder. Remedy:
|
| F31142 (N, A) Encoder 1: Battery voltage fault | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The battery voltage is no longer sufficient to check the multiturn information. Remedy: Replace battery. |
| F31150 (N, A) Encoder 1: Initialization error | Cause: Encoder functionality selected in p0404 is not operating correctly. Remedy:
|
| F31151 (N, A) Encoder 1: Encoder speed for initialization AB too high | Cause: The encoder speed is too high while initializing the Sensor Module. Remedy: Reduce the speed of the encoder accordingly during initialization. If necessary, deactivate monitoring (p0437.29). |
| F31152 (N, A) Encoder 1: Maximum input frequency exceeded | Cause: The maximum input frequency of the encoder evaluation has been exceeded. Remedy:
|
| F31153 (N, A) Encoder 1: 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. |
| F31160 (N, A) Encoder 1: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
| F31161 (N, A) Encoder 1: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
| F31163 (N, A) Encoder 1: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. 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. Remedy:
|
| A31401 (F, N) Encoder 1: Alarm threshold zero mark failed | Cause: The 1.5 x parameterized zero mark distance was exceeded. Remedy:
|
| F31405 (N, A) Encoder 1: Temperature in the encoder evaluation inadmissible | Cause: The encoder evaluation for a motor with DRIVE-CLiQ has detected an inadmissible temperature. The fault threshold is 125 ° C. Remedy: Reduce the ambient temperature for the DRIVE-CLIQ connection of the motor. |
| A31407 (F, N) Encoder 1: Function limit reached | Cause: The encoder has reached one of its function limits. A service is recommended. Remedy: Perform service. Replace the encoder if necessary. |
| A31410 (F, N) Encoder 1: Serial communications | Cause: Serial communication protocol transfer error between the encoder and evaluation module. Remedy:
|
| A31411 (F, N) Encoder 1: Absolute encoder signals internal alarms | Cause: The absolute encoder fault word includes alarm bits that have been set. Remedy: Replace encoder. |
| A31412 (F, N) Encoder 1: Error bit set in the serial protocol | Cause: The encoder sends a set error bit via the serial protocol. Remedy:
|
| A31414 (F, N) Encoder 1: Amplitude error track C or D (C^2 + D^2) | Cause: The amplitude (C^2 + D^2) of track C or D of the encoder or from the Hall signals, is not within the tolerance bandwidth. Remedy:
|
| N31415 (F, A) Encoder 1: Amplitude alarm track A or B (A^2 + B^2) | Cause: The amplitude (root of A^2 + B^2) for encoder 1 exceeds the permissible tolerance. 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:
|
| A31419 (F, N) Encoder 1: Track A or B outside tolerance | Cause: The amplitude/phase/offset correction for track A or B is at the limit. Remedy:
|
| A31421 (F, N) Encoder 1: Coarse position error | Cause: For the actual value sensing, an error was detected. As a result of this error, it must be assumed that the actual value sensing supplies an incorrect coarse position. Remedy: For a standard encoder with cable, contact the manufacturer where relevant. Correct the assignment of the tracks to the position value that is serially transferred. To do this, the two tracks must be connected, inverted, at the Sensor Module (interchange A with A* and B with B*) or, for a programmable encoder, check the zero offset of the position. |
| 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. Remedy:
|
| A31429 (F, N) Encoder 1: Position difference hall sensor/track C/D and A/B too large | Cause: The error for track C/D is greater than +/-15° mechanical or +/-60° electrical or the error for the Hall signals is greater than +/-60° electrical. 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:
|
| A31432 (F, N) Encoder 1: Rotor position adaptation corrects deviation | Cause: For track A/B, pulses have been lost or too many have been counted. These pulses are presently being corrected. Remedy:
|
| A31442 (F, N) Encoder 1: Battery voltage pre-alarm | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The multiturn information can no longer be buffered if the battery voltage drops even further. Remedy: Replace battery. |
| A31443 (F, N) Encoder 1: Unipolar CD signal level outside specification | Cause: The unipolar level (CP/CN or DP/DN) for encoder 1 is outside the permissible tolerance. Remedy:
|
| A31460 (N) Encoder 1: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
| A31461 (N) Encoder 1: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
| A31462 (N) Encoder 1: Analog sensor no channel active | Cause: Channel A and B are not activated for the analog sensor. Remedy:
|
| A31463 (N) Encoder 1: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Remedy:
|
| A31470 (F, N) Encoder 1: Soiling detected | Cause: In the case of the alternative encoder system interface on the Sensor Module Cabinet 30 (SMC30), a dirty encoder is signaled via a 0 signal at terminal X521.7. Remedy:
|
| F31500 (N, A) Encoder 1: Position tracking traversing range exceeded | Cause: For a configured linear axis without modulo correction, the drive/encoder has exceeded the maximum possible traversing range. Remedy: The fault should be resolved as follows: select encoder commissioning (p0010 = 4). reset the position tracking as follows (p0411.2 = 1). deselect encoder commissioning (p0010 = 0). The fault should then be acknowledged and the absolute encoder adjusted. |
| F31501 (N, A) Encoder 1: Position tracking encoder position outside tolerance window | Cause: When switched off, the drive/encoder was moved through a distance greater than was parameterized in the tolerance window. It is possible that there is no longer any reference between the mechanical system and encoder. Remedy: Reset the position tracking as follows: select encoder commissioning (p0010 = 4). reset the position tracking as follows (p0411.2 = 1). deselect encoder commissioning (p0010 = 0). The fault should then be acknowledged and, if necessary, the absolute encoder adjusted (p2507). |
| F31502 (N, A) Encoder 1: Encoder with measuring gear without valid signals | Cause: The encoder with measuring gear no longer provides any valid signals. Remedy: It must be ensured that all of the encoders, with mounted measuring gear, provide valid actual values in operation. |
| F31503 (N, A) Encoder 1: Position tracking cannot be reset | Cause: The position tracking for the measuring gear cannot be reset. Remedy: The fault should be resolved as follows: select encoder commissioning (p0010 = 4). reset the position tracking as follows (p0411.2 = 1). deselect encoder commissioning (p0010 = 0). The fault should then be acknowledged and the absolute encoder adjusted. |
| A31700 Encoder 1: Effectivity test does not supply the expected value | Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Remedy: Replace encoder. |
| N31800 (F) Encoder 1: Group signal | Cause: The motor encoder has detected at least one fault. Remedy: Evaluate the other messages that are presently available. |
| F31801 (N, A) Encoder 1 DRIVE-CLiQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Fault cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
|
| F31802 (N, A) Encoder 1: Time slice overflow | Cause: A time slice overflow has occurred in encoder 1. Remedy:
|
| F31804 (N, A) Encoder 1: Checksum error | Cause: A checksum error has occurred when reading-out the program memory on the Sensor Module. Remedy:
|
| F31805 (N, A) Encoder 1: EEPROM checksum error | Cause: Internal parameter data is corrupted. Remedy:
|
| F31806 (N, A) Encoder 1: Initialization error | Cause: The encoder was not successfully initialized. Remedy:
|
| A31811 (F, N) Encoder 1: Encoder serial number changed | Cause: The serial number of the motor encoder of a synchronous motor has changed. Remedy:
|
| F31812 (N, A) Encoder 1: Requested cycle or RX-/TX timing not supported | Cause: A cycle requested from the Control Unit or RX/TX timing is not supported. Remedy:
|
| F31813 Encoder 1: Hardware logic unit failed | Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Remedy:
|
| F31820 (N, A) Encoder 1 DRIVE-CLiQ: Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. Remedy:
|
| F31835 (N, A) Encoder 1 DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. The nodes do not send and receive in synchronism. Remedy:
|
| F31836 (N, A) Encoder 1 DRIVE-CLiQ: Send error for DRIVE-CLIQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Data were not able to be sent. Remedy:
|
| F31837 (N, A) Encoder 1 DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. Remedy:
|
| F31845 (N, A) Encoder 1 DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. 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. Remedy:
|
| F31851 (N, A) Encoder 1 DRIVE-CLiQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 1) involved to the Control Unit. Remedy:
|
| F31860 (N, A) Encoder 1 DRIVE-CLIQ (CU): Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 1) involved to the Control Unit. Remedy:
|
| F31875 (N, A) Encoder 1: power supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage has failed. Remedy:
|
| F31885 (N, A) Encoder 1 DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 1) involved to the Control Unit. The nodes do not send and receive in synchronism. Remedy:
|
| F31886 (N, A) Encoder 1 DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 1) involved to the Control Unit. Data were not able to be sent. Remedy:
|
| F31887 (N, A) Encoder 1 DRIVE-CLIQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLiQ component involved (Sensor Module for encoder 1). Faulty hardware cannot be excluded. Remedy:
|
| F31895 (N, A) Encoder 1 DRIVE-CLiQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 1) involved to the Control Unit. Remedy:
|
| F31896 (N, A) Encoder 1 DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (Sensor Module for encoder 1), specified by the fault value, have changed in an incompatible fashion with respect to the properties when booted. One cause can be, e.g. that a DRIVE-CLiQ cable or DRIVE-CLiQ component has been replaced. 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. Remedy:
|
| A31902 (F, N) Encoder 1: SPI-BUS error occurred | Cause: Error when operating the internal SPI bus. Remedy:
|
| A31903 (F, N) Encoder 1: I2C-BUS error occurred | Cause: Error when operating the internal I2C bus. 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. Remedy:
|
| F31912 Encoder 1: Device combination is not permissible | Cause: The selected device combination is not supported. Remedy:
|
| A31915 (F, N) Encoder 1: Configuration error | Cause: The configuration for encoder 1 is incorrect. Remedy:
|
| F31916 (N, A) Encoder 1: Parameterization fault | 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. Remedy:
|
| A31920 (F, N) Encoder 1: Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred. 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. Remedy:
|
| A31940 (F, N) Encoder 1: Spindle sensor S1 voltage incorrect | Cause: The voltage of analog sensor S1 is outside the permissible range. Remedy:
|
| F31950 Encoder 1: Internal software error | Cause: An internal software error has occurred. Remedy:
|
| A31999 (F, N) Encoder 1: Unknown alarm | Cause: An alarm has occurred on the Sensor Module for encoder 1 that cannot be interpreted by the Control Unit firmware. Remedy:
|
| F32100 (N, A) Encoder 2: Zero mark distance error | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. Remedy:
|
| F32101 (N, A) Encoder 2: Zero mark failed | Cause: The 1.5 x parameterized zero mark distance was exceeded. Remedy:
|
| F32103 (N, A) Encoder 2: Amplitude error track R | Cause: The amplitude of the reference track signal (track R) does not lie within the tolerance bandwidth for encoder 2. Remedy:
|
| F32110 (N, A) Encoder 2: Serial communications error | Cause: Serial communication protocol transfer error between the encoder and evaluation module. Remedy:
|
| F32111 (N, A) Encoder 2: Absolute encoder internal fault | Cause: The absolute encoder fault word supplies fault bits that have been set. Remedy:
|
| F32115 (N, A) Encoder 2: Amplitude error track A or B (A^2 + B^2) | Cause: The amplitude (root of A^2 + B^2) for encoder 2 exceeds the permissible tolerance. Remedy:
|
| F32116 (N, A) Encoder 2: Amplitude error monitoring track A + B | Cause: The amplitude of the rectified encoder signals A and B and the amplitude from the roots of A^2 + B^2 for encoder 2 are not within the tolerance bandwidth. Remedy:
|
| F32117 (N, A) Encoder 2: Inversion error signals A/B/R | Cause: For a square-wave encoder (bipolar, double ended) signals A*, B* and R* are not inverted with respect to signals A, B and R. Remedy:
|
| F32118 (N, A) Encoder 2: 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:
|
| F32120 (N, A) Encoder 2: Power supply voltage fault | Cause: A power supply fault was detected for encoder 2. Remedy:
|
| F32121 (N, A) Encoder 2: Coarse position error | Cause: For the actual value sensing, an error was detected on the module. As a result of this error, it must be assumed that the actual value sensing supplies an incorrect coarse position. Remedy:
|
| F32122 Encoder 2: Internal power supply voltage faulty | Cause: Fault in internal reference voltage of ASICs for encoder 2. Remedy:
|
| F32123 (N, A) Encoder 2: Signal level A/B unipolar outside tolerance | Cause: The unipolar level (AP/AN or BP/BN) for encoder 2 is outside the permissible tolerance. Remedy:
|
| F32125 (N, A) Encoder 2: Amplitude error track A or B overcontrolled | Cause: The amplitude of track A or B for encoder 2 exceeds the permissible tolerance band. Remedy:
|
| F32126 (N, A) Encoder 2: Amplitude AB too high | Cause: The amplitude (root of A^2 + B^2 or |A| + |B|) for encoder 2 exceeds the permissible tolerance. Remedy:
|
| F32129 (N, A) Encoder 2: Position difference hall sensor/track C/D and A/B too large | Cause: The error for track C/D is greater than +/-15° mechanical or +/-60° electrical or the error for the Hall signals is greater than +/-60° electrical. Remedy:
|
| F32130 (N, A) Encoder 2: Zero mark and position error from the coarse synchronization | Cause: After initializing the pole position using track C/D, Hall signals or pole position identification routine, the zero mark was detected outside the permissible range. Remedy:
|
| F32131 (N, A) Encoder 2: Deviation position incremental/absolute too large | Cause: Absolute encoder: When cyclically reading the absolute position, an excessively high difference to the incremental position was detected. Incremental encoder: When the zero pulse is passed, a deviation in the incremental position was detected. Remedy:
|
| F32135 Encoder 2: Fault when determining the position | Cause: The encoder supplies status information bit by bit in an internal status/fault word. Some of these bits cause this fault to be triggered. Remedy:
|
| F32136 Encoder 2: Error when determining multiturn information | Cause: The encoder supplies status information bit by bit in an internal status/fault word. Some of these bits cause this fault to be triggered. Remedy:
|
| F32137 Encoder 2: Internal fault when determining the position | Cause: A position determination fault has occurred in the DRIVE-CLiQ encoder. Remedy:
|
| F32138 Encoder 2: Internal error when determining multiturn information | Cause: A position determination fault has occurred in the DRIVE-CLiQ encoder. Remedy:
|
| F32142 (N, A) Encoder 2: Battery voltage fault | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The battery voltage is no longer sufficient to check the multiturn information. Remedy:
|
| F32150 (N, A) Encoder 2: Initialization error | Cause: Encoder functionality selected in p0404 is not operating correctly. Remedy:
|
| F32151 (N, A) Encoder 2: Encoder speed for initialization AB too high | Cause: The encoder speed is too high while initializing the Sensor Module. Remedy:
|
| F32152 (N, A) Encoder 2: Maximum input frequency exceeded | Cause: The maximum input frequency of the encoder evaluation has been exceeded. 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:
|
| F32160 (N, A) Encoder 2: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
| F32161 (N, A) Encoder 2: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
| F32163 (N, A) Encoder 2: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Remedy:
|
| A32400 (F, N) Encoder 2: Alarm threshold zero mark distance error | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. Remedy:
|
| A32401 (F, N) Encoder 2: Alarm threshold zero mark failed | Cause: The 1.5 x parameterized zero mark distance was exceeded. Remedy:
|
| F32405 (N, A) Encoder 2: Temperature in the encoder evaluation inadmissible | Cause: The encoder evaluation for a motor with DRIVE-CLiQ has detected an inadmissible temperature. The fault threshold is 125 ° C. Remedy:
|
| A32407 (F, N) Encoder 2: Function limit reached | Cause: The encoder has reached one of its function limits. A service is recommended. Remedy:
|
| A32410 (F, N) Encoder 2: Serial communications | Cause: Serial communication protocol transfer error between the encoder and evaluation module. Remedy:
|
| A32411 (F, N) Encoder 2: Absolute encoder signals internal alarms | Cause: The absolute encoder fault word includes alarm bits that have been set. Remedy:
|
| A32412 (F, N) Encoder 2: Error bit set in the serial protocol | Cause: The encoder sends a set error bit via the serial protocol. Remedy:
|
| A32414 (F, N) Encoder 2: Amplitude error track C or D (C^2 + D^2) | Cause: The amplitude (C^2 + D^2) of track C or D of the encoder or from the Hall signals, is not within the tolerance bandwidth. Remedy:
|
| N32415 (F, A) Encoder 2: Amplitude alarm track A or B (A^2 + B^2) | Cause: The amplitude (root of A^2 + B^2) for encoder 2 exceeds the permissible tolerance. Remedy:
|
| A32418 (F, N) Encoder 2: 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:
|
| A32419 (F, N) Encoder 2: Track A or B outside tolerance | Cause: The amplitude/phase/offset correction for track A or B is at the limit. Remedy:
|
| A32421 (F, N) Encoder 2: Coarse position error | Cause: For the actual value sensing, an error was detected. As a result of this error, it must be assumed that the actual value sensing supplies an incorrect coarse position. Remedy:
|
| A32422 (F, N) Encoder 2: Pulses per revolution square-wave encoder outside tolerance bandwidth | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. Remedy:
|
| A32429 (F, N) Encoder 2: Position difference hall sensor/track C/D and A/B too large | Cause: The error for track C/D is greater than +/-15° mechanical or +/-60° electrical or the error for the Hall signals is greater than +/-60° electrical. Remedy:
|
| A32431 (F, N) Encoder 2: Deviation position incremental/absolute too large | Cause: When the zero pulse is passed, a deviation in the incremental position was detected. Remedy:
|
| A32432 (F, N) Encoder 2: Rotor position adaptation corrects deviation | Cause: For track A/B, pulses have been lost or too many have been counted. These pulses are presently being corrected. 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:
|
| A32443 (F, N) Encoder 2: Unipolar CD signal level outside specification | Cause: The unipolar level (CP/CN or DP/DN) for encoder 2 is outside the permissible tolerance. Remedy:
|
| A32460 (N) Encoder 2: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
| A32461 (N) Encoder 2: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
| A32462 (N) Encoder 2: Analog sensor no channel active | Cause: Channel A and B are not activated for the analog sensor. Remedy:
|
| A32463 (N) Encoder 2: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Remedy:
|
| A32470 (F, N) Encoder 2: Soiling detected | Cause: In the case of the alternative encoder system interface on the Sensor Module Cabinet 30 (SMC30), a dirty encoder is signaled via a 0 signal at terminal X521.7. Remedy:
|
| F32500 (N, A) Encoder 2: Position tracking traversing range exceeded | Cause: For a configured linear axis without modulo correction, the drive/encoder has exceeded the maximum possible traversing range. Remedy:
|
| F32501 (N, A) Encoder 2: Position tracking encoder position outside tolerance window | Cause: When switched off, the drive/encoder was moved through a distance greater than was parameterized in the tolerance window. Remedy:
|
| F32502 (N, A) Encoder 2: Encoder with measuring gear without valid signals | Cause: The encoder with measuring gear no longer provides any valid signals. Remedy:
|
| F32503 (N, A) Encoder 2: Position tracking cannot be reset | Cause: The position tracking for the measuring gear cannot be reset. Remedy:
|
| A32700 Encoder 2: Effectivity test does not supply the expected value | Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Remedy:
|
| N32800 (F) Encoder 2: Group signal | Cause: The motor encoder has detected at least one fault. Remedy:
|
| F32801 (N, A) Encoder 2 DRIVE-CLIQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Remedy:
|
| F32802 (N, A) Encoder 2: Time slice overflow | Cause: A time slice overflow has occurred in encoder 2. Remedy:
|
| F32804 (N, A) Encoder 2: Checksum error | Cause: A checksum error has occurred when reading-out the program memory on the Sensor Module. Remedy:
|
| F32805 (N, A) Encoder 2: EEPROM checksum error | Cause: Internal parameter data is corrupted. Remedy:
|
| F32806 (N, A) Encoder 2: Initialization error | Cause: The encoder was not successfully initialized. Remedy:
|
| A32811 (F, N) Encoder 2: Encoder serial number changed | Cause: The encoder serial number has changed. The change is only checked for encoders with serial number (e.g. EnDat encoders). Remedy:
|
| F32812 (N, A) Encoder 2: Requested cycle or RX-/TX timing not supported | Cause: A cycle requested from the Control Unit or RX/TX timing is not supported. Fault value (r0949, interpret decimal):
Remedy: Carry out a POWER ON (switch-off/switch-on) for all components. |
| F32813 Encoder 2: Hardware logic unit failed | Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Fault value (r0949, interpret binary):
Remedy: Replace encoder. |
| F32820 (N, A) Encoder 2 DRIVE-CLIQ: Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. Fault cause:
Remedy:
|
| F32835 (N, A) Encoder 2 DRIVE-CLIQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. The nodes do not send and receive in synchronism. Fault cause:
Remedy:
|
| F32836 (N, A) Encoder 2 DRIVE-CLIQ: Send error for DRIVE-CLIQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Data were not able to be sent. Fault cause:
Remedy: Carry out a POWER ON. |
| F32837 (N, A) Encoder 2 DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLIQ component concerned. Faulty hardware cannot be excluded. Fault cause:
Remedy:
|
| F32845 (N, A) Encoder 2 DRIVE-CLIQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Fault cause:
Remedy:
|
| 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, interpret decimal):
Remedy:
|
| F32851 (N, A) Encoder 2 DRIVE-CLIQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit. Fault cause:
Remedy:
|
| F32860 (N, A) Encoder 2 DRIVE-CLIQ (CU): Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. Fault cause:
Remedy:
|
| F32875 (N, A) Encoder 2: power supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLIQ component involved to the Control Unit signals that the supply voltage has failed. Fault cause:
Remedy:
|
| F32885 (N, A) Encoder 2 DRIVE-CLIQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. The nodes do not send and receive in synchronism. Fault cause:
Remedy:
|
| F32886 (N, A) Encoder 2 DRIVE-CLIQ (CU): Error when sending DRIVE-CLIQ data | Cause: A DRIVE-CLIQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. Data were not able to be sent. Fault cause:
Remedy: Carry out a POWER ON. |
| F32887 (N, A) Encoder 2 DRIVE-CLIQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLIQ component involved (Sensor Module for encoder 2). Faulty hardware cannot be excluded. Fault cause:
Remedy:
|
| F32895 (N, A) Encoder 2 DRIVE-CLIQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLIQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. Fault cause:
Remedy:
|
| F32896 (N, A) Encoder 2 DRIVE-CLIQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (Sensor Module for encoder 2), specified by the fault value, have changed in an incompatible fashion with respect to the properties when booted. One cause can be, e.g. that a DRIVE-CLiQ cable or DRIVE-CLiQ component has been replaced. Fault value (r0949, interpret decimal): Component number. 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. 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. Remedy:
|
| A32902 (F, N) Encoder 2: SPI-BUS error occurred | Cause: Error when operating the internal SPI bus. Remedy:
|
| F32905 (N, A) Encoder 2: Parameterization error | Cause: A parameter of encoder 2 was detected as being incorrect. It is possible that the parameterized encoder type does not match the connected encoder. The parameter involved can be determined as follows: – determine the parameter number using the fault value (r0949). – determine the parameter index (p0187). Fault value (r0949, interpret decimal):
Remedy:
|
| F32912 Encoder 2: Device combination is not permissible | Cause: The selected device combination is not supported. Fault value (r0949, interpret decimal):
Remedy:
|
| A32915 (F, N) Encoder 2: Configuration error | Cause: The configuration for encoder 2 is incorrect. Alarm value (r2124, interpret decimal):
Remedy:
|
| F32916 (N, A) Encoder 2: Parameterization fault | Cause: A parameter of encoder 2 was detected as being incorrect. It is possible that the parameterized encoder type does not match the connected encoder. The parameter involved can be determined as follows: – determine the parameter number using the fault value (r0949). – determine the parameter index (p0187). Fault value (r0949, interpret decimal): Parameter number. Remedy:
|
| A32920 (F, N) Encoder 2: Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred. Fault cause:
Remedy:
|
| A32930 (N) Encoder 2: Data logger has saved data | Cause: For the activated function “Data logger” (p0437.0 = 1) a fault has occurred with the Sensor Module. This alarm indicates that the diagnostics data corresponding to the fault was saved on the memory card. Remedy: Not necessary. The alarm disappears automatically. The data logger is ready to record the next fault case. |
| A32940 (F, N) Encoder 2: Spindle sensor S1 voltage incorrect | Cause: The voltage of analog sensor S1 is outside the permissible range. Remedy:
|
| F32950 Encoder 2: Internal software error | Cause: An internal software error has occurred. Remedy:
|
| A32999 (F, N) Encoder 2: Unknown alarm | Cause: A alarm has occurred on the Sensor Module for encoder 2 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:
|
| F33100 (N, A) Encoder 3: Zero mark distance error | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. For distance-coded encoders, the zero mark distance is determined from zero marks detected pairs. This means that if a zero mark is missing, depending on the pair generation, this cannot result in a fault and also has no effect in the system. Remedy:
|
| F33101 (N, A) Encoder 3: Zero mark failed | Cause: The 1.5 x parameterized zero mark distance was exceeded. The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder). Remedy:
|
| F33103 (N, A) Encoder 3: Amplitude error track R | Cause: The amplitude of the reference track signal (track R) does not lie within the tolerance bandwidth for encoder 3. The fault can be initiated when the unipolar voltage level is exceeded (RP/RN) or if the differential amplitude is undershot. Remedy:
|
| F33110 (N, A) Encoder 3: Serial communications error | Cause: Serial communication protocol transfer error between the encoder and evaluation module. Remedy:
|
| F33111 (N, A) Encoder 3: Absolute encoder internal fault | Cause: The absolute encoder fault word supplies fault bits that have been set. For p0404.8 = 0, the following applies: Fault value for internal Siemens troubleshooting. For p0404.8 = 1, the following applies: Fault value (r0949, interpret binary): yyyyxxxx hex: yyyy = supplementary information, xxxx = fault cause yyyy = 0:
Remedy: For yyyy = 0:
For yyyy = 1: Encoder is defective. Replace encoder. |
| F33112 (N, A) Encoder 3: 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: For fault value, bit 0 = 1: In the case of an EnDat encoder, F31111 may provide further details. |
| F33115 (N, A) Encoder 3: Amplitude error track A or B (A^2 + B^2) | Cause: The amplitude (root of A^2 + B^2) for encoder 3 exceeds the permissible tolerance. The nominal signal level must lie in the range 375 mV to 600 mV. The response thresholds are < 170 mV and > 750 mV. Remedy:
|
| F33116 (N, A) Encoder 3: Amplitude error monitoring track A + B | Cause: The amplitude of the rectified encoder signals A and B and the amplitude from the roots of A^2 + B^2 for encoder 3 are not within the tolerance bandwidth. The nominal signal level must lie in the range 375 mV to 600 mV. The response thresholds are < 130 mV and > 955 mV. Remedy:
|
| F33117 (N, A) Encoder 3: Inversion error signals A/B/R | Cause: For a square-wave encoder (bipolar, double ended) signals A*, B* and R* are not inverted with respect to signals A, B and R. Fault value (r0949, interpret binary):
Remedy: – check the encoder/cable. – Does the encoder supply signals and the associated inverted signals? Note: For SMC30, check the setting of p0405. For a square-wave encoder without track R, jumpers must be set for the connection at X520 or X23. |
| F33118 (N, A) Encoder 3: 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:
|
| F33120 (N, A) Encoder 3: Power supply voltage fault | Cause: A power supply fault was detected for encoder 3. Fault value (r0949, interpret binary):
Remedy:
|
| F33121 (N, A) Encoder 3: Coarse position error | Cause: For the actual value sensing, an error was detected on the module. It must be assumed that the actual value sensing supplies an incorrect coarse position. Remedy: Replace the motor with DRIVE-CLiQ or the appropriate Sensor Module. |
| F33122 Encoder 3: Internal power supply voltage faulty | Cause: Fault in internal reference voltage of ASICs for encoder 3. Fault value (r0949, interpret decimal):
Remedy: Replace the motor with DRIVE-CLiQ or the appropriate Sensor Module. |
| F33123 (N, A) Encoder 3: Signal level A/B unipolar outside tolerance | Cause: The unipolar level (AP/AN or BP/BN) for encoder 3 is outside the permissible tolerance. The unipolar nominal signal level must lie in the range 2500 mV +/- 500 mV. The response thresholds are < 1700 mV and > 3300 mV. Remedy:
|
| F33125 (N, A) Encoder 3: Amplitude error track A or B overcontrolled | Cause: The amplitude of track A or B for encoder 3 exceeds the permissible tolerance band. This fault also occurs if the analog/digital converter is overcontrolled. The nominal signal level of the encoder must lie in the range 375 mV to 600 mV. The response threshold is > 750 mV. Remedy:
|
| F33126 (N, A) Encoder 3: Amplitude AB too high | Cause: The amplitude (root of A^2 + B^2 or |A| + |B|) for encoder 3 exceeds the permissible tolerance. The nominal signal level of the encoder must lie in the range 375 mV to 600 mV. The response threshold for (|A| + |B|) is > 1120 mV or the root of (A^2 + B^2) > 955 mV. Remedy:
|
| F33129 (N, A) Encoder 3: Position difference hall sensor/track C/D and A/B too large | Cause: The error for track C/D is greater than +/-15° mechanical or +/-60° electrical or the error for the Hall signals is greater than +/-60° electrical. Remedy:
|
| F33130 (N, A) Encoder 3: Zero mark and position error from the coarse synchronization | Cause: After initializing the pole position using track C/D, Hall signals or pole position identification routine, the zero mark was detected outside the permissible range. Remedy:
|
| F33131 (N, A) Encoder 3: Deviation position incremental/absolute too large | Cause: When cyclically reading the absolute position, an excessively high difference to the incremental position was detected. When the zero pulse is passed, a deviation in the incremental position was detected. Remedy:
|
| F33135 Encoder 3: Fault when determining the position | Cause: The encoder supplies status information bit by bit in an internal status/fault word. Some of these bits cause this fault to be triggered. Fault value (r0949, interpret binary) contains bits for various statuses like safety, lighting, signal amplitude, overvoltage, temperature, etc. Remedy: – determine the detailed cause of the fault using the fault value. – replace the encoder if necessary. Note: An EnDat 2.2 encoder may only be removed and inserted in the “Park” state. A POWER ON is necessary to acknowledge the fault if removed otherwise. |
| F33136 Encoder 3: Error when determining multiturn information | Cause: The encoder supplies status information bit by bit in an internal status/fault word. Some of these bits cause this fault to be triggered. The status/fault word is displayed in the fault value, indicating issues with safety status, lighting, signal amplitude, position value, voltage, current, etc. Remedy: – determine the detailed cause of the fault using the fault value. – replace the encoder if necessary. |
| F33137 Encoder 3: Internal fault when determining the position | Cause: A position determination fault has occurred in the DRIVE-CLiQ encoder. Fault value (r0949, interpret binary) provides a bit-coded fault cause, including signal monitoring, safety status, LED monitoring, multiturn fault, and temperature issues. Remedy: – determine the detailed cause of the fault using the fault value. – if required, replace the DRIVE-CLiQ encoder. |
| F33138 Encoder 3: Internal error when determining multiturn information | Cause: A position determination fault has occurred in the DRIVE-CLiQ encoder. Fault value (r0949, interpret binary) provides a bit-coded fault cause similar to F33137. Remedy: – determine the detailed cause of the fault using the fault value. – if required, replace the DRIVE-CLiQ encoder. |
| F33142 (N, A) Encoder 3: Battery voltage fault | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The battery voltage is no longer sufficient. Remedy: Replace battery. |
| F33150 (N, A) Encoder 3: Initialization error | Cause: Encoder functionality selected in p0404 is not operating correctly. Fault value (r0949, interpret hexadecimal): Encoder malfunction. The bit assignment corresponds to that of p0404. Remedy: – check that p0404 is correctly set. – check the encoder type used (incremental/absolute) and for SMCxx, the encoder cable. – if relevant, note additional fault messages that describe the fault in detail. |
| F33151 (N, A) Encoder 3: Encoder speed for initialization AB too high | Cause: The encoder speed is too high while initializing the Sensor Module. Remedy: Reduce the speed of the encoder accordingly during initialization. If necessary, deactivate monitoring (p0437.29). |
| F33152 (N, A) Encoder 3: Maximum input frequency exceeded | Cause: The maximum input frequency of the encoder evaluation has been exceeded. Remedy: – reduce the speed. – Use an encoder with a lower pulse number (p0408). |
| F33153 (N, A) Encoder 3: 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. |
| F33160 (N, A) Encoder 3: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Fault value (r0949, interpret decimal):
Remedy:
|
| F33161 (N, A) Encoder 3: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Fault value (r0949, interpret decimal):
Remedy:
|
| F33163 (N, A) Encoder 3: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Fault value (r0949, interpret decimal):
Remedy:
|
| A33400 (F, N) Encoder 3: Alarm threshold zero mark distance error | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. Remedy:
|
| A33401 (F, N) Encoder 3: Alarm threshold zero mark failed | Cause: The 1.5 x parameterized zero mark distance was exceeded. The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder). Remedy:
|
| F33405 (N, A) Encoder 3: Temperature in the encoder evaluation inadmissible | Cause: The encoder evaluation for a motor with DRIVE-CLiQ has detected an inadmissible temperature. The fault threshold is 125 ° C. Remedy: Reduce the ambient temperature for the DRIVE-CLiQ connection of the motor. |
| A33407 (F, N) Encoder 3: Function limit reached | Cause: The encoder has reached one of its function limits. A service is recommended. Alarm value (r2124, interpret decimal):
Remedy: Perform service. Replace the encoder if necessary. |
| A33410 (F, N) Encoder 3: Serial communications | Cause: Serial communication protocol transfer error between the encoder and evaluation module. This can be due to an incorrect quiescent level on the data line, CRC error, encoder acknowledgment error, internal driver error, timeout, or other communication issues. Remedy:
|
| A33411 (F, N) Encoder 3: Absolute encoder signals internal alarms | Cause: The absolute encoder fault word includes alarm bits that have been set. These can indicate issues like exceeded frequency or temperature, low battery, or errors in the signal amplitude or internal data. Remedy: Replace encoder. |
| A33412 (F, N) Encoder 3: Error bit set in the serial protocol | Cause: The encoder sends a set error bit via the serial protocol. Remedy:
|
| A33414 (F, N) Encoder 3: Amplitude error track C or D (C^2 + D^2) | Cause: The amplitude (C^2 + D^2) of track C or D of the encoder or from the Hall signals, is not within the tolerance bandwidth. Remedy:
|
| N33415 (F, A) Encoder 3: Amplitude alarm track A or B (A^2 + B^2) | Cause: The amplitude (root of A^2 + B^2) for encoder 3 exceeds the permissible tolerance. Remedy:
|
| A33418 (F, N) Encoder 3: 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:
|
| A33419 (F, N) Encoder 3: Track A or B outside tolerance | Cause: The amplitude/phase/offset correction for track A or B is at the limit. Remedy:
|
| A33421 (F, N) Encoder 3: Coarse position error | Cause: For the actual value sensing, an error was detected. As a result, it must be assumed that the actual value sensing supplies an incorrect coarse position. Remedy: For a standard encoder with cable, contact the manufacturer where relevant. Correct the assignment of the tracks to the position value that is serially transferred. |
| A33422 (F, N) Encoder 3: Pulses per revolution square-wave encoder outside tolerance bandwidth | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. Remedy:
|
| A33429 (F, N) Encoder 3: Position difference hall sensor/track C/D and A/B too large | Cause: The error for track C/D or the Hall signals is greater than the permissible mechanical or electrical angle. Remedy:
|
| A33431 (F, N) Encoder 3: Deviation position incremental/absolute too large | Cause: When the zero pulse is passed, a deviation in the incremental position was detected. Remedy:
|
| A33432 (F, N) Encoder 3: Rotor position adaptation corrects deviation | Cause: For track A/B, pulses have been lost or too many have been counted. These pulses are presently being corrected. Remedy:
|
| A33442 (F, N) Encoder 3: Battery voltage pre-alarm | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The multiturn information can no longer be buffered if the battery voltage drops even further. Remedy: Replace battery. |
| A33443 (F, N) Encoder 3: Unipolar CD signal level outside specification | Cause: The unipolar level (CP/CN or DP/DN) for encoder 3 is outside the permissible tolerance. Remedy:
|
| A33460 (N) Encoder 3: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
| A33461 (N) Encoder 3: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
| A33462 (N) Encoder 3: Analog sensor no channel active | Cause: Channel A and B are not activated for the analog sensor. Remedy: – activate channel A and/or channel B (p4670). – check the encoder configuration (p0404.17). |
| A33463 (N) Encoder 3: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Remedy:
|
| A33470 (F, N) Encoder 3: Soiling detected | Cause: In the case of the alternative encoder system interface on the Sensor Module Cabinet 30 (SMC30), a dirty encoder is signaled. Remedy: – check the plug connections. – replace the encoder or encoder cable. |
| F33500 (N, A) Encoder 3: Position tracking traversing range exceeded | Cause: For a configured linear axis without modulo correction, the drive/encoder has exceeded the maximum possible traversing range. Remedy: The fault should be resolved as follows:
|
| F33501 (N, A) Encoder 3: Position tracking encoder position outside tolerance window | Cause: When switched off, the drive/encoder was moved through a distance greater than was parameterized in the tolerance window. Remedy: Reset the position tracking as follows:
|
| F33502 (N, A) Encoder 3: Encoder with measuring gear without valid signals | Cause: The encoder with measuring gear no longer provides any valid signals. Remedy: It must be ensured that all of the encoders, with mounted measuring gear, provide valid actual values in operation. |
| F33503 (N, A) Encoder 3: Position tracking cannot be reset | Cause: The position tracking for the measuring gear cannot be reset. Remedy: The fault should be resolved as follows:
|
| A33700 Encoder 3: Effectivity test does not supply the expected value | Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Effectivity test x unsuccessful. Remedy: Replace encoder. |
| N33800 (F) Encoder 3: Group signal | Cause: The motor encoder has detected at least one fault. Remedy: Evaluate the other messages that are presently available. |
| F33801 (N, A) Encoder 3 DRIVE-CLiQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. The sign-of-life bit in the receive telegram is not set. Remedy:
|
| F33802 (N, A) Encoder 3: Time slice overflow | Cause: A time slice overflow has occurred in encoder 3. This can be a fast, average, or slow time slice overflow, or a timeout when waiting for SYNO. Remedy: Increase the current controller sampling time. |
| F33804 (N, A) Encoder 3: Checksum error | Cause: A checksum error has occurred when reading-out the program memory on the Sensor Module. Remedy:
|
| F33805 (N, A) Encoder 3: EEPROM checksum error | Cause: Internal parameter data is corrupted. Remedy: Replace the module. |
| F33806 (N, A) Encoder 3: Initialization error | Cause: The encoder was not successfully initialized. This can be due to failed mid-voltage matching, internal errors, or inconsistent EnDat 2.2 measuring unit data. Remedy: Acknowledge fault. If the fault cannot be acknowledged, check encoder power supply, cables, and settings in p0404. For EnDat 2.2 errors, check the cable and replace the measuring unit if necessary. |
| A33811 (F, N) Encoder 3: Encoder serial number changed | Cause: The encoder serial number has changed. The change is only checked for encoders with serial number (e.g. EnDat encoders). Remedy: Proceed as follows to hide serial number monitoring: set serial numbers in p0441-p0445. Mechanically adjust the encoder. Accept the new serial number with p0440 = 1. |
| F33812 (N, A) Encoder 3: Requested cycle or RX-/TX timing not supported | Cause: A cycle requested from the Control Unit or RX/TX timing is not supported. Remedy: Carry out a POWER ON (switch-off/switch-on) for all components. |
| F33813 Encoder 3: Hardware logic unit failed | Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Remedy: Replace encoder. |
| F33820 (N, A) Encoder 3 DRIVE-CLiQ: Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. Remedy:
|
| F33835 (N, A) Encoder 3 DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. The nodes do not send and receive in synchronism. Remedy:
|
| F33836 (N, A) Encoder 3 DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Data were not able to be sent. Remedy: Carry out a POWER ON. |
| F33837 (N, A) Encoder 3 DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. Remedy:
|
| F33845 (N, A) Encoder 3 DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Synchronization error during alternating cyclic data transfer. Remedy:
|
| F33850 (N, A) Encoder 3: Encoder evaluation internal software error | Cause: An internal software error has occurred in the Sensor Module of encoder 3. This can be due to a blocked time slice, incorrect checksum, or various data and initialization errors. Remedy:
|
| F33851 (N, A) Encoder 3 DRIVE-CLiQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit. The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit. Remedy:
|
| F33860 (N, A) Encoder 3 DRIVE-CLiQ (CU): Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit. This can be due to checksum errors, incorrect telegram length, or other communication issues. Remedy:
|
| F33875 (N, A) Encoder 3: power supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage has failed. Remedy:
|
| F33885 (N, A) Encoder 3 DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit. The nodes do not send and receive in synchronism. Remedy:
|
| F33886 (N, A) Encoder 3 DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit. Data were not able to be sent. Remedy: Carry out a POWER ON. |
| F33887 (N, A) Encoder 3 DRIVE-CLiQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLiQ component involved (Sensor Module for encoder 3). Faulty hardware cannot be excluded. Remedy:
|
| F33895 (N, A) Encoder 3 DRIVE-CLiQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit. Synchronization error during alternating cyclic data transfer. Remedy:
|
| F33896 (N, A) Encoder 3 DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component have changed in an incompatible fashion with respect to the properties when booted. Remedy: – carry out a POWER ON. – when a component is replaced, use the same component type and firmware version. – when a cable is replaced, use a cable of the same or similar length. |
| F33899 (N, A) Encoder 3: Unknown fault | Cause: A fault occurred on the Sensor Module for encoder 3 that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent. Remedy:
|
| A33902 (F, N) Encoder 3: SPI-BUS error occurred | Cause: Error when operating the internal SPI bus. Remedy:
|
| A33903 (F, N) Encoder 3: I2C-BUS error occurred | Cause: Error when operating the internal I2C bus. Alarm value (r2124, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: – replace the Sensor Module. – if required, upgrade the firmware in the Sensor Module. – contact Technical Support. |
| F33905 (N, A) Encoder 3: Parameterization error | Cause: A parameter of encoder 3 was detected as being incorrect. It is possible that the parameterized encoder type does not match the connected encoder. The parameter involved can be determined as follows: – determine the parameter number using the fault value (r0949). – determine the parameter index (p0187). Remedy: – check whether the connected encoder type matches the encoder that has been parameterized. – correct the parameter specified by the fault value (r0949) and p0187. – re parameter number = 314: – check the pole pair number and measuring gear ratio. The quotient of the “pole pair number” divided by the “measuring gear ratio” must be less than or equal to 1000 ((r0313* p0433) / p0432 <= 1000). |
| F33912 Encoder 3: Device combination is not permissible | Cause: The selected device combination is not supported. Fault value (r0949, interpret decimal): 1003, 1005, 1006, 2001, 2002. Remedy: For fault value = 1003, 1005, 1006: – Use a measuring unit that is permissible. For fault value = 2001: – set a permissible cycle combination (if required, use standard settings). For fault value = 2002: – Use a measuring unit with a lower resolution (p0422). |
| A33915 (F, N) Encoder 3: Configuration error | Cause: The configuration for encoder 3 is incorrect. Alarm value (r2124, interpret decimal): 1, 419. Remedy: For alarm value = 1: No re-parameterization between fault/alarm. For alarm value = 419: Reduce the fine resolution (p0419) or deactivate the monitoring (p0437.25), if the complete multiturn range is not required. |
| F33916 (N, A) Encoder 3: Parameterization fault | Cause: A parameter of encoder 3 was detected as being incorrect. It is possible that the parameterized encoder type does not match the connected encoder. The parameter involved can be determined as follows: – determine the parameter number using the fault value (r0949). – determine the parameter index (p0187). Remedy: – check whether the connected encoder type matches the encoder that has been parameterized. – correct the parameter specified by the fault value (r0949) and p0187. |
| A33920 (F, N) Encoder 3: Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred. Fault cause: 1 (= 01 hex): Wire breakage or sensor not connected. 2 (= 02 hex): Measured resistance too low. Remedy: – check that the encoder cable is the correct type and is correctly connected. – check the temperature sensor selection in p0600 to p0603. – replace the Sensor Module (hardware defect or incorrect calibration data). |
| A33930 (N) Encoder 3: Data logger has saved data | Cause: For the activated function “Data logger” (p0437.0 = 1) a fault has occurred with the Sensor Module. This alarm indicates that the diagnostics data corresponding to the fault was saved on the memory card. Remedy: Not necessary. The alarm disappears automatically. The data logger is ready to record the next fault case. |
| A33940 (F, N) Encoder 3: Spindle sensor S1 voltage incorrect | Cause: The voltage of analog sensor S1 is outside the permissible range. Alarm value (r2124, interpret decimal): Signal level from sensor S1. Remedy: – check the clamped tool. – check the tolerance and if required, adapt (p5040). – check the thresholds and if required, adapt (p5041). – check analog sensor S1 and connections. |
| F33950 Encoder 3: Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Information about the fault source. Only for internal Siemens troubleshooting. Remedy: – if necessary, upgrade the firmware in the Sensor Module to a later version. – contact Technical Support. |
| A33999 (F, N) Encoder 3: Unknown alarm | Cause: An alarm has occurred on the Sensor Module for encoder 3 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: – replace the firmware on the Sensor Module by an older firmware version (r0148). – upgrade the firmware on the Control Unit (r0018). |
| F34207 (N, A) VSM: Temperature fault threshold exceeded | Cause: The temperature (r3666) measured using the Voltage Sensing Module (VSM) has exceeded the threshold value (p3668). Remedy: – check the fan. – reduce the power. – check the temperature sensor type setting (p3665). – infeed: check the line filter type setting (p0220). |
| A34211 (F, N) VSM: Temperature alarm threshold exceeded | Cause: The temperature (r3666) measured using the Voltage Sensing Module (VSM) has exceeded the threshold value (p3667). Remedy: – check the fan. – reduce the power. |
| N34800 (F) VSM: Group signal | Cause: The Voltage Sensing Module (VSM) has detected at least one fault. Remedy: Evaluate other actual messages. |
| F34801 (N, A) VSM DRIVE-CLiQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module (VSM). Fault cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy: – check the DRIVE-CLiQ connection. – replace the component involved. |
| F34802 (N, A) VSM: Time slice overflow | Cause: A time slice overflow has occurred on the Voltage Sensing Module. Remedy: Replace the Voltage Sensing Module. |
| F34803 VSM: Memory test | Cause: An error has occurred during the memory test on the Voltage Sensing Module. Remedy: – check whether the permissible ambient temperature for the Voltage Sensing Module is being maintained. – replace the Voltage Sensing Module. |
| F34804 (N, A) VSM: CRC | Cause: A checksum error has occurred when reading-out the program memory on the Voltage Sensing Module (VSM). Remedy: – check whether the permissible ambient temperature for the component is maintained. – replace the Voltage Sensing Module. |
| F34805 (N, A) VSM: EEPROM checksum error | Cause: Internal parameter data is corrupted. Fault value (r0949, interpret hexadecimal): 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy: – check whether the permissible ambient temperature for the component is maintained. – replace the Voltage Sensing Module (VSM). |
| F34806 VSM: Initialization | Cause: For the Voltage Sensing Module (VSM), a fault has occurred while initializing. Remedy: Replace the Voltage Sensing Module. |
| A34807 (F, N) VSM: Sequence control time monitoring | Cause: Error, timeout in the sequence control on the Voltage Sensing Module (VSM). Remedy: Replace the Voltage Sensing Module. |
| F34820 VSM DRIVE-CLiQ: Telegram error | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module involved. Fault causes include checksum error, incorrect telegram length, and various synchronization issues. Remedy: – carry out a POWER ON (switch-off/switch-on). – check the electrical cabinet design and cable routing for EMC compliance – check the DRIVE-CLiQ wiring (interrupted cable, contacts, …). |
| F34835 VSM DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module involved. The nodes do not send and receive in synchronism. Remedy: – carry out a POWER ON. – replace the component involved. |
| F34836 VSM DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy: Carry out a POWER ON. |
| F34837 VSM DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. Fault causes include errors in the telegram header or buffer memory. Remedy: – check the DRIVE-CLiQ wiring (interrupted cable, contacts, …). – check the electrical cabinet design and cable routing for EMC compliance – if required, use another DRIVE-CLiQ socket (p9904). – replace the component involved. |
| F34845 VSM DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module (VSM). Fault cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON. |
| F34850 VSM: Internal software error | Cause: An internal software error in the Voltage Sensing Module (VSM) has occurred. Fault value (r0949, interpret decimal): 1: Background time slice is blocked. 2: Checksum over the code memory is not OK. Remedy: – replace the Voltage Sensing Module (VSM). – if required, upgrade the firmware in the Voltage Sensing Module. – contact Technical Support. |
| F34851 VSM DRIVE-CLiQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit. The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit. Remedy: Upgrade the firmware of the component involved. |
| F34860 VSM DRIVE-CLiQ (CU): Telegram error | Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit. Various fault causes related to telegram integrity, timing, and content. Remedy: – carry out a POWER ON (switch-off/switch-on). – check the electrical cabinet design and cable routing for EMC compliance – check the DRIVE-CLiQ wiring (interrupted cable, contacts, …). |
| F34875 VSM: power supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage has failed. Fault cause: 9 (= 09 hex): The power supply voltage for the components has failed. Remedy: – carry out a POWER ON (switch-off/switch-on). – check the power supply voltage wiring for the DRIVE-CLiQ component (interrupted cable, contacts, …). – check the dimensioning of the power supply for the DRIVE-CLiQ component. |
| F34885 VSM DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit. The nodes do not send and receive in synchronism. Remedy: – check the power supply voltage of the component involved. – carry out a POWER ON. – replace the component involved. |
| F34886 VSM DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy: Carry out a POWER ON. |
| F34887 VSM DRIVE-CLiQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLiQ component (Voltage Sensing Module) involved. Faulty hardware cannot be excluded. Various fault causes related to telegram headers and buffer memory errors. Remedy: – check the DRIVE-CLiQ wiring (interrupted cable, contacts, …). – check the electrical cabinet design and cable routing for EMC compliance – if required, use another DRIVE-CLiQ socket (p9904). – replace the component involved. |
| F34895 VSM DRIVE-CLiQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit. Fault cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy: – Carry out a POWER ON. – See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master). |
| F34896 VSM DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (Voltage Sensing Module), specified by the fault value, have changed in an incompatible fashion with respect to the properties when booted. One cause can be, e.g. that a DRIVE-CLiQ cable or DRIVE-CLiQ component has been replaced. Remedy: – carry out a POWER ON. – when a component is replaced, the same component type and if possible the same firmware version should be used. – when a cable is replaced, only cables whose length is the same as or as close as possible to the length of the original cables should be used (ensure compliance with the maximum cable length). |
| F34899 (N, A) VSM: Unknown fault | Cause: A fault occurred on the Voltage Sensing Module 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: – If required, the significance of this new fault can be read about in a more recent description of the Control Unit. – replace the firmware on the Voltage Sensing Module by an older firmware version (r0158). – upgrade the firmware on the Control Unit (r0018). |
| A34903 (F, N) VSM: I2C bus error occurred | Cause: An error has occurred when accessing the module-internal I2C bus. Remedy: – Replace the Terminal Module / Voltage Sensing Module (VSM). |
| A34904 (F, N) VSM: EEPROM | Cause: An error has occurred accessing the non-volatile memory on the Terminal Module. Remedy: – Replace the Voltage Sensing Module (VSM). |
| A34905 (F, N) VSM: Parameter access | Cause: The Control Unit attempted to write an illegal parameter value to the Voltage Sensing Module (VSM). Remedy: – check whether the firmware version of the VSM (r0158) matches the firmware version of Control Unit (r0018). – if required, replace the Voltage Sensing Module. |
| F34920 (N, A) VSM: overtemperature or temperature sensor fault | Cause: When evaluating the temperature sensor, a resistance value outside the permissible range was detected. Fault value (r0949, interpret decimal): 1: overtemperature, wire breakage or sensor not connected. 2: Measured resistance too low. Remedy: – make sure that the sensor is connected correctly. – replace the sensor. – allow to cool down and then check the ambient conditions, load cycle and cooling (fan fuse). – check the temperature sensor type setting (p3665). – infeed: check the line filter type setting (p0220). |
| F34950 VSM: Internal software error | Cause: An internal software error in the Voltage Sensing Module (VSM) has occurred. Remedy: – if necessary, upgrade the firmware in the Voltage Sensing Module to a later version. – contact Technical Support. |
| A34999 (F, N) VSM: Unknown alarm | Cause: A fault occurred on the Voltage Sensing Module (VSM) an alarm has occurred 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: – replace the firmware on the Voltage Sensing Module by an older firmware version (r0148). – upgrade the firmware on the Control Unit (r0018). |
| F35000 TM54F: Sampling time invalid | Cause: The set sampling time is invalid. It is not a multiple integer of the DP clock cycle. Remedy: – Adapt the sampling time (e.g. set the recommended valid sampling time). – See also: p10000 (SI TM54F communication clock cycle) |
| F35001 TM54F: Parameter value invalid | Cause: The functionality of Safety Basic Functions via TM54F is used. TM54F has been incorrectly parameterized (incorrect parameter assignment). Remedy: – check the setting of the fail-safe digital inputs (F-DI) for the Safety Extended Functions – and set to a value of 0 or 255 (p10024 … p10039). – check the setting of the signal sources for the fail-safe digital outputs (F-DO) and if necessary, correct (p10042 … p10045). |
| F35002 TM54F: Commissioning not possible | Cause: The commissioning mode activation was rejected because at least one drive belonging to the TM54F is enabled for operation. Remedy: – Withdraw the operating enable for the drive specified in the fault value. |
| F35003 TM54F: Acknowledgment on the Control Unit is required | Cause: A fault on the Terminal Module 54F (TM54) was acknowledged using the safe acknowledgment (p10006). An additional acknowledgment is also required at the Control Unit. Remedy: – acknowledge all faults on the Control Unit (BI: p2102). or – acknowledge all faults on the drive object TM54F (BI: p2103, p2104 or p2105). |
| F35004 TM54F: communication cycle invalid | Cause: The communication cycle specified in p10000[x] does not correspond with the monitoring cycle of the drive object, which was specified in p10010[x]. Remedy: – First check that all drives are entered in p10010, extended safety functions or basic functions have been enabled via TM54F. – Execute the copy function for TM54F(p9700 = 87). – adapt the checksums for TM54F(p9701 = 172). – copy RAM to ROM. – carry out a POWER ON. |
| F35005 TM54F:parallel connection not supported | Cause: The TM54F function with Basic Safety Functions is used. This function is not supported when power units are connected in parallel. Remedy: – deactivate parallel connection or TM54F with Basic Safety Functions. – copy RAM to ROM. – carry out a POWER ON (switch-off/switch-on). |
| F35006 TM54F: drive groups invalid | Cause: The functionality of the basic functions via TM54F is used. Drive groups have been incorrectly parameterized (incorrect parameter assignment). Remedy: – Corresponding to the fault value, p10011 should be checked to ensure that no Basic Safety drives are mixed with Extended Safety drives in a drive group. |
| F35009 TM54F: Safety commissioning drive incomplete | Cause: For Terminal Module 54F (TM54F), a drive object was assigned (p10010), for which no safety functions or faulty safety functions are parameterized (p9501, p9601). Remedy: – carry out the safety commissioning of the drive involved and enable the safety functions for TM54F. – commission the TM54F – and just set p9700 = 87d and p9701 = 172d. |
| F35011 TM54F: Drive object number assignment illegal | Cause: A drive object number was assigned twice. Each drive object number can be assigned only once. Remedy: – Correct the assignment of the drive object numbers. – See also: p10010 (SI TM54F drive object assignment) |
| A35012 TM54F: Test stop for fail-safe digital inputs/outputs | Cause: The forced checking procedure (test stop) for the fail-safe digital inputs/outputs (F-DI/F-DO) is currently in progress. Remedy: – The alarm is automatically withdrawn after successfully ending or canceling (when a fault condition occurs) the test stop. |
| F35013 TM54F: Test stop error | Cause: A fault has been detected during the forced checking procedure (test stop) of the fail-safe digital inputs/outputs on the TM54F. Failsafe control signals (failsafe values) are transferred to the safety functions. Remedy: – Check the wiring of the F-DIs and F-DOs and restart the test stop. – Check all parameters for the test stop (p10001, p10017, p10046, p10047). – A POWER ON must be carried out after correcting the parameters. |
| A35014 TM54F: Test stop for fail-safe digital inputs/outputs | Cause: The time set in p10003 for the forced checking procedure (test stop) for the digital inputs/outputs has been exceeded. A new forced checking procedure is required. Remedy: – Carry out the forced checking procedure for the digital inputs/outputs. |
| A35015 TM54F: Motor/Hydraulic Module replaced or configuration inconsistent | Cause: Cyclic communication of at least one drive with the Terminal Module 54F (TM54F) is not active. Possible causes include: hardware replacement, inconsistent parameterization, or no DRIVE-CLiQ communication. Remedy: – For all drive objects specified in p10010, check whether the drive-based motion monitoring functions with TM54F are enabled (p9601). – When replacing a Motor Module/Hydraulic Module, carry out the following steps: start the copy function (p9700 = 1D hex), acknowledge the hardware CRC (p9701 = EC hex), save all parameters (p0977 = 1), and carry out a POWER ON. |
| A35016 TM54F: Net data communication with drive not established | Cause: The cyclic net data communication within the Terminal Module 54F (TM54F) is still not active for at least one drive. Remedy: – When replacing a Motor Module/Hydraulic Module, carry out the following steps: start the copy function (p9700 = 1D hex), acknowledge the hardware CRC (p9701 = EC hex), save all parameters (p0977 = 1), and carry out a POWER ON. – Check whether the drive-based motion monitoring functions with TM54F are enabled (p9601). |
| F35040 TM54F: 24 V undervoltage | Cause: For the 24 V power supply for the Terminal Module 54F (TM54F) an undervoltage condition was detected. Remedy: – check the 24 V DC power supply for the TM54F. – carry out safe acknowledgment (p10006). |
| F35043 TM54F: 24 V overvoltage | Cause: For the 24 V power supply for the Terminal Module 54F (TM54F) an overvoltage condition was detected. Remedy: – check the 24 V DC power supply for the TM54F. – carry out safe acknowledgment (p10006). |
| F35051 TM54F: Defect in a monitoring channel | Cause: The Terminal Module 54F (TM54F) has identified an error in the crosswise data comparison between the two control channels. This can be the result of incorrect parameterization or defective hardware. Remedy: – Check the specified parameters for incorrect parameterization. – Activate the safety commissioning mode (p0010 = 95) and perform data copy and acknowledgment. – Save all parameters (p0977 = 1) and carry out safe acknowledgment (p10006). – For an internal software error, upgrade firmware or replace the TM54F. |
| F35052 (A) TM54F: Internal hardware error | Cause: An internal software/hardware error has been detected on the Terminal Module 54F (TM54F). Remedy: – check the electrical cabinet design and cable routing for EMC compliance – upgrade TM54F firmware to more recent version. – contact Technical Support. – replace the TM54F. |
| F35053 TM54F: Temperature fault threshold exceeded | Cause: The temperature measured using the temperature sensing on the TM54F has exceeded the threshold value to initiate this fault. Remedy: – allow the TM54F to cool down. – carry out safe acknowledgment (p10006). |
| A35054 TM54F: Temperature alarm threshold exceeded | Cause: The temperature measured using the temperature sensing on the TM54F has exceeded the threshold value to initiate this alarm. Remedy: – allow the TM54F to cool down. – carry out safe acknowledgment (p10006). |
| A35075 (F) TM54F: Error during internal communication | Cause: An internal communications error has occurred in the Terminal Module 54F (TM54F). This message is also output if parameter p10000 or p10010 (TM54F master) is not set the same as on the TM54F slave. Remedy: – For parameter mismatch: start copy function for node identifier (p9700 = 1D hex), acknowledge hardware CRC (p9701 = EC hex), save all parameters, and carry out a POWER ON. – For internal communication errors: check cabinet design and routing for EMC, upgrade software, contact support, or replace the TM54F. |
| A35080 (F) TM54F: Checksum error safety parameters | Cause: The calculated checksum entered in r10004 over the safety-relevant parameters does not match the reference checksum saved in p10005 at the last machine acceptance. Remedy: – check the safety-relevant parameters and if required, correct. – set the reference checksum to the actual checksum. – acknowledge the hardware replacement. – carry out a POWER ON (switch off/on). – carry out an acceptance test. |
| A35081 (F) TM54F: Static (steady state) 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. Remedy: – Set the fail-safe digital input (F-DI) to a logical 0 signal (p10006). |
| F35150 TM54F: Communication error | Cause: A communication error between the TM54F master and Control Unit or between the TM54F slave and the Motor Module/Hydraulic Module was detected. Remedy: – When replacing a Motor Module/Hydraulic Module, carry out the following steps: start the copy function for the node identifier on the TM54F (p9700 = 1D hex), acknowledge the hardware CRC on the TM54F (p9701 = EC hex), save all parameters (p0977 = 1), and carry out a POWER ON (switch off/on) for all components. – The following always applies: check the electrical cabinet design and cable routing for EMC compliance, upgrade the software on the TM54F, contact Technical Support, or replace the TM54F. |
| F35151 TM54F: Discrepancy error | Cause: The safety input terminals or output terminals show a different state longer than that parameterized in p10002. Remedy: – Check the wiring of the corresponding F-DI (contact problems). – Using the commissioning software, evaluate the input states and output states of the TM54F. – Compare parameters p10051 and p10052 from the TM54F master and TM54F slave for discrepancy. – Adjust the discrepancy time (p10002) for cyclic switching operations at the F-DIs based on the formulas provided in the manual. |
| F35152 TM54F: Internal software error | Cause: An internal software error has occurred in the Terminal Module 54F (TM54F). The fail-safe digital inputs and digital outputs (F-DI, F-DO) on the TM54F have been set to the safe state. Remedy: – Check that the firmware version of the TM54F matches the Control Unit’s firmware version. – The automatic firmware update must be activated in the project. – This signal may also appear with fault F35013. In this case, check all parameters for the test stop on the TM54F. A POWER ON is required after correcting parameters. |
| A35200 (F, N) TM: Calibration data | Cause: An error was detected in the calibration data of the Terminal Module. Remedy: – carry out a POWER ON (switch off/on) for all components. – replace the component if necessary. |
| F35207 (N, A) TM: Temperature fault/alarm threshold channel 0 exceeded | Cause: For the temperature evaluation via the Terminal Module (TM), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[0], p4103[0]), or fault threshold exceeded (p4102[1]). Remedy: – allow the temperature sensor to cool down to below p4102[1] – hysteresis (5 K, for TM150, can be set using p4118[0]). – if required, set the fault response to NONE (p2100, p2101). |
| F35208 (N, A) TM: Temperature fault/alarm threshold channel 1 exceeded | Cause: For the temperature evaluation via the Terminal Module (TM), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[2], p4103[1]), or fault threshold exceeded (p4102[3]). Remedy: – allow the temperature sensor to cool down to below p4102[3] – hysteresis (5 K, for TM150, can be set using p4118[1]). – if required, set the fault response to NONE (p2100, p2101). |
| F35209 (N, A) TM: Temperature fault/alarm threshold channel 2 exceeded | Cause: For the temperature evaluation via the Terminal Module (TM), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[4], p4103[2]), or fault threshold exceeded (p4102[5]). Remedy: – allow the temperature sensor to cool down to below p4102[5] – hysteresis (5 K, for TM150, can be set using p4118[2]). – if required, set the fault response to NONE (p2100, p2101). |
| F35210 (N, A) TM: Temperature fault/alarm threshold channel 3 exceeded | Cause: For the temperature evaluation via the Terminal Module (TM), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[6], p4103[3]), or fault threshold exceeded (p4102[7]). Remedy: – allow the temperature sensor to cool down to below p4102[7] – hysteresis (5 K, for TM150, can be set using p4118[3]). – if required, set the fault response to NONE (p2100, p2101). |
| A35211 (F, N) TM: Temperature alarm threshold channel 0 exceeded | Cause: The temperature measured using the temperature sensing of the Terminal Module (TM) (r4105[0]) has exceeded the threshold value to initiate this alarm (p4102[0]). Remedy: – Allow the temperature sensor to cool down to below p4102[0] – hysteresis (5 K, for TM150, can be set using p4118[0]). |
| A35212 (F, N) TM: Temperature alarm threshold channel 1 exceeded | Cause: The temperature measured using the temperature sensing of the Terminal Module (TM) (r4105[1]) has exceeded the threshold value to initiate this alarm (p4102[2]). Remedy: – Allow the temperature sensor to cool down to below p4102[4] – hysteresis (5 K, for TM150, can be set using p4118[1]). |
| A35213 (F, N) TM: Temperature alarm threshold channel 2 exceeded | Cause: The temperature measured using the temperature sensing of the Terminal Module (TM) (r4105[2]) has exceeded the threshold value to initiate this alarm (p4102[4]). Remedy: – Allow the temperature sensor to cool down to below p4102[4] – hysteresis (5 K, for TM150, can be set using p4118[2]). |
| A35214 (F, N) TM: Temperature alarm threshold channel 3 exceeded | Cause: The temperature measured using the temperature sensing of the Terminal Module (TM) (r4105[3]) has exceeded the threshold value to initiate this alarm (p4102[6]). Remedy: – Allow the temperature sensor to cool down to below p4102[6] – hysteresis (5 K, for TM150, can be set using p4118[3]). |
| F35220 (N, A) TM: Frequency limit reached for signal output | Cause: The signals output from the Terminal Module 41 (TM41) for tracks A/B have reached the limit frequency. The output signals are no longer in synchronism with the specified setpoint. Remedy: – SIMOTION (p4400 = 0) operating mode: enter a lower speed setpoint (p1155), reduce the encoder pulse number (p0408), check track A/B for short-circuits. – SINAMICS (p4400 = 1) operating mode: enter a lower speed setpoint (p1155), reduce the encoder pulse number (p0408). |
| F35221 (N, A) TM: Setpoint – actual value deviation outside the tolerance range | Cause: The deviation between the setpoint and the output signals (track A/B) exceeds the tolerance of +/-3 %. The deviation between the internal and external measured value is too high (> 1000 pulses). Remedy: – reduce the basic clock cycle (p0110, p0111). – if required, replace the component (e.g. internal short-circuit). |
| A35222 (F, N) TM: Encoder pulse number not permissible | Cause: The encoder pulse number entered does not match the permissible pulse number from a hardware perspective. Alarm value (r2124, interpret decimal): 1: Encoder pulse number is too high. 2: Encoder pulse number is too low. 4: Encoder pulse number is less than the zero mark offset (p4426). Remedy: – enter the encoder pulse number in the permissible range (p0408). – if necessary, replace TM41 SAC with TM41 DAC. |
| A35223 (F, N) TM: Zero mark offset not permissible | Cause: The entered zero mark offset is not permissible. Alarm value (r2124, interpret decimal): 1: Zero mark offset is too high. Remedy: – Enter the zero mark offset in the permissible range (p4426). |
| F35230 TM: Hardware fault | Cause: The Terminal Module (TM) used has signaled internal errors. Signals from this module may not be evaluated because they are very likely to be incorrect. Remedy: – If required, replace the Terminal Module. |
| F35233 DRIVE-CLiQ component function not supported | Cause: A function requested by the Control Unit is not supported by a DRIVE-CLiQ component. Remedy: – For fault value = 1: Deactivate timer for temperature evaluation (X522.7/8) (p4103 = 0.000) or use a compatible Terminal Module. |
| F35400 (N, A) TM: Temperature fault/alarm threshold channel 4 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[8], p4103[4]), or fault threshold exceeded (p4102[9]). Remedy: – allow the temperature sensor to cool down to below p4102[9] – hysteresis (p4118[4]). – if required, set the fault response to NONE (p2100, p2101). |
| F35401 (N, A) TM: Temperature fault/alarm threshold channel 5 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[10], p4103[5]), or fault threshold exceeded (p4102[11]). Remedy: – allow the temperature sensor to cool down to below p4102[11] – hysteresis (p4118[5]). – if required, set the fault response to NONE (p2100, p2101). |
| F35402 (N, A) TM: Temperature fault/alarm threshold channel 6 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[12], p4103[6]), or fault threshold exceeded (p4102[13]). Remedy: – allow the temperature sensor to cool down to below p4102[13] – hysteresis (p4118[6]). – if required, set the fault response to NONE (p2100, p2101). |
| F35403 (N, A) TM: Temperature fault/alarm threshold channel 7 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[14], p4103[7]), or fault threshold exceeded (p4102[15]). Remedy: – allow the temperature sensor to cool down to below p4102[15] – hysteresis (p4118[7]). – if required, set the fault response to NONE (p2100, p2101). |
| F35404 (N, A) TM: Temperature fault/alarm threshold channel 8 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[16], p4103[8]), or fault threshold exceeded (p4102[17]). Remedy: – allow the temperature sensor to cool down to below p4102[17] – hysteresis (p4118[8]). – if required, set the fault response to NONE (p2100, p2101). |
| F35405 (N, A) TM: Temperature fault/alarm threshold channel 9 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[18], p4103[9]), or fault threshold exceeded (p4102[19]). Remedy: – allow the temperature sensor to cool down to below p4102[19] – hysteresis (p4118[9]). – if required, set the fault response to NONE (p2100, p2101). |
| F35406 (N, A) TM: Temperature fault/alarm threshold channel 10 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[20], p4103[10]), or fault threshold exceeded (p4102[21]). Remedy: – allow the temperature sensor to cool down to below p4102[21] – hysteresis (p4118[10]). – if required, set the fault response to NONE (p2100, p2101). |
| F35407 (N, A) TM: Temperature fault/alarm threshold channel 11 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[22], p4103[11]), or fault threshold exceeded (p4102[23]). Remedy: – allow the temperature sensor to cool down to below p4102[23] – hysteresis (p4118[11]). – if required, set the fault response to NONE (p2100, p2101). |
| A35410 (F, N) TM: Temperature alarm threshold channel 4 exceeded | Cause: The temperature (r4105[4]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[8]). Remedy: – Allow the temperature sensor to cool down to below p4102[8] – hysteresis (p4118[4]). |
| A35411 (F, N) TM: Temperature alarm threshold channel 5 exceeded | Cause: The temperature (r4105[5]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[10]). Remedy: – Allow the temperature sensor to cool down to below p4102[10] – hysteresis (p4118[5]). |
| A35412 (F, N) TM: Temperature alarm threshold channel 6 exceeded | Cause: The temperature (r4105[6]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[12]). Remedy: – Allow the temperature sensor to cool down to below p4102[12] – hysteresis (p4118[6]). |
| A35413 (F, N) TM: Temperature alarm threshold channel 7 exceeded | Cause: The temperature (r4105[7]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[14]). Remedy: – Allow the temperature sensor to cool down to below p4102[14] – hysteresis (p4118[7]). |
| A35414 (F, N) TM: Temperature alarm threshold channel 8 exceeded | Cause: The temperature (r4105[8]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[16]). Remedy: – Allow the temperature sensor to cool down to below p4102[16] – hysteresis (p4118[8]). |
| A35415 (F, N) TM: Temperature alarm threshold channel 9 exceeded | Cause: The temperature (r4105[9]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[18]). Remedy: – Allow the temperature sensor to cool down to below p4102[18] – hysteresis (p4118[9]). |
| A35416 (F, N) TM: Temperature alarm threshold channel 10 exceeded | Cause: The temperature (r4105[10]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[20]). Remedy: – Allow the temperature sensor to cool down to below p4102[20] – hysteresis (p4118[10]). |
| A35417 (F, N) TM: Temperature alarm threshold channel 11 exceeded | Cause: The temperature (r4105[11]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[22]). Remedy: – Allow the temperature sensor to cool down to below p4102[22] – hysteresis (p4118[11]). |
| N35800 (F) TM: Group signal | Cause: The Terminal Module has detected at least one fault. Remedy: Evaluates other actual messages. |
| F35801 (N, A) TM DRIVE-CLIQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred between the Control Unit and the Terminal Module involved. Fault cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| A35802 (F, N) TM: Time slice overflow | Cause: A time slice overflow has occurred on the Terminal Module. Remedy: Replace the Terminal Module. |
| F35804 (N, A) TM: CRC | Cause: A checksum error has occurred when reading-out the program memory on the Terminal Module. Fault value (r0949, interpret hexadecimal): Difference between the checksum at POWER ON and the actual checksum. Remedy:
|
| F35805 (N, A) TM: EEPROM checksum error | Cause: Internal parameter data is corrupted. Alarm value (r2124, interpret hexadecimal): 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy:
|
| F35820 TM DRIVE-CLIQ: Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the Terminal Module involved. Fault cause: 1 (= 01 hex): Checksum error (CRC error). 2 (= 02 hex): Telegram is shorter than specified in the length byte or in the receive list. 3 (= 03 hex): Telegram is longer than specified in the length byte or in the receive list. 4 (= 04 hex): The length of the receive telegram does not match the receive list. 5 (= 05 hex): The type of the receive telegram does not match the receive list. 6 (= 06 hex): The address of the component in the telegram and in the receive list do not match. 7 (= 07 hex): A SYNC telegram is expected – but the received telegram is not a SYNC telegram. 8 (= 08 hex): No SYNC telegram is expected – but the received telegram is one. 9 (= 09 hex): The error bit in the receive telegram is set. 16 (= 10 hex): The receive telegram is too early. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| F35835 TM DRIVE-CLIQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the Terminal Module involved. The nodes do not send and receive in synchronism. Fault cause: 33 (= 21 hex): The cyclic telegram has not been received. 34 (= 22 hex): Timeout in the telegram receive list. 64 (= 40 hex): Timeout in the telegram send list. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| F35836 TM DRIVE-CLIQ: Send error for DRIVE-CLIQ data | Cause: A DRIVE-CLiQ communication error has occurred between the Control Unit and the Terminal Module involved. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy: Carry out a POWER ON. |
| F35837 PTM DRIVE-CLIQ: Component fault | Cause: Fault detected on the DRIVE-CLIQ component concerned. Faulty hardware cannot be excluded. Fault cause: 32 (= 20 hex): Error in the telegram header. 35 (= 23 hex): Receive error: The telegram buffer memory contains an error. 66 (= 42 hex): Send error: The telegram buffer memory contains an error. 67 (= 43 hex): Send error: The telegram buffer memory contains an error. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| F35845 TM DRIVE-CLIQ: Cyclic data transfer error | Cause: A DRIVE-CLIQ communication error has occurred between the Control Unit and the Terminal Module (TM) involved. Fault cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy: Carry out a POWER ON. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
| F35850 TM: Internal software error | Cause: An internal software error in the Terminal Module (TM) has occurred. Fault value (r0949, interpret decimal): 1: Background time slice is blocked. 2: Checksum over the code memory is not OK. Remedy:
|
| F35851 TM DRIVE-CLIQ (CU): Sign-of-life missing | Cause: A DRIVE-CLIQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit. The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit. Fault cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy: Upgrade the firmware of the component involved. |
| F35860 TM DRIVE-CLIQ (CU): Telegram error | Cause: A DRIVE-CLIQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit. Fault cause: 1 (= 01 hex): Checksum error (CRC error). 2 (= 02 hex): Telegram is shorter than specified in the length byte or in the receive list. 3 (= 03 hex): Telegram is longer than specified in the length byte or in the receive list. 4 (= 04 hex): The length of the receive telegram does not match the receive list. 5 (= 05 hex): The type of the receive telegram does not match the receive list. 6 (= 06 hex): The address of the power unit in the telegram and in the receive list do not match. Remedy: 9 (= 09 hex): The DRIVE-CLIQ communication from the DRIVE-CLIQ component involved to the Control Unit signals that the supply voltage has failed. 16 (= 10 hex): The receive telegram is too early. 17 (= 11 hex): CRC error and the receive telegram is too early. 18 (= 12 hex): The telegram is shorter than that specified in the length byte or in the receive list and the receive telegram is too early. 19 (= 13 hex): The telegram is longer than that specified in the length byte or in the receive list and the receive telegram is too early. 20 (= 14 hex): The length of the receive telegram does not match the receive list and the receive telegram is too early. 21 (= 15 hex): The type of the receive telegram does not match the receive list and the receive telegram is too early. 22 (= 16 hex): The address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early. 25 (= 19 hex): The error bit in the receive telegram is set and the receive telegram is too early. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause
|
| F35875 TM: power supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLIQ component involved to the Control Unit signals that the supply voltage has failed. Fault cause: 9 (= 09 hex): The power supply voltage for the components has failed. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| F35885 TM DRIVE-CLIQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLIQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit. The nodes do not send and receive in synchronism. Fault cause: 26 (= 1A hex): Sign-of-life bit in the receive telegram not set and the receive telegram is too early. 33 (= 21 hex): The cyclic telegram has not been received. 34 (= 22 hex): Timeout in the telegram receive list. 64 (= 40 hex): Timeout in the telegram send list. 98 (= 62 hex): Error at the transition to cyclic operation. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| F35886 TM DRIVE-CLIQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLIQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy: Carry out a POWER ON. |
| F35887 TM DRIVE-CLiQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLIQ component (Terminal Module) involved. Faulty hardware cannot be excluded. Fault cause: 32 (= 20 hex): Error in the telegram header. 35 (= 23 hex): Receive error: The telegram buffer memory contains an error. 66 (= 42 hex): Send error: The telegram buffer memory contains an error. 67 (= 43 hex): Send error: The telegram buffer memory contains an error. 96 (= 60 hex): Response received too late during runtime measurement. 97 (= 61 hex): Time taken to exchange characteristic data too long. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| F35895 TM DRIVE-CLIQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLIQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit. Fault cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy: Carry out a POWER ON. See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master) |
| F35896 TM DRIVE-CLIQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLIQ component (Terminal Module), specified by the fault value, have changed in an incompatible fashion with respect to the properties when booted. One cause can be, e.g. that a DRIVE-CLiQ cable or DRIVE-CLIQ component has been replaced. Fault value (r0949, interpret decimal): Component number. Remedy:
|
| F35899 (N, A) TM: Unknown fault | Cause: A fault has occurred on the Terminal Module 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. Note: If required, the significance of this new fault can be read about in a more recent description of the Control Unit. Remedy:
|
| A35903 (F, N) TM: I2C bus error occurred | Cause: An error has occurred while accessing the internal I2C bus of the Terminal Module. Remedy: Replace the Terminal Module. |
| A35904 (F, N) TM: EEPROM | Cause: An error has occurred accessing the non-volatile memory on the Terminal Module. Remedy: Replace the Terminal Module. |
| A35905 (F, N) TM: Parameter access | Cause: The Control Unit attempted to write an illegal parameter value to the Terminal Module. Remedy:
|
| A35906 (F, N) TM: 24 V power supply missing | Cause: The 24 V power supply for the digital outputs is missing. Alarm value (r2124, interpret hexadecimal): 01: TM17 24 V power supply for DI/DO 0 … 7 missing. 02: TM17 24 V power supply for DI/DO 8 … 15 missing. 04: TM15 24 V power supply for DI/DO 0 … 7 (X520) missing. 08: TM15 24 V power supply for DI/DO 8 … 15 (X521) missing. 10: TM15 24 V power supply for DI/DO 16 … 23 (X522) missing. 20: TM41 24 V power supply for DI/DO 0 … 3 missing. Remedy: Check the terminals for the power supply voltage (L1+, L2+, L3+, M or +24 V_1 for TM41). |
| A35907 (F, N) TM: Hardware initialization error | Cause: The Terminal Module was not successfully initialized. Alarm value (r2124, interpret hexadecimal): 01: TM17 or TM41 – incorrect configuration request. 02: TM17 or TM41 – programming not successful. 04: TM17 or TM41 – invalid time stamp Remedy: Carry out a POWER ON. |
| A35910 (F, N) TM: Module overtemperature | Cause: The temperature in the module has exceeded the highest permissible limit. Remedy:
|
| A35911 (F, N) TM: Clock synchronous operation sign-of-life missing | Cause: The maximum permissible number of errors in the master sign-of-life (clock synchronous operation) has been exceeded in cyclic operation. When the alarm is output, the module outputs are reset up to the next synchronization. Remedy:
|
| A35920 (F, N) TM: Error temperature sensor channel 0 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 1630 Ohm (TM150: R > 2170 Ohm), PT100: R > 194 Ohm, PT1000: R > 1720 Ohm (TM150: R > 1944 Ohm) 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 50 Ohm (TM150: R < 180 Ohm), PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
| A35921 (F, N) TM: Error temperature sensor channel 1 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 1630 Ohm (TM150: R > 2170 Ohm), PT100: R > 194 Ohm, PT1000: R > 1720 Ohm (TM150: R > 1944 Ohm) 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 50 Ohm (TM150: R < 180 Ohm), PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
| A35922 (F, N) TM: Error temperature sensor channel 2 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 1630 Ohm (TM150: R > 2170 Ohm), PT100: R > 194 Ohm, PT1000: R > 1720 Ohm (TM150: R > 1944 Ohm) 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 50 Ohm (TM150: R < 180 Ohm), PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
| A35923 (F, N) TM: Error temperature sensor channel 3 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 1630 Ohm (TM150: R > 2170 Ohm), PT100: R > 194 Ohm, PT1000: R > 1720 Ohm (TM150: R > 1944 Ohm) 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 50 Ohm (TM150: R < 180 Ohm), PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
| A35924 (F, N) TM: Error temperature sensor channel 4 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 2170 Ohm, PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 180 Ohm, PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
| A35925 (F, N) TM: Error temperature sensor channel 5 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 2170 Ohm, PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 180 Ohm, PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
| A35926 (F, N) TM: Error temperature sensor channel 6 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 2170 Ohm, PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 180 Ohm, PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
| A35927 (F, N) TM: Error temperature sensor channel 7 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 2170 Ohm, PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 180 Ohm, PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
| A35928 (F, N) TM: Error temperature sensor channel 8 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 2170 Ohm, PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 180 Ohm, PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
| A35929 (F, N) TM: Error temperature sensor channel 9 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 2170 Ohm, PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 180 Ohm, PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
| A35930 (F, N) TM: Error temperature sensor channel 10 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A35931 (F, N) TM: Error temperature sensor channel 11 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| F35950 TM: Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Information about the fault source. Only for internal Siemens troubleshooting. Remedy:
|
| A35999 (F, N) TM: Unknown alarm | Cause: An alarm has occurred on the Terminal Module that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Alarm value (r2124, interpret decimal): Alarm number. Remedy:
|
| F36207 (N, A) Hub: Overtemperature component | Cause: The temperature on the DRIVE-CLiQ Hub Module has exceeded the fault threshold. Fault value (r0949, interpret decimal): Actual temperature in 0.1 °C resolution. Remedy:
|
| A36211 (F, N) Hub: Overtemperature alarm component | Cause: The temperature on the DRIVE-CLiQ Hub Module has exceeded the alarm threshold. Alarm value (r2124, interpret decimal): Actual temperature in 0.1 °C resolution. Remedy:
|
| F36214 (N, A) Hub: overvoltage fault 24 V supply | Cause: The 24 V power supply on the DRIVE-CLiQ Hub Module has exceeded the fault threshold. Fault value (r0949, interpret decimal): Actual operating voltage in 0.1 V resolution. Remedy:
|
| F36216 (N, A) Hub: undervoltage fault 24 V supply | Cause: The 24 V power supply on the DRIVE-CLiQ Hub Module has undershot the fault threshold. Fault value (r0949, interpret decimal): Actual operating voltage in 0.1 V resolution. Remedy:
|
| A36217 (N) Hub: undervoltage alarm 24 V supply | Cause: The 24 V power supply on the DRIVE-CLiQ Hub Module has undershot the alarm threshold. Alarm value (r2124, interpret decimal): Actual operating voltage in 0.1 V resolution. Remedy:
|
| N36800 (F) Hub: Group signal | Cause: The DRIVE-CLiQ Hub Module has detected at least one fault. Remedy: Evaluates other actual messages. |
| A36801 (F, N) Hub DRIVE-CLIQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the DRIVE-CLiQ Hub Module involved. Fault cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
|
| A36802 (F, N) Hub: Time slice overflow | Cause: A time slice overflow has occurred on the DRIVE-CLiQ Hub Module. Fault value (r0949, interpret decimal): xx: Time slice number xx Remedy:
|
| F36804 (N, A) Hub: Checksum error | Cause: A checksum error has occurred when reading out the program memory on the DRIVE-CLiQ Hub Module. Fault value (r0949, interpret hexadecimal): Difference between the checksum at POWER ON and the actual checksum. Remedy:
|
| F36805 (N, A) Hub: EEPROM checksum incorrect | Cause: The internal parameter data on the DRIVE-CLiQ Hub Module is incorrect. Alarm value (r2124, interpret hexadecimal): 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy:
|
| F36820 Hub DRIVE-CLIQ: Telegram error | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the DRIVE-CLiQ Hub Module involved. Various fault causes are listed, including checksum errors, incorrect telegram length, and mismatched addresses. Remedy:
|
| F36835 Hub DRIVE-CLIQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred. The nodes do not send and receive in synchronism. Fault causes include: cyclic telegram not received and timeouts. Remedy:
|
| F36836 Hub DRIVE-CLIQ: Send error for DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communications error has occurred. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy: Carry out a POWER ON. |
| F36837 Hub DRIVE-CLIQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. Fault causes include errors in the telegram header and buffer memory. Remedy:
|
| F36845 Hub DRIVE-CLIQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred. Fault cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON. |
| F36851 Hub DRIVE-CLIQ (CU): Sign-of-life missing | Cause: DRIVE-CLiQ communication error from DRIVE-CLiQ Hub Module. The component did not set the sign-of-life to the Control Unit. Fault cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy: Upgrade the firmware of the component involved. |
| F36860 Hub DRIVE-CLIQ (CU): Telegram error | Cause: DRIVE-CLiQ communication error from the Hub Module. Multiple fault causes are listed relating to checksum errors, telegram length, addressing, supply voltage failure, and timing. Remedy:
|
| F36875 HUB: power supply voltage failed | Cause: The DRIVE-CLiQ communication signals that the supply voltage has failed. Fault cause: 9 (= 09 hex): The power supply voltage for the components has failed. Remedy:
|
| F36885 Hub DRIVE-CLIQ (CU): Cyclic data transfer error | Cause: DRIVE-CLiQ communication error from the Hub Module. The nodes do not send and receive in synchronism. Fault causes include: sign-of-life bit not set, cyclic telegram not received, timeouts, and transition errors. Remedy:
|
| F36886 Hub DRIVE-CLIQ (CU): Error when sending DRIVE-CLIQ data | Cause: DRIVE-CLiQ communication error. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy: Carry out a POWER ON. |
| F36887 Hub DRIVE-CLiQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLiQ Hub Module. Faulty hardware cannot be excluded. Various causes including telegram header/buffer errors and late responses. Remedy:
|
| F36895 Hub DRIVE-CLiQ (CU): Alternating cyclic data transfer error | Cause: DRIVE-CLiQ communication error from the Hub Module. Fault cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON. |
| F36896 Hub DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ Hub Module have changed since boot (e.g., a component or cable has been replaced). Remedy:
|
| F36899 (N, A) Hub: Unknown fault | Cause: A fault occurred on the Hub Module that cannot be interpreted by the Control Unit firmware (likely a version mismatch). Remedy:
|
| F36950 Hub: Internal software error | Cause: An internal software error has occurred. This is for internal Siemens troubleshooting. Remedy:
|
| A36999 (F, N) Hub: Unknown alarm | Cause: An alarm occurred on the Hub Module that cannot be interpreted by the Control Unit firmware (likely a version mismatch). Remedy:
|
| F40000 Fault at DRIVE-CLIQ socket X100 | Cause: A fault has occurred at the drive object at the DRIVE-CLIQ socket X100. Remedy: Evaluate the fault buffer of the specified object. |
| F40001 Fault at DRIVE-CLIQ socket X101 | Cause: A fault has occurred at the drive object at the DRIVE-CLIQ socket X101. Remedy: Evaluate the fault buffer of the specified object. |
| F40002 Fault at DRIVE-CLIQ socket X102 | Cause: A fault has occurred at the drive object at the DRIVE-CLIQ socket X102. Remedy: Evaluate the fault buffer of the specified object. |
| F40003 Fault at DRIVE-CLIQ socket X103 | Cause: A fault has occurred at the drive object at the DRIVE-CLIQ socket X103. Remedy: Evaluate the fault buffer of the specified object. |
| F40004 Fault at DRIVE-CLIQ socket X104 | Cause: A fault has occurred at the drive object at the DRIVE-CLIQ socket X104. Remedy: Evaluate the fault buffer of the specified object. |
| F40005 Fault at DRIVE-CLIQ socket X105 | Cause: A fault has occurred at the drive object at the DRIVE-CLIQ socket X105. Remedy: Evaluate the fault buffer of the specified object. |
| A40100 Alarm at DRIVE-CLIQ socket X100 | Cause: An alarm has occurred at the drive object at the DRIVE-CLIQ socket X100. Remedy: Evaluate the alarm buffer of the specified object. |
| A40101 Alarm at DRIVE-CLIQ socket X101 | Cause: An alarm has occurred at the drive object at the DRIVE-CLIQ socket X101. Remedy: Evaluate the alarm buffer of the specified object. |
| A40102 Alarm at DRIVE-CLIQ socket X102 | Cause: An alarm has occurred at the drive object at the DRIVE-CLIQ socket X102. Remedy: Evaluate the alarm buffer of the specified object. |
| A40103 Alarm at DRIVE-CLIQ socket X103 | Cause: An alarm has occurred at the drive object at the DRIVE-CLIQ socket X103. Remedy: Evaluate the alarm buffer of the specified object. |
| A40104 Alarm at DRIVE-CLIQ socket X104 | Cause: An alarm has occurred at the drive object at the DRIVE-CLIQ socket X104. Remedy: Evaluate the alarm buffer of the specified object. |
| A40105 Alarm at DRIVE-CLIQ socket X105 | Cause: An alarm has occurred at the drive object at the DRIVE-CLIQ socket X105. Remedy: Evaluate the alarm buffer of the specified object. |
| F40799 CX32: Configured transfer end time exceeded | Cause: The configured transfer end time when transferring the cyclic actual values was exceeded. Remedy:
|
| F40801 CX32 DRIVE-CLiQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the controller extension involved. The sign-of-life bit in the receive telegram is not set. Remedy:
|
| F40820 CX32 DRIVE-CLIQ: Telegram error | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the controller extension involved. Various fault causes are listed, including checksum errors, incorrect telegram length, and mismatched addresses. Remedy:
|
| F40825 CX32 DRIVE-CLIQ: Supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage has failed. Remedy:
|
| F40835 CX32 DRIVE-CLIQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred. The nodes do not send and receive in synchronism. Fault causes include: cyclic telegram not received and timeouts. Remedy:
|
| F40836 CX32 DRIVE-CLIQ: Send error for DRIVE-CLIQ data | Cause: A DRIVE-CLiQ communications error has occurred. Data were not able to be sent. Telegram type does not match send list. Remedy: Carry out a POWER ON (switch-off/switch-on). |
| F40837 CX32 DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. Fault causes include errors in the telegram header and buffer memory. Remedy:
|
| F40845 CX32 DRIVE-CLIQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred. Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON (switch-off/switch-on). |
| F40851 CX32 DRIVE-CLIQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communications error has occurred from the controller extension involved to the Control Unit. The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit. Remedy: Upgrade the firmware of the component involved. |
| F40860 CX32 DRIVE-CLiQ (CU): Telegram error | Cause: A DRIVE-CLiQ communications error has occurred from the controller extension involved to the Control Unit. Multiple fault causes are listed relating to checksum errors, telegram length, addressing, and timing. Remedy:
|
| F40875 CX32 DRIVE-CLIQ (CU): Supply voltage failed | Cause: The DRIVE-CLiQ communication signals that the supply voltage has failed. Remedy:
|
| F40885 CX32 DRIVE-CLIQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred. The nodes do not send and receive in synchronism. Various causes related to telegram timing and reception. Remedy:
|
| F40886 CX32 DRIVE-CLIQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communications error has occurred. Data were not able to be sent. Telegram type does not match send list. Remedy: Carry out a POWER ON (switch-off/switch-on). |
| F40887 CX32 DRIVE-CLiQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. Various causes including telegram header/buffer errors and late responses. Remedy:
|
| F40895 CX32 DRIVE-CLIQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred. Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON (switch-off/switch-on). |
| F49150 Cooling unit: Fault occurred | Cause: The cooling unit signals a general fault. Remedy:
|
| F49151 Cooling unit: Conductivity has exceeded the fault threshold | Cause: The conductivity of the cooling liquid has exceeded the selected fault threshold. Remedy: Check the device to de-ionize the cooling liquid. |
| F49152 Cooling unit: ON command feedback signal missing | Cause: The feedback signal of the ON command of the cooling unit is missing. Remedy:
|
| F49153 Cooling unit: Liquid flow too low | Cause: The drive converter cooling unit signals that the cooling liquid flow is too low. Remedy:
|
| F49154 (A) Cooling unit: Liquid leak is present | Cause: The liquid leakage monitoring function has responded. Remedy:
|
| F49155 Cooling unit: Power Stack Adapter, firmware version too old | Cause: The firmware version in the Power Stack Adapter (PSA) is too old and does not support the liquid cooling. Remedy: Upgrade the firmware. Check EEPROM data. |
| F49156 Cooling unit: Cooling liquid temperature has exceeded the fault threshold | Cause: The cooling liquid intake temperature has exceeded the specified fault threshold. Remedy: Check the cooling system and the ambient conditions. |
| A49170 Cooling unit: Alarm has occurred | Cause: The cooling unit signals a general alarm. Remedy:
|
| A49171 (N) Cooling unit: Conductivity has exceeded the alarm threshold | Cause: The conductivity of the cooling liquid has exceeded the selected alarm threshold. Remedy: Check the device to de-ionize the cooling liquid. |
| A49172 Cooling unit: Conductivity actual value is not valid | Cause: When monitoring the conductivity of the cooling liquid, there is a fault in the wiring or in the sensor. Remedy:
|
| A49173 Cooling unit: Cooling liquid temperature has exceeded the alarm threshold | Cause: The cooling liquid intake temperature has exceeded the specified alarm threshold. Remedy: Check the cooling system and the ambient conditions. |
| F49200 Excitation group signal fault | Cause: The excitation sequence control signals a fault. Various bit-specific causes are listed related to feedback signals and timing. Remedy:
|
| A49201 (F) Excitation group signal alarm | Cause: The “excitation group signal alarm” signal is present. Remedy: Check the excitation equipment. |
| A49204 (N) Excitation switch-off alarm | Cause: When switching off the excitation, the excitation current has still not decayed to zero after the delay time has expired. Remedy: Extend the switch-off delay time. |
| A49998 Recorder trigger event occurred | Cause: A recorder trigger event has occurred. The data are then written to the memory card. Remedy: Not necessary. This message disappears automatically. |
| A50001 (F) PN/COMM BOARD: Configuration error | Cause: A PROFINET controller attempts to establish a connection using an incorrect configuring telegram. Various alarm values indicate specific configuration mismatches. Remedy: Check the configuration of the PROFINET controllers. |
| A50002 (F) COMM BOARD: Alarm 2 | Cause: A specific telegram word (send) is being used twice. Remedy: Correct the parameter assignment. |
| A50003 (F) COMM BOARD: Alarm 3 | Cause: A specific telegram word (receive) is being used twice. Remedy: Correct the parameter assignment. |
| A50004 (F) COMM BOARD: Alarm 4 | Cause: Telegram word (receive) and address of sender are inconsistent or the sender address exceeds the maximum project address. Remedy: Correct the parameter assignment. |
| A50005 (F) COMM BOARD: Alarm 5 | Cause: Sender not found on SINAMICS Link. Remedy: Check the connection to the sender and set parameters correctly for all participants. |
| A50006 (F) COMM BOARD: Alarm 6 | Cause: The parameter assignment indicates that the sender and the receiver are one and the same, which is not permitted. Remedy: Correct the parameter assignment. |
| A50007 (F) COMM BOARD: Alarm 7 | Cause: A send telegram word is greater than possible in the project. Remedy: Correct the parameter assignment. |
| A50008 (F) COMM BOARD: Alarm 8 | Cause: A receive telegram word is greater than possible in the project. Remedy: Correct the parameter assignment. |
| A50010 (F) PNCOMM BOARD: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration for the Communication Board. Various causes related to IP configuration, station names, or DHCP. Remedy: Check and correct the required interface configuration, then activate it. Or reconfigure the station via commissioning software. |
| A50011 (F) EtherNetIP/COMM BOARD: configuration error | Cause: An EtherNet/IP controller attempts to establish a connection using an incorrect configuring telegram. The telegram length does not match. Remedy: Check the set telegram length. |
| A50020 (F) PNCOMM BOARD: Second controller missing | Cause: The PROFINET function “Shared Device” has been activated, but only one controller is present. Remedy: Check the configuration of the PROFINET controllers. |