Siemens G220 Drive Fault Codes:
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| F01000 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01001 FloatingPoint exception | Cause: An exception occurred for an operation with the FloatingPoint data type. The error can be caused by the basic system or a technology function. 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. Example: xxxx = 000B hex = 11 dec (Checksum error). The firmware download may have been caused by a loss of connection to the firmware file. Specific values: 11: Checksum error. 15: File content not accepted. 18: Firmware version too old. 19: Firmware version not suitable for hardware. 101: No response from component. 139: Only new boot loader loaded. 140: Firmware file not available. 141: Inconsistent file length. 142: Component mode not changed. 156: Selected component not available. 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 converter. Alarm value (r2124, interpret decimal): Component number of the DRIVE-CLiQ component. Remedy:
|
| 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). Alarm value (r2124, interpret decimal): Component number of the DRIVE-CLiQ component. Note: For a component number = 1, a POWER ON of the Control Unit is required. Remedy:
|
| A01009 (N) Control Unit overtemperature | Cause: The temperature (r0037[0]) of the converter has exceeded the specified limit value. Remedy:
Note: The alarm is automatically withdrawn once the limit value has been fallen below. |
| F01011 (N) Download interrupted | Cause: The project download was interrupted. Fault value (r0949, interpret decimal): 1: The user prematurely interrupted the project download. 2: The communication cable was interrupted (e.g. cable breakage, cable withdrawn). 3: The project download was prematurely exited by the commissioning tool. 100: Different versions between the firmware version and project files loaded from memory card. Note: The response is “first commissioning”. Remedy:
|
| F01014 Topology: DRIVE-CLiQ component property changed | Cause: The properties of the DRIVE-CLiQ component have fundamentally changed. Fault value (r0949, interpret hexadecimal): Component number. Remedy:
|
| F01015 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01016 (F) Firmware changed | Cause: At least one firmware file in the directory was illegally changed on the non-volatile memory (memory card/device memory) with respect to the version when shipped from the factory. Alarm value (r2124, interpret decimal): 0: Checksum of one file is incorrect. 1: File missing. 2: File too many. 3: Incorrect firmware version. 4: Incorrect checksum of the backup file. Remedy:
|
| A01017 Component lists changed | Cause: The memory card has a defective file. Alarm value (r2124, interpret decimal): xyz dec: x = problem, y = file name x = 1: file checksum is incorrect. x = 2: error when parsing the file. y = 1 to 30: Represents specific system files (e.g. MOTARM.ACX, BEARING.ACX). Remedy:
|
| F01018 Runup has been interrupted several times | Cause: Module booting was interrupted several times. As a consequence, the module boots with the factory setting. Possible reasons: Power supply interrupted, CPU crashed, Parameterization invalid. Remedy:
|
| A01019 Writing to the removable data medium unsuccessful | Cause: The write access to the removable data medium was unsuccessful. Remedy:
|
| A01020 Writing to RAM disk unsuccessful | Cause: A write access to the internal RAM disk was unsuccessful. Remedy:
|
| F01023 Software timeout (internal) | Cause: An internal software timeout has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01030 Sign-of-life failure for master control | Cause: For active PC master control of the PC, no sign-of-life was received within the monitoring time. The master control was returned to the drive. Remedy:
|
| A01032 (F) All parameters must be saved | Cause: Data backup is incomplete. The partially saved parameters are not loaded the next time the system runs up. Alarm value (r2124, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01033 Units changeover: Reference parameter value invalid | Cause: When changing over the units to the referred representation type, it is not permissible for any of the required reference parameters to be equal to 0.0. Fault value (r0949, parameter): Reference parameter whose value is 0.0. Remedy:
|
| F01034 Units changeover: Calculation parameter values after reference value change unsuccessful | Cause: The change of a reference parameter meant that for an involved parameter the selected value was not able to be re-calculated in the per unit representation. Fault value (r0949, parameter): Parameter whose value was not able to be re-calculated. Remedy:
|
| A01035 (F) ACX: Parameter backup file corrupted | Cause: When the converter runs up, no complete data set was found from the parameter backup files. It is possible that the backup was interrupted by switching off or withdrawing the memory card. Alarm value (r2124): ddccbbaa hex. aa = 01: Power up without data backup. Drive in factory setting. aa = 02: Last available backup loaded. Check parameterization. Remedy:
|
| F01036 (A) Parameter backup file missing | Cause: When loading the device parameterization, a parameter backup file cannot be found. Remedy:
|
| F01038 (A) Loading the parameter backup file unsuccessful | Cause: An error has occurred when loading parameter backup files from the non-volatile memory. Remedy:
|
| F01039 (A) Writing to the parameter back-up file unsuccessful | Cause: Writing to at least one parameter backup file in the non-volatile memory was unsuccessful. – File has “read only” attribute. – Insufficient free memory. – Non-volatile memory is defective. Remedy:
|
| F01041 Parameter save necessary | Cause: Defective or missing files were detected on the memory card when booting. Fault value (r0949, interpret decimal): 1: Source file cannot be opened. 2: Source file cannot be read. 3: Target directory cannot be set up. 4: Target file cannot be set up/opened. 5: Target file cannot be written to. 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). Fault value (r0949, hexadecimal): ccbbaaaa hex. aaaa = Parameter, bb = Index, cc = fault cause. 0: Parameter number illegal. 1: Parameter value cannot be changed. 2: Lower or upper value limit exceeded. 3: Sub-index incorrect. 4: No array, no sub-index. 5: Data type incorrect. … (See manual for full list of codes 6-204) Remedy:
|
| F01043 Fatal error at project download | Cause: A fatal error was detected when downloading a project using the commissioning tool. Fault value (r0949, interpret decimal): 1-24: Various internal errors (e.g. device status, topology mismatch, drive object errors). Remedy:
|
| F01044 Descriptive data error | Cause: An error was detected when loading the descriptive data saved in the non-volatile memory. Remedy:
|
| A01045 Configuring data invalid | Cause: An error was detected when evaluating the parameter files (.ACX) saved in the non-volatile memory. Alarm value (r2124): Only for internal Siemens troubleshooting. Remedy:
|
| A01049 It is not possible to write to file | Cause: It is not possible to write to a write-protected parameter backup file. Alarm value (r2124): Number drive object. Remedy:
|
| F01050 Memory card and device incompatible | Cause: The memory card and the device type do not match (e.g. a memory card for SINAMICS S is inserted in SINAMICS G). Remedy:
|
| F01054 System limit exceeded | Cause: At least one system overload has been identified. Fault value: 1 (Computing time load too high), 5 (Peak load too high). Remedy:
|
| F01068 Data memory memory overflow | Cause: The utilization for a data memory area is too large. Fault value indicates which high-speed data memory is overloaded. Remedy:
|
| A01069 Parameter backup and device incompatible | Cause: The parameter backup on the memory card and the drive unit do not match. The module boots with factory settings. Remedy:
|
| F01070 Project/firmware is being downloaded to the memory card | Cause: An upgrade was initiated. While this fault is active, do not switch off the converter. Caution: Switching off may destroy the file system. Remedy:
|
| F01072 Memory card restored from the backup copy | Cause: The converter was switched off while writing to the memory card. The visible partition became defective and was restored from the backup copy. Remedy:
|
| A01073 (N) POWER ON required for backup copy on memory card | Cause: The parameter assignment on the visible partition has changed. To update the backup copy, a POWER ON is required. Remedy:
|
| F01082 Parameter error when running up from data backup | Cause: Parameterizing errors detected (e.g. incorrect parameter value). Fault value (r0949): ccbbaaaa hex (same format as F01042). Remedy:
|
| A01100 Memory card withdrawn | Cause: The memory card was withdrawn during operation. Notice: It is not permissible to withdraw under voltage. Remedy:
|
| F01105 (A) Insufficient memory | Cause: The functionality on this converter is too extensive (too many drives, functions, data sets, etc). Remedy:
|
| F01107 Save to memory card unsuccessful | Cause: A data save in the non-volatile memory failed. – Memory defective or insufficient space. Remedy:
|
| F01112 Power unit not permissible | Cause: The connected power unit cannot be used together with this converter. Remedy:
|
| F01120 (A) Terminal initialization has failed | Cause: An internal software error occurred while the terminal functions were being initialized. Remedy:
|
| F01122 (A) Frequency at the measuring probe input too high | Cause: The frequency of the pulses at the measuring probe input is too high. Fault value indicates specific DI/DO pin. Remedy:
|
| F01151 Number of drive objects of a category exceeded | Cause: The maximum permissible number of drive objects of a category was exceeded. Remedy:
|
| F01205 Time slice overflow | Cause: Insufficient processing time is available for the existing topology. Remedy:
|
| F01250 EEPROM incorrect read-only data | Cause: Error when reading the read-only data of the EEPROM in the converter. Remedy:
|
| A01251 EEPROM incorrect read-write data | Cause: Error when reading the read-write data of the EEPROM in the converter. Remedy:
|
| F01255 Option Board EEPROM read-only data error | Cause: Error when reading the read-only data of the EEPROM in the Option Board. Remedy:
|
| A01256 Option Board EEPROM read-write data error | Cause: Error when reading the read-write data of the EEPROM in the Option Board. Remedy:
|
| F01303 Component does not support the required function | Cause: A function requested by the converter is not supported by a DRIVE-CLiQ component. Fault value (r0949, interpret decimal):
Remedy:
|
| 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. Alarm value (r2124, interpret decimal): Component number of the DRIVE-CLiQ component involved. Remedy: Repeat the firmware update by switching off the device and switching on again. |
| A01306 Firmware of the DRIVE-CLiQ component being updated | Cause: Firmware update is active for at least one DRIVE-CLiQ component. Alarm value (r2124, interpret decimal): Component number of the DRIVE-CLiQ component. Remedy: Not necessary. This alarm is automatically withdrawn after the firmware update has been completed. |
| 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. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex:
Note: Component class and connection number are described in F01375. 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” (p0125, p0145, p0155, p0165). Note: This is the only message that is displayed for a deactivated component. Remedy: The alarm is automatically withdrawn for the following actions:
|
| A01318 Deactivated signal interconnections available | Cause: This alarm is used in the following cases:
Remedy: Deactivate the drive object again. |
| A01319 Inserted component not initialized | Cause: Initialization is required for at least one inserted component. This is only possible if the pulse inhibit is active on all drive objects. Remedy: Activate pulse inhibit for all drive objects. |
| F01325 Topology: Component number not included in target topology | Cause: The component referenced in a data set (e.g. PDS, MDS or EDS) is not contained in the target topology. Fault value (r0949, interpret decimal): Component number. Remedy: Establish consistency between the topology and data set configuration. |
| A01330 Topology: Quick commissioning not possible | Cause: Unable to carry out a quick commissioning. The existing actual topology does not fulfill the requirements. Alarm value (r2124, interpret hexadecimal) ccccbbaa hex:
Remedy:
|
| A01331 Topology: At least one component not assigned to a converter | Cause: At least one component is not assigned to a converter.
Alarm value: Component number of the unassigned component. Remedy: Assign this component to a converter. |
| F01341 Topology: Maximum number of DRIVE-CLiQ components exceeded | Cause: Too many DRIVE-CLiQ components were defined in the actual topology. Note: Pulse enable is withdrawn and prevented. Remedy:
|
| F01354 Topology: Actual topology indicates an illegal component | Cause: The actual topology indicates at least one illegal component. Fault value (r0949, interpret hexadecimal) yyxx hex:
Note: Pulse enable is prevented. Remedy: Remove the illegal components and restart the system. |
| F01356 Topology: There is a defective DRIVE-CLiQ component | Cause: The actual topology indicates at least one defective DRIVE-CLiQ component. Fault value (r0949, interpret hexadecimal) zzyyxx hex:
Note: Pulse enable is withdrawn and prevented. Remedy: Replace the defective component and restart the system. |
| F01357 Topology: Two converters identified on the DRIVE-CLiQ line | Cause: In the actual topology, 2 converters are connected with one another through DRIVE-CLiQ. As standard, this is not permitted. Fault value (r0949) details connection and component numbers. Note: Pulse enable is withdrawn and prevented. Remedy: Remove the connection to the second converter and restart. |
| 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. Alarm value (r2124) details the connection number and component number where the terminator is missing. 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. Fault value (r0949, interpret hexadecimal) ccccbbaa hex (aa = fault cause):
Note: The drive system is no longer booted. Remedy:
|
| A01361 Topology: Actual topology contains SINUMERIK and SIMOTION components | Cause: The detected actual topology contains SINUMERIK and SIMOTION components. The drive system is no longer booted. Alarm value details:
Remedy:
|
| A01362 Topology: Topology rule(s) broken | Cause: At least one topology rule for the SINAMICS S120 Combi has been broken. Alarm value (r2124) indicates which rule (1-19) has been violated (e.g., S120 Combi wiring to NCU, Module connections, specific port usage). 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. Fault value (r0949) details the connection and component numbers involved in the ring. Remedy: Output the fault value and remove the specified connection. Note: Use the commissioning tool’s topology view for diagnostics. |
| F01380 Topology: Actual topology EEPROM defective | Cause: When detecting the actual topology, a component with a defective EEPROM was detected. Fault value (r0949) identifies the component with the defective EEPROM. Remedy: Output the fault value and remove the defected component. |
| A01382 Topology: Sensor Module incorrectly inserted | Cause: The topology comparison has detected a Sensor Module in the actual topology that has been incorrectly inserted with respect to the target topology. The drive system is no longer booted. 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 with respect to the target topology. The drive system is no longer booted. Remedy: Adapting topologies:
|
| 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 with respect to the target topology. The drive system is no longer booted. Remedy: Adapting topologies:
|
| A01385 Topology: Controller Extension incorrectly inserted | Cause: The topology comparison has detected a controller extension 32 (CX32) in the actual topology that has been incorrectly inserted with respect to the target topology. The drive system is no longer booted. Remedy: Adapting topologies:
|
| 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 with respect to the target topology. The drive system is no longer booted. Remedy: Adapting topologies:
|
[Preceding Fault] Topology: Controller Extension 32 (CX32) incorrectly inserted | Cause: The topology comparison has detected a controller extension 32 (CX32) in the actual topology that has been incorrectly inserted with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: dd = connection number (%4) cc = component number (%3) bb = component class (% 2) aa = component number of the incorrectly inserted component (% 1) Affected Connections (examples):
Remedy: Adapting topologies:
Note: Under “Topology –> Topology view” the commissioning tool offers improved diagnostics capability. |
A01386 Topology: DRIVE-CLiQ component incorrectly inserted Component: %1, to %2, %3, connection: %4 | Cause: The topology comparison has detected a DRIVE-CLiQ component in the actual topology that has been incorrectly inserted with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: dd = connection number (%4) cc = component number (%3) bb = component class (% 2) aa = component number of the incorrectly inserted component (% 1) Note: The component is described in dd, cc and bb. Component class and connection number are described in F01375. Remedy: Adapting topologies:
|
A01389 Topology: Motor with DRIVE-CLiQ incorrectly inserted Component: %1, to %2, %3, connection: %4 | Cause: The topology comparison has detected a motor with DRIVE-CLiQ in the actual topology that has been incorrectly inserted with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: dd = connection number (%4) cc = component number (%3) bb = component class (% 2) aa = component number of the incorrectly inserted component (% 1) Remedy: Adapting topologies:
|
A01416 Topology: Component additionally inserted Component: %1, to %2, %3, connection: %4 | Cause: The topology comparison has detected a component in the actual topology which is not specified in the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: dd = component class (% 2) cc = connection number (%4) bb = component class of the additional component (%1) aa = component number (%3) Remedy: Adapting topologies:
|
A01420 Topology: Component different Component: %1, target: %2, actual: %3, difference: %4 | Cause: The topology comparison has detected differences in the actual topology and target topologies in the electronic rating plate. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: aa = component number (%1) bb = component class of the target topology (%2) cc = component class of the actual topology (%3) dd = difference (%4) Difference Values (%4 / dd):
Remedy: Adapting topologies:
|
A01425 Topology: Serial number different Component: %1, %2, differences: %3 | Cause: The topology comparison has detected differences in the actual and target topologies in relation to one component. The serial number is different. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: dd = reserved cc = number of differences (%3) bb = component class (% 2) aa = component number (%1) Remedy: Adapting topologies:
|
A01428 Topology: Incorrect connection used Component: %1, %2, connection (actual): %3, connection (target): %4 | Cause: The topology comparison has detected differences in the actual and target topologies in relation to one component. For a component, another connection was used. The different connections of a component are described in the alarm value. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: dd = connection number of the target topology (%4) cc = connection number of the actual topology (%3) bb = component class (% 2) aa = component number (%1) Remedy: Adapting topologies:
|
F01451 Topology: Target topology is invalid Message value: %1 | Cause: An error was detected in the target topology. The target topology is invalid. Fault value (r0949, interpret hexadecimal): ccccbbaa hex: cccc = index error, bb = component number, aa = fault cause
Remedy: Download the target topology again using the commissioning tool. |
A01481 (N) Topology: Motor Module not connected Component: %1, to %2, %3, connection: %4 | Cause: The topology comparison has detected a Motor Module that is missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: dd = connection number (%4) cc = component number (%3) bb = component class (% 2) aa = component number of the component that has not been inserted (% 1) Remedy: Adapting topologies:
|
A01482 Topology: Sensor Module not connected Component: %1, to %2, %3, connection: %4 | Cause: The topology comparison has detected a Sensor Module that is missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: dd = connection number (%4) cc = component number (%3) bb = component class (% 2) aa = component number of the component that has not been inserted (% 1) Remedy: Adapting topologies:
|
A01483 Topology: Terminal Module not connected Component: %1, to %2, %3, connection: %4 | Cause: The topology comparison has detected a Terminal Module that is missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: dd = connection number (%4) cc = component number (%3) bb = component class (% 2) aa = component number of the component that has not been inserted (% 1) Remedy: Adapting topologies:
|
A01484 Topology: DRIVE-CLiQ Hub Module not connected Component: %1, to %2, %3, connection: %4 | Cause: The topology comparison has detected a DRIVE-CLiQ Hub Module missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: dd = connection number (%4) cc = component number (%3) bb = component class (% 2) aa = component number of the component that has not been inserted (% 1) Remedy: Adapting topologies:
|
A01485 Topology: Controller Extension not connected Component: %1, to %2, %3, connection: %4 | Cause: (Details not provided in screenshot, likely similar to previous modules: Controller Extension missing in actual topology). Remedy: (Details not provided in screenshot, likely similar to previous modules: Insert component, adapt project, check hardware). |
| A01484 (Inferred) Topology: DRIVE-CLiQ Hub Module not connected | Cause: The topology comparison has detected a DRIVE-CLiQ Hub Module missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex. (dd = connection number %4, cc = component number %3, bb = component class %2, aa = component number %1). See list of connection numbers (X205, X400… X507) in manual. Remedy: Adapting topologies:
Check the hardware:
|
| A01485 Topology: Controller Extension not connected | Cause: The topology comparison has detected a Control Extension (CX32) missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex. dd = connection number (%4), cc = component number (%3), bb = component class (%2), aa = component number (%1). Explanation of Message Values: %2 (Component Class): 0=Unknown, 1=Control Unit, 2=Motor Module, 3=Line Module, 4=Sensor Module, 5=Voltage Sensing Module, 6=Terminal Module, 7=DMC Hub Module, 8=Controller Extension, 9=Filter module, 10=Hydraulic Module, 49=DRIVE-CLiQ component, 50=Option slot, 60=Encoder, 70=DRIVE-CLiQ motor, 71=Hydraulic cylinder, 72=Hydraulic valve, 80=Motor. %4 (Connection Number): 0=Port 0, 1=Port 1 … 9=Port 9, 10=X100 … 15=X105, 20=X200 … 24=X204, 25=X205, 40=X400, 41=X401, 42=X402, 50=X500 … 57=X507. Remedy: Adapting topologies:
Check the hardware:
|
| A01486 Topology: DRIVE-CLiQ component not connected | Cause: The topology comparison has detected a DRIVE-CLiQ component missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex. Explanation of Message Values: %2 (Component Class): 0=Unknown, 1=Control Unit, 2=Motor Module, 3=Line Module, 4=Sensor Module, 5=Voltage Sensing Module, 6=Terminal Module, 7=DMC Hub Module, 8=Controller Extension, 9=Filter module, 10=Hydraulic Module, 49=DRIVE-CLiQ component, 50=Option slot, 60=Encoder, 70=DRIVE-CLiQ motor, 71=Hydraulic cylinder, 72=Hydraulic valve, 80=Motor. %4 (Connection Number): See standard connection list (e.g., 0-9 for Ports, 10-15 for X100-X105, etc.). Remedy: Adapting topologies:
Check the hardware:
|
| A01487 Topology: Option slot component not inserted | Cause: The topology comparison has detected an option slot component missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex. Explanation of Message Values: %2 (Component Class): 0=Unknown, 1=Control Unit, 2=Motor Module, 3=Line Module, 4=Sensor Module, 5=Voltage Sensing Module, 6=Terminal Module, 7=DMC Hub Module, 8=Controller Extension, 9=Filter module, 10=Hydraulic Module, 49=DRIVE-CLiQ component, 50=Option slot, 60=Encoder, 70=DRIVE-CLiQ motor, 71=Hydraulic cylinder, 72=Hydraulic valve, 80=Motor. %4 (Connection Number): See standard connection list. Remedy: Adapting topologies:
Check the hardware:
|
| A01489 Topology: motor with DRIVE-CLiQ not connected | Cause: The topology comparison has detected a motor with DRIVE-CLiQ missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex. Explanation of Message Values: %2 (Component Class): 0=Unknown, 1=Control Unit, 2=Motor Module, 3=Line Module, 4=Sensor Module, 5=Voltage Sensing Module, 6=Terminal Module, 7=DMC Hub Module, 8=Controller Extension, 9=Filter module, 10=Hydraulic Module, 49=DRIVE-CLiQ component, 50=Option slot, 60=Encoder, 70=DRIVE-CLiQ motor, 71=Hydraulic cylinder, 72=Hydraulic valve, 80=Motor. %4 (Connection Number): See standard connection list. Remedy: Adapting topologies:
Check the hardware:
|
| A01507 (F, N) Signal interconnections to inactive objects available | Cause: There are signal interconnections to an inactive/inoperable drive object. Alarm value (r2124, interpret decimal): Number of signal interconnections found to inactive drive objects. Remedy: Make the non-operational drive object active/operational again (re-insert or activate components). |
| A01508 Signal interconnections to inactive objects exceeded | Cause: The maximum number of signal interconnections (signal sinks) when deactivating a drive object was exceeded. Remedy: Not necessary. |
| F01510 Signal source is not float type | Cause: The required signal source has the incorrect data type. This interconnection is not established. Fault value (r0949, interpret decimal): Parameter number to which an interconnection should be made. Remedy: Interconnect this signal sink with a signal source, data type float. |
| F01511 (A) Signal interconnection with different scaling | Cause: The requested signal interconnection was established. However, a conversion is made between the signal source and signal sink via the reference values. The signal source has a different standard unit than the signal sink. Fault value (r0949, interpret decimal): Parameter number of the signal sink. Remedy: Not necessary. |
| F01512 No scaling available | Cause: An attempt was made to determine a conversion factor for a scaling that does not exist. Fault value (r0949, interpret decimal): Unit (e.g. corresponding to SPEED) for which an attempt was made to determine a factor. Remedy: Apply scaling or check the transfer value. |
| F01513 (N, A) Signal interconnection cross DO with different scaling | Cause: The requested signal interconnection was established. However, a conversion is made between the signal source and signal sink via the reference values. An interconnection is made between different drive objects and the signal source has different standard units than the signal sink or the standard units are the same but the reference values are different. Fault value (r0949, interpret decimal): Parameter number of the signal sink. Remedy: Not necessary. |
| A01514 (F) Error when writing during a reconnect | Cause: During a reconnect operation (e.g. while booting or downloading) a parameter was not able to be written to. Example: When writing to a signal sink with double word format (DWORD), in the second index, the memory areas overlap. Alarm value (r2124, interpret decimal): Parameter number of the signal sink. Remedy: Not necessary. |
| F01515 (A) 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. |
| A01550 Security: Drive data encryption invalid | Cause: The password for drive data encryption (DDE) does not match the password configured in the converter or no password was configured. The DDE password protects sensitive data on the SD card. It is not possible to transfer the data backup from the SD card. Remedy: To be able to restore the data backup on the SD card, the DDE password must correspond to the password that was originally configured for the data backup in the original converter:
If the data backup on the SD card is not be used:
|
| A01590 (F) Drive: Motor maintenance interval expired | Cause: The selected service/maintenance interval for this motor was reached. Alarm value (r2124, interpret decimal): Motor data set number. See also: p0650, p0651. Remedy: Carry out service/maintenance and reset the service/maintenance interval (p0651). |
| C01600 SI: STO self test failed | Cause: The “Safety Integrated” function integrated in the drive has identified a fault in the self test of the switch-off signal path, and has initiated an STO (Safe Torque Off). Fault value (r60049, interpret decimal): 1005: STO active, although STO not selected and there is no internal STO active. 1010: STO inactive, although STO is selected or an internal STO is active. 1015: The self test was unsuccessful in operation. 1016: Error in the communication path for brake/F-DI/F-DO/STO Remedy:
|
| C01601 SI: Communication error with OM-SMT | Cause: An error has occurred in the communication with the Option Module Safe Motor Temperature (OM-SMT). Note: This fault results in an STO (Safe Torque Off). Remedy:
|
| C01603 SI: Module temperature – limit value exceeded | Cause: A safe monitoring function has detected that the module temperature has exceeded a limit value. STO (Safe Torque Off) was initiated to maintain the safe state. Remedy:
|
| F01604 SI: Safety EEPROM data error | Cause: Safety relevant EEPROM data are not correct. This message results in an STO (Safe Torque Off). Remedy: Replace the module. |
| A01605 SI: Checksum error has occurred | Cause: A checksum error (CRC error) has occurred in the converter program memory. Remedy:
|
| A01637 (F) SI: Safety configuration not protected | Cause: Safety configuration is not protected using UMAC (User Management and Access Control). Remedy: Activate UMAC and assign the rights for changing the “Edit Safety Integrated application” safety configuration to a specific user that is saved with user name and password. |
| A01641 (F, N) SI: Component exchange identified and save necessary | Cause: “Safety Integrated” has identified that a component has been replaced. Bits: 3: It was identified that OM-SMT has been replaced. 4: It was identified that the Sensor Module has been replaced. 5: It was identified that the sensor has been replaced. No additional stop response is initiated. When safety functions are active, after a component has been replaced it is necessary to carry out a partial acceptance test. Remedy:
|
| A01644 SI: OM-SMT connected and SMT not enabled | Cause: An OM-SMT is connected; however, the SMT function is not enabled. Remedy: Release the SMT function with p9604.22. |
| C01645 SI: Parameterizing error OM-SMT | Cause: An error occurred when parameterizing the Option Module Safe Motor Temperature (OM-SMT). Fault value (r60049, interpret decimal): 1: Function SMT was enabled, although no OM-SMT is connected (p9604.22 = 1). 2: Function SMT was enabled, although this function is not available in this software release. 3: Sending safety communication timeout information to the OM-SMT unsuccessful. Remedy: For fault value = 1: – Connect OM-SMT. – Deactivate function SMT (p9604.22 = 0). For fault value = 2, 3: – Upgrade the converter firmware to a later version. |
| F01646 SI: Change logbook | Cause: The saved functional safety checksum (r9780[0]) or hardware-related safety checksum (r9780[1]) differs from the safety checksum calculated when running up or a previously calculated safety checksum was not found. Fault value (r0949, interpret decimal): 1: The safety logbook has identified that a functional safety checksum has changed. 2: The safety logbook has identified that a hardware-related safety checksum has changed. Remedy: For fault value = 1: Carry out an acceptance test and generate an acceptance report. For fault value = 2: Carry out the function checks for the modified hardware and generate an acceptance report. |
| C01647 SI: PROFIsafe PLC configuring not the same as the parameterization | Cause: The drive has identified a difference between the PROFIsafe configuring in the F-PLC and the parameterization in SINAMICS. Message value (r60049, interpret decimal): 1: The PROFIsafe telegram number in the F-PLC configuration is not identical with the value in p9611. 2: The PROFIsafe monitoring time F_WD_Time in the F-PLC configuration is not identical with the value in p9614. Remedy:
|
| C01648 SI: PROFIsafe communication error | Cause: The drive has identified a PROFIsafe communication error. Message value (r60049, interpret decimal): 6000…6166: PROFIsafe message values. 6064…6076: Error when evaluating F parameters. 6064: Destination address and PROFIsafe address are different. 6065: Destination address not valid. (See manual for full list of sub-codes 6066-6166). Remedy: For message value = 6064: Check the setting of the value in the F parameter F_Dest_Add at the PROFIsafe device. For message value = 6065: Check the setting of the value in the F parameter F_Dest_Add. Destination address cannot be 0 or FFFF. (See manual for detailed remedies for codes 6066-65535). |
| C01649 SI: Internal software error | Cause: An internal error has occurred in the Safety Integrated software. Note: This message results in an STO (Safe Torque Off) that cannot be acknowledged. Remedy:
|
| F01650 SI: Acceptance test required | Cause: The drive-integrated “Safety Integrated” function requires an acceptance test. Message value (r0949): 2003: Acceptance test is required as a safety parameter has been changed. Remedy: Carry out an acceptance test and generate an acceptance report. |
| C01652 SI: Monitoring clock cycle not permissible | Cause: One of the Safety Integrated monitoring clock cycles is not permissible. Message value (r60049): 100: No matching monitoring clock cycle (p9500) was able to be found. 107: The actual value sensing clock cycle (p9511) is not an integer multiple of the sampling time of the current controller. 108: The parameterized actual value sensing clock cycle (p9511) cannot be set on this component. 111: The monitoring clock cycle (p9500) is not an integer multiple of the sampling time of the current controller. Remedy:
|
| C01653 SI: PROFIBUS/PROFINET configuration error | Cause: There is a PROFIBUS/PROFINET configuration error for using Safety Integrated monitoring functions with a higher-level control (F-PLC). Fault value (r60049): 200, 220, 230, 231, 300, 320, 330, 331, 400 (Configuration mismatches regarding safety slots). Remedy:
|
| A01654 (F, N) SI: PROFIsafe configuration different | Cause: The configuration of a PROFIsafe telegram in the higher-level control (F-PLC) does not match the parameterization in the drive. Alarm value (r2124): 1: PROFIsafe configured in PLC but not enabled in drive. 2: PROFIsafe parameterized in drive but not configured in PLC. Remedy:
|
| C01657 SI: PROFIsafe telegram number invalid | Cause: The PROFIsafe telegram number set in p9611 is not valid. Remedy: Check the telegram number setting (p9611). |
| C01658 SI: PROFIsafe telegram number not equal | Cause: The PROFIsafe telegram number in p9611 differs from the configured PROFIsafe telegram number in the F-PLC. Remedy: Align the telegram number in p9611 with the PROFIsafe telegram number in the F-PLC. |
| F01661 SI: Simulation of the safety inputs active | Cause: Simulation of the safety inputs is active (p9604.15 = 1). Remedy: Deactivate the simulation of the safety inputs (p9604.15 = 0). |
| C01657 SI: PROFIsafe telegram number invalid | Cause: The PROFIsafe telegram number set in p9611 is not valid. When PROFIsafe is enabled (p9603.1 = 1), then a telegram number greater than zero must be entered in p9611. Remedy:
|
| C01658 SI: PROFIsafe telegram number not equal | Cause: The PROFIsafe telegram number in p9611 differs from the configured PROFIsafe telegram number in the F-PLC. Remedy:
|
| F01661 SI: Simulation of the safety inputs active | Cause: The simulation of the digital inputs is active (p0795). It is not permissible that safety inputs are simulated. Fault value (r0949, interpret binary): The displayed bits indicate which digital inputs must not be simulated. Remedy:
|
| C01668 SI: Checksum error safety monitoring functions | Cause: The actual checksum calculated by the drive and entered in r10098 via the safety-relevant parameters does not match the reference checksum saved in p10099. Safety-relevant parameters have been changed or a fault is present. Remedy:
|
| C01670 SI: invalid Sensor Module configuration | Cause: The configuration of a Sensor Module used for Safety Integrated is not permissible. Fault value (r60049): 1: Encoder data set not valid/assigned. 2: Encoder not parameterized for Safety. 4: Communication error with encoder. 5-16: Encoder parameters/bits invalid. 17: Encoder not compatible (accuracy/speed mismatch). 20: DQi encoder offset changed. 21: Timer for effectivity test error. 22: Encoder type not permitted for Safety. Remedy:
|
| C01671 SI: Parameterization actual value acquisition incorrect | Cause: The parameterization of the actual value sensing for Safety Integrated is incorrect. Fault value (r60049): yyyy = 0: No additional info. xxxx = 9522: The gear stage was set too high. Remedy:
|
| C01673 SI: Safe encoder assignment incorrect | Cause: The existing actual value sensing configuration is incorrect. Fault value (r60049): 1: A Safety Integrated function requires an encoder, but no encoder data set or incorrect set is configured. Remedy:
|
| C01674 SI: Safety function not supported by PROFIsafe telegram | Cause: The monitoring function enabled in p9604 is not supported by the currently set PROFIsafe telegram (p9611). Bit 3=1: SS1E not supported. Bit 5=1: SS2E not supported. Bit 9=1: SLS limit transfer not supported. Bit 30=1: Transfer of F-DI via PROFIsafe not supported. Remedy:
|
| C01676 SI: Parameterization of the failsafe inputs not permissible | Cause: When simultaneously controlled via terminal (p9603.0 = 1) and PROFIsafe (p9603.1 = 1): – Only the failsafe digital input F-DI 0 (r10071.0) may be selected. – Only STO (c10022) / SS1 (c10023) may be interconnected. Remedy:
|
| C01677 SI: Incorrect onboard F-I/O parameter value | Cause: The parameter cannot be parameterized with this value. Fault value (r60049): xxxx = 10000: Non-existent F-DI enabled. xxxx = 10002: Discrepancy time issues. xxxx = 10017/10018: Input filter or dark pulse length issues. xxxx = 10042: F-DO signal source invalid. Remedy:
|
| C01680 SI: Checksum error safety monitoring functions | Cause: The actual checksum over the safety-relevant parameters does not match the reference checksum last saved. Safety-relevant parameters have been changed or a fault is present. Remedy:
|
| C01681 SI: Incorrect parameter value | Cause: The parameter cannot be parameterized with this value. xxxx = 9547: Parameter rule not complied with. xxxx = 9560: Parameter must be > 0 when SS1 with SBR is activated. xxxx = 9603: Control type not permissible. xxxx = 10050: Inadmissible signal source for F-DI via PROFIsafe. Remedy:
|
| C01682 SI: Monitoring function not supported | Cause: At least one of the monitoring functions enabled in p9604 is not supported with this firmware version on this device. Remedy:
|
| C01690 SI: Data backup problem for the NVRAM | Cause: When saving parameters r9780, r9781 and r9782 (Safety logbook), an error occurred. 1: No physical NVRAM. 2: No free memory space. Remedy:
|
| A01698 (F) SI: 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:
|
| C01700 SI: STO (Safe Torque Off) initiated | Cause: The drive is stopped using STO (Safe Torque Off). Possible causes: Subsequent response to messages C01706, C01714, C01715, C01716. Remedy:
|
| C01701 SI: SS1 (Safe Stop 1) initiated | Cause: The drive is stopped using SS1 (Safe Stop 1) (braked along the OFF3 down ramp). After time expire or speed threshold, STO is initiated. Possible causes: C01707, C01711, C01714, C01715, C01716. Remedy:
|
| C01706 SI: SAM/SBR limit exceeded | Cause: The safety functions SAM (Safe Acceleration Monitor) / SBR (Safe Brake Ramp) have identified an error. The drive is shut down by message C01700 (STO). Remedy:
|
| C01707 SI: 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 message C01701 “SI: SS1 initiated”. Remedy:
|
| C01711 SI: SCF (Safety Channel Failure) initiated | Cause: The drive has detected an error in a safe monitoring function and has initiated SCF. Monitoring functions are no longer reliable. Remedy:
|
| C01714 SI: Safely-Limited Speed exceeded | Cause: The drive has moved faster than that specified by the velocity limit value (p9531). 100: SLS1 exceeded. 200: SLS2 exceeded. Remedy:
|
| C01716 SI: Tolerance for Safe Direction exceeded | Cause: The tolerance for function SDI (Safe Direction) was exceeded. 0: Tolerance for “SDI positive” exceeded. 1: Tolerance for “SDI negative” exceeded. Remedy:
|
| C01730 SI: Reference block for dynamic Safely-Limited Speed invalid | Cause: The reference block transferred via PROFIsafe is negative. The drive is stopped by the configured stop response. Remedy:
|
| C01750 SI: Hardware fault safety-related encoder | Cause: The encoder used for safety-relevant motion monitoring signals a hardware fault. This fault results in STO. Remedy:
|
| C01751 SI: Effectivity test error safety-related encoder | Cause: The DRIVE-CLiQ encoder signals an error for the internal encoder effectivity tests. This message results in an SCF. Remedy:
|
| C01753 SI: Fault safety-relevant encoder | Cause: The encoder signals a fault. 1012: Plausibility violation. 1021: Cyclic communication failure. 1022: Sign-of-life error. 1031: Data transfer error (CRC). Remedy:
|
| C01754 SI: Fault safety-relevant actual value acquisition | Cause: The actual value sensing for safe motion monitoring signals an error. 1039: Converting position on load side exceeds data format. Remedy:
|
| C01755 SI: Encoder limit frequency exceeded | Cause: 1: The actual velocity exceeds the encoder limit frequency of 500 kHz. Remedy:
|
| C01769 SI: Error for data cross-check | Cause: Difference detected between two monitoring channels (SCF initiated). One of the monitoring functions no longer functions reliably. Remedy:
|
| C01770 SI: Fault of the failsafe inputs | Cause: The failsafe digital inputs (F-DI) have a fault condition. 1: Discrepancy error (state between channels different too long). 2: Too many switching operations. 3: Test pulse error. 4: Internal software error. Remedy:
|
| C01771 SI: Fault of the failsafe outputs | Cause: The failsafe digital outputs (F-DO) have a fault condition. 1: Discrepancy error. 2: Feedback signal fault. 3: Test pulse error. 4: Overcurrent detected. Remedy:
|
| C01793 SI: Internal safety message buffer is full | Cause: Too many safety messages have occurred within a short time so that some have not been able to be displayed. Remedy:
|
| A01796 (F, N) SI: Wait for communication | Cause: The drive waits for communication to be established to execute the safety-relevant functions. 3: Wait for communication to PROFIsafe F-Host. Remedy:
|
| C01799 SI: Acceptance test mode active | Cause: The acceptance test mode is active. The setpoint velocity limiting is deactivated (r9733). Remedy:
|
| F01800 (A) DRIVE-CLiQ: Hardware/configuration error | Cause: A DRIVE-CLiQ connection fault has occurred. 10: Loss of connection (e.g. cable withdrawn). 11: Repeated faults detected. 12: Connection detected but node ID exchange failed (defective component). Remedy:
|
| A01839 DRIVE-CLiQ diagnostics: cable fault to the component | Cause: The fault counter (r9936) to monitor the DRIVE-CLiQ connections 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. 2: Too many PZD data words. 3: Uneven number of bytes. 502: PROFIsafe telegram does not match. Remedy:
|
| A01902 PB/PN: Isochronous operation parameterization not permissible | Cause: Parameterization for isochronous operation is not permissible. Values 0-13 indicate specific timing violations (Tdp, Ti, To, Tmapc). Remedy:
|
| A01904 (F, N) PN: Controller setting of the PZD telegram rejected | Cause: A controller attempts to set a PZD telegram. The setting is not applied. 1: Project contains free telegram interconnections. 2: Controller specifies fixed/free combination. 4: Telegram cannot be set due to drive configuration. Remedy:
|
| A01905 (N) PN: Controller setting to activate the channel diagnostics rejected | Cause: Controller attempted to change channel diagnostics activation but lacks function rights. 1: Activation attempts. 2: Deactivation attempts. Remedy:
|
| F01910 (N, A) Fieldbus: setpoint timeout | Cause: The reception of setpoints from the fieldbus interface has been interrupted. – Bus connection interrupted. – Controller switched off or in STOP state. Remedy:
|
| F01911 (N, A) PB/PN: Isochronous operation clock cycle failure | Cause: Communication error to the higher-level control system (9). Remedy:
|
| A01905 (N) PN: Controller setting to activate the channel diagnostics rejected | Cause: A controller attempted to change the activation of the channel diagnostics. The setting is not applied as the controller does not have the function rights to make a change. Alarm value (r2124): 1: Channel diagnostics are activated. Controller attempts to deactivate them. 2: Channel diagnostics are not activated. Controller attempts to activate them. Remedy: Activate channel diagnostics in the bus configuration and check and align function rights in the drive. |
| F01910 (N, A) Fieldbus: setpoint timeout | Cause: The reception of setpoints from the fieldbus interface (PROFIBUS/PROFINET) has been interrupted. – Bus connection interrupted. – Controller switched off. – Controller set into the STOP state. Remedy: Restore the bus connection and set the controller to RUN. |
| F01911 (N, A) PB/PN: Isochronous operation clock cycle failure | Cause: The telegram to synchronize the clock cycles has failed for several bus clock cycles or in several bus clock cycles has consecutively violated the specified time grid (see bus cycle time, Tdp and Tpllw). Remedy:
|
| F01912 (N, A) PB/PN: Isochronous operation sign-of-life failure | Cause: The maximum permissible number of errors in the controller sign-of-life (isochronous operation) has been exceeded in cyclic operation. Remedy:
|
| A01925 (F) Modbus TCP: connection interrupted | Cause: The Ethernet connection to the Modbus controller is interrupted. Remedy:
|
| A01940 PB/PN: clock cycle synchronism not reached | Cause: The bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing telegram. Synchronization with the clock cycle specified by the controller was still not able to be performed. – The controller does not send an isochronous telegram, although isochronous operation was selected when configuring the bus. – The controller uses another isochronous bus clock cycle than was transferred to the device in the parameterizing telegram. Remedy:
|
| A01941 PB/PN: clock cycle signal missing when establishing bus communication | Cause: The bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing telegram. The synchronization telegram is not received. Remedy: Check the controller application and bus configuration. |
| A01943 PB/PN: clock cycle signal error when establishing bus communication | Cause: The bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing telegram. The synchronization telegram is irregularly received. – The controller sends an irregular synchronization telegram. – The controller uses another isochronous bus clock cycle than was transferred to the device in the parameterizing telegram. Remedy:
|
| A01944 PB/PN: sign-of-life synchronism not reached | Cause: The bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing telegram. Synchronization with the controller sign-of-life (STW2.12 … STW2.15) could not be completed because the sign-of-life changes differently to how it was configured in the Tmapc time grid. Remedy:
|
| F01950 (N, A) PB/PN: Isochronous operation synchronization unsuccessful | Cause: Synchronization of the internal clock cycle to the controller clock cycle has failed. The internal clock cycle exhibits an unexpected shift. Remedy: Only for internal Siemens troubleshooting. |
| F01951 Synch. application clock cycle missing | Cause: If DRIVE-CLiQ components with different application clock cycle are operated on a DRIVE-CLiQ port, then this requires synchronization with the converter. This synchronization routine was unsuccessful. Remedy:
|
| F01952 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. Remedy: Upgrade the firmware of the component specified in the fault value. |
| F01954 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). Remedy: 1. Remove the cause of a possibly active DRIVE-CLiQ error. 2. Initiate a new synchronization, e.g. as follows:
|
| A01955 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. Remedy: Carry out a POWER ON (switch-off/switch-on) for all components of the DO. |
| A01980 PN: cyclic connection interrupted | Cause: The cyclic connection to the PROFINET controller is interrupted. See also: r8936 (PN cyclic connection state). Remedy: Establish the PROFINET connection and activate the PROFINET controller in the cyclic mode. Check parameters “Name of Station” and “IP of Station”. |
| 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 is automatically withdrawn after approx. 30 seconds. Remedy: Check the configuration of the PROFINET controllers. |
| A01982 PN: second controller missing | Cause: Connections to two PROFINET controllers are expected. However, only the connection to a PROFINET controller is available or the controller is in the STOP state. – System redundancy is activated. Remedy: Check the PROFINET controller. |
| 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: Not necessary. This alarm is automatically withdrawn after switchover has been completed. |
| A01989 PN: internal cyclic data transfer error | Cause: The cyclic actual values and/or setpoints were not transferred within the specified times. Remedy: Correctly set T_io_input or T_io_output. |
| A02000 Function generator: Start not possible | Cause: The function generator has already been started. Remedy: Stop the function generator and restart again if necessary. |
| A02005 Function generator: Drive does not exist | Cause: The drive object specified for connection does not exist. Remedy: Use the existing drive object with the corresponding number. |
| A02006 Function generator: No drive specified for connection | Cause: No drive specified for connection was specified. Remedy: At least one drive to be connected must be specified. |
| A02007 Function generator: Drive not SERVO / VECTOR / DC_CTRL | Cause: The drive object specified for connection is not a SERVO, VECTOR or DC_CTRL. Remedy: Use a SERVO, VECTOR or DC_CTRL drive object with the corresponding number. |
| A02008 Function generator: Drive specified a multiple number of times | Cause: The drive object specified for connection is already specified. Remedy: Specify another drive object. |
| A02009 Function generator: Illegal mode | Cause: The selected operating mode (p1300) of the drive object is not permissible when using the function generator. Remedy: Change the operating mode for this drive object to p1300 = 20 (encoderless closed-loop speed control) or p1300 = 21 (closed-loop speed control with encoder). |
| 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: For all of the drives specified for connection, set the speed setpoints to zero. |
| 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: Set the relevant drives to zero speed before starting the function generator. |
| A02015 Function generator: Drive enable signals missing | Cause: The master control and/or enable signals are missing to connect to the specified drive. Remedy: Fetch the master control to the specified drive object and set all enable signals. |
| A02016 Function generator: Magnetizing running | Cause: Magnetizing has not yet been completed on a drive object specified for connection. Remedy: Wait for magnetizing of the motor (r0056.4). |
| A02020 Function generator: Parameter cannot be changed | Cause: This parameter setting cannot be changed when the function generator is active. Remedy:
|
| A02025 Function generator: Period too short | Cause: The value for the period is too short. Remedy: Check and adapt the value for the period. |
| 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. Remedy: Reduce pulse width. |
| A02030 Function generator: Physical address equals zero | Cause: The specified physical address is zero. Remedy: Set a physical address with a value other than zero. |
| 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. Remedy: Adjust the offset value accordingly. |
| 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. Remedy: Check the value for the bandwidth and adapt accordingly. |
| A02047 Function generator: Time slice clock cycle invalid | Cause: The time slice clock cycle selected does not match any of the existing time slices. Remedy: Enter an existing time slice clock cycle. The fastest cycle time can be read out using the commissioning tool. |
| A02050 Trace: Start not possible | Cause: The trace has already been started. Remedy: Stop the trace and, if necessary, start again. |
| A02055 Trace: Recording time too short | Cause: The trace duration is too short. The minimum is twice the value of the trace clock cycle. Remedy: Check the selected recording time and, if necessary, adjust. |
| A02056 Trace: Recording cycle too short | Cause: The selected recording clock cycle is shorter than the selected basic clock cycle 0. Remedy: Increase the value for the trace cycle. The fastest cycle time can be read out using the commissioning tool. |
| A02057 Trace: Time slice clock cycle invalid | Cause: The time slice clock cycle selected does not match any of the existing time slices. Remedy: Enter an existing time slice clock cycle. The fastest cycle time can be read out using the commissioning tool. |
| A02059 Trace: Time slice clock cycle for 2 x 8 recording channels not valid | Cause: The selected time slice clock cycle cannot be used for more than 4 recording channels. Remedy: Enter the clock cycle of an existing time slice with a cycle time >= 4 ms or reduce the number of recording channels to 4 per trace. |
| A02060 Trace: Signal to be traced missing | Cause: – A signal to be traced was not specified. – The specified signals are not valid. Remedy:
|
| A02061 Trace: Invalid signal | Cause: – The specified signal does not exist. – The specified signal can no longer be traced (recorded). Remedy:
|
| A02062 Trace: Invalid trigger signal | Cause: – A trigger signal was not specified. – The specified signal does not exist. – The specified signal is not a fixed-point signal. – The specified signal cannot be used as a trigger signal for the trace. Remedy: Specify a valid trigger signal. |
| A02063 Trace: Invalid data type | Cause: The specified data type to select a signal using a physical address is invalid. Remedy: Use a valid data type. |
| A02070 Trace: Parameter cannot be changed | Cause: The trace parameter settings cannot be changed when the trace is active. Remedy:
|
| A02075 Trace: Pretrigger time too long | Cause: The selected pretrigger time must be shorter than the trace time. Remedy: Check the pretrigger time setting and change if necessary. |
| F02080 Trace: Parameterization deleted due to unit changeover | Cause: The trace parameterization in the drive unit was deleted due to a unit changeover or a change in the reference parameters. Remedy: Restart trace. |
| A02085 Message function: Parameterization error | Cause: A parameterization error was identified when starting the variable message function. Remedy: Correct the parameter and restart. |
| 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). 1: Memory card cannot be accessed. 3: Data save operation to slow. 4: Data save operation canceled. 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). (Causes same as A02096) Remedy: (Remedies same as A02096) |
| A02099 Trace: Insufficient converter memory space | Cause: The memory space still available on the converter is no longer sufficient for the trace function. Remedy: Reduce the memory required, e.g. as follows:
|
| A02150 TEC: Technology Extension cannot be loaded | Cause: The system was not able to load a Technology Extension. 10 hex: DCB user library incompatible. 12 hex: Technology package was not able to be downloaded. Remedy:
|
| F02151 (A) TEC: internal software error | Cause: An internal software error has occurred within a Technology Extension. Remedy:
|
| F02152 (A) TEC: insufficient memory | Cause: The functionality on this converter is too extensive (e.g. too many drives, functions, data sets, Technology Extensions, blocks, etc). Remedy: Change the configuration on this converter, e.g.
|
| F02153 TEC: technology function does not exist | Cause: A technology function (e.g. Technology Extension, DCB library) does not exist on the drive device. Remedy:
|
| F03001 NVRAM checksum incorrect | Cause: A checksum error occurred when evaluating the non-volatile data (NVRAM) on the converter. The NVRAM data affected was deleted. Remedy: Carry out a POWER ON (switch-off/switch-on) for all components. |
| F03505 (N, A) Analog input wire breakage | Cause: The wire-break monitoring for an analog input has responded. Remedy: Check the wiring for interruptions. |
| A03506 (F, N) 24 V power supply missing | Cause: The 24 V power supply for the digital outputs (X124) is missing. Remedy: Check the terminals for the power supply voltage (X124, L1+, M). |
| A03510 (F, N) Calibration data not plausible | Cause: During booting, the calibration data for the analog inputs is read and checked with respect to plausibility. At least one calibration data point was determined to be invalid. Remedy:
|
| A03520 (F, N) Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124) indicates detail (e.g. 33: Wire breakage, 34: Resistance too low). Remedy:
|
| A05054 (N) 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. Remedy: Re-activate the deactivated power units if required. |
| A05065 (F, N) Voltage measured values not plausible | Cause: The voltage measurement does not supply any plausible values and is not used. Remedy: The following parameterization must be made in order to deactivate the alarm:
|
| 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). Possible reasons: line supply not connected, contactor not closed, line voltage too low/incorrect, precharging resistors overheated, DC link fault. Remedy:
|
| F06050 Infeed: Smart Mode not supported | Cause: The power unit does not support the Smart Mode. Remedy: Upgrade the power unit software and/or hardware for the Smart Mode. |
| F06080 (A) Infeed: parameter error | Cause: An infeed parameter is incorrectly set. Remedy: Appropriately change the parameter specified in the fault value. |
| 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). Remedy:
|
| A06105 (F) Infeed: Line supply undervoltage | Cause: The filtered (steady-state) value of line supply voltage is lower than the alarm threshold (p0282). Remedy:
|
| F06200 Infeed: One or several line phases failed | Cause: Failure overvoltage in one or several line supply phases. The fault can be output during switch-on or while infeed is operational. Remedy:
|
| A06205 (F) Infeed: Voltage dip in at least one line supply phase | Cause: Voltage dip or overvoltage in one or several line supply phases has been detected in operation. Remedy:
|
| A06206 (F) Infeed: Line currents asymmetrical alarm | Cause: The asymmetry of the three line currents at the terminals of the power unit exceeds the set alarm threshold (p3465). Remedy:
|
| F06207 Infeed: Line currents asymmetrical | Cause: The asymmetry of the line currents is continuously too high. The most probable cause is failure of a line phase. Fault value (r2133, floating point): Digits to the left of the decimal point: Highest rms phase current in amps. Decimal places: Quotient of the lowest and highest rms phase current value. Remedy:
|
| A06208 Infeed: line supply voltage asymmetrical | Cause: Asymmetry of the voltages in the line phase too high. The most probable cause is failure of a line phase. Note: This message is only output when asymmetry monitoring is activated (p3640.1 = 1). Remedy:
|
| F06210 Infeed: Summation current too high | Cause: The smoothed sum of the phase currents (i1 + i2 + i3) is higher than 4 % of the maximum power unit current (r13209). Possible causes: – The DC link has a ground fault that results in a high total current (r13069[6]). – The zero point calibration of the current measurement was not carried out (p3491, A06602). – Defective current measurement in the power unit. Remedy:
|
| A06215 Infeed: Summation current too high | Cause: The smoothed sum of the phase currents (i1 + i2 + i3) is higher than 3 % of the maximum power unit current (r13209). Possible causes: – The DC link has a ground fault that results in a high total current (r13069[6]). – The zero point calibration of the current measurement was not carried out (p3491, A06602). – Defective current measurement in the power unit. Remedy:
|
| F06300 Infeed: Line voltage too high at power on | Cause: The RMS line supply voltage Vrms was so high when switching on that controlled operation is not possible without exceeding the permissible maximum voltage in the DC link (p0280). Fault condition: Vrms * 1.5 > p0280. Lowest possible controlled DC link voltage for the line supply voltage presently connected. See also: p0280 (DC link voltage maximum steady-state) Remedy:
|
| A06301 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. Remedy:
|
| F06310 Infeed: Supply voltage (p0210) incorrectly parameterized | Cause: After precharging has been completed, the measured DC link voltage lies outside the tolerance range. Permissible range: 1.16 * p0210 < r0070 < 1.6 * p0210 Note: The fault can only be acknowledged when the drive is switched off. Remedy:
|
| F06311 Infeed: Supply voltage (p0210) incorrect | Cause: The supply voltage Vrms does not lie within the extended tolerance range of the set line voltage (p0210). The following applies for the extended tolerance range: 75 % * p0210 < Vrms < 120 % * p0210 Remedy:
|
| A06350 Infeed: Measured line frequency too high | Cause: The actual line frequency f_line is higher than the parameterized alarm threshold (f_line > p0211 * p0284). The alarm can be output in two operating states: 1. During the switch-on phase: Synchronization interrupted. 2. While operational: The infeed remains in “operating” state, signifying a critical operational fault. Remedy:
|
| A06351 Infeed: Measured line frequency too low | Cause: The actual line frequency f_line is lower than the parameterized alarm threshold (f_line < p0211 * p0285). The alarm can be output in two operating states: 1. During the switch-on phase: Synchronization interrupted. 2. While operational: The infeed remains in “operating” state, signifying a critical operational fault. Remedy:
|
| F06500 Infeed: Line synchronization not possible | Cause: The line synchronization is not possible within the monitoring time. The infeed was re-synchronized because it was interrupted due to incorrect line frequency or excessively high line voltage distortion. After 20 attempts, synchronization was interrupted. Remedy:
|
| A06601 Infeed: Current offset measurement interrupted | Cause: Defective current measurement or a DC current is present during the offset measurement. Alarm value (r2124): 1: Excessively high phase current during offset calibration. 2: Measured current offset > 3% of max permissible converter current. 3: Not enough phase current measured values. Remedy: For alarm value = 1:
For alarm value = 2:
For alarm value = 3:
|
| A06602 Infeed: Current offset measurement not possible | Cause: After an OFF1 = 1 no valid current offset measurement was able to be made within the monitoring time (p3491) before closing the line contactor. The current offset is set to 0. Remedy:
|
| F06700 Infeed: Switch line contactor for load condition | Cause: For an ON command, the infeed line contactor should be switched under load. Remedy:
|
| A06800 Infeed: Maximum steady-state DC link voltage reached | Cause: The DC link voltage setpoint has reached the maximum steady-state voltage parameterized in p0280. Possible reasons: Modulation depth reserve too low (p3480), Line supply voltage too high, Supply voltage (p0210) parameterized too low. Remedy:
|
| A06925 Operating mode only for diagnostic purposes | Cause: The current operating mode is only intended for diagnostic purposes. See also: p1300 (Open-loop/closed-loop control type) Remedy:
|
| F07011 Drive: Motor overtemperature | Cause: KTY84/Pt1000 or no sensor: Measured temperature exceeded fault threshold. PTC or bimetallic NC contact: Response threshold 1650 Ohm exceeded or NC contact opened. Possible causes: Motor overloaded, ambient temperature too high, wire breakage. Remedy:
|
| A07012 Drive: Motor temperature model overtemperature | Cause: Motor temperature model 1/3 or the additional motor overload protection identified that the alarm threshold was exceeded. Alarm value (r2124): 200: Model 1 (I2t) too high. 300: Model 3 too high. 400: Additional motor overload protection load too high. Remedy:
|
| F07013 Drive: Motor temperature model configuration fault | Cause: A fault has occurred in the configuration of the motor temperature model. Fault value (r0949): 300: Sensor does not supply necessary encoder temperature. 301: Encoder type unknown. 302: More than one temperature model activated. 303: Motor temperature model unknown in firmware. Remedy:
|
| A07014 Drive: Motor temperature model configuration alarm | Cause: A fault has occurred in the configuration of the motor temperature model. Alarm value (r2124): 1: Not possible to save model temperature. 300: Threshold value for alarm is higher than threshold value for fault. Remedy:
|
| A07015 Drive: Motor temperature sensor alarm | Cause: An error was detected when evaluating the temperature sensor set in p0600 and p0601. Possible causes: – Wire breakage or sensor not connected. – Measured resistance too low. – Alarm value r2124 indicates SME/TM120 channel. Remedy:
|
| F07016 Drive: Motor temperature sensor fault | Cause: An error was detected when evaluating the temperature sensor set in p0600 and p0601. Note: If alarm A07015 is present, the time in p0607 is started. If fault persists, F07016 is output. Remedy:
|
| F07048 Drive: Incorrect characteristic measurement | Cause: A fault has occurred during the characteristic measurement. Fault value (r0949): 1: Speed threshold for DQ saturation not reached. Remedy: For fault value = 1:
|
| F07080 Drive: Incorrect control parameter | Cause: The closed-loop control parameters have been parameterized incorrectly (e.g. p0356 = L_spread = 0). Fault value (r0949): The fault value includes the parameter number involved. Remedy:
|
| F07082 Macro: Execution not possible | Cause: The macro cannot be executed. Fault causes: 19: Called file invalid for trigger parameter. 24: Data type of a TAG is incorrect. 27: Value entered as string is not “DEFAULT”. 31: Entered drive object type unknown. 35: Not permissible to write parameter via macro. 36: Writing parameter unsuccessful. Remedy:
|
| F07083 Template: ACX file not found | Cause: The template to be executed was not able to be found. Fault value (r0949): Parameter number with which the execution was started. 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. 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. Fault value (r0949): Diagnostics parameter to display the parameters that were not able to be re-calculated. 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: Rounding inaccuracies, FloatingPoint inaccuracies. Fault value (r0949): See p0100. Remedy:
|
| A07089 Unit switchover: Function activation is blocked | Cause: An attempt was made to activate a function. This is not permissible if the units have already been changed over. 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. Remedy:
|
| A07094 General parameter limit violation | Cause: As a result of the violation of a parameter limit, the parameter value was automatically corrected. Minimum or Maximum limit violated. Alarm value (r2124): Parameter number whose value had to be adapted. Remedy:
|
| A07200 Drive: Master control ON command present | Cause: The ON/OFF1 command is present (no 0 signal). The command is either influenced via binary signal sink c0840 or control word bit 0. Remedy:
|
| F07220 Drive: Master control by PLC missing | Cause: The “master control by PLC” signal was missing in operation. Possible causes: Interconnection error, signal withdrawn, data transfer interrupted. Remedy:
|
| F07300 Drive: Line contactor feedback signal missing | Cause: The line contactor was not able to be closed/opened within time p0861, dropped out, or closed while drive was off. Remedy:
|
| F07311 Bypass motor switch | Cause: Feedback signal missing, too slow, or inconsistent. Fault value (r0949, bit-serial): Bit 1/2: Switch “Closed”/”Open” feedback missing. Bit 3: Feedback too slow. Bit 6: Feedback not consistent with bypass state. Remedy:
|
| F07312 Bypass Line Side Switch | Cause: The Line Side Switch feedback signal is not plausible. Fault value (r0949, binary): Bit 1/2: Switch “Closed”/”Open” feedback missing. Bit 3: Feedback too slow. Bit 6: Feedback not consistent with bypass state. Remedy:
|
| A07314 Debypass without flying restart | Cause: Flying restart was not selected when switching back to converter operation with a non-synchronized bypass. The motor is not reconnected but coasts down. Remedy:
|
| F07320 Drive: Automatic restart interrupted | Cause: The specified number of restart attempts (p1211) has been completely used up, or monitoring time expired. Remedy:
|
| A07321 Drive: Automatic restart active | Cause: The automatic restart (AR) is active. Remedy:
|
| F07330 Flying restart: Measured search current too low | Cause: During a flying restart, it was identified that the search current reached is too low. It is possible that the motor is not connected. 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:
|
| F07334 Function not possible | Cause: The selected function is not possible for this configuration. Fault value 0: Function “Travel to fixed stop” selected although encoderless operation or U/f operation is active. Remedy:
|
| A07350 Drive: Measuring probe parameterized to a digital output | Cause: The measuring probe is connected to a bidirectional digital input/output and the terminal is set as output. Remedy:
|
| A07353 Drive: DC quantity control deactivated | Cause: The DC quantity control has deactivated itself. The manipulated variable was at its limit. Remedy:
|
| A07400 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. Remedy:
|
| A07401 Drive: DC link voltage maximum controller deactivated | Cause: The Vdc_max controller can no longer maintain the DC link voltage below the limit value and was therefore switched out. 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, p1240, p1280. Remedy: The alarm disappears when power supply returns. |
| 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). |
| F07406 (N, A) Drive: Kinetic buffering maximum time exceeded | Cause: The maximum buffer time (p1255 and p1295 for vector drives with U/f control) has been exceeded without the line supply having returned. Remedy: Check the time threshold for Vdc-min controller (kinetic buffering) (p1255, p1295). |
| A07409 (N) Drive: U/f control, current limiting controller active | Cause: The current limiting controller of the U/f control was activated because the current limit was exceeded. Remedy: The alarm is automatically withdrawn after one of the following measures:
|
| F07410 Drive: Current controller output limited | Cause: The condition “I_act = 0 and Uq_set_1 longer than 16 ms at its limit” is present and can be caused by the following:
Remedy:
|
| F07411 Drive: Flux setpoint not reached when building up excitation | Cause: When quick magnetizing is configured (p1401.6 = 1) the specified flux setpoint is not reached although 90% of the maximum current is specified.
Remedy:
|
| A07416 Drive: Flux controller configuration | Cause: The configuration of the flux control (p1401) is contradictory. Alarm value (r2124, interpret hexadecimal): ccbbaaaa hex.
Remedy:
|
| F07417 Drive: Pulse technique not plausible (motor model) | Cause: The evaluation of the test pulse response indicated incorrect values. Fault value (r0949):
Remedy:
|
| 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. Remedy: Reduce the natural frequency of PT2 element for reference model (p1433). |
| F07426 (A) Technology controller actual value limited | Cause: The actual value for the technology controller (c2264) has reached a limit.
Remedy:
|
| A07428 (N) Technology controller parameterizing error | Cause: The technology controller has a parameterizing error. 1: The upper output limit in p2291 is set lower than the lower output limit in p2292. Remedy: Set the output limit in p2291 higher than in p2292. |
| F07434 Drive: It is not possible to change the direction of rotation with the pulses enabled | Cause: With the pulses enabled, a drive data set that has a different parameterized direction of rotation was selected (p1821). It is only possible to change direction using p1821 when 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 (c1141). An internal setting command caused the setpoint to be frozen. Remedy: Deactivate the hold command for the ramp-function generator (c1141). |
| F07501 Drive: Motor Data Set MDS not configured | Cause: Only for power units: The motor data set was not configured (data set number not entered in associated drive data set). Remedy: The index of the motor data set associated with the drive data set should be entered into p0186. |
| F07502 Drive: Encoder Data Set EDS not configured | Cause: The encoder data set was not configured. Remedy: The index of the encoder data set associated with the drive data set should be entered into p0187 (1st encoder), p0188 (2nd encoder). |
| 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 existing motor data sets must be assigned using the MDS number (p0186). Remedy:
|
| 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 assignment. Remedy: In the drive data sets, no longer assign MDS/EDS using p0186, p0187, p0188 or set a valid component number. |
| F07510 Drive: Encoder in the drive data set used a multiple number of times | Cause: Within a drive, in each drive data set, each encoder must always be encoder 1 or always encoder 2. This unique assignment has been violated. Remedy: Assign the drive data set to different encoders. |
| F07511 Drive: Encoder used a multiple number of times | Cause: Each encoder must only be assigned to one encoder data set. This unique assignment has been violated. Remedy: Correct the double use of an encoder component. |
| 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). The drive data set must be re-commissioned. Remedy: Commission the drive data set specified in the fault value (r0949). |
| F07517 Drive: Encoder data set changeover incorrectly parameterized | Cause: In at least two drive data sets (DDS), the same motor data set (MDS) is assigned different encoder data sets (EDS) for the motor encoder. It is not permissible for an MDS to have different motor encoders in various DDSs. Remedy: Create two MDS with the same motor data in order to operate one motor with different motor encoders. |
| A07530 Drive: Drive Data Set DDS not present | Cause: The selected drive data set is not available (r0837 > p0180). Remedy:
|
| A07531 Drive: Command Data Set CDS not present | Cause: The selected command data set is not available (r0836 > p0170). Remedy:
|
| A07550 (F, N) Drive: Not possible to reset encoder parameters | Cause: When restoring a factory setting, it was not possible to reset the encoder parameters (directly read out via DRIVE-CLiQ). Remedy:
|
| F07551 Drive encoder: No commutation angle information | Cause: The commutation angle information is missing. Synchronous motors cannot be controlled (closed-loop control). Fault value (r0949):
Remedy:
|
| F07552 (A) Drive encoder: Encoder configuration not supported | Cause: The requested encoder configuration is not supported (p0404 vs r0456). Remedy:
|
| F07553 (A) Drive encoder: Sensor Module configuration not supported | Cause: The Sensor Module does not support the requested configuration (p0430, p1982, p0437). Remedy:
|
| F07555 (A) Drive encoder: Configuration position tracking | Cause: For position tracking, the configuration is not supported.
Remedy:
|
| F07556 Measuring gearbox: Position tracking, maximum actual value exceeded | Cause: When position tracking of the measuring gearbox is configured, the maximum possible absolute position actual value (r0483) cannot be represented within 32 bits. Remedy:
|
| F07560 Drive encoder: Number of pulses is not to the power of two | Cause: For rotary absolute encoders, the pulse number in p0408 must be to the power of two. Remedy:
|
| F07561 Drive encoder: Number of multiturn pulses is not to the power of two | Cause: The multiturn resolution in p0421 must be to the power of two. Remedy:
|
| F07562 (A) Drive, encoder: Position tracking, incremental encoder not possible | Cause: The requested position tracking for incremental encoders is not supported.
Remedy:
|
| F07563 (A) Drive encoder: XIST1_ERW configuration incorrect | Cause: An incorrect configuration was identified for the “Absolute position for incremental encoder” function. Remedy:
|
| A07565 (F, N) Drive: Encoder error in PROFIdrive encoder interface 1 | Cause: An encoder error is signaled for the motor encoder via the PROFIdrive encoder interface (G1_ZSW.15). Remedy: Acknowledge the encoder error using the encoder control word (G1_STW.15 = 1). |
| A07566 (F, N) Drive: Encoder error in PROFIdrive encoder interface 2 | Cause: An encoder error was signaled for encoder 2 via the PROFIdrive encoder interface (G2_ZSW.15). Remedy: Acknowledge the encoder error using the encoder control word (G2_STW.15 = 1). |
| A07569 (F) Enc identification active | Cause: During encoder identification (waiting) with p0400 = 10100, the encoder could still not be identified. Wrong encoder, wrong cable, or not connected. Remedy:
|
| N07570 (F) Encoder identification data transfer running | Cause: The encoder type was automatically determined using p0400 = 10100. This fault causes pulses to be canceled to transfer parameterization. Remedy: Acknowledge the fault without taking additional measures. |
| F07575 Drive: Motor encoder not ready | Cause: The motor encoder signals that it is not ready.
Remedy: Evaluate other active faults via the motor encoder. |
| A07576 Drive: Encoderless operation due to a fault active | Cause: Encoderless operation is active due to a fault (r1407.13 = 1). The behavior for faults has been set to ENCODER fault response in p0491. Remedy:
|
| A07580 (F, N) Drive: No Sensor Module with matching component number | Cause: A Sensor Module with the specified component number was not found. Remedy: Correct the component number of the Sensor Module. |
| F07800 Drive: No power unit present | Cause: The power unit parameters cannot be read or no parameters are stored in the power unit. Also occurs if incorrect topology was selected in commissioning tool. 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:
|
| F07807 Drive: Short-circuit/ground fault detected | Cause: A phase-phase short-circuit or ground fault was detected at the motor-side output terminals. 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. |
| A07820 Drive: Temperature sensor not connected | Cause: The temperature sensor for monitoring the motor temperature (p0600) is not available. 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 monitoring time. Infeed not operational or binary signal sink incorrect. Remedy:
|
| F07841 (A) Drive: Infeed operation withdrawn | Cause: The signal “infeed operation” was withdrawn in operation. Remedy:
|
| F07860 (A) External fault 1 | Cause: The condition for “External fault 1” is active (initiated by 1/0 edge via binary signal sink c2106). Remedy:
|
| F07861 (A) External fault 2 | Cause: The condition for “External fault 2” is present (initiated by 1/0 edge via binary signal sink c2107). Remedy:
|
| F07890 Internal voltage protection/internal armature short-circuit with STO (Safe Torque Off) active | Cause: The internal armature short-circuit (p1231 = 4) is not possible as STO is enabled. Remedy: Switch out the internal armature short-circuit (p1231=0) or deactivate Safe Torque Off (p9603 = 0). |
| A07891 Drive: Load monitoring pump/fan blocked | Cause: The load monitoring function (p2193=4,5) detects when the pump/fan is blocked. Blocking torque threshold (p2168) might be set too low. Remedy:
|
| A07892 Drive: Load monitoring pump/fan no load condition | Cause: The monitoring function detects when the pump/fan is operating under no load conditions (dry state or broken belt). Detection torque threshold might be too low. Remedy:
|
| A07893 Drive: Load monitoring pump leakage | Cause: The load monitoring is configured for a pump (p2193 = 4). The monitoring function detects a leak in the pump circuit. In this case, the pump requires a torque that is lower than in normal operation to pump the reduced quantity. See also: p2181, p2182, p2183, p2184, p2186, p2188, p2190, p2193 Remedy:
|
| F07894 Drive: Load monitoring pump/fan blocked | Cause: The load monitoring is configured for a pump or fan (p2193 = 4, 5). The monitoring function detects when the pump/fan is blocked. It is possible that the blocking torque threshold (p2168) is set too low (e.g. heavy duty starting). See also: p2165, p2168, p2181, p2193 Remedy:
|
| F07895 Drive: Load monitoring pump/fan no load condition | Cause: The load monitoring is configured for a pump or fan (p2193 = 4, 5). The monitoring function detects when the pump/fan is operating under no load conditions. The pump is running in the dry state (no medium to be pumped) – or the fan has a broken belt. It is possible that the detection torque threshold is too low (p2191). Remedy:
|
| F07896 Drive: Load monitoring pump leakage | Cause: The load monitoring is configured for a pump (p2193 = 4). The monitoring function detects a leak in the pump circuit. In this case, the pump requires a torque that is lower than in normal operation to pump the reduced quantity. Remedy:
|
| 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. This situation can only occur, if the following conditions apply: p0504 = 0, 2 and p1300 = 20 p2177 > p1758 p1750.2 = 0 p1750.6 = 0 Remedy:
|
| F07900 (N, A) Drive: Motor blocked | Cause: Motor has been operating at the torque limit longer than the time specified in p2177 and below the speed threshold in p2175. This signal can also be triggered if the speed is oscillating and the speed controller output repeatedly goes to its limit. It may also be the case that thermal monitoring of the power unit reduces the current limit (see p0290), thereby causing the motor to decelerate. Remedy:
|
| F07901 Drive: Motor overspeed | Cause: The maximum permissible speed was either positively or negatively exceeded. The maximum permissible positive speed is formed as follows: Minimum (p1082, c1085) + p2162 The maximum permissible negative speed is formed as follows: Maximum (-p1082, c1088) – p2162 Remedy: The following applies for a positive direction of rotation:
The following applies for a negative direction of rotation:
|
| F07902 (N, A) Drive: Motor stalled | Cause: The system has identified that the motor has stalled for a time longer than is set in p2178. Fault value (r0949, interpret decimal): 1: Stall detection using r1408.11 (p1744, p0492). 2: Stall detection using r1408.12 (p1745, p1743 for synchronous reluctance motors) or via the flux difference (r0083 … r0084). 4: Missing load r2197.11 Remedy:
|
| A07903 Drive: Motor speed deviation | Cause: The absolute value of the speed difference between the setpoint (c2151) and the speed actual value (r2169) exceeds the tolerance threshold (p2163) for longer than the tolerated time (p2164, p2166). The alarm is only enabled for p2149.0 = 1. Remedy:
|
| F07904 (N, A) External armature short-circuit: Contactor feedback signal “Closed” missing | Cause: When closing the contactor, the binary signal sink “External armature short-circuit: contactor feedback signal” (c1235) 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, the binary signal sink “External armature short-circuit: contactor feedback signal” (c1235) 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. Fault value (r0949, interpret decimal): zzzz = 0001 hex = 1 dec: No permanent magnet synchronous motor selected. zzzz = 0002 hex = 2 dec: No induction motor selected. zzzz = 0065 hex = 101 dec: External armature short-circuit: Output (r1239.0) not wired. (See manual for full list of hex codes) Remedy:
|
| F07907 Internal armature short-circuit: Motor terminals are not at zero potential after pulse cancellation | Cause: The function “Internal voltage protection” (p1231 = 3) was activated. The following must be observed: – When the internal voltage protection is active, after pulse cancellation, all of the motor terminals are at half of the DC link voltage. – It is only permissible to use motors that are short-circuit proof. – The converter must be able to continually provide 1.8x the short-circuit current of the motor. – The internal voltage protection cannot be interrupted due to a fault response. Remedy:
|
| A07908 Internal armature short-circuit active | Cause: The converter signals that the motor is short-circuited through the power semiconductors (r1239.5 = 1). The pulses cannot be enabled. The internal armature short-circuit is selected (p1231 = 4). Remedy:
|
| 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. The status signal r1239.6 = 1 indicates that the internal voltage protection is ready. Remedy:
|
| A07910 (N) Drive: Motor overtemperature | Cause: KTY84/Pt1000 or no sensor: The measured motor temperature or the temperature of the motor temperature model 2 has exceeded the alarm threshold. The parameterized response becomes active. PTC or bimetallic NC contact: The response threshold of 1650 Ohm was exceeded or the NC contact opened. Remedy:
|
| A07920 Drive: Torque/speed too low | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic (too low). For p2193 = 2: The speed signal from the external encoder (see c3230) deviates from the speed (r2169) (too low). Remedy:
|
| A07921 Drive: Torque/speed too high | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic (too high). For p2193 = 2: The speed signal from the external encoder (see c3230) deviates from the speed (r2169) (too high). Remedy:
|
| A07922 Drive: Torque/speed out of tolerance | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic. For p2193 = 2: The speed signal from the external encoder (see c3230) deviates from the speed (r2169). Remedy:
|
| F07923 Drive: Torque/speed too low | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic (too low). For p2193 = 2: The speed signal from the external encoder (see c3230) deviates from the speed (r2169) (too low). Remedy:
|
| F07924 Drive: Torque/speed too high | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic (too high). For p2193 = 2: The speed signal from the external encoder (see c3230) deviates from the speed (r2169) (too high). Remedy:
|
| F07925 Drive: Torque/speed out of tolerance | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic. For p2193 = 2: The speed signal from the external encoder (see c3230) deviates from the speed (r2169). Remedy:
|
| A07926 Drive: Envelope curve parameter invalid | Cause: Invalid parameter values were entered for the envelope characteristic of the load monitoring. The following rules apply for the speed thresholds: p2182 < p2183 < p2184 The following rules apply for the torque thresholds: p2185 > p2186, p2187 > p2188, p2189 > p2190 Remedy:
|
| A07927 DC braking active | Cause: The motor is braked with DC current. DC braking is active. Remedy:
|
| F07928 Internal voltage protection initiated | Cause: The converter signals that the motor is short-circuited through the power semiconductors (r1239.5 = 1). The pulses cannot be enabled. The internal voltage protection is selected (p1231 = 3). Remedy:
|
| A07929 (F) Drive: No motor detected | Cause: The absolute current value is so small after enabling the inverter pulses that no motor is detected. Note: In the case of vector control and an induction motor, this alarm is followed by the fault F07902. Remedy:
|
| F07936 Drive: load failure | Cause: The load monitoring has detected a load failure. Remedy:
|
| 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). Possible causes: Interconnection/scaling incorrect, encoder faulty, wrong polarity, smoothing time constant issues. Remedy:
|
| F07950 (A) Drive: Incorrect motor parameter | Cause: The motor parameters were incorrectly entered while commissioning (e.g. p0300 = 0, no motor). Fault value (r0949, interpret decimal): 300: Motor type not supported for this control mode. 307: Motor parameters incorrect. 302: DQI motor type no longer supported. Remedy:
|
| F07951 Drive: Motor is not permitted | Cause: As a result of the insulation class, the motor is not permitted to be connected to this converter. The supply voltage is too high for 1PH8 motors. Remedy:
|
| F07955 Drive: Motor has been changed | Cause: Connect the original motor, switch on the converter again (POWER ON) and exit quick commissioning. Or: set p0300 = 10100, without recommissioning. Or: set p0300 = 10000 (load the parameters from the motor with DRIVE-CLiQ) and re-commission. Remedy:
|
| 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:
|
| A07960 Drive: Incorrect friction characteristic | Cause: The friction characteristic is incorrect. Alarm values: 1 (format), 1538 (torque > max), 1539 (torque < min), 3820-3829 (speeds incorrect), 3830-3839 (torques incorrect). Remedy:
|
| A07961 Drive: Record friction characteristic activated | Cause: The automatic friction characteristic record is activated. The friction characteristic is recorded at the next switch-on command. Remedy:
|
| F07963 Drive: Record friction characteristic canceled | Cause: The conditions to record the friction characteristic are not fulfilled. Fault values: 0046 (Enable signals), 1082 (Speed > max), 1300 (Control mode), 1960 (Speed controller optimization active), etc. Remedy:
|
| F07967 Drive: Automatic encoder adjustment/pole position identification incorrect | Cause: A fault has occurred during the automatic encoder adjustment or the pole position identification. Only for internal Siemens troubleshooting. Remedy:
|
| F07968 Drive: Lq-Ld measurement incorrect | Cause: A fault has occurred during the Lq-Ld measurement. Fault values: 10 (Ratio too low), 12 (Max current exceeded), 16 (Drive too small), 17 (Abort due to pulse inhibit). Remedy:
|
| F07969 Drive: Incorrect pole position identification | Cause: A fault has occurred during the pole position identification routine. Fault values include Current controller limited, Motor shaft locked, Encoder signal not plausible, etc. Remedy:
|
| F07970 Drive: Automatic encoder adjustment incorrect | Cause: A fault has occurred during the automatic encoder adjustment. Fault values: 1 (Current controller limited), 2 (Motor shaft locked), 4 (Encoder signal not plausible), etc. Remedy:
|
| A07971 Drive: Angular commutation offset determination activated | Cause: The automatic determination of the angular commutation offset (encoder adjustment) is activated (p1990 = 1, 3). Note: The automatic determination is carried out at the next switch-on command. Remedy: Not necessary. The alarm is automatically withdrawn after successful determination or for the setting p1990 = 0. |
| A07975 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. This alarm is automatically withdrawn after 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. Alarm value (interpret decimal):
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. Note: During the rotating measurement it is not possible to save the parameters (p0977). Remedy: Not necessary. The alarm is automatically withdrawn after the speed controller optimization has been successfully completed or for the setting p1900 = 0. |
| A07981 Drive: Enable signals for the rotating measurement missing | Cause: The rotating measurement cannot be started due to missing enable signals. For p1959.13 = 1, the following applies:
Remedy:
|
| F07982 Drive: Rotating measurement encoder test | Cause: A fault has occurred during the encoder test. Fault value (r0949, interpret decimal):
Remedy:
|
| F07983 Drive: Rotating measurement saturation characteristic | Cause: A fault has occurred while determining the saturation characteristic. Fault value (r0949, interpret decimal):
Remedy:
|
| F07984 Drive: Speed controller optimization, moment of inertia | Cause: A fault has occurred while identifying the moment of inertia. Fault value (r0949, interpret decimal):
Remedy:
|
| F07985 Drive: Speed controller optimization (oscillation test) | Cause: A fault has occurred during the vibration test. Fault value (r0949, interpret decimal):
Remedy:
|
| F07986 Drive: Rotating measurement ramp-function generator | Cause: Problems with the ramp-function generator occurred. Fault value 1: The positive and negative directions are inhibited. Remedy:
|
| 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: Error while measuring dynamic leakage inductance. Fault value (r0949):
Remedy:
|
| F07990 Drive: Incorrect motor data identification | Cause: A fault has occurred during the identification routine. Fault value (r0949) indicates specific parameter issues (Resistance, Reactance, Time constants outside expected ranges 1-9), incorrect connection (10), shaft rotation (11), ground fault (12), etc. Remedy:
|
| 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. Alarm is withdrawn after completion or setting p1900 = 0. |
| A07994 (F, N) Drive: motor data identification not performed | Cause: Operating mode p0504 = 1 or vector control set, but motor data ID not performed. Initiated when changing drive data set if vector control parameterized but ID missing. Remedy:
|
| F08000 (N, A) TB: +/-15 V power supply faulted | Cause: Terminal Board 30 detects an incorrect internal power supply voltage. 0: Error testing monitoring circuit. 1: Fault in normal operation. Remedy:
|
| F08010 (N, A) TB: Analog-digital converter | Cause: The analog/digital converter on Terminal Board 30 has not supplied any converted data. Remedy:
|
| A08560 IE: Syntax error in configuration file | Cause: Syntax error detected in configuration file for Industrial Ethernet interface (X127). Saved configuration not loaded. Remedy: Reinitialize the station using the “Edit Ethernet node” screen form. |
| A08561 IE: Consistency error affecting adjustable parameters | Cause: Consistency error detected for Industrial Ethernet interface (X127). Values: 1 (IP config), 2 (Station names), 5 (Gateway), 6 (Station name), 7 (IP address subnet). Remedy: Reinitialize the station using the “Edit Ethernet node” screen form. |
| A08562 PROFINET: Syntax error in configuration file | Cause: Syntax error detected in configuration file for PROFINET interface (X150). Remedy: Reinitialize the station using the “Edit Ethernet node” screen form. |
| A08563 PROFINET: Consistency error affecting adjustable parameters | Cause: Consistency error detected for PROFINET interface (X150). Values: 1 (IP config), 2 (Station names), 3 (DHCP), 5 (Gateway), 6 (Station name), 7 (IP address subnet). Remedy: Reinitialize the station using the “Edit Ethernet node” screen form. |
| A08566 IIOT: Syntax error in configuration file | Cause: Syntax error detected in configuration file for IIoT interface (X128). Remedy: Reinitialize the station using the “Edit Ethernet node” screen form. |
| A08567 IIoT: Consistency error for adjustable parameters | Cause: Consistency error detected for IIoT interface (X128). Values: 1 (IP config), 2 (Station names), 5 (Gateway), 6 (Station name), 7 (IP subnet). Remedy: Reinitialize the station using the “Edit Ethernet node” screen form. |
| A08800 PROFIenergy energy-saving mode active | Cause: The PROFIenergy energy-saving mode is active. Remedy: Not necessary. Alarm automatically withdrawn when energy-saving mode is exited (end_pause command, STOP state, or disconnection). |
| F13000 License not adequate | Cause: Options require a license but licenses are not sufficient or error checking licensing. 0: No license data on card. 1: License data withdrawn or card defective. 3: License does not match card serial. 4-7: License manipulated/invalid. Remedy:
|
| A13002 Licensing not sufficient in operation | Cause: Options require a license but licenses are not sufficient. (Similar causes to F13000). Remedy:
|
| A13030 Trial License activated | Cause: The “Trial License” function was activated. One of the available periods is expiring. Remedy: Not necessary. Automatically withdrawn after periods expire. |
| A13031 Trial License period expired | Cause: One of the available periods of the “Trial License” function has expired. Remedy:
|
| A13032 Trial License last period activated | Cause: The “Trial License” function was activated. The last of the available periods is expiring. Remedy: Not necessary. Automatically withdrawn after last period. |
| A13033 Trial License last period expired | Cause: The last period of the “Trial License” function has expired. Remedy:
|
| F29001 Infeed power unit: Overcurrent | Cause: Power unit detected overcurrent. – Closed-loop control incorrectly parameterized. – High discharge/post-charging currents. – Power cables not correctly connected / Line phase interrupted / Defective unit. Remedy:
|
| F29002 Infeed power unit: DC link voltage overvoltage | Cause: Overvoltage in DC link. – Motor regenerates too much energy. – Device supply voltage too high. – Line phase interrupted. Remedy:
|
| F29003 Infeed power unit: DC link voltage undervoltage | Cause: Undervoltage in DC link. – Line supply failure. – Line supply voltage below permissible value. – Line supply infeed failed/interrupted. Remedy:
|
| F29004 Infeed power unit: Heat sink overtemperature | Cause: Heat sink temperature exceeded limit. – Insufficient cooling/fan failure. – Overload. – Ambient temperature too high. – Pulse frequency too high. Remedy:
|
| F29005 Infeed power unit: Overload I2t | Cause: Power unit overloaded (r13036 = 100%). – Permissible rated current exceeded for too long. – Load duty cycle not maintained. Remedy:
|
| F29007 Infeed power unit: Inadmissible asymmetry of the partial DC links | Cause: Inadmissibly high level of asymmetry in partial capacitances. – Asymmetrical line voltage dips/interruptions. – Strongly oscillating DC link load. – Device damage. Remedy:
|
| F29008 Infeed power unit: Sign-of-life error cyclic data | Cause: Converter has not punctually updated cyclic setpoint telegrams. Remedy: Check the converter and if required replace. |
| A29010 (F) Infeed power unit: Sign-of-life error cyclic data | Cause: Internal communication error. Cyclic setpoint telegrams not received on time. Remedy: Check the power unit and if required replace. |
| F29011 Infeed power unit: Line phase failure in the main circuit | Cause: DC link voltage ripple exceeded permissible limit. – Line phase failed. – Line phases inadmissibly asymmetrical. – Resonance frequency issue. – Main circuit fuse ruptured. Remedy:
|
| F29012 Infeed power unit: Temperature sensor wire breakage | Cause: Connection to a temperature sensor in power unit is interrupted. Bit 1-15 indicates location (Air intake, Inverter, Rectifier, etc.). Remedy: Contact Technical Support. |
| F29013 Infeed power unit: Temperature sensor short-circuit | Cause: A temperature sensor in the power unit is short-circuited. Bit 1-15 indicates location. Remedy: Contact Technical Support. |
| F29017 Infeed power unit: Hardware current limit has responded too often | Cause: Hardware current limit responded too frequently. Remedy: (Implicitly requires checking load/power unit conditions, similar to overcurrent). |
| F29013 Infeed power unit: Temperature sensor short-circuit | Cause: A temperature sensor in the power unit is short-circuited. Fault value (r0949, interpret binary): Bit 1: Air intake Bit 2: Inverter 1 Bit 3: Inverter 2 Bit 4: Inverter 3 Bit 5: Inverter 4 Bit 6: Inverter 5 Bit 7: Inverter 6 Bit 8: Rectifier Bit 10: Moisture ext. moisture sensor Bit 11: Temperature ext. moisture sensor Bit 14: Capacitor air discharge Bit 15: Liquid intake Remedy:
|
| F29017 Infeed power unit: Hardware current limit has responded too often | Cause: The hardware current limiting in the particular phase has responded too frequently (see A29031, A29032, A29033). The number of times the limit has been exceeded depends on the design and type of power unit. Possible causes: – Closed-loop control is incorrectly parameterized. – Load is too large. – Power unit defective. Fault value (r0949, interpret binary): Bit 3: phase U Bit 4: phase V Bit 5: phase W Remedy:
|
| F29020 Infeed power unit: Configuration not supported | Cause: A configuration is requested that is not supported by the power unit. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex: xxxx = fault cause, yyyy = additional information (internal Siemens) xxxx = 1: The requested DRIVE-CLiQ timing is not permissible. xxxx = 3: Initialization was not able to be successfully completed. It is possible that the converter was switched-off before or while running up. xxxx = 4: The combination of power unit and converters is not supported. xxxx = 8: The version of the ASIC installed in the power unit is no longer supported. Remedy:
|
| F29021 Infeed power unit: Ground fault | Cause: The power unit has detected a ground fault. Possible causes: – Ground fault in the motor cables or in the motor. – Braking resistor has a ground fault. – DC link ground fault. – CT defective. Note: Fault value 0 = Braking resistor fault; > 0 = Absolute value, total current amplitude. Remedy:
|
| F29022 Infeed 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: – The power supply for power semiconductor gating missing. – Short-circuit at the power unit output. – Defective semiconductor in the power unit. Fault value (r0949, interpret binary): Bit 0: Short-circuit in phase U Bit 1: Short-circuit in phase V Bit 2: Short-circuit in phase W Bit 4: U_ce group fault signal interrupted Remedy:
|
| F29024 Infeed power unit: Overtemperature thermal model | Cause: The temperature difference between the power semiconductor involved and the heat sink has exceeded the permissible fault threshold. – The permissible load duty cycle was not maintained. – Insufficient cooling, fan failure. – Overload. – Ambient temperature too high. – Pulse frequency too high. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex: yyyy= Power semiconductor, xxxx = Temperature in 0.01°C Remedy:
|
| F29025 Infeed power unit: Chip overtemperature | Cause: The chip temperature of the power semiconductor involved has exceeded the permissible fault threshold. – The permissible load duty cycle was not maintained. – Insufficient cooling, fan failure. – Overload. – Ambient temperature too high. – Pulse frequency too high. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex: yyyy= Power semiconductor, xxxx = Temperature in 0.01°C Remedy:
|
| F29027 Infeed power unit: Precharging DC link time monitoring | Cause: The power unit DC link was not able to be precharged within the expected time. 1) There is no line supply voltage connected. 2) The line contactor/line side switch has not been closed. 3) The line supply voltage is too low. 4) Line supply voltage incorrectly set (p0210). 5) The precharging resistors are overheated (too many operations per time unit). 6) DC link capacitance is too high. 7) Power taken from DC link before “ready for operation”. 8) Line contactor closed during DC link fast discharge. 9) DC link ground fault or short-circuit. 10) Precharging circuit defective. 11) Infeed defective. Fault value (r0949): See list manual for specific bit codes (0-13) regarding precharge state and errors. Remedy:
|
| A29030 Infeed power unit: Internal overtemperature alarm | Cause: The temperature inside the drive converter has exceeded the permissible temperature limit. – Insufficient cooling, fan failure. – Overload. – Ambient temperature too high. Remedy:
|
| A29031 Infeed power unit: Hardware current limiting in phase U | Cause: Hardware current limit for phase U responded. The pulsing in this phase is inhibited for one pulse period. – Closed-loop control is incorrectly parameterized. – Fault in the power cables. – The power cables exceed the maximum permissible length. – Power unit defective. Remedy:
|
| A29032 Infeed 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. – Closed-loop control is incorrectly parameterized. – Fault in the power cables. – The power cables exceed the maximum permissible length. – Power unit defective. Remedy:
|
| A29033 Infeed 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. – Closed-loop control is incorrectly parameterized. – Fault in the power cables. – The power cables exceed the maximum permissible length. – Power unit defective. Remedy:
|
| A29034 Infeed power unit: Internal overtemperature | Cause: The alarm threshold for internal overtemperature has been reached. Fault F29036 is triggered if temperature increases further. – Ambient temperature might be too high. – Insufficient cooling, fan failure. Alarm value (r2124, interpret binary) indicates specific area (control electronics, power electronics, processor, internal fan, intake air). Remedy:
|
| F29035 Infeed power unit: Overtemperature air intake | Cause: The air intake in the power unit has exceeded the permissible temperature limit. – Ambient temperature too high. – Insufficient cooling, fan failure. Remedy:
|
| F29036 Infeed power unit: Internal overtemperature | Cause: The temperature inside the converter has exceeded the permissible limit value. – Insufficient cooling, fan failure. – Overload. – Ambient temperature too high. Fault value indicates specific area (control electronics, power electronics, processor, internal fan, intake air). Remedy:
|
| F29040 Infeed power unit: Undervoltage 24 V | Cause: Failure of the 24 V power supply for the power unit. The undervoltage threshold was undershot for longer than 3 ms. Remedy:
|
| A29041 (F) Infeed power unit: Undervoltage 24/48 V alarm | Cause: For the power unit power supply, the lower threshold has been violated. Remedy:
|
| A29042 (N) Infeed power unit: Fan has reached the maximum operating hours | Cause: The maximum operating time of at least one fan will soon be reached, or has already been exceeded. Alarm value (r2124) indicates which fan (heat sink fan, internal fan 1, internal fan 2). Remedy:
|
| F29043 Infeed power unit: Overvoltage 24/48 V | Cause: For the power unit power supply, the upper threshold has been violated. Remedy:
|
| A29044 (F) Infeed power unit: Overvoltage 24/48 V alarm | Cause: For the power unit power supply, the upper threshold has been violated. Remedy:
|
| A29048 (N) Infeed power unit: Defective fan | Cause: The feedback signal of a fan signals a fault, or there is a communication error with one or several fans. – Fan defective / blocked. – Feedback signal error. Remedy:
|
| F29050 Infeed power unit: 24 V supply overvoltage | Cause: The voltage monitor signals an overvoltage fault on the module. Remedy:
|
| F29052 Infeed EEPROM data error | Cause: Power unit EEPROM data error. Remedy:
|
| F29053 Infeed FPGA data error | Cause: The FPGA data of the power unit are faulty. This can be caused, for example, if a firmware update is interrupted. Remedy:
|
| F29055 Infeed power unit: Braking chopper overcurrent | Cause: An overcurrent condition has occurred in the braking chopper. Remedy:
|
| A29057 Infeed 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. If these frequencies occur with high amplitudes, Fault F29011 is output. Remedy:
|
| F29058 (N, A) Infeed power unit: Heat sink fan defective | Cause: The feedback signal of the heat sink fan signals a fault, or there is a communication error with the fan. Remedy:
|
| F29059 Infeed power unit: Internal fan 1 defective | Cause: The feedback signal of internal fan 1 signals a fault, or there is a communication error with the fan. Remedy:
|
| F29062 Infeed bypass contactor opened with current flowing | Cause: The bypass contactor of the precharging unit has been opened under current. Possible causes: A defect at the bypass contactor. Remedy:
|
| A29066 (N) Infeed power unit: Overtemperature, alarm capacitor air discharge | Cause: The air discharged from the DC link capacitor has exceeded the alarm threshold. – Ambient temperature too high. – Insufficient cooling, fan failure. Note: If operation is unchanged, fault F30067 may be output. Remedy:
|
| F29067 Infeed power unit: Overtemperature, fault capacitor air discharge | Cause: The air discharged from the DC link capacitor has exceeded the permissible limit. – Ambient temperature too high. – Insufficient cooling, fan failure. Remedy:
|
| F29068 Infeed power unit: Undertemperature inverter heat sink | Cause: The actual inverter heat sink temperature is below the permissible minimum value. – The power unit is being operated at an ambient temperature that lies below the permissible range. – The temperature sensor evaluation is defective. Remedy:
|
| F29105 Infeed power unit: Actual value sensing error | Cause: At least one incorrect actual value channel was detected on the Power Stack Adapter (PSA). Remedy:
|
| A29250 (N) Infeed power unit: Overtemperature heat sink rectifier | Cause: The alarm threshold for overtemperature at the infeed heat sink has been reached. Fault F29004 is output if the temperature increases by 5 K. Remedy:
|
| A29252 Infeed power unit: Chip overtemperature alarm | Cause: The chip temperature of the power semiconductor involved has exceeded the permissible alarm threshold. Fault F29025 is output if the temperature of the heat sink increases by 5 K. Remedy:
|
| A29253 Infeed power unit: Overtemperature thermal model alarm | Cause: The temperature difference between the power semiconductor involved and the heat sink has exceeded the permissible alarm threshold. Note: If the temperature continues to increase, this can result in fault F29024. Remedy:
|
| A29254 (N) Infeed power unit: Overtemperature air intake alarm | Cause: The alarm threshold for the air intake overtemperature has been reached. Fault F29035 is initiated if the air intake temperature continues to increase. Remedy:
|
| A29256 Infeed power unit: Overload I2t | Cause: The alarm threshold for I2t overload (95%) of the power unit has been exceeded. Remedy:
|
| F29260 Infeed power unit: Fault in the driver supply for the power semiconductor | Cause: A fault has occurred in the driver supply of the power semiconductor. Remedy:
|
| F29261 Infeed power unit: Internal fan 2 defective | Cause: The feedback signal of internal fan 2 signals a fault, or there is a communication error with the fan. Remedy:
|
| A29266 Infeed power unit: Required modulator setting cannot be implemented | Cause: The required modulator setting was not able to be implemented. This can involve some undesirable effects; for example, unexpectedly high switching losses can occur or the current controller bandwidth can be reduced. Remedy:
|
| A29507 (F, N) Infeed power unit: Asymmetry of the partial DC links | Cause: Asymmetry has occurred between partial capacitances in the DC link. – Asymmetrical line voltage dips. – Strongly oscillating DC link load. – Device damage. Remedy:
|
| N29800 (F) Infeed power unit: Group signal | Cause: The power unit has detected at least one fault. Remedy:
|
| F29801 Infeed power unit DRIVE-CLiQ: Sign-of-life missing | Cause: There is a DRIVE-CLiQ communication error between the converter and the power unit involved. The computing time load might be too high. Remedy:
|
| F29802 Infeed power unit: Time slice overflow | Cause: A time slice overflow has occurred. Remedy:
|
| F29804 (N, A) Infeed power unit: CRC | Cause: A checksum error (CRC error) has occurred for the power unit. Remedy:
|
| F29805 Infeed power unit: EEPROM checksum error | Cause: Internal parameter data is corrupted (EEPROM access error or too many blocks). Remedy:
|
| F29809 Infeed power unit: Switching information not valid | Cause: For 3P gating unit: The last switching status word in the setpoint telegram is identified by the end ID. Such an end ID was not found. Remedy:
|
| F29810 Infeed power unit: Watchdog timer elapsed | Cause: The watchdog timer has expired. This can only be caused by a fatal software error. Remedy:
|
| F29820 Infeed power unit DRIVE-CLiQ: Telegram error | Cause: There is a DRIVE-CLiQ communication error between the converter and the power unit involved. Remedy:
|
| F29835 Infeed power unit DRIVE-CLiQ: Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error between the converter and the power unit involved. The nodes do not send and receive in synchronism. Remedy:
|
| F29836 Infeed power unit DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: There is a DRIVE-CLiQ communication error between the converter and the power unit involved. Data were not able to be sent. Remedy:
|
| F29837 Infeed power unit DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component involved. Faulty hardware cannot be excluded. Remedy:
|
| F29845 Infeed power unit DRIVE-CLiQ: Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error between the converter and the power unit involved. Synchronization error during alternating cyclic data transfer. Remedy:
|
| F29850 Infeed power unit: Internal software error | Cause: An internal software error has occurred in the power unit. Remedy:
|
| F29851 Power unit DRIVE-CLiQ: Sign-of-life missing | Cause: There is a DRIVE-CLiQ communication error from the power unit involved to the converter. The DRIVE-CLiQ component did not set the sign-of-life to the converter. Remedy:
|
| A29853 Infeed power unit: Sign-of-life error cyclic data | Cause: The power unit has detected that the cyclic setpoint telegrams of the converter have not been updated on time. At least two sign-of-life errors have occurred within the window that has been set. Remedy:
|
| F29860 Infeed power unit DRIVE-CLiQ: Telegram error | Cause: There is a DRIVE-CLiQ communication error from the power unit involved to the converter. Fault value (r0949, interpret hexadecimal): 0000yyxx hex (yy = component number, xx = fault cause) xx = 1: Checksum error (CRC error). xx = 2: Telegram is shorter than specified in the length byte or in the receive list. xx = 3: Telegram is longer than specified in the length byte or in the receive list. xx = 4: The length of the receive telegram does not match the receive list. xx = 5: The type of the receive telegram does not match the receive list. xx = 6: The address of the power unit in the telegram and in the receive list do not match. xx = 9: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the converter signals that the supply voltage has failed. xx = 16: The receive telegram is too early. xx = 17: CRC error and the receive telegram is too early. xx = 18: The telegram is shorter than that specified in the length byte or in the receive list and the receive telegram is too early. xx = 19: The telegram is longer than that specified in the length byte or in the receive list and the receive telegram is too early. xx = 20: The length of the receive telegram does not match the receive list and the receive telegram is too early. xx = 21: The type of the receive telegram does not match the receive list and the receive telegram is too early. xx = 22: The address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early. xx = 25: The error bit in the receive telegram is set and the receive telegram is too early. Remedy:
|
| F29875 Infeed power unit: Supply voltage failed | Cause: Supply voltage fault (undervoltage). The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the converter signals that the supply voltage has failed. Fault value (r0949): xx = 9 (= 09 hex): The power supply voltage for the components has failed. Remedy:
|
| F29885 Power unit DRIVE-CLiQ: Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error from the power unit involved to the converter. The nodes do not send and receive in synchronism. Error cause (xx): 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. Remedy:
|
| F29886 Power unit DRIVE-CLiQ: Error when sending DRIVE-CLiQ data | Cause: There is a DRIVE-CLiQ communication error from the power unit involved to the converter. Data were not able to be sent. Error cause: 65 (= 41 hex): Telegram type does not match send list. Remedy:
|
| F29887 Infeed power unit DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component (power unit) involved. Faulty hardware cannot be excluded. Error cause (xx): 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. Remedy:
|
| F29895 Power unit DRIVE-CLiQ: Alternating cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error from the power unit involved to the converter. Error cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy:
|
| F29896 Infeed power unit DRIVE-CLiQ: Component properties inconsistent | 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:
|
| F29899 (N, A) Infeed power unit: Unknown fault | Cause: A fault occurred on the power unit, which cannot be interpreted by the converter firmware. This can occur if the firmware on the power unit is more recent than the firmware on the converter. Note: The significance of the fault still cannot be known in an older firmware version. Remedy:
|
| F29903 Infeed power unit: I2C bus error occurred | Cause: Communications error with an EEPROM or an analog/digital converter. Fault value (hex): 80000000 hex: Internal software error. 00000001 hex … 0000FFFF hex: Module fault. Remedy:
|
| F29907 Infeed power unit: FPGA configuration unsuccessful | Cause: During initialization within the power unit, an internal software error has occurred. Remedy:
|
| A29920 (F) Infeed power unit: Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A29930 (N) Infeed power unit: Component trace has saved data | Cause: Error in the parameterization / configuration / commissioning procedure. Remedy:
|
| F29950 Infeed power unit: Internal software error | Cause: An internal software error has occurred. Only for internal Siemens troubleshooting. Remedy:
|
| A29999 (F, N) Infeed power unit: Unknown alarm | Cause: An alarm occurred on the power unit, which cannot be interpreted by the converter firmware. This can occur if the firmware on the power unit is more recent than the firmware on the converter. Remedy:
|
| F30001 Power unit: Overcurrent | Cause: The power unit has detected an overcurrent condition. Causes include: – Closed-loop control incorrectly parameterized. – Motor short-circuit or fault to ground. – U/f operation: ramp set too low or rated motor current significantly higher than Motor Module. – Infeed: High discharge/post-charging currents. – Power cables not connected correctly or exceed max length. – Power unit defective. – Line phase interrupted. Fault value (bit-serial): Bit 0: Phase U, Bit 1: Phase V, Bit 2: Phase W, Bit 3: Overcurrent in DC link. Remedy:
|
| F30002 Power unit: DC link voltage overvoltage | Cause: The power unit has detected overvoltage in the DC link. – Motor regenerates too much energy. – Device supply voltage too high. – Voltage Sensing Module (VSM) phase assignment differs from power unit. – Line phase interrupted. Remedy:
|
| F30003 Power unit: DC link voltage undervoltage | Cause: The power unit has detected an undervoltage condition in the DC link. – Line supply failure. – Line supply voltage below the permissible value. – Line supply infeed failed or interrupted. – Line phase interrupted. Remedy:
|
| F30004 Power unit: Overtemperature heat sink inverter | Cause: The temperature of the power unit heat sink has exceeded the permissible limit value. – Insufficient cooling, fan failure. – Overload. – Ambient temperature too high. – Pulse frequency too high. Remedy:
|
| F30005 Power unit: Overload I2t (AC) | Cause: The fault threshold for the I2t overload on the AC side of the power unit has exceeded. The permissible load duty cycle or the continuous load was not maintained. Remedy:
|
| F30008 Power unit: Sign-of-life error cyclic data | Cause: The converter has not punctually updated the cyclic setpoint telegrams. The number of consecutive tolerated sign-of-life errors has exceeded the fault threshold. Remedy:
|
| A30010 (F) Power unit: Sign-of-life error cyclic data | Cause: There is an internal communication error in the converter. The cyclic setpoint telegrams of the converter were not received on time 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: – A line phase has failed. – The 3 line phases are inadmissibly asymmetrical. – Resonance frequency between DC link capacitor and line inductance. – Fuse ruptured. – Motor phase failed. Remedy:
|
| F30012 Power unit: Temperature sensor wire breakage | Cause: The connection to a temperature sensor in the power unit is interrupted. Fault value (r0949) bits indicate the specific sensor (e.g., Bit 1: Air intake, Bit 2: Inverter 1, etc.). Remedy:
|
| F30013 Power unit: Temperature sensor short-circuit | Cause: A temperature sensor in the power unit is short-circuited. Fault value (r0949) bits indicate the specific sensor (e.g., Bit 1: Air intake, Bit 2: Inverter 1, etc.). Remedy:
|
| F30015 (N, A) Power unit: Phase failure motor cable | Cause: A phase failure in the motor feeder cable was detected. Can also trigger if the motor stalls in U/f control (0 A measured due to asymmetry) or if closed-speed control is unstable. Remedy:
|
| A30016 (N) Power unit: Load supply switched off | 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 (see A30031, A30032, A30033) has responded too often. For infeed units: Incorrect parameterization, load too high, VSM issue, line reactor issue, or power unit defective. For Motor Modules: Incorrect parameterization, fault in motor/cable, cable too long, load too high, or power unit defective. Remedy:
|
| F30020 Power unit: Configuration not supported | Cause: A configuration is requested that is not supported by the power unit. Fault value (hex): xxxx = 1: Requested DRIVE-CLiQ timing not permissible. xxxx = 3: Initialization failed. xxxx = 4: Combination of power unit and converters not supported. xxxx = 8: ASIC version not supported. Remedy:
|
| F30021 Power unit: Ground fault | Cause: The power unit has detected a ground fault. Possible causes: Ground fault in power cables or motor; CT defective; Hardware DC current monitoring responded when brake closes; Short-circuit at braking resistor. 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: Fiber-optic cable interrupted; Power supply for gating missing; Short-circuit at output; Defective semiconductor. Remedy:
|
| F30024 Power unit: Overtemperature thermal model | Cause: The temperature difference between the power semiconductor and the heat sink has exceeded the permissible fault threshold. – Permissible load duty cycle not maintained. – Insufficient cooling, fan failure. – Overload. – Ambient temperature/Pulse frequency too high. Remedy:
|
| F30025 Power unit: Chip overtemperature | Cause: The chip temperature of the power semiconductor has exceeded the permissible fault threshold. 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. Possible causes: No line supply; Line contactor not closed; Line voltage too low/incorrect; Precharging resistors overheated; DC link fault/short-circuit; Infeed defective. Remedy:
|
| A30030 Power unit: Internal overtemperature alarm | Cause: The temperature inside the drive converter has exceeded the permissible temperature limit. – Insufficient cooling, fan failure. – Overload. – Ambient temperature too high. 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. – Closed-loop control incorrectly parameterized. – Fault in motor/cables. – Cables too long. – Motor load too high. – Power unit defective. Remedy:
|
| A30032 Power unit: Hardware current limiting in phase V | Cause: Hardware current limit for phase V responded. The pulsing in this phase is inhibited for one pulse period. (Same causes as Phase U). 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. (Same causes as Phase U). Remedy:
|
| A30034 Power unit: Internal overtemperature | Cause: The alarm threshold for internal overtemperature has been reached. – Ambient temperature too high. – Insufficient cooling, fan failure. Alarm value bits indicate specific area (control electronics, power electronics, processor, internal fan, air intake). Remedy:
|
| F30036 Power unit: Internal overtemperature | Cause: The temperature inside the converter has exceeded the permissible limit value. – Insufficient cooling, fan failure. – Overload. – Ambient temperature too high. Remedy:
|
| F30037 Power unit: Rectifier overtemperature | Cause: The temperature in the rectifier of the power unit has exceeded the permissible temperature limit. Remedy:
|
| F30040 Power unit: 24 V undervoltage | 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 (N) Power unit: Fan has reached the maximum operating hours | Cause: The maximum operating time of at least one fan will soon be reached, or has already been exceeded. Alarm value (r2124, interpret binary): Bit 0 = 1: Heat sink fan reached 99%. Bit 2 = 1: Heat sink fan exceeded 100%. Bit 8 = 1: 1st internal fan reached 99%. Bit 10 = 1: 1st internal fan exceeded 100%. Bit 16 = 1: 2nd internal fan reached 99%. Bit 18 = 1: 2nd internal fan exceeded 100%. 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. Fault value (r0949, interpret decimal): 24 V voltage [0.1 V]. Remedy:
|
| A30044 (F) Power unit: Overvoltage 24 V alarm | Cause: For the power unit power supply, the upper threshold has been violated. Alarm value (r2124, interpret decimal): 24 V voltage [0.1 V]. Remedy:
|
| A30048 (N) Power unit: fan defective | Cause: The feedback signal of a fan signals a fault, or there is a communication error with one or several fans. – Fan defective. – Fan blocked. – Feedback signal error. Alarm value (r2124, interpret binary): Bit 0 = 1: heat sink fan Bit 1 = 1: fan 1 inside the device Bit 2 = 1: fan 2 inside the device Bit 4 = 1: Internal communication error 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: The EEPROM data of the power unit module are incorrect. Remedy:
|
| F30053 FPGA data faulty | Cause: The FPGA data of the power unit are faulty. This can be caused if a firmware update is interrupted. Remedy:
|
| F30055 Power unit: Braking chopper overcurrent | Cause: An overcurrent condition has occurred in the braking chopper. Remedy:
|
| 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. If these frequencies persist, fault F30011 is output. Remedy:
|
| F30058 (N, A) Power unit: heat sink fan defective | Cause: The feedback signal of the heat sink fan signals a fault, or there is a communication error with the fan. Fault value (r0949, decimal): 0: Feedback signal of the fan signals a fault. 1: Internal communication error to the fan. Remedy:
|
| F30059 Power unit: Internal fan 1 defective | Cause: The feedback signal of internal fan 1 signals a fault, or there is a communication error with the fan. Fault value (r0949, decimal): 0: Feedback signal of the fan signals a fault. 1: Internal communication error to the fan. Remedy:
|
| F30062 Bypass contactor opened under current | Cause: The bypass contactor of the precharging unit has been opened under current. Possible causes: A defect at the bypass contactor. Remedy:
|
| A30065 (F, N) Voltage measured values not plausible | Cause: The voltage measurement is not supplying any plausible values. Alarm value (r2124, bit-serial): Bit 1: Phase U. Bit 2: Phase V. Bit 3: Phase W. Remedy:
|
| F30068 Power unit: undertemperature inverter heat sink | Cause: The actual inverter heat sink temperature is below the permissible minimum value. Possible causes: Ambient temperature too low, or sensor evaluation defective. Remedy:
|
| A30076 (N) Power unit: Thermal overload braking resistor alarm | Cause: The energy absorbed by the braking resistor has exceeded the alarm threshold of 80%. If operation continues, the shutdown threshold may be reached (Alarm A30077). Remedy:
|
| A30077 (N) Power unit: Thermal overload braking resistor | Cause: The braking resistor is thermally overloaded. This is the reason that its use was inhibited. Remedy:
|
| F30105 PU: Actual value sensing fault | Cause: At least one incorrect actual value channel was detected on the Power Stack Adapter (PSA). Remedy:
|
| A30250 (N) Power unit: Overtemperature heat sink inverter | Cause: The alarm threshold for overtemperature at the inverter heat sink has been reached. Remedy:
|
| A30251 (N) Power unit: Rectifier overtemperature | Cause: The alarm threshold for the overtemperature of the rectifier has been reached. Remedy:
|
| A30252 Power unit: Chip overtemperature alarm | Cause: The chip temperature of the power semiconductor involved has exceeded the permissible alarm threshold. Remedy:
|
| A30253 Power unit: Overtemperature thermal model alarm | Cause: The temperature difference between the power semiconductor involved and the heat sink has exceeded the permissible alarm threshold. Remedy:
|
| A30256 Power unit: Overload I2t (AC) | Cause: The alarm threshold for I2t overload (95%) of the power unit has been exceeded. Remedy:
|
| A30257 Power unit: Overload I2t (DC) | Cause: The alarm threshold for the I2t overload on the DC side of the power unit has been exceeded. Remedy:
|
| F30258 Power unit: Overload I2t (DC) | Cause: The fault threshold for the I2t overload on the DC side of the power unit has been exceeded. Remedy:
|
| F30260 Power unit: Fault in the driver supply for the power semiconductor | Cause: A fault has occurred in the driver supply of the power semiconductor. Remedy:
|
| F30262 Power unit: Braking chopper defective | Cause: The braking chopper is defective. Remedy:
|
| F30263 Power unit: Braking chopper upper defective | Cause: The upper braking chopper is defective. Remedy:
|
| F30264 Power unit: Braking chopper inhibited due to implausible DC link voltage | Cause: The braking chopper was inhibited because the unloaded DC link voltage continuously reaches or exceeds the chopper activation threshold. Remedy:
|
| F30265 Power unit: Line voltage failure detected | Cause: Line voltage failure was detected. Remedy:
|
| A30266 Power unit: Required modulator setting cannot be implemented | Cause: The required modulator setting was not able to be implemented. This can involve some undesirable effects (e.g. high switching losses). Remedy:
|
| A30267 Power unit: Active power overload | Cause: The alarm threshold for the active power overload of the power unit has been exceeded. Remedy:
|
| F30268 Power unit: Active power overload | Cause: The fault threshold for the active power overload of the power unit has been exceeded. Remedy:
|
| F30314 Power unit: 24 V power supply overloaded by the converter | Cause: The 24 V power supply is overloaded by the converter. An external 24V power supply is not connected to the converter via X124. Remedy:
|
| A30315 (F) Power unit: 24 V power supply overloaded by the converter | Cause: The 24 V power supply is overloaded by the converter. An external 24V power supply is not connected to the converter via X124. Remedy:
|
| A30502 Power unit: DC link overvoltage | Cause: The power unit has detected overvoltage in the DC link on a pulse inhibit. – Device supply voltage too high. – Line reactor incorrectly dimensioned. Remedy:
|
| C30603 SI: Module temperature – limit value exceeded | Cause: A safe monitoring function has detected that the module temperature has exceeded a limit value. STO (Safe Torque Off) was initiated. Remedy:
|
| F30604 SI: Safety EEPROM data error | Cause: Safety relevant EEPROM data are not correct. This message results in an STO (Safe Torque Off). Remedy:
|
| A30605 SI: Checksum error has occurred | Cause: A checksum error (CRC error) has occurred in the converter program memory. Remedy:
|
| C30649 SI: Internal software error | Cause: An internal error has occurred in the Safety Integrated software. This message results in an STO (Safe Torque Off) that cannot be acknowledged. Remedy:
|
| N30800 (F) Power unit: Group signal | Cause: The power unit has detected at least one fault. Remedy:
|
| F30801 Power unit DRIVE-CLiQ: Sign-of-life missing | Cause: There is a DRIVE-CLiQ communication error between the converter and the power unit involved. 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: Checksum error occurred | 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 (EEPROM access error or too many blocks). Remedy:
|
| F30809 Power unit: Switching information not valid | Cause: For 3P gating unit, the switching status word in the setpoint telegram is missing the end ID. Remedy:
|
| F30810 Power unit: Watchdog timer expired | Cause: The watchdog timer has expired. This can only be caused by a fatal software error. Remedy:
|
| F30815 Power unit: Processor clock signal error | Cause: The processor clock signal monitoring has signaled an error. This can involve the signal itself or its PLL. Remedy:
|
| F30820 Power unit DRIVE-CLiQ: Telegram error | Cause: There is a DRIVE-CLiQ communication error between the converter and the power unit involved. Fault value: Checksum error, length mismatch, or timing error. Remedy:
|
| F30835 Power unit DRIVE-CLiQ: Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error between the converter and the power unit involved. The nodes do not send and receive in synchronism. Remedy:
|
| F30836 Power unit DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: There is a DRIVE-CLiQ communication error between the converter and the power unit involved. Data were not able to be sent. Remedy:
|
| F30837 Power unit DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component involved. Faulty hardware cannot be excluded. Remedy:
|
| F30845 Power unit DRIVE-CLiQ: Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error between the converter and the power unit involved. Fault value: Synchronization error during alternating cyclic data transfer. Remedy:
|
| F30850 Power unit: Internal software error | Cause: An internal software error has occurred in the power unit. Remedy:
|
| F30851 Power unit DRIVE-CLiQ: Sign-of-life missing | Cause: There is a DRIVE-CLiQ communication error from the power unit involved to the converter. The DRIVE-CLiQ component did not set the sign-of-life to the converter. Fault value (r0949): 10 (0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
|
| A30853 Power unit: Sign-of-life error cyclic data | Cause: The power unit has detected that the cyclic setpoint telegrams of the converter have not been updated on time. Remedy: Check the converter and if required replace. |
| F30860 Power unit DRIVE-CLiQ: Telegram error | Cause: There is a DRIVE-CLiQ communication error from the power unit involved to the converter. Fault value (r0949):
Remedy:
|
| F30875 Power unit: power supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the converter signals that the supply voltage has failed. Error cause 9 (= 09 hex): The power supply voltage for the components has failed. Remedy:
|
| F30885 Power unit DRIVE-CLiQ: Cyclic data transfer error | Cause: The nodes do not send and receive in synchronism. Fault value (r0949):
Remedy:
|
| F30886 Power unit DRIVE-CLiQ: Error when sending DRIVE-CLiQ data | Cause: Data were not able to be sent. Error cause 65 (= 41 hex): The telegram type does not match send list. Remedy: Carry out a POWER ON. |
| F30887 Power unit DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component (power unit) involved. Faulty hardware cannot be excluded. Fault value (r0949): 32 (Header error), 35 (Receive buffer error), 66/67 (Send buffer error), 96 (Response too late), 97 (Characteristic data exchange too long). Remedy:
|
| F30895 Power unit DRIVE-CLiQ: Alternating cyclic data transfer error | Cause: Error cause 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON (switch-off/switch-on). |
| F30896 Power unit DRIVE-CLiQ: Component properties inconsistent | Cause: The properties of the DRIVE-CLiQ component (power unit) have changed in an incompatible fashion (e.g., cable or component replaced). Remedy:
|
| F30899 (N, A) Power unit: Unknown fault | Cause: A fault occurred on the power unit that cannot be interpreted by the converter firmware (firmware mismatch). Remedy:
|
| F30903 Power unit: I2C bus error occurred | Cause: Communications error with an EEPROM or an analog/digital converter. Fault value (r0949): 80000000 hex (Internal software error), 00000001…FFFF hex (Module fault). Remedy:
|
| 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, which cannot be interpreted by the converter firmware. Remedy:
|
| F31100 (N, A) Motor encoder: Zero mark distance error | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. Remedy:
|
| F31101 (N, A) Motor encoder: Zero mark failed | Cause: The 1.5 x parameterized zero mark distance was exceeded. Remedy:
|
| F31103 (N, A) Motor encoder: Zero mark signal level (track R) out of tolerance | Cause: The zero mark signal level (track R) does not lie within the tolerance bandwidth. Remedy:
|
| F31110 (N, A) Motor encoder: Serial communication faulted | Cause: Error in transfer of serial communication protocol. Fault value bits (0-15) indicate specific errors (Alarm bit, quiescent level, CRC, Timeout, etc.). Remedy:
|
| F31111 (N, A) Motor encoder: Encoder signals an internal error (detailed information) | Cause: The encoder error word provides detailed information. Fault value (r0949) bits:
Remedy:
|
| F31112 (N, A) Motor encoder: Encoder signals an internal error | Cause: The encoder signals an internal error via serial protocol. Remedy: In the case of an EnDat encoder, F31111 may provide further details. |
| F31115 (N, A) Motor encoder: Signal level track A or B too low | Cause: The signal level (root from A^2 + B^2) falls below the permissible limit. Nominal: 375-600 mV. Response threshold < 170 mV (< 256kHz). Remedy:
|
| F31116 (N, A) Motor encoder: Signal level track A or B too low | Cause: The signal level of the rectified encoder signals A and B fall below permissible limit. Remedy:
|
| F31117 (N, A) Motor encoder: Inversion signal A/B/R error | Cause: For a square-wave encoder, signals A*, B*, R* are not inverted with respect to A, B, R. Remedy:
|
| F31118 (N, A) Motor encoder: Speed change not plausible | Cause: For HTL/TTL encoder, speed change exceeded value in p0492 over several sampling cycles. Remedy:
|
| F31120 (N, A) Motor encoder: Encoder power supply fault | Cause: Encoder power supply fault detected (Undervoltage, Overcurrent, Overvoltage, Hardware fault). Remedy:
|
| F31121 (N, A) Motor encoder: Determined commutation position incorrect | Cause: A commutation position actual value sensing error was detected. Remedy: Check the encoder mounting, and if necessary, replace the encoder and/or the motor. |
| F31122 Motor encoder: Sensor Module hardware fault | Cause: Internal Sensor Module hardware fault (Reference voltage error, internal under/overvoltage). Remedy: Replace the corresponding Sensor Module or the motor. |
| F31123 (N, A) Motor encoder: Signal level A/B outside tolerance | Cause: The unipolar level (AP/AN or BP/BN) is outside permissible tolerance. Remedy:
|
| F31125 (N, A) Motor encoder: Signal level track A or B too high | Cause: The signal level (root from A^2 + B^2) exceeds the permissible limit value. Remedy:
|
| F31126 (N, A) Motor encoder: Signal level track A or B too high | Cause: The signal level (|A| + |B|) exceeds the permissible limit value. Remedy:
|
| F31129 (N, A) Motor encoder: Position difference, Hall sensor/track C/D and A/B too large | Cause: Error for track C/D or Hall signals is greater than limit (+/-15° mech or +/-60° elec). Remedy:
|
| F31130 (N, A) Motor encoder: Zero mark and position error from the coarse synchronization | Cause: After initializing pole position, zero mark was detected outside permissible range. Remedy:
|
| F31131 (N, A) Motor encoder: Position deviation incremental/absolute too high | Cause: Excessive difference between incremental and absolute position detected. Remedy:
|
| F31135 Motor encoder: Fault when determining the position (singleturn) | Cause: The encoder identified a position determination fault (singleturn). Fault value contains status bits (0-31) indicating specific errors (Signal, LED, Overvoltage, etc.). Remedy:
|
| F31136 Motor encoder: Fault when determining the position (multiturn) | Cause: The encoder identified a position determination fault (multiturn). Fault value contains status bits (0-31). Remedy:
|
| F31137 Motor encoder: Fault when determining the position (singleturn) | Cause: Position determination fault in DRIVE-CLiQ encoder. Fault value indicates specific hardware/software errors (FPGA, memory, temperature, etc.). Remedy:
|
| F31138 Motor encoder: Fault when determining the position (multiturn) | Cause: Position determination fault (multiturn) in DRIVE-CLiQ encoder. Remedy:
|
F31138 Motor encoder: Fault when determining the position (multiturn) Fault cause: %1 bin | Cause: A position determination fault has occurred in the DRIVE-CLiQ encoder. Fault value (r0949, interpret binary): yyxxxxxx hex: yy = encoder version, xxxxxx = bit coding of the fault cause For yy = 8 (0000 1000 bin):
For yy = 11 (0000 1011 bin):
For yy = 14 (0000 1110 bin):
Remedy:
|
F31142 (N, A) Motor encoder: Battery voltage error | 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) Motor encoder: Initialization error %1 | Cause: Encoder functionality selected in p0404 cannot be executed. Fault value (r0949, interpret hexadecimal): Encoder malfunction. The bit assignment corresponds to that of p0404 (e.g. bit 5 set: Error track C/D). See also: p0404, p0491. Remedy:
|
F31151 (N, A) Motor encoder: Encoder speed for initialization too high %1 | 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). See also: p0437 (Sensor Module configuration extended) |
F31152 (N, A) Motor encoder: Maximum signal frequency (track A/B) exceeded %1 | Cause: The maximum signal frequency of the encoder evaluation has been exceeded. Fault value (r0949, interpret decimal): Actual signal frequency in Hz. See also: p0408 (Rotary encoder pulse number) Remedy:
|
F31153 (N, A) Motor encoder: Identification error %1 | Cause: An error has occurred when identifying the encoder (waiting) p0400 = 10100. The connected encoder was not able to be identified. Fault value (r0949, interpret binary): Bit 0: Data length incorrect. See also: p0400 (Encoder type selection) Remedy: Manually configure the encoder according to the data sheet. |
A31400 (F, N) Motor encoder: Zero mark distance error (alarm threshold exceeded) Position/speed actual value incorrect or not available (11), Value: %1 | 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. The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder). Alarm value (r2124, interpret decimal): Last measured zero mark distance in increments (4 increments = 1 encoder pulse). Remedy:
|
A31401 (F, N) Motor encoder: Zero marked failed (alarm threshold is exceeded) Position/speed actual value incorrect or not available (11), Value: %1 | Cause: The 1.5x parameterized zero mark distance was exceeded without a zero mark being detected. The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder). Alarm value (r2124, interpret decimal): Number of increments after POWER ON or since the last zero mark that was detected. Remedy:
|
F31405 (N, A) Motor encoder: Temperature in the encoder evaluation exceeded Overtemperature of the electronic components (6) | Cause: An inadmissibly high temperature was detected in the encoder electronics or the encoder evaluation. Fault value (r0949, interpret hexadecimal): yyxxxx hex: yy = temperature sensor number, xxxx = measured module temperature in 0.1 °C. Remedy: When using a Sensor Module: Reduce the ambient temperature of the Sensor Module. Otherwise: Reduce the encoder ambient temperature. |
A31407 (F, N) Motor encoder: Function limit reached %1 | Cause: The encoder has reached one of its function limits. A service is recommended. Alarm value (r2124, interpret decimal): 1: Incremental signals 3: Absolute track 4: Code connection Remedy: Perform service. Replace the encoder if necessary. Note: The actual functional reserve of an encoder can be displayed via r4651. |
A31410 (F, N) Motor encoder: Communication error (encoder and Sensor Module) Fault cause: %1 bin | Cause: Serial communication protocol transfer error between the encoder and evaluation module. Alarm value (r2124, interpret binary):
Remedy:
|
A31411 (F, N) Motor encoder: Encoder signals an internal alarm (detailed information) Fault cause: %1 bin, additional information: %2 | Cause: The absolute encoder fault word includes alarm bits that have been set. Alarm value (r2124, interpret binary): yyyyxxxx hex: yyyy = supplementary information, xxxx = fault cause yyyy = 0:
yyyy = 1:
See also: p0491 Remedy: Replace encoder. |
A31412 (F, N) Motor encoder: Encoder signals an internal alarm %1 | Cause: The encoder signals an internal alarm via serial protocol. Alarm value (r2124, interpret binary): Bit 0: Fault bit in the position protocol. Bit 1: Alarm bit in the position protocol. Remedy:
|
A31414 (F, N) Motor encoder: Signal level track C or D out of tolerance C track: %1, D track: %2 | Cause: The signal level (C^2 + D^2) of track C or D of the encoder or from the Hall signals, is not within the tolerance bandwidth. The nominal signal level of the encoder must lie in the range 375 mV to 600 mV. Alarm value (r2124, interpret hexadecimal): yyyyxxxx hex (yyyy = D track, xxxx = C track). Remedy:
|
N31415 (F, A) Motor encoder: Signal level track A or B out of tolerance (alarm) Amplitude: %1, Angle: %2 | Cause: The signal level (root from A^2 + B^2) of the encoder is outside the permissible tolerance. The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %). Alarm value (r2124, interpret hexadecimal): yyyyxxxx hex (yyyy = angle, xxxx = amplitude). Remedy:
|
A31418 (F, N) Motor encoder: Speed change not plausible (alarm) %1 | Cause: For an HTL/TTL encoder, the speed change has exceeded the value in p0492 over several sampling cycles. See also: p0492 (Maximum speed difference per sampling cycle). Remedy:
|
A31419 (F, N) Motor encoder: Track A or B out of tolerance %1 | Cause: The amplitude/phase/offset correction for track A or B is at the limit. Amplitude error correction: Amplitude B / Amplitude A = 0.78 … 1.27 Phase: <84 degrees or >96 degrees Alarm value (r2124, interpret hexadecimal):
Remedy:
|
A31421 (F, N) Motor encoder: Determined commutation position incorrect (alarm) %1 | Cause: A commutation position actual value sensing error was detected. Alarm value = 3: The absolute position of the serial protocol and track A/B differ by half an encoder pulse. The absolute position must have its zero position in the quadrants in which both tracks are negative. Remedy: For alarm value = 3:
|
A31422 (F, N) Motor encoder: Number of square-wave encoder pulses outside tolerance band %1 | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. This alarm is triggered with active square-wave encoder PPR correction if the accumulator contains larger values than p4683 or p4684. Alarm value (r2124, interpret decimal): accumulated differential pulses in encoder pulses. Remedy:
|
A31429 (F, N) Motor encoder: Position difference, Hall sensor/track C/D and A/B too large %1 | 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. The monitoring responds if, for example, Hall sensors are connected as equivalent for the C/D tracks with the incorrect direction of rotation or supply values that are not accurate enough. Remedy:
|
A31431 (F, N) Motor encoder: Position deviation incremental/absolute too high (alarm) %1 | Cause: When the zero pulse is passed, a deviation in the incremental position was detected. Alarm value (r2124, interpret decimal): Deviation in quadrants (1 pulse = 4 quadrants). Remedy:
|
A31432 (F, N) Motor encoder: Rotor position adaptation corrects deviation %1 | Cause: On track A/B, pulses have been lost or too many have been counted. These pulses are presently being corrected. Alarm value (r2124, interpret decimal): Last measured deviation of zero mark in increments (4 increments = 1 encoder pulse). Remedy:
|
A31442 (F, N) Motor encoder: Battery voltage alarm threshold reached | 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) Motor encoder: Signal level track C/D outside tolerance (alarm) Fault cause: %1 bin | Cause: The unipolar level (CP/CN or DP/DN) for the motor encoder is outside the permissible tolerance. Alarm value (r2124, interpret binary): Bit 0 = 1: Either CP or CN outside the tolerance. Bit 16 = 1: Either DP or DN outside the tolerance. Remedy:
|
A31470 (F, N) Motor encoder: Encoder signals an internal error (X521.7) | Cause: For the Sensor Module Cabinet 30 (SMC30), a dirty encoder is signaled via a 0 signal at terminal X521.7. Remedy:
|
F31500 (N, A) Motor encoder: Position tracking traversing range exceeded | Cause: For a configured linear axis without modulo correction, the drive/encoder has exceeded the maximum possible traversing range. The value should be read in p0412 and interpreted as the number of motor revolutions. Remedy: The fault should be resolved as follows:
The fault should then be acknowledged and the absolute encoder adjusted. |
F31501 (N, A) Motor encoder: Position tracking encoder position out of tolerance window %1 | 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. Fault value (r0949, interpret decimal): Deviation (difference) to the last encoder position in increments of the absolute value. Remedy: Reset the position tracking as follows:
The fault should then be acknowledged. |
F31502 (N, A) Motor encoder: Encoder with measuring gearbox without valid signals | Cause: The encoder with measuring gearbox no longer provides any valid signals. Remedy: It must be ensured that all of the encoders, with mounted measuring gearbox, provide valid actual values in operation. |
F31503 (N, A) Motor encoder: Position tracking cannot be reset | Cause: The position tracking for the measuring gearbox cannot be reset. Remedy: The fault should be resolved as follows:
The fault should then be acknowledged and the absolute encoder adjusted. |
A31700 Motor encoder: Functional safety monitoring initiated Fault cause: %1 bin | Cause: Functional safety was activated. Self test of the DRIVE-CLiQ encoder has detected a fault. Alarm value (r2124, interpret binary): Bit x = 1: Effectivity test x unsuccessful. Remedy: Replace encoder. |
N31800 (F) Motor encoder: Group signal | Cause: The motor encoder has detected at least one fault. See also: p0491 Remedy: Evaluate the other messages that are presently available. |
F31801 (N, A) Motor encoder DRIVE-CLiQ: Sign-of-life missing Component number: %1, fault cause: %2 | Cause: There is a DRIVE-CLiQ communication error between the converter and the encoder involved. Fault value (r0949, interpret hexadecimal): 0000yyxx hex (yy = component number, xx = fault cause). Error cause 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
|
F31802 (N, A) Motor encoder: Time slice overflow %1 | Cause: A time slice overflow for the motor encoder has occurred. Fault value (r0949, interpret hexadecimal): yx hex: y = function involved, x = time slice involved (9, A, C). yx = 3E7: Timeout when waiting for SYNO. Remedy: Increase the current controller sampling time. |
F31804 (N, A) Motor encoder: Sensor Module checksum error %1 | Cause: A checksum error has occurred when reading-out the program memory on the Sensor Module. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex (yyyy: Memory area involved, xxxx: Difference). Remedy:
|
F31805 (N, A) Motor encoder: EEPROM checksum error %1 | Cause: Data in the EEPROM corrupted. Fault value (r0949, interpret hexadecimal): 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy: Replace the module. |
F31806 (N, A) Motor encoder: Initialization error %1 | Cause: The encoder was not successfully initialized. Fault value (r0949, interpret binary):
Remedy: Acknowledge fault. If the fault cannot be acknowledged:
|
A31811 (F, N) Motor encoder: Encoder serial number changed | Cause: The serial number of the motor encoder of a synchronous motor has changed. Cause 1: The encoder was replaced. Cause 2: A third-party, built-in or linear motor was re-commissioned. Cause 3: The motor with integrated and adjusted encoder was replaced. Cause 4: The firmware was updated to a version that checks the encoder serial number. Remedy: For causes 1, 2: Carry out an automatic adjustment using the pole position identification routine (p1990 = 1). For causes 3, 4: Accept the new serial number by copying from r0460 to p0441. |
F31812 (N, A) Motor encoder: Requested cycle or RX/TX timing not supported %1 | Cause: A cycle or RX/TX timing requested by the converter is not supported. Fault value (r0949, interpret decimal): 0: Application cycle is not supported. 1: DRIVE-CLiQ cycle is not supported. 2: Distance between RX and TX instants in time too low. 3: TX instant in time too early. Remedy: Carry out a POWER ON (switch-off/switch-on) for all components. |
F31813 Motor encoder: Hardware logic unit failed Fault cause: %1 bin | Cause: The logic unit of the DRIVE-CLiQ encoder has failed. Fault value (r0949, interpret binary): Bit 0: ALU watchdog has responded. Bit 1: ALU has detected a sign-of-life error. Remedy: When the error reoccurs, replace the encoder. |
| F31820 (N, A) Motor encoder DRIVE-CLiQ: Telegram error | Cause: There is a DRIVE-CLiQ communication error between the converter and the encoder involved. Fault value (r0949, interpret hexadecimal): 0000yyxx hex (yy = component number, xx = fault cause). Error 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. See also: p0491 (Motor encoder fault response ENCODER) Remedy:
|
| F31835 (N, A) Motor encoder DRIVE-CLiQ: Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error between the converter and the encoder involved. The nodes do not send and receive in synchronism. Fault value (r0949, interpret hexadecimal): 0000yyxx hex (yy = component number, xx = fault cause). Error 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. See also: p0491 (Motor encoder fault response ENCODER) Remedy:
|
| F31836 (N, A) Motor encoder DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: There is a DRIVE-CLiQ communication error between the converter and the encoder involved. Data were not able to be sent. Fault value (r0949, interpret hexadecimal): 0000yyxx hex (yy = component number, xx = fault cause). Error cause: 65 (= 41 hex): Telegram type does not match send list. See also: p0491 (Motor encoder fault response ENCODER) Remedy: Carry out a POWER ON. |
| F31837 (N, A) Motor encoder DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component involved. Faulty hardware cannot be excluded. Fault value (r0949, interpret hexadecimal): 0000yyxx hex (yy = component number, xx = fault cause). Error 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. See also: p0491 (Motor encoder fault response ENCODER) Remedy:
|
| F31845 (N, A) Motor encoder DRIVE-CLiQ: Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error between the converter and the encoder involved. Fault value (r0949, interpret hexadecimal): 0000yyxx hex (yy = component number, xx = fault cause). Error cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. See also: p0491 (Motor encoder fault response ENCODER) Remedy: Carry out a POWER ON (switch-off/switch-on). |
| F31850 (N, A) Motor encoder: Encoder evaluation internal software error | Cause: An internal software error has occurred in the Sensor Module of the motor encoder. Fault value (r0949, interpret decimal): 1: Background time slice is blocked. 2: Checksum over the code memory is not correct. 10000: OEM memory of the EnDat encoder contains data that cannot be interpreted. 11000 … 11499: Descriptive data from EEPROM incorrect. 11500 … 11899: Calibration data from EEPROM incorrect. 11900 … 11999: Configuration data from EEPROM incorrect. 12000 … 12008: communication with analog/digital converter faulted. 16000: DRIVE-CLiQ encoder initialization application error. 16001: DRIVE-CLiQ encoder initialization ALU error. 16002: DRIVE-CLiQ encoder HISI / SISI initialization error. 16003: DRIVE-CLiQ encoder safety initialization error. 16004: DRIVE-CLiQ encoder internal system error. See also: p0491 Remedy:
|
| F31851 (N, A) Encoder 1 DRIVE-CLiQ: Sign-of-life missing | Cause: There is a DRIVE-CLiQ communication error from the Sensor Module involved (encoder 1) to the converter. The DRIVE-CLiQ component did not set the sign-of-life to the converter. Fault value (r0949, interpret hexadecimal): 0000yyxx hex (yy = component number, xx = fault cause). Error cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
|
| F31860 (N, A) Encoder 1 DRIVE-CLiQ: Telegram error | Cause: There is a DRIVE-CLiQ communication error from the Sensor Module involved (encoder 1) to the converter. Fault value (r0949, interpret hexadecimal): 0000yyxx hex (yy = component number, xx = fault cause). Error 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. 9 (= 09 hex): The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the converter 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. Remedy:
|
| F31875 (N, A) Motor encoder: Supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the converter signals that the supply voltage has failed. Fault value (r0949, interpret hexadecimal): 0000yyxx hex. Error cause: 9 (= 09 hex): The power supply voltage for the components has failed. Remedy:
|
| F31885 (N, A) Encoder 1 DRIVE-CLiQ: Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error between the Sensor Module involved (encoder 1) and the converter. The nodes do not send and receive in synchronism. Fault value (r0949, interpret hexadecimal): 0000yyxx hex. Error 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. Remedy:
|
| F31886 (N, A) Encoder 1 DRIVE-CLiQ: Error when sending DRIVE-CLiQ data | Cause: There is a DRIVE-CLiQ communication error from the Sensor Module involved (encoder 1) to the converter. Data were not able to be sent. Fault value (r0949, interpret hexadecimal): 0000yyxx hex. Error cause: 65 (= 41 hex): Telegram type does not match send list. Remedy: Carry out a POWER OFF/ON. |
| F31887 (N, A) Motor encoder DRIVE-CLiQ: Component fault | Cause: A fault has been detected on the DRIVE-CLiQ component involved (Sensor Module for the motor encoder). Faulty hardware cannot be excluded. Fault value (r0949, interpret hexadecimal): 0000yyxx hex. Error 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. Remedy:
|
| F31895 (N, A) Encoder 1 DRIVE-CLiQ: Alternating cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error from the Sensor Module involved (encoder 1) to the converter. Error cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Fault value (r0949, interpret hexadecimal): 0000yyxx hex. Remedy: Carry out a POWER ON. |
| F31896 (N, A) Motor encoder DRIVE-CLiQ: Component properties inconsistent | Cause: The properties of the DRIVE-CLiQ component (Sensor Module for the motor encoder), specified by the fault value, have changed in an incompatible fashion with respect to the properties when running up. 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:
|
| F31899 (N, A) Motor encoder: Unknown fault | Cause: A fault occurred on the Sensor Module for encoder 1 that cannot be interpreted by the converter firmware. This can occur if the firmware on this component is more recent than the firmware on the converter. Fault value (r0949, interpret decimal): Fault number. See also: p0491 Remedy:
|
| A31902 (F, N) Motor encoder: SPI-BUS error occurred | Cause: Error when operating the internal SPI bus. Alarm value (r2124, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| A31903 (F, N) Motor encoder: I2C-BUS error occurred | Cause: Error when operating the internal I2C bus. Alarm value (r2124, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F31905 (N, A) Motor encoder: Encoder parameterization error | Cause: An error was identified in the encoder parameterization. It is possible that the parameterized encoder type does not match the connected encoder. Fault value (r0949, interpret decimal): yyyyxxxx dec (yyyy = supplementary information, xxxx = parameter) xxxx = 421: For an EnDat/SSI encoder, the absolute position in the protocol must be less than or equal to 30 bits. xxxx = 12008: Compares the configuration with the properties of the Sensor Module (p0430 with r0458 or p0437 with r0459). yyyy = 0: No additional information available. yyyy = 1: The component does not support HTL level combined with track monitoring A/B <> -A/B. yyyy = 2: A code number for an identified encoder has been entered into p0400, however, no identification was carried out. yyyy = 3: A code number for an identified encoder has been entered into p0400, however, no identification was carried out. yyyy = 4: This component does not support SSI encoders without track A/B. yyyy = 5: For SQW encoder, value in p4686 greater than in p0425. yyyy = 6: DRIVE-CLiQ encoder cannot be used with this firmware version. yyyy = 7: For an SQW encoder, the XIST1 correction is only permitted for equidistant zero marks. yyyy = 8: The motor pole pair width is not supported by the linear scale being used. yyyy = 9: The length of the position in the EnDat protocol may be a maximum of 32 bits. yyyy = 10: The connected encoder is not supported. yyyy = 11: The hardware does not support track monitoring. Remedy:
|
| F31912 Motor encoder: Device combination is not permissible | Cause: The selected device combination is not supported. Fault value (r0949, interpret decimal): 1003: Connected measuring unit cannot be operated with the EnDat 2.2 converter. 1005: The type of measuring unit (incremental) is not supported by the EnDat 2.2 converter. 1006: The maximum duration of the EnDat transfer (31.25 µs) was exceeded. 2001: The set combination of current controller cycle, DP cycle and Safety cycle is not supported by the EnDat 2.2 converter. 2002: The resolution of the linear measuring unit does not match the pole pair width of the linear motor. Remedy:
|
| A31915 (F, N) Motor encoder: Encoder configuration error | Cause: The motor encoder configuration is incorrect. Alarm value (r2124, interpret decimal): 1: Re-parameterization between fault/alarm is not permissible. 2: The cyclic DQ receive telegram is too long and is limited. 3: The cyclic DQ send telegram is too long and is limited. 419: When the fine resolution Gx_XIST2 is configured, the encoder identifies a maximum possible absolute position actual value (r0483) that can no longer be represented within 32 bits. Remedy:
|
| F31916 (N, A) Motor encoder: Encoder parameterization error | Cause: An encoder parameter was detected as being incorrect. It is possible that the parameterized encoder type does not match the connected encoder. Fault value (r0949, interpret decimal): Parameter number. See also: p0491 Remedy:
|
| F31950 Motor encoder: Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): The fault value contains information regarding the fault source. Only for internal Siemens troubleshooting. Remedy:
|
| A31999 (F, N) Motor encoder: Unknown alarm | Cause: An alarm occurred on the Sensor Module for encoder 1, which cannot be interpreted by the converter firmware. This can occur if the firmware on this component is more recent than the converter firmware. Alarm value (r2124, interpret decimal): Alarm number. 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. For distance-coded encoders, the zero mark distance is determined from zero marks detected pairs. Fault value (r0949, interpret decimal): Last measured zero mark distance in increments (4 increments = 1 encoder pulse). Remedy:
|
| F32101 (N, A) Encoder 2: Zero mark failed | Cause: The 1.5 x parameterized zero mark distance was exceeded. Fault value (r0949, interpret decimal): Number of increments after POWER ON or since the last zero mark that was detected (4 increments = 1 encoder pulse). Remedy:
|
| F32103 (N, A) Encoder 2: Signal level zero track (track R) outside tolerance | Cause: The zero mark signal level (track R) does not lie within the tolerance bandwidth for encoder 2. The fault can be initiated when the unipolar voltage level is exceeded (RP/RN) or if the differential amplitude is undershot. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex (yyyy = 0, xxxx = Signal level, track R 16 bits with sign). The response thresholds of the unipolar signal levels are between < 1400 mV and > 3500 mV. The response threshold for the differential signal level is < -1600 mV. Remedy:
|
| F32110 (N, A) Encoder 2: Serial communications error | Cause: There is an error in the transfer of the serial communication protocol between the encoder and internal or external evaluation module. Fault value (r0949, interpret binary) for EnDat 2.1 encoder: Bit 0: Alarm bit in the position protocol. Bit 1: Incorrect quiescent level on the data line. Bit 2: Encoder does not respond. Bit 3: CRC error. Bit 4: Encoder acknowledgment error. Bit 5: Internal error in the serial driver. Bit 6: Timeout when cyclically reading. Bit 7: Timeout for the register communication. Bit 8: Protocol is too long. Bit 9: Receive buffer overflow. Bit 10: Frame error when reading twice. Bit 11: Parity error. Bit 12: Data line signal level error during the monoflop time. Bit 13: Data line incorrect. Bit 14: Register communication error. Bit 15: Internal communication error. Remedy:
|
| F32111 (N, A) Encoder 2: Encoder signals an internal error (detailed information) | Cause: The encoder error word provides detailed information (error bit). Fault value (r0949, interpret binary): Bit 0: Lighting system failed. Bit 1: Signal amplitude too low. Bit 2: Position value incorrect. Bit 3: Encoder power supply overvoltage condition. Bit 4: Encoder power supply undervoltage condition. Bit 5: Encoder power supply overcurrent condition. Bit 6: The battery must be changed. Remedy:
|
| F32115 (N, A) Encoder 2: Signal level track A or B too low | Cause: The signal level (root from A^2 + B^2) of the encoder falls below the permissible limit value. The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %). The response threshold is < 170 mV (input frequency <= 256 kHz) or < 120 mV (input frequency > 256 kHz). Remedy:
|
| F32116 (N, A) Encoder 2: Signal level track A or B too low | Cause: The signal level of the rectified encoder signals A and B of the encoder fall below the permissible limit value. The nominal signal level of the encoder must lie in the range 375 mV to 600 mV. The response threshold is < 130 mV. 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. Fault value (r0949, interpret binary): Bits 0…15 (Internal), Bit 16 (Track A), Bit 17 (Track B), Bit 18 (Track R). Remedy:
|
| F32118 (N, A) Encoder 2: Speed change not plausible | Cause: For an HTL/TTL encoder, the speed change has exceeded the value in p0492 over several sampling cycles. See also: p0492. Remedy:
|
| F32120 (N, A) Encoder 2: Encoder power supply fault | Cause: An encoder power supply fault was detected. Fault value (r0949, interpret binary): Bit 0: Undervoltage condition on the sense line. Bit 1: Overcurrent condition for the encoder power supply. Bit 2: Overcurrent condition on cable resolver excitation negative. Bit 3: Overcurrent condition on cable resolver excitation positive. Bit 4: The 24 V power supply via the inverter is overloaded. Bit 5: Overcurrent at the EnDat connection of the converter. Bit 6: Overvoltage at the EnDat connection of the converter. Bit 7: Hardware fault at the EnDat connection of the converter. Note: If encoder cables are interchanged, this can result in the encoder being destroyed. Remedy:
|
| F32121 (N, A) Encoder 2: Determined commutation position incorrect | Cause: A commutation position actual value sensing error was detected. Remedy:
|
| F32122 Encoder 2: Sensor Module hardware fault | Cause: An internal Sensor Module hardware fault was detected. Fault value (r0949): 1: Reference voltage error. 2: Internal undervoltage. 3: Internal overvoltage. Remedy:
|
| F32123 (N, A) Encoder 2: Signal level A/B outside tolerance | Cause: The unipolar level (AP/AN or BP/BN) for encoder 2 is outside the permissible tolerance. The unipolar nominal signal level must lie in the range 2500 mV +/- 500 mV. Response thresholds are < 1700 mV and > 3300 mV. Remedy:
|
| F32125 (N, A) Encoder 2: Signal level track A or B too high | Cause: The signal level (root from A^2 + B^2) of the encoder exceeds the permissible limit value. Nominal range: 375 mV to 600 mV. Response threshold > 750 mV. Remedy:
|
| F32126 (N, A) Encoder 2: Signal level track A or B too high | Cause: The signal level (|A| + |B|) of the encoder exceeds the permissible limit value. Response threshold for (|A| + |B|) is > 1120 mV or the root of (A^2 + B^2) > 955 mV. 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. Possible incorrect direction of rotation or supply values not accurate enough. Remedy:
|
| F32130 (N, A) Encoder 2: Zero mark and position error from the coarse synchronization | Cause: After initializing the pole position, the zero mark was detected outside the permissible range. Track C/D: Angular range +/-18° mechanical. Hall sensors: Angular range +/-60° electrical. Remedy:
|
| F32131 (N, A) Encoder 2: Position deviation incremental/absolute too high | Cause: Excessively high difference detected between incremental and absolute position (for absolute encoders) or deviation in incremental position when zero pulse passed. Remedy:
|
| F32135 Encoder 2: Fault when determining the position (single turn) | Cause: The encoder has identified a position determination fault (singleturn) and supplies status information. Fault value (r0949) contains bit code (e.g., lighting, signal amplitude, overvoltage). Remedy:
|
| F32136 Encoder 2: Fault when determining the position (multiturn) | Cause: The encoder has identified a position determination fault (multiturn). Fault value (r0949) contains bit code (e.g., multiturn position error, battery error). Remedy:
|
| F32137 Encoder 2: Fault when determining the position (single turn) | Cause: A position determination fault has occurred in the DRIVE-CLiQ encoder. Fault value (r0949) bits indicate specific issues (e.g., signal monitoring, LED monitoring, temperature, FPGA error). Remedy:
|
| F32138 Encoder 2: Fault when determining the position (multiturn) | Cause: A position determination fault has occurred in the DRIVE-CLiQ encoder (multiturn specific). Remedy:
|
| F32142 (N, A) Encoder 2: Battery voltage fault | Cause: The battery voltage to back up the multiturn information is no longer sufficient. Remedy:
|
| F32150 (N, A) Encoder 2: Initialization error | Cause: Encoder functionality selected in p0404 cannot be executed. The bit assignment corresponds to that of p0404 (e.g. bit 5 set: Error track C/D). 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 signal frequency (track A/B) exceeded | Cause: The maximum signal 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. Remedy:
|
| A32400 (F, N) Encoder 2: Zero mark distance error (alarm threshold exceeded) | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance (p0425/p0424). Remedy:
|
| A32401 (F, N) Encoder 2: Zero mark failed (alarm threshold exceeded) | Cause: The 1.5x parameterized zero mark distance was exceeded without a zero mark being detected. Remedy:
|
| F32405 (N, A) Encoder 2: Temperature in the encoder evaluation exceeded | Cause: An inadmissibly high temperature was detected in the encoder electronics or the encoder evaluation. Remedy:
|
| A32407 (F, N) Encoder 2: Function limit reached | Cause: The encoder has reached one of its function limits (Incremental signals, Absolute track, Code connection). Remedy:
|
| A32410 (F, N) Encoder 2: Communication error (encoder and Sensor Module) | Cause: Serial communication protocol transfer error. Remedy:
|
| A32411 (F, N) Encoder 2: Encoder signals an internal alarm (detailed information) | Cause: The absolute encoder fault word includes alarm bits that have been set (e.g. freq exceeded, temp exceeded, battery discharged). Remedy:
|
| A32412 (F, N) Encoder 2: Encoder signals an internal alarm | Cause: The encoder signals an internal alarm via serial protocol. Remedy:
|
| A32414 (F, N) Encoder 2: Signal level track C or D out of tolerance | Cause: The signal level (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: Signal level track A or B outside tolerance (alarm) | Cause: The signal level (root from A^2 + B^2) of the encoder is outside the permissible tolerance. Remedy:
|
| A32418 (F, N) Encoder 2: Speed change not plausible (alarm) | Cause: For an HTL/TTL encoder, the speed change has exceeded the value in p0492 over several sampling cycles. 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: Determined commutation position incorrect (alarm) | Cause: A commutation position actual value sensing error was detected. Alarm value 3: The absolute position of the serial protocol and track A/B differ by half an encoder pulse. 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: Position deviation incremental/absolute too high (alarm) | 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: On 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 alarm threshold reached | Cause: The encoder uses a battery to back up the multiturn information. The battery voltage has dropped. Remedy:
|
| A32443 (F, N) Encoder 2: Signal level track C/D outside tolerance (alarm) | Cause: The unipolar level (CP/CN or DP/DN) for encoder 2 is outside the permissible tolerance. Remedy:
|
| A32470 (F, N) Encoder 2: Encoder signals an internal error (X521.7) | Cause: For 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 gearbox without valid signals | Cause: The encoder with measuring gearbox no longer provides any valid signals. Remedy:
|
| F32503 (N, A) Encoder 2: Position tracking cannot be reset | Cause: The position tracking for the measuring gearbox cannot be reset. Remedy: The fault should be resolved as follows:
The fault should then be acknowledged and the absolute encoder adjusted. |
| 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. Alarm value (r2124): Bit x = 1: Effectivity test x unsuccessful. Remedy: Replace encoder. |
| N32800 (F) Encoder 2: Group signal | Cause: The motor encoder has detected at least one fault. Remedy: Evaluation of other active messages. |
| F32801 (N, A) Encoder 2 DRIVE-CLiQ: Sign-of-life missing | Cause: There is a DRIVE-CLiQ communication error between the converter and the encoder involved. Fault value (r0949): 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
|
| F32802 (N, A) Encoder 2: Time slice overflow | Cause: A time slice overflow has occurred in encoder 2. Fault value (r0949, hexadecimal): x = 9: Time slice overflow of the fast (current controller clock cycle) time slice. x = A: Time slice overflow of the average time slice. x = C: Time slice overflow of the slow time slice. yx = 3E7: Timeout when waiting for SYNO. Remedy: Increase the current controller sampling time. Note: For a current controller sampling time = 31.25 µs, use an SMx20. |
| F32804 (N, A) Encoder 2: Sensor Module checksum error | Cause: A checksum error has occurred when reading-out the program memory on the Sensor Module. yyyy: Memory area involved. xxxx: Difference between the checksum at POWER ON and the actual checksum. Remedy:
|
| F32805 (N, A) Encoder 2: EEPROM checksum error | Cause: Data in the EEPROM corrupted. 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy: Replace the module. |
| F32806 (N, A) Encoder 2: Initialization error | Cause: The encoder was not successfully initialized. Fault value (r0949) indicates detailed bit failures (e.g., Bit 0, 1: Initialization failed with motor rotating; Bit 2-20: Voltage matching/safety errors; Bit 28-31: EnDat measurement errors). Remedy: Acknowledge fault. If the fault cannot be acknowledged:
|
| 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). – The encoder was replaced. Remedy: Mechanically adjust the encoder. Accept the new serial number by copying from r0460 to p0441. |
| F32812 (N, A) Encoder 2: Requested cycle or RX-/TX timing not supported | Cause: A cycle or RX/TX timing requested by the converter is not supported. 0: Application cycle is not supported. 1: DRIVE-CLiQ cycle is not supported. 2: Distance between RX and TX instants in time too low. 3: TX instant in time too early. Remedy: Carry out a POWER ON (switch-off/switch-on) for all components. |
| F32813 Encoder 2: Hardware logic unit failed | Cause: The logic unit of the DRIVE-CLiQ encoder has failed. Bit 0: ALU watchdog has responded. Bit 1: ALU has detected a sign-of-life error. Remedy: When the error reoccurs, replace the encoder. |
| F32820 (N, A) Encoder 2 DRIVE-CLiQ: Telegram error | Cause: There is a DRIVE-CLiQ communication error between the converter and the encoder involved. 1: Checksum error (CRC error). 2: Telegram shorter than specified. 3: Telegram longer than specified. 4: Length does not match receive list. 5: Type does not match receive list. 16: Receive telegram is too early. Remedy:
|
| F32835 (N, A) Encoder 2 DRIVE-CLiQ: Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error between the converter and the encoder involved. The nodes do not send and receive in synchronism. 33: Cyclic telegram not received. 34: Timeout in telegram receive list. 64: Timeout in telegram send list. Remedy:
|
| F32836 (N, A) Encoder 2 DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: There is a DRIVE-CLiQ communication error. Data were not able to be sent. 65: Telegram type does not match send list. Remedy: Carry out a POWER ON. |
| F32837 (N, A) Encoder 2 DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component involved. Faulty hardware cannot be excluded. 32: Error in telegram header. 35: Receive error (buffer memory). 66: Send error (buffer memory). Remedy:
|
| F32845 (N, A) Encoder 2 DRIVE-CLiQ: Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error between the converter and the encoder involved. 11: Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON (switch-off/switch-on). |
| 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 values indicate memory/calibration/configuration errors (e.g., 10000, 11000, 12000, 16000 series). Remedy:
|
| F32851 (N, A) Encoder 2 DRIVE-CLiQ: Sign-of-life missing | Cause: There is a DRIVE-CLiQ communication error. The DRIVE-CLiQ component did not set the sign-of-life. 10: The sign-of-life bit in the receive telegram is not set. Remedy:
|
| F32860 (N, A) Encoder 2 DRIVE-CLiQ: Telegram error | Cause: There is a DRIVE-CLiQ communication error. 1: Checksum error. 2-4: Length mismatch. 9: Supply voltage failed signal. 16-25: Timing/Early telegram errors. Remedy:
|
| F32875 (N, A) Encoder 2: power supply voltage failed | Cause: The DRIVE-CLiQ communication signals that the supply voltage has failed. 9: The power supply voltage for the components has failed. Remedy:
|
| F32885 (N, A) Encoder 2 DRIVE-CLiQ: Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error. The nodes do not send and receive in synchronism. 26: Sign-of-life bit not set / early telegram. 33: Cyclic telegram not received. 34: Timeout in receive list. 98: Error at transition to cyclic operation. Remedy:
|
| F32886 (N, A) Encoder 2 DRIVE-CLiQ: Error when sending DRIVE-CLiQ data | Cause: There is a DRIVE-CLiQ communication error. Data were not able to be sent. 65: Telegram type does not match send list. Remedy: Carry out a POWER ON. |
| F32887 (N, A) Encoder 2 DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component involved (Sensor Module for encoder 2). 32: Error in telegram header. 35: Receive error. 66, 67: Send error. 96: Response received too late. 97: Time taken to exchange characteristic data too long. Remedy:
|
| F32895 (N, A) Encoder 2 DRIVE-CLiQ: Alternating cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error. 11: Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON. |
| F32896 (N, A) Encoder 2 DRIVE-CLiQ: Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (Sensor Module) have changed in an incompatible fashion (e.g. cable or component replaced). Remedy:
|
| F32899 (N, A) Encoder 2: Unknown fault | Cause: A fault occurred on the Sensor Module which cannot be interpreted by the converter firmware (firmware on component is more recent than converter). Remedy:
|
| A32902 (F, N) Encoder 2: SPI-BUS error occurred | Cause: Error when operating the internal SPI bus. Remedy:
|
| F32905 (N, A) Encoder 2: Encoder parameterization error | Cause: An error was identified in the encoder parameterization. Possible that the parameterized encoder type does not match the connected encoder. Fault value (r0949) indicates the specific parameter error (e.g. EnDat/SSI position, HTL level support, SSI encoders, etc.). Remedy:
|
| F32912 Encoder 2: Device combination is not permissible | Cause: The selected device combination is not supported. 1003: Measuring unit cannot be operated with EnDat 2.2 converter. 1006: Max duration of EnDat transfer exceeded. 2001: Combination of cycles not supported. 2002: Resolution does not match pole pair width. Remedy:
|
| A32915 (F, N) Encoder 2: Encoder configuration error | Cause: The configuration for encoder 2 is incorrect. 1: Re-parameterization between fault/alarm not permissible. 419: Fine resolution Gx_XIST2 too high for 32 bits. Remedy:
|
| F32916 (N, A) Encoder 2: Encoder parameterization error | Cause: An encoder parameter was detected as being incorrect. Remedy:
|
| F32950 Encoder 2: Internal software error | Cause: An internal software error has occurred. Only for internal Siemens troubleshooting. Remedy:
|
| A32999 (F, N) Encoder 2: Unknown alarm | Cause: An alarm occurred on the Sensor Module which cannot be interpreted by the converter firmware. Remedy:
|
| F34803 VSM: Memory test | Cause: An error has occurred during the memory test on the Voltage Sensing Module. Remedy:
|
| F34804 (N, A) VSM: CRC | Cause: A checksum error occurred when reading-out the program memory on the Voltage Sensing Module (VSM). Remedy:
|
| F34805 (N, A) VSM: EEPROM checksum error | Cause: Internal parameter data is corrupted. 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy:
|
| 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. |
| F34850 VSM: Internal software error | Cause: An internal software error in the Voltage Sensing Module (VSM) has occurred. Remedy:
|
| F34899 (N, A) VSM: Unknown fault | Cause: A fault has occurred on the Voltage Sensing Module, which cannot be interpreted by the converter firmware. Remedy:
|
| A34903 VSM: I2C bus error occurred | Cause: An error has occurred when accessing the module-internal I2C bus. Remedy:
|
| A34904 VSM: EEPROM | Cause: An error has occurred accessing the non-volatile memory on the Terminal Module. Remedy:
|
| F34920 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. (KTY: R > 1630 Ohm, Pt1000: R > 1720 Ohm) 2: Measured resistance too low. (PTC: R < 20 Ohm, KTY: R < 50 Ohm, Pt1000: R < 723 Ohm) Remedy:
|
| F34950 VSM: Internal software error | Cause: An internal software error in the Voltage Sensing Module (VSM) has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A34999 VSM: Unknown alarm | Cause: An alarm has occurred on the Voltage Sensing Module (VSM) that cannot be interpreted by the converter firmware. This can occur if the firmware on this component is more recent than the firmware on the converter. Note: If required, the significance of this new alarm can be read about in a more recent description of the converter. Remedy:
|
| C35550 SMT: Motor temperature fault threshold exceeded | Cause: The motor temperature has exceeded the fault threshold. Possible causes: – Motor is overloaded. – The motor ambient temperature is too high. – PTC temperature sensor not connected or wire breakage. This fault results in an STO (Safe Torque Off). The drive must remain in the STO state for 60 seconds. Remedy:
|
| A35552 SMT: Motor temperature alarm threshold exceeded | Cause: The motor temperature has exceeded the alarm threshold. Possible causes: – Motor is overloaded. – The motor ambient temperature is too high. – PTC temperature sensor not connected or wire breakage. Remedy:
|
| C35553 SMT: Internal hardware fault | Cause: The OM-SMT signals a hardware fault. Note: This message results in an STO (Safe Torque Off) that cannot be acknowledged. Remedy:
|
| C35554 SMT: Internal hardware fault | Cause: The OM-SMT signals a hardware fault. Note: This message results in an STO (Safe Torque Off) that cannot be acknowledged. Remedy:
|
| C35555 SMT: Short-circuit detected at the temperature sensor for fault | Cause: There is a short-circuit at the temperature sensor for fault. This fault results in an STO (Safe Torque Off). Acknowledgment is only possible if the short-circuit has been removed for at least 60 seconds. Remedy:
|
| C35557 SMT: Internal software error | Cause: An internal error has occurred in the Safety Integrated software of the OM-SMT. Note: This message results in an STO (Safe Torque Off). Remedy:
|
| C35558 SMT: Internal software error | Cause: An internal error has occurred in the Safety Integrated software of the OM-SMT. Note: This message results in an STO (Safe Torque Off). Remedy:
|
| C35559 SMT: Module temperature – limit value exceeded | Cause: The module temperature of the OM-SMT has exceeded the upper limit value. STO (Safe Torque Off) was initiated to maintain the safe state. Remedy:
|
| C35561 SMT: Error for data cross-check | Cause: When carrying out a data cross-check between the two monitoring channels, the OM-SMT detected a difference and initiated an STO (Safe Torque Off). The monitoring no longer reliably functions. Remedy:
|
| A35563 SMT: Checksum error has occurred | Cause: A checksum error (CRC error) has occurred in the OM-SMT program memory. Remedy:
|
| A35564 SMT: Checksum error has occurred | Cause: A checksum error (CRC error) has occurred in the OM-SMT program memory. Remedy:
|
| C35565 SMT: Internal safety message buffer is full | Cause: Too many safety messages have occurred within a short time so that some have not been able to be displayed. Remedy:
|
| C35567 SMT: Communication error with converter | Cause: A communication error with the converter has occurred. Note: This fault results in an STO (Safe Torque Off). Remedy:
|
| A35569 SMT: Short-circuit detected at the temperature sensor for alarm | Cause: There is a short-circuit at the temperature sensor for alarm. Remedy:
|
| F35950 TM: Internal software error | Cause: An internal software error has occurred. Fault value (r0949): Only for internal Siemens troubleshooting. Remedy:
|
| F36207 Hub: Overtemperature component | Cause: The temperature on the DRIVE-CLiQ Hub Module has exceeded the fault threshold. Remedy:
|
| A36211 Hub: Overtemperature alarm component | Cause: The temperature on the DRIVE-CLiQ Hub Module has exceeded the alarm threshold. Remedy:
|
| F36214 Hub: overvoltage fault 24 V supply | Cause: The 24 V power supply on the DRIVE-CLiQ Hub Module has exceeded the fault threshold. Remedy:
|
| F36216 Hub: undervoltage fault 24 V supply | Cause: The 24 V power supply on the DRIVE-CLiQ Hub Module has undershot the fault threshold. Remedy:
|
| A36217 Hub: undervoltage alarm 24 V supply | Cause: The 24 V power supply on the DRIVE-CLiQ Hub Module has undershot the alarm threshold. Remedy:
|
| F36804 Hub: Checksum error has occurred | Cause: A checksum error occurred when reading out the program memory on the DRIVE-CLiQ Hub Module. Remedy:
|
| F36805 Hub: EEPROM checksum incorrect | Cause: The internal parameter data on the DRIVE-CLiQ Hub Module is incorrect. Alarm value (r2124): 01: EEPROM access error, 02: Too many blocks in the EEPROM. Remedy:
|
| F36899 Hub: Unknown fault | Cause: A fault occurred on the DRIVE-CLiQ Hub Module, which cannot be interpreted by the firmware. This can occur if the firmware on this component is more recent than the firmware on the converter. Remedy:
|
| F36950 Hub: Internal software error | Cause: An internal software error has occurred. Fault value (r0949): Only for internal Siemens troubleshooting. Remedy:
|
| A36999 Hub: Unknown alarm | Cause: An alarm occurred on the DRIVE-CLiQ Hub Module, which cannot be interpreted by the firmware. This can occur if the firmware on this component is more recent than the converter firmware. Remedy:
|
| A39200 IIoT: Communications problem | Cause: The IIOT module has an internal communications problem. It is not possible to transfer data to the EdgeBox. Bit 0 – 7: Internal communications error Bit 8 – 11: Ethernet configuration error identified Bit 12 – 15: Ethernet communications error identified Bit 16 – 19: Internal communications error Remedy:
|
| N39800 IIoT: Group signal | Cause: The IIoT module has detected at least one fault. Remedy:
|
| A39801 IIoT: Sign-of-life missing | Cause: There is a DRIVE-CLiQ communication error between the converter and the IIoT modules involved. Error cause 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
|
| A39802 IIoT: Time slice overflow | Cause: A time slice overflow has occurred on the IIoT module. Fault value (r0949): Time slice number xx. Remedy:
|
| F39804 IIoT: Checksum error has occurred | Cause: A checksum error has occurred when reading-out the program memory on the IIoT module. Fault value (r0949): Difference between the checksum at POWER ON and the actual checksum. Remedy:
|
| F39805 IIoT: EEPROM checksum incorrect | Cause: The internal parameter data on the IIoT module is corrupted. Alarm value (r2124): 01: EEPROM access error, 02: Too many blocks in the EEPROM. Remedy:
|
| F39820 IIoT DRIVE-CLiQ: Telegram error | Cause: There is a DRIVE-CLiQ communication error between the converter and the IIoT module involved. Error causes: 1: Checksum error (CRC error). 2: Telegram shorter than specified. 3: Telegram longer than specified. 4: Length does not match receive list. 5: Type does not match receive list. 6: Address does not match receive list. 7: SYNC telegram expected but not received. 8: No SYNC telegram expected but received. 9: Error bit set. 16: Telegram too early. Remedy:
|
| F39835 IIoT DRIVE-CLiQ: Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error between the converter and the IIoT module involved. The nodes do not send and receive in synchronism. Error causes: 33: Cyclic telegram not received. 34: Timeout in receive list. 64: Timeout in send list. Remedy:
|
| F39836 IIoT DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: There is a DRIVE-CLiQ communication error between the converter and the IIoT modules involved. Data were not able to be sent. Error cause 65: Telegram type does not match send list. Remedy:
|
| F39837 IIoT DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component involved. Faulty hardware cannot be excluded. Error causes: 32: Error in telegram header. 35: Receive error: buffer contains error. 66: Send error: buffer contains error. 67: Send error: buffer contains error. Remedy:
|
| F39845 IIoT DRIVE-CLiQ: Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error between the converter and the IIoT modules involved. Error cause 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy:
|
| F39851 IIoT DRIVE-CLiQ (CU): Sign-of-life missing | Cause: There is a DRIVE-CLiQ communication error between the IIoT module involved and the converter. Error cause 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
|
| F39860 IIoT DRIVE-CLiQ (CU): Telegram error | Cause: There is a DRIVE-CLiQ communication error between the IIoT module involved and the converter. Error causes: 1: Checksum error. 2: Telegram shorter than specified. 3: Telegram longer than specified. 4: Length mismatch. 5: Type mismatch. 6: Address mismatch. 9: Supply voltage failed signal. 16-25: Timing and synchronization errors (telegram too early). Remedy:
|
| F39875 IIoT: Supply voltage failed | Cause: The component involved has signaled that the 24 V supply has failed. Error cause 9 (= 09 hex): The power supply voltage for the components has failed. Remedy:
|
| F39885 IIoT DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error between the IIoT module involved and the converter. The nodes do not send and receive in synchronism. Error causes: 26: Sign-of-life bit not set/too early. 33: Cyclic telegram not received. 34: Timeout in receive list. 64: Timeout in send list. 98: Error at transition to cyclic operation. Remedy:
|
| F39886 IIoT DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data | Cause: There is a DRIVE-CLiQ communication error between the DRIVE-CLiQ Hub Module involved and the converter. Data were not able to be sent. Error cause 65: Telegram type does not match send list. Remedy:
|
| F39887 IIoT DRIVE-CLiQ (CU): Component fault | Cause: A fault was detected on the DRIVE-CLiQ component (IIoT module) involved. Faulty hardware cannot be excluded. Error causes: 32: Error in telegram header. 35: Receive error: buffer error. 66: Send error: buffer error. 67: Send error: buffer error. 96: Response received too late. 97: Time taken to exchange characteristic data too long. Remedy:
|
| F39895 IIoT DRIVE-CLiQ (CU): Alternating cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error between the IIoT module involved and the converter. Error cause 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy:
|
| F39896 IIoT DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (IIoT module), specified by the fault value, have changed in an incompatible fashion with respect to the properties when running up. Remedy:
|
| F39899 IIoT: Unknown fault | Cause: A fault occurred on the IIoT module, which cannot be interpreted by the firmware. This can occur if the firmware on this component is more recent than the firmware on the converter. Remedy:
|
| F39950 IIoT: Internal software error | Cause: An internal software error has occurred. Fault value (r0949): Only for internal Siemens troubleshooting. Remedy:
|
| A39999 IIoT: Unknown alarm | Cause: An alarm occurred on the IIoT module, which cannot be interpreted by the firmware. This can occur if the firmware on this component is more recent than the firmware on the converter. Remedy:
|