Siemens 6RA80 DC Drive Fault Codes:
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| F01000 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01001 FloatingPoint exception | Cause: An exception occurred during an operation with the FloatingPoint data type. The error may be caused by the basic system or a technology function (e.g. FBLOCKS, DCC, TEC). Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Refer to r9999 for further information about this fault. Bit 0 = 1: Operation invalid Bit 1 = 1: Division by zero Bit 2 = 1: Overflow Bit 3 = 1: Underflow Bit 4 = 1: Inaccurate result Remedy:
|
| F01002 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01003 Acknowledgment delay when accessing the memory | Cause: A memory area was accessed that does not return a “READY”. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| N01004 (F, A) Internal software error | Cause: An internal software error has occurred. Fault value (r0949, hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01005 Firmware download for DRIVE-CLiQ component unsuccessful | Cause: It was not possible to download the firmware to a DRIVE-CLiQ component. Fault value (r0949, interpret hexadecimal): yyxxxx hex: yy = component number, xxxx = fault cause xxxx = 000B hex: Checksum error. xxxx = 000F hex: Content rejected. xxxx = 0012 hex: Version too old. xxxx = 0013 hex: Version not suitable for hardware. xxxx = 0065 hex: No response. xxxx = 008B hex: Boot loader loaded (repeat POWER ON). xxxx = 008C hex: File not available on memory card. xxxx = 008D hex: Inconsistent file length. xxxx = 008F hex: Mode not changed. xxxx = 0090 hex: File on memory card defective. xxxx = 0091 hex: Checksum check not completed in time. xxxx = 009C hex: Component not available (p7828). Remedy:
|
| A01006 Firmware update for DRIVE-CLiQ component required | Cause: The firmware of a DRIVE-CLiQ component must be updated as there is no suitable firmware or firmware version in the component for operation with the Control Unit. Alarm value (r2124, interpret decimal): Component number of the DRIVE-CLiQ component. Remedy: Update the firmware using the commissioning tool:
|
| A01007 POWER ON for DRIVE-CLiQ component required | Cause: A DRIVE-CLiQ component must be switched on again (POWER ON) (e.g. due to a firmware update). Alarm value (r2124, interpret decimal): Component number of the DRIVE-CLiQ component. Note: For a component number = 1, a POWER ON of the Control Unit is required. Remedy:
|
| F01010 Drive type unknown | Cause: An unknown drive type was found. Fault value (r0949, interpret decimal): Drive object number (refer to p0101, p0107). Remedy:
|
| F01011 (N) Download interrupted | Cause: The project download was interrupted. Fault value (r0949, interpret decimal): 1: The user prematurely interrupted the project download. 2: The communication cable was interrupted (e.g. cable breakage, cable withdrawn). 3: The project download was prematurely exited by the commissioning tool. 100: Different versions between the firmware version and project files loaded. Remedy:
|
| F01015 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01016 (F) Firmware changed | Cause: At least one firmware file in the directory was illegally changed on the non-volatile memory with respect to the version when shipped from the factory. Alarm value (r2124, interpret decimal): 0: Checksum of one file is incorrect. 1: File missing. 2: File too many. 3: Incorrect firmware version. 4: Incorrect checksum of the back-up file. Remedy:
|
| A01017 Component lists changed | Cause: On the memory card, one file in the directory /SIEMENS/SINAMICS/DATA or /ADDON/SINAMICS/DATA has been illegally changed with respect to that supplied from the factory. No changes are permitted in this directory. Alarm value (r2124, interpret decimal): zyx dec: x = Problem, y = Directory, z = File name x = 1: File does not exist, x = 2: Version mismatch, x = 3: Checksum incorrect. (See manual for full list of ‘z’ file codes). Remedy:
|
| F01018 Booting has been interrupted several times | Cause: Module booting was interrupted several times. As a consequence, the module boots with the factory setting. Possible reasons: power supply interrupted, CPU crashed, parameterization invalid. Remedy:
|
| A01019 Writing to the removable data medium unsuccessful | Cause: The write access to the removable data medium was unsuccessful. Remedy:
|
| A01020 Writing to RAM disk unsuccessful | Cause: A write access to the internal RAM disk was unsuccessful. Remedy:
|
| F01023 Software timeout (internal) | Cause: An internal software timeout has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01030 Sign-of-life failure for master control | Cause: For active PC master control, no sign-of-life was received within the monitoring time. The master control was returned to the active BICO interconnection. Remedy:
|
| F01031 Sign-of-life failure for OFF in REMOTE | Cause: With the “OFF in REMOTE” mode active, no sign-of-life was received within 3 seconds. Remedy:
|
| A01032 (F) ACX: all parameters must be saved | Cause: The parameters of an individual drive object were saved (p0971 = 1), although there is still no backup of all drive system parameters. The saved object-specific parameters are not loaded the next time that the system powers 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. Fault value (r0949): Reference parameter whose value is 0.0. Remedy:
|
| F01034 Units changeover: Calculation parameter values after reference value change unsuccessful | Cause: The change of a reference parameter meant that for an involved parameter the selected value was not able to be re-calculated in the per unit representation. The change was rejected and the original parameter value restored. Remedy:
|
| A01035 (F) ACX: Parameter back-up file corrupted | Cause: When the Control Unit is booted, no complete data set was found from the parameter back-up files. The last time that the parameterization was saved, it was not completely carried out. Alarm value (r2124, hex): aa = 01 (Power up without backup), aa = 02 (Last available backup loaded). Remedy:
|
| F01036 (A) ACX: Parameter back-up file missing | Cause: When downloading the device parameterization, a parameter back-up file PSxxxyyy.ACX associated with a drive object cannot be found. Remedy:
|
| F01038 (A) ACX: Loading the parameter back-up file unsuccessful | Cause: An error has occurred when downloading PSxxxyyy.ACX or PTxxxyyy.ACX files from the non-volatile memory. Fault value: Byte 2 = 255 (Incorrect drive object type), 254 (Topology comparison unsuccessful). Remedy:
|
| F01039 (A) ACX: Writing to the parameter back-up file was unsuccessful | Cause: Writing to at least one parameter back-up file PSxxxyyy.*** in the non-volatile memory was unsuccessful. – file read-only. – insufficient free memory. – non-volatile memory defective. Remedy:
|
| F01040 Save parameter settings and carry out a POWER ON | Cause: A parameter was changed in the drive system which means that it is necessary to save the parameters and re-boot. Remedy:
|
| F01041 Parameter save necessary | Cause: Defective or missing files were detected on the memory card when booting. Fault value: 1 (cannot open), 2 (cannot read), 3 (directory error), 4 (setup error), 5 (write error). Remedy:
|
| F01042 Parameter error during project download | Cause: An error was detected when downloading a project using the commissioning software (e.g. incorrect parameter value). Fault value (r0949, hex): ccbbaaaa hex (aaaa=Parameter, bb=Index, cc=Fault cause). Causes include: Illegal value, limit exceeded, setting not permitted, master control inhibited, etc. Remedy:
|
| F01043 Fatal error at project download | Cause: A fatal error was detected when downloading a project using the commissioning tool. Fault value (r0949) 1-25: Various topology/device status errors (e.g., Device status cannot be changed, drive object deleted/regenerated). Remedy:
|
| F01044 CU: 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. Remedy:
|
| A01049 CU: It is not possible to write to file | Cause: It is not possible to write into a write-protected file (PSxxxxxx.acx). 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. 1: Computing time load too high. 5: Peak load too high. Remedy: For fault value = 1, 5:
|
| F01055 CU: Internal error (SYNO of port and application not identical) | Cause: All applications that operate with slaves at one port must be derived from the same SYNO clock cycle. Remedy:
|
| F01056 CU: Internal error (clock cycle of parameter group already assigned differently) | Cause: The requested parameter group (IREG, NREG, …) is already being used in a different clock cycle. Remedy:
|
| F01057 CU: Internal error (different DRIVE-CLiQ type for the slave) | Cause: The requested DRIVE-CLiQ type (hps_ps, hps_enc, …) has been specified differently for the same slave component. Remedy:
|
| F01058 CU: Internal error (slave missing in topology) | Cause: The requested slave component does not exist in the topology. Remedy:
|
| F01059 CU: Internal error (port does not exist) | Cause: The port object assigned according to the topology of the requested slave component does not exist. Remedy:
|
| F01060 CU: Internal error (parameter group not available) | Cause: The requested parameter group (IREG, NREG, …) is not offered by this slave type. Remedy:
|
| F01061 CU: Internal error (application not known) | Cause: An application that is not registered with TSM has attempted to register with registerSlaves(). Remedy:
|
| F01063 CU: Internal error (PDM) | Cause: An internal software error has occurred. Remedy:
|
| F01068 CU: Data memory memory overflow | Cause: The utilization for a data memory area is too large. Fault value (r0949, interpret binary): Bits 0-3 indicate 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. Example: Devices A and B are not compatible and a memory card with the parameter backup for device A is inserted in device B. Remedy:
|
| F01072 Memory card restored from the backup copy | Cause: The Control Unit was switched-off while writing to the memory card. This is why the visible partition became defective. After switching on, the data from the non-visible partition (backup copy) were written to the visible partition. Remedy:
|
| A01073 (N) POWER ON required for backup copy on memory card | Cause: The parameter assignment on the visible partition of the memory card has changed. In order that the backup copy on the memory card is updated on the non-visible partition, it is necessary to carry out a POWER ON or hardware reset (p0972) of the Control Unit. Note: It is possible that a new POWER ON is requested via this alarm (e.g. after saving with p0971 = 1). Remedy:
|
| F01082 Parameter error when powering 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. The detailed cause of the fault can be determined using the fault value. Fault value (r0949, interpret hexadecimal): ccbbaaaa hex aaaa = Parameter, bb = Index, cc = fault cause 0: Parameter number illegal. 1: Parameter value cannot be changed. 2: Lower or upper value limit exceeded. 3: Sub-index incorrect. 4: No array, no sub-index. 5: Data type incorrect. 6: Setting not permitted (only resetting). 7: Descriptive element cannot be changed. 9: Descriptive data not available. 11: No master control. 15: No text array available. 17: Task cannot be executed due to operating state. 20: Illegal value. 21: Response too long. 22: Parameter address illegal. 23: Format illegal. 24: Number of values not consistent. 25: Drive object does not exist. 101: Presently deactivated. 104: Illegal value. 107: Write access not permitted when controller enabled. 108: Unit unknown. 109: Write access only in the commissioning state, encoder (p0010 = 4). 110: Write access only in the commissioning state, motor (p0010 = 3). 111: Write access only in the commissioning state, power unit (p0010 = 2). 112: Write access only in the quick commissioning mode (p0010 = 1). 113: Write access only in the ready mode (p0010 = 0). 114: Write access only in the commissioning state, parameter reset (p0010 = 30). 115: Write access only in the Safety Integrated commissioning state (p0010 = 95). 116: Write access only in the commissioning state, technological application/units (p0010 = 5). 117: Write access only in the commissioning state (p0010 not equal to 0). 118: Write access only in the commissioning state, download (p0010 = 29). 119: Parameter may not be written in download. 120-127: Write access only in specific states (see manual for full details). 129: Parameter may not be written in download. 130: Transfer of the master control is inhibited via binector input p0806. 131: Required BICO interconnection not possible because BICO output does not supply floating value. 132: Free BICO interconnection inhibited via p0922. 133: Access method not defined. 200: Below the valid values. 201: Above the valid values. 202: Cannot be accessed from the Basic Operator Panel (BOP). 203: Cannot be read from the Basic Operator Panel (BOP). 204: Write access not permitted. Remedy:
|
| A01099 (N) UTC synchronization tolerance violated | Cause: The tolerance (p3109) set for UTC synchronization was violated. Note: UTC: Universal Time Coordinates. See also: p3109 (UTC synchronization tolerance). Remedy:
Note: The deviation when synchronizing is shown in r3107. |
| A01100 CU: Memory card withdrawn | Cause: The memory card (non-volatile memory) was withdrawn during operation. Notice: It is not permissible for the memory card to be withdrawn or inserted under voltage. Remedy:
|
| A01104 CU: Do not switch off. File system being optimized | Cause: The file system is currently being optimized in the non-volatile device memory of the Control Unit. This process may take several minutes. Notice: The Control Unit must not be switched off during optimization, as this can lead to user data being lost. Remedy:
Note: The alarm is automatically withdrawn once the file system has been optimized. |
| F01105 (A) CU: Insufficient memory | Cause: Too many functions have been configured on this Control Unit (e.g. too many drives, function modules, data sets, Technology Extensions, blocks, etc). Remedy:
|
| F01106 CU: Insufficient memory | Cause: There is not sufficient free memory space available. 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. – non-volatile memory is defective. – insufficient space in the non-volatile memory. 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. Fault value (r0949, interpret decimal): Number of the second drive with a SINAMICS G type power unit. Remedy:
|
| F01111 CU: Mixed operation of drive units illegal | Cause: Illegal operation of various drive units on one Control Unit: – SINAMICS S together with SINAMICS G – SINAMICS S together with SINAMICS S Value or Combi Fault value (r0949, interpret decimal): Number of the first drive object with a different power unit type. Remedy:
|
| F01112 CU: Power unit not permissible | Cause: The connected power unit cannot be used together with this Control Unit. Fault value (r0949, interpret decimal): 1: Power unit is not supported (e.g. PM240). 2: DC/AC power unit connected to CU310 not permissible. 3: Power unit (S120M) not permitted for vector control. Remedy:
|
| F01120 (A) Terminal initialization has failed | Cause: An internal software error occurred while the terminal functions were being initialized. Remedy:
|
| F01122 (A) Frequency at the measuring probe input too high | Cause: The frequency of the pulses at the measuring probe input is too high. Fault value (r0949, interpret decimal): 1: DI/DO 9 (X122.8) 2: DI/DO 10 (X122.10) … (see manual for full bit mask) 128: DI/DO 12 (X132.7) 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. Drive object type (p0107), for which the maximum permissible number of instances was exceeded. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): ddccbbaa hex Remedy:
|
| F01151 CU: Number of drive objects of a category exceeded | Cause: The maximum permissible number of drive objects of a category was exceeded. Drive object category, for which the maximum permissible number of drive objects was exceeded. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): ddccbbaa hex Remedy:
|
| 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:
|
| 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 (r0949, interpret hexadecimal): 998: Too many time slices occupied by technology functions (e.g. DCC). 999: Too many time slices occupied by the basic system. Too many different sampling times may have been set. Remedy:
|
| F01205 CU: Time slice overflow | Cause: Insufficient processing time is available for the existing topology. Remedy:
|
| F01221 CU: Basic clock cycle too low | Cause: The closed-loop control / monitoring cannot maintain the envisaged clock cycle. The runtime of the closed-loop control/monitoring is too long for the particular clock cycle or the computing time remaining in the system is not sufficient for the closed-loop control/monitoring. Remedy:
|
| F01222 CU: Basic clock cycle too low (computing time for communication not available) | Cause: A time slice has not been defined that fulfills the requirements. The port cannot be correctly operated as the alternating cyclic clock cycle cannot be maintained. Remedy:
|
| A01223 CU: Sampling time inconsistent | Cause: When changing a sampling time (p0115[0], p0799 or p4099), inconsistency between the clock cycles has been identified. Alarm value (r2124, interpret decimal): 1: Value lower than minimum value. 2: Value higher than maximum value. 3: Value not a multiple of 1.25 µs. 4: Value does not match isochronous PROFIBUS operation. 5: Value not a multiple of 125 µs. 6: Value not a multiple of 250 µs. 7: Value not a multiple of 375 µs. 8: Value not a multiple of 400 µs. 10: Special restriction of the drive object violated. 20-46: Various node/sampling time identification errors (see manual). 52-58: Nodes have been identified on the DRIVE-CLiQ line whose highest common denominator of the sampling times is less than specific values. 99: Inconsistency of cross drive objects detected. 116: Recommended clock cycle in r0116[0…1]. Remedy:
|
| A01224 CU: Pulse frequency inconsistent | Cause: When changing the minimum pulse frequency (p0113) inconsistency between the pulse frequencies was identified. Alarm value (r2124, interpret decimal): 1: Value lower than minimum value. 2: Value higher than maximum value. 3: Resulting sampling time is not a multiple of 1.25 µs. 4: Value does not match isochronous PROFIBUS operation. 10: Special restriction of the drive object violated. 99: Inconsistency of cross drive objects detected. 116: Recommended clock cycle in r0116[0…1]. Remedy:
|
| F01250 CU: CU-EEPROM incorrect read-only data | Cause: Error when reading the read-only data of the EEPROM in the Control Unit. Remedy:
|
| A01251 CU: CU-EEPROM incorrect read-write data | Cause: Error when reading the read-write data of the EEPROM in the Control Unit. Remedy:
|
| F01255 CU: Option Board EEPROM read-only data error | Cause: Error when reading the read-only data of the EEPROM in the Option Board. Remedy:
|
| A01256 CU: Option Board EEPROM read-write data error | Cause: Error when reading the read-write data of the EEPROM in the Option Board. Remedy:
|
| F01303 Component does not support the required function | Cause: A function requested by the Control Unit is not supported by a DRIVE-CLiQ component. Fault value (r0949, interpret decimal): 1: The component does not support the deactivation. 101: The Motor Module does not support an internal armature short-circuit. 102: The Motor Module does not support the deactivation. 201-203: Sensor Module support issues (value inversion, parking, deactivation). 204: Terminal Module 15 (TM15) firmware support issue. 205: Sensor Module selected temperature evaluation support issue. 206: Terminal Modules TM41/TM31/TM15 old firmware version. 207: Power unit hardware version voltage support issue. 208: Sensor Module commutation de-selection support issue. 211-216: Various Sensor Module support issues (single-track, LVDT, characteristic type, temp evaluation). Remedy:
|
| A01304 (F) Firmware version of DRIVE-CLiQ component is not up-to-date | Cause: The non-volatile memory has a more recent firmware version than the one in the connected DRIVE-CLiQ component. Remedy:
|
| F01305 Topology: Component number missing | Cause: The component number from the topology was not parameterized (p0121, p0131, p0141, p0151, p0161). Note: The fault also occurs if encoders have been configured but no component numbers exist for them. Remedy:
|
| A01306 Firmware of the DRIVE-CLiQ component being updated | Cause: Firmware update is active for at least one DRIVE-CLiQ component. Remedy:
|
| A01314 Topology: Component must not be present | Cause: For a component, “deactivate and not present” is set but this component is still in the topology. Remedy:
|
| A01317 (N) Deactivated component again present | Cause: If a component of the target topology for an active drive object is inserted and the associated parameter of the component is set to “deactivate” (p0125, p0145, p0155, p0165). Remedy:
|
| A01318 BICO: Deactivated interconnections present | Cause: This alarm is used when an inactive/non-operational drive object is active again/ready for operation, or if there are items in the list of BI/CI parameters, or if BICO interconnections have changed. Remedy:
|
| A01319 Inserted component not initialized | Cause: Initialization is required for at least one inserted component. This is only possible if the pulses are inhibited for all the drive objects. Remedy:
|
| A01320 Topology: Drive object number does not exist in configuration | Cause: A drive object number is missing in p0978. Remedy:
|
| A01321 Topology: Drive object number does not exist in configuration | Cause: p0978 contains a drive object number that does not exist. Remedy:
|
| A01322 Topology: Drive object number present twice in configuration | Cause: A drive object number is present more than once in p0978. Remedy:
|
| A01323 Topology: More than two partial lists created | Cause: Partial lists are available more than twice in p0978. After the second 0, all must be 0. Remedy:
|
| A01324 Topology: Dummy drive object number incorrectly created | Cause: In p0978, dummy drive object numbers (255) are only permitted in the first partial list. Remedy:
|
| F01325 Topology: Component number not present in target topology | Cause: The component configured in a parameter (e.g. p0121, p0131, etc.) is not present in the target topology. Fault value (r0949, interpret decimal): Configured component number that is not present in target topology. Remedy:
|
| A01330 Topology: Quick commissioning not possible | Cause: Unable to carry out a quick commissioning. The existing actual topology does not fulfill the requirements. Alarm value (r2124, interpret hexadecimal): ccccbbaa hex: cccc = preliminary component number, bb = supplementary information, aa = fault cause aa = 01 hex = 1 dec: On one component illegal connections were detected. – bb = 01 hex: For a Motor Module, more than one motor with DRIVE-CLiQ was detected. – bb = 02 hex: For a motor with DRIVE-CLiQ, the DRIVE-CLiQ cable is not connected to a Motor Module. aa = 02 hex = 2 dec: The topology contains too many components of a particular type. – bb = 01 hex: More than one master Control Unit. – bb = 02 hex: More than 1 infeed (8 for parallel). – bb = 03 hex: More than 10 Motor Modules (8 for parallel). – bb = 04 hex: More than 9 encoders. – bb = 05 hex: More than 8 Terminal Modules. – bb = 07 hex: Unknown component type. – bb = 08 hex: More than 6 drive slaves. – bb = 09 hex: Connection of a drive slave not permitted. – bb = 0a hex: There is no drive master. – bb = 0b hex: More than one motor with DRIVE-CLiQ for a parallel circuit. – bb = 0c hex: Different power units are being used in a parallel connection. aa = 03 hex = 3 dec: More than 16 components are connected at a DRIVE-CLiQ socket of the Control Unit. – bb = 0, 1, 2, 3 means e.g. detected at the DRIVE-CLiQ socket X100, X101, X102, X103. aa = 04 hex = 4 dec: The number of components connected one after the other is greater than 125. aa = 05 hex = 5 dec: The component is not permissible for SERVO. – bb = 01 hex: SINAMICS G available. – bb = 02 hex: Chassis available. aa = 06 hex = 6 dec: On one component illegal EEPROM data was detected. – bb = 01 hex: The Article No. [MLFB] of the power unit replaced includes a space retainer. aa = 07 hex = 7 dec: The actual topology contains an illegal combination of components. – bb = 01 hex: Active Line Module (ALM) and Basic Line Module (BLM). – bb = 02 hex: Active Line Module (ALM) and Smart Line Module (SLM). – bb = 03 hex: SIMOTION control and SINUMERIK component. – bb = 04 hex: SINUMERIK control and SIMOTION component. aa = 08 hex = 8 dec: The motor is not completely connected. Remedy:
|
| A01331 Topology: At least one component not assigned to a drive object | Cause: At least one component is not assigned to a drive object. – when commissioning, a component was not able to be automatically assigned to a drive object. – the parameters for the data sets are not correctly set. Alarm value (r2124, interpret decimal): Component number of the unassigned component. Remedy: This component is assigned to a drive object. Check the parameters for the data sets. Examples:
|
| F01340 Topology: Too many components on one line | Cause: For the selected communications clock cycle, too many DRIVE-CLiQ components are connected to one line of the Control Unit. Fault value (r0949, interpret hexadecimal): xyy hex (x=fault cause, yy=component number) 1yy: Communications clock cycle insufficient for read transfers. 2yy: Communications clock cycle insufficient for write transfers. 3yy: Cyclic communication is fully utilized. 4yy: The DRIVE-CLiQ cycle starts before the earliest end of the application. Dead time issues. 5yy: Internal buffer overflow for net data. 6yy: Internal buffer overflow for receive data. 7yy: Internal buffer overflow for send data. 8yy: Component clock cycles cannot be combined. 900: Lowest common multiple of clock cycles too high. 901: Lowest common multiple cannot be generated with hardware. Remedy:
|
| F01341 Topology: Maximum number of DRIVE-CLiQ components exceeded | Cause: Too many DRIVE-CLiQ components were defined in the actual topology. Note: Pulse enable is withdrawn and prevented. Remedy:
|
| F01354 Topology: Actual topology indicates an illegal component | Cause: The actual topology indicates at least one illegal component. Fault value (r0949, interpret hexadecimal): yyxx hex (yy=component number, xx=cause) xx = 1: Component at this Control Unit not permissible. xx = 2: Component in combination with another component not permissible. Remedy:
|
| F01355 Topology: Actual topology changed | Cause: The device target topology (p0099) does not correspond to the device actual topology (r0098). The fault only occurs if the topology was commissioned using the automatic internal device mechanism and not using the commissioning tool. Fault value (r0949): Only for internal Siemens troubleshooting. Remedy: One of the following counter-measures can be selected if no faults have occurred in the topology detection itself: If commissioning is still not completed:
If commissioning has already been completed:
|
| F01356 Topology: There is a defective DRIVE-CLiQ component | Cause: The actual topology indicates at least one defective DRIVE-CLiQ component. Fault value (r0949, interpret hexadecimal): zzyyxx hex zz = connection number of component where defective component is connected. yy = component number of component where defective component is connected. xx = 1: Component at this Control Unit not permissible. xx = 2: Component with communication defect. Remedy:
|
| F01357 Topology: Two Control Units identified on the DRIVE-CLiQ line | Cause: In the actual topology, 2 Control Units are connected with one another through DRIVE-CLiQ. As standard, this is not permitted unless using OALINK. Fault value (r0949, hex): yyxx (yy=connection number, xx=component number). Remedy: In general:
When using OALINK:
|
| A01358 Topology: Line termination not available | Cause: At least one line with distributed drives is not terminated. The last participant on the line must be terminated with a line termination connector. Alarm value (r2124, hex): zzyyxx (details on connection/component numbers). Remedy:
|
| 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. Fault value (r0949): Only for internal Siemens troubleshooting. Remedy:
|
| F01360 Topology: Actual topology not permissible | Cause: The detected actual topology is not permissible. Fault value (r0949, hex): ccccbbaa (aa = fault cause) aa = 01: Too many components detected (max 199). aa = 02: Component type not known. aa = 03: Illegal to combine ALM and BLM. aa = 04: Illegal to combine ALM and SLM. aa = 05: Illegal to combine BLM and SLM. aa = 06: CX32 not directly connected to permitted Control Unit. aa = 07: NX10 or NX15 not directly connected to permitted Control Unit. aa = 08: Component connected to Control Unit not permitted for this purpose. aa = 09: Component connected to Control Unit with out-of-date firmware. aa = 0A: Too many components of a particular type detected. aa = 0B: Too many components of a particular type detected on a single line. Remedy:
|
| A01361 Topology: Actual topology contains SINUMERIK and SIMOTION components | Cause: The detected actual topology contains SINUMERIK and SIMOTION components. Alarm value (r2124, hex): ddccbbaa (cc = fault cause) cc = 01: An NX10 or NX15 was connected to a SIMOTION control. cc = 02: A CX32 was connected to a SINUMERIK control. Remedy:
|
| A01362 Topology: Topology rule(s) broken | Cause: At least one topology rule for the SINAMICS S120 Combi has been broken. Alarm value (r2124) indicates which rule was violated (1-13). Example rules include wiring S120 Combi only via X200 to X100 on NCU, connection rules for Motor Modules, Sensor Modules, etc. Remedy:
|
| F01375 Topology: Connection duplicated between two components | Cause: When checking the actual topology, a ring-type connection was detected. Fault value (r0949, hex): ccbbaaaa (details on connection numbers and component class). Remedy:
|
| F01380 Topology: Actual topology EEPROM defective | Cause: When detecting the actual topology, a component with a defective EEPROM was detected. Fault value (r0949, hex): bbbbaaaa (aaaa = preliminary component number). Remedy:
|
| A01381 Topology: power unit incorrectly inserted | Cause: The topology comparison has detected a power unit in the actual topology that has been incorrectly inserted. Alarm value (r2124, hex): ddccbbaa (details on connection/component numbers). Remedy: Adapting topologies:
|
| A01381 Topology: Motor Module incorrectly inserted | Cause: The topology comparison has detected a Motor Module in the actual topology that has been incorrectly inserted with respect to the target technology. Alarm value (r2124, hex): ddccbbaa. Remedy: Adapting topologies:
|
| A01382 Topology: Sensor Module incorrectly inserted | Cause: The topology comparison has detected a Sensor Module in the actual topology that has been incorrectly inserted with respect to the target technology. Alarm value (r2124, hex): ddccbbaa. Remedy: Adapting topologies:
|
| A01383 Topology: Terminal Module incorrectly inserted | Cause: The topology comparison has detected a Terminal Module in the actual topology that has been incorrectly inserted with respect to the target technology. Remedy: Adapting topologies:
|
| A01384 Topology: DRIVE-CLiQ Hub Module incorrectly inserted | Cause: The topology comparison has detected a DRIVE-CLiQ Hub Module in the actual topology that has been incorrectly inserted with respect to the target topology. Remedy: Adapting topologies:
|
| A01385 Topology: Controller Extension incorrectly inserted | Cause: The topology comparison has detected a controller extension 32 (CX32) in the actual topology that has been incorrectly inserted with respect to the target topology. Remedy: Adapting topologies:
|
| A01386 Topology: DRIVE-CLiQ component incorrectly inserted | Cause: The topology comparison has detected a DRIVE-CLiQ component in the actual topology that has been incorrectly inserted with respect to the target topology. 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. 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. Alarm value (r2124, hex): ddccbbaa (dd = difference code). dd = 01: Different component type. dd = 02: Different article number. dd = 03: Different manufacturer. dd = 04: Incorrect subcomponent connected (e.g. Double Motor Module X201 instead of X200). dd = 05: NX10 or NX15 used instead of CX32. dd = 06: NX10 or NX15 used instead of CX32. dd = 07: Different number of connections. 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. 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. 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, hex): ccccbbaa (aa = fault cause) aa = 1B: Error not specified. aa = 1C: Value illegal. aa = 1D: Incorrect ID. aa = 1E: Incorrect ID length. aa = 1F: Too few indices left. aa = 20: Component not connected to Control Unit. Remedy:
|
| A01481 (N) Topology: power unit not connected | Cause: The topology comparison has detected a power unit that is missing in the actual topology with respect to the target topology. Remedy: Adapting topologies:
Check the hardware:
|
| A01481 (N) 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 DRIVE-CLiQ Hub Module missing in the actual topology with respect to the target topology. Remedy: Adapting topologies:
Check the hardware:
|
| A01485 Topology: Controller Extension not connected | Cause: The topology comparison has detected a Control Extension (CX32) missing in the actual topology with respect to the target topology. Remedy: Adapting topologies:
Check the hardware:
|
| A01486 Topology: DRIVE-CLiQ component not connected | Cause: The topology comparison has detected a DRIVE-CLiQ component missing in the actual topology with respect to the target topology. Remedy: Adapting topologies:
Check the hardware:
|
| A01487 Topology: Option slot component not inserted | Cause: The topology comparison has detected an option slot component missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: dd = connection number (%4) cc = component number (%3) bb = component class (%2) aa = component number of the component that has not been inserted (%1) Note: The component is described in dd, cc and bb, where the component has not been inserted. Component class and connection number are described in F01375. Remedy: Adapting topologies:
Check the hardware:
Note: Under “Topology –> Topology view” the commissioning tool where relevant offers improved diagnostics capability (e.g. setpoint/actual value comparison). |
| A01489 Topology: motor with DRIVE-CLiQ not connected | Cause: The topology comparison has detected a motor with DRIVE-CLiQ missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: dd = connection number (%4) cc = component number (%3) bb = component class (%2) aa = component number of the component that has not been inserted (%1) Note: The component is described in dd, cc and bb, where the component has not been inserted. Component class and connection number are described in F01375. Remedy: Adapting topologies:
Check the hardware:
Note: Under “Topology –> Topology view” the commissioning tool where relevant offers improved diagnostics capability (e.g. setpoint/actual value comparison). |
| A01507 (F, N) BICO: Interconnections to inactive objects present | Cause: There are BICO interconnections to an inactive/inoperable drive object. The BI/CI parameters involved are listed in r9498. The associated BO/CO parameters are listed in r9499. The list of the BICO interconnections to other drive objects is displayed in r9491 and r9492 of the deactivated drive object. Note: r9498 and r9499 are only written to, if p9495 is not set to 0. Alarm value (r2124, interpret decimal): Number of BICO interconnections found to inactive drive objects. Remedy:
|
| A01508 BICO: Interconnections to inactive objects exceeded | Cause: The maximum number of BICO interconnections (signal sinks) when deactivating a drive object was exceeded. When deactivating a drive object, all BICO interconnections (signal sinks) are listed in the following parameters: – r9498[0…29]: List of the BI/CI parameters involved. – r9499[0…29]: List of the associated BO/CO parameters. Remedy: Not necessary. This alarm is automatically withdrawn as soon as no BICO interconnection is entered in r9498[29] and r9499[29] (value = 0). Notice: When re-activating the drive object, all BICO interconnections should be checked and if required, re-established. |
| F01510 BICO: Signal source is not float type | Cause: The requested connector output does not have the correct data type. This interconnection is not established. Fault value (r0949, interpret decimal): Parameter number to which an interconnection should be made (connector output). Remedy:
|
| F01511 (A) BICO: Interconnection with different scalings | Cause: The requested BICO interconnection was established. However, a conversion is made between the BICO output and BICO input using the reference values. – the BICO output has different normalized units than the BICO input. – message only for interconnections within a drive object. Example: The BICO output has, as normalized unit, voltage and the BICO input has current. This means that the factor p2002/p2001 is calculated between the BICO output and the BICO input. Fault value (r0949, interpret decimal): Parameter number of the BICO input (signal sink). Remedy: Not necessary. |
| F01512 BICO: No scaling available | Cause: An attempt was made to determine a conversion factor for a scaling that does not exist. Fault value (r0949, interpret decimal): Unit (e.g. corresponding to SPEED) for which an attempt was made to determine a factor. Remedy:
|
| F01513 (N, A) BICO: Interconnection cross DO with different scalings | Cause: The requested BICO interconnection was established. However, a conversion is made between the BICO output and BICO input using the reference values. An interconnection is made between different drive objects and the BICO output has different normalized units than the BICO input or the normalized units are the same but the reference values are different. Example 1: BICO output with voltage normalized unit, BICO input with current normalized unit, BICO output and BICO input lie in different drive objects. Example 2: BICO output with voltage normalized unit in drive object 1 (DO1), BICO input with voltage normalized unit in drive object 2 (DO2). The reference values for voltage (p2001) of the two drive objects have different values. Fault value (r0949, interpret decimal): Parameter number of the BICO input (signal sink). Remedy: Not necessary. |
| A01514 (F) BICO: Error when writing during a reconnect | Cause: During a reconnect operation (e.g. while booting or downloading – but can also occur in normal operation) a parameter was not able to be written to. Example: When writing to BICO input with double word format (DWORD), in the second index, the memory areas overlap (e.g. p8861). The parameter is then reset to the factory setting. Alarm value (r2124, interpret decimal): Parameter number of the BICO input (signal sink). Remedy: Not necessary. |
| F01515 (A) BICO: Writing to parameter not permitted as the master control is active | Cause: When changing the number of CDS or when copying from CDS, the master control is active. Remedy:
|
| A01590 (F) Drive: Motor maintenance interval expired | Cause: The selected service/maintenance interval for this motor was reached. Alarm value (r2124, interpret decimal): Motor data set number. Remedy:
|
| F01800 DRIVE-CLiQ: Hardware/configuration error | Cause: A DRIVE-CLiQ connection fault has occurred. Fault value (r0949, interpret decimal): 100 … 107: Communication via DRIVE-CLiQ socket X100 … X107 has not been switched to cyclic operation. The cause may be an incorrect structure or a configuration that results in an impossible bus timing. 10: Loss of the DRIVE-CLiQ connection. 11: Repeated faults when detecting the connection. 12: A connection was detected but the node ID exchange mechanism does not function. Remedy: For fault value = 100 … 107:
For fault value = 10:
For fault value = 11:
For fault value = 12:
|
| A01839 DRIVE-CLiQ diagnostics: cable fault to the component | Cause: The fault counter (r9936[0…199]) to monitor the DRIVE-CLiQ connections/cables has been incremented. Alarm value (r2124, interpret decimal): Component number. Note: The component number specifies the component whose feeder cable from the direction of the Control Unit is faulted. The alarm automatically disappears after 5 seconds. Remedy:
|
| A01900 (F) PB/PN: Configuration telegram error | Cause: A controller attempts to establish a connection using an incorrect configuring telegram. Alarm value (r2124, interpret decimal): 1: Connection established to more drive objects than configured in the device. 2: Too many PZD data words for output or input to a drive object. 3: Uneven number of bytes for input or output. 4: Setting data for synchronization not accepted. 211: Unknown parameterizing block. 223: Clock synchronization for the PZD interface set in p8815[0] is not permissible. 253: PN Shared Device: Illegal mixed configuration of PROFIsafe and PZD. 254: PN Shared Device: Illegal double assignment of a slot/subslot. 255: PN: Configured drive object and existing drive object do not match. 256: PN: configured telegram cannot be set. 500: Illegal PROFIsafe configuration for the interface set in p8815[1]. 501: PROFIsafe parameter error (e.g. F_dest). 502: PROFIsafe telegram does not match. 503: PROFIsafe connection is rejected as long as there is no isochronous connection (p8969). Remedy: Check the bus configuration on the master and the slave sides. For alarm value = 1, 2:
For alarm value = 2:
For alarm value = 211:
For alarm value = 223, 500:
For alarm value = 255:
For alarm value = 256:
For alarm value = 501:
For alarm value = 502:
|
| A01902 PB/PN: clock cycle synchronous operation parameterization not permissible | Cause: Parameterization for isochronous operation is not permissible. Alarm value (r2124, interpret decimal): 0: Bus cycle time Tdp < 0.5 ms. 1: Bus cycle time Tdp > 32 ms. 2: Bus cycle time Tdp is not an integer multiple of the current controller sampling time. 3: Instant of the actual value sensing Ti > Bus cycle time Tdp or Ti = 0. 4: Instant of the actual value sensing Ti is not an integer multiple of the current controller sampling time. 5: Instant of the setpoint acceptance To >= Bus cycle time Tdp or To = 0. 6: Instant of the setpoint acceptance To is not an integer multiple of the current controller sampling time. 7: Master application cycle time Tmapc is not an integer multiple of the speed controller sampling time. 8: Bus reserve bus cycle time Tdp – data exchange time Tdx less than two current controller sampling times. 10: Instant of the setpoint acceptance To <= data exchange time Tdx + current controller sampling time. 11: Master application cycle time Tmapc > 14 x Tdp or Tmapc = 0. 12: PLL tolerance window Tpll_w > Tpll_w_max. 13: Bus cycle time Tdp is not a multiple of all basic clock cycles p0110[x]. 16: For COMM BOARD, the instant in time for the actual value sensing Ti is less than two current controller sampling times. Remedy:
For alarm value = 10:
Note: PB: PROFIBUS PN: PROFINET |
| F01910 (N, A) Fieldbus: setpoint timeout | Cause: The reception of setpoints from the fieldbus interface (onboard, PROFIBUS/PROFINET/USS) has been interrupted. – bus connection interrupted. – controller switched off. – controller set into the STOP state. See also: p2040 (Fieldbus interface monitoring time), p2047 (PROFIBUS additional monitoring time) Remedy:
Note regarding PROFIBUS slave redundancy: For operation on a Y link, it must be ensured that “DP alarm mode = DPV1” is set in the slave parameterization. |
| F01911 (N, A) PB/PN: clock cycle synchronous operation clock cycle failure | Cause: The global control telegram to synchronize the clock cycles has failed – in cyclic operation – for several DP clock cycles or has violated the time grid specified in the parameterizing telegram over several consecutive DP clock cycles (refer to the bus cycle time, Tdp and Tpllw). Remedy:
PB: PROFIBUS PN: PROFINET |
| F01915 (N, A) PB/PN: clock cycle synchronous operation sign-of-life failure drive object 1 | Cause: Group display for problems with the sign-of-life of the master (isochronous operation) on the drive object 1 (Control Unit). For central measurements, synchronism with the central master is lost. Remedy: Note: PB: PROFIBUS PN: PROFINET |
| A01920 (F) PROFIBUS: Interruption cyclic connection | Cause: The cyclic connection to the PROFIBUS master is interrupted. Remedy:
Note: If there is no communication to a higher-level control system, then p2030 should be set = 0 to suppress this message. |
| A01921 (F) PROFIBUS: Receive setpoints after To | Cause: Output data of PROFIBUS master (setpoints) received at the incorrect instant in time within the PROFIBUS clock cycle. Remedy:
|
| A01925 (F) Modbus TCP: connection interrupted | Cause: The Ethernet connection to the Modbus controller is interrupted. Remedy:
|
| A01930 PB/PN: current controller sampling time clock cycle synch. not equal | Cause: The current controller sampling time of all drives must be set the same for the clock cycle synchronous operation. Alarm value (r2124, interpret decimal): Number of the drive object with different current controller sampling time. Remedy:
|
| A01931 PB/PN: speed controller sampling time clock cycle synch. not equal | Cause: The speed controller sampling time of all drives must be set the same for the clock cycle synchronous operation. Alarm value (r2124, interpret decimal): Number of the drive object with the different speed controller sampling time. Remedy:
|
| A01940 PB/PN: clock cycle synchronism not reached | Cause: The bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing telegram. It was not possible to synchronize to the clock cycle specified by the master. – the master does not send a clock synchronous global control telegram although clock synchronous operation was selected when configuring the bus. – the master is using another clock synchronous DP clock cycle than was transferred to the slave in the parameterizing telegram. – at least one drive object has a pulse enable (not controlled from PROFIBUS/PROFINET either). Remedy:
|
| A01941 PB/PN: clock cycle signal missing when establishing bus communication | Cause: The bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing telegram. The global control telegram for synchronization is not being received. Remedy:
|
| A01943 PB/PN: clock cycle signal error when establishing bus communication | Cause: The bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing telegram. The global control telegram for synchronization is being irregularly received. – the master is sending an irregular global control telegram. – the master is using another clock synchronous DP clock cycle than was transferred to the slave in the parameterizing telegram. Remedy:
|
| A01945 PROFIBUS: Connection to the Publisher failed | Cause: For PROFIBUS peer-to-peer data transfer, the connection to at least one Publisher has failed. Alarm value (r2124, interpret binary): Bit 0 = 1: Publisher with address in r2077[0], connection failed. … Bit 15 = 1: Publisher with address in r2077[15], connection failed. Remedy:
|
| F01946 (A) PROFIBUS: Connection to the Publisher aborted | Cause: At this drive object, the connection to at least one Publisher for PROFIBUS peer-to-peer data transfer in cyclic operation has been aborted. Fault value (r0949, interpret binary): Bit 0 = 1: Publisher with address in r2077[0], connection aborted. … Bit 15 = 1: Publisher with address in r2077[15], connection aborted. Remedy:
|
| F01950 (N, A) PB/PN: clock cycle synchronous operation synchronization unsuccessful | Cause: Synchronization of the internal clock cycle to the global control telegram has failed. The internal clock cycle exhibits an unexpected shift. Remedy: Only for internal Siemens troubleshooting. |
| F01951 CU SYNC: Synchronization application clock cycle missing | Cause: If DRIVE-CLiQ components with different application clock cycle are operated on a DRIVE-CLiQ port, this requires synchronization with the Control Unit. This synchronization routine was unsuccessful. Remedy:
|
| F01952 CU DRIVE-CLiQ: Synchronization of component not supported | Cause: The existing system configuration requires that the connected DRIVE-CLiQ components support the synchronization between the basic clock cycle, DRIVE-CLiQ clock cycle and the application clock cycle. However, not all DRIVE-CLiQ components have this functionality. Fault value (r0949, interpret decimal): Component number of the first faulty DRIVE-CLiQ component. Remedy:
|
| A01953 CU SYNC: Synchronization not completed | Cause: After the drive system is switched on, the synchronization between the basic clock cycle, DRIVE-CLiQ clock cycle and application clock cycle was started but was not completed within the selected time tolerance. Remedy:
|
| F01954 CU DRIVE-CLiQ: Synchronization unsuccessful | Cause: Synchronization between the basic clock cycle, DRIVE-CLiQ clock cycle and application clock cycle was started and was not able to be successfully completed (e.g. after switch-on). Remedy:
|
| A01955 CU DRIVE-CLiQ: Synchronization DO not completed | Cause: After the drive system is switched on, the synchronization between the basic clock cycle, DRIVE-CLiQ clock cycle and application clock cycle was started but was not completed within the selected time tolerance. Remedy:
|
| A01970 CBE25: cyclic connection interrupted | Cause: The cyclic connection to the PROFINET controller is interrupted. Remedy:
|
| A01971 CBE2x: 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. Alarm value (r2124, interpret hexadecimal): yyyyxxxx hex: yyyy = info. 1, xxxx = info. 2 Info 1 = 0: number of RT connections exceeded Info 1 > 0: number of IRT connections exceeded Info 2: permitted number of connections Remedy:
|
| A01979 CBE2x: internal error for cyclic data transfer | Cause: The cyclic actual values and/or setpoints were not transferred within the specified times. Remedy:
|
| A01990 (F) USS: PZD configuration error | Cause: The configuration of the process data (PZD) for the USS protocol is incorrect. Alarm value (r2124, interpret decimal): 2: PZD amount (p2022) too great for the first drive object (p978[0]). The number of possible PZD items in a drive object is determined by the number of indices in r2050/p2051. Remedy: For alarm value = 2:
|
| A02000 Function generator: Start not possible | Cause: The function generator has already been started. Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02005 Function generator: Drive does not exist | Cause: The drive object specified for connection does not exist. Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02006 Function generator: No drive specified for connection | Cause: No drive specified for connection in p4815. Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02007 Function generator: Drive not SERVO / VECTOR / DC_CTRL | Cause: The drive object specified for connection is not a SERVO / VECTOR or DC_CTRL. Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02008 Function generator: Drive specified a multiple number of times | Cause: The drive object specified for connection is already specified. Alarm value (r2124, interpret decimal): Drive object number of the drive object that is specified a multiple number of times. Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02009 Function generator: Illegal mode | Cause: The set operating mode (p1300) of the drive object is not permissible when using the function generator. Alarm value (r2124, interpret decimal): Number of the drive object involved. Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02010 Function generator: Speed setpoint from the drive is not zero | Cause: The speed setpoint of a drive selected for connection is greater than the value for the standstill detection set using p1226. Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02011 Function generator: The actual drive speed is not zero | Cause: The speed actual value of a drive selected for connection is greater than the value for the standstill detection set using p1226. Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02015 Function generator: Drive enable signals missing | Cause: The master control and/or enable signals are missing to connect to the specified drive. Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02016 Function generator: Magnetizing running | Cause: Magnetizing has not yet been completed on a drive object specified for connection. Alarm value (r2124, interpret decimal): Number of the drive object involved. Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02020 Function generator: Parameter cannot be changed | Cause: This parameter setting cannot be changed when the function generator is active (p4800 = 1). Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02025 Function generator: Period too short | Cause: The value for the period is too short. Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02026 Function generator: Pulse width too high | Cause: The selected pulse width is too high. The pulse width must be less than the period duration. Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02030 Function generator: Physical address equals zero | Cause: The specified physical address is zero. Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02040 Function generator: Illegal value for offset | Cause: The value for the offset is higher than the value for the upper limit or lower than the value for the lower limit. Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02041 Function generator: Illegal value for bandwidth | Cause: The bandwidth referred to the time slice clock cycle of the function generator has either been set too low or too high. Depending on the time slice clock cycle, the bandwidth is defined as follows: Bandwidth_max = 1 / (2 x time slice clock cycle) Bandwidth_min = Bandwidth_max / 100000 Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02047 Function generator: Time slice clock cycle invalid | Cause: The time slice clock cycle selected does not match any of the existing time slices. Remedy:
Note: The alarm is reset by removing the cause of this alarm or restarting the function generator. |
| A02050 Trace: Start not possible | Cause: The trace has already been started. Remedy:
|
| A02051 Trace: recording not possible as a result of know-how protection | Cause: TRACE recording is not possible as at least one signal or trigger signal being used is under know-how protection. Alarm value (r2124, interpret hexadecimal): bbbbaaaa hex: aaaa = 1: recorder 0 aaaa = 2: recorder 1 aaaa = 3: recorders 0 and 1 bbbb = parameter number (hexadecimal), that was not able to be written to. Remedy:
|
| A02055 Trace: Recording time too short | Cause: The trace duration is too short. The minimum is twice the value of the trace clock cycle. Remedy:
|
| A02056 Trace: Recording cycle too short | Cause: The selected recording cycle is shorter than the selected basic clock cycle 0 (p0110[0]). See also: p4720 (Trace recording cycle) Remedy: Increase the value for the trace cycle. |
| A02057 Trace: Time slice clock cycle invalid | Cause: The time slice clock cycle selected does not match any of the existing time slices. See also: p4723 (Trace time slice cycle) Remedy: Enter an existing time slice clock cycle. The existing time slices can be read out via p7901. See also: r7901 (Sampling times) |
| A02058 Trace: Time slice clock cycle for endless trace not valid | Cause: The selected time slice clock cycle cannot be used for the endless trace. See also: p4723 (Trace time slice cycle) Remedy: Enter the clock cycle of an existing time slice with a cycle time >= 2 ms for up to 4 recording channels or >= 4 ms from 5 recording channels per trace. The existing time slices can be read out via p7901. See also: r7901 (Sampling times) |
| A02059 Trace: Time slice clock cycle for 2 x 8 recording channels not valid | Cause: The selected time slice clock cycle cannot be used for more than 4 recording channels. See also: p4723 (Trace time slice cycle) Remedy:
See also: r7901 (Sampling times) |
| A02060 Trace: Signal to be traced missing | Cause:
See also: p4730, p4731, p4732, p4733 Remedy:
|
| A02061 Trace: Invalid signal | Cause:
See also: p4730, p4731, p4732, p4733 Remedy:
|
| A02062 Trace: Invalid trigger signal | Cause:
See also: p4711 (Trace trigger signal) Remedy: Specify a valid trigger signal. |
| A02063 Trace: Invalid data type | Cause: The specified data type to select a signal using a physical address is invalid. See also: p4711, p4730, p4731, p4732, p4733 Remedy: Use a valid data type. |
| A02070 Trace: Parameter cannot be changed | Cause: The trace parameter settings cannot be changed when the trace is active. See also: p4700, p4710, p4711, p4712, p4713, p4714, p4715, p4716, p4720, p4721, p4722, p4730, p4731, p4732, p4733, p4780, p4781, p4782, p4783, p4789, p4795 Remedy:
|
| A02075 Trace: Pretrigger time too long | Cause: The selected pretrigger time must be shorter than the trace time. See also: p4721 (Trace recording time), p4722 (Trace trigger delay) Remedy: Check the pretrigger time setting and change if necessary. |
| F02080 Trace: Parameterization deleted due to unit changeover | Cause: The trace parameterization in the drive unit was deleted due to a unit changeover or a change in the reference parameters. Remedy: Restart trace. |
| A02095 MTrace 0: multiple trace cannot be activated | Cause: The following functions or settings are not permissible in conjunction with a multiple trace (trace recorder 0):
Remedy:
See also: p4840 (MTrace cycle number setting) |
| A02096 MTrace 0: cannot be saved | Cause: It is not possible to save the measurement results of a multiple trace on the memory card (trace recorder 0). A multiple trace is not started or is canceled. Alarm value (r2124, interpret decimal):
See also: p4840 (MTrace cycle number setting) Remedy:
|
| A02097 MTrace 1: multiple trace cannot be activated | Cause: The following functions or settings are not permissible in conjunction with a multiple trace (trace recorder 1):
Remedy:
See also: p4840 (MTrace cycle number setting) |
| A02098 MTrace 1: cannot be saved | Cause: It is not possible to save the measurement results of a multiple trace on the memory card (trace recorder 1). A multiple trace is not started or is canceled. Alarm value (r2124, interpret decimal):
See also: p4840 (MTrace cycle number setting) Remedy:
|
| A02099 Trace: Insufficient Control Unit memory | Cause: The memory space still available on the Control Unit is no longer sufficient for the trace function. Remedy: Reduce the memory required, e.g. as follows:
See also: r4708 (Trace memory space required), r4799 (Trace memory location free) |
| A02100 Drive: Computing dead time current controller too short | Cause: The value in p0118 produces a dead time of one clock cycle because it is prior to setpoint availability. Possible causes:
Alarm value (r2134, floating point): Minimum value for p0118 where dead time no longer occurs. Remedy:
|
| A02150 TEC: Technology Extension cannot be loaded | Cause: The system was not able to load a Technology Extension. Alarm value (r2124, interpret hexadecimal):
Remedy:
See also: r4950, r4955, p4956, r4957 |
| F02151 (A) TEC: internal software error | Cause: An internal software error has occurred within a Technology Extension. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
See also: r4950, r4955, p4956, r4957 |
| F02152 (A) TEC: insufficient memory | Cause: Too many functions have been configured on this Control Unit (e.g. too many drives, function modules, data sets, Technology Extensions, blocks, etc). Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| F02153 TEC: technology function does not exist | Cause: A technology function (e.g. Technology Extension, DCB library) does not exist on the drive device. This can occur when downloading a project or when powering up. Remedy:
|
| F03000 NVRAM fault on action | Cause: A fault occurred during execution of action p7770 = 1 or 2 for the NVRAM data. Fault value (r0949, interpret hexadecimal) yyxx hex: yy = fault cause, xx = application ID
See also: p7770 (NVRAM action) Remedy:
|
| F03001 NVRAM checksum incorrect | Cause: A checksum error occurred when evaluating the non-volatile data (NVRAM) on the Control Unit. The NVRAM data affected was deleted. Remedy: Carry out a POWER ON (switch-off/switch-on) for all components. |
| F03500 (A) TM: Initialization | Cause: When initializing the Terminal Modules, the terminals of the Control Unit or the Terminal Board 30, an internal software error has occurred. Fault value (r0949, interpret decimal): yxxx hex y = Only for internal Siemens troubleshooting xxx = component number (p0151) Remedy:
|
| A03501 TM: Sampling time change | Cause: The sampling times of the inputs/outputs were changed. This change only becomes valid after the next boot. Remedy: Carry out a POWER ON. |
| F03505 (N, A) Analog input wire breakage (Drive Object: CU, TM150, etc) | Cause: The wire-break monitoring for an analog input has responded. The input value has exceeded the threshold value parameterized in p4061[x]. Fault value (r0949, interpret decimal): yxxx dec y = analog input (0 = AI 0, 1 = AI 1) xxx = component number (p0151) Note: Monitoring is active when p4056[x] = 3 (unipolar current input monitored). Remedy:
Note: A current less than 4 mA is not displayed in r4052[x], but r4052[x] = 4 mA is output. |
| F03505 (N, A) Analog input wire breakage (Drive Object: DC_CTRL) | Cause: The wire-break monitoring for an analog input has responded. Remedy: Check the wiring for interruptions. |
| F03505 (N, A) TM: Analog input wire breakage (Drive Object: TM15DI_DO, TM31) | Cause: The wire-break monitoring for an analog input has responded. The input value has exceeded the threshold value parameterized in p4061[x]. Fault value (r0949, interpret decimal): yxxx dec y = analog input (0 = AI 0, 1 = AI 1) xxx = component number (p0151) Note: Monitoring is active when p4056[x] = 3. Remedy:
|
| A03510 (F, N) Calibration data not plausible (Drive Object: CU_DC, DC_CTRL…) | Cause: During ramp-up, the Terminal Module 31 (TM31) calibration data is read in and checked for plausibility. At least one calibration data point was determined to be invalid. Alarm value (r2124, interpret binary):
Remedy:
|
| A03510 (F, N) TM: Calibration data not plausible (Drive Object: TM150, TM15DI_DO, TM31) | Cause: During ramp-up, the Terminal Module 31 (TM31) calibration data is read in and checked for plausibility. Alarm value (r2124, interpret binary):
Remedy:
|
| A03550 TM: Speed setpoint filter natural frequency > Shannon frequency | Cause: The natural filter frequency of the speed setpoint filter (p1417) is greater than or equal to the Shannon frequency. Formula: 0.5 / p4099[3] Remedy: Reduce the natural frequency of the speed setpoint filter (PT2 low pass) (p1417). |
| F03590 (N, A) TM: Module not ready | Cause: The Terminal Module involved does not send a ready signal and no valid cyclic data. Fault value (r0949, interpret decimal): Drive object number of the Terminal Module involved. Remedy:
|
| F07082 Macro: Execution not possible | Cause: The macro cannot be executed. Fault value (r0949, interpret hexadecimal): ccccbbaa hex (cccc = param number, bb = info, aa = cause) Fault causes (aa):
Remedy:
See also: p0015, p0700, p1000, p1500 |
| F07083 Macro: ACX file not found | Cause: The ACX file (macro) to be executed was not able to be found in the appropriate directory. Fault value (r0949, interpret decimal): Parameter number with which the execution was started. Remedy: Check whether the file is saved in the appropriate directory on the memory card. Example directory: … /PMACROS/DEVICE/P15/PM001501.ACX |
| F07084 Macro: Condition for WaitUntil not fulfilled | Cause: The WaitUntil condition set in the macro was not fulfilled in a certain number of attempts. Fault value (r0949, interpret decimal): Parameter number for which the condition was set. Remedy: Check and correct the conditions for the WaitUntil loop. |
| F07085 Drive: Open-loop/closed-loop control parameters changed | Cause: Open-loop/closed-loop control parameters have had to be changed. Possible causes:
Fault value (r0949, interpret decimal): Changed parameter number. 340: Motor/control parameters auto-calculated (p0340=1) because vector control activated. 611: Time constant for thermal motor model 1 estimated. 612: Thermal motor model 1 activated (p0612.0 = 1). Remedy: Not necessary. It is not necessary to change the parameters as they have already been correctly limited. |
| F07086 Units changeover: Parameter limit violation due to reference value change | Cause: A reference parameter was changed in the system. This resulted in the fact that for the parameters involved, the selected value was not able to be written in the per unit notation. The values were set to the corresponding violated minimum/maximum limit or factory setting. Fault value (r0949, parameter): Diagnostics parameter to display the parameters that were not able to be re-calculated. See also: p0596, p2000, p2001, p2002, p2003, r2004 Remedy: Check the adapted parameter value and if required correct. See also: r9450 |
| F07088 Units changeover: Parameter limit violation due to units changeover | Cause: A changeover of units was initiated. This resulted in a violation of a parameter limit. Possible causes:
Fault value (r0949, interpret decimal): Diagnostics parameter r9451 to display all parameters whose value had to be adapted. Remedy: Check the adapted parameter values and if required correct. See also: r9451 |
| A07089 Changing over units: Function module activation is blocked because the units have been changed over | Cause: An attempt was made to activate a function module. This is not permissible if the units have already been changed over. Remedy: Restore units that have been changed over to the factory setting. |
| A07094 General parameter limit violation | Cause: As a result of the violation of a parameter limit, the parameter value was automatically corrected. Minimum/Maximum limit violated -> parameter set to min/max value. Alarm value (r2124, interpret decimal): Parameter number, whose value had to be adapted. Remedy: Check the adapted parameter values and if required correct. |
| F07110 Drive: Sampling times and basic clock cycle do not match | Cause: The parameterized sampling times do not match the basic clock cycle. Fault value (r0949, interpret decimal): The fault value specifies the parameter involved. See also: r0110, r0111, p0115 Remedy:
See also: r0110, r0111, p0112, p0115 |
| A07200 Drive: Master control ON command present | Cause: The ON/OFF1 command is present (no 0 signal). The command is either influenced via binector input p0840 (current CDS) or control word bit 0 via the master control. Remedy: Switch the signal via binector input p0840 (current CDS) or control word bit 0 via the master control to 0. |
| F07220 (N, A) Drive: Master control by PLC missing | Cause: The “master control by PLC” signal was missing in operation.
Remedy:
|
| A07350 (F) Drive: Measuring probe parameterized to a digital output | Cause: The measuring probe is connected to a bi-directional digital input/output and the terminal is set as output. Alarm value (r2124, interpret decimal):
The first designation is valid for CU320, the second for CU305. Remedy:
|
| F07426 (A) Technology controller actual value limited | Cause: The actual value for the technology controller, interconnected via connector input p2264, has reached a limit. Fault value (r0949, interpret decimal):
Remedy:
See also: p0595, p0596, p2264, p2267, p2268 |
| A07428 (N) Technology controller parameterizing error | Cause: The technology controller has a parameterizing error. Alarm value (r2124, interpret decimal): 1: The upper output limit in p2291 is set lower than the lower output limit in p2292. Remedy: For alarm value = 1: Set the output limit in p2291 higher than in p2292. See also: p2291, p2292 |
| F07447 Load gear: Position tracking, maximum actual value exceeded | Cause: When the position tracking of the load gear is configured, the drive/encoder identifies a maximum possible absolute position actual value (r2723) that can no longer be represented within 32 bits. Fault value (r0949, interpret hexadecimal): ccbbaa hex (aa=encoder data set, bb=component, cc=drive data set) Remedy:
See also: p0419, p2721 |
| F07448 (A) Load gear: Position tracking, linear axis has exceeded the maximum range | Cause: For a configured linear axis/no modulo axis, the currently effective motor encoder (encoder 1) has exceeded the maximum possible traversing range. See also: p0421, p2721 Remedy: The fault should be resolved as follows:
The fault should then be acknowledged and the absolute encoder adjusted. |
| F07449 (A) Load gear: Position tracking actual position outside tolerance window | Cause: When switched off, the currently effective motor encoder was moved through a distance greater than was parameterized in the tolerance window. It is possible that there is no longer any reference between the mechanical system and encoder. Fault value (r0949): Deviation to the last encoder position. See also: p2722, r2724 Remedy: Reset the position tracking as follows:
The fault should then be acknowledged and, if necessary, the absolute encoder adjusted (p2507). |
| F07500 Drive: Power unit data set PDS not configured | Cause: Only for controlled line supply infeed/regenerative feedback units: The power unit data set was not configured. Fault value (r0949): Drive data set number of p0185. Remedy: The index of the power unit data set associated with the drive data set should be entered into p0185. |
| F07501 Drive: Motor Data Set MDS not configured | Cause: Only for power units: The motor data set was not configured. Fault value (r0949): The fault value includes the drive data set number of p0186. Remedy: The index of the motor data set associated with the drive data set should be entered into p0186. |
| F07502 Drive: Encoder Data Set EDS not configured | Cause: Only for power units: The encoder data set was not configured. Fault value (r0949): Includes the drive data set number of p0187, p0188 and p0189. Value increased by 100 * encoder number. Remedy: The index of the encoder data set associated with the drive data set should be entered into p0187 (1st encoder), p0188 (2nd encoder) and p0189 (3rd encoder). |
| A07504 Drive: Motor data set is not assigned to a drive data set | Cause: A motor data set is not assigned to a drive object. All of the existing motor data sets in the drive data sets must be assigned using the MDS number (p0186[0…n]). Alarm value (r2124): Number of the motor data set that has not been assigned. Remedy:
|
| F07509 Drive: Component assignment missing | Cause: A Drive Data Set (DDS) is assigned to a Motor Data Set (MDS) or Encoder Data Set (EDS) that does not have a component number. Fault value (r0949, interpret decimal): nnmmmxxyyy nn: Number of MDS/EDS, mmm: Parameter number, xx: Number of DDS, yyy: Parameter number ref. Remedy: In the drive data sets, no longer assign MDS/EDS using p0186, p0187, p0188, p0189 or set a valid component number. See also: p0141, p0142, p0187, p0188 |
| F07510 Drive: Identical encoder in the drive data set | Cause: More than one encoder with identical component number is assigned to a single drive data set. In one drive data set, it is not permissible that identical encoders are operated together. Fault value (r0949): 1000 * first identical encoder + 100 * second identical encoder + drive data set. Remedy: Assign the drive data set to different encoders. See also: p0141, p0187, p0188 |
| F07511 Drive: Encoder used a multiple number of times | Cause: Each encoder may only be assigned to one drive and within a drive must – in each drive data set – either always be encoder 1, always encoder 2 or always encoder 3. This unique assignment has been violated. Fault value (r0949): The two parameters in coded form that refer to the same component number. Remedy: Correct the double use of a component number using the two parameters coded in the fault value. |
| F07512 Drive: Encoder data set changeover cannot be parameterized | Cause: Using p0141, a changeover of the encoder data set is prepared that is illegal. In this firmware release, an encoder data set changeover is only permitted for the components in the actual topology. Fault value (r0949): Incorrect EDS data set number. See also: p0187, p0188 Remedy:
|
| F07515 Drive: Power unit and motor incorrectly connected | Cause: A power unit (via PDS) was assigned to a motor (via MDS) in a drive data set that is not connected in the target topology. It is possible that a motor has not been assigned to the power unit (p0131). Fault value (r0949, interpret decimal): Number of the incorrectly parameterized drive data set. Remedy:
See also: p0121 (Power unit component number) |
| F07516 Drive: Re-commission the data set | Cause: The assignment between the drive data set and motor data set (p0186) or between the drive data set and the encoder data set was modified (p0187). This is the reason that the drive data set must re-commissioned. Fault value (r0949, interpret decimal): Drive data set to be re-commissioned. Remedy:
|
| F07517 Drive: Encoder data set changeover incorrectly parameterized | Cause: In at least two drive data sets (DDS), the same motor data set (MDS) is assigned different encoder data sets (EDS) for the motor encoder. In various DDSs, it is not permissible for an MDS to have different motor encoders. Fault value (r0949, interpret decimal): The lower 16 bits indicate the first DDS. The upper 16 bits indicate the second DDS. Remedy:
|
| F07518 Drive: Motor data set changeover incorrectly parameterized | Cause: The system has identified that two motor data sets were incorrectly parameterized. Parameter r0313, r0315 and p1982 may only have different values if the motor data sets are assigned different motors. Fault value (r0949, interpret hexadecimal): xxxx: First DDS with assigned MDS yyyy: Second DDS with assigned MDS Remedy:
|
| A07530 Drive: Drive Data Set DDS not present | Cause: The selected drive data set is not available (p0837 > p0180). The drive data set was not changed over. Remedy:
|
| A07531 Drive: Command Data Set CDS not present | Cause: The selected command data set is not available (p0836 > p0170). The command data set was not changed over. Remedy:
|
| A07541 Drive: Data set changeover not possible | Cause: The selected drive data set changeover and the assigned motor changeover are not possible and are not carried out. For synchronous motors, the motor contactor may only be switched for actual speeds less than the speed at the start of field weakening (r0063 < p0348). Remedy:
|
| A07550 (F, N) Drive: Not possible to reset encoder parameters | Cause: When carrying out a factory setting (e.g. using p0970 = 1), it was not possible to reset the encoder parameters. The encoder parameters are directly read out of the encoder via DRIVE-CLiQ. Alarm value (r2124): Component number of the encoder involved. Remedy:
|
| F07551 Drive encoder: No commutation angle information | Cause: The commutation angle information is missing. This means that synchronous motors cannot be controlled (closed loop control). Fault value (r0949, interpret decimal): yyyy = 1: The motor encoder used does not supply an absolute commutation angle. yyyy = 2: The selected ratio of the measuring gear does not match the motor pole pair number. Remedy: For fault cause = 1:
For fault cause = 2:
|
| F07552 (A) Drive encoder: Encoder configuration not supported | Cause: The requested encoder configuration is not supported. Only bits may be requested in p0404 that are signaled as being supported by the encoder evaluation in r0456. Fault value (r0949, interpret decimal cccc): 1: encoder sin/cos with absolute track (SME25). 3: Squarewave encoder (SMC30). 4: sin/cos encoder (SMC20, SMI20, SME20, SME25). 10: DRIVE-CLiQ encoder (DQI). 12: sin/cos encoder with reference mark (SME20). 15: Commutation with zero mark for separately excited synchronous motors. 23: Resolver (SMC10, SMI10). 65535: Other function. Remedy:
|
| F07553 (A) Drive encoder: Sensor Module configuration not supported | Cause: The Sensor Module does not support the requested configuration. Fault value (r0949) details: cc = 0: incorrect parameter is p0430 cc = 1: incorrect parameter is p0437 cc = 2: incorrect parameter is r0459 Remedy:
|
| F07555 (A) Drive encoder: Configuration position tracking | Cause: For position tracking, the configuration is not supported. Position tracking can only be activated for absolute encoders. Fault value (r0949) dd = fault cause: 00 hex: An absolute encoder is not being used. 01 hex: Position tracking cannot be activated (NVRAM memory insufficient). 02 hex: For a linear axis, position tracking activated for load and measuring gear. 03 hex: Position tracking cannot be activated (gear ratio/tolerance mismatch). 04 hex: A linear encoder is being used. Remedy:
|
| F07556 Measuring gear: Position tracking, maximum actual value exceeded | Cause: When the position tracking of the measuring gear is configured, the drive/encoder identifies a maximum possible absolute position actual value (r0483) that cannot be represented within 32 bits. Maximum value: p0408 * p0412 * 2^p0419 Remedy:
|
| F07560 Drive encoder: Number of pulses is not to the power of two | Cause: For rotary absolute encoders, the pulse number in p0408 must be to the power of two. Remedy:
|
| F07561 Drive encoder: Number of multiturn pulses is not to the power of two | Cause: The multiturn resolution in p0421 must be to the power of two. Remedy:
|
| F07562 (A) Drive, encoder: Position tracking, incremental encoder not possible | Cause: The requested position tracking for incremental encoders is not supported. Fault value (r0949) cccc = fault cause: 00 hex: Encoder type does not support “Position tracking incremental encoder”. 01 hex: Memory of internal NVRAM not sufficient. 04 hex: A linear encoder is used that does not support “position tracking”. Remedy:
|
| F07563 (A) Drive encoder: XIST1_ERW configuration incorrect | Cause: An incorrect configuration was identified for the “Absolute position for incremental encoder” function. Fault value 1 (= 01 hex): The “Absolute value for incremental encoder” function is not supported. Remedy:
|
| A07565 (F, N) Drive: Encoder error in PROFIdrive encoder interface 1 | Cause: An encoder error was signaled for encoder 1 via the PROFIdrive encoder interface (G1_ZSW.15). Alarm value (r2124): Error code from G1_XIST2, refer to the description regarding r0483. Remedy:
|
| A07566 (F, N) Drive: Encoder error in PROFIdrive encoder interface 2 | Cause: An encoder error was signaled for encoder 2 via the PROFIdrive encoder interface (G2_ZSW.15). Alarm value (r2124): Error code from G2_XIST2, refer to the description regarding r0483. Remedy:
|
| A07567 (F, N) Drive: Encoder error in PROFIdrive encoder interface 3 | Cause: An encoder error was signaled for encoder 3 via the PROFIdrive encoder interface (G3_ZSW.15). Alarm value (r2124): Error code from G3_XIST2, refer to the description regarding r0483. Remedy:
|
| A07569 (F) Enc identification active | Cause: During encoder identification (waiting) with p0400 = 10100, the encoder could still not be identified. Encoder identification must be supported by the encoder (EnDat, SSI, or Motor with DRIVE-CLiQ). Remedy:
|
| N07570 (F) Encoder identification data transfer running | Cause: The encoder type was automatically determined using p0400 = 10100. Note: This fault causes the pulses to be suppressed. Remedy:
|
| F07575 Drive: Motor encoder not ready | Cause: The motor encoder signals that it is not ready. Possible causes: – initialization of encoder 1 was unsuccessful. – the function “parking encoder” is active. – the encoder interface is deactivated. – the Sensor Module is defective. Remedy:
|
| A07580 (F, N) Drive: No Sensor Module with matching component number | Cause: A Sensor Module with the component number specified in p0141 was not found. Remedy:
|
| A07850 (F) External alarm 1 | Cause: The condition for “External alarm 1” is satisfied (initiated by a 1/0 edge via binector input p2112). Remedy:
|
| A07851 (F) External alarm 2 | Cause: The condition for “External alarm 2” is satisfied (initiated by a 1/0 edge via binector input p2116). Remedy:
|
| A07852 (F) External alarm 3 | Cause: The condition for “External alarm 3” is satisfied (initiated by a 1/0 edge via binector input p2117). Remedy:
|
| F07860 (A) External fault 1 | Cause: The condition for “External fault 1” is satisfied (initiated by a 1/0 edge via binector input p2106). Remedy:
|
| F07861 (A) External fault 2 | Cause: The condition for “External fault 2” is satisfied (initiated by a 1/0 edge via binector input p2107). Remedy:
|
| F07862 (A) External fault 3 | Cause: The condition for “External fault 3” is satisfied (initiated by a 1/0 edge via parameters p2108, p3111, p3112). Remedy:
|
| F08000 (N, A) TB: +/-15 V power supply faulted | Cause: Terminal Board 30 detects an incorrect internal power supply voltage. Fault value (r0949): 0: Error when testing the monitoring circuit. 1: Fault in normal operation. Remedy:
|
| F08010 (N, A) TB: Analog-digital converter | Cause: The analog/digital converter on Terminal Board 30 has not supplied any converted data. Remedy:
|
| F08500 (A) COMM BOARD: Monitoring time configuration expired | Cause: The monitoring time for the configuration has expired. Fault value (r0949): 0: Send configuration data time exceeded. 1: Receive configuration data time exceeded. Remedy:
|
| F08501 (N, A) PN/COMM BOARD: Setpoint timeout | Cause: The reception of setpoints from the COMM BOARD has been interrupted. Possible causes: bus connection interrupted, controller switched off, controller in STOP state, COMM BOARD defective. Remedy:
|
| F08502 (A) PN/COMM BOARD: Monitoring time sign-of-life expired | Cause: The monitoring time for the sign-of-life counter has expired. The connection to the COMM BOARD was interrupted. Remedy:
|
| A08504 (F) PN/COMM BOARD: Internal cyclic data transfer error | Cause: The cyclic actual and/or setpoint values were not transferred within the specified times. Alarm value (r2124): Only for internal Siemens troubleshooting. Remedy:
|
| F08510 (A) PN/COMM BOARD: Send configuration data invalid | Cause: COMM BOARD did not accept the send-configuration data. Remedy:
|
| A08511 (F) PN/COMM BOARD: Receive configuration data invalid | Cause: The drive unit did not accept the receive configuration data. Alarm value (r2124) details: 1: Connection established to more drive objects than configured. 2: Too many PZD data words. 3: Uneven number of bytes. 4: Synchronization data not accepted. 17: CBE20 Shared Device config changed. 223: Illegal clock synchronization. 500: Illegal PROFIsafe configuration. Remedy:
|
| A08520 (F) PN/COMM BOARD: Non-cyclic channel error | Cause: The memory or the buffer status of the non-cyclic channel has an error. Alarm value: 0 (buffer status), 1 (memory). Remedy:
|
| A08526 (F) PN/COMM BOARD: No cyclic connection | Cause: There is no cyclic connection to the control. Remedy:
|
| A08530 (F) PN/COMM BOARD: Message channel error | Cause: The memory or the buffer status of the message channel has an error. Remedy:
|
| A08531 (F) CBE20 POWER ON required | Cause: At least one parameter of the CBE20 was changed as a result of a project download. A POWER ON is required to activate the values. Remedy:
|
| A08550 PZD Interface Hardware assignment error | Cause: The assignment of the hardware to the PZD interface has been incorrectly parameterized. Alarm value (r2124): 1: Only one of two indices is not equal to 99. 2: Both PZD interfaces assigned to same hardware. 3: Assigned COMM BOARD missing. Remedy:
|
| A08555 Modbus TCP: commissioning error | Cause: A setting for the “Modbus TCP” protocol is incorrect. Alarm value 2: A drive object supported by Modbus is not available under p0978[0]. Remedy:
|
| A08564 PN/COMM BOARD: syntax error in the configuration file | Cause: A syntax error has been detected in the ASCII configuration file for the Communication Board Ethernet 20/25. Remedy:
|
| A08565 PNCOMM BOARD: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration (p8945). Alarm value (r2124): 0: general consistency error. 1: error in IP configuration. 2: Error in station names. 3: DHCP not activated (cyclic connection exists). Remedy:
|
| F13000 License not adequate | Cause: For the drive unit, the options that require a license are being used but the licenses are not sufficient. Fault value (r0949): 0: Existing license not sufficient. 1: Adequate license not determinable (card withdrawn). 2: Adequate license not determinable (no license data on card). 3: License key checksum error. 4: Internal error checking license. Remedy:
|
| A13001 Error in license checksum | Cause: When checking the checksum of the license key, an error was detected. Remedy:
|
| F13009 Licensing Technology Extension not licensed | Cause: At least one Technology Extension that requires a license does not have a license. Remedy:
|
| F13010 Licensing function module not licensed | Cause: At least one function module requiring a license is not licensed. Remedy:
|
| A13021 License for 600 Hz is not sufficient | Cause: You have parameterized speeds that result in output frequencies >550Hz, but the license is not sufficient. 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:
|
| F13100 Know-how protection: Copy protection error | Cause: The know-how protection with copy protection for the memory card is active. An error has occurred when checking the memory card. Fault value (r0949, interpret decimal): 0: A memory card is not inserted. 2: An invalid memory card is inserted. 3: The memory card is being used in another Control Unit. 12: An invalid memory card is inserted (OEM input incorrect, p7769). 13: The memory card is being used in another Control Unit (OEM input incorrect, p7759). Remedy:
|
| F13101 Know-how protection: Copy protection cannot be activated | Cause: An error occurred when attempting to activate the copy protection for the memory card. Fault value (r0949, interpret decimal): 0: A memory card is not inserted. Remedy:
|
| F13102 Know-how protection: Consistency error of the protected data | Cause: An error was identified when checking the consistency of the protected files. As a consequence, the project on the memory card cannot be run. Fault value (r0949, interpret hexadecimal): xxxx = 1: A file has a checksum error. xxxx = 2: The files are not consistent with one another. xxxx = 3: The project files, which were loaded into the file system via load, are inconsistent. Remedy:
|
| F30001 Power unit: Overcurrent | Cause: The power unit has detected an overcurrent condition. Possible causes include: – closed-loop control is incorrectly parameterized. – motor has a short-circuit or fault to ground (frame). – U/f operation: Up ramp set too low or rated motor current significantly greater than Motor Module. – infeed: High discharge/post-charging currents, or short-circuit currents at switch-on. – power cables not correctly connected or exceed maximum length. – power unit defective or line phase interrupted. Fault value (r0949, interpret bitwise binary): Bit 0: Phase U, Bit 1: Phase V, Bit 2: Phase W, Bit 3: Overcurrent in DC link. Remedy:
|
| F30002 Power unit: DC link voltage overvoltage | Cause: The power unit has detected overvoltage in the DC link. – motor regenerates too much energy. – device supply voltage too high. – VSM phase assignment differs from power unit. – line phase interrupted. Fault value (r0949): DC link voltage at time of trip. Remedy:
|
| F30003 Power unit: DC link voltage undervoltage | Cause: The power unit has detected an undervoltage condition in the DC link. – line supply failure. – line supply voltage below the permissible value. – line supply infeed failed or interrupted. – line phase interrupted. Remedy:
|
| F30004 Power unit: Overtemperature heat sink AC inverter | Cause: The temperature of the power unit heat sink has exceeded the permissible limit value. – insufficient cooling, fan failure. – overload. – ambient temperature too high. – pulse frequency too high. Remedy:
|
| F30005 Power unit: Overload I2t | Cause: The power unit was overloaded (r0036 = 100 %). – permissible rated power unit current exceeded for inadmissibly long time. – permissible load duty cycle not maintained. Remedy:
|
| F30006 Power unit: Thyristor Control Board | Cause: The Thyristor Control Board (TCB) of the Basic Line Module signals a fault. – no line supply voltage or contactor not closed. – line supply frequency/voltage out of range. – DC link short-circuit. – internal fault in Thyristor Control Board. Remedy:
|
| F30008 Power unit: Sign-of-life error cyclic data | Cause: The Control Unit has not punctually updated the cyclic setpoint telegram to the power unit. Consecutive tolerated sign of life errors exceeded threshold (p7789). Remedy:
|
| A30010 (F) Power unit: Sign-of-life error cyclic data | Cause: A DRIVE-CLiQ communication error has occurred. Cyclic setpoint telegrams not received on time. Remedy:
|
| F30011 Power unit: Line phase failure in main circuit | Cause: At the power unit, the DC link voltage ripple has exceeded the permissible limit value. – a line phase has failed or phases are asymmetrical. – DC link capacitor resonance. – main circuit fuse ruptured. – motor phase failed. Remedy:
|
| F30012 Power unit: Temperature sensor wire breakage | Cause: The connection to a temperature sensor in the power unit is interrupted. Fault value indicates the specific sensor (e.g., Bit 1: Air intake, Bit 2: Inverter 1, etc.). Remedy:
|
| F30013 Power unit: Temperature sensor short circuit | Cause: A temperature sensor in the power unit is short-circuited. Fault value indicates the specific sensor. Remedy:
|
| F30017 Power unit: Hardware current limit has responded too often | Cause: The hardware current limitation in the relevant phase has responded too often. Causes include incorrectly parameterized closed-loop control, high load, voltage sensing errors, missing line reactor, or defective power unit. Remedy:
|
| F30021 Power unit: Ground fault | Cause: The power has detected a ground fault. – ground fault in power cables or motor. – CT defective. – brake connection issues. – parallel switching device settings. Remedy:
|
| F30022 Power unit: Monitoring U_ce | Cause: The monitoring of the collector-emitter voltage (U_ce) of the semiconductor has responded. – fiber-optic cable interrupted. – power supply of IGBT gating module missing. – short-circuit at power unit output. – defective semiconductor. Remedy:
|
| F30025 Power unit: Chip overtemperature | Cause: The chip temperature of the semiconductor has exceeded the permissible limit value. – permissible load duty cycle not maintained. – insufficient cooling / fan failure / overload. 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. Causes include missing line voltage, open contactors, low voltage, overheated resistors, or short circuits. Fault value gives detailed status (e.g., 1: Restart inhibit, 2: Overvoltage, etc.). Remedy:
|
| A30030 Power unit: Internal overtemperature alarm | Cause: The temperature inside the drive converter has exceeded the permissible temperature limit. – insufficient cooling, fan failure, overload, or high ambient temperature. Remedy:
|
| A30031 Power unit: Hardware current limiting in phase U | Cause: Hardware current limit for phase U responded. The pulsing in this phase is inhibited for one pulse period. – closed-loop control incorrectly parameterized. – fault in motor or power cables. – motor load too high. Remedy:
|
| A30032 Power unit: Hardware current limiting in phase V | Cause: Hardware current limit for phase V responded. Remedy:
|
| A30033 Power unit: Hardware current limiting in phase W | Cause: Hardware current limit for phase W responded. Remedy:
|
| F30035 Power unit: Air intake overtemperature | Cause: The air intake in the power unit has exceeded the permissible temperature limit (55 °C for air-cooled). Remedy:
|
| F30037 Power unit: Rectifier overtemperature | Cause: The temperature in the rectifier of the power unit has exceeded the permissible temperature limit. – insufficient cooling, overload, high ambient temp, or line supply phase failure. Remedy:
|
| F30040 Power unit: Undervolt 24/48 V | Cause: The undervoltage threshold of the 24 V power supply for the power unit was fallen below for longer than 3 ms. Remedy:
|
| A30041 (F) Power unit: 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:
|
| F30043 Power unit: Overvolt 24/48 V | Cause: For the power unit power supply, the upper threshold has been violated. Remedy:
|
| A30044 (F) Power unit: Overvolt 24/48 V alarm | Cause: For the power unit power supply, the upper threshold has been violated. Remedy:
|
| F30045 Power unit: Supply undervoltage | Cause: Power supply fault in the power unit. Voltage monitor signals undervoltage. Remedy:
|
| A30046 (F) Power unit: Undervoltage alarm | Cause: Before the last restart, a problem occurred at the power unit power supply. Remedy:
|
| F30050 Power unit: 24 V supply overvoltage | Cause: The voltage monitor signals an overvoltage fault on the module. Remedy:
|
| F30051 Power unit: Motor holding brake short circuit detected | Cause: A short-circuit at the motor holding brake terminals has been detected. Remedy:
|
| F30052 EEPROM data error | Cause: EEPROM data error of the power unit module. Data incorrect or incompatible firmware. Remedy:
|
| F30053 FPGA data faulty | Cause: The FPGA data of the power unit are faulty (e.g., interrupted firmware update). Remedy:
|
| F30070 Cycle requested by the power unit module not supported | Cause: A cycle is requested that is not supported by the power unit (current control cycle or DRIVE-CLiQ cycle). Remedy:
|
| F30071 No new actual values received from the power unit | Cause: The number of actual value telegrams from the power unit module that have failed has exceeded the permissible number. Remedy:
|
| F30072 Setpoints can no longer be transferred to the power unit | Cause: More than one setpoint telegram was not able to be transferred to the power unit module. Remedy:
|
| A30073 (N) Actual value/setpoint preprocessing no longer synchronous | Cause: Communication with the power unit module is no longer in synchronism with the current control cycle. Remedy:
|
| F30074 (A) Communication error between the Control Unit and Power Module | Cause: Communications between CU and PM via interface no longer possible. CU withdrawn or incorrectly inserted. Remedy:
|
| F30081 Power unit: Switching operations too frequent | Cause: The power unit has executed too many switching operations for current limitation. – closed-loop control parameters, short-circuits, or ramp settings. Remedy:
|
| F30105 PU: Actual value sensing fault | Cause: At least one incorrect actual value channel was detected on the Power Stack Adapter (PSA). Remedy:
|
| N30800 (F) Power unit: Group signal | Cause: The power unit has detected at least one fault. Remedy:
|
| F30801 Power unit DRIVE-CLiQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. The computing time load might be too high. Fault cause 10 (= 0A hex): 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. Fault value (r0949, interpret decimal): xx = time slice number. Remedy:
|
| F30804 (N, A) Power unit: CRC | Cause: A checksum error (CRC error) has occurred for the power unit. Remedy:
|
| F30805 Power unit: EEPROM checksum error | Cause: Internal parameter data is corrupted. Fault value (r0949, interpret hexadecimal): 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:
|
| A30810 (F) Power unit: Watchdog timer | Cause: When booting it was detected that the cause of the previous reset was an SAC watchdog timer overflow. Remedy:
|
| F30820 Power unit DRIVE-CLiQ: Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. Fault cause: 1 (= 01 hex): Checksum error (CRC error). 2 (= 02 hex): Telegram is shorter than specified in the length byte or in the receive list. 3 (= 03 hex): Telegram is longer than specified in the length byte or in the receive list. 4 (= 04 hex): The length of the receive telegram does not match the receive list. 5 (= 05 hex): The type of the receive telegram does not match the receive list. 6 (= 06 hex): The address of the component in the telegram and in the receive list do not match. 7 (= 07 hex): A SYNC telegram is expected – but the received telegram is not a SYNC telegram. 8 (= 08 hex): No SYNC telegram is expected – but the received telegram is one. 9 (= 09 hex): The error bit in the receive telegram is set. 16 (= 10 hex): The receive telegram is too early. Remedy:
|
| F30835 Power unit DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. The nodes do not send and receive in synchronism. Fault cause: 33 (= 21 hex): The cyclic telegram has not been received. 34 (= 22 hex): Timeout in the telegram receive list. 64 (= 40 hex): Timeout in the telegram send list. 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. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy:
|
| F30837 Power unit DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. Fault cause: 32 (= 20 hex): Error in the telegram header. 35 (= 23 hex): Receive error: The telegram buffer memory contains an error. 66 (= 42 hex): Send error: The telegram buffer memory contains an error. 67 (= 43 hex): Send error: The telegram buffer memory contains an error. 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. Fault cause: 11 (= 0B hex): 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. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. 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. Fault cause 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. 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. Fault cause: 1 (= 01 hex): Checksum error (CRC error). 2 (= 02 hex): Telegram is shorter than specified in the length byte or in the receive list. 3 (= 03 hex): Telegram is longer than specified in the length byte or in the receive list. 4 (= 04 hex): The length of the receive telegram does not match the receive list. 5 (= 05 hex): The type of the receive telegram does not match the receive list. 6 (= 06 hex): The address of the power unit in the telegram and in the receive list do not match. 9 (= 09 hex): The DRIVE-CLiQ communication signals that the supply voltage has failed. 16 (= 10 hex): The receive telegram is too early. 17-22: Various timing and addressing errors. 25 (= 19 hex): The error bit in the receive telegram is set and the receive telegram is too early. Remedy:
|
| F30875 Power unit: power supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage has failed. Fault cause 9 (= 09 hex): 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. The nodes do not send and receive in synchronism. Fault cause: 26 (= 1A hex): Sign-of-life bit in the receive telegram not set and the receive telegram is too early. 33 (= 21 hex): The cyclic telegram has not been received. 34 (= 22 hex): Timeout in the telegram receive list. 64 (= 40 hex): Timeout in the telegram send list. 98 (= 62 hex): Error at the transition to cyclic operation. 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. Fault cause 65 (= 41 hex): Telegram type does not match send list. Remedy:
|
| F30887 Power unit DRIVE-CLiQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLiQ component (power unit) involved. Faulty hardware cannot be excluded. Fault cause: 32 (= 20 hex): Error in the telegram header. 35 (= 23 hex): Receive error: The telegram buffer memory contains an error. 66 (= 42 hex): Send error: The telegram buffer memory contains an error. 67 (= 43 hex): Send error: The telegram buffer memory contains an error. 96 (= 60 hex): Response received too late during runtime measurement. 97 (= 61 hex): Time taken to exchange characteristic data too long. 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. Fault cause 11 (= 0B hex): 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), specified by the fault value, have changed in an incompatible fashion with respect to the properties when booted. One cause can be, e.g. that a DRIVE-CLiQ cable or DRIVE-CLiQ component has been replaced. Remedy:
|
| F30899 (N, A) Power unit: Unknown fault | Cause: A fault occurred on the power unit that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Remedy:
|
| F30903 Power unit: I2C bus error occurred | Cause: Communications error with an EEPROM or an analog/digital converter. Fault value (r0949, interpret hexadecimal): 80000000 hex: internal software error. 00000001 hex … 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:
|
| A30920 (F) Power unit: Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A30999 (F, N) Power unit: Unknown alarm | Cause: An alarm occurred on the power unit that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Remedy:
|
| F31100 (N, A) Encoder 1: Zero mark distance error | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder). Remedy:
|
| F31101 (N, A) Encoder 1: Zero mark failed | Cause: The 1.5 x parameterized zero mark distance was exceeded. The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder). Remedy:
|
| F31103 (N, A) Encoder 1: Signal level zero mark (track R) outside tolerance | Cause: The zero mark signal level (track R) does not lie within the tolerance bandwidth for encoder 1. The fault can be initiated when the unipolar voltage level is exceeded (RP/RN) or if the differential amplitude is undershot. Remedy:
|
| F31110 (N, A) Encoder 1: Serial communications error | Cause: There is an error in the transfer of the serial communication protocol between the encoder and internal or external evaluation module. Fault value (r0949, interpret binary): Bit 0: Alarm bit in the position protocol. Bit 1: Incorrect quiescent level on the data line. Bit 2: Encoder does not respond. Bit 3: CRC error. Bit 4: Encoder acknowledgment error. Bit 5: Internal error in the serial driver. Bit 6: Timeout when cyclically reading. Bit 7: Timeout for the register communication. Bit 8: Protocol is too long. Bit 9: Receive buffer overflow. Bit 10: Frame error when reading twice. Bit 11: Parity error. Bit 12: Data line signal level error. Bit 13: Data line incorrect. Bit 14: Fault for the register communication. Bit 15: Internal communication error. Remedy:
|
| F31111 (N, A) Encoder 1: Encoder signals an internal error (detailed information) | Cause: The encoder error word provides detailed information (error bit). Fault value (r0949, interpret binary): Bit 0: Lighting system failed. Bit 1: Signal amplitude too low. Bit 2: Position value incorrect. Bit 3: Encoder power supply overvoltage condition. Bit 4: Encoder power supply undervoltage condition. Bit 5: Encoder power supply overcurrent condition. Bit 6: The battery must be changed. Remedy:
|
| F31112 (N, A) Encoder 1: Encoder signals an internal error | Cause: The encoder signals an internal error via serial protocol. Fault value (r0949, interpret binary): Bit 0: Fault bit in the position protocol. Remedy:
|
| F31115 (N, A) Encoder 1: Signal level track A or B too low | Cause: The signal level (root from A^2 + B^2) of the encoder falls below the permissible limit value. The nominal signal level of the encoder must lie in the range 375 mV to 600 mV. Remedy:
|
| F31116 (N, A) Encoder 1: Signal level track A or B too low | Cause: The signal level of the rectified encoder signals A and B of the encoder fall below the permissible limit value. The nominal signal level of the encoder must lie in the range 375 mV to 600 mV. Remedy:
|
| F31117 (N, A) Encoder 1: Inversion error signals A/B/R | Cause: For a square-wave encoder (bipolar, double ended) signals A*, B* and R* are not inverted with respect to signals A, B and R. Fault value (r0949, interpret binary): Bits 0 … 15: Only for internal Siemens troubleshooting. Bit 16: Error track A. Bit 17: Error track B. Bit 18: Error track R. Remedy:
|
| F31118 (N, A) Encoder 1: Speed change not plausible | Cause: For an HTL/TTL encoder, the speed change has exceeded the value in p0492 over several sampling cycles. Remedy:
|
| F31120 (N, A) Encoder 1: Encoder power supply fault | Cause: An encoder power supply fault was detected. Fault value (r0949, interpret binary): Bit 0: Undervoltage condition on the sense line. Bit 1: Overcurrent condition for the encoder power supply. Bit 2: Overcurrent condition for encoder power supply on cable resolver excitation negative. Bit 3: Overcurrent condition for encoder power supply on cable resolver excitation positive. Bit 4: The 24 V power supply through the Power Module (PM) is overloaded. Bit 5: Overcurrent at the EnDat connection of the converter. Bit 6: Overvoltage at the EnDat connection of the converter. Bit 7: Hardware fault at the EnDat connection of the converter. Remedy:
|
| F31121 (N, A) Encoder 1: Determined commutation position incorrect | Cause: A commutation position actual value sensing error was detected. Remedy:
|
| F31122 Encoder 1: Sensor Module hardware fault | Cause: An internal Sensor Module hardware fault was detected. Fault value (r0949, interpret decimal): 1: Reference voltage error. 2: Internal undervoltage. 3: Internal overvoltage. Remedy:
|
| F31123 (N, A) Encoder 1: Signal level A/B outside tolerance | Cause: The unipolar level (AP/AN or BP/BN) for encoder 1 is outside the permissible tolerance. Remedy:
|
| F31125 (N, A) Encoder 1: Signal level track A or B too high | Cause: The signal level (root from A^2 + B^2) of the encoder exceeds the permissible limit value. Remedy:
|
| F31126 (N, A) Encoder 1: Signal level track A or B too high | Cause: The signal level (|A| + |B|) of the encoder exceeds the permissible limit value. The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %). The response threshold for (|A| + |B|) is > 1120 mV or the root of (A^2 + B^2) > 955 mV. Remedy:
|
| F31129 (N, A) Encoder 1: Position difference hall sensor/track C/D and A/B too large | Cause: The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° electrical or the error for the Hall signals is greater than +/-60 ° electrical. One period of track C/D corresponds to 360 ° mechanical. One period of the Hall signal corresponds to 360 ° electrical. The monitoring responds if, for example, Hall sensors are connected as equivalent for the C/D tracks with the incorrect rotational sense or supply values that are not accurate enough. Remedy:
|
| F31130 (N, A) Encoder 1: Zero mark and position error from the coarse synchronization | Cause: After initializing the pole position using track C/D, Hall signals or pole position identification routine, the zero mark was detected outside the permissible range. For distance-coded encoders, the test is carried out after passing 2 zero marks. Fine synchronization was not carried out. Remedy:
|
| F31131 (N, A) Encoder 1: Position deviation incremental/absolute too high | Cause: Absolute encoder: When cyclically reading the absolute position, an excessively high difference to the incremental position was detected. Incremental encoder: When the zero pulse is passed, a deviation in the incremental position was detected. Remedy:
|
| F31135 Encoder 1: Fault when determining the position (single turn) | Cause: The encoder has identified a position determination fault (singleturn) and supplies status information bit by bit in an internal status/fault word. Fault value (r0949, interpret binary): Bit 0: F1 (safety status display). Bit 1: F2 (safety status display). Bit 2: Reserved (lighting). Bit 3: Reserved (signal amplitude). Bit 4: Reserved (position value). Bit 5: Reserved (overvoltage). Bit 6: Reserved (undervoltage)/hardware fault EnDat supply. Bit 7: Reserved (overcurrent)/EnDat encoder withdrawn when not in the parked state. (See list manual for full bit definitions). Remedy:
|
| F31136 Encoder 1: Fault when determining the position (multiturn) | Cause: The encoder has identified a position determination fault (multiturn) and supplies status information bit by bit in an internal status/fault word. Fault value (r0949, interpret binary): Bit 0: F1 (safety status display). Bit 1: F2 (safety status display). Bit 2: Reserved (lighting). Bit 3: Reserved (signal amplitude). (See list manual for full bit definitions). Remedy:
|
| F31137 Encoder 1: Fault when determining the position (single turn) | Cause: A position determination fault has occurred in the DRIVE-CLiQ encoder. Fault value (r0949, interpret binary): For yy = 8: Signal monitoring, F1/F2 error, LED monitoring. For yy = 11: Position word errors, temperature exceeded, power supply issues. For yy = 12: Encoder fault, internal position data transport error. For yy = 14: Temperature, position determination, FPGA, velocity errors. Remedy:
|
| F31138 Encoder 1: Fault when determining the position (multiturn) | Cause: A position determination fault has occurred in the DRIVE-CLiQ encoder. Fault value (r0949, interpret binary): For yy = 8: Signal monitoring, F1/F2 error, LED monitoring. For yy = 11: Position word errors, temperature exceeded, power supply issues. For yy = 14: Temperature, position determination, FPGA, velocity errors. Remedy:
|
| F31142 (N, A) Encoder 1: Battery voltage fault | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The battery voltage is no longer sufficient to check the multiturn information. Remedy:
|
| F31150 (N, A) Encoder 1: Initialization error | Cause: Encoder functionality selected in p0404 cannot be executed. Fault value (r0949, interpret hexadecimal): Encoder malfunction. Remedy:
|
| F31151 (N, A) Encoder 1: Encoder speed for initialization AB too high | Cause: The encoder speed is too high while initializing the Sensor Module. Remedy:
|
| F31152 (N, A) Encoder 1: Max. signal frequency (track A/B) exceeded | Cause: The maximum signal frequency of the encoder evaluation has been exceeded. See also: p0408 (Rotary encoder pulse number). Remedy:
|
| F31153 (N, A) Encoder 1: Identification error | Cause: An error has occurred when identifying the encoder (waiting) p0400 = 10100. The connected encoder was not able to be identified. Bit 0: Data length incorrect. Remedy:
|
| F31160 (N, A) Encoder 1: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Fault value (r0949, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside the measuring range set in (p4673). 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy:
|
| F31161 (N, A) Encoder 1: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Fault value (r0949, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside the selected measuring range (p4675). 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy:
|
| F31163 (N, A) Encoder 1: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Fault value (r0949, interpret decimal): 1: Position value from the LVDT sensor. 2: Position value from the encoder characteristic. Remedy:
|
| A31400 (F, N) Encoder 1: Zero mark distance error (alarm threshold exceeded) | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. For distance-coded encoders, the zero mark distance is determined from zero marks detected pairs. Remedy:
|
| A31401 (F, N) Encoder 1: Zero mark failed (alarm threshold exceeded) | Cause: The 1.5x parameterized zero mark distance was exceeded without a zero mark being detected. The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder). Remedy:
|
| F31405 (N, A) Encoder 1: Temperature in the encoder evaluation exceeded | Cause: An inadmissibly high temperature was detected in the encoder electronics or the encoder evaluation. Remedy:
|
| A31407 (F, N) Encoder 1: Function limit reached | Cause: The encoder has reached one of its function limits. A service is recommended. Alarm value (r2124, interpret decimal): 1: Incremental signals. 3: Absolute track. 4: Code connection. Remedy:
|
| A31410 (F, N) Encoder 1: Communication error (encoder and Sensor Module) | Cause: Serial communication protocol transfer error between the encoder and evaluation module. Alarm value includes bits for Alarm, Incorrect quiescent level, CRC error, Timeout, Protocol too long, etc. Remedy:
|
| A31411 (F, N) Encoder 1: Encoder signals an internal alarm (detailed information) | Cause: The absolute encoder fault word includes alarm bits that have been set. yyyy = 0: Frequency exceeded, Temperature exceeded, Battery discharged, Reference point passed. yyyy = 1: Signal amplitude outside control range, Error multiturn interface, Internal data error, Error EEPROM, etc. Remedy:
|
| A31412 (F, N) Encoder 1: Encoder signals an internal alarm | Cause: The encoder signals an internal alarm via serial protocol. Bit 0: Fault bit in the position protocol. Bit 1: Alarm bit in the position protocol. Remedy:
|
| A31414 (F, N) Encoder 1: Signal level track C or D out of tolerance | Cause: The signal level (C^2 + D^2) of track C or D of the encoder or from the Hall signals, is not within the tolerance bandwidth. Remedy:
|
| N31415 (F, A) Encoder 1: Signal level track A or B outside tolerance (alarm) | Cause: The signal level (root from A^2 + B^2) of the encoder is outside the permissible tolerance. The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %). Remedy:
|
| A31418 (F, N) Encoder 1: Speed change not plausible (alarm) | Cause: For an HTL/TTL encoder, the speed change has exceeded the value in p0492 over several sampling cycles. The change to the averaged speed actual value – if applicable – is monitored in the current controller sampling time. Remedy:
|
| A31419 (F, N) Encoder 1: Track A or B outside tolerance | Cause: The amplitude/phase/offset correction for track A or B is at the limit. Alarm value provides specific details on Offset, Amplitude, Phase, or Cubic correction limits. Remedy:
|
| A31421 (F, N) Encoder 1: Determined commutation position incorrect (alarm) | Cause: A commutation position actual value sensing error was detected. 3: The absolute position of the serial protocol and track A/B differ by half an encoder pulse. Remedy:
|
| A31422 (F, N) Encoder 1: Pulses per revolution square-wave encoder outside tolerance bandwidth | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. This alarm is triggered with active square-wave encoder PPR correction. Remedy:
|
| A31429 (F, N) Encoder 1: Position difference hall sensor/track C/D and A/B too large | Cause: The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° electrical or the error for the Hall signals is greater than +/-60 ° electrical. The monitoring responds if, for example, Hall sensors are connected as equivalent for the C/D tracks with the incorrect rotational sense or supply values. Remedy:
|
| A31431 (F, N) Encoder 1: Position deviation incremental/absolute too high (alarm) | Cause: When the zero pulse is passed, a deviation in the incremental position was detected. Checked against equidistant zero marks or distance-coded zero marks. Remedy:
|
| A31432 (F, N) Encoder 1: Rotor position adaptation corrects deviation | Cause: On track A/B, pulses have been lost or too many have been counted. These pulses are presently being corrected. Remedy:
|
| A31442 (F, N) Encoder 1: Battery voltage alarm threshold reached | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The multiturn information can no longer be buffered if the battery voltage drops even further. Remedy:
|
| A31443 (F, N) Encoder 1: Signal level track C/D outside tolerance (alarm) | Cause: The unipolar level (CP/CN or DP/DN) for encoder 1 is outside the permissible tolerance. Remedy:
|
| A31460 (N) Encoder 1: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. 1: Input voltage outside detectable measuring range. 2: Input voltage outside measuring range set in p4673. 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy:
|
| A31461 (N) Encoder 1: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. 1: Input voltage outside detectable measuring range. 2: Input voltage outside the selected measuring range (p4675). 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy:
|
| A31462 (N) Encoder 1: Analog sensor no channel active | Cause: Channel A and B are not activated for the analog sensor. Remedy:
|
| A31463 (N) Encoder 1: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Alarm value (r2124, interpret decimal): 1: Position value from the LVDT sensor. 2: Position value from the encoder characteristic. Remedy: For alarm value = 1:
For alarm value = 2:
|
| A31470 (F, N) Encoder 1: Encoder signals an internal error (X521.7) | Cause: For the Sensor Module Cabinet 30 (SMC30), a dirty encoder is signaled via a 0 signal at terminal X521.7. Remedy:
|
| F31500 (N, A) Encoder 1: Position tracking traversing range exceeded | Cause: For a configured linear axis without modulo correction, the drive/encoder has exceeded the maximum possible traversing range. The value should be read in p0412 and interpreted as the number of motor revolutions. For p0411.0 = 1, the maximum traversing range for the configured linear axis is defined to be 64x (+/- 32x) of p0421. For p0411.3 = 1, the maximum traversing range for the configured linear axis is preset (default value) to the highest possible value and is +/-p0412/2 (rounded off to complete revolutions). The highest possible value depends on the pulse number (p0408) and the fine resolution (p0419). Remedy: The fault should be resolved as follows:
The fault should then be acknowledged and the absolute encoder adjusted. |
| F31501 (N, A) Encoder 1: Position tracking encoder position outside tolerance window | Cause: When switched off, the drive/encoder was moved through a distance greater than was parameterized in the tolerance window. It is possible that there is no longer any reference between the mechanical system and encoder. Fault value (r0949, interpret decimal): Deviation (difference) to the last encoder position in increments of the absolute value. The sign designates the traversing direction. Note: The deviation (difference) found is also displayed in r0477. See also: p0413, r0477. Remedy: Reset the position tracking as follows:
The fault should then be acknowledged and, if necessary, the absolute encoder adjusted (p2507). See also: p0010. |
| F31502 (N, A) Encoder 1: Encoder with measuring gear without valid signals | Cause: The encoder with measuring gear no longer provides any valid signals. Remedy:
|
| F31503 (N, A) Encoder 1: Position tracking cannot be reset | Cause: The position tracking for the measuring gear cannot be reset. Remedy: The fault should be resolved as follows:
The fault should then be acknowledged and the absolute encoder adjusted. |
| A31700 Encoder 1: Functional safety monitoring initiated | Cause: Functional safety was activated. Self-test of the DRIVE-CLiQ encoder has detected a fault. Alarm value (r2124, interpret binary): Bit x = 1: Effectivity test x unsuccessful. Remedy:
|
| N31800 (F) Encoder 1: Group signal | Cause: The motor encoder has detected at least one fault. Remedy:
|
| F31801 (N, A) Encoder 1 DRIVE-CLiQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Fault cause 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause. Remedy:
|
| F31802 (N, A) Encoder 1: Time slice overflow | Cause: A time slice overflow has occurred in encoder 1. Fault value (r0949, interpret hexadecimal): yx hex: y = function involved, x = time slice involved. x = 9: Time slice overflow of the fast (current controller clock cycle) time slice. x = A: Time slice overflow of the average time slice. x = C: Time slice overflow of the slow time slice. yx = 3E7: Timeout when waiting for SYNO (e.g. unexpected return to non-cyclic operation). Remedy:
Note: For a current controller sampling time = 31.25 µs, use an SMx20 with Article No. 6SL3055-0AA00-5xA3. |
| F31804 (N, A) Encoder 1: Sensor Module checksum error | Cause: A checksum error has occurred when reading-out the program memory on the Sensor Module. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex yyyy: Memory area involved. xxxx: Difference between the checksum at POWER ON and the actual checksum. Remedy:
|
| F31805 (N, A) Encoder 1: EEPROM checksum error | Cause: Data in the EEPROM corrupted. Fault value (r0949, interpret hexadecimal): 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy:
|
| F31806 (N, A) Encoder 1: Initialization error | Cause: The encoder was not successfully initialized. Fault value (r0949, interpret hexadecimal): Bit 0, 1: Encoder initialization with the motor rotating has failed. Bit 2-9: Mid-voltage matching failures (Tracks A, B, Safety A/B, C, D, R). Bit 10-15: Difference in mid-voltages too great. Bit 16-20: Internal faults/errors. Bit 28-31: Errors regarding EnDat 2.2 measuring unit. Remedy: Acknowledge fault. If the fault cannot be acknowledged:
|
| A31811 (F, N) Encoder 1: Encoder serial number changed | Cause: The serial number of the motor encoder of a synchronous motor has changed. Cause 1: the encoder was replaced. Cause 2: a third-party, built-in or linear motor was re-commissioned. Cause 3: the motor with integrated and adjusted encoder was replaced. Cause 4: the firmware was updated to a version that checks the encoder serial number. Remedy: For causes 1, 2:
For causes 3, 4:
|
| F31812 (N, A) Encoder 1: Requested cycle or RX-/TX timing not supported | Cause: A cycle requested from the Control Unit or RX/TX timing is not supported. Fault value (r0949, interpret decimal): 0: Application cycle is not supported. 1: DRIVE-CLiQ cycle is not supported. 2: Distance between RX and TX instants in time too low. 3: TX instant in time too early. Remedy:
|
| F31813 Encoder 1: Hardware logic unit failed | Cause: The logic unit of the DRIVE-CLiQ encoder has failed. Fault value (r0949, interpret binary): Bit 0: ALU watchdog has responded. Bit 1: ALU has detected a sign-of-life error. Remedy:
|
| F31820 (N, A) Encoder 1 DRIVE-CLiQ: Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. Fault cause (hex): 01: Checksum error (CRC error). 02, 03, 04, 05, 06: Telegram length/address issues. 07: SYNC telegram expected but received telegram is not SYNC. 08: No SYNC telegram expected but received telegram is one. 09: Error bit in receive telegram is set. 10: Receive telegram too early. Remedy:
|
| F31835 (N, A) Encoder 1 DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. The nodes do not send and receive in synchronism. Fault cause (hex): 21: Cyclic telegram not received. 22: Timeout in telegram receive list. 40: Timeout in telegram send list. Remedy:
|
| F31836 (N, A) Encoder 1 DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Data were not able to be sent. Fault cause 65 (= 41 hex): Telegram type does not match send list. Remedy:
|
| F31837 (N, A) Encoder 1 DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. Fault cause (hex): 20: Error in telegram header. 23: Receive error: Telegram buffer memory contains an error. 42: Send error: Telegram buffer memory contains an error. 43: Send error: Telegram buffer memory contains an error. Remedy:
|
| F31845 (N, A) Encoder 1 DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Fault cause 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy:
|
| F31850 (N, A) Encoder 1: Encoder evaluation internal software error | Cause: An internal software error has occurred in the Sensor Module of encoder 1. Fault value (r0949, interpret decimal): 1: Background time slice is blocked. 2: Checksum over the code memory is not OK. 10000+: Various memory/EEPROM/Configuration errors. 16000+: DRIVE-CLiQ encoder initialization/ALU/Safety errors. Remedy:
|
| F31851 (N, A) Encoder 1 DRIVE-CLiQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 1) involved to the Control Unit. The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit. Fault cause 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
|
| F31860 (N, A) Encoder 1 DRIVE-CLiQ (CU): Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 1) involved to the Control Unit. Fault cause (hex): 01 (CRC), 02-06 (Length/Address mismatch), 09 (Signal supply voltage failed), 10-19 (Telegram timing/errors). Remedy:
|
| F31875 (N, A) Encoder 1: power supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage has failed. Fault cause 9 (= 09 hex): The power supply voltage for the components has failed. Remedy:
|
| F31885 (N, A) Encoder 1 DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 1) involved to the Control Unit. The nodes do not send and receive in synchronism. Fault cause (hex): 1A (Sign-of-life not set), 21 (Cyclic telegram not received), 22 (Timeout receive list), 40 (Timeout send list), 62 (Error at transition to cyclic operation). Remedy:
|
| F31886 (N, A) Encoder 1 DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 1) involved to the Control Unit. Data were not able to be sent. Fault cause 65 (= 41 hex): Telegram type does not match send list. Remedy:
|
| F31887 (N, A) Encoder 1 DRIVE-CLiQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLiQ component involved (Sensor Module for encoder 1). Faulty hardware cannot be excluded. Fault cause (hex): 20, 23, 42, 43 (Telegram buffer errors), 60 (Response received too late), 61 (Time taken to exchange characteristic data too long). Remedy:
|
| F31895 (N, A) Encoder 1 DRIVE-CLiQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 1) involved to the Control Unit. Fault cause 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy:
|
| F31896 (N, A) Encoder 1 DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (Sensor Module for encoder 1) 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 component has been replaced. Remedy:
|
| F31899 (N, A) Encoder 1: Unknown fault | Cause: A fault occurred on the Sensor Module for encoder 1 that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Remedy:
|
| A31902 (F, N) Encoder 1: SPI-BUS error occurred | Cause: Error when operating the internal SPI bus. Remedy:
|
| A31903 (F, N) Encoder 1: I2C-BUS error occurred | Cause: Error when operating the internal I2C bus. Remedy:
|
| F31905 (N, A) Encoder 1: Encoder parameterization error | Cause: An error was identified in the encoder parameterization. It is possible that the parameterized encoder type does not match the connected encoder. Fault value (r0949) determines the parameter index (p0187). Common causes include issues with EnDat/SSI encoder protocols, HTL level support, SQW encoder values, or linear scale pole pair widths. Remedy:
|
| F31912 Encoder 1: Device combination is not permissible | Cause: The selected device combination is not supported. Fault value (r0949): 1003, 1005: Measuring unit not supported by EnDat 2.2 converter. 1006: Max duration of EnDat transfer exceeded. 2001: Cycle combination not supported. 2002: Resolution does not match pole pair width. Remedy:
|
| A31915 (F, N) Encoder 1: Encoder configuration error | Cause: The configuration for encoder 1 is incorrect. Alarm value (r2124, interpret decimal): 1: Re-parameterization between fault/alarm is not permissible. 419: When the fine resolution Gx_XIST2 is configured, the encoder identifies a maximum possible absolute position actual value (r0483) that can no longer be represented within 32 bits. Remedy:
|
| F31916 (N, A) Encoder 1: Encoder parameterization error | Cause: An encoder parameter was detected as being incorrect. The parameterized encoder type might not match the connected encoder. Remedy:
|
| A31920 (F, N) Encoder 1: Temperature sensor fault (motor) | Cause: The motor detected a fault when evaluating the temperature sensor. Fault cause: 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A31930 (N) Encoder 1: Data logger has saved data | Cause: For the activated function “Data logger” (p0437.0 = 1) a fault has occurred with the Sensor Module. This alarm indicates that the diagnostics data corresponding to the fault was saved on the memory card. Remedy:
|
| A31940 (F, N) Encoder 1: Spindle sensor S1 voltage incorrect | Cause: The voltage of analog sensor S1 is outside the permissible range. Alarm value (r2124): Signal level from sensor S1. Remedy:
|
| F31950 Encoder 1: Internal software error | Cause: An internal software error has occurred. Only for internal Siemens troubleshooting. Remedy:
|
| A31999 (F, N) Encoder 1: Unknown alarm | Cause: A alarm has occurred on the Sensor Module for encoder 1 that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Remedy:
|
| F32100 (N, A) Encoder 2: Zero mark distance error | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. Remedy:
|
| F32101 (N, A) Encoder 2: Zero mark failed | Cause: The 1.5 x parameterized zero mark distance was exceeded. Remedy:
|
| F32103 (N, A) Encoder 2: Signal level zero track (track R) outside tolerance | Cause: The zero mark signal level (track R) does not lie within the tolerance bandwidth for encoder 2. Remedy:
|
| F32110 (N, A) Encoder 2: Serial communications error | Cause: There is an error in the transfer of the serial communication protocol between the encoder and internal or external evaluation module. Fault value bits (r0949) indicate specific errors (Alarm bit, CRC error, Timeout, etc) for EnDat 2.1/2.2 encoders. Remedy:
|
| F32111 (N, A) Encoder 2: Encoder signals an internal error (detailed information) | Cause: Fault cause: %1 bin, additional information: %2 The encoder error word provides detailed information (error bit). For p0404.8 = 0, the following applies: Fault value for internal Siemens troubleshooting. For p0404.8 = 1, the following applies: Fault value (r0949, interpret binary): yyyyxxxx hex: yyyy = supplementary information, xxxx = fault cause yyyy = 0: Bit 0: Lighting system failed. Bit 1: Signal amplitude too low. Bit 2: Position value incorrect. Bit 3: Encoder power supply overvoltage condition. Bit 4: Encoder power supply undervoltage condition. Bit 5: Encoder power supply overcurrent condition. Bit 6: The battery must be changed. Remedy: For yyyy = 0:
For yyyy = 1:
|
| F32112 (N, A) Encoder 2: Encoder signals an internal error | Cause: The encoder signals a set error bit via the serial protocol. Fault value (r0949, interpret binary): Bit 0: Fault bit in the position protocol. Remedy:
|
| F32115 (N, A) Encoder 2: Signal level track A or B too low | Cause: The signal level (root from A^2 + B^2) of the encoder falls below the permissible limit value. The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %). The response threshold is < 170 mV (input frequency <= 256 kHz) or < 120 mV (input frequency > 256 kHz). Note: The analog values of the amplitude error are not measured at the same time with the hardware fault output by the Sensor Module. Remedy:
|
| F32116 (N, A) Encoder 2: Signal level track A or B too low | Cause: The signal level of the rectified encoder signals A and B of the encoder fall below the permissible limit value. The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %). The response threshold is < 130 mV. Remedy:
|
| F32117 (N, A) Encoder 2: Inversion error signals A/B/R | Cause: For a square-wave encoder (bipolar, double ended) signals A*, B* and R* are not inverted with respect to signals A, B and R. Fault value (r0949, interpret binary): Bit 16: Error track A. Bit 17: Error track B. Bit 18: Error track R. Remedy:
|
| F32118 (N, A) Encoder 2: Speed change not plausible | Cause: For an HTL/TTL encoder, the speed change has exceeded the value in p0492 over several sampling cycles. See also: p0492 (Square-wave encoder maximum speed difference per sampling cycle). Remedy:
|
| F32120 (N, A) Encoder 2: Encoder power supply fault | Cause: An encoder power supply fault was detected. Fault value (r0949, interpret binary): Bit 0: Undervoltage condition on the sense line. Bit 1: Overcurrent condition for the encoder power supply. Bit 2: Overcurrent condition for encoder power supply on cable resolver excitation negative. Bit 3: Overcurrent condition for encoder power supply on cable resolver excitation positive. Bit 4: The 24 V power supply through the Power Module (PM) is overloaded. Bit 5: Overcurrent at the EnDat connection of the converter. Bit 6: Overvoltage at the EnDat connection of the converter. Bit 7: Hardware fault at the EnDat connection of the converter. Remedy:
|
| F32121 (N, A) Encoder 2: Determined commutation position incorrect | Cause: A commutation position actual value sensing error was detected. Remedy:
|
| F32122 Encoder 2: Sensor Module hardware fault | Cause: An internal Sensor Module hardware fault was detected. Fault value (r0949, interpret decimal): 1: Reference voltage error. 2: Internal undervoltage. 3: Internal overvoltage. Remedy:
|
| F32123 (N, A) Encoder 2: Signal level A/B outside tolerance | Cause: The unipolar level (AP/AN or BP/BN) for encoder 2 is outside the permissible tolerance. Fault value (r0949, interpret binary): Bit 0 = 1: Either AP or AN outside the tolerance. Bit 16 = 1: Either BP or BN outside the tolerance. The unipolar nominal signal level of the encoder must lie in the range 2500 mV +/- 500 mV. Remedy:
|
| F32125 (N, A) Encoder 2: Signal level track A or B too high | Cause: The signal level (root from A^2 + B^2) of the encoder exceeds the permissible limit value. The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %). The response threshold is > 750 mV. Remedy:
|
| F32126 (N, A) Encoder 2: Signal level track A or B too high | Cause: The signal level (|A| + |B|) of the encoder exceeds the permissible limit value. The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %). The response threshold for (|A| + |B|) is > 1120 mV or the root of (A^2 + B^2) > 955 mV. Remedy:
|
| F32129 (N, A) Encoder 2: Position difference hall sensor/track C/D and A/B too large | Cause: The error for track C/D is greater than +/-15° mechanical or +/-60° electrical or the error for the Hall signals is greater than +/-60° electrical. Fault value (r0949, interpret decimal): For track C/D: Measured deviation as mechanical angle. For Hall signals: Measured deviation as electrical angle. Remedy:
|
| F32130 (N, A) Encoder 2: Zero mark and position error from the coarse synchronization | Cause: After initializing the pole position using track C/D, Hall signals or pole position identification routine, the zero mark was detected outside the permissible range. Scaling: 32768 dec = 180°. Remedy:
|
| F32131 (N, A) Encoder 2: Position deviation incremental/absolute too high | Cause: Absolute encoder: When cyclically reading the absolute position, an excessively high difference to the incremental position was detected. The absolute position that was read is rejected. Limit value for the deviation: EnDat encoder: Is supplied from the encoder and is a minimum of 2 quadrants. Other encoders: 15 pulses = 60 quadrants. Incremental encoder: When the zero pulse is passed, a deviation in the incremental position was detected. Remedy:
|
| F32135 Encoder 2: Fault when determining the position (single turn) | Cause: The encoder has identified a position determination fault (singleturn) and supplies status information bit by bit in an internal status/fault word. Fault value (r0949, interpret binary): See manual for specific bit definitions (Bit 0 to Bit 31) regarding F1/F2 safety status, lighting, signal amplitude, overvoltage, etc. Remedy:
|
| F32136 Encoder 2: Fault when determining the position (multiturn) | Cause: The encoder has identified a position determination fault (multiturn) and supplies status information bit by bit in an internal status/fault word. See manual for specific bit definitions (Bit 0 to Bit 31). Remedy:
|
| F32137 Encoder 2: Fault when determining the position (single turn) | Cause: A position determination fault has occurred in the DRIVE-CLiQ encoder. Fault value (r0949, interpret binary): yyxxxxxx hex: yy = encoder version, xxxxxx = bit coding of the fault cause. Specific bit codes exist for yy = 8, yy = 11, yy = 12, yy = 14. Remedy:
|
| F32138 Encoder 2: Fault when determining the position (multiturn) | Cause: A position determination fault has occurred in the DRIVE-CLiQ encoder (multiturn). Fault value (r0949, interpret binary): yyxxxxxx hex: yy = encoder version, xxxxxx = bit coding. Remedy:
|
| F32142 (N, A) Encoder 2: Battery voltage fault | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The battery voltage is no longer sufficient to check the multiturn information. Remedy:
|
| F32150 (N, A) Encoder 2: Initialization error | Cause: Encoder functionality selected in p0404 cannot be executed. Fault value (r0949, interpret hexadecimal): Encoder malfunction. The bit assignment corresponds to that of p0404 (e.g. bit 5 set: Error track C/D). Remedy:
|
| F32151 (N, A) Encoder 2: Encoder speed for initialization AB too high | Cause: The encoder speed is too high while initializing the Sensor Module. Remedy:
|
| F32152 (N, A) Encoder 2: Max. signal frequency (track A/B) exceeded | Cause: The maximum signal frequency of the encoder evaluation has been exceeded. Fault value (r0949, interpret decimal): Actual input frequency in Hz. Remedy:
|
| F32153 (N, A) Encoder 2: Identification error | Cause: An error has occurred when identifying the encoder (waiting) p0400 = 10100. The connected encoder was not able to be identified. Fault value (r0949, interpret hexadecimal): Bit 0: Data length incorrect. Remedy:
|
| F32160 (N, A) Encoder 2: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Fault value (r0949, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside the measuring range set in (p4673). 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy:
|
| F32161 (N, A) Encoder 2: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Fault value (r0949, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside the selected measuring range (p4675). 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy:
|
| F32163 (N, A) Encoder 2: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Fault value (r0949, interpret decimal): 1: Position value from the LVDT sensor. 2: Position value from the encoder characteristic. Remedy:
|
| A32400 (F, N) Encoder 2: Zero mark distance error (alarm threshold exceeded) | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder). Remedy:
|
| A32401 (F, N) Encoder 2: Zero mark failed (alarm threshold exceeded) | Cause: The 1.5x parameterized zero mark distance was exceeded without a zero mark being detected. The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder). Remedy:
|
| F32405 (N, A) Encoder 2: Temperature in the encoder evaluation exceeded | Cause: Overtemperature of the electronic components (6) An inadmissibly high temperature was detected in the encoder electronics or the encoder evaluation. Fault value (r0949, interpret hexadecimal): yyxxxx hex: yy = temperature sensor number, xxxx = measured module temperature in 0.1 °C. Remedy:
|
| A32407 (F, N) Encoder 2: Function limit reached | Cause: The encoder has reached one of its function limits. A service is recommended. Alarm value (r2124, interpret decimal): 1: Incremental signals 3: Absolute track 4: Code connection Remedy:
|
| A32410 (F, N) Encoder 2: Communication error (encoder and Sensor Module) | Cause: Serial communication protocol transfer error between the encoder and evaluation module. Alarm value (r2124, interpret binary): Bit 0: Alarm bit in the position protocol. Bit 1: Incorrect quiescent level on the data line. Bit 2: Encoder does not respond. Bit 3: CRC error. Bit 6: Timeout when cyclically reading. Bit 9: Receive buffer overflow. Remedy:
|
| A32411 (F, N) Encoder 2: Encoder signals an internal alarm (detailed information) | Cause: The absolute encoder fault word includes alarm bits that have been set. Alarm value (r2124, interpret binary): yyyyxxxx hex: yyyy = supplementary information, xxxx = fault cause yyyy = 0: Bit 0: Frequency exceeded (speed too high). Bit 1: Temperature exceeded. Bit 2: Control reserve, lighting system exceeded. Bit 3: Battery discharged. Bit 4: Reference point passed. yyyy = 1: Bit 0: Signal amplitude outside the control range. Bit 1: Error multiturn interface. Bit 2: Internal data error (singleturn/multiturn not with single steps). Bit 3: Error EEPROM interface. Bit 4: SAR converter error. Bit 5: Fault for the register data transfer. Bit 6: Internal error identified at the error pin (nErr). Bit 7: Temperature threshold exceeded or fallen below. Remedy:
|
| A32412 (F, N) Encoder 2: Encoder signals an internal alarm | Cause: The encoder signals an internal alarm via serial protocol. Alarm value (r2124, interpret binary): Bit 0: Fault bit in the position protocol. Bit 1: Alarm bit in the position protocol. Remedy:
|
| A32414 (F, N) Encoder 2: Signal level track C or D out of tolerance | Cause: The signal level (C^2 + D^2) of track C or D of the encoder or from the Hall signals, is not within the tolerance bandwidth. Alarm value (r2124, interpret hexadecimal): yyyyxxxx hex: yyyy = Signal level, track D (16 bits with sign). xxxx = Signal level, track C (16 bits with sign). The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %). The response thresholds are < 230 mV (observe the frequency response of the encoder) and > 750 mV. A signal level of 500 mV peak value corresponds to the numerical value 5333 hex = 21299 dec. Note: If the amplitude is not within the tolerance bandwidth, then it cannot be used to initialize the start position. Remedy:
|
| N32415 (F, A) Encoder 2: Signal level track A or B outside tolerance (alarm) | Cause: The signal level (root from A^2 + B^2) of the encoder is outside the permissible tolerance. Alarm value (r2124, interpret hexadecimal): yyyyxxxx hex: yyyy = Angle xxxx = amplitude, i.e. root of A^2 + B^2 (16 bits without sign) The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %). The response threshold is < 230 mV (observe the frequency response of the encoder). A signal level of 500 mV peak value corresponds to the numerical value 299A hex = 10650 dec. The angle 0 … FFFF hex corresponds to 0 … 360 degrees of the fine position. Zero degrees is present at the negative zero crossover of track B. Note for Sensor Modules for resolvers (e.g. SMC10): The nominal signal level is at 2900 mV (2.0 Vrms). The response threshold is < 1414 mV (1.0 Vrms). A signal level of 2900 mV peak value corresponds to the numerical value 3333 hex = 13107 dec. Note: The analog values of the amplitude error are not measured at the same time with the hardware fault output by the Sensor Module. Remedy:
|
| A32418 (F, N) Encoder 2: Speed change not plausible (alarm) | Cause: For an HTL/TTL encoder, the speed change has exceeded the value in p0492 over several sampling cycles. The change to the averaged speed actual value – if applicable – is monitored in the current controller sampling time. Alarm value (r2124, interpret decimal): Only for internal Siemens troubleshooting. See also: p0492 (Square-wave encoder maximum speed difference per sampling cycle) Remedy:
|
| A32419 (F, N) Encoder 2: Track A or B outside tolerance | Cause: The amplitude/phase/offset correction for track A or B is at the limit. Amplitude error correction: Amplitude B / Amplitude A = 0.78 … 1.27 Phase: <84 degrees or >96 degrees SMC20: Offset correction: +/-140 mV SMC10: Offset correction: +/-650 mV Alarm value (r2124, interpret hexadecimal): xxxx1: Minimum of the offset correction, track B xxxx2: Maximum of the offset correction, track B xxx1x: Minimum of the offset correction, track A xxx2x: Maximum of the offset correction, track A xx1xx: Minimum of the amplitude correction, track B/A xx2xx: Maximum of the amplitude correction, track B/A x1xxx: Minimum of the phase error correction x2xxx: Maximum of the phase error correction 1xxxx: Minimum of the cubic correction 2xxxx: Maximum of the cubic correction Remedy:
|
| A32421 (F, N) Encoder 2: Determined commutation position incorrect (alarm) | Cause: A commutation position actual value sensing error was detected. Alarm value (r2124, interpret decimal): 3: The absolute position of the serial protocol and track A/B differ by half an encoder pulse. The absolute position must have its zero position in the quadrants in which both tracks are negative. In the case of a fault, the position can be incorrect by one encoder pulse. Remedy: For alarm value = 3:
|
| A32422 (F, N) Encoder 2: Pulses per revolution square-wave encoder outside tolerance bandwidth | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. This alarm is triggered with active square-wave encoder PPR correction and re-parameterized fault 31131 if the accumulator contains larger values than p4683 or p4684. The zero mark distance for zero mark monitoring is set in p0425 (rotary encoder). Alarm value (r2124, interpret decimal): accumulated differential pulses in encoder pulses. Remedy:
|
| A32429 (F, N) Encoder 2: Position difference hall sensor/track C/D and A/B too large | Cause: The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° electrical or the error for the Hall signals is greater than +/-60 ° electrical. One period of track C/D corresponds to 360 ° mechanical. One period of the Hall signal corresponds to 360 ° electrical. The monitoring responds if, for example, Hall sensors are connected as equivalent for the C/D tracks with the incorrect rotational sense or supply values that are not accurate enough. Alarm value (r2124, interpret decimal): For track C/D, the following applies: Measured deviation as mechanical angle (16 bits with sign, 182 dec corresponds to 1 °). For Hall signals, the following applies: Measured deviation as electrical angle (16 bits with sign, 182 dec corresponds to 1 °). Remedy:
|
| A32431 (F, N) Encoder 2: Position deviation incremental/absolute too high (alarm) | Cause: When the zero pulse is passed, a deviation in the incremental position was detected. For equidistant zero marks, the following applies: – the first zero mark passed supplies the reference point for all subsequent checks. The other zero marks must have n times the distance referred to the first zero mark. For distance-coded zero marks, the following applies: – the first zero mark pair supplies the reference point for all subsequent checks. The other zero mark pairs must have the expected distance to the first zero mark pair. Alarm value (r2124, interpret decimal): Deviation in quadrants (1 pulse = 4 quadrants). Remedy:
|
| A32432 (F, N) Encoder 2: Rotor position adaptation corrects deviation | Cause: On track A/B, pulses have been lost or too many have been counted. These pulses are presently being corrected. Alarm value (r2124, interpret decimal): Last measured deviation of zero mark in increments (4 increments = 1 encoder pulse). The sign designates the direction of motion when detecting the zero mark distance. Remedy:
|
| A32442 (F, N) Encoder 2: Battery voltage alarm threshold reached | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The multiturn information can no longer be buffered if the battery voltage drops even further. Remedy:
|
| A32443 (F, N) Encoder 2: Signal level track C/D outside tolerance (alarm) | Cause: The unipolar level (CP/CN or DP/DN) for encoder 2 is outside the permissible tolerance. Alarm value (r2124, interpret binary): Bit 0 = 1: Either CP or CN outside the tolerance. Bit 16 = 1: Either DP or DN outside the tolerance. The unipolar nominal signal level of the encoder must lie in the range 2500 mV +/- 500 mV. The response thresholds are < 1700 mV and > 3300 mV. Note: The signal level is not evaluated unless the following conditions are satisfied: – Sensor Module properties available (r0459.31 = 1). – monitoring active (p0437.31 = 1). Remedy:
|
| A32460 (N) Encoder 2: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Alarm value (r2124, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside measuring range set in p4673. 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy:
|
| A32461 (N) Encoder 2: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Alarm value (r2124, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside the selected measuring range (p4675). 3: The absolute value of the input voltage has exceeded the range limit (p4676). Remedy:
|
| A32462 (N) Encoder 2: Analog sensor no channel active | Cause: Channel A and B are not activated for the analog sensor. Remedy:
|
| A32463 (N) Encoder 2: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Alarm value (r2124, interpret decimal): 1: Position value from the LVDT sensor. 2: Position value from the encoder characteristic. Remedy:
|
| A32470 (F, N) Encoder 2: Encoder signals an internal error (X521.7) | Cause: For the Sensor Module Cabinet 30 (SMC30), a dirty encoder is signaled via a 0 signal at terminal X521.7. Remedy:
|
| F32500 (N, A) Encoder 2: Position tracking traversing range exceeded | Cause: For a configured linear axis without modulo correction, the drive/encoder has exceeded the maximum possible traversing range. The value should be read in p0412 and interpreted as the number of motor revolutions. For p0411.0 = 1, the maximum traversing range for the configured linear axis is defined to be 64x (+/- 32x) of p0421. For p0411.3 = 1, the maximum traversing range for the configured linear axis is preset (default value) to the highest possible value and is +/-p0412/2 (rounded off to complete revolutions). The highest possible value depends on the pulse number (p0408) and the fine resolution (p0419). Remedy: The fault should be resolved as follows:
The fault should then be acknowledged and the absolute encoder adjusted. |
| F32501 (N, A) Encoder 2: Position tracking encoder position outside tolerance window | Cause: When switched off, the drive/encoder was moved through a distance greater than was parameterized in the tolerance window. It is possible that there is no longer any reference between the mechanical system and encoder. Fault value (r0949, interpret decimal): Deviation (difference) to the last encoder position in increments of the absolute value. The sign designates the traversing direction. Note: The deviation (difference) found is also displayed in r0477. See also: p0413 (Measuring gear position tracking tolerance window), r0477 (Measuring gear position difference) Remedy: Reset the position tracking as follows:
The fault should then be acknowledged and, if necessary, the absolute encoder adjusted (p2507). See also: p0010 |
| F32502 (N, A) Encoder 2: Encoder with measuring gear without valid signals | Cause: The encoder with measuring gear no longer provides any valid signals. Remedy:
|
| F32503 (N, A) Encoder 2: Position tracking cannot be reset | Cause: The position tracking for the measuring gear cannot be reset. Remedy: The fault should be resolved as follows:
The fault should then be acknowledged and the absolute encoder adjusted. |
| A32700 Encoder 2: Effectivity test does not supply the expected value | Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Alarm value (r2124, interpret binary): Bit x = 1: Effectivity test x unsuccessful. Remedy:
|
| N32800 (F) Encoder 2: Group signal | Cause: The motor encoder has detected at least one fault. Remedy:
|
| F32801 (N, A) Encoder 2 DRIVE-CLiQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Fault cause 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| F32802 (N, A) Encoder 2: Time slice overflow | Cause: A time slice overflow has occurred in encoder 2. Fault value (r0949, interpret hexadecimal): yx hex: y = function involved (Siemens-internal fault diagnostics), x = time slice involved x = 9: Time slice overflow of the fast (current controller clock cycle) time slice. x = A: Time slice overflow of the average time slice. x = C: Time slice overflow of the slow time slice. yx = 3E7: Timeout when waiting for SYNO (e.g. unexpected return to non-cyclic operation). Remedy:
Note: For a current controller sampling time = 31.25 µs, use an SMx20 with Article No. 6SL3055-0AA00-5xA3. |
| F32804 (N, A) Encoder 2: Sensor Module checksum error | Cause: A checksum error has occurred when reading-out the program memory on the Sensor Module. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex yyyy: Memory area involved. xxxx: Difference between the checksum at POWER ON and the actual checksum. Remedy:
|
| F32805 (N, A) Encoder 2: EEPROM checksum error | Cause: Data in the EEPROM corrupted. Fault value (r0949, interpret hexadecimal): 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy:
|
| F32806 (N, A) Encoder 2: Initialization error | Cause: The encoder was not successfully initialized. Fault value (r0949, interpret hexadecimal): Bit 0, 1: Encoder initialization with the motor rotating has failed (deviation involving coarse and fine position in encoder pulses/4). Bit 2: Mid-voltage matching for track A unsuccessful. Bit 3: Mid-voltage matching for track B unsuccessful. Bit 4: Mid-voltage matching for acceleration input unsuccessful. Bit 5: Mid-voltage matching for track safety A unsuccessful. Bit 6: Mid-voltage matching for track safety B unsuccessful. Bit 7: Mid-voltage matching for track C unsuccessful. Bit 8: Mid-voltage matching for track D unsuccessful. Bit 9: Mid-voltage matching for track R unsuccessful. Bit 10: The difference in mid-voltages between A and B is too great (> 0.5 V) Bit 11: The difference in mid-voltages between C and D is too great (> 0.5 V) Bit 12: The difference in mid-voltages between safety A and safety B is too great (> 0.5 V) Bit 13: The difference in mid-voltages between A and safety B is too great (> 0.5 V) Bit 14: The difference in mid-voltages between B and safety A is too great (> 0.5 V) Bit 15: The standard deviation of the calculated mid-voltages is too great (> 0.3 V) Bit 16: Internal fault – fault when reading a register (CAFE) Bit 17: Internal fault – fault when writing a register (CAFE) Bit 18: Internal fault: No mid-voltage matching available Bit 19: Internal error – ADC access error. Bit 20: Internal error – no zero crossover found. Bit 28: Error while initializing the EnDat 2.2 measuring unit. Bit 29: Error when reading out the data from the EnDat 2.2 measuring unit. Bit 30: EEPROM checksum of the EnDat 2.2 measuring unit incorrect. Bit 31: Data of the EnDat 2.2 measuring unit inconsistent. Note: Bit 0, 1: Up to 6SL3055-0AA00-5*A0 Bits 2 … 20: 6SL3055-0AA00-5*A1 and higher Remedy: Acknowledge fault. If the fault cannot be acknowledged:
|
| A32811 (F, N) Encoder 2: Encoder serial number changed | Cause: The encoder serial number has changed. The change is only checked for encoders with serial number (e.g. EnDat encoders). – the encoder was replaced. Note: With closed-loop position control, the serial number is accepted when starting the adjustment (p2507 = 2). When the encoder is adjusted (p2507 = 3), the serial number is checked for changes and if required, the adjustment is reset (p2507 = 1). Proceed as follows to hide serial number monitoring: – set the following serial numbers for the corresponding Encoder Data Set: p0441= FF, p0442 = 0, p0443 = 0, p0444 = 0, p0445 = 0. Remedy:
|
| F32812 (N, A) Encoder 2: Requested cycle or RX-/TX timing not supported | Cause: A cycle requested from the Control Unit or RX/TX timing is not supported. Fault value (r0949, interpret decimal): 0: Application cycle is not supported. 1: DRIVE-CLiQ cycle is not supported. 2: Distance between RX and TX instants in time too low. 3: TX instant in time too early. Remedy:
|
| F32813 Encoder 2: Hardware logic unit failed | Cause: The logic unit of the DRIVE-CLiQ encoder has failed. Fault value (r0949, interpret binary): Bit 0: ALU watchdog has responded. Bit 1: ALU has detected a sign-of-life error. Remedy:
|
| F32820 (N, A) Encoder 2 DRIVE-CLiQ: Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. Fault cause: 1 (= 01 hex): Checksum error (CRC error). 2 (= 02 hex): Telegram is shorter than specified in the length byte or in the receive list. 3 (= 03 hex): Telegram is longer than specified in the length byte or in the receive list. 4 (= 04 hex): The length of the receive telegram does not match the receive list. 5 (= 05 hex): The type of the receive telegram does not match the receive list. 6 (= 06 hex): The address of the component in the telegram and in the receive list do not match. 7 (= 07 hex): A SYNC telegram is expected – but the received telegram is not a SYNC telegram. 8 (= 08 hex): No SYNC telegram is expected – but the received telegram is one. 9 (= 09 hex): The error bit in the receive telegram is set. 16 (= 10 hex): The receive telegram is too early. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| F32835 (N, A) Encoder 2 DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. The nodes do not send and receive in synchronism. Fault cause: 33 (= 21 hex): The cyclic telegram has not been received. 34 (= 22 hex): Timeout in the telegram receive list. 64 (= 40 hex): Timeout in the telegram send list. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| F32836 (N, A) Encoder 2 DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| F32837 (N, A) Encoder 2 DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. Fault cause: 32 (= 20 hex): Error in the telegram header. 35 (= 23 hex): Receive error: The telegram buffer memory contains an error. 66 (= 42 hex): Send error: The telegram buffer memory contains an error. 67 (= 43 hex): Send error: The telegram buffer memory contains an error. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| F32845 (N, A) Encoder 2 DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Fault cause 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| F32850 (N, A) Encoder 2: Encoder evaluation internal software error | Cause: An internal software error has occurred in the Sensor Module of encoder 2. Fault value (r0949, interpret decimal): 1: Background time slice is blocked. 2: Checksum over the code memory is not OK. 10000: OEM memory of the EnDat encoder contains data that cannot be interpreted. 11000 … 11499: Descriptive data from EEPROM incorrect. 11500 … 11899: Calibration data from EEPROM incorrect. 11900 … 11999: Configuration data from EEPROM incorrect. 12000 … 12008: communication with analog/digital converter faulted. 16000: DRIVE-CLiQ encoder initialization application error. 16001: DRIVE-CLiQ encoder initialization ALU error. 16002: DRIVE-CLiQ encoder HISI / SISI initialization error. 16003: DRIVE-CLiQ encoder safety initialization error. 16004: DRIVE-CLiQ encoder internal system error. Remedy:
|
| F32851 (N, A) Encoder 2 DRIVE-CLiQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit. Fault cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Fault value (r0949/r2124): 0000yyxx hex (yy = component number, xx = error cause). Remedy:
|
| F32860 (N, A) Encoder 2 DRIVE-CLiQ (CU): Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. Fault causes include: 1: Checksum error (CRC error). 2-4: Telegram length errors. 5: Telegram type mismatch. 6: Address mismatch. 9: Supply voltage failed signals. 16-25: Timing and Receive errors (too early, etc). Remedy:
|
| F32875 (N, A) Encoder 2: power supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage has failed. Fault cause: 9 (= 09 hex): The power supply voltage for the components has failed. Remedy:
|
| F32885 (N, A) Encoder 2 DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred. The nodes do not send and receive in synchronism. Fault causes: 26: Sign-of-life bit not set and telegram too early. 33: Cyclic telegram not received. 34, 64: Timeout in telegram lists. 98: Error at transition to cyclic operation. Remedy:
|
| F32886 (N, A) Encoder 2 DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy:
|
| F32887 (N, A) Encoder 2 DRIVE-CLiQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLiQ component involved (Sensor Module for encoder 2). Faulty hardware cannot be excluded. Fault causes include: 32: Error in telegram header. 35, 66, 67: Buffer memory errors. 96: Response received too late. 97: Time taken to exchange characteristic data too long. Remedy:
|
| F32895 (N, A) Encoder 2 DRIVE-CLiQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred. Fault cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy:
|
| F32896 (N, A) Encoder 2 DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component have changed in an incompatible fashion with respect to the properties when booted (e.g., cable or component replaced). Remedy:
|
| F32899 (N, A) Encoder 2: Unknown fault | Cause: A fault occurred on the Sensor Module that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on the component is more recent than on the Control Unit. Remedy:
|
| A32902 (F, N) Encoder 2: SPI-BUS error occurred | Cause: Error when operating the internal SPI bus. Remedy:
|
| A32903 (F, N) Encoder 2: I2C-BUS error occurred | Cause: Error when operating the internal I2C bus. Remedy:
|
| F32905 (N, A) Encoder 2: Encoder parameterization error | Cause: An error was identified in the encoder parameterization. The parameterized encoder type may not match the connected encoder. Fault value (r0949) indicates the parameter error (e.g., EnDat/SSI protocol bits, HTL level support, etc.). Remedy:
|
| F32912 Encoder 2: Device combination is not permissible | Cause: The selected device combination is not supported. 1003, 1005: Measuring unit not supported by EnDat 2.2 converter. 1006: Max duration of EnDat transfer exceeded. 2001: Cycle combination not supported. 2002: Resolution mismatch. Remedy:
|
| A32915 (F, N) Encoder 2: Encoder configuration error | Cause: The configuration for encoder 2 is incorrect. 1: Re-parameterization between fault/alarm is not permissible. 419: Fine resolution Gx_XIST2 issue (max absolute position > 32 bits). Remedy:
|
| F32916 (N, A) Encoder 2: Encoder parameterization error | Cause: An encoder parameter was detected as being incorrect. Parameterized type may not match connected encoder. Remedy:
|
| A32920 (F, N) Encoder 2: Temperature sensor fault (motor) | Cause: The motor detected a fault when evaluating the temperature sensor. 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A32930 (N) Encoder 2: Data logger has saved data | Cause: For the activated function “Data logger”, a fault occurred. Diagnostics data was saved to the memory card (/USER/SINAMICS/DATA/SMTRC00.BIN…). Remedy:
|
| A32940 (F, N) Encoder 2: Spindle sensor S1 voltage incorrect | Cause: The voltage of analog sensor S1 is outside the permissible range. Remedy:
|
| F32950 Encoder 2: Internal software error | Cause: An internal software error has occurred. Remedy:
|
| A32999 (F, N) Encoder 2: Unknown alarm | Cause: An alarm occurred on the Sensor Module that cannot be interpreted by the Control Unit firmware (firmware version mismatch). Remedy:
|
| F33125 (N, A) Encoder 3: Signal level track A or B too high | Cause: The signal level (root from A^2 + B^2) of the encoder exceeds the permissible limit value. Remedy:
|
| F33126 (N, A) Encoder 3: Signal level track A or B too high | Cause: The signal level (|A| + |B|) of the encoder exceeds the permissible limit value. Remedy:
|
| F33142 (N, A) Encoder 3: Battery voltage fault | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The battery voltage is no longer sufficient. Remedy:
|
| F33152 (N, A) Encoder 3: Max. signal frequency (track A/B) exceeded | Cause: The maximum signal frequency of the encoder evaluation has been exceeded. Remedy:
|
| A33442 (F, N) Encoder 3: Battery voltage alarm threshold reached | Cause: The encoder battery voltage has dropped; multiturn information can no longer be buffered if it drops further. Remedy:
|
| A33700 Encoder 3: Effectivity test does not supply the expected value | Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Remedy:
|
| F33875 (N, A) Encoder 3: power supply voltage failed | Cause: The DRIVE-CLiQ communication signals that the supply voltage has failed. Fault cause: 9 (= 09 hex). Remedy:
|
| F33912 Encoder 3: Device combination is not permissible | Cause: The selected device combination is not supported. 1003, 1005: Measuring unit not supported by EnDat 2.2 converter. 1006: Max duration of EnDat transfer exceeded. 2001: Cycle combination not supported. 2002: Resolution mismatch. Remedy:
|
| F34851 VSM DRIVE-CLiQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module (VSM). Sign-of-life bit not set. Remedy:
|
| F34860 VSM DRIVE-CLiQ (CU): Telegram error | Cause: A DRIVE-CLiQ communications error has occurred from the VSM. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy:
|
| F34875 VSM: power supply voltage failed | Cause: The DRIVE-CLiQ communication from the VSM signals that the supply voltage has failed. Remedy:
|
| F34885 VSM DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred. 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. Data were not able to be sent. Remedy:
|
| F34887 VSM DRIVE-CLiQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLiQ component (VSM) involved. Faulty hardware cannot be excluded. Remedy:
|
| F34895 VSM DRIVE-CLiQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred (Synchronization error). Remedy:
|
| F34896 VSM DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the VSM have changed in an incompatible fashion (e.g., cable or component replaced). Remedy:
|
| A35200 (F, N) TM: Calibration data | Cause: An error was detected in the calibration data of the Terminal Module. Remedy:
|
| F35207 (N, A) TM: Temperature fault/alarm threshold channel 0 exceeded | Cause: Temperature evaluation fault via Terminal Module (TM). Alarm or fault threshold exceeded for channel 0. Remedy:
|
| F35208 (N, A) TM: Temperature fault/alarm threshold channel 1 exceeded | Cause: Temperature evaluation fault via Terminal Module (TM). Alarm or fault threshold exceeded for channel 1. Remedy:
|
| F35209 (N, A) TM: Temperature fault/alarm threshold channel 2 exceeded | Cause: Temperature evaluation fault via Terminal Module (TM). Alarm or fault threshold exceeded for channel 2. Remedy:
|
| F35210 (N, A) TM: Temperature fault/alarm threshold channel 3 exceeded | Cause: Temperature evaluation fault via Terminal Module (TM). Alarm or fault threshold exceeded for channel 3. Remedy:
|
| A35211 (F, N) TM: Temperature alarm threshold channel 0 exceeded | Cause: The temperature measured using the temperature sensing of the Terminal Module (TM) (r4105[0]) has exceeded the threshold value to initiate this alarm (p4102[0]). Note: For sensor type “PTC thermistor” and “Bimetallic NC contact” (p4100[0] = 1, 4): – if r4101[0] > 1650 ohms, temperature = 250 °C – if r4101[0] <= 1650 ohms, temperature = -50 °C Alarm value (r2124): Temperature actual value [0.1 °C]. Remedy:
|
| A35212 (F, N) TM: Temperature alarm threshold channel 1 exceeded | Cause: The temperature measured using the temperature sensing of the Terminal Module (TM) (r4105[1]) has exceeded the threshold value to initiate this alarm (p4102[2]). Remedy:
|
| A35213 (F, N) TM: Temperature alarm threshold channel 2 exceeded | Cause: The temperature measured using the temperature sensing of the Terminal Module (TM) (r4105[2]) has exceeded the threshold value to initiate this alarm (p4102[4]). Remedy:
|
| A35214 (F, N) TM: Temperature alarm threshold channel 3 exceeded | Cause: The temperature measured using the temperature sensing of the Terminal Module (TM) (r4105[3]) has exceeded the threshold value to initiate this alarm (p4102[6]). Remedy:
|
| F35220 (N, A) TM: Frequency limit reached for signal output | Cause: The signals output from the Terminal Module 41 (TM41) for tracks A/B have reached the limit frequency. The output signals are no longer in synchronism with the specified setpoint. SIMOTION (p4400 = 0) operating mode: – if TM41 configured as technology project, fault output in response to short-circuited A/B signals in X520. SINAMICS (p4400 = 1) operating mode: – fine resolution of TM41 in p0418 does not match connector input. – encoder position actual value r0479 has excessively high actual speed. – output signals correspond to a speed greater than maximum speed (r1082). Remedy:
|
| F35221 (N, A) TM: Setpoint – actual value deviation outside the tolerance range | Cause: The deviation between the setpoint and the output signals (track A/B) exceeds the tolerance of +/-3 %. The deviation between the internal and external measured value is too high (> 1000 pulses). Remedy:
|
| A35222 (F, N) TM: Encoder pulse number not permissible | Cause: The encoder pulse number entered does not match the permissible pulse number from a hardware perspective. Alarm value (r2124): 1: Encoder pulse number is too high. 2: Encoder pulse number is too low. 4: Encoder pulse number is less than the zero mark offset (p4426). Remedy:
|
| A35223 (F, N) TM: Zero mark offset not permissible | Cause: The entered zero mark offset is not permissible. Alarm value (r2124): 1: Zero mark offset is too high. Remedy:
|
| F35230 TM: Hardware fault | Cause: The Terminal Module (TM) used has signaled internal errors. Signals from this module may not be evaluated because they are very likely to be incorrect. Remedy:
|
| F35233 DRIVE-CLiQ component function not supported | Cause: A function requested by the Control Unit is not supported by a DRIVE-CLiQ component. Fault value (r0949): 1: TM31 does not support “Timer for temperature evaluation”. 4: Improved actual value resolution not supported. 5: Improved setpoint resolution not supported. 6: Residual value handling in setpoint channel cannot be deactivated. 7: Output frequencies > 750 kHz cannot be activated. Remedy:
|
| F35400 (N, A) TM: Temperature fault/alarm threshold channel 4 exceeded | Cause: For the temperature evaluation via TM150, conditions to initiate this fault fulfilled: – alarm threshold exceeded longer than set in timer. – fault threshold exceeded. Fault value (r0949): Temperature actual value [0.1 °C]. Remedy:
|
| F35401 (N, A) TM: Temperature fault/alarm threshold channel 5 exceeded | Cause: Similar to F35400 but for channel 5. – alarm threshold exceeded (p4102[10]). – fault threshold exceeded (p4102[11]). Remedy:
|
| F35402 (N, A) TM: Temperature fault/alarm threshold channel 6 exceeded | Cause: Similar to F35400 but for channel 6. Remedy:
|
| F35403 (N, A) TM: Temperature fault/alarm threshold channel 7 exceeded | Cause: Similar to F35400 but for channel 7. Remedy:
|
| F35404 (N, A) TM: Temperature fault/alarm threshold channel 8 exceeded | Cause: Similar to F35400 but for channel 8. Remedy:
|
| F35405 (N, A) TM: Temperature fault/alarm threshold channel 9 exceeded | Cause: Similar to F35400 but for channel 9. Remedy:
|
| F35406 (N, A) TM: Temperature fault/alarm threshold channel 10 exceeded | Cause: Similar to F35400 but for channel 10. Remedy:
|
| F35407 (N, A) TM: Temperature fault/alarm threshold channel 11 exceeded | Cause: Similar to F35400 but for channel 11. Remedy:
|
| A35410 (F, N) TM: Temperature alarm threshold channel 4 exceeded | Cause: The temperature (r4105[4]) measured via TM150 has exceeded the threshold value to initiate this alarm (p4102[8]). Remedy:
|
| A35411 (F, N) TM: Temperature alarm threshold channel 5 exceeded | Cause: The temperature (r4105[5]) measured via TM150 has exceeded the threshold value to initiate this alarm (p4102[10]). Remedy:
|
| A35412 (F, N) TM: Temperature alarm threshold channel 6 exceeded | Cause: The temperature (r4105[6]) measured via TM150 has exceeded the threshold value to initiate this alarm (p4102[12]). Remedy:
|
| A35413 (F, N) TM: Temperature alarm threshold channel 7 exceeded | Cause: The temperature (r4105[7]) measured via TM150 has exceeded the threshold value to initiate this alarm (p4102[14]). Remedy:
|
| A35414 (F, N) TM: Temperature alarm threshold channel 8 exceeded | Cause: The temperature (r4105[8]) measured via TM150 has exceeded the threshold value to initiate this alarm (p4102[16]). Remedy:
|
| A35415 (F, N) TM: Temperature alarm threshold channel 9 exceeded | Cause: The temperature (r4105[9]) measured via TM150 has exceeded the threshold value to initiate this alarm (p4102[18]). Remedy:
|
| A35416 (F, N) TM: Temperature alarm threshold channel 10 exceeded | Cause: The temperature (r4105[10]) measured via TM150 has exceeded the threshold value to initiate this alarm (p4102[20]). Remedy:
|
| A35417 (F, N) TM: Temperature alarm threshold channel 11 exceeded | Cause: The temperature (r4105[11]) measured via TM150 has exceeded the threshold value to initiate this alarm (p4102[22]). Remedy:
|
| N35800 (F) TM: Group signal | Cause: The Terminal Module has detected at least one fault. Remedy:
|
| F35801 (N, A) TM DRIVE-CLiQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred between the Control Unit and the Terminal Module involved. 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
|
| A35802 (F, N) TM: Time slice overflow | Cause: A time slice overflow has occurred on the Terminal Module. Remedy:
|
| A35803 (F, N) TM: Memory test | Cause: An error has occurred during the memory test on the Terminal Module. Remedy:
|
| F35804 (N, A) TM: CRC | Cause: A checksum error has occurred when reading-out the program memory on the Terminal Module. Remedy:
|
| F35805 (N, A) TM: EEPROM checksum error | Cause: Internal parameter data is corrupted. 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy:
|
| A35807 (F, N) TM: Sequence control time monitoring | Cause: Error, timeout, sequence control on the Terminal Module. Remedy:
|
| F35820 TM DRIVE-CLiQ: Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the Terminal Module involved. Fault cause: 1: CRC error. 2: Telegram shorter than specified. 3: Telegram longer than specified. 4: Length does not match receive list. 5: Type does not match receive list. 6: Address does not match receive list. 7: SYNC telegram expected but not received. 8: No SYNC telegram expected. 9: Error bit set. 16: Receive telegram too early. Remedy:
|
| F35835 TM DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the Terminal Module involved. The nodes do not send and receive in synchronism. Fault cause: 33: Cyclic telegram not received. 34: Timeout in telegram receive list. 64: Timeout in telegram send list. Remedy:
|
| F35836 TM DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred between the Control Unit and the Terminal Module involved. Data were not able to be sent. 65: Telegram type does not match send list. Remedy:
|
| F35837 PTM DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. 32: Error in telegram header. 35: Receive error (telegram buffer). 66: Send error (telegram buffer). 67: Send error (telegram buffer). Remedy:
|
| F35845 TM DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred between the Control Unit and the Terminal Module involved. 11: Synchronization error during alternating cyclic data transfer. Remedy:
|
| F35850 TM: Internal software error | Cause: An internal software error in the Terminal Module (TM) has occurred. 1: Background time slice is blocked. 2: Checksum over the code memory is not OK. Remedy:
|
| F35851 TM DRIVE-CLiQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit. 10: The sign-of-life bit in the receive telegram is not set. Remedy:
|
| 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. 1: CRC error. 2, 3: Telegram length issues. 4, 5, 6: Mismatches in receive list (length, type, address). 9: Supply voltage failed. 16-22, 25: Timing and header errors (receive telegram too early, etc.). Remedy:
|
| F35875 TM: power supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage has failed (Cause 9). 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. 26: Sign-of-life bit not set and telegram too early. 33: Cyclic telegram not received. 34, 64: Timeouts. 98: Error at transition to cyclic operation. 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. 65: Telegram type does not match send list. Remedy:
|
| F35887 TM DRIVE-CLiQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLiQ component (Terminal Module) involved. Faulty hardware cannot be excluded. Fault cause: 32 (= 20 hex): Error in the telegram header. 35 (= 23 hex): Receive error: The telegram buffer memory contains an error. 66 (= 42 hex): Send error: The telegram buffer memory contains an error. 67 (= 43 hex): Send error: The telegram buffer memory contains an error. 96 (= 60 hex): Response received too late during runtime measurement. 97 (= 61 hex): Time taken to exchange characteristic data too long. Remedy:
|
| F35895 TM DRIVE-CLiQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit. Fault cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. 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:
|
| F35899 (N, A) TM: Unknown fault | Cause: A fault has occurred on the Terminal Module that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Remedy:
|
| A35903 (F, N) TM: I2C bus error occurred | Cause: An error has occurred while accessing the internal I2C bus of the Terminal Module. Remedy:
|
| A35904 (F, N) TM: EEPROM | Cause: An error has occurred accessing the non-volatile memory on the Terminal Module. Remedy:
|
| A35905 (F, N) TM: Parameter access | Cause: The Control Unit attempted to write an illegal parameter value to the Terminal Module. Remedy:
|
| A35906 (F, N) TM: 24 V power supply missing | Cause: The 24 V power supply for the digital outputs is missing. Alarm value (r2124, interpret hexadecimal): 01: TM17 24 V power supply for DI/DO 0 … 7 missing. 02: TM17 24 V power supply for DI/DO 8 … 15 missing. 04: TM15 24 V power supply for DI/DO 0 … 7 (X520) missing. 08: TM15 24 V power supply for DI/DO 8 … 15 (X521) missing. 10: TM15 24 V power supply for DI/DO 16 … 23 (X522) missing. 20: TM41 24 V power supply for DI/DO 0 … 3 missing. Remedy:
|
| A35907 (F, N) TM: Hardware initialization error | Cause: The Terminal Module was not successfully initialized. Alarm value (r2124, interpret hexadecimal): 01: TM17 or TM41 – incorrect configuration request. 02: TM17 or TM41 – programming not successful. 04: TM17 or TM41 – invalid time stamp. Remedy:
|
| A35910 (F, N) TM: Module overtemperature | Cause: The temperature in the module has exceeded the highest permissible limit. Remedy:
|
| A35911 (F, N) TM: Clock synchronous operation sign-of-life missing | Cause: The maximum permissible number of errors in the master sign-of-life (clock synchronous operation) has been exceeded in cyclic operation. When the alarm is output, the module outputs are reset up to the next synchronization. Remedy:
|
| A35920 (F, N) TM: Error temperature sensor channel 0 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A35921 (F, N) TM: Error temperature sensor channel 1 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A35922 (F, N) TM: Error temperature sensor channel 2 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A35923 (F, N) TM: Error temperature sensor channel 3 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A35924 (F, N) TM: Error temperature sensor channel 4 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A35925 (F, N) TM: Error temperature sensor channel 5 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A35926 (F, N) TM: Error temperature sensor channel 6 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A35927 (F, N) TM: Error temperature sensor channel 7 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A35928 (F, N) TM: Error temperature sensor channel 8 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A35929 (F, N) TM: Error temperature sensor channel 9 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A35930 (F, N) TM: Error temperature sensor channel 10 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A35931 (F, N) TM: Error temperature sensor channel 11 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. 2: Measured resistance too low. Remedy:
|
| A35999 (F, N) TM: Unknown alarm | Cause: An alarm has occurred on the Terminal Module that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. 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. Fault 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. Fault cause (interpret hex): 1: Checksum error (CRC error). 2: Telegram shorter than specified in length byte/receive list. 3: Telegram longer than specified in length byte/receive list. 4: Length of receive telegram does not match receive list. 5: Type of receive telegram does not match receive list. 6: Address of power unit in telegram and receive list do not match. 9: DRIVE-CLiQ signals that supply voltage has failed. 16: Receive telegram too early. 17: CRC error and receive telegram too early. 18: Telegram shorter than specified and too early. 19: Telegram longer than specified and too early. 20: Length does not match and too early. 21: Type does not match and too early. 22: Address of power unit does not match and too early. 25: Error bit in receive telegram set and too early. Remedy:
|
| F36875 HUB: power supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage has failed. Fault cause: 9 (= 09 hex): The power supply voltage for the components has failed. Remedy:
|
| F36885 Hub DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: DRIVE-CLiQ communication error from DRIVE-CLiQ Hub Module in question to the Control Unit. The nodes do not send and receive in synchronism. Fault cause: 26 (= 1A hex): Sign-of-life bit in the receive telegram not set and the receive telegram is too early. 33 (= 21 hex): The cyclic telegram has not been received. 34 (= 22 hex): Timeout in the telegram receive list. 64 (= 40 hex): Timeout in the telegram send list. 98 (= 62 hex): Error at the transition to cyclic operation. 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. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy:
|
| F36887 Hub DRIVE-CLiQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLiQ component (DRIVE-CLiQ Hub Module) involved. Faulty hardware cannot be excluded. Fault cause: 32 (= 20 hex): Error in the telegram header. 35 (= 23 hex): Receive error: The telegram buffer memory contains an error. 66 (= 42 hex): Send error: The telegram buffer memory contains an error. 67 (= 43 hex): Send error: The telegram buffer memory contains an error. 96 (= 60 hex): Response received too late during runtime measurement. 97 (= 61 hex): Time taken to exchange characteristic data too long. 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. Fault 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. One cause can be, e.g. that a DRIVE-CLiQ cable or DRIVE-CLiQ component has been replaced. Remedy:
|
| F40000 Fault at DRIVE-CLiQ socket X100 | Cause: A fault has occurred at the drive object at the DRIVE-CLiQ socket X100. Fault value (r0949, interpret decimal): First fault that has occurred for this drive object. Remedy:
|
| F40001 Fault at DRIVE-CLiQ socket X101 | Cause: A fault has occurred at the drive object at the DRIVE-CLiQ socket X101. Fault value (r0949, interpret decimal): First fault that has occurred for this drive object. Remedy:
|
| F40002 Fault at DRIVE-CLiQ socket X102 | Cause: A fault has occurred at the drive object at the DRIVE-CLiQ socket X102. Fault value (r0949, interpret decimal): First fault that has occurred for this drive object. Remedy:
|
| F40003 Fault at DRIVE-CLiQ socket X103 | Cause: A fault has occurred at the drive object at the DRIVE-CLiQ socket X103. Fault value (r0949, interpret decimal): First fault that has occurred for this drive object. Remedy:
|
| F40004 Fault at DRIVE-CLiQ socket X104 | Cause: A fault has occurred at the drive object at the DRIVE-CLiQ socket X104. Fault value (r0949, interpret decimal): First fault that has occurred for this drive object. Remedy:
|
| F40005 Fault at DRIVE-CLiQ socket X105 | Cause: A fault has occurred at the drive object at the DRIVE-CLiQ socket X105. Fault value (r0949, interpret decimal): First fault that has occurred for this drive object. Remedy:
|
| A40100 Alarm at DRIVE-CLiQ socket X100 | Cause: An alarm has occurred at the drive object at the DRIVE-CLiQ socket X100. Alarm value (r2124, interpret decimal): First alarm that has occurred for this drive object. Remedy:
|
| A40101 Alarm at DRIVE-CLiQ socket X101 | Cause: An alarm has occurred at the drive object at the DRIVE-CLiQ socket X101. Alarm value (r2124, interpret decimal): First alarm that has occurred for this drive object. Remedy:
|
| A40102 Alarm at DRIVE-CLiQ socket X102 | Cause: An alarm has occurred at the drive object at the DRIVE-CLiQ socket X102. Alarm value (r2124, interpret decimal): First alarm that has occurred for this drive object. Remedy:
|
| A40103 Alarm at DRIVE-CLiQ socket X103 | Cause: An alarm has occurred at the drive object at the DRIVE-CLiQ socket X103. Alarm value (r2124, interpret decimal): First alarm that has occurred for this drive object. Remedy:
|
| A40104 Alarm at DRIVE-CLiQ socket X104 | Cause: An alarm has occurred at the drive object at the DRIVE-CLiQ socket X104. Alarm value (r2124, interpret decimal): First alarm that has occurred for this drive object. Remedy:
|
| A40105 Alarm at DRIVE-CLiQ socket X105 | Cause: An alarm has occurred at the drive object at the DRIVE-CLiQ socket X105. Alarm value (r2124, interpret decimal): First alarm that has occurred for this drive object. Remedy:
|
| F40799 CX32: Configured transfer end time exceeded | Cause: The configured transfer end time when transferring the cyclic actual values was exceeded. Remedy:
|
| F40801 CX32 DRIVE-CLiQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the controller extension involved. Fault cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
|
| F40820 CX32 DRIVE-CLiQ: Telegram error | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the controller extension involved. Fault cause (interpret hex): 1: Checksum error (CRC error). 2: Telegram shorter than specified. 3: Telegram longer than specified. 4: Length of receive telegram does not match receive list. 5: Type of receive telegram does not match receive list. 6: Address of component in telegram and receive list do not match. 7: SYNC telegram expected but not received. 8: No SYNC telegram expected but received. 9: Error bit in receive telegram set. 16: Receive telegram too early. Remedy:
|
| F40825 CX32 DRIVE-CLiQ: Supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage has failed. Fault cause: 9 (= 09 hex): The power supply voltage for the components has failed. Remedy:
|
| F40835 CX32 DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the controller extension involved. The nodes do not send and receive in synchronism. Fault cause: 33 (= 21 hex): The cyclic telegram has not been received. 34 (= 22 hex): Timeout in the telegram receive list. 64 (= 40 hex): Timeout in the telegram send list. Remedy:
|
| F40836 CX32 DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the controller extension involved. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy:
|
| F40837 CX32 DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. Fault cause: 32 (= 20 hex): Error in the telegram header. 35 (= 23 hex): Receive error: The telegram buffer memory contains an error. 66 (= 42 hex): Send error: The telegram buffer memory contains an error. 67 (= 43 hex): Send error: The telegram buffer memory contains an error. Remedy:
|
| F40845 CX32 DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the controller extension involved. Fault cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| F40851 CX32 DRIVE-CLiQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communications error has occurred from the controller extension involved to the Control Unit. The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit. Fault cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| F40860 CX32 DRIVE-CLiQ (CU): Telegram error | Cause: A DRIVE-CLiQ communications error has occurred from the controller extension involved to the Control Unit. Fault cause: 1 (= 01 hex): Checksum error (CRC error). 2 (= 02 hex): Telegram is shorter than specified in the length byte or in the receive list. 3 (= 03 hex): Telegram is longer than specified in the length byte or in the receive list. 4 (= 04 hex): The length of the receive telegram does not match the receive list. 5 (= 05 hex): The type of the receive telegram does not match the receive list. 6 (= 06 hex): The address of the power unit in the telegram and in the receive list do not match. 9 (= 09 hex): The error bit in the receive telegram is set. 16 (= 10 hex): The receive telegram is too early. 17 (= 11 hex): CRC error and the receive telegram is too early. 18 (= 12 hex): The telegram is shorter than specified… and is too early. 19 (= 13 hex): The telegram is longer than specified… and is too early. 20 (= 14 hex): The length of the receive telegram does not match… and is too early. 21 (= 15 hex): The type of the receive telegram does not match… and is too early. 22 (= 16 hex): The address of the power unit… does not match… and is too early. 25 (= 19 hex): The error bit in the receive telegram is set and the receive telegram is too early. Remedy:
|
| F40875 CX32 DRIVE-CLiQ (CU): Supply voltage failed | Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage has failed. Fault cause: 9 (= 09 hex): The power supply voltage for the components has failed. Note regarding the message value (r0949/r2124): 0000yyxx hex: yy = component number, xx = error cause Remedy:
|
| F40885 CX32 DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred from the controller extension involved to the Control Unit. The nodes do not send and receive in synchronism. Fault cause: 26 (= 1A hex): Sign-of-life bit in the receive telegram not set and the receive telegram is too early. 33 (= 21 hex): The cyclic telegram has not been received. 34 (= 22 hex): Timeout in the telegram receive list. 64 (= 40 hex): Timeout in the telegram send list. 98 (= 62 hex): Error at the transition to cyclic operation. Remedy:
|
| F40886 CX32 DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communications error has occurred from the controller extension involved to the Control Unit. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy:
|
| F40887 CX32 DRIVE-CLiQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. Fault cause: 32 (= 20 hex): Error in the telegram header. 35 (= 23 hex): Receive error: The telegram buffer memory contains an error. 66 (= 42 hex): Send error: The telegram buffer memory contains an error. 67 (= 43 hex): Send error: The telegram buffer memory contains an error. 96 (= 60 hex): Response received too late during runtime measurement. 97 (= 61 hex): Time taken to exchange characteristic data too long. Remedy:
|
| F40895 CX32 DRIVE-CLiQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred from the controller extension involved to the Control Unit. Fault cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy:
|
| A50002 (F) COMM BOARD: Alarm 2 | Cause: CBE20 SINAMICS Link: A specific telegram word (send) is being used twice. Alarm value (r2124, interpret decimal): Telegram word used twice. See also: p8871 (SINAMICS Link PZD send word) Remedy:
|
| A50003 (F) COMM BOARD: Alarm 3 | Cause: CBE20 SINAMICS Link: A specific telegram word (receive) is being used twice. Alarm value (r2124, interpret hexadecimal): yyyyxxxx hex: yyyy = info. 1, xxxx = info. 2 Info. 1 (decimal) = Address of sender Info. 2 (decimal) = Receive telegram word See also: p8870, p8872 Remedy:
|
| A50004 (F) COMM BOARD: Alarm 4 | Cause: CBE20 SINAMICS Link: – telegram word (receive) and address of sender inconsistent. Both values have to be either equal to zero or not equal to zero. – address of the sender > maximum project address. See also: p8811, p8870, p8872 Remedy:
|
| A50005 (F) COMM BOARD: Alarm 5 | Cause: CBE20 SINAMICS Link: Sender not found on SINAMICS Link. Alarm value (r2124, interpret decimal): 0: synchronization to the bus clock cycle unsuccessful. 1 … 64: address of the sender that was not found. See also: p8872 Remedy:
|
| A50006 (F) COMM BOARD: Alarm 6 | Cause: CBE20 SINAMICS Link: The parameter assignment indicates that the sender and the receiver are one and the same. This is not permitted. See also: p8836, p8872 Remedy:
|
| A50007 (F) COMM BOARD: Alarm 7 | Cause: CBE20 SINAMICS Link: A send telegram word is greater than possible in the project. See also: p8811, p8871 Remedy:
|
| A50008 (F) COMM BOARD: Alarm 8 | Cause: CBE20 SINAMICS Link: A receive telegram word is greater than possible in the project. See also: p8811, p8870 Remedy:
|
| A50011 (F) EtherNetIP/COMM BOARD: configuration error | Cause: CBE20 EtherNet/IP: An EtherNet/IP controller attempts to establish a connection using an incorrect configuring telegram. The telegram length set in the controller does not match the parameterization in the drive device. Remedy:
|
| A60003 (F, N) Line monitoring automatic restart active | Cause: An automatic restart does not take place. An automatic restart is initiated by a line undervoltage condition. Remedy:
|
| F60004 (N, A) Armature circuit phase failure detected | Cause: Phase failure in armature infeed. Possible causes: – Phase failure threshold set incorrectly (p50353) – Armature phase failed – Line contactor opened in operation – Fuse blown on three-phase side of armature circuit – Fuse blown in power unit Fault value (r0949): 1: Power failure has occurred in armature infeed (UV, VW, WU) 2: Wait time for new zero crossing has expired in one armature phase 3: Line asymmetry in armature infeed (UV, VW, WU) Remedy:
|
| F60005 (N, A) Field circuit phase failure detected | Cause: A phase failure has been detected in the field circuit. – Phase failure threshold set incorrectly (p50353) – Field phase failed – Line contactor opened in operation – Fuse blown in field circuit Fault value (r0949): 1: Power failure in field infeed 2: Wait time for new zero crossing has expired in the field phase. Remedy:
|
| F60006 (N, A) Line monitoring undervoltage | Cause: The line voltage has undershot the permissible undervoltage limit for longer than the setting in p50361. Fault value (r0949): 1: Armature undervoltage occurred 2: Field undervoltage occurred Notes on sub-codes available in r50047. Remedy:
|
| F60007 (N, A) Line monitoring overvoltage | Cause: The line voltage has overshot the permissible overvoltage limit for longer than the setting in p50362. Fault value (r0949): 1: Armature overvoltage occurred 2: Field overvoltage occurred Remedy:
|
| F60008 (N, A) Line frequency less than minimum line frequency | Cause: The line frequency has undershot the set threshold for monitoring of the minimum line frequency for more than 40 ms. Fault value (r0949): 1: Armature supply frequency less than minimum line frequency 2: Field supply frequency less than minimum line frequency Remedy:
|
| F60009 (N, A) Line frequency greater than maximum line frequency | Cause: The line frequency has overshot the set threshold for monitoring of the maximum line frequency for more than 40 ms. Fault value (r0949): 1: Armature supply frequency greater than maximum line frequency 2: Field supply frequency greater than maximum line frequency Remedy:
|
| F60010 (N, A) Armature circuit uneven current distribution | Cause: An uneven current distribution through the thyristors has been identified in the armature circuit. Significantly less current flows in one thyristor than in the others. Possible causes: – A fuse has blown. – A thyristor is not fired (defective thyristor, defective pulse transformer, defective firing electronics). Remedy:
|
| F60012 (N, A) P2P IF: Telegram monitoring time expired | Cause: The telegram monitoring time for communication via the peer-to-peer interface (P2P IF) has expired. Possible causes: – Break in connecting cable – Electromagnetic interference on the connecting cable – Telegram monitoring time set too short (p50797) Remedy:
|
| F60014 (N, A) Parallel interface telegram monitoring time expired | Cause: The telegram monitoring time for communication via the parallel interface (Par-IF) has expired. Possible causes: – Break in connecting cable – Electromagnetic interference on the connecting cable – Telegram monitoring time set too short (p51807) Remedy:
|
| A60018 (F, N) Digital output overloaded | Cause: At least one digital output is overloaded or has short-circuited. Alarm value (r2124) bits indicate which CUD digital output (0-7) is overloaded. The fault value is equal to the inverted value of parameter r53021. Remedy:
|
| F60025 (N, A) Brush length too short | Cause: A motor brush length which is too short has been reported via a binector input (p50486) for a period exceeding a permanently set delay time. Remedy:
|
| F60026 (N, A) Poor bearing condition | Cause: A defective motor bearing has been reported via a binector input (p50487) for a period exceeding a permanently set delay time. Remedy:
|
| F60027 (N, A) Motor fan fault | Cause: A defective motor fan has been reported via a binector input (p50488) for a period exceeding a permanently set delay time. Remedy:
|
| F60028 (N, A) Motor temperature too high | Cause: A motor temperature which is too high has been reported via a binector input (p50489) for a period exceeding a permanently set delay time. Possible causes: – motor is overloaded. – Ambient temperature of the motor is too high – wire breakage or sensor not connected. Remedy:
|
| F60029 (N, A) Motor temperature fault | Cause: The motor temperature is higher than the threshold set in p50491 to trigger this fault. Possible causes: – motor is overloaded. – Ambient temperature is too high See also: p50492 (Motor interface fault threshold) Remedy:
|
| F60031 (N, A) Excessive setpoint/actual value deviation | Cause: The absolute value of the set/act deviation of the speed controller has exceeded the set threshold. See also: p50388, p50590, p50591 Remedy:
|
| A60032 (F, N) Motor temperature alarm | Cause: The motor temperature is higher than the threshold set in p50491 to trigger this alarm. Possible causes: – motor is overloaded. – Ambient temperature is too high See also: p50491 Remedy:
|
| F60035 (N, A) Motor blocked | Cause: The fault is triggered if the following conditions prevail for longer than the time set in p50355: – The positive or negative armature current or torque limit has been reached – Armature current r52109 > 1.0% – The speed actual value r52166 < p50356 filtered using parameter p50358. Remedy:
|
| F60036 (N, A) Armature circuit/field circuit interrupted | Cause: The firing angle is at the rectifier stability limit for more than 500 ms and the current is less than 1% of the rated DC current. Fault value (r0949): 1: Armature circuit 2: Field circuit Remedy:
|
| A60037 (F, N) I2t monitoring alarm excessive motor temperature rise | Cause: The I2t calculation shows that the motor’s temperature rise is excessive. The alarm is triggered if the calculated motor temperature rise in r52309 > 100%. See also: p50114, r52309 Remedy:
|
| F60038 (N, A) Overspeed threshold overshot | Cause: The speed actual value has overshot the threshold for the positive or negative maximum speed. Note: Possible cause if p50083 = 3 (EMF as speed actual value): Interrupted armature circuit. Remedy:
|
| A60039 (F, N) I2t monitoring alarm excessive power unit temperature rise | Cause: The temperature rise of the thyristors is more than 102% of the maximum permissible value. Remedy:
|
| F60041 (N, A) Ramp-function generator parameter set cannot be selected | Cause: Ramp-function generator parameter sets 2 and 3 were selected simultaneously for more than 0.5 s via binector input p50637/p50638. The ramp-function generator parameter set is not changed over; the most recently selected set is retained. Remedy:
|
| F60042 (N, A) Defective tachometer monitoring error | Cause: The ratio “Speed actual value/EMF actual value” (r52179/r52287) was less than +0.1 for more than approx. 40 ms. This ratio is then only checked if the EMF actual value is > p50357. Possible causes include cable break, incorrect connection, failed power supply, faulty tachometer, or parameter errors. Fault value (r0949): 1: Cable break affecting tachometer or incremental encoder TTL/HTL 2: Tachometer or incremental encoder TTL/HTL polarity incorrect Remedy:
|
| F60043 (N, A) EMF for braking operation too high | Cause: The EMF actual value is too high for braking operation. This fault is triggered if a firing angle greater than 165° would be required in the new torque direction immediately after a torque direction change. Possible fault causes: – “Speed-dependent field weakening” (p50081 = 0) has not been parameterized. Remedy:
|
| F60044 (N, A) Parallel interface node failure | Cause: A fault involving the parallel connection of power units has occurred. Fault value (r0949): 1: There is a fault on one of the slaves. 2: One of the slaves is not in the Operation state. 3: There are fewer power units connected in parallel that are active than set using p51802. 4: There are fewer devices that are active than set using p51815. 50, 51, 52, 53: Switchover/topology errors. Remedy:
|
| F60045 (N, A) Standstill field not permitted in operation | Cause: The standstill field was activated while the drive was operational. The binector input p50692 to activate the standstill field must not have a 1 signal in operation. See also: p50692 (CI-loop field curr ctrl sig source for inject of standst field) Remedy: If required, set binary input p50692 – used to activate the standstill field – to a 0 signal. |
| F60046 (N, A) Wire break at “Main setpoint” analog input | Cause: A wire break has been detected at the CUD’s “Main setpoint” analog input (X177.25/26). This fault is triggered if p50700 = 2 (unipolar monitoring of current input (+4 mA to +20 mA)) is set and an input current of less than 2 mA is flowing. Possible fault causes:
Note: This fault is also indicated via binector input r53030.0. See also: p50700 (CUD analog input 0 type) Remedy:
|
| F60047 (N, A) Wire break at analog input 1 | Cause: A wire break has been detected at the CUD’s analog input 1 (X177.27/28). This fault is triggered if p50700 = 2 (unipolar monitoring of current input (+4 mA to +20 mA)) is set and an input current of less than 2 mA is flowing. Possible fault causes:
Note: This fault is also indicated via binector output r53030.1. See also: p50710 (CUD analog input 1 type) Remedy:
|
| F60050 Optimization run aborted due to internal cause | Cause: An optimization run which had been started has been interrupted due to an internal cause. Fault value (r0949, interpret decimal):
(Note: Additional diagnostic information available in r50047 for various fault values) Remedy:
|
| F60051 (N, A) Optimization run limit value violated | Cause: During the optimization run, an attempt was made to set a parameter to a value outside its valid range of values. The parameter value was set to the appropriate limit value. Fault value (r0949, interpret decimal): Parameter number of the parameter causing the error. See also r50047 for incorrect/limited values. Remedy: You might have to set the parameter value manually. |
| F60052 (N, A) Optimization run aborted due to external cause | Cause: An optimization run which had been started has been interrupted due to an external cause. Fault value (r0949, interpret decimal):
See also r50047 for specific error details. Remedy: Interpret the fault value and rectify the fault correspondingly. For fault value 109:
|
| F60055 Field characteristic not valid | Cause: Field weakening in conjunction with the optimization run for field weakening has not yet been performed. Fault value (r0949, interpret decimal):
Remedy: Record field characteristic. See also: p50081, p50117, p50170 |
| F60056 Important parameter not set | Cause: Settings required for operation have not yet been made or connected components have not yet been commissioned. Fault value (r0949, interpret decimal):
Remedy: Make the setting as appropriate for the fault value displayed. |
| F60057 (N, A) Armature current sensing fault | Cause: The message is triggered if there are opposing current and torque directions. The monitoring is active as soon as the current values exceed the device rated current by 20%. See also r50047 for torque direction and current scan values. Remedy: Check current transformer/shunt. |
| F60058 Parameter settings not consistent | Cause: Inconsistent values have been set in parameters depending on each other. Fault value (r0949, interpret decimal):
Remedy: Make the setting as appropriate for the fault value displayed. |
| F60061 Thyristor test unsuccessful | Cause: With the thyristor test activated (p50830), a fault was detected for at least one thyristor. Fault value (r0949, interpret decimal):
Possible reasons: Interrupted snubber circuit, current controller not optimized, cooling failure, excessive voltage peaks, external short-circuit, firing pulse cable fault. Remedy: Interpret the fault value and rectify the fault correspondingly (e.g., replace thyristor module, check firing pulse cable, check gating module). |
| F60062 (N, A) Communication error to the voltage sensing | Cause: Communication to one of the two voltage sensing devices is faulted or interrupted. Fault value (r0949):
Remedy: Carry out a POWER ON (switch-off/switch-on) for all components. |
| F60063 (N, A) Incorrect calibration values for analog inputs/outputs | Cause: The factory-set calibration values on the electronics module for the analog inputs/outputs are implausible. Fault value (r0949) indicates the specific input/output and error type (1-56). Examples:
Remedy: Replace the electronics module with the incorrect calibration values. |
| F60064 (N, A) Error communicating with second processor TMS320 | Cause: Communication with the second processor (TMS320) has failed. Remedy: Carry out a POWER ON (switch-off/switch-on) for all components. |
| F60065 (N, A) Software update on second processor (TMS320) failed | Cause: The updating of the software for the second processor (TMS320) has failed. Fault value (r0949) indicates the state in which the fault occurred (e.g., bootloader, Flash API, Flash EPROM deletion). Values 100, 101 indicate incompatible versions. Remedy: Carry out a POWER ON (switch-off/switch-on) for all components. |
| F60066 (N, A) Error communicating with sensors | Cause: An error occurred when polling the fan speeds and temperature sensors. Fault value (r0949):
Remedy: Carry out a POWER ON (switch-off/switch-on) for all components. |
| F60067 (N, A) Fault temperature too high | Cause: The temperature at one of the temperature sensors has exceeded the highest permissible temperature. Fault value (r0949):
Remedy:
|
| F60068 (N, A) Incorrect calibration values for power unit | Cause: The calibration values for the power unit are missing or incorrect. Fault value (r0949):
Remedy: Carry out a POWER ON (switch-off/switch-on) for all components. |
| F60069 (N, A) Invalid article number (MLFB) | Cause: The data read from the power unit (serial number, MLFB, accessory options) is invalid. Fault value (r0949):
Remedy: Send your SINAMICS DC MASTER to the manufacturer’s plant or an authorized repair center. |
| A60080 (F, N) Alarm temperature too high | Cause: The temperature at one of the temperature sensors has exceeded the highest permissible temperature to initiate this alarm. Alarm value (r2124): See F60067 for sensor details. Remedy:
|
| A60081 (F, N) Alarm module temperature exceeded | Cause: The temperature on the Control Unit DC MASTER (CUD) has exceeded the alarm value (temperature above 90 °C). Remedy: Check the ambient temperature and reduce if necessary. |
| A60082 (F, N) Alarm derating factor K1 limit value fallen below | Cause: For a drive device equipped with option L99, derating (reduced power) is calculated depending on the air intake temperature. The calculated derating factor K1 has fallen below the set limit value (p50066). See also: p50066 (Power unit I2t monitoring derating factor K1 limit value) Remedy:
|
| F60090 (N, A) Fault module temperature exceeded | Cause: The temperature on the Control Unit DC MASTER (CUD) has exceeded the fault value (temperature above 95 °C). Remedy:
|
| F60091 (N, A) Reference voltage P10 outside tolerance | Cause: The reference voltage P10 (+10 V) at terminal X177.31 lies outside the tolerance (deviation greater than +/-5%). Remedy:
|
| F60092 (N, A) Reference voltage N10 outside tolerance | Cause: The reference voltage N10 (-10 V) at terminal X177.32 lies outside the tolerance (deviation greater than +/-5%). Remedy:
|
| F60093 (N, A) Power supply P5 overloaded | Cause: Power supply P5 (+5 V) at connector X179.1 is overloaded. Remedy:
|
| F60094 (N, A) Power supply P15 overloaded | Cause: Power supply P15 (+15 V) at terminal X177.41 is overloaded. Remedy:
|
| F60095 (N, A) Power supply P24 overloaded | Cause: Power supply P24 (+24 V) at terminal X177.9 or X177.10 is overloaded. Remedy:
|
| F60096 (N, A) Temperature sensor faulty | Cause: A cable break or a short circuit has been detected on at least one temperature sensor. Fault value (r0949, interpret decimal): 1: A cable break has occurred. 2: A short circuit has occurred. Note: When using PTCs (p50490 = 2,3,4,5) the cable is not monitored for interruption or short-circuit. Remedy:
|
| F60097 (N, A) Power supply faulty | Cause: The power supply is not working correctly. Note: For SINAMICS DCM with 2 CUD, if a reset is carried out at one CUD, this fault is output at the other. Remedy:
|
| A60098 (F, N) System utilization high | Cause: The average computing time utilization (r9976[1]) for the system is greater than 95 %. Remedy:
|
| F60099 (N, A) System utilization too high | Cause: The average computing time utilization (r9976[1]) for the system is greater than 100 %. Remedy:
|
| F60104 (N, A) Armature circuit line voltage not OK | Cause: On power up, the time set in p50089 (voltage wait time) or p50095 (line contactor feedback) has expired. Fault value (r0949): 2: Wait time set in p50089 has expired in operating state o4.0. 3: Fuse blown on three-phase side of armature circuit. 6: Wait time set in p50095 has expired in operating state o3.3. Note for fault value = 2 (Bit field r50047[1]): Bit 0=1: Overvoltage, Bit 1=1: Undervoltage, Bit 4=1: Phase failure, Bit 12=1: Clockwise phase sequence, etc. Remedy:
|
| F60105 (N, A) Field current monitoring fault in field circuit | Cause: Field current monitoring has detected erroneous behavior. Fault value (r0949): 1: Field current actual value < percentage of setpoint (p50396). 2: Field line voltage not available within time set (p50089). 3: Field current not available within time set (p50089). 4: External field current monitoring responded (BI: p50265 = 1/0). Remedy:
|
| F60106 (N, A) Short-circuit voltage Uk too high | Cause: The per unit short-circuit voltage of the line supply is greater than 10 %. Permissible values are between 2 and 10 %. Remedy:
|
| F60137 (N, A) I2t monitoring fault excessive motor temperature rise | Cause: The I2t calculation shows that the motor’s temperature rise is excessive. Triggered if r52309 > 110%. Remedy:
|
| F60139 (N, A) I2t monitoring fault excessive power unit temperature rise | Cause: The temperature rise of the thyristors is more than 102% of the maximum permissible value. Remedy:
|
| A60143 (F, N) Reduction of the field current setpoint for an excessively high EMF during braking active | Cause: Reduction of the field current setpoint for an excessively high EMF during braking is active. Remedy:
|
| A60144 Minimum field current setpoint limit reached | Cause: The minimum field current setpoint limit was reached. Remedy:
|
| A60165 (F, N) Fan end of service life has been reached or exceeded | Cause: At least one device fan has reached the end of its service life – or has exceeded it. Remedy:
|
| A60166 (F, N) Alarm fan speed too slow | Cause: The fan speed is too slow. The fan is probably blocked or faulty. Remedy:
|
| F60167 (N, A) Fault fan speed too slow | Cause: a) The fan speed is too slow. The fan is probably blocked or faulty. b) The AC fan was switched off in operation or before the fan run on time p50096 expired by an external fan control. Remedy:
|
| A60168 (F, N) Memory card not plugged in | Cause: The data recorded with the recorder function could not be saved on the memory card. Possible causes: Memory card not plugged in or defective. Fault value (r0949): 1: Unable to create or open the file 2: Unable to write to the file 3: Unable to write all data to the file Remedy:
|
| F60203 (N, A) External fault triggered | Cause: An external fault has been triggered via terminal 124/125 on the Control Module. Remedy:
|
| F60204 (N, A) Fuse monitoring has responded | Cause: Fuse monitoring on the Control Module has detected at least one blown fuse. Fault value (r0949): 1: Slot X23B, 2: Slot X23C, 3: Slot X23D, 4: Slot X23E, 5: Slot X23F. Remedy:
|
| A60266 (F, N) Alarm fan not OK | Cause: For Control Module without option Z01…Z15: Signal at terminal 122/123 signals “Fan not OK”. For Control Module with option Z01…Z15: Differential pressure fallen below threshold. Remedy:
|
| F60267 (N, A) CM: Fan not OK | Cause: For Control Module without option Z01…Z15: Signal at terminal 122/123 signals “Fan not OK”. For Control Module with option Z01…Z15: Differential pressure fallen below threshold. Remedy:
|
| F60300 Commutation failure | Cause: Commutation failure or overcurrent has occurred or a test command was entered via p51583. Fault value (r0949, interpret decimal): 1: Thyristor being turned off did not accept blocking voltage. 2: Current did not flow through correct thyristor or current cusp made a kink upwards. 3: Magnitude of current cusp > 290% of rated DC current. 4: SINAMICS DCM connected in parallel detected commutation failure. 5: Test command entered via p51583. Remedy:
|
| F60320 (N, A) CCP not functional | Cause: The SIMOREG CCP is not functional. Fault value (r0949): 1: No voltage at U, V, W connections. 2: Voltage at C-D does not match. 3: Turn-off capacitors have not reached setpoint voltage. 4: No connection (X165_2). 5: No connection (X177 / X172). 11: I2t value of voltage limiting chopper 1 too high. 12: I2t value of voltage limiting chopper 2 too high. 20: Chopper capacitors not precharged in time. Remedy:
|
| A60321 (F, N) CCP not functional | Cause: The SIMOREG CCP is not functional. Alarm value (r2124): Same codes as F60320 (1, 2, 3, 4, 5, 11, 12, 20). Remedy:
|