Siemens S200 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 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): yyyyxxxx hex: yy = component number, xxxx = fault cause. Common causes: – 11 (000B hex): Checksum error. – 15: Firmware file not accepted. – 18: Firmware version too old. – 19: Firmware not suitable for hardware. – 101: No response from component. – 140: Firmware file not available on memory card. – 141: Inconsistent firmware file length. 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. 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). Remedy:
|
| A01009 Control Unit overtemperature | Cause: The temperature (r0037[0]) of the converter has exceeded the specified limit value. Remedy:
|
| F01011 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. 3: The project download was prematurely exited by the commissioning tool. 100: Different versions between firmware and project files. Remedy:
|
| F01014 Topology: DRIVE-CLiQ component property changed | Cause: The properties of the DRIVE-CLiQ component have fundamentally changed. Remedy:
|
| F01015 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01016 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): 0=Checksum incorrect, 1=File missing, 2=File too many, 3=Incorrect version. Remedy:
|
| A01017 Component lists changed | Cause: The memory card has a defective file. Alarm value (r2124) indicates specific file problem (e.g., checksum incorrect, parsing error). 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. 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 All parameters must be saved | Cause: Data backup is incomplete. The partially saved parameters are not loaded the next time the system runs up. 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. Remedy:
|
| F01034 Units changeover: Calculation parameter values after reference value change unsuccessful | Cause: The change of a reference parameter meant that for an involved parameter the selected value was not able to be re-calculated in the per unit representation. Remedy:
|
| A01035 ACX: Parameter backup file corrupted | Cause: When the converter runs up, no complete data set was found from the parameter backup files. The drive is in the factory setting or the last available backup data record was loaded. Remedy:
|
| F01036 Parameter backup file missing | Cause: When loading the device parameterization, a parameter backup file cannot be found. Remedy:
|
| F01038 Loading the parameter backup file unsuccessful | Cause: An error has occurred when loading parameter backup files from the non-volatile memory. Remedy:
|
| F01039 Writing to the parameter back-up file unsuccessful | Cause: Writing to at least one parameter backup file in the non-volatile memory was unsuccessful (e.g. read-only attribute, insufficient space, defective memory). Remedy:
|
| F01040 Save parameter settings and carry out a POWER ON | Cause: A parameter was changed, which means that it is necessary to save the parameters and reboot. Remedy:
|
| F01041 Parameter save necessary | Cause: Defective or missing files were detected on the memory card when booting. Remedy:
|
| F01042 Parameter error during project download | Cause: An error was detected when downloading a project using the commissioning software (e.g. incorrect parameter value). Remedy:
|
| F01043 Fatal error at project download | Cause: A fatal error was detected when downloading a project using the commissioning tool. Remedy:
|
| F01044 Descriptive data error | Cause: An error was detected when loading the descriptive data saved in the non-volatile memory. Remedy:
|
| A01045 CU: Configuring data invalid | Cause: An error was detected when evaluating the parameter files saved in the non-volatile memory. Under certain circumstances, several of the saved parameter values were not able to be accepted. Remedy:
|
| A01049 CU: It is not possible to write to file | Cause: It is not possible to write to a write-protected parameter backup file. The write request was interrupted. 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 CU: System limit exceeded | Cause: At least one system overload has been identified (e.g. computing time load or peak load too high). Remedy:
|
| F01068 CU: Data memory memory overflow | Cause: The utilization for a data memory area is too large (High-speed data memory overloaded). Remedy:
|
| A01069 Parameter backup and device incompatible | Cause: The parameter backup on the memory card and the drive unit do not match. The module boots with the factory settings. Remedy:
|
| F01070 Project/firmware is being downloaded to the memory card | Cause: An upgrade (project/firmware download) was initiated on the memory card. While this fault is active, it is not permissible to switch off the converter. 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 POWER ON required for backup copy on memory card | Cause: The parameter assignment on the visible partition of the memory card has changed. A POWER ON or hardware reset is required to update the backup copy. Remedy:
|
| F01082 Parameter error when running up from data backup | Cause: Parameterizing errors have been detected (e.g. incorrect parameter value). It is possible that the parameter limits are dependent on other parameters. Remedy:
|
| A01100 CU: Memory card withdrawn | Cause: The memory card (non-volatile memory) was withdrawn during operation. Remedy:
|
| F01105 CU: Insufficient memory | Cause: The functionality on this Control Unit is too extensive (e.g. too many drives, functions, data sets, Technology Extensions, blocks, etc). Remedy:
|
| F01107 CU: Save to memory card unsuccessful | Cause: A data save in the non-volatile memory was not able to be successfully carried out (e.g. defective memory, insufficient space). Remedy:
|
| F01110 CU: More than one SINAMICS G on one Control Unit | Cause: More than one SINAMICS G type power unit is being operated from the Control Unit. Remedy:
|
| F01111 CU: Mixed operation of drive units illegal | Cause: Illegal operation of various drive units on one Control Unit (e.g. SINAMICS S together with SINAMICS G). Remedy:
|
| F01112 CU: Power unit not permissible | Cause: The connected power unit cannot be used together with this Control Unit (e.g. Power unit not supported, or DC/AC type mismatch). Remedy:
|
| F01122 Frequency at the measuring probe input too high | Cause: The frequency of the pulses at the measuring probe input is too high. Remedy:
|
| F01123 Power unit does not support digital inputs/outputs | Cause: The power unit does not support the activated “Digital inputs/outputs” function. Remedy:
|
| F01150 CU: Number of instances of a drive object type exceeded | Cause: The maximum permissible number of instances of a drive object type was exceeded. Remedy:
|
| F01151 CU: Number of drive objects of a category exceeded | Cause: The maximum permissible number of drive objects of a category was exceeded. aa = drive object category exceeded. bb = number permitted. cc = actual number. dd = no significance. Remedy: – Switch off the unit. – Suitably restrict the number of drive objects of the specified category by reducing the number of inserted components. – Re-commission the unit. |
| F01152 CU: Invalid constellation of drive object types | Cause: It is not possible to simultaneously operate drive object types SERVO, VECTOR and HLA. A maximum of 2 of these drive object types can be operated on a Control Unit. Remedy: – Switch off the unit. – Restrict the use of drive object types SERVO, VECTOR, HLA to a maximum of 2. – Re-commission the unit. |
| F01200 CU: Time slice management internal software error | Cause: A time slice management error has occurred. It is possible that the sampling times have been inadmissibly set. Fault value 998: Too many time slices occupied by technology functions (e.g. DCC). Fault value 999: Too many time slices occupied by the basic system. Remedy: – Contact Technical Support. |
| F01205 CU: Time slice overflow | Cause: Insufficient processing time is available for the existing topology. Remedy: – Reduce the number of drives. |
| F01250 EEPROM incorrect read-only data | Cause: Error when reading the read-only data of the EEPROM in the converter. Remedy: – Carry out a POWER ON (switch-off/switch-on). – Replace the converter. |
| A01251 CU: CU-EEPROM incorrect read-write data | Cause: Error when reading the read-write data of the EEPROM in the converter. Remedy: For alarm value r2124 < 256: – Carry out a POWER ON (switch-off/switch-on). – Replace the converter. For alarm value r2124 >= 256: – For the converter with this alarm, clear the fault memory (p0952 = 0). – Replace the converter. |
| F01255 CU: Option Board EEPROM read-only data error | Cause: Error when reading the read-only data of the EEPROM in the Option Board. Remedy: – Carry out a POWER ON (switch-off/switch-on). – Replace the Control Unit. |
| A01256 CU: Option Board EEPROM read-write data error | Cause: Error when reading the read-write data of the EEPROM in the Option Board. Remedy: – Carry out a POWER ON (switch-off/switch-on). – Replace the Control Unit. |
| A01304 Firmware version of DRIVE-CLiQ component is not up-to-date | Cause: The non-volatile memory has a more recent firmware version than the one in the connected DRIVE-CLiQ component. Remedy: 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. 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 indicates component number, class and connection number. (See F01375 for class descriptions). Remedy: – Remove the corresponding component. – Change the setting “deactivate and not present”. |
| A01317 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). Remedy: The alarm is automatically withdrawn for the following actions: – Activate the components involved (p0125 = 1, p0145 = 1, p0155 = 1, p0165 = 1). – Again withdraw the component involved. |
| A01318 Deactivated signal interconnections available | Cause: This alarm is used if an inactive/non-operational drive object is active again/ready for operation, or if the list of parameters that can be interconnected as signal sink is not empty. 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. 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. Fault causes (aa): 01 hex: Illegal connections (e.g., >1 motor per Motor Module). 02 hex: Too many components of a particular type (e.g., >1 master CU, >10 Motor Modules). 03 hex: >16 components on one DRIVE-CLiQ socket. 04 hex: >125 components in series. 05 hex: Component not permissible for SERVO. 06 hex: Illegal EEPROM data detected. 07 hex: Illegal combination of components (e.g., Active Line Module + Basic Line Module). 08 hex: Motor not completely connected. 09 hex: Encoder interface X100 issue. Remedy: – Adapt the output topology to the permissible requirements. – Commission the device using the commissioning tool. – For aa=06/bb=01: Correct the Article No. – For aa=09: Using encoder interface X100. |
| 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: – Check the DRIVE-CLiQ wiring. – Reduce the number components on the DRIVE-CLiQ line involved in order to maintain the maximum quantity structure. |
| F01354 Topology: Actual topology indicates an illegal component | Cause: The actual topology indicates at least one illegal component. xx = 1: Component at this Control Unit not permissible. xx = 2: Component in combination with another component not permissible. 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. xx = 1: Component at this Control Unit not permissible. xx = 2: Component with communication defect. 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. 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. 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: – Carry out a POWER ON (switch-off/switch-on). – Distribute components across several DRIVE-CLiQ lines. |
| F01360 Topology: Actual topology not permissible | Cause: The detected actual topology is not permissible. Fault causes (aa): 01 hex: >199 components detected. 02 hex: Unknown component type. 03 hex: Illegal combination ALM and BLM. 04 hex: Illegal combination ALM and SLM. 05 hex: Illegal combination BLM and SLM. 06 hex: CX32 not directly connected to permitted CU. 07 hex: NX10/NX15 not directly connected to permitted CU. 08 hex: Component not permitted for this CU. 09 hex: Component with out-of-date firmware. 0A hex: Too many components of a particular type. 0B hex: Too many components of a particular type on a single line. Remedy: Check fault cause and: 1: Connect less than 199 components. 2: Remove unknown component. 3, 4, 5: Establish valid combination. 6, 7: Connect expansion module directly to permitted CU. 8: Remove component or use permissible component. 9: Upgrade firmware. 10, 11: Reduce number of components. |
| A01361 Topology: Actual topology contains SINUMERIK and SIMOTION components | Cause: The detected actual topology contains SINUMERIK and SIMOTION components. cc = 01 hex: NX10/NX15 connected to SIMOTION. cc = 02 hex: CX32 connected to SINUMERIK. Remedy: For alarm value = 1: Replace all NX10 or NX15 by a CX32. For alarm value = 2: Replace all CX32 by an NX10 or NX15. |
| A01362 Topology: Topology rule(s) broken | Cause: At least one topology rule for the SINAMICS S120 Combi has been broken. (Codes 1 through 19 detailed in manual, relating to wiring specific sockets X200-X505 and module combinations). 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. The fault value describes a component contained in the ring. Remedy: Output the fault value and remove the specified connection. |
| F01380 Topology: Actual topology EEPROM defective | Cause: When detecting the actual topology, a component with a defective EEPROM was detected. Remedy: Output the fault value and remove the defected component. |
| 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. Remedy: – Insert the components involved at the right connection. – Adapt the project/parameterizing in the commissioning tool. – Automatically resolve the topology error. |
| 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. Remedy: – Insert the components involved at the right connection. – Adapt the project/parameterizing in the commissioning tool. – Automatically resolve the topology error. |
| A01384 Topology: DRIVE-CLiQ Hub Module incorrectly inserted | Cause: The topology comparison has detected a DRIVE-CLiQ Hub Module in the actual topology that has been incorrectly inserted with respect to the target topology. Remedy: – Insert the components involved at the right connection. – Adapt the project/parameterizing in the commissioning tool. – Automatically resolve the topology error. |
| 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. In this state, the drive control (closed-loop) cannot be enabled. Remedy: Adapting topologies:
Note: Under “Topology –> Topology view” the commissioning tool offers improved diagnostics capability. |
| 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. In this state, the drive control (closed-loop) cannot be enabled. Remedy: Adapting topologies:
|
| A01389 Topology: Motor with DRIVE-CLiQ incorrectly inserted | Cause: The topology comparison has detected a motor with DRIVE-CLiQ in the actual topology that has been incorrectly inserted with respect to the target topology. The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled. Remedy: Adapting topologies:
|
| A01416 Topology: Component additionally inserted | Cause: The topology comparison has found a component in the actual topology which is not specified in the target topology. Remedy: Adapting topologies:
|
| A01420 Topology: Component different | Cause: The topology comparison has detected differences in the actual topology and target topologies in the electronic rating plate. Note: For a multi-component module, the incorrect subcomponent (index) is connected (e.g. Double Motor Module X201 instead of X200) – or only a part of a multi-component module is set to “deactivate and not available”. The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled. Remedy: Adapting topologies:
|
| A01425 Topology: Serial number different | Cause: The topology comparison has detected differences in the actual and target topologies in relation to one component. The serial number is different. The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled. Remedy: Adapting topologies:
|
| A01428 Topology: Incorrect connection used | 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 drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled. Remedy: Adapting topologies:
|
| F01451 Topology: Target topology is invalid | 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 aa = 1B hex = 27 dec: Error not specified. aa = 1C hex = 28 dec: Value illegal. aa = 1D hex = 29 dec: Incorrect ID. aa = 1E hex = 30 dec: Incorrect ID length. aa = 1F hex = 31 dec: Too few indices left. aa = 20 hex = 32 dec: component not connected to Control Unit. Remedy:
|
| A01481 Topology: Motor Module not connected | Cause: The topology comparison has detected a Motor Module that is missing in the actual topology with respect to the target topology. Remedy: Adapting topologies:
Check the hardware:
|
| A01482 Topology: Sensor Module not connected | Cause: The topology comparison has detected a Sensor Module that is missing in the actual topology with respect to the target topology. Remedy: Adapting topologies:
Check the hardware:
|
| A01483 Topology: Terminal Module not connected | Cause: The topology comparison has detected a Terminal Module that is missing in the actual topology with respect to the target topology. Remedy: Adapting topologies:
Check the hardware:
|
| A01484 Topology: DRIVE-CLiQ Hub Module not connected | 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. Note: The component is described in dd, cc and bb, where the component has not been inserted. Remedy:
Note: Under “Topology -> Topology view” the commissioning tool offers improved diagnostics capability. |
| A01485 Topology: Controller Extension 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. Remedy:
|
| A01486 Topology: DRIVE-CLiQ component 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. Remedy:
|
| A01487 Topology: Option slot component not inserted | 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. Remedy:
|
| A01489 Topology: motor with DRIVE-CLiQ not connected | 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. Remedy:
|
| 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:
|
| A01514 Error when writing during a reconnect | Cause: During a reconnect operation (e.g. while booting or downloading – but can also occur in normal operation) a parameter was not able to be written to. The parameter is then reset to the factory setting. Remedy:
|
| 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:
Notice: Not observing this and continuing to work at the converter can lead to the data backup on the SD card being lost. |
| A01590 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. Remedy:
|
| 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): 1005: STO active, although STO not selected. 1010: STO inactive, although STO is selected. 1015: The self test was unsuccessful. 1016: Error in communication path. 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:
|
| A01605 SI: Checksum error has occurred | Cause: A checksum error (CRC error) has occurred in the converter program memory. Alarm value (r2124, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01637 SI: Safety configuration not protected | Cause: Safety configuration is not protected using UMAC (User Management and Access Control). Remedy:
|
| F01646 SI: Change logbook | Cause: The saved functional safety checksum differs from the safety checksum calculated when running up. An acceptance test is required as changes have been made to a safety parameter or the safety hardware. Remedy:
|
| 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:
|
| 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. 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 at the last machine acceptance. Safety-relevant parameters have been changed or a fault is present. Note: This message results in an STO (Safe Torque Off). Remedy:
|
| C01677 SI: Incorrect onboard F-I/O parameter value | Cause: The parameter cannot be parameterized with this value. Message value (r60049): yyyyxxxx dec (yyyy = supplementary info, xxxx = parameter). xxxx = 10000: A non-existent F-DI was enabled. xxxx = 10002: F-DI discrepancy time is less than SI monitoring clock cycle. xxxx = 10017: Input filter issue. xxxx = 10018: Self test length dark pulses is zero. xxxx = 10041: Invalid value in F-DI self test mode selection. xxxx = 10071: F-DI status enabled which was not enabled in p10000. Remedy: Correct the parameter value:
|
| C01680 SI: Checksum error safety monitoring functions | Cause: The actual checksum over the safety-relevant parameters, calculated by the drive, does not match the reference checksum last saved for the last machine acceptance test. Safety-relevant parameters have been changed or a fault is present. Note: This message results in an STO. Remedy:
|
| C01681 SI: Incorrect parameter value | Cause: The parameter cannot be parameterized with this value. Note: This fault results in STO. xxxx = 10006 or 10022: An inadmissible signal source for the control via F-DI was set. 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. This message results in an STO. Remedy:
|
| C01690 SI: Data backup problem for the NVRAM | Cause: When saving parameters r9780, r9781 and r9782 (Safety logbook) says, an error has occurred in conjunction with the NVRAM. Fault value 1: No physical NVRAM. Fault value 2: No free memory space. 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:
|
| 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. Safe operation not possible. Note: This fault results in an SS1 and consequently STO. Remedy:
|
| C01770 SI: Fault of the failsafe inputs | Cause: The failsafe digital inputs (F-DI) have a fault condition. Value 1: Discrepancy error. Value 2: Too many switching operations. Value 3: Test pulse error. Value 4: Internal software error. 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:
|
| F01800 DRIVE-CLiQ: Hardware/configuration error | Cause: A DRIVE-CLiQ connection fault has occurred. Fault value 100…107: Communication fault. Fault value 10: Loss of connection. Fault value 11: Repeated faults. Fault value 12: Connection detected but node ID exchange failed. Remedy:
|
| A01839 DRIVE-CLiQ diagnostics: cable fault to the component | Cause: The fault counter to monitor the DRIVE-CLiQ connections/cables has been incremented. The component number specifies the component whose feeder cable from the direction of the converter is faulted. 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 PN: Configuration telegram error | Cause: A controller attempts to establish a connection using an incorrect configuring telegram. Remedy: Check the bus configuration on the controller and device sides. |
| A01902 PN: Isochronous operation parameterization not permissible | Cause: Parameterization for isochronous operation is not permissible. Alarm value indicates specific timing violation (e.g., Bus cycle time Tdp < 0.5 ms, PLL tolerance window exceeded). Remedy:
|
| A01904 PN: Controller setting of the PZD telegram rejected | Cause: A controller attempts to set a PZD telegram. The setting is not applied because controllers have no function rights or telegram implies invalid configuration. Remedy: Check and align the telegram settings in the drive project and in the controller. |
| A01905 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. Remedy: Activate channel diagnostics in the bus configuration and check and align function rights in the drive. |
| F01910 Fieldbus: setpoint timeout | Cause: The reception of setpoints from the fieldbus interface (PROFINET) is 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 PN: Isochronous operation, clock cycle failure | Cause: The telegram to synchronize the clock cycles has failed for several bus clock cycles or has violated the specified time grid. Remedy:
|
| F01912 PN: Isochronous operation sign-of-life missing | Cause: The maximum permissible number of errors in the controller sign-of-life (isochronous operation) has been exceeded in cyclic operation. Remedy:
|
| A01932 PN: Clock cycle synchronization missing for DSC | Cause: There is no clock synchronization or clock synchronous sign of life and DSC (Dynamic Servo Control) is selected. Remedy: Set clock synchronization across the bus configuration and transfer clock synchronous sign-of-life. |
| A01940 PB/PN: clock cycle synchronism not reached | Cause: The bus is in the data exchange state and clock synchronous operation has been selected, but synchronization specified by the controller was not able to be performed. Remedy:
|
| A01980 PN: cyclic connection interrupted | Cause: The cyclic connection to the PROFINET controller is interrupted. 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. Remedy: Check the configuration of the PROFINET controllers. |
| A02000 Function generator: Start not possible | Cause: The function generator has already been started. Remedy: Stop the function generator and restart again if necessary. |
| 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. |
| 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. |
| 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. |
| A02096 MTrace 0: cannot be saved | Cause: It is not possible to save the measurement results of a multiple trace on the memory card. Card not inserted, blocked, or data save too slow. Remedy:
|
| F02151 TEC: internal software error | Cause: An internal software error has occurred within a Technology Extension. Remedy:
|
| F05055 Parallel connection: Power units with illegal code numbers | Cause: The code numbers of the power units do not match. Remedy: Use power units with the same code number. For parallel circuit configurations, only power units with identical power unit data may be used. |
| F05057 Parallel circuit: Power unit firmware versions differ | Cause: The firmware versions of the power units connected in parallel do not match. Remedy: Use power units with the same firmware version. |
| F07011 Drive: Motor overtemperature | Cause: The calculated motor temperature is too high. Possible causes: Motor overloaded, ambient temperature too high, or sensor wire breakage. 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. Remedy: Check the adapted parameter value and if required correct. |
| F07090 Drive: Upper torque limit less than the lower torque limit | Cause: The upper torque limit is lower than the lower torque limit. Remedy: When setting the torque limits via telegram 750, the positive torque limit must be >= the negative torque. |
| A07092 Drive: moment of inertia estimator still not ready | Cause: The moment of inertia estimator has still not determined any valid values. The acceleration cannot be calculated. The moment of inertia estimator has stabilized, if the frictional values as well as the moment of inertia were determined and the corresponding status signal is set. Remedy: Traverse the axis until the moment of inertia estimator has stabilized. This alarm is automatically withdrawn after the moment of inertia estimator has stabilized. |
| F07093 Drive: Test signal error | Cause: An error was identified when executing the “Test signal” function. The function was not executed or was canceled. Fault value (r0949): 1: No distance limit defined (p5308=0). 2: Moment of inertia not stabilized. 3: Parameterized distance exceeded. 4: No motor encoder parameterized. 6: Pulse enable withdrawn while traversing. 7: Speed setpoint not equal to zero. Remedy:
|
| A07094 General parameter limit violation | Cause: As a result of the violation of a parameter limit, the parameter value was automatically corrected. Minimum limit violated -> parameter is set to the minimum value. Maximum limit violated -> parameter is set to the maximum value. Remedy: Check the adapted parameter values and if required correct. |
| A07095 Drive: One Button Tuning activated | Cause: The One Button Tuning function is active. One Button Tuning is performed at the next switch-on command. Remedy: Not necessary. The alarm is automatically withdrawn after One Button Tuning has been exited. |
| F07097 Drive: Test signal error distance limiting | Cause: An error was identified when executing function “Test signal” or One Button Tuning selection (p5300 = 1). The function was not executed or was canceled. Remedy: Enter the traversing path in parameter p5308 – or deselect the function involved in p5301. For fault cause = 1, 2: Deselect bits in parameter p5301 per manual instructions. |
| 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 via the master control. Remedy: Switch the signal to 0 via binary signal sink c0840 (actual CDS) or control word bit 0 via the master control. |
| F07220 Drive: Master control by PLC missing | Cause: The “master control by PLC” signal was missing in operation. – The higher-level control has withdrawn the “master control by PLC” signal. – Data transfer via the fieldbus was interrupted. Remedy: Check the “master control by PLC” signal and, if required, switch in. Check data transfer via the fieldbus. |
| F07300 Drive: Line contactor feedback signal missing | Cause: – The line contactor was not able to be closed within the time in p0861. – The line contactor was not able to be opened within the time in p0861. – The line contactor dropped out during operation. – The line contactor has closed although the drive converter is switched off. Remedy: Check the setting of p0860. Check the feedback circuit from the line contactor. Increase the monitoring time in p0861. |
| 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: Deselect measuring probe (p0488, p0489). |
| 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. – Motor not connected or motor contactor open. – No DC link voltage present. – Power unit defective. Remedy: Connect the motor or check the motor contactor. Check the DC link voltage (r0070). Check the power unit. |
| F07412 Drive: Commutation angle incorrect (motor model) | Cause: An incorrect commutation angle was detected, which can result in a positive coupling in the speed controller. – Phase sequence incorrect. – Motor encoder incorrectly adjusted. – Motor encoder damaged. – Motor encoder speed signal faulted. Remedy: Check phase sequence. If encoder mounting changed, re-adjust encoder. Replace defective motor/encoder. |
| F07419 Drive: Current setpoint filter adaptation error | Cause: An error has occurred when configuring or when using the “Current setpoint filter adaptation” function. Remedy: The remedy should be applied depending on the fault value (Bit 2, Bit 3, etc). – Set filter type “General filter 2nd order”. – Activate filter (p1656). – Carry out POWER ON. |
| F07420 Drive: Current setpoint filter natural frequency > Shannon frequency | Cause: One of the filter natural frequencies is greater than the Shannon frequency. Remedy: Reduce the numerator or denominator natural frequency of the current setpoint filter involved. Deactivate the filter involved. |
| F07421 Drive: Speed filter natural frequency > Shannon frequency | Cause: One of the filter natural frequencies is greater than the Shannon frequency. Remedy: Reduce the numerator or denominator natural frequency of the speed setpoint filter involved. Deactivate the filter involved. |
| 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). |
| F07432 Drive: Motor without overvoltage protection | Cause: In the case of a fault at maximum speed, the motor can generate an overvoltage that can destroy the converter. Remedy: Limit the maximum speed (p1082) without any additional protection. |
| 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). Remedy: Change over the drive data set with the pulses inhibited. Ensure changeover does not result in motor direction change. |
| A07440 EPOS: Jerk time is limited | Cause: The calculation of the jerk time Tr resulted in an excessively high value so that the jerk time is internally limited to 1000 ms. Remedy: Increase the jerk limiting (p2574). Reduce maximum acceleration or deceleration. |
| A07441 LR: Save the position offset of the absolute encoder adjustment | Cause: The status of the absolute encoder adjustment has changed. To permanently accept the determined position offset, it must be retentively saved. Remedy: Readjust the encoder. |
| F07442 LR: Multiturn does not match the modulo range | Cause: The ratio between the multiturn resolution and the modulo range (p2576) is not an integer number. Remedy: Make the ratio between the multiturn resolution and the modulo range an integer number. |
| F07443 LR: Home position not in the permissible range | Cause: The home position received when adjusting the encoder via numerical signal sink r2599 lies outside the half of the encoder range and cannot be set as actual axis position. Remedy: Set the home position to a lower value than specified in the fault value. |
| F07446 Load gearbox: Position tracking cannot be reset | Cause: The position tracking cannot be reset. Remedy: Reset position tracking via encoder commissioning, reset p2720.2 = 1, deselect encoder commissioning. |
| F07450 LR: Standstill monitoring has responded | Cause: After the standstill monitoring time (p2543) expired, the drive left the standstill window (p2542). – Window too small. – Time too low. – Loop gain issues. – Mechanical overload. Remedy: Check the causes and resolve. |
| F07451 LR: Position monitoring has responded | Cause: When the position monitoring time (p2545) expired, the drive had still not reached the positioning window (p2544). Remedy: Check parameterization (window too small, time too short) and mechanical locking. |
| F07452 LR: Following error too high | Cause: The difference between the position setpoint position actual value is higher than the tolerance (p2546). Remedy: Check drive torque, measuring system, encoder cable, position control sense, and mechanical system. |
| F07453 LR: Position actual value preprocessing error | Cause: A position measuring system fault has occurred (F31110, F31111). An error occurred during position actual value preprocessing. Remedy: Resolve the cause of the position measuring position fault. Check the encoder. |
| A07454 LR: Position actual value preprocessing does not have a valid encoder | Cause: Problems with position actual value preprocessing: – Encoder not assigned (p2502=0). – Encoder assigned but no data set. – Invalid data. Remedy: Check drive data sets, encoder data sets and encoder assignment. |
| A07455 EPOS: Maximum velocity limited | Cause: The maximum velocity (p2571) is too high to correctly calculate the modulo correction. Remedy: Reduce the maximum velocity (p2571). |
| A07456 EPOS: Setpoint velocity limited | Cause: The actual setpoint velocity is greater than the parameterized maximum velocity (p2571) and is therefore limited. Remedy: Check entered setpoint velocity. Reduce velocity override. Increase maximum velocity. |
| A07457 EPOS: Combination of input signals illegal | Cause: An illegal combination of input signals that are simultaneously set was identified. Remedy: Check the appropriate input signals and correct. |
| F07458 EPOS: Reference cam not found | Cause: After the active homing starts, the axis moved through the maximum permissible distance to search for the reference cam without actually finding the reference cam. Remedy: Check signal “Reference cam”. Check maximum permissible distance (p2606). |
| F07459 EPOS: No zero mark | Cause: After leaving the reference cam, the axis has traversed the maximum permissible distance between the reference cam and zero mark without finding the zero mark. Remedy: Check the encoder regarding the zero mark. Check p2609. |
| F07460 EPOS: End of reference cam not found | Cause: In “active homing” mode, the axis reached the end of traversing range without detecting an edge at binary signal “Reference cam”. Remedy: Check signal “reference cam”. Repeat active homing. |
| A07461 EPOS: Home position not set | Cause: When starting a traversing block/direct setpoint input, a home position is not set. Remedy: Carry out homing (active homing, passive homing, set home position). |
| A07462 EPOS: Selected traversing block number does not exist | Cause: A traversing block selected via binector input was started but the block number is not contained in p2616. Remedy: Correct the traversing program. Select an available traversing block number. |
| A07463 EPOS: External block change not requested in the traversing block | Cause: For a traversing block with block change enable CONTINUE_EXTERNAL_ALARM, the external block change was not requested. Remedy: Resolve the reason why the signal edge at the measuring probe is missing. |
| F07464 EPOS: Traversing block is inconsistent | Cause: The traversing block does not contain valid information. Remedy: Check the traversing block and where relevant, take into consideration alarms that are present. |
| A07465 EPOS: Traversing block does not have a subsequent block | Cause: There is no subsequent block in the traversing block. Remedy: Parameterize this traversing block with the block change enable END. |
| A07466 EPOS: Traversing block number assigned a multiple number of times | Cause: The same traversing block number was assigned a multiple number of times. Remedy: Correct the traversing blocks. |
| A07467 EPOS: Traversing block has illegal task parameters | Cause: The task parameter in the traversing block contains an illegal value. Remedy: Correct the task parameter in the traversing block. |
| A07468 EPOS: Traversing block jump destination does not exist | Cause: In a traversing block, a jump was programmed to a non-existent block. Remedy: Correct the traversing block. Add the missing traversing block. |
| A07469 EPOS: Traversing block target position < negative software limit switch | Cause: In the traversing block the specified absolute target position lies outside the range limited by the negative software limit switch. Remedy: Correct the traversing block. Change the negative software limit switch. |
| A07470 EPOS: Traversing block target position > positive software limit switch | Cause: In the traversing block the specified absolute target position lies outside the range limited by the positive software limit switch. Remedy: Correct the traversing block. Change the positive software limit switch. |
| A07471 EPOS: Traversing block target position outside the modulo range | Cause: In the traversing block the target position lies outside the modulo range. Remedy: In the traversing block, correct the target position. Change the modulo range (p2576). |
| A07472 EPOS: Traversing block ABS_POS/ABS_NEG not possible | Cause: Positioning mode ABS_POS or ABS_NEG parameterized with modulo correction not activated. Remedy: Correct the traversing block. |
| A07473 EPOS: Beginning of traversing range reached | Cause: When traversing, the axis has moved to the traversing range limit. Remedy: Move away in the positive direction. |
| A07474 EPOS: End of traversing range reached | Cause: When traversing, the axis has moved to the traversing range limit. Remedy: Move away in the negative direction. |
| F07475 EPOS: Target position < start of traversing range | Cause: The target position for relative traversing lies outside the traversing range. Remedy: Correct the target position. |
| F07476 EPOS: Target position > end of the traversing range | Cause: The target position for relative traversing lies outside the traversing range. Remedy: Correct the target position. |
| A07477 EPOS: Target position < negative software limit switch | Cause: In the actual traversing operation, the target position is less than the negative software limit switch. Remedy: Correct the target position. Change the negative software limit switch. |
| A07478 EPOS: Target position > positive software limit switch | Cause: In the actual traversing operation, the target position is greater than the positive software limit switch. Remedy: Correct the target position. Change the positive software limit switch. |
| A07479 EPOS: Negative software limit switch reached | Cause: The axis is at the position of the negative software limit switch. An active traversing block was interrupted. Remedy: Correct the target position. Change the negative software limit switch. |
| A07480 EPOS: Positive software limit switch reached | Cause: The axis is at the position of the positive software limit switch. An active traversing block was interrupted. Remedy: Correct the target position. Change the positive software limit switch. |
| F07481 EPOS: Axis position < negative software limit switch | Cause: The actual position of the axis is less than the position of the negative software limit switch. Remedy: Correct the target position. Change the negative software limit switch. |
| F07482 EPOS: Axis position > positive software limit switch | Cause: The actual position of the axis is greater than the position of the positive software limit switch. Remedy: Correct the target position. Change the positive software limit switch. |
| A07483 EPOS: Travel to fixed stop clamping torque not reached | Cause: The fixed stop in the traversing block was reached without the clamping torque/clamping force having been achieved. Remedy: Check the torque limits (p1520, p1521). |
| F07484 EPOS: Fixed stop outside the monitoring window | Cause: In the “fixed stop reached” state, the axis has moved outside the defined monitoring window (p2635). Remedy: Check the monitoring window (p2635). Check the mechanical system. |
| F07485 EPOS: Fixed stop not reached | Cause: In a traversing block with the task FIXED STOP, the end position was reached without detecting a fixed stop. Remedy: Check the traversing block. Reduce the maximum following error window. |
| A07486 EPOS: Intermediate stop missing | Cause: In operating mode “traversing blocks” or “direct setpoint input/MDI”, at the start of motion, c2640 is set to an intermediate stop. Remedy: Set c2640 to “No intermediate stop” (1 signal) and restart motion. |
| A07487 EPOS: Reject traversing task missing | Cause: At the start of motion, the binary signal sink “Do not reject traversing task” (c2641) does not have a 1 signal. Remedy: Connect a 1 signal to the binary signal sink “Do not reject traversing task/reject traversing task” (c2641) and restart motion. |
| F07488 EPOS: Relative positioning not possible | Cause: In the mode “direct setpoint input/MDI”, for continuous transfer (c2649 = 1) relative positioning was selected (c2648 = 0). Remedy: Check the control. |
| F07490 EPOS: Enable signal withdrawn while traversing | Cause: – For a standard assignment, another fault may have occurred. – The drive is in the “switching on inhibited” state. Remedy: Set the enable signals or check the cause of the fault that first occurred. Check the assignment to enable the basic positioning function. |
| F07491 EPOS: Negative hardware limit switch reached | Cause: A 0 signal was detected at c2569 (negative hardware limit switch). Remedy: Leave the negative hardware limit switch in the positive traversing direction. Check wiring. |
| F07492 EPOS: Positive hardware limit switch reached | Cause: A 0 signal was detected at c2570 (positive hardware limit switch). Remedy: Leave the positive hardware limit switch in the negative traversing direction. Check wiring. |
| F07493 LR: Overflow of the value range for position actual value | Cause: The value range for the position actual value representation was exceeded. Remedy: If required, reduce the traversing range or position resolution (p2506). |
| F07494 LR: Drive Data Set changeover in operation | Cause: A Drive Data Set changeover (DDS) with a change of the mechanical relationships or encoder assignment was requested in operation. Remedy: To changeover the drive data set, initially, exit the “operation” mode. |
| A07495 LR: Homing function interrupted | Cause: An activated homing function was canceled. – Encoder fault. – Position actual value was set during homing. – Homing mark search and measuring probe evaluation simultaneously activated. Remedy: Check the causes and resolve. Reset the control. |
| A07496 EPOS: Enable not possible | Cause: Not possible to enable basic positioner because at least one condition is missing. 1: EPOS enable missing. 2: Position actual value/feedback missing. Remedy: Check the corresponding missing condition. |
| A07498 LR: Measuring probe evaluation not possible | Cause: When evaluating the measuring probe, an error occurred (input terminal not set, pulse frequency too high, etc.). Remedy: Deactivate measuring probe evaluation (c2509=0). Check hardware, frequency, and clock cycle settings. |
| F07499 EPOS: Reversing cam approached with the incorrect traversing direction | Cause: The negative reversing cam was approached in the positive traversing direction, or vice versa. Remedy: Check the wiring of the reversing cam. Check the traversing direction. |
| F07503 EPOS: Hardware limit switch approached with the incorrect traversing direction | Cause: The negative hardware limit switch was approached in the positive traversing direction, or vice versa. Remedy: Check the wiring of the hardware limit switch. Check the traversing direction. |
| A07507 EPOS: Home position cannot be set | Cause: After the home position correction, the position setpoint lies outside the traversing range limits. Remedy: Optimize the position controller. |
| A07520 Drive: Motor cannot be changed over | Cause: A motor data set switchover was requested via PROFINET that the converter does not support. Remedy: Check the PROFINET telegram. |
| A07530 Drive: Drive Data Set DDS not present | Cause: A data set switchover was requested via PROFINET that the converter does not support. Remedy: Check the PROFINET telegram. |
| A07531 Drive: Command Data Set CDS not present | Cause: The selected command data set is not available. Remedy: Select the existing command data set. Set up additional command data sets. |
| A07550 Drive: Not possible to reset encoder parameters | Cause: When restoring a factory setting, it was not possible to reset the encoder parameters. The encoder parameters are directly read out of the encoder. Alarm value (r2124, interpret decimal): Component number of the encoder involved. Remedy:
|
| F07555 Drive encoder: Configuration position tracking | Cause: For position tracking, the configuration is not supported. Position tracking can only be activated for absolute encoders. For linear axes, it is not possible to simultaneously activate the position tracking for load and measuring gears. Fault value (r0949, interpret hexadecimal): ddccbbaa hex aa = encoder data set, bb = component number, cc = drive data set, dd = fault cause. dd=00: Absolute encoder not used. dd=01: NVRAM memory insufficient. dd=02: Linear axis activated for load and measuring gearbox. dd=03: Position tracking already detected with different parameters. dd=04: Linear encoder is being used. Remedy:
|
| F07556 Measuring gearbox: Position tracking, maximum actual value exceeded | Cause: When the position tracking of the measuring gearbox is configured, the drive/encoder identifies a maximum possible absolute position actual value (r0483) that cannot be represented within 32 bits. Maximum value: p0408 * p0412 * 2^p0419. Remedy:
|
| A07557 Motor encoder: Home position not in the permissible range | Cause: The home position received via p2599 when adjusting the encoder lies outside half of the encoder range and cannot be set as actual axis position. The maximum permissible value is displayed in the supplementary information. Remedy:
|
| F07562 Drive, encoder: Position tracking, incremental encoder not possible | Cause: The requested position tracking for incremental encoders is not supported. Fault value (r0949, interpret hexadecimal): ccccbbaa hex (aa=encoder data set, bb=component number, cccc=fault cause). cccc=00: Encoder type does not support function. cccc=01: NVRAM memory insufficient. cccc=04: Linear encoder used that does not support function. Remedy:
|
| A07565 Drive: Encoder error in PROFIdrive encoder interface 1 | Cause: An encoder error was signaled for encoder 1 via the PROFIdrive encoder interface (G1_ZSW.15). Remedy:
|
| A07569 Enc identification active | Cause: During encoder identification (waiting) with p0400 = 10100, the encoder could still not be identified. Possible incorrect encoder, no encoder available, or incorrect cable. Remedy:
|
| F07575 Drive: Motor encoder not ready | Cause: The motor encoder signals that it is not ready. – Initialization of encoder 1 unsuccessful. – “Parking encoder” function is active. – Sensor Module is defective. Remedy:
|
| A07577 Motor encoder: Measuring probe evaluation not possible | Cause: When evaluating the measuring probe, an error occurred. Alarm value (r2124): 6: Input terminal not set. 4098: Error initializing probe. 4100: Measuring pulse frequency too high. 4200: Bus cycle time not integer multiple of position controller clock cycle. Remedy:
|
| A07580 Drive: No Sensor Module with matching component number | Cause: A Sensor Module with the specified component number was not found. Remedy:
|
| A07581 Motor encoder: Position actual value preprocessing error | Cause: An error has occurred during the position actual value preprocessing. Remedy:
|
| A07587 Motor encoder: Position actual value preprocessing has no valid encoder | Cause: The encoder data set has been assigned, but contains no encoder data (p0400 = 0) or invalid data. Remedy:
|
| A07593 Motor encoder: Value range for position actual value exceeded | Cause: The value range (-2147483648 … 2147483647) for the position actual value representation was exceeded. 1: Position actual value (r2521) exceeded. 2: Encoder position actual value Gn_XIST2 exceeded. 3: Maximum encoder value * factor (LU) exceeded range. Remedy:
|
| A07596 Motor encoder: Homing function interrupted | Cause: An activated homing function was canceled. – Encoder fault occurred. – Position actual value set during homing. – Homing mark search and measuring probe evaluation simultaneously activated. – Activated homing function was de-activated. Remedy:
|
| F07800 Drive: No power unit present | Cause: Power unit parameters cannot be read or no parameters stored. DRIVE-CLiQ cable interrupted or defective. Incorrect topology selected. Remedy:
|
| F07801 Drive: Motor overcurrent | Cause: The permissible motor limit current was exceeded. – Active current limit too low. – Current controller not correctly set. – Load too high. – Short-circuit or ground fault. – Motor current does not match drive current. Remedy:
|
| F07802 Drive: Infeed not ready | Cause: The drive does not signal a ready state after an internal switch-on command. – DC link voltage not present. – Defective drive. – Supply voltage incorrectly set. Remedy:
|
| F07808 HF Damping Module: damping not ready | Cause: When switching on, the HF Damping Module does not return a ready signal. 1: Fault at switch-on. 2: Fault during operation. Remedy:
|
| F07810 Drive: Power unit EEPROM without rated data | Cause: No rated data are stored in the power unit EEPROM. Remedy:
|
| F07815 Drive: Power unit has been changed | Cause: The code number of the actual power unit does not match the saved number. Remedy:
|
| F07860 External fault 1 | Cause: The condition for “External fault 1” is active (initiated by 1/0 edge via c2106). Remedy:
|
| F07900 Drive: Motor blocked/speed controller at its limit | Cause: Motor operates longer than 0.2 seconds at torque limit and below speed threshold p2175. Remedy:
|
| F07901 Drive: Motor overspeed | Cause: The maximum permissible speed was exceeded (p1082). Remedy:
|
| A07920 Drive: Torque/speed too low | Cause: The torque deviates from the torque/speed envelope characteristic (too low). Remedy:
|
| A07921 Drive: Torque/speed too high | Cause: The torque deviates from the torque/speed envelope characteristic (too high). Remedy:
|
| A07922 Drive: Torque/speed out of tolerance | Cause: The torque deviates from the torque/speed envelope characteristic. Remedy:
|
| F07923 Drive: Torque/speed too low | Cause: The torque deviates from the torque/speed envelope characteristic (too low). Remedy:
|
| F07924 Drive: Torque/speed too high | Cause: The torque deviates from the torque/speed envelope characteristic (too high). Remedy:
|
| F07925 Drive: Torque/speed out of tolerance | Cause: The torque deviates from the torque/speed envelope characteristic. Remedy:
|
| F07934 Drive: S120 Combi motor holding brake configuration | Cause: Brake detected but not assigned to just one Combi feed drive. 0: No brake assigned. 1: Brake assigned to >1 drive. 2: Brake assigned to spindle (not permitted). 3: Safe Brake Control enabled for spindle (not permitted). Remedy:
|
| F07955 Drive: Motor has been changed | Cause: The code number of the actual motor with DRIVE-CLiQ does not match the saved number. Remedy:
|
| F07956 Drive: Motor code does not match the list (catalog) motor | Cause: Motor code of connected motor with DRIVE-CLiQ does not match possible list motor types (p0300). Remedy:
|
| F08000 TB: +/-15 V power supply faulted | Cause: Terminal Board 30 detects incorrect internal power supply voltage. 0: Error testing monitoring circuit. 1: Fault in normal operation. Remedy:
|
| F08010 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 file not loaded. Remedy:
|
| A08561 IE: Consistency error affecting adjustable parameters | Cause: Consistency error detected activating configuration for Industrial Ethernet interface (X127). Alarm values indicate specific IP/subnet/gateway errors. Remedy:
|
| A08562 PROFINET: Syntax error in configuration file | Cause: Syntax error detected in configuration file for PROFINET interface (X150). Saved file not loaded. Remedy:
|
| A08563 PROFINET: Consistency error affecting adjustable parameters | Cause: Consistency error detected activating configuration for PROFINET interface (X150). Alarm values indicate specific IP/subnet/gateway/DHCP errors. Remedy:
|
| A08566 IIOT: Syntax error in configuration file | Cause: Syntax error detected in configuration file for IIoT interface (X128). Saved file not loaded. Remedy:
|
| A08567 IIoT: Consistency error for adjustable parameters | Cause: Consistency error detected activating configuration for IIoT interface (X128). Remedy:
|
| A08800 PROFIenergy energy-saving mode active | Cause: The PROFIenergy energy-saving mode is active. Remedy:
|
| F13000 License not adequate | Cause: The converter uses options that require a license and the licenses are not sufficient or invalid. 0: No license data. 1: License data defective. 2: No license data on memory card. 3: License does not match serial number. 4-7: License data manipulated/invalid. 8-9: Internal error. Remedy:
|
| A13002 Licensing not sufficient in operation | Cause: Options requiring license used but licenses not sufficient. Values similar to F13000. Remedy:
|
| A13030 Trial License activated | Cause: The “Trial License” function was activated. One of the available periods is expiring. Remedy:
|
| 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:
|
| A13033 Trial License last period expired | Cause: The last period of the “Trial License” function has expired. No additional periods available. Remedy:
|
| F30001 Drive: overcurrent | Cause: The drive has detected an overcurrent condition. – Closed-loop control incorrect. – Short-circuit/ground fault. – Infeed issues (discharge currents, overload, short-circuit). – Power cable connection/length issues. – Defective drive/Line phase interrupted. Remedy:
|
| F30002 Drive: DC link overvoltage | Cause: Overvoltage condition in DC link. – Motor regenerates too much energy. – Device supply voltage too high. – Line phase interrupted. Remedy:
|
| F30003 Power unit: DC link voltage undervoltage | Cause: Undervoltage condition in DC link. – Line supply failure. – Line supply voltage below permissible value. – Line phase interrupted. Remedy:
|
| F30004 Power unit: Overtemperature heat sink inverter | Cause: Temperature of power unit heat sink exceeded limit. – Insufficient cooling/fan failure. – Overload. – Ambient temperature/Pulse frequency too high. Remedy:
|
| F30005 Power unit: Overload I2t (AC) | Cause: I2t overload on AC side of power unit exceeded threshold. Permissible load duty cycle/continuous load not maintained. Remedy:
|
| F30011 Power unit: Line phase failure in main circuit | Cause: DC link voltage ripple exceeded permissible limit. – Line phase failed. – Phases inadmissibly asymmetrical. – Fuse ruptured. – Motor phase failed. Remedy:
|
| F30012 Power unit: Temperature sensor wire breakage | Cause: Connection to a temperature sensor in the power unit is interrupted. Remedy:
|
| F30013 Power unit: Temperature sensor short-circuit | Cause: A temperature sensor in the power unit is short-circuited. Remedy:
|
| F30015 Power unit: Phase failure motor cable | Cause: A phase failure in the motor feeder cable was detected. Or closed-speed control is instable. Remedy:
|
| A30016 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: Hardware current limitation responded too often. – Closed-loop control incorrect. – Fault in motor/power cables. – Motor load too high. – Power unit defective. Remedy:
|
| F30020 Power unit: Configuration not supported | Cause: Configuration requested is not supported. 1: Requested DRIVE-CLiQ timing not permissible. 3: Initialization failed. 4: Power unit/converter combination not supported. 8: ASIC version not supported. Remedy:
|
| F30021 Drive: Ground fault | Cause: The drive has detected a ground fault. – Ground fault in power cables or motor. – Brake closing causes hardware DC current monitoring. – Short-circuit at braking resistor. Remedy:
|
| F30022 Power unit: Monitoring U_ce | Cause: Ground fault / inter-phase short-circuit detected. Remedy:
|
| F30022 Power unit: Monitoring U_ce | Cause: In the power unit, the monitoring of the collector-emitter voltage (U_ce) of the semiconductor has responded. Possible causes:
Remedy:
|
| F30024 Power unit: Overtemperature thermal model | Cause: The temperature difference between the power semiconductor involved and the heat sink has exceeded the permissible fault threshold.
Remedy:
|
| F30025 Power unit: Chip overtemperature | Cause: The chip temperature of the power semiconductor involved 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.
Remedy: In general:
|
| A30030 Power unit: Internal overtemperature alarm | Cause: The temperature inside the drive converter has exceeded the permissible temperature limit.
Remedy:
Notice: This alarm is automatically withdrawn once the permissible temperature limit value has been fallen below minus 5 K. |
| A30031 Power unit: Hardware current limiting in phase U | Cause: Hardware current limit for phase U responded. The pulsing in this phase is inhibited for one pulse period.
Remedy:
|
| A30032 Power unit: Hardware current limiting in phase V | Cause: Hardware current limit for phase V responded. The pulsing in this phase is inhibited for one pulse period. (Same causes as A30031) 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 A30031) Remedy:
|
| A30034 Power unit: Internal overtemperature | Cause: The alarm threshold for internal overtemperature has been reached. If the temperature inside the power unit increases up to the fault threshold, then fault F30036 is triggered.
Remedy:
|
| F30036 Power unit: Internal overtemperature | Cause: The temperature inside the converter has exceeded the permissible limit value.
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/48 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 Power unit: Undervolt 24/48 V alarm | Cause: For the power unit power supply, the lower threshold has been violated. Remedy:
|
| A30042 Power unit: Fan has reached the maximum operating hours | Cause: The maximum operating time of at least one fan will soon be reached, or has already been exceeded. Remedy: For the fan involved, carry out the following:
|
| F30043 Power unit: Overvolt 24/48 V | Cause: For the power unit power supply, the upper threshold has been violated. Remedy: Check the power supply of the power unit. |
| A30044 Power unit: Overvolt 24/48 V alarm | Cause: For the power unit power supply, the upper threshold has been violated. Remedy: Check the power supply of the power unit. |
| F30045 Power unit: Supply undervoltage | Cause: Power supply fault in the power unit. – The voltage monitor signals an undervoltage fault on the module. Remedy:
|
| A30046 Power unit: Undervoltage alarm | Cause: Before the last restart, a problem occurred at the power unit power supply. The voltage monitor in the internal FPGA of the PSA signals an undervoltage fault on the module. Remedy:
|
| A30048 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.
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: Replace the power unit module or update the EEPROM data. |
| F30053 FPGA data faulty | Cause: The FPGA data of the power unit are faulty. This can be caused, for example, if a firmware update is interrupted. Remedy: Replace the power unit or update of the FPGA data by updating the firmware. |
| 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. Remedy:
|
| F30058 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:
|
| 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. 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: It is urgently recommended that the components involved are replaced to prevent serious damage to the entire converter line-up. |
| F30068 Power unit: undertemperature inverter heat sink | Cause: The actual inverter heat sink temperature is below the permissible minimum value. Possible causes:
Remedy:
|
| A30076 Power unit: Thermal overload braking resistor alarm | Cause: The energy absorbed by the braking resistor has exceeded the alarm threshold of 80 %. If the power unit is still operated in the generator mode, then this can reach the shutdown threshold. Remedy: Reduce the power when generating. |
| A30077 Power unit: Thermal overload braking resistor | Cause: The braking resistor is thermally overloaded. This is the reason that its use was inhibited. Remedy: Reduce the power when generating. |
| F30078 Power unit: Line reactor overheated | Cause: The temperature monitoring of the line reactor has responded. In addition to the OFF2 response, the use of the braking resistor was inhibited. Remedy:
|
| A30082 Power unit: cooling medium flow rate too low alarm threshold | Cause: The flow rate is too low, and has fallen below the specified alarm threshold. If the flow rate is still too low after the specified time has expired, then fault F30083 is output. Remedy:
|
| F30083 Power unit: cooling medium flow rate too low fault threshold | Cause: The flow rate is too low, and has fallen below the specified fault threshold. Remedy:
|
| A30086 Power unit: coolant temperature has exceeded the alarm threshold | Cause: The coolant temperature has exceeded the specified alarm threshold. If the coolant temperature increases up to the specified fault threshold, then fault F30087 is output. Remedy: Check the cooling system and the ambient conditions. |
| F30087 Power unit: coolant temperature has exceeded the fault threshold | Cause: The coolant temperature has exceeded the specified fault threshold. Remedy: Check the cooling system and the ambient conditions. |
| F30105 PU: Actual value sensing fault | Cause: At least one incorrect actual value channel was detected on the Power Stack Adapter (PSA). The incorrect actual value channels are displayed in the following diagnostic parameters. Remedy: Evaluate the diagnostic parameters. If the actual value channel is incorrect, check the components and if required, replace. |
| A30250 Power unit: Overtemperature heat sink inverter | Cause: The alarm threshold for overtemperature at the inverter heat sink has been reached. Fault F30004 is initiated if the temperature of the heat sink increases by 5 K. Remedy: Check the following:
|
| A30251 Power unit: Rectifier overtemperature | Cause: The alarm threshold for the overtemperature of the rectifier has been reached. The response is set using p0290. If the temperature of the rectifier increases by an additional 5 K, then fault F30037 is triggered. Remedy: Check the following:
|
| A30252 Power unit: Chip overtemperature alarm | Cause: The chip temperature of the power semiconductor involved has exceeded the permissible alarm threshold. Remedy: Check the following:
|
| 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. The maximum output current is reduced as overload response. Remedy: Not necessary. The alarm is automatically withdrawn once the alarm threshold has been fallen below. |
| A30256 Power unit: Overload I2t (AC) | Cause: The alarm threshold for the I2t overload on the AC side of the power unit has been exceeded. Depending on the selected overload response, the output current and therefore the output frequency can be reduced. 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. Depending on the selected overload response, the output current and therefore the output frequency can be reduced. 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. The permissible load duty cycle or the continuous load was not maintained. 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: There is a hardware defect. The device must be replaced. |
| F30262 Power unit: Braking chopper defective | Cause: The braking chopper is defective. Remedy: Replace the converter. |
| F30263 Power unit: Braking chopper upper defective | Cause: The upper braking chopper is defective. Remedy: Replace the converter. |
| 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: Replace the converter. |
| 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. Remedy: Carry out a POWER ON (switch-off/switch-on). |
| 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. The permissible load duty cycle or the continuous load was not maintained. Remedy:
|
| F30314 Power unit: 24 V power supply overloaded by PM | Cause: The 24 V power supply through the Power Module (PM) is overloaded. An external 24 V power supply via X124 on the Control Unit is not connected. Remedy: Connect an external 24 V power supply via X124 at the Control Unit. |
| A30315 Power unit: 24 V power supply overloaded by PM | Cause: The 24 V power supply through the Power Module (PM) is overloaded. An external 24 V power supply via X124 on the Control Unit is not connected. Remedy: Connect an external 24 V power supply via X124 at the Control Unit. |
| A30502 Power unit: DC link overvoltage | Cause: The power unit has detected overvoltage in the DC link on a pulse inhibit.
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 to maintain the safe state. 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: Replace the module. |
| 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: Only for internal Siemens troubleshooting. |
| C30649 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:
|
| N30800 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: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. The computing time load might be too high. The sign-of-life bit in the receive telegram is not set. Remedy:
|
| F30802 Power unit: Time slice overflow | Cause: A time slice overflow has occurred. Remedy:
|
| F30804 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. 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy:
|
| F30809 Power unit: Switching information not valid | Cause: For 3P gating unit, the following applies: The last switching status word in the setpoint telegram is identified by the end ID. Such an end ID was not found. Remedy:
|
| 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: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. Error causes include checksum errors, telegram length mismatches, address mismatches, or expected SYNC telegrams missing. Remedy:
|
| F30835 Power unit DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred. The nodes do not send and receive in synchronism. Causes: Cyclic telegram not received, Timeout in telegram receive/send list. Remedy:
|
| F30836 Power unit DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. Data were not able to be sent. Telegram type does not match send list. Remedy:
|
| F30845 Power unit DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. 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 (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the power unit to the Control Unit involved. The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit. Remedy:
|
| A30853 Power unit: Sign-of-life error cyclic data | Cause: The cyclic setpoint telegrams of the power unit were not refreshed on time. Remedy:
|
| F30860 Power unit DRIVE-CLiQ (CU): Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the power unit to the Control Unit involved. Error causes: Checksum error, Telegram length mismatch, Address mismatch, or Supply voltage failure signaled. Remedy:
|
| F30875 Power unit: power supply voltage failed | Cause: The component involved has signaled that the 24 V supply has failed. The power supply voltage for the components has failed. Remedy:
|
| F30885 CU DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the power unit to the Control Unit involved. Nodes do not send/receive in synchronism. Sign-of-life bit missing, Cyclic telegram not received, Timeouts, Error at transition to cyclic operation. Remedy:
|
| F30886 PU DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred from the power unit to the Control Unit involved. Data were not able to be sent. Telegram type does not match send list. Remedy:
|
| F30895 PU DRIVE-CLiQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the power unit to the Control Unit involved. Synchronization error during alternating cyclic data transfer. Remedy:
|
| F30896 Power unit DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (power unit) have changed in an incompatible fashion (e.g. cable or component replaced). Remedy:
|
| F30899 Power unit: Unknown fault | Cause: A fault occurred on the power unit, which cannot be interpreted by the converter firmware (firmware on component is more recent than converter). Remedy:
|
| F30903 Power unit: I2C bus error occurred | Cause: Communications error with an EEPROM or an analog/digital converter. 80000000 hex: Internal software error. 00000001 … 0000FFFF hex: Module fault. Remedy:
|
| F30907 Power unit: FPGA configuration unsuccessful | Cause: During initialization within the power unit, an internal software error has occurred. Remedy:
|
| A30919 Power unit: Temperature monitoring failed | Cause: The temperature monitoring in the power unit has failed. Fault-free operation is no longer guaranteed. Remedy:
|
| F30950 Power unit: Internal software error | Cause: An internal software error has occurred. Only for internal Siemens troubleshooting. Remedy:
|
| A30999 Power unit: Unknown alarm | Cause: An alarm occurred on the power unit, which cannot be interpreted by the converter firmware. Remedy:
|
| F31110 Motor encoder: Serial communication faulted | Cause: Error in the transfer of the serial communication protocol between the encoder and evaluation module. Bits indicate: Alarm bit, Encoder not responding, CRC error, Timeout. Remedy:
|
| F31111 Motor encoder: Encoder signals an internal error (detailed information) | Cause: The encoder error word provides detailed information. Remedy:
|
| F31112 Motor encoder: Encoder signals an internal error | Cause: The encoder signals an internal error via serial protocol. Remedy:
|
| F31150 Motor encoder: Initialization error | Cause: Encoder functionality selected in p0404 cannot be executed. Encoder malfunction. Remedy:
|
| A31407 Motor encoder: Function limit reached | Cause: The encoder has reached one of its function limits. A service is recommended. 1: Incremental signals, 3: Absolute track, 4: Code connection. Remedy:
|
| A31410 Motor encoder: Communication error (encoder and Sensor Module) | Cause: Error in the transfer of the serial communication protocol. Remedy:
|
| A31411 Motor encoder: Encoder signals an internal alarm (detailed information) | Cause: The encoder error word provides detailed information (LED current incorrect, Signal amplitude outside range, Overtemperature). Remedy:
|
| A31412 Motor encoder: Encoder signals an internal alarm | Cause: The encoder signals an internal alarm via serial protocol. Remedy:
|
| F31502 Motor encoder: Encoder with measuring gearbox without valid signals | Cause: The encoder with measuring gearbox no longer provides any valid signals. Remedy:
|
| F31503 Motor encoder: Position tracking cannot be reset | Cause: The position tracking for the measuring gearbox cannot be reset. Remedy:
|
| A31700 Motor encoder: Functional safety monitoring initiated | Cause: Functional safety was activated. Self test of the DRIVE-CLiQ encoder has detected a fault. Remedy:
|
| N31800 Motor encoder: Group signal | Cause: The motor encoder has detected at least one fault. Remedy:
|
| F31801 Motor encoder DRIVE-CLiQ: Sign-of-life missing | Cause: There is a DRIVE-CLiQ communication error between the converter and the encoder involved. The sign-of-life bit is not set. Remedy:
|
| F31802 Motor encoder: Time slice overflow | Cause: A time slice overflow for the motor encoder has occurred. Remedy:
|
| F31804 Motor encoder: Sensor Module checksum error | Cause: A checksum error has occurred when reading-out the program memory on the Sensor Module. Remedy:
|
| F31805 Motor encoder: EEPROM checksum error | Cause: Data in the EEPROM corrupted. Remedy:
|
| F31813 Motor encoder: Hardware logic unit failed | Cause: The logic unit of the DRIVE-CLiQ encoder has failed (ALU watchdog or sign-of-life error). Remedy:
|
| F31820 Motor encoder DRIVE-CLiQ: Telegram error | Cause: A DRIVE-CLiQ communication error has occurred. Error causes: Checksum, length mismatch, address mismatch, SYNC telegram errors, etc. Remedy:
|
| F31835 Motor encoder DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error between converter and encoder. Nodes do not send/receive in synchronism (Cyclic telegram not received, Timeouts). Remedy:
|
| F31836 Motor encoder DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error between converter and encoder. Data were not able to be sent. Remedy:
|
| F31837 Motor encoder DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component involved. Faulty hardware cannot be excluded (Error in telegram header, Receive error, Send error). Remedy:
|
| F31845 Motor encoder DRIVE-CLiQ: Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error between the converter and the encoder involved. Synchronization error during alternating cyclic data transfer. Remedy:
|
| F31850 Motor encoder: Encoder evaluation internal software error | Cause: An internal software error has occurred in the Sensor Module of the motor encoder. Remedy:
|
| F31851 Encoder 1 DRIVE-CLiQ: Sign-of-life missing | Cause: 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. Remedy:
|
| F31860 Encoder 1 DRIVE-CLiQ: Telegram error | Cause: There is a DRIVE-CLiQ communication error from the Sensor Module involved (encoder 1) to the converter. Error causes: Checksum, length mismatch, address mismatch, SYNC errors, supply voltage failure signaled. Remedy:
|
| F31875 Motor encoder: Supply voltage failed | Cause: There is a DRIVE-CLiQ communication error from the Sensor Module involved (encoder 1) to the converter. The DRIVE-CLiQ communication signals that the supply voltage has failed. Remedy:
|
| F31885 Motor encoder DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: There is a DRIVE-CLiQ communication error between the Sensor Module (motor encoder) involved and the Control Unit. The nodes do not send and receive in synchronism. Remedy:
|
| F31886 Motor encoder DRIVE-CLiQ (CU): 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. Remedy: Carry out a POWER ON. |
| F31887 Motor encoder DRIVE-CLiQ (CU): 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. Remedy:
|
| F31895 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. Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON. |
| F31896 Motor encoder DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (Sensor Module for the motor encoder) 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 component has been replaced. Remedy:
|
| F31899 Motor encoder: Unknown fault | Cause: A fault has occurred on the Sensor Module for the motor encoder which cannot be interpreted by the Control Unit firmware (firmware on component may be more recent than Control Unit). Remedy:
|
| A31902 Motor encoder: SPI-BUS error occurred | Cause: Error when operating the internal SPI bus. Remedy:
|
| A31903 Motor encoder: I2C-BUS error occurred | Cause: Error when operating the internal I2C bus. Remedy:
|
| F31905 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. Remedy:
|
| F31950 Motor encoder: Internal software error | Cause: An internal software error has occurred. Remedy:
|
| A31999 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. Remedy:
|
| A32700 Encoder 2: Effectivity test does not supply the expected value | Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Effectivity test x unsuccessful. Remedy: Replace encoder. |
| N32800 Encoder 2: Group signal | Cause: The motor encoder has detected at least one fault. Remedy: Evaluation of other active messages. |
| F32801 Encoder 2 DRIVE-CLiQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. The sign-of-life bit in the receive telegram is not set. Remedy:
|
| F32802 Encoder 2: Time slice overflow | Cause: A time slice overflow has occurred in encoder 2. Remedy: Increase the current controller sampling time. |
| F32805 Encoder 2: EEPROM checksum error | Cause: Data in the EEPROM corrupted. Remedy: Replace the module. |
| F32813 Encoder 2: Hardware logic unit failed | Cause: The logic unit of the DRIVE-CLiQ encoder has failed. Remedy: When the error reoccurs, replace the encoder. |
| F32820 Encoder 2 DRIVE-CLiQ: Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned (Checksum error, length mismatch, etc). Remedy:
|
| F32835 Encoder 2 DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. The nodes do not send and receive in synchronism. Remedy:
|
| F32836 Encoder 2 DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Data were not able to be sent. Remedy: Carry out a POWER ON. |
| F32845 Encoder 2 DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON (switch-off/switch-on). |
| F32851 Encoder 2 DRIVE-CLiQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. The sign-of-life bit is not set. Remedy:
|
| F32860 Encoder 2 DRIVE-CLiQ (CU): Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit (Checksum error, length error, etc). Remedy:
|
| F32875 Encoder 2: power supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage has failed. Remedy:
|
| F32885 Encoder 2 DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. The nodes do not send and receive in synchronism. Remedy:
|
| F32886 Encoder 2 DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. Data were not able to be sent. Remedy: Carry out a POWER ON. |
| F32895 Encoder 2 DRIVE-CLiQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON. |
| F32896 Encoder 2 DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (Sensor Module for encoder 2) have changed in an incompatible fashion with respect to the properties when booted. Remedy:
|
| F32899 Encoder 2: Unknown fault | Cause: A fault occurred on the Sensor Module for encoder 2, which cannot be interpreted by the converter firmware (firmware version mismatch). Remedy:
|
| A32902 Encoder 2: SPI-BUS error occurred | Cause: Error when operating the internal SPI bus. Remedy:
|
| A32903 Encoder 2: I2C-BUS error occurred | Cause: Error when operating the internal I2C bus. Remedy:
|
| F32950 Encoder 2: Internal software error | Cause: An internal software error has occurred. Remedy:
|
| A32999 Encoder 2: Unknown alarm | Cause: An alarm occurred on the Sensor Module for encoder 2, which cannot be interpreted by the converter firmware. Remedy:
|
| F33899 Encoder 3: Unknown fault | Cause: A fault occurred on the Sensor Module for encoder 3, which cannot be interpreted by the converter firmware. Remedy:
|
| A33999 Encoder 3: Unknown alarm | Cause: A alarm occurred on the Sensor Module for encoder 3, which cannot be interpreted by the converter firmware. Remedy:
|
| F34851 VSM DRIVE-CLiQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit. The sign-of-life bit in the receive telegram is not set. Remedy: Upgrade the firmware of the component involved. |
| F34860 VSM DRIVE-CLiQ (CU): Telegram error | Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit (Checksum error, length error, etc). Remedy:
|
| F34875 VSM: power supply voltage failed | Cause: The component involved (VSM) has signaled that the 24 V supply has failed. Remedy:
|
| F34885 VSM DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit. The nodes do not send and receive in synchronism. Remedy:
|
| F34886 VSM DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit. Data were not able to be sent. Remedy: Carry out a POWER ON. |
| F34895 VSM DRIVE-CLiQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit. Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON. |
| F34896 VSM DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (Voltage Sensing Module) have changed in an incompatible fashion with respect to the properties when booted. Remedy:
|
| F34950 VSM: Internal software error | Cause: An internal software error in the Voltage Sensing Module (VSM) has occurred. Remedy:
|
| F35220 TM: Frequency limit reached for signal output | Cause: The signals output from the Terminal Module 41 (TM41) for tracks A/B have reached the limit frequency. The output signals are no longer in synchronism with the specified setpoint. Remedy:
|
| F35851 TM DRIVE-CLiQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit. The sign-of-life bit in the receive telegram is not set. Remedy: Upgrade the firmware of the component involved. |
| F35860 TM DRIVE-CLiQ (CU): Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit (Checksum error, length error, etc). Remedy:
|
| F35875 TM: power supply voltage failed | Cause: The component involved has signaled that the 24 V supply has failed. Remedy:
|
| F35885 TM DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit. The nodes do not send and receive in synchronism. Remedy:
|
| F35886 TM DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit. Data were not able to be sent. Error cause: 65 (= 41 hex): Telegram type does not match send list. Remedy:
|
| F35895 TM DRIVE-CLiQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit. Error cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy:
|
| F35896 TM DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (Terminal Module), specified by the fault value, have changed in an incompatible fashion with respect to the properties when booted. One cause can be, e.g. that a DRIVE-CLiQ cable or DRIVE-CLiQ component has been replaced. Remedy:
|
| F35950 TM: Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Information about the fault source. Only for internal Siemens troubleshooting. Remedy:
|
| 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:
|
| N36800 Hub: Group signal | Cause: The DRIVE-CLiQ Hub Module has detected at least one fault. Remedy:
|
| A36802 Hub: Time slice overflow | Cause: A time slice overflow has occurred on the DRIVE-CLiQ Hub Module. 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. 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy:
|
| F36837 Hub DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component involved. Faulty hardware cannot be excluded. 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. Remedy:
|
| F36851 Hub DRIVE-CLiQ (CU): Sign-of-life missing | Cause: DRIVE-CLiQ communication error from DRIVE-CLiQ Hub Module in question to Control Unit. The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit. Error cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
|
| F36860 Hub DRIVE-CLiQ (CU): Telegram error | Cause: DRIVE-CLiQ communication error from DRIVE-CLiQ Hub Module in question to Control Unit. 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. 9 (= 09 hex): The DRIVE-CLiQ communication from the component involved signals that the supply voltage has failed. 17 (= 11 hex): CRC error and the receive telegram is too early. (See manual for full list of codes 1-25) Remedy:
|
| F36875 HUB: power 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:
|
| F36885 Hub DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: DRIVE-CLiQ communication error from DRIVE-CLiQ Hub Module in question to Control Unit. The nodes do not send and receive in synchronism. 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:
|
| F36886 Hub DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data | Cause: DRIVE-CLiQ communication error from DRIVE-CLiQ Hub Module in question to Control Unit. Data were not able to be sent. Error cause: 65 (= 41 hex): Telegram type does not match send list. Remedy:
|
| F36895 Hub DRIVE-CLiQ (CU): Alternating cyclic data transfer error | Cause: DRIVE-CLiQ communication error from DRIVE-CLiQ Hub Module in question to Control Unit. Error cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy:
|
| F36896 Hub DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (DRIVE-CLiQ Hub Module), specified by the fault value, have changed in an incompatible fashion with respect to the properties when booted. 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. Remedy:
|
| A36999 Hub: Unknown alarm | Cause: An alarm has occurred on the DRIVE-CLiQ Hub Module, which 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. Remedy:
|