Siemens S120 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 Floating Point data type. The error may be caused by the basic system or an OA application (e.g., FBLOCKS, DCC). Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Note: Refer to r9999 for further information about this fault. r9999[0]: Fault number. r9999[1]: Program counter at the time when the exception occurred. r9999[2]: Cause of the Floating Point exception. 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 Acknowledgement 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:
See also: r9999 (Software error internal supplementary diagnostics) |
| 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 = 11 dec: DRIVE-CLiQ component has detected a checksum error. xxxx = 000F hex = 15 dec: The selected DRIVE-CLiQ component did not accept the contents of the firmware file. xxxx = 0012 hex = 18 dec: Firmware version is too old and is not accepted by the component. xxxx = 0013 hex = 19 dec: Firmware version is not suitable for the hardware release of the component. xxxx = 0065 hex = 101 dec: After several communication attempts, no response from the DRIVE-CLiQ component. xxxx = 008B hex = 139 dec: Initially, a new boot loader is loaded (must be repeated after POWER ON). xxxx = 008C hex = 140 dec: Firmware file for the DRIVE-CLiQ component not available on the memory card. xxxx = 008D hex = 141 dec: An inconsistent length of the firmware file was signaled. The firmware download may have been caused by a loss of connection to the firmware file. This can occur during a project download/reset in the case of a SINAMICS Integrated Control Unit, for example. xxxx = 008F hex = 143 dec: Component has not changed to the mode for firmware download. It was not possible to delete the existing firmware. xxxx = 0090 hex = 144 dec: When checking the firmware that was downloaded (checksum), the component detected a fault. It is possible that the file on the memory card is defective. xxxx = 0091 hex = 145 dec: Checking the loaded firmware (checksum) was not completed by the component in the appropriate time. xxxx = 009C hex = 156 dec: Component with the specified component number is not available (p7828). xxxx = Additional values: Only for internal Siemens troubleshooting. Remedy:
Depending on p7826, the firmware will be automatically downloaded. |
| 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: Firmware update using the commissioning software: The firmware version of all of the components on the “Version overview” page can be read in the Project Navigator under “Configuration” of the associated drive unit and an appropriate firmware update can be carried out. Firmware update via parameter:
|
| A01007 POWER ON for DRIVE-CLiQ component required | Cause: A DRIVE-CLiQ component must be powered up again (POWER ON) (e.g. due to a firmware update). Alarm value (r2124, interpret decimal): Component number of the DRIVE-CLiQ component. Note: For a component number = 1, a POWER ON of the Control Unit is required. Remedy:
|
| A01009 (N) CU: Control module overtemperature | Cause: The temperature (r0037[0]) of the control module (Control Unit) has exceeded the specified limit value. Remedy:
Note: The alarm automatically disappears after the limit value has been undershot. |
| 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 ended by the commissioning software (e.g. STARTER, SCOUT). 100: Different versions between the firmware version and project files which were loaded by loading into the file system “Download from memory card”. Note: The response to an interrupted download is the state “first commissioning”. Remedy:
|
| F01012 (N) Project conversion error | Cause: When converting the project of an older firmware version, an error occurred. Fault value (r0949, interpret decimal): Parameter number of the parameter causing the error. For fault value = 600, the following applies: The temperature evaluation is no longer assigned to the power unit but to the encoder evaluation. Notice: Monitoring of the motor temperature is no longer ensured. Remedy: Check the parameter indicated in the fault value and correctly adjust it accordingly. For fault value = 600: Parameter p0600 must be set to the values 1, 2 or 3 in accordance with the assignment of the internal encoder evaluation to the encoder interface. Value 1 means: The internal encoder evaluation is assigned to the encoder interface 1 via p0187. Value 2 means: The internal encoder evaluation is assigned to the encoder interface 2 via p0188. Value 3 means: The internal encoder evaluation is assigned to the encoder interface 3 via p0189.
|
| A01013 CU: Fan operating time reached or exceeded | Cause: The maximum operating time of the fan in the Control Unit has either been reached or exceeded. Alarm value (r2124, interpret decimal): 0: The maximum fan operating time is 500 hours. 1: The maximum fan operating time has been exceeded (50000 hours). Remedy: Replace the fan in the Control Unit and reset the operating hours counter to 0 (p3961 = 0). |
| F01015 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01016 (F) Firmware changed | Cause: At least one firmware file in the directory was illegally changed on the non-volatile memory (memory card/device memory) with respect to the version when shipped from the factory. Alarm value (r2124, interpret decimal): 0: Checksum of one file is incorrect. 1: File missing. 2: Too many files. 3: Incorrect firmware version. 4: Incorrect checksum of the back-up file. Remedy: For the non-volatile memory for the firmware (memory card/device memory), restore the delivery condition. Note: The file involved can be read out using parameter r9925. The status of the firmware check is displayed using r9926. See also: r9925 (Firmware file incorrect), r9926 (Firmware check status) |
| 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: Firmware version of the file does not match the software version. x = 3: File checksum is incorrect. y = 0: Directory /SIEMENS/SINAMICS/DATA/ y = 1: Directory /ADDON/SINAMICS/DATA/ z = 0: File MOTARM.ACX z = 1: File MOTSRM.ACX z = 2: File MOTSLM.ACX z = 3: File ENCDATA.ACX z = 4: File FILTDATA.ACX z = 5: File BRKDATA.ACX z = 6: File DAT_BEAR.ACX z = 7: File CFG_BEAR.ACX z = 8: File ENC_GEAR.ACX Remedy: For the file on the memory card involved, restore the status originally supplied from the factory. |
| A01020 Writing to RAM disk unsuccessful | Cause: A write access to the internal RAM disk was unsuccessful. Remedy: Adapt the file size for the system logbook to the internal RAM disk (p9930). See also: p9930 (System logbook activation) |
| 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: Set the monitoring time higher at the PC or, if required, completely disable the monitoring function. For the commissioning software, the monitoring time is set as follows: Notice: The monitoring time should be set as short as possible. A long monitoring time means a late response when the communication fails! |
| 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. For the system to successfully power up, all of the parameters must have been completely backed up. Alarm value (r2124, interpret decimal): Only for internal Siemens troubleshooting. See also: p0971 (Save drive object parameters) Remedy: Save all parameters (p0977 = 1 or “copy RAM to ROM”). See also: p0977 (Save all parameters) |
| F01033 Units changeover: Reference parameter value invalid | Cause: When changing over the units to the referred representation type, it is not permissible for any of the required reference parameters to be equal to 0.0 Fault value (r0949, parameter): Reference parameter whose value is 0.0. See also: p0349 (System of units motor equivalent circuit diagram data), p0505 (Selecting the system of units), p0595 (Technological unit selection) Remedy: Set the value of the reference parameter to a number different than 0.0. See also: p0304, p0305, p0310, p0596, p2000, p2001, p2002, p2003, r2004 |
| 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. Fault value (r0949, parameter): Parameter whose value was not able to be re-calculated. See also: p0304, p0305, p0310, p0596, p2000, p2001, p2002, p2003, r2004 Remedy:
See also: p0304, p0305, p0310, p0596, p2000, p2001, p2002, p2003, r2004 |
| 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. It is possible that the backup was interrupted by switching off or withdrawing the memory card. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: aa = 01 hex: Power up was realized without data backup. The drive is in the factory setting. aa = 02 hex: The last available backup data record was loaded. The parameterization must be checked. It is recommended that the parameterization is downloaded again. dd, cc, bb: Only for internal Siemens troubleshooting. See also: p0971 (Save drive object parameters), p0977 (Save all parameters) Remedy:
See also: p0977 (Save all parameters) |
| F01036 (A) ACX: Parameter back-up file missing | Cause: When downloading the device parameterization, a parameter back-up file PSxxxyyy.ACX associated with a drive object cannot be found. Fault value (r0949, interpret hexadecimal): Byte 1: yyy in the file name PSxxxyyy.ACX yyy = 000 –> consistency back-up file yyy = 001 … 062 –> drive object number yyy = 099 –> PROFIBUS parameter back-up file Byte 2, 3, 4: Only for internal Siemens troubleshooting. Remedy: If you have saved the project data using the commissioning software, carry out a new download for your project. Save using the function “Copy RAM to ROM” or with p0977 = 1 This means that the parameter files are again completely written into the non-volatile memory. Note: If the project data have not been backed up, then a new first commissioning is required. |
| F01038 (A) ACX: Loading the parameter back-up file unsuccessful | Cause: An error has occurred when downloading PSxxxyyy.ACX or PTxxxyyy.ACX files from the non-volatile memory. Fault value (r0949, interpret hexadecimal): Byte 1: yyy in the file name PSxxxyyy.ACX yyy = 000 –> consistency back-up file yyy = 001 … 062 –> drive object number yyy = 099 –> PROFIBUS parameter back-up file Byte 2: 255: Incorrect drive object type. 254: Topology comparison unsuccessful -> drive object type was not able to be identified. Reasons could be: – Incorrect component type in the actual topology – Component does not exist in the actual topology. – Component not active. Additional values: Only for internal Siemens troubleshooting. Byte 4, 3: Only for internal Siemens troubleshooting. Remedy:
Re byte 2 = 255: – Correct the drive object type (see p0107). |
| 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. – In the directory /USER/SINAMICS/DATA/ at least one parameter back-up file PSxxxyyy.*** has the “read only” file attribute and cannot be overwritten. – There is not sufficient free memory space available. – The non-volatile memory is defective and cannot be written to. Fault value (r0949, interpret hexadecimal): dcba hex a = yyy in the file names PSxxxyyy.*** a = 000 –> consistency back-up file a = 001 … 062 –> drive object number a = 070 –> FEPROM.BIN a = 080 –> DEL4BOOT.TXT a = 099 –> PROFIBUS parameter back-up file b = xxx in the file names PSxxxyyy.*** b = 000 –> data save started with p0977 = 1 or p0971 = 1 b = 010 –> data save started with p0977 = 10 b = 011 –> data save started with p0977 = 11 b = 012 –> data save started with p0977 = 12 d, c: Only for internal Siemens troubleshooting. 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:
Then: – upload the drive unit (commissioning software). |
| 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. Examples: – p1810.2 (wobulation of the pulse frequency) and p1802 (edge modulation) – p1750.5 (cl.-loop control mode PESM up to f=0Hz with HF signal injection) Remedy:
When changing p1750.5 or p1810.2 for edge modulation, a warm restart is sufficient (p0009 = 30, p0976 = 3). Then: – upload the drive unit (commissioning software). |
| F01041 Parameter save necessary | Cause: Defective or missing files were detected on the memory card when booting. Fault value (r0949, interpret decimal): 1: Source file cannot be opened. 2: Source file cannot be read. 3: Target directory cannot be set up. 4. Target file cannot be set up/opened. 5. Target file cannot be written to. Additional values: Only for internal Siemens troubleshooting. 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). For the specified parameter, it was detected that dynamic limits were exceeded that may possibly depend on other parameters. Fault value (r0949, interpret hexadecimal): ccbbaaaa hex aaaa = Parameter bb = Index cc = fault cause (A detailed list of fault cause codes from 0 to 204 follows) Remedy:
|
| F01043 Fatal error at project download | Cause: A fatal error was detected when downloading a project using the commissioning software. Fault value (r0949, interpret decimal): (A detailed list of fault value codes from 1 to 22 follows) Additional values: only for internal Siemens troubleshooting. Remedy:
|
| F01044 CU: Descriptive data error | Cause: An error was detected when loading the descriptive data saved in the non-volatile memory. Remedy: Replace the memory card or Control Unit. |
| A01045 CU: Configuring data invalid | Cause: An error was detected when evaluating the parameter files PSxxxyyy.ACX, PTxxxyyy.ACX, CAxxxyyy.ACX, or CCxxxyyy.ACX saved in the non-volatile memory. Because of this, under certain circumstances, several of the saved parameter values were not able to be accepted. Also see r9406 up to r9408. Alarm value (r2124, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
Then save the parameterization in STARTER using the “Copy RAM to ROM” function or with p0977 = 1. This overwrites the incorrect parameter files in the non-volatile memory – and the alarm is withdrawn. |
| 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. Alarm value (r2124, interpret decimal): Drive object number. Remedy: Check whether the “write protected” attribute has been set for the files in the non-volatile memory under …/USER/SINAMICS/DATA/… When required, remove write protection and save again (e.g. set p0977 to 1). |
| 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. Fault value (r0949, interpret decimal): 1: Computing time load too high (r9976[1]). 5: Peak load too high (r9976[5]). Note: As long as this fault is present, it is not possible to save the parameters (p0971, p0977). See also: r9976 (System utilization) Remedy: Re fault value = 1, 5:
When using the Drive Control Chart (DCC) or free function blocks (FBLOCKS), the following applies
|
| 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. The first application whose registration (log-on) connects a slave to a port defines the SYNO clock cycle that will be used as basis for the port. Fault value (r0949, interpret hexadecimal): Method ID. Note: Only for internal Siemens troubleshooting. Remedy: Contact the Hotline. |
| 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. Fault value (r0949, interpret hexadecimal): Method ID. Note: Only for internal Siemens troubleshooting. Remedy: Contact the Hotline. |
| 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. Fault value (r0949, interpret hexadecimal): Method ID. Note: Only for internal Siemens troubleshooting. Remedy: Contact the Hotline. |
| F01058 CU: Internal error (slave missing in topology) | Cause: The requested slave component does not exist in the topology. Fault value (r0949, interpret hexadecimal): Method ID. Note: Only for internal Siemens troubleshooting. Remedy: Contact the Hotline. |
| 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. Fault value (r0949, interpret hexadecimal): Method ID. Note: Only for internal Siemens troubleshooting. Remedy: Contact the Hotline. |
| F01060 CU: Internal error (parameter group not available) | Cause: The requested parameter group (IREG, NREG, …) is not offered by this slave type. Fault value (r0949, interpret hexadecimal): Method ID. Note: Only for internal Siemens troubleshooting. Remedy: Contact the Hotline. |
| F01061 CU: Internal error (application not known) | Cause: An application that is not registered with TSM has attempted to register with registerSlaves(). The cause can be an unsuccessful TSM registration or an incorrect registration sequence. It is always necessary to log in to the TSM before registerSlaves() can be used. Fault value (r0949, interpret hexadecimal): Method ID. Note: Only for internal Siemens troubleshooting. Remedy: Contact the Hotline. |
| F01063 CU: Internal error (PDM) | Cause: An internal software error has occurred. Fault value (r0949, interpret hexadecimal): Method ID. Note: Only for internal Siemens troubleshooting. Remedy: Contact the Hotline. |
| A01064 (F) CU: Internal error (CRC) | Cause: CRC error in the Control Unit program memory Remedy:
|
| F01068 CU: Data memory memory overflow | Cause: The utilization for a data memory area is too large. Fault value (r0949, interpret binary): Bit 0 = 1: High-speed data memory 1 overloaded Bit 1 = 1: High-speed data memory 2 overloaded Bit 2 = 1: High-speed data memory 3 overloaded Bit 3 = 1: High-speed data memory 4 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:
|
| F01070 Project/firmware is being downloaded to the memory card | Cause: An upgrade (project/firmware download) was initiated on the memory card. While this fault is present, the corresponding update takes place with plausibility and consistency checks. After this, depending on the command option, a new boot (reset) for the Control Unit is initiated. Caution: During the upgrade and while this fault is present, it is not permissible to switch off the Control Unit. If the operation is interrupted, this can destroy the file system on the memory card. The memory card will then no longer work properly and must be repaired. Remedy: Not necessary. The fault automatically disappears after the upgrade has been completed. |
| F01072 Memory card restored from the backup copy | Cause: The Control Unit was switched-off while writing to the memory card. 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: Check that the firmware and parameterization is up-to-date. |
| A01073 (N) POWER ON required for backup copy on memory card | Cause: The parameter assignment on the visible partition of the memory card has changed. 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:
|
| A01099 Tolerance window of time synchronization exited | Cause: The time master exited the selected tolerance window for time synchronization. See also: p3109 (RTC real time synchronization tolerance window) Remedy: Select the re-synchronization interval so that the synchronization deviation between the time master and drive system lies within the tolerance window. See also: r3108 (RTC last synchronization deviation) |
| 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:
|
| 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, OA applications, blocks, etc). Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01106 CU: Insufficient memory | Cause: There is not sufficient free memory space available. Remedy: Not necessary. |
| F01107 CU: Save to memory card unsuccessful | Cause: A data save in the non-volatile memory was not able to be successfully carried out. – non-volatile memory is defective. – insufficient space in the non-volatile memory. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. 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: Only one SINAMICS G drive type is permitted. |
| F01111 CU: Mixed operation of drive units illegal | Cause: Illegal operation of various drive units on one Control Unit: – 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: Only power units of one particular drive type may be operated with one Control Unit. |
| F01112 CU: Power unit not permissible | Cause: The connected power unit cannot be used together with this Control Unit. 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: Replace the power unit that is not permissible by a component that is permissible. |
| F01120 (A) Terminal initialization has failed | Cause: An internal software error occurred while the terminal functions were being initialized. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. 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) 4: DI/DO 11 (X122.11) 8: DI/DO 13 (X132.8) 16: DI/DO 14 (X132.10) 32: DI/DO 15 (X132.11) 64: DI/DO 8 (X122.7) 128: DI/DO 12 (X132.7) Remedy: Reduce the frequency of the pulses at the measuring probe input. |
| F01123 Power unit does not support digital inputs/outputs | Cause: Power unit does not support the activated “digital inputs/outputs” function module Remedy: De-activate the function module. |
| 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: Drive object type (p0107), for which the maximum permissible number of instances was exceeded. Number permitted: Max. permissible number of instances for this drive object type. Actual number: Current number of instances for this drive object type. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): ddccbbaa hex: aa = drive object type, bb = number limited, cc = actual number, dd = no significance 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: Drive object category, for which the maximum permissible number of drive objects was exceeded. Number permitted: Max. permissible number for this drive object category. Actual number: Actual number for this drive object category. Note regarding the message value: The individual information is coded as follows in the message value (r0949/r2124): ddccbbaa hex: aa = drive object category, bb = number limited, cc = actual number, dd = no significance 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 OA (e.g. DCC). 999: Too many time slices occupied by the basic system. Too many different sampling times may have been set. Additional values: Only for internal Siemens troubleshooting. Remedy:
|
| F01205 CU: Time slice overflow | Cause: Insufficient processing time is available for the existing topology. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01221 CU: Bas clk cyc 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. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: Increase the basic clock cycle of DRIVE-CLiQ communication. See also: p0112 (Sampling times pre-setting p0115) |
| 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. Fault value (r0949, interpret hexadecimal): Method ID. Note: Only for internal Siemens troubleshooting. Remedy: Contact the Hotline. |
| 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): (A detailed list of value inconsistency codes from 1 to 116 follows) Remedy: General note: The topology rules should be noted when connecting up DRIVE-CLiQ (refer to the appropriate product documentation). The parameters of the sampling times can also be changed with automatic calculations. Example for highest common denominator: 125 µs, 125 µs, 62.5 µs –> 62.5 µs
See also: p0115, p0799, p4099 |
| 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 clock-cycle synchronous 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: Set a valid pulse frequency. See also: p0113 (Minimum pulse frequency, selection) |
| F01250 CU: CU-EEPROM incorrect read-only data | Cause: Error when reading the read-only data of the EEPROM in the Control Unit. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01251 CU: CU-EEPROM incorrect read-write data | Cause: Error when reading the read-write data of the EEPROM in the Control Unit. Alarm value (r2124, interpret decimal): Only for internal Siemens troubleshooting. Remedy: For alarm value r2124 < 256, the following applies:
For alarm value r2124 >= 256, the following applies:
|
| F01255 CU: Option Board EEPROM read-only data error | Cause: Error when reading the read-only data of the EEPROM in the Option Board. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. 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. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01260 Software not released | Cause: The runtime software (RT-SW) has not been released. Remedy: Only for internal Siemens troubleshooting. |
| F01275 Hardware description error | Cause: An error has occurred while accessing the hardware description file on the CompactFlash card. Directory and file name: ADDON/SINAMICS/DATA/HW_DESC/014/DESC0000.ACX Fault value (r0949, interpret decimal): 22: File not found. 24: File read access error. 26: Format error. 28: Version error. 30: Internal error ACX reader. 40: Contents error. 45: Hardware description not consistent. 60: Inconsistency: Number of Power Stack Adapters (PSA). 61: Inconsistency: Number of Sensor Module Cabinets (SMC). 62: Inconsistency: Number of Voltage Sensing Modules (VSM). 63: Inconsistency: Number of Terminal Modules (TM). 64: Inconsistency: Number of Terminal Boards (TB). Remedy: Only for internal Siemens troubleshooting. |
| A01276 Hardware description not fully compatible | Cause: The hardware description file contains more data than the firmware requires. Remedy: Not necessary. |
| A01302 Error in the component trace | Cause: An error has occurred in the component trace. The message appears in the following cases: – upload trace data (p7792 = 1). – change factory setting (p7790, p7791) for missing property “component trace” (r0193.1 = 0). Alarm value (r2124, interpret decimal): 1: The DRIVE-CLiQ component does not support the component trace (r0193.1 = 0). 101: Data from trace 1 cannot be read. 102: Data from trace 2 cannot be read. 103: Data from trace 3 cannot be read. 104: Data from trace 4 cannot be read. 105: Data from trace 5 cannot be read. Remedy: Re alarm value = 1: Upgrade the firmware of the DRIVE-CLiQ component involved. |
| F01303 Component does not support the required function | Cause: A function requested by the Control Unit is not supported by a DRIVE-CLiQ component. Fault value (r0949, interpret decimal): (A detailed list of fault value codes from 1 to 213 follows) Remedy: Upgrade the firmware of the DRIVE-CLiQ component involved. For fault value = 205: Check parameter p0600 and p0601 and if required, adapt interpretation. For fault value = 207: Replace the power unit or if required set the device supply voltage higher (p0210). For fault value = 208: Check parameter p0430.23 and reset if necessary. |
| A01304 (F) Firmware version of DRIVE-CLiQ component is not up-to-date | Cause: The non-volatile memory has a more recent firmware version than the one in the connected DRIVE-CLiQ component. Alarm value (r2124, interpret decimal): Component number of the DRIVE-CLiQ component involved. Remedy: Update the firmware (p7828, p7829 and commissioning software). |
| F01305 Topology: Component number missing | Cause: The component number from the topology was not parameterized (p0121 (for power unit, refer to p0107), p0131 (for servo/vector drives, refer to p0107), p0141, p0151, p0161). Fault value (r0949, interpret decimal): Data set number. Note: The fault also occurs if encoders have been configured (p0187 to p0189) but no component numbers exist for them. In this case, the fault value includes the drive data set number plus 100 * encoder number (e.g. 3xx, if a component number was not entered in p0141 for encoder 3 (p0189)). See also: p0121, p0131, p0141, p0142, p0151, p0161, p0186, p0187, p0188, p0189 Remedy:
See also: p0121, p0131, p0141, p0142, p0151, p0161, p0186, p0187, p0188, p0189 |
| A01306 Firmware of the DRIVE-CLiQ component being updated | Cause: Firmware update is active for at least one DRIVE-CLiQ component. Alarm value (r2124, interpret decimal): Component number of the DRIVE-CLiQ component. Remedy: Not necessary. This alarm automatically disappears after the firmware has been updated. |
| A01314 Topology: Component must not be present | Cause: For a component, “de-activate and not present” is set but this component is still in the topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: aa = component number bb = component class of the component cc = connection number Note: Component class and connection number are described in F01375. Remedy:
Note: Under “Topology –> Topology view” the commissioning software where relevant offers improved diagnostics capability (e.g. setpoint/actual value comparison). See also: p0105, p0125, p0145, p0155, p0165 |
| A01315 Drive object not ready for operation | Cause: For the active drive object involved, at least one activated component is missing. Note: All other active and operational drive objects can be in the “RUN” state. Remedy: The alarm automatically disappears again with the following actions:
See also: p0105, p0125, p0145, p0155, p0165 |
| A01316 Drive object inactive and again ready for operation | Cause: If, when inserting a component of the target topology, an inactive, non-operational drive object becomes operational again. The associated parameter of the component is, in this case, set to “activate” (p0125, p0145, p0155, p0165). Note: This is the only message that is displayed for a de-activated drive object. Remedy: The alarm automatically disappears again with the following actions:
See also: p0105 |
| A01317 (N) De-activated 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 “de-activate” (p0125, p0145, p0155, p0165). Note: This is the only message that is displayed for a de-activated component. Remedy: The alarm automatically disappears again with the following actions:
See also: p0125, p0145, p0155, p0165 |
| A01318 BICO: De-activated interconnections present | Cause: This alarm is used in the following cases:
Remedy: Reset alarm:
or
|
| A01319 Inserted component not initialized | Cause: Initialization is required for at least one inserted component. This is only possible if the pulses are inhibited for all the drive objects. Remedy: Activate pulse inhibit for all drive objects. |
| A01320 Topology: Drive object number does not exist in configuration | Cause: A drive object number is missing in p0978 Alarm value (r2124, interpret decimal): Index of p0101 under which the missing drive object number can be determined. Remedy: Set p0009 to 1 and change p0978: Rules:
|
| A01321 Topology: Drive object number does not exist in configuration | Cause: p0978 contains a drive object number that does not exist. Alarm value (r2124, interpret decimal): Index of p0978 under which the drive object number can be determined. Remedy: Set p0009 to 1 and change p0978: Rules:
|
| A01322 Topology: Drive object number present twice in configuration | Cause: A drive object number is present more than once in p0978. Alarm value (r2124, interpret decimal): Index of p0978 under which the involved drive object number is located. Remedy: Set parameter p0009 = 1 and change p0978: Rules:
|
| A01323 Topology: More than two partial lists created | Cause: Partial lists are available more than twice in p0978. After the second 0, all must be 0. Alarm value (r2124, interpret decimal): Index of p0978 under which the illegal value is located. Remedy: Set p0009 to 1 and change p0978: Rules:
|
| A01324 Topology: Dummy drive object number incorrectly created | Cause: In p0978, dummy drive object numbers (255) are only permitted in the first partial list. Alarm value (r2124, interpret decimal): Index of p0978 under which the illegal value is located. Remedy: Set p0009 to 1 and change p0978: Rules:
|
| F01325 Topology: Component number not present in target topology | Cause: The component configured in a parameter (e.g. p0121, p0131, etc.) is not present in the target topology. Alarm value (r2124, interpret decimal): Configured component number that is not present in target topology. Remedy: Establish topology and DO configuration consistency. |
| A01330 Topology: Quick commissioning not possible | Cause: Unable to carry out a quick commissioning. The existing actual topology does not fulfill the requirements. Alarm value (r2124, interpret hexadecimal): (A detailed list of fault cause codes and supplementary information follows) Remedy: Note: Connection type and connection number are described in F01375. See also: p0097 (Select drive object type), r0098 (Actual device topology), p0099 (Device target topology)
Re aa = 06 hex = 6 dec and bb = 01 hex = 1 dec: Correct the order number when commissioning using the commissioning software. See also: p0097 (Select drive object type), r0098 (Actual device topology), p0099 (Device target topology) |
| 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): (A detailed list of fault cause codes follows) Remedy:
(Additional remedies for specific fault values follow) |
| 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. Note: Pulse enable is prevented. Remedy: Remove the illegal components and restart the system. |
| F01355 Topology: Actual topology changed | Cause: The device target topology (p0099) does not correspond to the device actual topology (r0098). The fault only occurs if the topology was commissioned using the automatic internal device mechanism and not using the commissioning software. Fault value (r0949, interpret decimal): 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:
Notice: Topology changes that result in this fault being generated cannot be accepted by the automatic function in the device, but must be transferred using the commissioning software and parameter download. |
| 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 the component at which the defective component is connected yy = component number of the component at which the defective component is connected xx = fault cause xx = 1: Component at this Control Unit not permissible. xx = 2: component with communication defect. Note: Pulse enable is withdrawn and prevented. Remedy: Replace the defective component and restart the system. |
| F01357 Topology: Two Control Units identified on the DRIVE-CLIQ line | Cause: In the actual topology, 2 Control Units are connected with one another through DRIVE-CLiQ. As standard, this is not permitted. It is only permitted, if the OA application OALINK is already installed on both Control Units. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = connection number of the Control Unit at which the second Control Unit is connected xx = component number of the Control Unit at which the second Control Unit is connected Note: Pulse enable is withdrawn and prevented. Remedy:
|
| A01358 Topology: Line termination not available | Cause: At least one line with distributed drives is not terminated. The last participant on the line must be terminated with a line termination connector. This therefore ensures the degree of protection of the distributed drives. Fault value (r0949, interpret hexadecimal): zzyyxx hex: zz = connection number of the distributed drive where there is no terminating connector yy = component number xx = CU connection number Remedy: Install the line terminating connector for the last distributed drive. |
| F01359 Topology: DRIVE-CLiQ performance not sufficient | Cause: The DRIVE-CLiQ performance is not sufficient at one line in order to identify an inserted component. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
Note: For this topology, do not withdraw and insert components in operation. |
| F01360 Topology: Actual topology not permissible | Cause: The detected actual topology is not permissible. Fault value (r0949, interpret hexadecimal): (A detailed list of fault cause codes follows) Note: The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled. Remedy: (Remedies for specific fault causes are listed) |
| A01361 Topology: Actual topology contains SINUMERIK and SIMOTION components | Cause: The detected actual topology contains SINUMERIK and SIMOTION components. The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled. Alarm value (r2124, interpret hexadecimal): (Alarm value details follow) Remedy: Re alarm value = 1: Replace all NX10 or NX15 by a CX32. Re alarm value = 2: Replace all CX32 by an NX10 or NX15. |
| A01362 Topology: Topology rule(s) broken | Cause: At least one topology rule for the SINAMICS S120 Combi has been broken. In the event of a fault, the ramping up of the drive system is aborted and closed-loop drive control is not enabled. Alarm value (r2124, interpret decimal): The alarm value indicates which rule has been violated. (A list of 13 broken rules follows) Remedy: Evaluate the alarm value and ensure compliance with the corresponding topology rule(s). |
| F01375 Topology: Connection duplicated between two components | Cause: When checking the actual topology, a ring-type connection was detected. The fault value describes a component contained in the ring. Fault value (r0949, interpret hexadecimal): (Fault value details follow, including Component class and Connection number descriptions) Remedy: Output the fault value and remove the specified connection. Note: Under “Topology –> Topology view” the commissioning software where relevant offers improved diagnostics capability (e.g. setpoint/actual value comparison). |
| F01380 Topology: Actual topology EEPROM defective | Cause: When detecting the actual topology, a component with a defective EEPROM was detected. Fault value (r0949, interpret hexadecimal): bbbbaaaa hex: bbbb = reserved aaaa = preliminary component number of the defective components Remedy: Output the fault value and remove the defected component. |
| 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, interpret hexadecimal): (Alarm value details describe the component and connection) 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, interpret hexadecimal): (Alarm value details describe the component and connection) 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. Alarm value (r2124, interpret hexadecimal): (Alarm value details describe the component and connection) 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. Alarm value (r2124, interpret hexadecimal): (Alarm value details describe the component and connection) 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. Alarm value (r2124, interpret hexadecimal): (Alarm value details describe the component and connection) 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. Alarm value (r2124, interpret hexadecimal): (Alarm value details describe the component and connection) 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. Alarm value (r2124, interpret hexadecimal): (Alarm value details describe the component and connection) 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. Alarm value (r2124, interpret hexadecimal): (Alarm value details describe the component and connection) Remedy: Adapting topologies:
|
| A01420 Topology: Component different | Cause: The topology comparison has detected differences in the actual and target topologies in the electronic rating plate. Alarm value (r2124, interpret hexadecimal): (Alarm value details describe the component, classes, and difference) Remedy: Adapting topologies:
Topology comparison – if required, adapt the comparison level:
|
| 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. Alarm value (r2124, interpret hexadecimal): (Alarm value details describe the component and number of differences) Remedy: Adapting topologies:
(Additional remedies for specific byte values follow) |
| A01428 Topology: Incorrect connection used | Cause: The topology comparison has detected differences in the actual and target topologies in relation to one component. For a component, another connection was used. The different connections of a component are described in the alarm value. Alarm value (r2124, interpret hexadecimal): (Alarm value details describe the component and connections) Remedy: Adapting topologies:
|
| F01451 Topology: Target topology is invalid | Cause: An error was detected in the target topology. The target topology is invalid. Fault value (r0949, interpret hexadecimal): (A detailed list of fault cause codes follows) Remedy: Reload the target topology using the commissioning software. |
| A01481 (N) Topology: power unit not inserted | Cause: The topology comparison has detected a power unit that is missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): (Alarm value details describe the component and connection) Remedy: Adapting topologies:
Check the hardware:
|
| A01482 Topology: Sensor Module not inserted | Cause: The topology comparison has detected a Sensor Module that is missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): (Alarm value details describe the component and connection) Remedy: Adapting topologies:
Check the hardware:
|
| A01484 Topology: DRIVE-CLiQ Hub Module not inserted | Cause: The topology comparison has detected a DRIVE-CLiQ Hub Module missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: dd = connection number (%4) cc = component number (%3) bb = component class (% 2) aa = component number of the component that has not been inserted (% 1) 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 software where relevant offers improved diagnostics capability (e.g. setpoint/actual value comparison). |
| A01485 Topology: Controller Extension not inserted | Cause: The topology comparison has detected a Control Extension (CX32) missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: dd = connection number (%4) cc = component number (%3) bb = component class (% 2) aa = component number 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 software where relevant offers improved diagnostics capability (e.g. setpoint/actual value comparison). |
| A01486 Topology: DRIVE-CLiQ component not inserted | Cause: The topology comparison has detected a DRIVE-CLiQ component missing in the actual topology with respect to the target topology. Alarm value (r2124, interpret hexadecimal): ddccbbaa hex: 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 software where relevant offers improved diagnostics capability (e.g. setpoint/actual value comparison). |
| 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 software where relevant offers improved diagnostics capability (e.g. setpoint/actual value comparison). |
| A01489 Topology: Motor with DRIVE-CLiQ not inserted | 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 software where relevant offers improved diagnostics capability (e.g. setpoint/actual value comparison). |
| F01505 (A) BICO: Interconnection cannot be established | Cause: A PROFIdrive telegram has been set (p0922). An interconnection contained in the telegram was not able to be established. Fault value (r0949, interpret decimal): Parameter receiver that should be changed. Remedy: Establish another interconnection. |
| F01506 (A) BICO: No standard telegram | Cause: The standard telegram in p0922 is not maintained and therefore p0922 is set to 999. Fault value (r0949, interpret decimal): BICO parameter for which the write attempt was unsuccessful. Remedy: Again set the required standard telegram (p0922). |
| 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 de-activated 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 de-activating a drive object was exceeded. When de-activating 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: The alarm automatically disappears as soon as no BICO interconnection (value = 0) is entered in r9498[29] and r9499[29]. 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: Interconnect this connector input with a connector output having a float data type. |
| F01511 (A) BICO: Interconnection with different scalings | Cause: The requested BICO interconnection was established. However, a conversion is made between the BICO output and BICO input using the reference values. – 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. p2002: contains the reference value for current p2001: contains the reference value for voltage 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: Apply scaling or check the transfer value. |
| 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. 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: If required, return the master control and repeat the operation. |
| A01590 (F) Drive: Motor maintenance interval expired | Cause: The selected service/maintenance interval for this motor was reached. Alarm value (r2124, interpret decimal): Motor data set number. See also: p0650 (Actual motor operating hours), p0651 (Motor operating hours maintenance interval) Remedy: carry out service/maintenance and reset the service/maintenance interval (p0651). |
| F01600 SI P1 (CU): STOP A initiated | Cause: The drive-integrated “Safety Integrated” function on the Control Unit (CU) has detected a fault and initiated a STOP A (STO via the safety shutdown path of the Control Unit). – forced checking procedure of the safety shutdown path of the Control Unit unsuccessful. – subsequent response to fault F01611 (defect in a monitoring channel). Fault value (r0949, interpret decimal): (A list of fault value codes follows) Remedy:
For fault value = 9999:
|
| F01611 (A) SI P1 (CU): Defect in a monitoring channel | Cause: The drive-integrated “Safety Integrated” function on processor 1 has detected a fault in the crosswise data comparison between the two monitoring channels and has initiated a STOP F. As a result of this fault, after the parameterized transition has expired (p9658), fault F01600 (SI CU: STOP A initiated) is output. Fault value (r0949, interpret decimal): (A very detailed list of fault value codes from 0 to 6166 follows) Remedy: (A very detailed list of remedies corresponding to the fault values is provided across pages 59 and 60. This includes carrying out POWER ON, upgrading software, checking connections, and correcting parameter settings.) |
| F01612 SI P1 (CU): STO inputs for power units connected in parallel different | Cause: The drive-integrated “Safety Integrated” function on the Control Unit (CU) has identified different states of the AND’ed STO inputs for power units connected in parallel and has initiated a STOP F. As a result of this fault, after the parameterized transition has expired (p9658), fault F01600 (SI CU: STOP A initiated) is output. Fault value (r0949, interpret binary): Binary image of the digital inputs of the Control Unit that are used as signal source for the function “Safe Torque Off”. Remedy: – check the tolerance time SGE changeover and if required, increase the value (p9650). – check the wiring of the safety-relevant inputs (SGE) (contact problems). |
| N01620 (F, A) SI P1 (CU): Safe Torque Off active | Cause: The “Safe Torque Off” (STO) function of the basic functions has been selected on the Control Unit (CU) using the input terminal and is active. Note: – This message does not result in a safety stop response. – This message is not output when STO is selected using the Extended Functions. Remedy: Not necessary. |
| N01621 (F, A) SI P1 (CU): Safe Stop 1 active | Cause: The “Safe Stop 1” (SS1) function has been selected on the Control Unit (CU) and is active. Note: This message does not result in a safety stop response. Remedy: Not necessary. |
| F01625 SI P1 (CU): Sign-of-life error in safety data | Cause: The drive-integrated “Safety Integrated” function on the Control Unit (CU) has detected an error in the sign-of-life of the safety data between the two monitoring channels and has initiated a STOP A. – there is either a DRIVE-CLiQ communication error or communication has failed. – a time slice overflow of the safety software has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01630 SI P1 (CU): Brake control error | Cause: The drive-integrated “Safety Integrated” function on the Control Unit (CU) has detected a brake control fault and initiated a STOP A. – motor cable is not shielded correctly. – defect in control circuit of the Motor Module. Fault value (r0949, interpret decimal): (A list of fault values from 10 to 90 follows, indicating issues like “open holding brake”, “brake open”, etc.) Remedy:
Operation with Safe Brake Module or Safe Brake Adapter:
|
| A01631 (F, N) SI P1 (CU): motor holding brake/SBC configuration not practical | Cause: A configuration of motor holding brake and SBC was detected that is not practical. The following configurations can result in this message: – “No motor holding brake available” (p1215 = 0) and “SBC” enabled (p9602 = 1). – “Motor holding brake just like the sequence control, connection via BICO” (p1215 = 3) and “SBC” enabled (p9602 = 1). Remedy: Check the parameterization of the motor holding brake and SBC and correct. See also: p1215 (Motor holding brake configuration), p9602 (SI enable Safe Brake Control (Control Unit)), p9802 (SI enable Safe Brake Control (Motor Module)) |
| F01632 SI P1 (CU): shutoff valve control/feedback signal error | Cause: The drive-integrated “Safety Integrated” function on the Control Unit (monitoring channel 1) has detected a fault for the control/feedback signal of the shutoff valve and initiated a STOP A. Possible causes: (A list of possible causes including connection issues, incorrect settings, and defective components follows). Fault value (r0949, interpret decimal): (A list of fault values from 10 to 80 follows, indicating issues like “Open shutoff valve” operation.) Remedy:
|
| F01640 SI P1 (CU): component replacement identified and acknowledgment/save required | Cause: The “Safety Integrated” function integrated in the drive has identified that a component has been replaced. It is no longer possible to operate the drive. When safety functions are active, after a component has been replaced it is necessary to carry out a partial acceptance test. Fault value (r0949, interpret binary): (A list of bits indicates which component has been replaced, e.g., Control Unit, Motor Module, etc.) Remedy:
Note: In addition to the fault, diagnostics bits r9776.2 and r9776.3 are set. |
| F01641 SI P1 (CU): component replacement identified and save required | Cause: The “Safety Integrated” function integrated in the drive has identified that a component has been replaced (e.g., Control Unit, Motor/Hydraulic Module, Power Module, Sensor Module, TM54F). No additional fault response is initiated, therefore operation of the particular drive is not restricted. When safety functions are active, after a component has been replaced it is necessary to carry out a partial acceptance test. Remedy:
See also: r9776 (SI diagnostics) |
| F01649 SI P1 (CU): Internal software error | Cause: An internal error in the Safety Integrated software on the Control Unit has occurred. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01650 SI P1 (CU): Acceptance test required | Cause: The drive-integrated “Safety Integrated” function on monitoring channel 1 requires an acceptance test. Note: This fault results in a STOP A that can be acknowledged. Fault value (r0949, interpret decimal): (A detailed list of fault value codes from 130 to 9999 follows, indicating reasons like first commissioning, checksum errors, parameter changes, etc.) Remedy: (A detailed list of remedies corresponding to the fault values is provided across pages 70 and 71. This includes carrying out safety commissioning, checking checksums, performing acceptance tests, and generating reports.) |
| F01650 SI P1 (CU): Acceptance test required | Cause: The drive-integrated “Safety Integrated” function on monitoring channel 1 requires an acceptance test. Note: This fault results in a STOP A that can be acknowledged. Fault value (r0949, interpret decimal): A detailed list of fault value codes from 130 to 9999 follows, indicating reasons like first commissioning, checksum errors, parameter changes, etc. Remedy: A detailed list of remedies corresponding to the fault values is provided:
|
| F01651 SI P1 (CU): Synchronization safety time slices unsuccessful | Cause: The “Safety Integrated” function requires a synchronization of the safety time slices between the two monitoring channels and between the Control Unit and the higher-level control. This synchronization routine was unsuccessful. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret decimal): 121: with SINUMERIK Safety Integrated enabled, a drive-side warm restart was performed on the CU/NX or the function “restore factory setting” was selected. 150: fault in the synchronization to the PROFIBUS master. All other values: only for internal Siemens troubleshooting. Remedy:
|
| F01652 SI P1 (CU): Illegal monitoring clock cycle | Cause: One of the Safety Integrated monitoring clock cycles is not permissible. – the monitoring clock cycle integrated in the drive cannot be maintained due to the communication conditions required in the system. – the monitoring clock cycle for safe motion monitoring functions is not permissible (p9500). – the actual value sensing clock cycle for safe motion monitoring functions is not permissible (p9511). – The sampling time for the current controller (p0112, p0115[0]) cannot be supported. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret decimal): A detailed list of fault values from 100 to 202 indicates specific clock cycle inconsistencies. Remedy: A detailed list of remedies is provided for each fault value, which includes:
|
| F01653 SI P1 (CU): PROFIBUS/PROFINET configuration error | Cause: There is a PROFIBUS/PROFINET configuration error for using Safety Integrated monitoring functions with a higher-level control (SINUMERIK or F-PLC). Note: For safety functions that have been enabled, this fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret decimal): A detailed list of fault values from 200 to 340 indicates specific configuration issues with safety slots for receive/send data. Remedy: The following generally applies:
For fault value = 250:
Re fault value = 231, 331:
|
| A01654 (F) SI P1 (CU): Deviating PROFIsafe configuration | Cause: The configuration of a PROFIsafe telegram in the higher-level control (F-PLC) does not match the parameterization in the drive. Note: This message does not result in a safety stop response. Alarm value (r2124, interpret decimal): 1: A PROFIsafe telegram is configured in the higher-level control, however PROFIsafe is not enabled in the drive (p9601.3). 2: PROFIsafe is parameterized in the drive; however, a PROFIsafe telegram has not been configured in the higher-level control. Remedy: The following generally applies:
Re alarm value = 1:
Re alarm value = 2:
|
| F01655 SI P1 (CU): Align monitoring functions | Cause: An error has occurred when aligning the Safety Integrated monitoring functions of both monitoring channels. No common set of supported SI monitoring functions was able to be determined. – there is either a DRIVE-CLiQ communication error or communication has failed. – Safety Integrated software releases on the Control Unit and Motor Module/Hydraulic Module are not compatible with one another. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01656 SI CU: Parameter monitoring channel 2 error | Cause: When accessing the Safety Integrated parameters for monitoring channel 2 in the non-volatile memory, an error has occurred. Note: This fault results in a STOP A that can be acknowledged. Fault value (r0949, interpret decimal): 129: safety parameters for monitoring channel 2 corrupted. 131: Internal Motor Module/Hydraulic Module software error. 132: Communication errors when uploading or downloading the safety parameters for monitoring channel 2. 255: Internal software error on the Control Unit. Remedy:
For fault value = 129:
For fault value = 132:
|
| F01657 SI P1 (CU): PROFIsafe telegram number invalid | Cause: The PROFIsafe telegram number set in p9611 is not valid. When PROFIsafe is enabled (p9601.3 = 1), then a telegram number greater than zero must be entered in p9611. Note: This fault does not result in a safety stop response. Remedy: Check the telegram number setting (p9611). |
| F01658 SI P1 (CU): PROFIsafe telegram number differ | Cause: The PROFIsafe telegram number is set differently in p9611 and p60022. For p9611 not equal to 998, the telegram number must be identically set in both parameters. As a result of the compatibility to firmware versions < 4.5, then only the values 0 and 30 are permitted in p60022. Note: This fault does not result in a safety stop response. Remedy: Match the telegram number in both parameters so that they are the same (p9611, p60022). |
| F01659 SI P1 (CU): Write request for parameter rejected | Cause: The write request for one or several Safety Integrated parameters on the Control Unit (CU) was rejected. Note: This fault does not result in a safety stop response. Fault value (r0949, interpret decimal): A detailed list of fault values from 1 to 33 indicates rejected attempts to enable unsupported functions or invalid configurations. Remedy: A detailed list of remedies for each fault value is provided, including:
|
| F01660 SI P1 (CU): Safety-related functions not supported | Cause: The Motor Module/Hydraulic Module does not support the safety-related functions (e.g. the version is not correct). Safety Integrated cannot be commissioned. Note: This fault does not result in a safety stop response. Remedy:
|
| F01661 SI P1 (CU): Simulation of the safety inputs active | Cause: The simulation of the digital inputs of the Control Unit (p0795) is active. It is not permissible that safety inputs are simulated. Fault value (r0949, interpret binary): The displayed bits indicate which digital inputs must not be simulated. Remedy:
|
| F01663 SI P1 (CU): Copying the SI parameters rejected | Cause: In p9700, the value 87 or 208 is saved or was entered offline. This is the reason that when booting, an attempt is made to copy SI parameters from monitoring channel 1 to monitoring channel 2. However, no safety-relevant function has been selected on monitoring channel 1 (p9501 = 0, p9601 = 0). Copying was rejected for safety reasons. Note: This fault does not result in a safety stop response. Remedy:
|
| F01664 SI P1 (CU): No automatic firmware update | Cause: During booting, the system detected that the “Firmware update automatic” function (p7826 = 1) was not activated. This function must be activated for automatic firmware updates/downgrades to prevent impermissible version combinations when safety functions are enabled. Note: This fault does not result in a safety stop response. Remedy: When safety functions are enabled (p9501 <> 0 and/or p9601 <> 0):
When de-activating the safety functions (p9501 = 0, p9601 = 0), the fault can be acknowledged after exiting the safety commissioning mode. |
| F01665 SI P1 (CU): System is defective | Cause: A system defect was detected before the last boot or in the actual one. The system might have been rebooted (reset). Fault value (r0949, interpret hexadecimal): 200000 hex, 400000 hex, 8000yy hex (yy any): Fault in the actual booting/operation. 800004 hex: Parameters p9500/p9300 are, under certain circumstances, not the same. In addition, Safety message C01711/C30711 is displayed. Remedy:
Re fault value = 200000 hex, 400000 hex, 8000yy hex (yy any):
Re fault value = 800004 hex:
|
| A01666 (F) SI Motion P1 (CU): Steady-state (static) 1 signal at the F-DI for safe acknowledgment | Cause: A logical 1 signal is present at the F-DI configured in p10006 for more than 10 seconds. If, at the F-DI no acknowledgment was performed for safe acknowledgment, then a steady-state logical 0 signal must be present. This avoids unintentional safety-relevant acknowledgement if a wire breaks or one of the two digital inputs bounces. Remedy: Set the fail-safe digital input (F-DI) to a logical 0 signal (p10006). |
| A01669 (F, N) SI Motion: Unfavorable combination of motor and power unit | Cause: The combination of motor and power unit used is not suitable for using safe motion monitoring functions without an encoder. The ratio between the power unit rated current (r0207[0]) and rated motor current (p0305) is greater than 5. Alarm value (r2124, interpret decimal): Number of the motor data set, which caused the fault. Notice: If this alarm is not observed, then message C01711 or C30711 – with the value 1041 … 1044 can sporadically occur. Remedy: Use a suitable power unit with a lower power rating or a motor with a higher power rating. |
| F01670 SI Motion: Invalid parameterization Sensor Module | Cause: The parameterization of a Sensor Module used for Safety Integrated is not permissible. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret decimal): A detailed list of fault values from 1 to 13 indicates specific parameterization issues with the encoder. Remedy: A detailed list of remedies is provided for each fault value, including:
|
| F01671 SI Motion: Parameterization encoder error | Cause: The parameterization of the encoder used by Safety Integrated is different to the parameterization of the standard encoder. Note: This fault does not result in a safety stop response. Fault value (r0949, interpret decimal): Parameter number of the non-corresponding safety parameter. Remedy: Align the encoder parameterization between the safety encoder and the standard encoder. |
| F01672 SI P1 (CU): Motor Module software/hardware incompatible | Cause: The existing Motor Module/Hydraulic Module software does not support safe motion monitoring, is not compatible with the Control Unit software, or there is a communications error. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret decimal): A detailed list of fault values from 1 to 13 indicates the specific incompatibility. Remedy:
|
| F01673 SI Motion: Sensor Module software/hardware incompatible | Cause: The existing Sensor Module software and/or hardware does not support the safe motion monitoring function with the higher-level control. Note: This fault does not result in a safety stop response. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01674 SI Motion P1 (CU): Safety function not supported by PROFIsafe telegram | Cause: The monitoring function enabled in p9501 and p9601 is not supported by the currently set PROFIsafe telegram (p9611). Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret bitwise binary): Bit 24 = 1: Transfer SLS (SG) limit value via PROFIsafe not supported. Bit 25 = 1: Transfer safe position via PROFIsafe is not supported. Bit 26 = 1: Gearbox stage switchover via PROFIsafe is not supported. Remedy:
|
| F01679 SI CU: Safety parameter settings and topology changed, warm restart/POWER ON required | Cause: Safety parameters have been changed; these will only take effect following a warm restart or POWER ON (see alarm A01693). A partial power up (boot) with modified configuration was then performed. Remedy:
|
| F01680 SI Motion P1 (CU): Checksum error safety monitoring functions | Cause: The actual checksum calculated by the drive and entered in r9728 via the safety-relevant parameters does not match the reference checksum saved in p9729 at the last machine acceptance. Safety-relevant parameters have been changed or a fault is present. Note: This fault results in a STOP A that can be acknowledged. Fault value (r0949, interpret decimal): 0: Checksum error for SI parameters for motion monitoring. 1: Checksum error for SI parameters for actual values. 2: Checksum error for SI parameters for component assignment. Remedy:
|
| F01681 SI Motion P1 (CU): Incorrect parameter value | Cause: The parameter cannot be parameterized with this value. Note: This message does not result in a safety stop response. Fault value (r0949, interpret decimal): yyyyxxxx dec: yyyy = supplementary information, xxxx = parameter A detailed list of fault conditions for various parameters (9500, 9501, 9505, 9506, 9511, 9522, 9534, 9535, 9544, 9547, 9573, 9585, 9601) is provided, indicating invalid settings or combinations. Remedy: A detailed list of remedies corresponding to the specific fault value (xxxx and yyyy) is provided:
|
| F01682 SI Motion P1 (CU): Monitoring function not supported | Cause: The monitoring function enabled in p9501, p9601, p9801, p9307 or p9507 is not supported in this firmware version. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret decimal): A detailed list of fault values indicates the specific unsupported function (e.g., SLP, SCA, SLS override, F-DI in PROFIsafe, encoderless functions, etc.). Remedy:
|
| F01683 SI Motion P1 (CU): SOS/SLS enable missing | Cause: The safety-relevant basic function “SOS/SLS” is not enabled in p9501 although other safety-relevant monitoring functions are enabled. Note: This fault does not result in a safety stop response. Remedy: Enable the function “SOS/SLS” (p9501.0) and carry out a POWER ON. |
| F01684 SI Motion P1 (CU): Safely limited position limit values interchanged | Cause: For the function “Safely Limited Position” (SLP), a lower value is in p9534 than in p9535. Note: This fault does not result in a safety stop response. Fault value (r0949, interpret decimal): 1: Limit values SLP1 interchanged. 2: Limit values SLP2 interchanged. Remedy:
|
| F01685 SI Motion P1 (CU): Safely-limited speed limit value too high | Cause: The limit value for the function “Safely-Limited Speed” (SLS) is greater than the speed that corresponds to an encoder limit frequency of 500 kHz. Note: This fault does not result in a safety stop response. Fault value (r0949, interpret decimal): Maximum permissible speed. Remedy: Correct the limit values for SLS and carry out a POWER ON. |
| F01686 SI Motion: Illegal parameterization cam position | Cause: At least one enabled “Safety Cam” (SCA) is parameterized in p9536 or p9537 too close to the tolerance range around the modulo position. The conditions for cam length and distance between cams are not met. Note: This fault does not result in a safety stop response. Fault value (r0949, interpret decimal): Number of the “Safe Cam” with an illegal position. Remedy: Correct the cam position and carry out a POWER ON. |
| F01687 SI Motion: Illegal parameterization modulo value SCA (SN) | Cause: The parameterized modulo value for the “Safe Cam” (SCA) function is not a multiple of 360 000 mDegrees. Note: This fault does not result in a safety stop response. Remedy: Correct the modulo value for SCA and carry out a POWER ON. |
| F01688 SI Motion CU: Actual value synchronization not permissible | Cause: – It is not permissible to enable actual value synchronization for a 1-encoder system. – It is not permissible to simultaneously enable actual value synchronization and a monitoring function with absolute reference (SCA/SLP). – It is not permissible to simultaneously enable actual value synchronization and safe position via PROFIsafe. Note: This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| C01689 SI Motion: Axis re-configured | Cause: The axis configuration was changed (e.g. changeover between linear axis and rotary axis). Parameter p0108.13 is internally set to the correct value. Note: This fault does not result in a safety stop response. Fault value (r0949, interpret decimal): Parameter number of parameter that initiated the change. Remedy: The following should be carried out after the changeover:
Once the Control Unit has been switched on, safety message F01680 or F30680 indicates that the checksums have changed. The following must, therefore, be carried out:
|
| F01690 SI Motion: Data save problem for the NVRAM | Cause: There is not sufficient memory space in the NVRAM on the drive to save parameters r9781 and r9782 (safety logbook). Note: This fault does not result in a safety stop response. Fault value (r0949, interpret decimal): 0: There is no physical NVRAM available in the drive. 1: There is no longer any free memory space in the NVRAM. Remedy:
|
| A01691 (F) SI Motion: Ti and To unsuitable for DP cycle | Cause: The configured times for PROFIBUS communication are not permitted and the DP cycle is used as the actual value acquisition cycle for the safe movement monitoring functions. Isochronous PROFIBUS: The sum of Ti and To is too high for the selected DP cycle. No isochronous PROFIBUS: The DP clock cycle must be at least 4x the current controller clock cycle. Notice: If this alarm is not observed, then message C01711 or C30711 may sporadically occur. Remedy:
|
| F01692 SI Motion P1 (CU): Parameter value not permitted for encoderless | Cause: The parameter cannot be set to this value if encoderless motion monitoring functions have been selected in p9506. Note: This fault does not result in a safety stop response. Fault value (r0949, interpret decimal): Parameter number with the incorrect value. Remedy:
|
A01693 (F) SI P1 (CU): Safety parameter setting changed, wam restart/POWER ON required | Cause: Safety parameters have been changed; these will only take effect following a warm restart or POWER ON. All changed parameters of the safety motion monitoring functions will only take effect following a warm restart or POWER ON. Alarm value (r2124, interpret decimal): Parameter number of the safety parameter which has changed, necessitating a warm restart or POWER ON. Remedy:
Note: Before performing an acceptance test, a POWER ON must be carried out for all components. |
F01694 (A) SI Motion CU: Firmware version Motor Module/Hydraulic Module older Control Unit | Cause: The firmware version of the Motor Module/Hydraulic Module is older than the version of the Control Unit. It is possible that safety functions are not available (r9771/r9871). This message does not result in a safety stop response. This message can also occur, if after an automatic firmware update, a POWER ON was not carried out (Alarm A01007). Remedy: Upgrade the firmware of the Motor Module/Hydraulic Module to a later version. |
A01695 (F) SI Motion: Sensor Module was replaced | Cause: A Sensor Module, which is used for safe motion monitoring functions, was replaced. The hardware replacement must be acknowledged. An acceptance test must be subsequently performed. This message does not result in a safety stop response. Remedy: Carry out the following steps using the STARTER commissioning software:
As an alternative, carry out the following steps in the expert list of the commissioning software:
Then carry out an acceptance test (refer to the Safety Integrated Function Manual). |
A01696 (F) SI Motion: Testing of the motion monitoring functions selected when booting | Cause: The test of the motion monitoring functions was already illegally active when booting. This is the reason that the test is only carried out again after selecting the forced checking procedure parameterized in p9705. This message does not result in a safety stop response. Remedy: De-select the forced checking procedure of the safety motion monitoring functions and then select again. The signal source for initiation is parameterized in binector input p9705. |
A01697 (F) SI Motion: Motion monitoring functions must be tested | Cause: The time set in p9559 for the forced checking procedure of the safety motion monitoring functions has been exceeded. A new test is required. After next selecting the forced checking procedure parameterized in p9705, the message is withdrawn and the monitoring time is reset. This message does not result in a safety stop response. As the shutdown paths are not automatically checked during booting, an alarm is always issued once booting is complete. The test must be performed within a defined, maximum time interval (p9559, maximum of 9000 hours) in order to comply with the requirements as laid down in the standards for timely fault detection and the conditions to calculate the failure rates of safety functions (PFH value). Remedy: Carry out the forced checking procedure of the safety motion monitoring functions. The signal source for initiation is parameterized in binector input p9705. |
A01698 (F) SI P1 (CU): Commissioning mode active | Cause: The commissioning of the “Safety Integrated” function is selected. This message is withdrawn after the safety functions have been commissioned. This message does not result in a safety stop response. In the safety commissioning mode, the “STO” function is internally selected. Remedy: Not necessary. |
A01699 (F) SI P1 (CU): Shutdown path must be tested | Cause: The time set in p9659 for the forced checking procedure of the safety shutdown paths has been exceeded. The safety shutdown paths must be re-tested. After the next time the “STO” function is de-selected, the message is withdrawn and the monitoring time is reset. This message does not result in a safety stop response. The test must be performed within a defined, maximum time interval (p9659, maximum of 9000 hours) in order to comply with the requirements as laid down in the standards for timely fault detection and the conditions to calculate the failure rates of safety functions (PFH value). Remedy: Select STO and then de-select again. |
C01700 SI Motion P1 (CU): STOP A initiated | Cause: The drive is stopped via a STOP A (STO via the safety shutdown path of the Control Unit). Possible causes: stop request from the second monitoring channel. STO not active after a parameterized time (p9557) after test stop selection. subsequent response to the message C01706 “SI Motion CU: SAM/SBR limit exceeded”. subsequent response to the message C01714 “SI Motion CU: Safely-Limited Speed exceeded”. subsequent response to the message C01701 “SI Motion CU: STOP B initiated”. subsequent response to the message C01715 “SI Motion CU: Safely-limited position exceeded”. subsequent response to the message C01716 “SI Motion CU: tolerance for safe motion direction exceeded”. Remedy:
|
C01701 SI Motion P1 (CU): STOP B initiated | Cause: The drive is stopped via a STOP B (braking along the OFF3 deceleration ramp). As a result of this fault, after the time parameterized in p9556 has expired, or the speed threshold parameterized in p9560 has been undershot, message C01700 “STOP A initiated” is output. Possible causes: stop request from the second monitoring channel. subsequent response to the message C01714 “SI Motion CU: Safely-Limited Speed exceeded”. subsequent response to the message C01711 “SI Motion CU: Defect in a monitoring channel”. subsequent response to the message C01707 “SI Motion CU: tolerance for safe operating stop exceeded”. subsequent response to the message C01715 “SI Motion CU: Safely-limited position exceeded”. subsequent response to the message C01716 “SI Motion CU: tolerance for safe motion direction exceeded”. Remedy:
|
C01706 SI Motion P1 (CU): SAM/SBR limit exceeded | Cause: Motion monitoring functions with encoder (p9506 = 0) or encoderless with set acceleration monitoring (SAM, p9506 = 3): after initiating STOP B (SS1) or STOP C (SS2), the speed has exceeded the selected tolerance. Motion monitoring functions encoderless with set brake ramp monitoring (SBR p9506 = 1): after initiating STOP B (SS1) or SLS changeover to the lower speed stage, the speed has exceeded the selected tolerance. The drive is shut down by the message C01700 “SI Motion: STOP A initiated”. Remedy: Check the braking behavior and, if necessary, adapt the parameterization of the parameter settings of the “SAM” or the “SBR” function. |
C01707 SI Motion P1 (CU): Tolerance for safe operating stop exceeded | Cause: The actual position has distanced itself further from the target position than the standstill tolerance. The drive is shut down by the message C01701 “SI Motion: STOP B initiated”. Remedy:
|
C01708 SI Motion P1 (CU): STOP C initiated | Cause: The drive is stopped via a STOP C (braking along the OFF3 deceleration ramp). “Safe Operating Stop” (SOS) is activated after the parameterized time has expired. Possible causes: stop request from the higher-level control. subsequent response to the message C01714 “SI Motion CU: Safely-Limited Speed exceeded”. subsequent response to the message C01715 “SI Motion CU: Safely-limited position exceeded”. subsequent response to the message C01716 “SI Motion CU: tolerance for safe motion direction exceeded”. Remedy:
|
C01709 SI Motion P1 (CU): STOP D initiated | Cause: The drive is stopped via a STOP D (braking along the path). “Safe Operating Stop” (SOS) is activated after the parameterized time has expired. Possible causes: stop request from the higher-level control. subsequent response to the message C01714 “SI Motion CU: Safely-Limited Speed exceeded”. subsequent response to the message C01715 “SI Motion CU: Safely-limited position exceeded”. subsequent response to the message C01716 “SI Motion CU: tolerance for safe motion direction exceeded”. Remedy:
|
C01710 SI Motion P1 (CU): STOP E initiated | Cause: The drive is stopped via a STOP E (retraction motion). “Safe Operating Stop” (SOS) is activated after the parameterized time has expired. Possible causes: stop request from the higher-level control. subsequent response to the message C01714 “SI Motion CU: Safely-Limited Speed exceeded”. subsequent response to the message C01715 “SI Motion CU: Safely-limited position exceeded”. subsequent response to the message C01716 “SI Motion CU: tolerance for safe motion direction exceeded”. Remedy:
|
C01711 SI Motion P1 (CU): Defect in a monitoring channel | Cause: When cross-comparing the two monitoring channels, the drive detected a difference between the input data or results of the monitoring functions and initiated a STOP F. One of the monitoring functions no longer reliably functions – i.e. safe operation is no longer possible. If at least one monitoring function is active, then after the parameterized timer has expired, the message C01701 “SI Motion: STOP B initiated” is output. Remedy: The following generally applies: The monitoring clock cycles in both channels and the axis types should be checked for equality and the same setting applied if necessary. If the error continues to be identified, increasing the monitoring clock cycles may resolve it. |
A01693 (F) SI P1 (CU): Safety parameter setting changed, wam restart/POWER ON required | Cause: Safety parameters have been changed; these will only take effect following a warm restart or POWER ON. All changed parameters of the safety motion monitoring functions will only take effect following a warm restart or POWER ON. Alarm value (r2124, interpret decimal): Parameter number of the safety parameter which has changed, necessitating a warm restart or POWER ON. Remedy:
Note: Before performing an acceptance test, a POWER ON must be carried out for all components. |
F01694 (A) SI Motion CU: Firmware version Motor Module/Hydraulic Module older Control Unit | Cause: The firmware version of the Motor Module/Hydraulic Module is older than the version of the Control Unit. It is possible that safety functions are not available (r9771/r9871). This message does not result in a safety stop response. This message can also occur, if after an automatic firmware update, a POWER ON was not carried out (Alarm A01007). Remedy: Upgrade the firmware of the Motor Module/Hydraulic Module to a later version. |
A01695 (F) SI Motion: Sensor Module was replaced | Cause: A Sensor Module, which is used for safe motion monitoring functions, was replaced. The hardware replacement must be acknowledged. An acceptance test must be subsequently performed. This message does not result in a safety stop response. Remedy: Carry out the following steps using the STARTER commissioning software:
As an alternative, carry out the following steps in the expert list of the commissioning software:
Then carry out an acceptance test (refer to the Safety Integrated Function Manual). |
A01696 (F) SI Motion: Testing of the motion monitoring functions selected when booting | Cause: The test of the motion monitoring functions was already illegally active when booting. This is the reason that the test is only carried out again after selecting the forced checking procedure parameterized in p9705. This message does not result in a safety stop response. Remedy: De-select the forced checking procedure of the safety motion monitoring functions and then select again. The signal source for initiation is parameterized in binector input p9705. |
A01697 (F) SI Motion: Motion monitoring functions must be tested | Cause: The time set in p9559 for the forced checking procedure of the safety motion monitoring functions has been exceeded. A new test is required. After next selecting the forced checking procedure parameterized in p9705, the message is withdrawn and the monitoring time is reset. This message does not result in a safety stop response. As the shutdown paths are not automatically checked during booting, an alarm is always issued once booting is complete. The test must be performed within a defined, maximum time interval (p9559, maximum of 9000 hours) in order to comply with the requirements as laid down in the standards for timely fault detection and the conditions to calculate the failure rates of safety functions (PFH value). Remedy: Carry out the forced checking procedure of the safety motion monitoring functions. The signal source for initiation is parameterized in binector input p9705. |
A01698 (F) SI P1 (CU): Commissioning mode active | Cause: The commissioning of the “Safety Integrated” function is selected. This message is withdrawn after the safety functions have been commissioned. This message does not result in a safety stop response. In the safety commissioning mode, the “STO” function is internally selected. Remedy: Not necessary. |
A01699 (F) SI P1 (CU): Shutdown path must be tested | Cause: The time set in p9659 for the forced checking procedure of the safety shutdown paths has been exceeded. The safety shutdown paths must be re-tested. After the next time the “STO” function is de-selected, the message is withdrawn and the monitoring time is reset. This message does not result in a safety stop response. The test must be performed within a defined, maximum time interval (p9659, maximum of 9000 hours) in order to comply with the requirements as laid down in the standards for timely fault detection and the conditions to calculate the failure rates of safety functions (PFH value). Remedy: Select STO and then de-select again. |
C01700 SI Motion P1 (CU): STOP A initiated | Cause: The drive is stopped via a STOP A (STO via the safety shutdown path of the Control Unit). Possible causes: stop request from the second monitoring channel. STO not active after a parameterized time (p9557) after test stop selection. subsequent response to the message C01706 “SI Motion CU: SAM/SBR limit exceeded”. subsequent response to the message C01714 “SI Motion CU: Safely-Limited Speed exceeded”. subsequent response to the message C01701 “SI Motion CU: STOP B initiated”. subsequent response to the message C01715 “SI Motion CU: Safely-limited position exceeded”. subsequent response to the message C01716 “SI Motion CU: tolerance for safe motion direction exceeded”. Remedy:
|
C01701 SI Motion P1 (CU): STOP B initiated | Cause: The drive is stopped via a STOP B (braking along the OFF3 deceleration ramp). As a result of this fault, after the time parameterized in p9556 has expired, or the speed threshold parameterized in p9560 has been undershot, message C01700 “STOP A initiated” is output. Possible causes: stop request from the second monitoring channel. subsequent response to the message C01714 “SI Motion CU: Safely-Limited Speed exceeded”. subsequent response to the message C01711 “SI Motion CU: Defect in a monitoring channel”. subsequent response to the message C01707 “SI Motion CU: tolerance for safe operating stop exceeded”. subsequent response to the message C01715 “SI Motion CU: Safely-limited position exceeded”. subsequent response to the message C01716 “SI Motion CU: tolerance for safe motion direction exceeded”. Remedy:
|
C01706 SI Motion P1 (CU): SAM/SBR limit exceeded | Cause: Motion monitoring functions with encoder (p9506 = 0) or encoderless with set acceleration monitoring (SAM, p9506 = 3): after initiating STOP B (SS1) or STOP C (SS2), the speed has exceeded the selected tolerance. Motion monitoring functions encoderless with set brake ramp monitoring (SBR p9506 = 1): after initiating STOP B (SS1) or SLS changeover to the lower speed stage, the speed has exceeded the selected tolerance. The drive is shut down by the message C01700 “SI Motion: STOP A initiated”. Remedy: Check the braking behavior and, if necessary, adapt the parameterization of the parameter settings of the “SAM” or the “SBR” function. |
C01707 SI Motion P1 (CU): Tolerance for safe operating stop exceeded | Cause: The actual position has distanced itself further from the target position than the standstill tolerance. The drive is shut down by the message C01701 “SI Motion: STOP B initiated”. Remedy:
|
C01708 SI Motion P1 (CU): STOP C initiated | Cause: The drive is stopped via a STOP C (braking along the OFF3 deceleration ramp). “Safe Operating Stop” (SOS) is activated after the parameterized time has expired. Possible causes: stop request from the higher-level control. subsequent response to the message C01714 “SI Motion CU: Safely-Limited Speed exceeded”. subsequent response to the message C01715 “SI Motion CU: Safely-limited position exceeded”. subsequent response to the message C01716 “SI Motion CU: tolerance for safe motion direction exceeded”. Remedy:
|
C01709 SI Motion P1 (CU): STOP D initiated | Cause: The drive is stopped via a STOP D (braking along the path). “Safe Operating Stop” (SOS) is activated after the parameterized time has expired. Possible causes: stop request from the higher-level control. subsequent response to the message C01714 “SI Motion CU: Safely-Limited Speed exceeded”. subsequent response to the message C01715 “SI Motion CU: Safely-limited position exceeded”. subsequent response to the message C01716 “SI Motion CU: tolerance for safe motion direction exceeded”. Remedy:
|
C01710 SI Motion P1 (CU): STOP E initiated | Cause: The drive is stopped via a STOP E (retraction motion). “Safe Operating Stop” (SOS) is activated after the parameterized time has expired. Possible causes: stop request from the higher-level control. subsequent response to the message C01714 “SI Motion CU: Safely-Limited Speed exceeded”. subsequent response to the message C01715 “SI Motion CU: Safely-limited position exceeded”. subsequent response to the message C01716 “SI Motion CU: tolerance for safe motion direction exceeded”. Remedy:
|
C01711 SI Motion P1 (CU): Defect in a monitoring channel | Cause: When cross-comparing the two monitoring channels, the drive detected a difference between the input data or results of the monitoring functions and initiated a STOP F. One of the monitoring functions no longer reliably functions – i.e. safe operation is no longer possible. If at least one monitoring function is active, then after the parameterized timer has expired, the message C01701 “SI Motion: STOP B initiated” is output. Remedy: The following generally applies: The monitoring clock cycles in both channels and the axis types should be checked for equality and the same setting applied if necessary. If the error continues to be identified, increasing the monitoring clock cycles may resolve it. |
C01712 SI Motion P1 (CU): Defect in F-IO processing | Cause: When cross checking and comparing the two monitoring channels, the drive detected a difference between parameters or results of the F-IO processing and initiated a STOP F. One of the monitoring functions no longer reliably functions – i.e. safe operation is no longer possible. The safety message C01711 with message value 0 is also displayed due to initiation of STOP F. If at least one monitoring function is active, the safety message C01701 “SI Motion: STOP B initiated” is output after the parameterized timer has expired. Remedy:
|
C01714 SI Motion P1 (CU): Safely-Limited Speed exceeded | Cause: The drive has moved faster than that specified by the velocity limit value (p9531). The drive is stopped as a result of the configured stop response (p9563). Remedy:
|
C01715 SI Motion P1 (CU): Safely-Limited Position exceeded | Cause: The axis has moved past a parameterized position that is monitored by the “SLP” function. Remedy:
|
C01716 SI Motion P1 (CU): Tolerance for safe motion direction exceeded | Cause: The tolerance for the “safe motion direction” function was exceeded. The drive is stopped as a result of the configured stop response (p9566). Remedy:
|
C01730 SI Motion P1 (CU): Reference block for dynamic safely limited speed invalid | Cause: The reference block transferred via PROFIsafe is negative. A reference block is used to generate a referred velocity limit value based on the reference quantity “Velocity limit value SLS1” (p9531[0]). The drive is stopped as a result of the configured stop response (p9563[0]). Remedy: In the PROFIsafe telegram, input data S_SLS_LIMIT_IST must be corrected. |
C01745 SI Motion P1 (CU): Checking braking torque for the brake test | Cause: The scaling of the brake torque for the brake test can be changed using parameter p2003. An acceptance test must be carried out again for the braking test. This determines whether the braking test is still carried out with the correct braking torque. Remedy:
|
C01750 SI Motion P1 (CU): Hardware fault safety-relevant encoder | Cause: The encoder that is used for the safety-relevant motion monitoring functions signals a hardware fault. Remedy:
|
C01751 SI Motion P1 (CU): Effectivity test fault safety-relevant encoder | Cause: The DRIVE-CLiQ encoder for safe motion monitoring signals an error for the effectivity tests. Remedy:
|
C01752 SI Motion P1 (CU): reference position invalid | Cause: The transferred reference position is invalid. Remedy:
|
C01770 SI Motion P1 (CU): Discrepancy error of the fail-safe inputs/outputs | Cause: The fail-safe digital inputs/digital outputs (F-DI/F-DO) show a different state longer than that parameterized in p10002 / p10102. Remedy:
|
A01772 SI Motion P1 (CU): Test stop failsafe inputs/outputs active | Cause: The test stop for the fail-safe digital inputs (F-DI) and/or fail-safe digital outputs (F-DO) is presently being performed. Remedy: The alarm disappears automatically after successfully ending or canceling (when a fault condition occurs) the test stop. |
F01773 SI Motion P1 (CU): Test stop error | Cause: A fault has occurred on the CU side during the test stop for the fail-safe outputs. Remedy: Check the wiring of the F-DOs and restart the test stop. |
A01774 SI Motion P1 (CU): Test stop necessary | Cause:
Remedy: Initiate test stop (BI: p10007). |
A01780 SBT When selected, the brake is closed | Cause: When selecting the brake test or starting the brake test, not all of the brakes were open. Remedy: Open all brakes and reselect the brake test (p10230.0, p10235.0). |
A01781 SBT brake opening time exceeded | Cause: The maximum time (11 s) to open the brake during the brake test was exceeded. Remedy:
|
A01782 SBT brake test incorrect control | Cause: The brake test was canceled as a result of incorrect control. Remedy:
|
A01783 SBT brake closing time exceeded | Cause: The maximum time (11 s) to close the brake during the brake test was exceeded. Remedy:
|
A01784 SBT brake test canceled with fault | Cause: The safe brake test was canceled as a result of a fault. Remedy:
|
A01785 SBT brake test configuration error | Cause: Error when parameterizing the brake test. In this configuration, the brake test cannot be started or cannot be started without error. Remedy: Check parameterization of the brake test. |
F01786 SCC signal source changed | Cause: The signal source in p10235 or p10250 was changed. The new signal source is effective immediately. Remedy: Acknowledge fault. |
F01787 SBT motor type different | Cause: The motor type set for the safe brake test (p10204) does not match the motor type set via the function module (r0108.12). Remedy: Adapt the motor type set for the safe brake test. |
A01788 Automatic test stop: wait for STO deselection via SMM | Cause: The STO function is selected via Safety Extended Functions or a safety message is present, which results in STO. The automatic test stop was not able to be carried out since the power up. The automatic test stop is performed after deselecting STO. Remedy: Deselect STO via Safety Extended Functions. Remove the cause of the safety message and acknowledge the fault. |
A01789 Automatic test stop and brake test not permitted when test stop is selected | Cause: The parameterization of the automatic test stop (p9507.6/p9307.6) and the brake test when a test stop is selected (p10203 = 2) is not permissible. The test stop is not automatically carried out when the powering up. Remedy:
|
A01794 (N) SI MOTION: check modulo value for safe position via PROFIsafe | Cause: When parameterizing the modulo value for safe position via PROFIsafe (p9505) the position actual value can jump when the range that can be represented overflows. Remedy: Correct the parameter assignment. Set p9505 to 2^n revolutions – and to complete revolutions (i.e. a multiple of 360 °). |
A01795 SI Motion P1 (CU): Wait time after exiting the safe pulse cancellation expired | Cause: After exiting safe pulse cancellation, within the wait time of 5 seconds, encoderless actual value sensing was not able to be activated for the extended functions without selection. A change is again made into the “safe pulse cancellation” state. Remedy:
|
A01796 (F, N) SI P1 (CU): Wait for communication | Cause: The drive waits for communication to be established to execute the safety-relevant motion monitoring functions. Remedy: If, after a longer period of time, the message is not automatically withdrawn, the following checks have to be made as appropriate:
|
C01797 SI Motion P1 (CU): Axis not safely referenced | Cause: The standstill position saved before powering down does not match the actual position determined at power-up. Remedy: If safe automatic referencing is not possible the user must issue a user agreement for the new position using the softkey. This mean that this position is then designated as safety-relevant. |
C01798 SI Motion P1 (CU): Test stop running | Cause: The test stop is active. Remedy: Not necessary. The message is withdrawn when the test stop is finished. |
C01799 SI Motion P1 (CU): Acceptance test mode active | Cause: The acceptance test mode is active. This means the setpoint velocity limiting is deactivated and standard limit switches are deactivated for function SLP (SE). Remedy: Not necessary. The message is withdrawn when exiting the acceptance test mode. |
F01800 DRIVE-CLiQ: Hardware/configuration error | Cause: A DRIVE-CLiQ connection fault has occurred. This can be due to incorrect structure, bus timing issues, loss of connection, or a defective component. Remedy:
|
A01839 DRIVE-CLiQ diagnostics: cable fault to the component | Cause: The fault counter (r9936[0…199]) to monitor the DRIVE-CLiQ connections/cables has been incremented. Remedy:
|
A01840 SMI: Component found without motor data | Cause: An SMI/DQI without motor data has been found (e.g. SMI installed as replacement part). Remedy:
|
A01900 (F) PB/PN: Configuration telegram error | Cause: A controller attempts to establish a connection using an incorrect configuring telegram. Reasons include more drive objects than configured, too many PZD data words, uneven bytes, synchronization data not accepted, unknown parameterizing block, illegal PROFIsafe configuration, etc. Remedy: Check the bus configuration on the master and the slave sides. Depending on the alarm value, check the drive object list (p0978), number of data words, settings in p8839 and p8815, configured drive objects, and PROFIsafe address (p9610) and telegram (p60022, p9611). |
A01902 PB/PN clock cycle synchronous operation parameterization not permissible | Cause: Parameterization for isochronous operation is not permissible. Reasons include bus cycle time out of range, not an integer multiple of the sampling time, incorrect timing for actual value sensing or setpoint acceptance. Remedy:
|
A01903 (F) COMM INT: Receive configuration data invalid | Cause: The drive unit did not accept the receive configuration data. Reasons include connection to more drive objects than configured, too many PZD words, uneven bytes, synchronization data not accepted, or a PROFIsafe parameter error. Remedy: Check the receive configuration data. Check the list of drive objects (p0978), the number of data words for input/output, and the set PROFIsafe address (p9610). |
F01910 (N, A) Fieldbus: setpoint timeout | Cause: The reception of setpoints from the fieldbus interface (onboard, PROFIBUS/PROFINET/USS) has been interrupted. This may be due to a bus connection interruption, the controller being switched off, or the controller being set to the STOP state. Remedy: Restore the bus connection and set the controller to RUN. |
F01911 (N, A) PB/PN clock cycle synchronous operation clock cycle failure | Cause: The global control telegram to synchronize the clock cycles has failed in cyclic operation. Remedy:
|
F01912 (N, A) PB/PN clock cycle synchronous operation sign-of-life failure | Cause: The maximum permissible number of errors in the controller sign-of-life (clock synchronous operation) has been exceeded in cyclic operation. Remedy:
|
F01913 (N, A) COMM INT: Monitoring time sign-of-life expired | Cause: The monitoring time for the sign-of-life counter has expired. The connection between the drive and the higher-level control (SIMOTION, SINUMERIK) has been interrupted. Remedy:
|
F01914 (N, A) COMM INT: Monitoring time configuration expired | Cause: The monitoring time for the configuration has expired. Remedy:
|
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 (clock-cycle synchronous operation) on the drive object 1 (Control Unit). For central measurements, synchronism with the central master is lost. Remedy: No remedy specified, only a note. |
A01920 (F) PROFIBUS: Interruption cyclic connection | Cause: The cyclic connection to the PROFIBUS master is interrupted. Remedy: Establish the PROFIBUS connection and activate the PROFIBUS master in the cyclic mode. |
A01921 (F) PROFIBUS: Receive setpoints after To | Cause: Output data of PROFIBUS master (setpoints) received at the incorrect instant in time within the PROFIBUS clock cycle. Remedy:
|
A01930 PB/PN current controller sampling time clock cycle synch. not equal | Cause: The current controller sampling time of all drives must be set the same for the clock cycle synchronous operation. Remedy: Set current controller sampling time to identical values (p0115[0]). |
A01931 PB/PN speed controller sampling time clock cycle synch. not equal | Cause: The speed controller sampling time of all drives must be set the same for the clock cycle synchronous operation. Remedy: Set the speed controller sampling times to identical values (p0115[1]). |
A01932 PB/PN clock cycle synchronization missing for DSC | Cause: There is no clock synchronization or clock synchronous sign of life and DSC is selected. Remedy: Set clock synchronization across the bus configuration and transfer clock synchronous sign-of-life. |
A01940 PB/PN clock cycle synchronism not reached | Cause: 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. 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: Check the master application and bus configuration. |
A01943 PB/PN clock cycle signal error when establishing bus communication | Cause: The bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing telegram. The global control telegram for synchronization is being irregularly received. Remedy:
|
A01944 PB/PN sign-of-life synchronism not reached | Cause: The bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing telegram. Synchronization with the master sign-of-life could not be completed because the sign-of-life is changing differently to how it was configured. Remedy:
|
A01945 PROFIBUS: Connection to the Publisher failed | Cause: For PROFIBUS peer-to-peer data transfer, the connection to at least one Publisher has failed. Remedy:
|
F01946 (A) PROFIBUS: Connection to the Publisher aborted | Cause: At this drive object, the connection to at least one Publisher for PROFIBUS peer-to-peer data transfer in cyclic operation has been aborted. Remedy:
|
F01950 (N, A) PB/PN clock cycle synchronous operation synchronization unsuccessful | Cause: Synchronization of the internal clock cycle to the global control telegram has failed. 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. Remedy: Upgrade the firmware of the component specified in the fault value. |
A01953 CU SYNC: Synchronization not completed | Cause: After the drive system is powered up, the synchronization between the basic clock cycle, DRIVE-CLiQ clock cycle and application clock cycle was started but was not completed within the selected time tolerance. Remedy: Carry out a POWER ON (power off/on) for all components. If the error occurs after the drive sampling times were changed, and if a Terminal Module 31 (TM31) is being used, the sampling times (p0115, p4099) should be set as integer multiples to the drive clock cycles (p0115). |
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 powered up, the synchronization between the basic clock cycle, DRIVE-CLiQ clock cycle and application clock cycle was started but was not completed within the selected time tolerance. Remedy: Carry out a POWER ON (power off/on) for all components of the DO. |
A01970 CBE25: Interruption cyclic connection | Cause: The cyclic connection to a PROFINET controller is interrupted. Remedy: Establish the PROFINET connection and activate the PROFINET controller in the cyclic mode. |
A01971 CBE25: Maximum number of controllers exceeded | Cause: A controller attempts to establish a connection to the drive, and as a consequence exceeds the permitted number of PROFINET connections. Remedy: Check the configuration of the PROFINET controllers as well as the p8929 setting. |
A01972 PROFINET: Second controller missing | Cause: The PROFINET function “Shared Device” has been activated (p8929 = 2). However, only the connection to a PROFINET controller is present. Remedy: Check the configuration of the PROFINET controllers as well as the p8929 setting. |
A01979 PROFINET: Internal cyclic data transfer error | Cause: The cyclic actual values and/or setpoints were not transferred within the specified times. Remedy: Correctly set T_io_input or T_io_output. |
A01980 PN: Interruption cyclic connection | Cause: The cyclic connection to a PROFINET controller is interrupted. Remedy: Establish the PROFINET connection and activate the PROFINET controller in the cyclic mode. |
A01981 PN: Maximum number of controllers exceeded | Cause: A controller attempts to establish a connection to the drive, and as a consequence exceeds the permitted number of PROFINET connections. Remedy: Check the configuration of the PROFINET controllers as well as the p8929 setting. |
A01982 PROFINET: Second controller missing | Cause: The PROFINET function “Shared Device” has been activated (p8929 = 2). However, only the connection to a PROFINET controller is present. Remedy: Check the configuration of the PROFINET controllers as well as the p8929 setting. |
A01989 PROFINET: Internal cyclic data transfer error | Cause: The cyclic actual values and/or setpoints were not transferred within the specified times. Remedy: Correctly set T_io_input or T_io_output. |
A01990 (F) USS: PZD configuration error | Cause: The configuration of the process data (PZD) for the USS protocol is incorrect. PZD amount (p2022) too great for the first drive object (p978[0]). Remedy: Check the amount of USS PZD (p2022) and the maximum PZD amount (r2050/p2051) for the first drive object (p0978[0]). |
A02000 Function generator: Start not possible | Cause: The function generator has already been started. Remedy: Stop the function generator and restart again if necessary. |
A02005 Function generator: Drive does not exist | Cause: The drive object specified for connection does not exist. Remedy: Use the existing drive object with the corresponding number. |
A02006 Function generator: No drive specified for connection | Cause: No drive specified for connection in p4815. Remedy: At least one drive to be connected must be specified in p4815. |
A02007 Function generator: Drive not SERVO / VECTOR / DC_CTRL | Cause: The drive object specified for connection is not a SERVO / VECTOR or DC_CTRL. Remedy: Use a SERVO / VECTOR / DC_CTRL drive object with the corresponding number. |
A02008 Function generator: Drive specified a multiple number of times | Cause: The drive object specified for connection is already specified. Remedy: Specify a different drive object. |
A02009 Function generator: Illegal mode | Cause: The set operating mode (p1300) of the drive object is not permissible when using the function generator. Remedy: Change the operating mode for this drive object to p1300 = 20 (encoderless speed control) or p1300 = 21 (speed control with encoder). |
A02010 Function generator: Speed setpoint from the drive is not zero | Cause: The speed setpoint of a drive selected for connection is greater than the value for the standstill detection set using p1226. Remedy: For all of the drives specified for connection, set the speed setpoints to zero. |
A02011 Function generator: The actual drive speed is not zero | Cause: The speed actual value of a drive selected for connection is greater than the value for the standstill detection set using p1226. Remedy: Set the relevant drives to zero speed before starting the function generator. |
A02015 Function generator: Drive enable signals missing | Cause: The master control and/or enable signals are missing to connect to the specified drive. Remedy: Fetch the master control to the specified drive object and set all enable signals. |
A02016 Function generator: Magnetizing running | Cause: Magnetizing has not yet been completed on a drive object specified for connection. Remedy: Wait for magnetizing of the motor (r0056.4). |
A02020 Function generator: Parameter cannot be changed | Cause: This parameter setting cannot be changed when the function generator is active (p4800 = 1). Remedy: – stop the function generator before parameterizing (p4800 = 0). – if required, start the function generator (p4800 = 1). |
A02025 Function generator: Period too short | Cause: The value for the period is too short. Remedy: Check and adapt the value for the period. |
A02026 Function generator: Pulse width too high | Cause: The selected pulse width is too high. The pulse width must be less than the period duration. Remedy: Reduce pulse width. |
A02030 Function generator: Physical address equals zero | Cause: The specified physical address is zero. Remedy: Set a physical address with a value other than zero. |
A02040 Function generator: Illegal value for offset | Cause: The value for the offset is higher than the value for the upper limit or lower than the value for the lower limit. Remedy: Adjust the offset value accordingly. |
A02041 Function generator: Illegal value for bandwidth | Cause: The bandwidth referred to the time slice clock cycle of the function generator has either been set too low or too high. Remedy: Check the value for the bandwidth and adapt accordingly. |
A02047 Function generator: Time slice clock cycle invalid | Cause: The time slice clock cycle selected does not match any of the existing time slices. Remedy: Enter an existing time slice clock cycle. The existing time slices can be read out via p7901. |
A02050 Trace: Start not possible | Cause: The trace has already been started. Remedy: Stop the trace and, if necessary, start again. |
A02051 Trace: recording not possible as a result of know-how protection | Cause: TRACE recording is not possible as at least one signal or trigger signal being used is under know-how protection. Remedy: – Temporarily activate or deactivate know-how protection (p7766). – Include the signal in the OEM exception list (p7763, p7764). – Where relevant do not record of the signal. |
A02055 Trace: Recording time too short | Cause: The trace duration is too short. The minimum is twice the value of the trace clock cycle. Remedy: Check the selected recording time and, if necessary, adjust. |
A02056 Trace: Recording cycle too short | Cause: The selected recording cycle is shorter than the selected basic clock cycle 0 (p0110[0]). Remedy: Increase the value for the trace cycle. |
A02057 Trace: Time slice clock cycle invalid | Cause: The time slice clock cycle selected does not match any of the existing time slices. Remedy: Enter an existing time slice clock cycle. The existing time slices can be read out via p7901. |
A02058 Trace: Time slice clock cycle for endless trace not valid | Cause: The selected time slice clock cycle cannot be used for the endless trace. Remedy: Enter the clock cycle of an existing time slice with a cycle time >= 2 ms for up to 4 recording channels or >= 4 ms from 5 recording channels per trace. The existing time slices can be read out via p7901. |
A02059 Trace: Time slice clock cycle for 2 x 8 recording channels not valid | Cause: The selected time slice clock cycle cannot be used for more than 4 recording channels. Remedy: Enter the clock cycle of an existing time slice with a cycle time >= 4 ms or reduce the number of recording channels to 4 per trace. The existing time slices can be read out via p7901. |
A02060 Trace: Signal to be traced missing | Cause: – a signal to be traced was not specified. – the specified signals are not valid. Remedy: – specify the signal to be traced. – check whether the relevant signal can be traced. |
A02061 Trace: Invalid signal | Cause: – the specified signal does not exist. – the specified signal can no longer be traced (recorded). Remedy: – specify the signal to be traced. – check whether the relevant signal can be traced. |
A02062 Trace: Invalid trigger signal | Cause: – a trigger signal was not specified. – the specified signal does not exist. – the specified signal is not a fixed-point signal. – the specified signal cannot be used as a trigger signal for the trace. Remedy: Specify a valid trigger signal. |
A02063 Trace: Invalid data type | Cause: The specified data type to select a signal using a physical address is invalid. Remedy: Use a valid data type. |
A02070 Trace: Parameter cannot be changed | Cause: The trace parameter settings cannot be changed when the trace is active. Remedy: – stop the trace before parameterization. – if required, start the trace. |
A02075 Trace: Pretrigger time too long | Cause: The selected pretrigger time must be shorter than the trace time. Remedy: Check the pretrigger time setting and change if necessary. |
F02080 Trace: Parameterization deleted due to unit changeover | Cause: The trace parameterization in the drive unit was deleted due to a unit changeover or a change in the reference parameters. Remedy: Restart trace. |
A02085 Message function: Parameterization error | Cause: A parameterization error was identified when starting the variable message function. Remedy: Correct the parameter and restart. |
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): – measuring function – long-time trace – trigger condition “immediate recording start” (IMMEDIATE) – trigger condition “start with function generator” (FG_START) Remedy: – if required, deactivate the multiple trace (p4840[0] = 0). – deactivate function or setting that is not permissible |
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. Remedy: – insert or remove the memory card. – use a larger memory card. – configure a longer trace time or use an endless trace. – avoid saving parameters while a multiple trace is running. – check whether other functions are presently accessing measurement result files. |
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): – measuring function – long-time trace – trigger condition “immediate recording start” (IMMEDIATE) – trigger condition “start with function generator” (FG_START) Remedy: – if required, deactivate the multiple trace (p4840[1] = 0). – deactivate function or setting that is not permissible |
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. Remedy: – insert or remove the memory card. – use a larger memory card. – configure a longer trace time or use an endless trace. – avoid saving parameters while a multiple trace is running. – check whether other functions are presently accessing measurement result files. |
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: – reduce the trace time. – increase the trace clock cycle. – reduce the number of signals to be traced. |
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. Remedy: – set p0118 to zero. – set p0118 to a value greater than or equal to the alarm value (for p1810.11 = 1) – set p0117 (from the device) to an automatic setting (p0117 = 1). – check the firmware versions of the components involved. |
A02150 OA: Application cannot be loaded | Cause: The system was not able to load an OA application. Remedy: – carry out a POWER ON (power off/on) for all components. – upgrade firmware to later version. – contact the Hotline. Re alarm value = 16: Load a compatible DCB user library (compatible to the interface of the DCC standard library). |
F02151 (A) OA: Internal software error | Cause: An internal software error has occurred within an OA application. Remedy: – carry out a POWER ON (power off/on) for all components. – upgrade firmware to later version. – contact the Hotline. – replace the Control Unit. |
F02152 (A) OA: Insufficient memory | Cause: Too many functions have been configured on this Control Unit (e.g. too many drives, function modules, data sets, OA applications, blocks, etc). Remedy: – change the configuration on this Control Unit (e.g. fewer drives, function modules, data sets, OA applications, blocks, etc). – use an additional Control Unit. |
F03000 NVRAM fault on action | Cause: A fault occurred during execution of action p7770 = 1 or 2 for the NVRAM data. Remedy: – Perform the remedy according to the results of the troubleshooting. – If necessary, start the action again. |
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 (power off/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. Remedy: – power down/power up the power supply for the Control Unit. – check the DRIVE-CLiQ connection. – if required, replace the Terminal Module. |
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) CU: Analog input wire breakage | Cause: The wire-break monitoring for an analog input has responded. Remedy: – Check the wiring to the signal source for interruptions. – Check the magnitude of the injected current – it is possible that the infed signal is too low. – Check the load resistor (250 Ohm). |
F03505 (N, A) Analog input wire breakage | Cause: The wire-break monitoring for an analog input has responded. Remedy: – check the wiring for interruptions. – Check the magnitude of the injected current – it is possible that the infed signal is too low. – Check the load resistor (250 Ohm). |
F03505 (N, A) TB: Analog input wire breakage | 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 | Cause: The wire-break monitoring for an analog input has responded. Remedy: – check the wiring for interruptions. – Check the magnitude of the injected current – it is possible that the infed signal is too low. – Check the load resistor (250 Ohm). |
A03506 (F, N) 24 V power supply missing | Cause: The 24 V power supply for the digital outputs (X124) is missing. Remedy: Check the terminals for the power supply voltage (X124, L1+, M). |
A03507 (F, N) Digital output not set | Cause: Despite specification by the signal source the digital output has not been set. Remedy: – check the 24 V power supply (e.g. X130.6 for CU310-2, ground is X130.5). – check the output terminals for short-circuits. – reset the signal source of the digital output for use by Safety Extended functions. – carry out a POWER ON (power off/on). |
A03510 (F, N) CU: Calibration data not plausible | Cause: During booting, the calibration data for the analog inputs is read and checked with respect to plausibility. At least one calibration data point was determined to be invalid. Remedy: – power down/power up the power supply for the Control Unit. – check the DRIVE-CLiQ wiring. |
A03510 (F, N) Calibration data not plausible | Cause: During ramp-up, the Terminal Module 31 (TM31) calibration data is read in and checked for plausibility. At least one calibration data point was determined to be invalid. Remedy: – power down/power up the power supply for the Control Unit. – check the DRIVE-CLiQ wiring. |
A03510 (F, N) TM: Calibration data not plausible | Cause: During ramp-up, the Terminal Module 31 (TM31) calibration data is read in and checked for plausibility. At least one calibration data point was determined to be invalid. Remedy: – power down/power up the power supply for the Control Unit. – check the DRIVE-CLiQ wiring. |
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. 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. Remedy: – check the 24 V power supply. – check the DRIVE-CLiQ wiring. – check whether the sampling time of the drive object involved is not equal to zero (p4099[0]). |
A05000 (N) Power unit: Overtemperature heat sink AC inverter | Cause: The alarm threshold for overtemperature at the inverter heat sink has been reached. Remedy: Check the following: – is the ambient temperature within the defined limit values? – have the load conditions and the load duty cycle been appropriately dimensioned? – has the cooling failed? |
A05001 (N) Power unit: Overtemperature depletion layer chip | Cause: Alarm threshold for overtemperature of the power semiconductor in the AC converter has been reached. Remedy: Check the following: – is the ambient temperature within the defined limit values? – have the load conditions and the load duty cycle been appropriately dimensioned? – has the cooling failed? – pulse frequency too high? |
A05002 (N) Power unit: Air intake overtemperature | Cause: The alarm threshold for the air intake overtemperature has been reached. Remedy: Check the following: – is the ambient temperature within the defined limit values? – has the fan failed? Check the direction of rotation. |
A05003 (N) Power unit: Internal overtemperature | Cause: The alarm threshold for internal overtemperature has been reached. Remedy: Check the following: – is the ambient temperature within the defined limit values? – has the fan failed? Check the direction of rotation. |
A05004 (N) Power unit: Rectifier overtemperature | Cause: The alarm threshold for the overtemperature of the rectifier has been reached. Remedy: Check the following: – is the ambient temperature within the defined limit values? – have the load conditions and the load duty cycle been appropriately dimensioned? – has the fan failed? Check the direction of rotation. – has a phase of the line supply failed? – is an arm of the supply (incoming) rectifier defective? |
A05005 Cooling unit: Cooling medium flow rate too low | Cause: Cooling unit: Alarm – flow rate has fallen below the alarm value. Remedy: – Check the feedback signals and parameter assignment (p0260 … p0267). – Check the coolant feed. |
A05006 (N) Power unit: Overtemperature thermal model | Cause: The temperature difference between the chip and heat sink has exceeded the permissible limit value (blocksize power units only). Remedy: Not necessary. The alarm disappears automatically once the limit value is undershot. |
A05007 (A) Power unit: Overtemperature thermal model (chassis PU) | Cause: The temperature difference between the chip and heat sink has exceeded the permissible limit value (r0293) (chassis power units only). Remedy: Not necessary. The alarm disappears automatically once the limit value is undershot. |
F05050 Parallel circuit: Pulse enable in spite of pulse inhibit | Cause: A power unit signals that the pulses are enabled although the pulses are inhibited. Remedy: The power unit is defective and must be replaced. |
F05051 Parallel circuit: Power unit pulse enable missing | Cause: For one or several power units, the pulses were not able to be enabled. Remedy:
|
A05052 (F) Parallel circuit: Illegal current dissymmetry | Cause: The deviation of the individual currents of the power units exceeds the alarm threshold specified in p7010. Remedy:
|
A05053 (F) Parallel circuit: Inadmissible DC link voltage dissymmetry | Cause: The deviation of the DC link voltage measured values exceeds the alarm threshold specified in p7011. Remedy:
|
A05054 Parallel circuit: Power unit de-activated | Cause: For the drive object involved, fewer power units connected in parallel are active than exist in the target topology. Operation is only possible at reduced power (power derating). Remedy: Re-activate the de-activated power units if required. |
F05055 Parallel connection: Power units with illegal code numbers | Cause: The code numbers of the power units are not permissible. For parallel circuit configurations, only power units with identical power unit data may be used. Remedy:
|
F05056 Parallel circuit: Power unit EEPROM versions differ | Cause: The EEPROM versions of the power units do not match. Remedy: Use power units with the same EEPROM version. |
F05057 Parallel circuit: Power unit firmware versions differ | Cause: The firmware versions of the power units connected in parallel do not match. Remedy: Use power units with the same firmware version. |
F05058 Parallel circuit: VSM EEPROM versions differ | Cause: The EEPROM versions of the Voltage Sensing Modules (VSM) do not match. Remedy: For parallel circuit configurations, only Voltage Sensing Modules (VSM) with identical EEPROM versions may be used. |
F05059 Parallel circuit: VSM firmware versions differ | Cause: The firmware versions of the Voltage Sensing Module (VSM) do not match. Remedy: For parallel circuit configurations, only Voltage Sensing Modules (VSM) with identical firmware versions may be used. |
F05060 Parallel circuit: Power unit firmware version does not match | Cause: Firmware from version V02.30.01.00 is required when connecting the power units in parallel. Remedy: Update the firmware of the power units (at least V02.30.01.00). |
F05061 Infeed VSM count | Cause: The number of active Voltage Sensing Modules (VSM) for the drive object infeed with chassis power units is not correct. Remedy: Adapts the number of active Voltage Sensing Modules (VSM). |
F05064 Parallel connection: Pulse synchronization error | Cause: The pulse synchronization of at least one of the power units connected in parallel is incorrect. Remedy: Restart the drive system. |
A05065 (F, N) Voltage measured values not plausible | Cause: The voltage measurement does not supply any plausible values and is not used. Remedy: The following parameterization must be made in order to deactivate the alarm:
|
F05118 (A) Pre-charging contactor simultaneity monitoring time exceeded | Cause: A feedback signal for the pre-charging contactor is interconnected and the simultaneity monitoring activated. After opening or closing a contactor of the parallel connection, after a monitoring time has elapsed, not all of the contactors have assumed the same state. Remedy:
|
F05119 (A) Bypass contactor simultaneity monitoring time exceeded | Cause: A feedback signal for the bypass contactor is interconnected and the simultaneity monitoring activated. After opening or closing a contactor of the parallel connection, after a monitoring time has elapsed, not all of the contactors have assumed the same state. Remedy:
|
F06000 Infeed: Precharging monitoring time expired | Cause: After the line contactor closes the power unit does not signal the READY state within the monitoring time (p0857). The end of the DC link pre-charging was not able to be completed for various reasons like no/low line supply, overheated resistors, or a defective circuit. Remedy: In general:
For specific causes (5-9), refer to the manual for detailed steps regarding cooling, capacitance checks, and ground fault checks. |
F06010 Infeed: Power unit EP 24 V missing in operation | Cause: In operation, the pulse enable via terminal EP at the Line Module (X21.3, X21.4) was withdrawn. Remedy:
|
F06050 Infeed: Smart Mode not supported | Cause: The power unit does not support the Smart Mode. Remedy:
|
F06052 Infeed: Filter temperature evaluation not supported | Cause: The power unit does not support filter temperature evaluation. This feature is required when an Active Interface Module is used as a line filter. Remedy: Upgrade the firmware for the power unit to a later version. |
F06100 Infeed: Shutdown due to line supply undervoltage condition | Cause: The filtered (steady-state) value of the line supply voltage is less than the fault threshold (p0283). Remedy:
|
A06105 (F) Infeed: Line supply undervoltage | Cause: The filtered (steady-state) value of line supply voltage is lower than the alarm threshold (p0282). Remedy:
|
F06200 Infeed: One or several line phases failed | Cause: Failure or overvoltage in one or several line supply phases, either during power-on or during operation. Remedy:
|
A06205 (F) Infeed: Voltage dip in at least one line supply phase | Cause: Voltage dip or overvoltage in one or several line supply phases has been detected in operation. Remedy: Generally, the following applies when an alarm message is output:
Specific remedies apply depending on the bitwise coded alarm value (r2124). |
F06207 (N, A) Infeed: Line currents not symmetrical | Cause: Asymmetry of the currents in the line phase too high. The most probable cause is failure of a line phase. Remedy:
|
F06210 Infeed: Summation current too high | Cause: The smoothed total of the phase currents (i1 + i2 + i3) is greater than 4 % of the maximum power unit current (r0209). This may be due to a DC link ground fault, incorrect zero point calibration, or a defective current measurement. Remedy:
|
F06211 Infeed: Summation current impermissibly high | Cause: The smoothed sum of the phase currents (i1 + i2 + i3) is impermissibly high. The summed current has exceeded the parameterized threshold for the ground fault monitoring (p0287). This may be due to a ground fault, incorrect zero point calibration, or a defective current measurement. Remedy:
|
A06215 (F) Infeed: Summation current too high | Cause: The smoothed total of the phase currents (i1 + i2 + i3) is greater than 3 % of the maximum power unit current (r0209). This may be due to a DC link ground fault, incorrect zero point calibration, or a defective current measurement. Remedy:
|
A06250 (F, N) Infeed: Defective capacitor(s) in at least one phase of line filter | Cause: A change in the line filter capacitance was detected in at least one line phase. Remedy:
|
F06255 (A) Infeed: temperature threshold value outside the measuring range | Cause: The fault number specifies the number of the VSM where a temperature sensor value is outside the measurable range of 181°C to 300°C for sensor type KTY. Remedy: Depending on the fault value, ensure the relevant parameter (p3667/p3668, p5467[0]/p5468[0], or p5467[1]/p5468[1]) is set within the value range from 181°C up to 300°C. |
A06260 Infeed: Temperature in the line filter too high | Cause: The temperature monitoring in the line filter has responded. If the temperature remains too high, it will result in fault F06261. Remedy:
|
F06261 Infeed: Temperature in the line filter permanently too high | Cause: After the temperature monitoring responded, the temperature in the line filter was permanently exceeded. Remedy:
|
F06262 Infeed: Temperature switch in the line filter open when powering up | Cause: When powering up the infeed, the temperature in the line filter is too high. Powering up is prevented. Remedy:
|
F06300 Infeed: Line voltage too high at power on | Cause: The RMS line supply voltage Vrms was so high when powering up that controlled operation is not possible without exceeding the permissible maximum voltage in the DC link (p0280). Remedy:
|
A06301 (F) Infeed: Line supply overvoltage | Cause: The filtered (steady-state) value of the rms line supply voltage Vrms is higher than the alarm threshold (p0281). Remedy:
|
F06310 (A) Infeed: Supply voltage (p0210) incorrectly parameterized | Cause: After pre-charging was completed, the calculated line supply voltage Vrms is not within the tolerance range of the supply voltage. Remedy:
|
F06311 Infeed: Supply voltage (p0210) incorrect | Cause: The line voltage nominal value indicated in p0210 is outside the nominal voltage range of the power unit. The actual line supply voltage Vrms does not lie within the extended tolerance range. Remedy:
|
F06320 Master/slave: 4-channel multiplexer control not valid | Cause: Values 0, 1, 2, and 3 are valid to control the 4-channel multiplexer via connector input p3572. An invalid value was identified. Remedy:
|
F06321 Master/slave: 6-channel multiplexer control not valid | Cause: For the 6-channel multiplexer control via connector input p3577 an invalid value was identified. Remedy:
|
A06350 (F) Infeed: Measured line frequency too high | Cause: The actual line frequency f_line is higher than the parameterized alarm threshold (f_line > p0211 * p0284). Remedy:
|
A06351 (F) Infeed: Measured line frequency too low | Cause: The actual line frequency f_line is lower than the parameterized alarm threshold (f_line < p0211 * p0285). Remedy:
|
A06400 Infeed: Line supply data identification selected/active | Cause: The line supply data identification is selected and active. The line inductance and the DC link capacitance are measured at the next pulse enable. Remedy: Not necessary. The alarm automatically disappears after the measurement has been completed. |
A06401 Infeed: Transformer data identification/test mode selected/active | Cause: A transformer data identification type or a transformer test operation has been selected or is active. Remedy: Not necessary. The alarm automatically disappears after the identification has been completed. |
F06500 Infeed: Line synchronization not possible | Cause: The line synchronization is not possible within the monitoring time. The infeed was re-synchronized to the line supply because it was interrupted due to a line frequency that was determined to be either too low or too high. After 20 attempts, synchronization were interrupted. Remedy:
|
A06502 (F, N) Infeed: Unable to achieve line synchronization in transformer magnetization | Cause: Line synchronization is not possible within the monitoring time (p5481[2]). Remedy:
|
F06503 Infeed: Line black start unsuccessful | Cause: The line black start was unsuccessful. Remedy:
|
F06504 Infeed: Island line supply synchronization unsuccessful | Cause: The island line supply synchronization was unsuccessful. Remedy:
|
F06505 Infeed: For transformer magnetization current limit exceeded | Cause: The current limit was exceeded when magnetizing the transformer (p5494[1] * r0207). Remedy:
|
A06601 (F) Infeed: Current offset measurement interrupted | Cause: Defective current measurement or a DC current is present during the offset measurement. Remedy: For alarm value 1: possible counter-measure if there is no line contactor: Power up an adequately long time before OFF1 = 1. For alarm value 2: check for defective current measurement or DC current, and check the DC link for a ground fault. |
A06602 (F) Infeed: Current offset measurement not possible | Cause: After an OFF1 = 1 no valid current offset measurement was able to be made within the monitoring time (p3491) before closing the line contactor. The current offset is set to 0. Remedy:
|
F06700 (A) Infeed: Switch line contactor for load condition | Cause: For an ON command, the infeed line contactor should be switched under load. Remedy:
|
A06800 (F) Infeed: Maximum steady-state DC link voltage reached | Cause: The DC link voltage setpoint has reached the maximum steady-state voltage parameterized in p0280. Remedy:
|
A06810 (F) Infeed: DC link voltage alarm threshold | Cause: In operation, the DC link voltage has dropped to below the alarm threshold. Possible causes include line supply voltage dip, overload of the infeed, or incorrectly parameterized controller for Active Line Module. Remedy:
|
A06849 (F, N) Infeed: Short-circuit operation active | Cause: The current hysteresis controller sequence control has detected a short circuit (r5452, r5522). The absolute line supply voltage (r5444[0], r5512[0]) is below the short-circuit voltage limit (p5459[2], p5529[2]), and the current limitation is active (r5402.3=1, r5502.3=1). Remedy:
|
F06850 Infeed: Short-circuit prevailing for too long | Cause: The maximum permissible duration (p5458[1], p5528[1]) for the short-circuit has been exceeded. The short-circuit could not be cleared within this time. Remedy:
|
F06851 Infeed: Distributed infeed line monitoring tripped | Cause: The line monitoring of the distributed line infeed has tripped. Remedy:
|
F06855 Infeed: Line filter monitor responded | Cause: A threshold value parameterized in p3678 has been exceeded or undershot in the line filter. Remedy:
|
A06860 Infeed: Function module activation not possible | Cause: Function module activation is not possible. The power unit used does not have the “gating unit with current limitation control” feature (r0192.19 or r0192.30). Remedy:
|
A06900 (F) Braking Module: Fault (1 -> 0) | Cause: The Braking Module signals a fault (1 -> 0) via X21.4 (“booksize” format) or X21.5 (“chassis” format). Possible causes include incorrect wiring, overtemperature, missing power supply, ground fault/short-circuit, or an internal component fault. Remedy:
|
A06901 Braking Module: Pre-alarm I2t shutdown | Cause: The Braking Module “Booksize” format signals “Pre-alarm I2t shutdown” via terminal X21.3. Remedy:
|
A06904 (N) Braking Module internal is inhibited | Cause: The internal Braking Module was inhibited via binector input p3680 = 1 signal. Remedy: Release the internal Braking Module (BI: p3680 = 0 signal). |
A06905 Braking Module internal I2t shutdown alarm | Cause: The internal Braking Module outputs an alarm due to the high I2t value. 80% of the maximum switch-on duration of the braking resistor has been reached. Remedy: Reduce the number of braking operations. |
F06906 (A) Braking Module internal fault | Cause: The internal Braking Module outputs a fault due to overcurrent or an excessively high I2t value and is therefore inhibited. Remedy: Reduce the number of braking operations. |
F06907 Braking Module internal overtemperature | Cause: The temperature sensor connected to the braking resistor signals an overtemperature. Remedy:
|
F06908 Braking Module internal overtemperature shutdown | Cause: Braking module shut down due to overtemperature at the temperature sensor of the braking resistor. Remedy:
|
F06909 Braking Module internal Vce fault | Cause: In the power unit, the monitoring of the collector-emitter voltage (U_ce) of the power semiconductor to control the braking resistor has responded. Possible causes include a short circuit at the braking resistor terminals or a defective power semiconductor. Remedy:
|
A06921 (N) Braking resistor phase unsymmetry | Cause:
Remedy:
|
F06922 Braking resistor phase failure | Cause: A phase failure for the brake resistor was detected. Remedy: Check the feeder cables to the braking resistors. |
F07011 Drive: Motor overtemperature | Cause: The motor temperature has exceeded the fault threshold. This can be due to motor overload, high ambient temperature, sensor issues (wire breakage), or an incorrectly parameterized temperature model. Remedy:
|
A07012 (N) Drive: Motor temperature model 1/3 overtemperature | Cause: The motor temperature model 1/3 identified that the alarm threshold was exceeded. Remedy:
|
F07013 Drive: Motor temperature model configuration fault | Cause: A fault has occurred in the configuration of the motor temperature model, such as the sensor not supplying the necessary temperature, an unknown sensor type, or multiple models being activated simultaneously. Remedy:
|
A07014 (N) Drive: Motor temperature model configuration alarm | Cause: A fault has occurred in the configuration of the motor temperature model. It is not possible to save the model temperature, or the alarm threshold is higher than the fault threshold. Remedy:
|
A07015 Drive: Motor temperature sensor alarm | Cause: An error was detected when evaluating the temperature sensor set in p0600 and p0601. Possible causes include wire breakage, sensor not connected, or measured resistance too low. Remedy:
|
F07016 Drive: Motor temperature sensor fault | Cause: An error was detected when evaluating the temperature sensor set in p0600 and p0601. Possible causes are wire breakage, sensor not connected, or measured resistance too low. Remedy:
|
A07017 Additional temperature alarm threshold exceeded | Cause: The additional temperature has exceeded the alarm threshold in p4102[0]. Remedy:
|
F07018 Additional temperature fault threshold exceeded | Cause: The additional temperature has exceeded the fault threshold in p4102[1], or there is a wire breakage/sensor fault. Remedy:
|
F07080 Drive: Incorrect control parameter | Cause: The closed-loop control parameters have been parameterized incorrectly (e.g. p0356 = L_spread = 0). Remedy: Modify the parameter indicated in the fault value (r0949) (e.g. p0640 = current limit > 0). |
F07082 Macro: Execution not possible | Cause: The macro cannot be executed due to various reasons, such as invalid files, incorrect data types, recursive calls, write protection, or other specific parameter issues. Remedy:
|
F07083 Macro: ACX file not found | Cause: The ACX file (macro) to be executed was not able to be found in the appropriate directory. Remedy:
|
F07084 Macro: Condition for WaitUntil not fulfilled | Cause: The WaitUntil condition set in the macro was not fulfilled in a certain number of attempts. Remedy: Check and correct the conditions for the WaitUntil loop. |
F07085 Drive: Open-loop/closed-loop control parameters changed | Cause: Open-loop/closed-loop control parameters have had to be changed due to exceeding dynamic limits, hardware limitations, or missing thermal data. Remedy: Not necessary. It is not necessary to change the parameters as they have already been correctly limited. |
F07083 Macro: ACX file not found | Cause: The ACX file (macro) to be executed was not able to be found in the appropriate directory. Remedy:
|
F07084 Macro: Condition for WaitUntil not fulfilled | Cause: The WaitUntil condition set in the macro was not fulfilled in a certain number of attempts. Remedy:
|
F07085 Drive: Open-loop/closed-loop control parameters changed | Cause: Open-loop/closed-loop control parameters have had to be changed. Remedy:
|
F07086 Units changeover: Parameter limit violation due to reference value change | Cause: A reference parameter was changed in the system. This resulted in the fact that for the parameters involved, the selected value was not able to be written in the per unit notation. Remedy:
|
F07087 Drive: Encoderless operation not possible for the selected pulse frequency | Cause: Encoderless operation is not possible for the selected pulse frequency (p1800). Remedy:
|
F07088 Units changeover: Parameter limit violation due to units changeover | Cause: A changeover of units was initiated. This resulted in a violation of a parameter limit. Remedy:
|
A07089 Changing over units: Function module activation is blocked because the units have been changed over | Cause: An attempt was made to activate a function module. This is not permissible if the units have already been changed over. Remedy:
|
F07090 Drive: Upper torque limit less than the lower torque limit | Cause: The upper torque limit is lower than the lower torque limit. Remedy:
|
A07091 Drive: determined current controller dynamic response invalid | Cause: The identification of the current control loop was unsuccessful. Remedy:
|
A07092 Drive: moment of inertia estimator still not ready | Cause: The moment of inertia estimator still has no valid values. Remedy:
|
F07093 (A) Drive: Test signal error | Cause: Fault value (r0949, interpret decimal): Remedy: Fault value (r0949, interpret decimal):
|
F07100 Drive: Sampling times cannot be reset | Cause: When resetting drive parameter (p0976) sampling times cannot be reset using p0111, p0112, p0115. Remedy:
|
F07110 Drive: Sampling times and basic clock cycle do not match | Cause: The parameterized sampling times do not match the basic clock cycle. Remedy:
|
A07140 Drive: Current controller sampling time for spindle does not match | Cause: The parameterized current controller sampling time for the spindle has been set too high. Remedy:
|
A07200 Drive: Master control ON command present | Cause: The ON/OFF1 command is present (no 0 signal). Remedy:
|
F07220 (N, A) Drive: Master control by PLC missing | Cause: The “master control by PLC” signal was missing in operation. Remedy:
|
F07300 (A) Drive: Line contactor feedback signal missing | Cause: – the line contactor was not able to be closed within the time in p0861. Remedy:
|
F07311 Bypass motor switch | Cause: Fault value (r0949, interpret bitwise binary): Remedy:
|
F07312 Bypass LSS: | Cause: Fault value (r0949, interpret bitwise binary): Remedy:
|
F07320 Drive: Automatic restart interrupted | Cause: – The specified number of restart attempts (p1211) has been completely used up because within the monitoring time (p1213) the faults were not able to be acknowledged. The number of restart attempts (p1211) is decremented at each new start attempt. Remedy:
|
A07321 Drive: Automatic restart active | Cause: The automatic restart (AR) is active. When the line supply returns and/or the causes of the existing faults are removed the drive is automatically restarted. The pulses are enabled and the motor starts to rotate. Remedy:
|
A07329 (N) Drive: kT estimator, kT(iq) characteristic or voltage compensation does not function | Cause: A function of the function module “extended torque control” (r0108.1) was activated – however the (complete) function is not available. Remedy: Re fault value = 1, 2: |
F07330 Flying restart: Measured search current too low | Cause: During a flying restart, it was identified that the search current reached is too low. Remedy:
|
F07331 Flying restart: Function not supported | Cause: It is not possible to power up with the motor rotating (no flying restart). In the following cases, the “flying restart” function is not supported: 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. Remedy:
|
A07351 (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. Remedy:
|
A07354 Drive: cogging torque compensation not possible | Cause: Cogging torque compensation is selected and is not (completely) supported. Remedy: If required, deselect the cogging torque compensation (p5250 = 0). |
A07400 (N) Drive: DC link voltage maximum controller active | Cause: The DC link voltage controller has been activated because of the upper switch-in threshold (p1244). Remedy: Not necessary. |
A07401 (N) Drive: DC link voltage maximum controller de-activated | Cause: The Vdc_max controller can no longer maintain the DC link voltage (r0070) below the limit value (r1242, r1282) and was therefore switched out (disabled). Remedy:
|
A07402 (N) Drive: DC link voltage minimum controller active | Cause: The DC link voltage controller has been activated due to the lower switch-in threshold (p1248). Remedy: Not necessary. |
F07403 (N, A) Drive: Lower DC link voltage threshold reached | Cause: The DC link voltage monitoring is active (p1240 = 5, 6) and the lower DC link voltage threshold (p1248) was reached in the “Operation” state. Remedy:
|
F07404 Drive: Upper DC link voltage threshold reached | Cause: The DC link voltage monitoring is active (p1240 = 4, 6) and the upper DC link voltage threshold (p1244) was reached in the “Operation” state. Remedy:
|
F07405 (N, A) Drive: Kinetic buffering minimum speed not reached | Cause: During kinetic buffering the speed fell below minimum speed (p1257 or p1297 for vector drives with U/f control) and the line supply did not return. Remedy:
|
F07406 (N, A) Drive: Kinetic buffering maximum time exceeded | Cause: The maximum buffer time (p1255 and p1295 for vector drives with U/f control) has been exceeded without the line supply having returned. Remedy:
|
F07407 Drive: Vdc reduction not permissible | Cause: For chassis power units, the reduction of the line voltage (see r0212.0) is only possible for closed-loop control of the DC link voltage. Remedy:
|
A07409 Drive: U/f control, current limiting controller active | Cause: The current limiting controller of the U/f control was activated because the current limit was exceeded. Remedy: The alarm automatically disappears after one of the following measures: |
F07410 Drive: Current controller output limited | Cause: The condition “l_act = 0 and Uq_set_1 longer than 16 ms at its limit” is present and can be caused by the following: Remedy:
|
F07411 Drive: Flux controller output limited | Cause: The specified flux setpoint cannot be reached, although the set maximum field current is specified (p1603). Remedy:
|
F07412 Drive: Commutation angle incorrect (motor model) | Cause: An incorrect commutation angle was detected that can result in a positive coupling in the speed controller. Remedy:
|
F07413 Drive: Commutation angle incorrect (pole position identification) | Cause: An incorrect commutation angle was detected that can result in a positive coupling in the speed controller. Remedy:
|
F07414 (N, A) Drive: Encoder serial number changed | Cause: The serial number of the motor encoder of a synchronous motor has changed. The change was only checked for encoders with serial number (e.g. EnDat encoders) and build-in motors (e.g. p0300 = 401) or third-party motors (p0300 = 2). Remedy: Proceed as follows to hide serial number monitoring: |
N07415 (F) Drive: Angular commutation offset transfer running | Cause: The angular commutation offset was automatically determined using p1990 = 1. Remedy:
|
A07416 Drive: Flux controller configuration | Cause: The configuration of the flux control (p1401) is contradictory. Remedy: Re fault cause = 1: |
F07417 Drive: Pulse technique not plausible (motor model) | Cause: The evaluation of the test pulse response indicated incorrect values. Remedy: For fault value = 0: |
F07419 Drive: Current setpoint filter adaptation error | Cause: An error has occurred when configuring or when using the “Current setpoint filter adaptation” function. Remedy: The message can always be removed by deactivating adaptation (p5280 = 0, -1). |
F07420 Drive: Current setpoint filter natural frequency > Shannon frequency | Cause: One of the filter natural frequencies is greater than the Shannon frequency. Remedy:
|
F07421 Drive: Speed filter natural frequency > Shannon frequency | Cause: One of the filter natural frequencies is greater than the Shannon frequency. Remedy:
|
F07422 Drive: Reference model natural frequency > Shannon frequency | Cause: The natural filter frequency of the PT2 element for the reference model (p1433) is greater than the Shannon frequency. Remedy:
|
F07423 Drive: APC filter natural frequency > Shannon frequency | Cause: One of the filter natural frequencies is greater than the Shannon frequency. Remedy:
|
A07424 Drive: Operating condition for APC not valid | Cause: The APC function (Advanced Positioning Control) has identified an invalid operating condition. Remedy:
|
F07425 Drive: APC monitoring time for speed limit expired | Cause: The limit value (p3778) for the speed/velocity was exceeded for a time longer than that set in the monitoring time (p3779). Remedy:
|
F07426 (A) Technology controller actual value limited | Cause: The actual value for the technology controller, interconnected via connector input p2264, has reached a limit. Remedy:
|
A07428 (N) Technology controller parameterizing error | Cause: The technology controller has a parameterizing error. Remedy:
|
F07429 Drive: DSC without encoder not possible | Cause: The function DSC (Dynamic Servo Control) was activated although there is no encoder. Remedy:
|
F07430 Drive: Changeover to open-loop torque controlled operation not possible | Cause: For encoderless operation, the converter cannot change over to closed-loop torque-controlled operation (BI: p1501). Remedy:
|
F07431 Drive: Changeover to encoderless operation not possible | Cause: For closed-loop torque control, the converter cannot change over to encoderless operation (p1404). Remedy:
|
F07432 Drive: Motor without overvoltage protection | Cause: In the case of a fault at maximum speed, the motor can generate an overvoltage that can destroy the drive system. Remedy: Overvoltage protection can be implemented in the following ways:
See also: p0643 (Overvoltage protection for synchronous motors), p1231 (Armature short-circuit / DC braking configuration) |
F07433 Drive: Closed-loop control with encoder is not possible as the encoder has not been unparked | Cause: The changeover to closed-loop control with encoder is not possible as the encoder has not been unparked. Remedy:
|
F07434 Drive: It is not possible to change the direction of rotation with the pulses enabled | Cause: A drive data set was selected – with the pulses enabled – which has a different parameterized direction of rotation (p1821). It is only possible to change the motor direction of rotation using p1821 when the pulses are inhibited. Remedy:
|
F07435 (N) Drive: Setting the ramp-function generator for sensorless vector control | Cause: During operation with sensorless vector control (r1407.1) the ramp-function generator was stopped (p1141) or bypassed (p1122). The drive is switched-on with flying restart activated (p1200), and at the same time the ramp-function generator is bypassed (p1122). Remedy:
|
F07439 Drive: Function not supported | Cause: The power unit does not support the selected function. Remedy: For fault value = 1: Upgrade firmware or use a different power unit. |
A07440 EPOS: Jerk time is limited | Cause: The calculation of the jerk time resulted in an excessively high value, so it is internally limited to 1000 ms. Remedy:
|
A07441 LR: Save the position offset of the absolute encoder adjustment | Cause: The status of the absolute encoder adjustment has changed. To permanently save the new offset, it must be saved in a non-volatile fashion (p0971, p0977). Remedy:
|
F07442 (A) LR: Multiturn does not match the modulo range | Cause: The ratio between the multiturn resolution and the modulo range (p2576) is not an integer number. This causes the adjustment to be reset as the position cannot be reproduced after power-off/power-on. Remedy:
|
F07443 (A) LR: Reference point coordinate not in the permissible range | Cause: The reference point coordinate received via connector input p2599 lies outside the permissible range and cannot be set as the actual axis position. Remedy:
|
F07446 (A) Load gear: Position tracking cannot be reset | Cause: The position tracking cannot be reset. Remedy:
|
F07447 Load gear: Position tracking, maximum actual value exceeded | Cause: When position tracking of the load gear is configured, the maximum possible absolute position value (r2723) can no longer be represented within 32 bits. Remedy:
|
F07448 (A) Load gear: Position tracking, linear axis has exceeded the maximum range | Cause: For a configured linear axis/no modulo axis, the currently effective motor encoder has exceeded the maximum possible traversing range. Remedy:
|
F07449 (A) Load gear: Position tracking actual position outside tolerance window | Cause: When powered down, the currently effective motor encoder was moved through a distance greater than was parameterized in the tolerance window. There may no longer be a valid reference between the mechanical system and encoder. Remedy:
|
F07450 (A) LR: Standstill monitoring has responded | Cause: After the standstill monitoring time (p2543) expired, the drive left the standstill window (p2542). Possible causes include incorrect parameter settings, mechanical overload, or incorrect connections. Remedy:
|
F07451 (A) LR: Position monitoring has responded | Cause: When the position monitoring time (p2545) expired, the drive had still not reached the positioning window (p2544). Possible causes include incorrect parameterization or a mechanically locked drive. Remedy:
|
F07452 (A) LR: Following error too high | Cause: The difference between the position setpoint and position actual value is higher than the tolerance (p2546). Possible causes include exceeded torque, a position measuring system fault, or a locked mechanical system. Remedy:
|
F07453 LR: Position actual value preprocessing error | Cause: An error has occurred during the position actual value preprocessing. Remedy:
|
A07454 LR: Position actual value preprocessing does not have a valid encoder | Cause: One of the following problems has occurred with the position actual value preprocessing: Remedy:
|
A07455 EPOS: Maximum velocity limited | Cause: The maximum velocity (p2571) is too high to correctly calculate the modulo correction and has been limited. Remedy:
|
A07456 EPOS: Setpoint velocity limited | Cause: The actual setpoint velocity is greater than the parameterized maximum velocity (p2571) and is therefore limited. Remedy:
|
A07457 EPOS: Combination of input signals illegal | Cause: An illegal combination of input signals that are simultaneously set was identified. Remedy:
|
F07458 EPOS: Reference cam not found | Cause: After starting the search for reference, the axis moved through the maximum permissible distance without finding the reference cam. Remedy:
|
F07459 EPOS: No zero mark | Cause: After leaving the reference cam, the axis has traversed the maximum permissible distance between the reference cam and zero mark without finding the zero mark. Remedy:
|
F07460 EPOS: End of reference cam not found | Cause: During the search for reference, when the axis reached the zero mark it also reached the end of the traversing range without detecting an edge at the binector input “reference cam”. Remedy:
|
A07461 EPOS: Reference point not set | Cause: When starting a traversing block/direct setpoint input, a reference point is not set (r2684.11 = 0). Remedy:
|
A07462 EPOS: Selected traversing block number does not exist | Cause: A traversing block selected via binector input was started, but the block number does not exist in the program. Remedy:
|
A07463 (F) EPOS: External block change not requested in the traversing block | Cause: For a traversing block with the block change enable CONTINUE_EXTERNAL_ALARM, the external block change was not requested. Remedy:
|
F07464 EPOS: Traversing block is inconsistent | Cause: The traversing block does not contain valid information. Remedy:
|
A07465 EPOS: Traversing block does not have a subsequent block | Cause: There is no subsequent block in the traversing block. Remedy:
|
A07466 EPOS: Traversing block number assigned a multiple number of times | Cause: The same traversing block number was assigned a multiple number of times. Remedy:
|
A07467 EPOS: Traversing block has illegal task parameters | Cause: The task parameter in the traversing block contains an illegal value. Remedy:
|
A07468 EPOS: Traversing block jump destination does not exist | Cause: In a traversing block, a jump was programmed to a non-existent block. Remedy:
|
A07469 EPOS: Traversing block < target position < software limit switch minus | Cause: In the traversing block the specified absolute target position lies outside the range limited by the software limit switch minus. Remedy:
|
A07470 EPOS: Traversing block> target position > software limit switch plus | Cause: In the traversing block the specified absolute target position lies outside the range limited by the software limit switch plus. Remedy:
|
A07471 EPOS: Traversing block target position outside the modulo range | Cause: In the traversing block the target position lies outside the modulo range. Remedy:
|
A07472 EPOS: Traversing block ABS_POS/ABS_NEG not possible | Cause: In the traversing block the positioning mode ABS_POS or ABS_NEG were parameterized with the modulo correction not activated. Remedy:
|
A07473 (F) EPOS: Beginning of traversing range reached | Cause: When traversing, the axis has moved to the traversing range limit. Remedy:
|
A07474 (F) EPOS: End of traversing range reached | Cause: When traversing, the axis has moved to the traversing range limit. Remedy:
|
F07475 (A) EPOS: Target position < start of traversing range | Cause: The target position for relative traversing lies outside the traversing range. Remedy:
|
F07476 (A) EPOS: Target position > end of the traversing range | Cause: The target position for relative traversing lies outside the traversing range. Remedy:
|
A07477 (F) EPOS: Target position < software limit switch minus | Cause: In the actual traversing operation, the target position is less than the software limit switch minus. Remedy:
|
A07478 (F) EPOS: Target position > software limit switch plus | Cause: In the actual traversing operation, the target position is greater than the software limit switch plus. Remedy:
|
A07479 EPOS: Software limit switch minus reached | Cause: The axis is at the position of the software limit switch minus. An active traversing block was interrupted. Remedy:
|
A07480 EPOS: Software limit switch plus reached | Cause: The axis is at the position of the software limit switch plus. An active traversing block was interrupted. Remedy:
|
F07481 (A) EPOS: Axis position < software limit switch minus | Cause: The actual position of the axis is less than the position of the software limit switch minus. Remedy:
|
F07482 (A) EPOS: Axis position > software limit switch plus | Cause: The actual position of the axis is greater than the position of the software limit switch plus. Remedy:
|
A07483 EPOS: Travel to fixed stop clamping torque not reached | Cause: The fixed stop in the traversing block was reached without the clamping torque/clamping force having been achieved. Remedy:
|
F07484 EPOS: Fixed stop outside the monitoring window | Cause: In the “fixed stop reached” state, the axis has moved outside the defined monitoring window (p2635). Remedy:
|
F07485 (A) EPOS: Fixed stop not reached | Cause: In a traversing block with the task FIXED STOP, the end position was reached without detecting a fixed stop. Remedy:
|
A07486 EPOS: Intermediate stop missing | Cause: In the modes “traversing blocks” or “direct setpoint input/MDI” at the start of motion, the binector input “no intermediate stop/intermediate stop” (BI: p2640) did not have a 1 signal. Remedy:
|
A07487 EPOS: Reject traversing task missing | Cause: In the modes “traversing blocks” or “direct setpoint input/MDI” at the start of motion, the binector input “do not reject traversing task/reject traversing task” (BI: p2641) does not have a 1 signal. Remedy:
|
F07488 EPOS: Relative positioning not possible | Cause: In the mode “direct setpoint input/MDI”, for continuous transfer (p2649 = 1) relative positioning was selected (BI: p2648 = 0 signal). Remedy:
|
A07489 EPOS: Reference point correction outside the window | Cause: For the function “flying referencing” the difference between the measured position at the measuring probe and the reference point coordinate lies outside the parameterized window. Remedy:
|
F07490 (N) EPOS: Enable signal withdrawn while traversing | Cause: – for a standard assignment, another fault may have occurred as a result of withdrawing the enable signals. Remedy:
|
F07491 (A) EPOS: STOP cam minus reached | Cause: A 0 signal was detected at binector input BI: p2569, i.e. the STOP cam minus was reached. For a positive traversing direction, the STOP cam minus was reached – i.e. the wiring of the STOP cam is incorrect. Remedy:
|
F07492 (A) EPOS: STOP cam plus reached | Cause: A 0 signal was detected at binector input Bl: p2570, i.e. the STOP cam plus was reached. For a negative traversing direction, the STOP cam plus was reached – i.e. the wiring of the STOP cam is incorrect. Remedy:
|
F07493 LR: Overflow of the value range for position actual value | Cause: The value range for the position actual value representation was exceeded. Remedy:
|
F07494 LR: Drive Data Set changeover in operation | Cause: A Drive Data Set changeover (DDS) with a change of the mechanical relationships, direction of rotation, or encoder assignment was requested in operation. Remedy:
|
A07495 (F) LR: Reference function interrupted | Cause: An activated reference function (reference mark search or measuring probe evaluation) was interrupted. Possible causes include an encoder fault or simultaneous activation/deactivation of signals. Remedy:
|
A07496 EPOS: Enable not possible | Cause: It is not possible to enable the basic positioner because at least one signal is missing (e.g., EPOS enable or position actual value valid feedback). Remedy:
|
A07497 (N) LR: Position setting value activated | Cause: The position actual value is set to the value received via CI: p2515while Bl: p2514 = 1 signal. A possible system deviation cannot be corrected. Remedy:
|
A07498 (F) LR: Measuring probe evaluation not possible | Cause: When evaluating the measuring probe, an error occurred. Remedy:
|
F07499 (A) EPOS: Reversing cam approached with the incorrect traversing direction | Cause: The reversing cam MINUS was approached in the positive traversing direction or the reversing cam PLUS was approached in the negative traversing direction. Remedy:
|
F07500 Drive: Power unit data set PDS not configured | Cause: Only for controlled line supply infeed/regenerative feedback units: The power unit data set was not configured – this means that a data set number was not entered into the drive data set. Remedy:
|
F07501 Drive: Motor Data Set MDS not configured | Cause: Only for power units: The motor data set was not configured – this means that a data set number was not entered into the associated drive data set. Remedy:
|
F07502 Drive: Encoder Data Set EDS not configured | Cause: Only for power units: The encoder data set was not configured – this means that a data set number was not entered into the associated drive data set. Remedy:
|
F07503 EPOS: STOP cam approached with the incorrect traversing direction | Cause: The STOP cam MINUS was approached in the positive traversing direction or the STOP cam PLUS was approached in the negative traversing direction. Remedy:
|
A07504 Drive: Motor data set is not assigned to a drive data set | Cause: A motor data set is not assigned to a drive object. All existing motor data sets must be assigned using the MDS number (p0186[0…n]). Remedy:
|
A07505 EPOS: Task fixed stop not possible in the U/f/SLVC mode | Cause: In the U/f/SLVC mode, an attempt was made to execute a traversing block with the “fixed stop” task. This is not possible. Remedy:
|
F07509 Drive: Component assignment missing | Cause: A Drive Data Set (DDS) is assigned to a Motor Data Set (MDS) or Encoder Data Set (EDS) that does not have a component number. Remedy:
|
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. It is not permissible that identical encoders are operated together in one drive data set. Remedy:
|
F07511 Drive: Encoder used a multiple number of times | Cause: Each encoder may only be assigned to one drive and within a drive must – in each drive data set – either always be encoder 1, always encoder 2 or always encoder 3. This unique assignment has been violated. Remedy:
|
F07512 Drive: Encoder data set changeover cannot be parameterized | Cause: Using p0141, a changeover of the encoder data set is prepared that is illegal. In this firmware release, an encoder data set changeover is only permitted for the components in the actual topology. Remedy:
|
A07514 (N) Drive: Data structure does not correspond to the interface module | Cause: The interface mode “SIMODRIVE 611 universal” was set (p2038 = 1) and the data structure does not correspond to this mode. Remedy:
|
F07515 Drive: Power unit and motor incorrectly connected | Cause: A power unit was assigned to a motor in a drive data set that is not connected in the target topology. It is possible that a motor has not been assigned to the power unit (p0131). Remedy:
|
F07516 Drive: Re-commission the data set | Cause: The assignment between the drive data set and motor data set (p0186) or between the drive data set and the encoder data set was modified (p0187). This is the reason that the drive data set must re-commissioned. Remedy:
|
F07517 Drive: Encoder data set changeover incorrectly parameterized | Cause: An MDS cannot have different motor encoders in two different DDS. The parameterization therefore results in an error. 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. Remedy:
|
A07519 Drive: Motor changeover incorrectly parameterized | Cause: With the setting p0833.0 = 1, a motor changeover via the application is selected. This is the reason that p0827 must have different values in the appropriate motor data set. Remedy:
|
A07520 Drive: Motor cannot be changed over | Cause: The motor cannot be changed over. Remedy:
|
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 speeds less than the start of field weakening. 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. Remedy:
|
F07551 Drive encoder: No commutation angle information | Cause: The commutation angle information is missing. This means that synchronous motors cannot be controlled (closed-loop control). Remedy: Re fault cause = 1: |
F07552 (A) Drive encoder: Encoder configuration not supported | Cause: The requested encoder configuration is not supported. Only bits may be requested in p0404 that are signaled as being supported by the encoder evaluation in r0456. Remedy:
|
F07553 (A) Drive encoder: Sensor Module configuration not supported | Cause: The Sensor Module does not support the requested configuration. In p0430 or p0437 (requested functions), at least 1 bit was set that is not supported in r0458 or 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. For linear axes, it is not possible to simultaneously activate the position tracking for load and measuring gears. Remedy: For fault value 0: use an absolute encoder. |
F07556 Measuring gear: Position tracking, maximum actual value exceeded | Cause: When the position tracking of the measuring gear is configured, the drive/encoder identifies a maximum possible absolute position actual value (r0483) that cannot be represented within 32 bits. Remedy:
|
A07557 (F) Encoder 1: Reference point coordinate not in the permissible range | Cause: The reference point coordinate received when adjusting the encoder lies outside the half of the encoder range and cannot be set as actual axis position. Remedy:
|
A07558 (F) Encoder 2: Reference point coordinate not in the permissible range | Cause: The reference point coordinate received when adjusting the encoder lies outside the half of the encoder range and cannot be set as actual axis position. Remedy:
|
A07559 (F) Encoder 3: Reference point coordinate not in the permissible range | Cause: The reference point coordinate received when adjusting the encoder lies outside the half of the encoder range and cannot be set as actual axis position. Remedy:
|
F07560 Drive encoder: Number of pulses is not to the power of two | Cause: For rotary absolute encoders, the pulse number in p0408 must be to the power of two. Remedy:
|
F07561 Drive encoder: Number of multiturn pulses is not to the power of two | Cause: The multiturn resolution in p0421 must be to the power of two. Remedy:
|
F07562 (A) Drive, encoder: Position tracking, incremental encoder not possible | Cause: The requested position tracking for incremental encoders is not supported. Remedy:
|
F07563 (A) Drive encoder: XIST1_ERW configuration incorrect | Cause: An incorrect configuration was identified for the “Absolute position for incremental encoder” function. The function is not supported (r0459.13 = 0). 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). 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). 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). Remedy:
|
A07569 (F) Enc identification active | Cause: During encoder identification (waiting) with p0400 = 10100, the encoder could still not be identified. Either the wrong encoder/cable has been installed, or the DRIVE-CLiQ component has not been connected. Remedy:
|
N07570 (F) Encoder identification data transfer running | Cause: The encoder type was automatically determined using p0400 = 10100. This fault causes the pulses to be suppressed – this is necessary to transfer the encoder parameterization to p0400ff. Remedy:
|
F07575 Drive: Motor encoder not ready | Cause: The motor encoder signals that it is not ready. Possible causes: initialization unsuccessful, “parking encoder” function is active, or the encoder interface is deactivated/defective. Remedy:
|
A07576 Drive: Encoderless operation due to a fault active | Cause: Encoderless operation is active due to a fault (r1407.13 = 1). The behavior for faults has been set to ENCODER fault response in p0491. Remedy:
|
A07577 (F) Encoder 1: Measuring probe evaluation not possible | Cause: When evaluating the measuring probe, an error occurred. Remedy:
|
A07578 (F) Encoder 2: Measuring probe evaluation not possible | Cause: When evaluating the measuring probe, an error occurred. Remedy:
|
A07579 (F) Encoder 3: Measuring probe evaluation not possible | Cause: When evaluating the measuring probe, an error occurred. 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:
|
A07581 (F) Encoder 1: Position actual value preprocessing error | Cause: An error has occurred during the position actual value preprocessing. Remedy:
|
A07582 (F) Encoder 2: Position actual value preprocessing error | Cause: An error has occurred during the position actual value preprocessing. Remedy:
|
A07583 (F) Encoder 3: Position actual value preprocessing error | Cause: An error has occurred during the position actual value preprocessing. Remedy:
|
A07584 Encoder 1: Position setting value activated | Cause: The position actual value is set to the value received via Cl: p2515while Bl: p2514 = 1 signal. A possible system deviation cannot be corrected. Remedy:
|
A07585 Encoder 2: Position setting value activated | Cause: The position actual value is set to the value received via Cl: p2515while Bl: p2514 = 1 signal. A possible system deviation cannot be corrected. Remedy:
|
A07586 Encoder 3: Position setting value activated | Cause: The position actual value is set to the value received via Cl: p2515while Bl: p2514 = 1 signal. A possible system deviation cannot be corrected. Remedy:
|
A07587 Encoder 1: Position actual value preprocessing does not have a valid encoder | Cause: An encoder data set has been assigned, however, the encoder data set does not contain any encoder data (p0400 = 0) or invalid data (e.g. p0408 = 0). Remedy:
|
A07588 Encoder 2: Position actual value preprocessing does not have a valid encoder | Cause: An encoder data set has been assigned, however, the encoder data set does not contain any encoder data (p0400 = 0) or invalid data (e.g. p0408 = 0). Remedy:
|
A07589 Encoder 3: Position actual value preprocessing does not have a valid encoder | Cause: An encoder data set has been assigned, however, the encoder data set does not contain any encoder data (p0400 = 0) or invalid data (e.g. p0408 = 0). Remedy:
|
A07590 (F) Encoder 1: Drive Data Set changeover in operation | Cause: A Drive Data Set changeover (DDS) with a change of the mechanical relationships and the encoder assignment (p2502) was requested in operation. Remedy:
|
A07591 (F) Encoder 2: Drive Data Set changeover in operation | Cause: A Drive Data Set changeover (DDS) with a change of the mechanical relationships and the encoder assignment (p2502) was requested in operation. Remedy:
|
A07592 (F) Encoder 3: Drive Data Set changeover in operation | Cause: A Drive Data Set changeover (DDS) with a change of the mechanical relationships and the encoder assignment (p2502) was requested in operation. Remedy:
|
A07593 (F, N) Encoder 1: Value range for position actual value exceeded | Cause: The value range (-2147483648 … 2147483647) for the position actual value representation was exceeded. When the overflow occurs, the “referenced” or “absolute encoder adjusted” status is reset. Remedy:
|
A07594 (F, N) Encoder 2: Value range for position actual value exceeded | Cause: The value range (-2147483648 … 2147483647) for the position actual value representation was exceeded. Remedy:
|
A07595 (F, N) Encoder 3: Value range for position actual value exceeded | Cause: The value range (-2147483648 … 2147483647) for the position actual value representation was exceeded. Remedy:
|
A07596 (F) Encoder 1: Reference function interrupted | Cause: An activated reference function (reference mark search or measuring probe evaluation) was interrupted. Possible causes include an encoder fault, a position value set during the function, or simultaneous activation/deactivation of signals. Remedy:
|
A07597 (F) Encoder 2: Reference function interrupted | Cause: An activated reference function was interrupted due to an encoder fault, a position value set during the function, or simultaneous activation/deactivation of signals. Remedy:
|
A07598 (F) Encoder 3: Reference function interrupted | Cause: An activated reference function was interrupted due to an encoder fault, a position value set during the function, or simultaneous activation/deactivation of signals. Remedy:
|
F07599 (A) Encoder 1: Adjustment not possible | Cause: The maximum encoder value times the factor to convert the absolute position has exceeded the value range for displaying the position actual value. If the value for the maximum possible absolute position is too large, an adjustment is not possible due to an overflow. Remedy:
|
F07600 (A) Encoder 2: Adjustment not possible | Cause: The maximum encoder value times the factor to convert the absolute position has exceeded the value range for displaying the position actual value. If the value for the maximum possible absolute position is too large, an adjustment is not possible due to an overflow. Remedy:
|
F07601 (A) Encoder 3: Adjustment not possible | Cause: The maximum encoder value times the factor to convert the absolute position has exceeded the value range for displaying the position actual value. If the value for the maximum possible absolute position is too large, an adjustment is not possible due to an overflow. Remedy:
|
F07750 Drive: Parameter invalid | Cause: A parameter value has been set that is not valid, or was not correctly entered. Remedy:
|
F07751 Drive: valve does not respond | Cause: A valve with a valve feedback signal was parameterized (p0218.2 = 1), however the valve does not follow the setpoint. Remedy:
|
F07752 (A) Drive: Piston position not possible | Cause: The piston was calibrated (p0476 not equal to 0) and the absolute position is available (p1407.7 = 1). However, the piston position (r0094) is not plausible (negative or higher than the stroke in p0313). Remedy:
|
F07753 (N, A) Drive: No valid pressure actual value available | Cause: The function “force controller”, “force limiting” or “stiction compensation” is activated (p1400), and at least one of the two pressure sensors required is not supplying a valid value. Remedy:
|
F07754 Drive: Incorrect shutoff valve configuration | Cause: An incorrect shutoff valve configuration was detected. Remedy:
|
F07755 (N, A) Drive: travel to fixed end stop without force controller | Cause: The function “Travel to fixed end stop” (p1545) was selected, although no “Force controller” or “Force limiting” has been activated (p1400). With these settings, the drive would be traversed with maximum force against the end stop. Remedy:
|
F07756 Drive: Filter natural frequency > Shannon frequency | Cause: One of the filter natural frequencies is greater than the Shannon frequency, which is calculated as 0.5 / p0115[0]. Remedy:
|
F07800 Drive: No power unit present | Cause: The power unit parameters cannot be read or no parameters are stored in the power unit. It is possible that the DRIVE-CLiQ cable between the Control Unit and power unit is interrupted or defective, or an incorrect topology was selected. Remedy:
|
F07801 Drive: Motor overcurrent | Cause: The permissible motor limit current was exceeded. Remedy:
|
F07802 Drive: Infeed or power unit not ready | Cause: After an internal power-on command, the infeed or drive does not signal ready. Remedy:
|
A07805 (N) Infeed: Power unit overload I2t / Drive: Power unit overload I2t | Cause: Alarm threshold for I2t overload (p0294) of the power unit exceeded. The response parameterized in p0290 becomes active. Remedy:
|
F07807 Drive: Short-circuit/ground fault detected | Cause: A phase-phase short-circuit or ground fault was detected at the motor-side output terminals of the converter. Fault value (r0949, interpret decimal) indicates the type of fault. Remedy:
|
F07808 (A) HF damping module: damping not ready | Cause: When switching on or in the switched-on state, the HF damping module does not return a ready signal. Remedy:
|
F07810 Drive: Power unit EEPROM without rated data | Cause: No rated data are stored in the power unit EEPROM. Remedy:
|
F07815 Drive: Power unit has been changed | Cause: The code number of the actual power unit does not match the saved number. Remedy:
|
A07820 Drive: Temperature sensor not connected | Cause: The temperature sensor for monitoring the motor temperature, specified in p0600, is not available. Remedy:
|
A07825 (N) Drive: Simulation mode activated | Cause: The simulation mode is activated. The drive can only be powered up if the DC link voltage is less than 40 V. Remedy:
|
F07826 Drive: DC link voltage for simulation operation too high | Cause: The simulation mode is activated and the DC link voltage is greater than the permissible value of 40 V. Remedy:
|
F07840 Drive: Infeed operation missing | Cause: The signal “infeed operation” is not present although the enable signals for the drive have been present for longer than the parameterized monitoring time (p0857). Remedy:
|
F07841 (A) Drive: Infeed operation withdrawn | Cause: The signal “infeed operation” was withdrawn in operation due to incorrect interconnection, disabled enable signals, or a fault in the infeed. 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 the following parameters: p2108, p3111, p3112. Remedy:
|
F07890 Internal voltage protection / internal armature short-circuit with STO active | Cause: The internal armature short-circuit (p1231 = 4) is not possible as Safe Torque Off (STO) is enabled. The pulses cannot be enabled. Remedy:
|
F07898 Drive: flying restart unsuccessful due to excessively low flux | Cause: While identifying the rotor position of a separately-excited synchronous motor based on voltage measurement, after the excitation time had elapsed, the flux was too low. Remedy:
|
A07899 (N) Drive: Stall monitoring not possible | Cause: Stall monitoring is not possible, because a change was made into the open-loop speed controlled mode before the wait time p2177 had expired under specific conditions. Remedy:
|
F07900 (N, A) Drive: Motor blocked/speed controller at its limit | Cause: Motor has been operating at the torque limit longer than the time specified in p2177 and below the speed threshold in p2175. This can also be initiated if the speed actual value is oscillating. Remedy:
|
F07901 Drive: Motor overspeed | Cause: The maximum permissible speed was either positively or negatively exceeded. Remedy:
|
F07902 (N, A) Drive: Motor stalled | Cause: The system has identified that the motor has stalled for a time longer than is set in p2178. Remedy:
|
A07903 Drive: Motor speed deviation | Cause: The absolute value of the speed difference from the two setpoints (p2151, p2154) and the speed actual value (r2169) exceeds the tolerance threshold (p2163) longer than tolerated. Remedy:
|
F07904 (N, A) External armature short-circuit: Contactor feedback signal “Closed” missing | Cause: When closing, the contactor feedback signal (p1235) did not issue the signal “Closed” (r1239.1 = 1) within the monitoring time (p1236). Remedy:
|
F07905 (N, A) External armature short-circuit: Contactor feedback signal “Open” missing | Cause: When opening, the contactor feedback signal (p1235) did not issue the signal “Open” (r1239.1 = 0) within the monitoring time (p1236). Remedy:
|
F07906 Armature short-circuit / internal voltage protection: Parameterization error | Cause: The armature short-circuit is incorrectly parameterized. Remedy:
|
F07907 Internal armature short-circuit: Motor terminals are not at zero potential after pulse suppression | Cause: The function “Internal voltage protection” (p1231 = 3) was activated. Important operational conditions were not met, such as using short-circuit proof motors, ensuring sufficient current conduction capability of the Motor Module, and providing a stable 24 V power supply. Remedy:
|
A07908 Internal armature short-circuit active | Cause: The Motor Module signals that the motor is short-circuited through the power semiconductors (r1239.5 = 1). The pulses cannot be enabled. The internal armature short-circuit is selected (p1231 = 4). Remedy:
|
F07909 Internal voltage protection: De-activation only effective after POWER ON | Cause: The de-activation of the internal voltage protection (p1231 not equal to 3) only becomes effective after POWER ON. The status signal r1239.6 = 1 indicates that the internal voltage protection is ready. Remedy:
|
A07910 (N) Drive: Motor overtemperature | Cause: KTY: The motor temperature has exceeded the alarm threshold (p0604, p0616). Remedy:
|
F07913 Excitation current outside the tolerance range | Cause: The difference between the excitation current actual value and setpoint has exceeded the tolerance. Remedy:
|
F07914 Flux out of tolerance | Cause: The difference between the flux actual value and setpoint has exceeded the tolerance. The fault is only issued after the delay time in p3206 has expired. Remedy:
|
A07918 (N) Three-phase setpoint generator operation selected/active | Cause: Only for separately excited synchronous motors (p0300 = 5): The actual open-loop/closed-loop control mode is I/f control (open-loop) with a fixed current (p1300 = 18). The control dynamic performance is very limited in this mode. Remedy:
|
A07920 Drive: Torque/speed too low | Cause: The torque deviates from the torque/speed envelope characteristic (too low). Remedy:
|
A07921 Drive: Torque/speed too high | Cause: The torque deviates from the torque/speed envelope characteristic (too high). Remedy:
|
A07922 Drive: Torque/speed out of tolerance | Cause: The torque deviates from the torque/speed envelope characteristic. Remedy:
|
F07923 Drive: Torque/speed too low | Cause: The torque deviates from the torque/speed envelope characteristic (too low). Remedy:
|
F07924 Drive: Torque/speed too high | Cause: The torque deviates from the torque/speed envelope characteristic (too high). Remedy:
|
F07925 Drive: Torque/speed out of tolerance | Cause: The torque deviates from the torque/speed envelope characteristic. Remedy:
|
A07926 Drive: Envelope curve parameter invalid | Cause: Invalid parameter values were entered for the envelope characteristic of the load monitoring. Specific rules for speed and torque thresholds were not followed. Remedy:
|
A07927 DC braking active | Cause: The motor is braked with DC current. DC braking is active due to a message with response DCBRK or activation via binector input p1230. Remedy:
|
F07928 Internal voltage protection initiated | Cause: The Motor Module signals that the motor is short-circuited through the power semiconductors (r1239.5 = 1). The internal voltage protection is selected (p1231 = 3). The armature short-circuit is activated and response OFF2 is initiated if the DC link voltage exceeds 800 V. Remedy:
|
F07930 Drive: Brake control error | Cause: The Control Unit has detected a brake control error. Remedy:
|
A07931 (F, N) Brake does not open | Cause: This alarm is output for r1229.4 = 1. Remedy:
|
A07932 Brake does not close | Cause: This alarm is output for r1229.5 = 1. OFF1/OFF3 are suppressed to prevent the drive accelerating by a load that drives the motor. Remedy:
|
F07934 (N) Drive: S120 Combi motor holding brake configuration | Cause: A connected motor holding brake has been detected with an S120 Combi, but it has not been assigned to just one Combi feed drive, and therefore brake control is not configured correctly. Remedy:
|
F07935 (N) Drive: Incorrect motor holding brake configuration | Cause: An incorrect motor holding brake configuration was detected. Remedy:
|
F07937 (N) Drive: Speed deviation between motor model and external speed | Cause: The absolute value of the speed difference from the two actual values (r2169, r1443) exceeds the tolerance threshold (p3236) for longer than permitted (p3238). Remedy:
|
F07940 Sync-line-drive: Synchronizing error | Cause: After synchronization has been completed, the phase difference (r3808) is greater than the threshold value. Also occurs if the enable signal is withdrawn while the closed-loop phase control is active. Remedy:
|
A07941 Sync-line-drive: Target frequency not permissible | Cause: The target frequency is outside the permissible value range. Remedy:
|
A07942 Sync-line-drive: Setpoint frequency is completely different than the target frequency | Cause: There is a considerable difference between the setpoint frequency and the target frequency. The deviation that can be tolerated is set in p3806. Remedy:
|
A07943 Sync-line-drive: Synchronization not permitted | Cause: Synchronization is not permitted. Remedy:
|
F07950 (A) Drive: Incorrect motor parameter | Cause: The motor parameters were incorrectly entered while commissioning (e.g. p0300 = 0, no motor) or the motor type is not supported for the control mode. Remedy:
|
F07955 Drive: Motor has been changed | Cause: The code number of the actual motor with DRIVE-CLiQ does not match the saved number. Remedy:
|
F07956 (A) Drive: Motor code does not match the list (catalog) motor | Cause: The motor code of the connected motor with DRIVE-CLiQ does not match the possible list motor types (see selection in p0300). The connected motor might not be supported by this firmware version. Remedy:
|
A07960 Drive: Incorrect friction characteristic | Cause: The friction characteristic is incorrect. Remedy:
|
A07961 Drive: Friction characteristic record activated | Cause: The automatic friction characteristic record is activated. The friction characteristic is recorded at the next power-on command. When plotting the friction characteristic, it is not possible to save the parameters (p0971, p0977). Remedy:
|
F07963 Drive: Friction characteristic record interrupted | Cause: The conditions to record the friction characteristic are not fulfilled. Remedy:
|
A07965 (N) Drive: Save required | Cause: The angular commutation offset (p0431) was re-defined and has still not been saved. In order to permanently accept the new value, it must be saved in a non-volatile fashion (p0971, p0977). Remedy:
|
F07966 Drive: Check the commutation angle | Cause: The speed actual value was inverted and the associated angular commutation offset is not equal to zero and is therefore possibly incorrect. Remedy:
|
F07967 Drive: Automatic encoder adjustment/pole position identification incorrect | Cause: A fault has occurred during the automatic encoder adjustment or the pole position identification. Remedy:
|
F07968 Drive: Lq-Ld measurement incorrect | Cause: A fault has occurred during the Lq-Ld measurement. Remedy:
|
F07969 Drive: Incorrect pole position identification | Cause: A fault has occurred during the pole position identification routine. Remedy:
|
F07970 Drive: Automatic encoder adjustment incorrect | Cause: A fault has occurred during the automatic encoder adjustment. Remedy:
|
A07971 (N) Drive: Angular commutation offset determination activated | Cause: The automatic determination of the angular commutation offset (encoder adjustment) is activated (p1990 = 1 or 3). The automatic determination is carried out at the next power-on command. Remedy:
|
A07975 (N) Drive: Travel to the zero mark – setpoint input expected | Cause: The zero mark must be evaluated in order to adjust the encoder. It is expected that a speed or torque setpoint is entered. Remedy:
|
A07976 Drive: Fine encoder calibration activated | Cause: The alarm indicates the phases of the fine encoder calibration using the alarm value. Remedy:
|
A07980 Drive: Rotating measurement activated | Cause: The rotating measurement is activated. For the rotating measurement, the motor can accelerate up to the maximum speed and with maximum torque. Only the parameterized current limit (p0640) and the maximum speed (p1082) are effective. The behavior of the motor can be influenced using the direction inhibit (p1959.14, p1959.15) and the ramp-up/ramp-down time (p1958). The rotating measurement is carried out at the next power-on command. Remedy: Not necessary. The alarm automatically disappears after the rotating measurement has been successfully completed or for the setting p1960 = 0. |
A07981 Drive: Enable signals for the rotating measurement missing | Cause: The rotating measurement cannot be started due to missing enable signals. For p1959.13 = 1, the following applies: – enable signals for the ramp-function generator missing (see p1140… p1142). – enable signals for the speed controller integrator missing (see p1476, p1477). Remedy: – acknowledge faults that are present. – establish missing enable signals. |
F07982 Drive: Rotating measurement encoder test | Cause: A fault has occurred during the encoder test. Fault value (r0949, interpret decimal): 1: The speed did not reach a steady-state condition. 2: The speed setpoint was not able to be approached as the minimum limiting is active. 3: The speed setpoint was not able to be approached as the suppression (skip) bandwidth is active. 4: The speed setpoint was not able to be approached as the maximum limiting is active. 5: The encoder does not supply a signal. 6: Incorrect polarity. 7: Incorrect pulse number. 8: Noise in the encoder signal or speed controller unstable. 9: Voltage Sensing Module (VSM) incorrectly connected. Remedy: For fault value = 1: – check the motor parameters. – carry out a motor data identification routine (p1910). – if required, reduce the dynamic factor (p1967 < 25 %). For fault value = 2: – adapt the speed setpoint (p1965) or adapt the minimum limit (p1080). For fault value = 3: – adapt the speed setpoint (p1965) or suppression (skip) bandwidths (p1091 … p1094, p1101). For fault value = 4: – adapt the speed setpoint (p1965) or maximum limit (p1082, p1083 and p1086). For fault value = 5: – check the encoder connection. If required, replace the encoder. For fault value = 6: – check the connection assignment of the encoder cable. Adapt the polarity (p0410). For fault value = 7: – adapt the pulse number (p0408). For fault value = 8: – check the encoder connection and encoder cable. It is possible that there is a problem associated with the ground connection. – reduce the dynamic response of the speed controller (p1460, p1462 and p1470, p1472). For fault value = 9: – check the connections of the Voltage Sensing Module (VSM). |
F07983 Drive: Rotating measurement saturation characteristic | Cause: A fault has occurred while determining the saturation characteristic. Fault value (r0949, interpret decimal): 1: The speed did not reach a steady-state condition. 2: The rotor flux did not reach a steady-state condition. 3: The adaptation circuit did not reach a steady-state condition. 4: The adaptation circuit was not enabled. Remedy: For fault value = 1: – the total drive moment of inertia is far higher than that of the motor (p0341, p0342). De-select rotating measurement (p1960), enter the moment of inertia p0342, re-calculate the speed controller p0340 = 4 and repeat the measurement. Re fault value = 1 … 2: – increase the measuring speed (p1961) and repeat the measurement. Re fault value = 1 … 4: – check the motor parameters (rating plate data). After the change: Calculate p0340 = 3. – check the moment of inertia (p0341, p0342). After the change: Calculate p0340 = 3. – carry out a motor data identification routine (p1910). – if required, reduce the dynamic factor (p1967 < 25 %). For fault value = 5: – the speed setpoint (p1961) is too high. Reduce the speed. For fault value = 6: – adapt the speed setpoint (p1961) or minimum limiting (p1080). For fault value = 7: – adapt the speed setpoint (p1961) or suppression (skip) bandwidths (p1091 … p1094, p1101). For fault value = 8: – adapt the speed setpoint (p1961) or maximum limit (p1082, p1083 and p1086). Re fault value = 9, 10: – the measurement was carried out at an operating point where the load torque is too high. Select a more suitable operating point, either by changing the speed setpoint (p1961) or by reducing the load torque. The load torque may not be varied while making measurements. |
F07984 Drive: Speed controller optimization, moment of inertia | Cause: A fault has occurred while identifying the moment of inertia. Fault value (r0949, interpret decimal): 1: The speed did not reach a steady-state condition. 2: The speed setpoint was not able to be approached as the minimum limiting is active. 3. The speed setpoint was not able to be approached as the suppression (skip) bandwidth is active. 4. The speed setpoint was not able to be approached as the maximum limiting is active. 5: It is not possible to increase the speed by 10% as the minimum limiting is active. 6: It is not possible to increase the speed by 10% as the suppression (skip) bandwidth is active. 7: It is not possible to increase the speed by 10% as the maximum limiting is active. 8: The torque difference after the speed setpoint step is too low in order to be able to still reliably identify the moment of inertia. 9: Too few data to be able to reliably identify the moment of inertia. 10: After the setpoint step, the speed either changed too little or in the incorrect direction. 11: The identified moment of inertia is not plausible. Remedy: For fault value = 1: – check the motor parameters (rating plate data). After the change: Calculate p0340 = 3. – check the moment of inertia (p0341, p0342). After the change: Calculate p0340 = 3. – carry out a motor data identification routine (p1910). – if required, reduce the dynamic factor (p1967 < 25 %). Re fault value = 2, 5: – adapt the speed setpoint (p1965) or adapt the minimum limit (p1080). Re fault value = 3, 6: – adapt the speed setpoint (p1965) or suppression (skip) bandwidths (p1091 … p1094, p1101). Re fault value = 4, 7: – adapt the speed setpoint (p1965) or maximum limit (p1082, p1083 and p1086). For fault value = 8: – the total drive moment of inertia is far higher than that of the motor (refer to p0341, p0342). De-select rotating measurement (p1960), enter the moment of inertia p0342, re-calculate the speed controller p0340 = 4 and repeat the measurement. For fault value = 9: – check the moment of inertia (p0341, p0342). After the change, re-calculate (p0340 = 3 or 4). For fault value = 10: – check the moment of inertia (p0341, p0342). After the change: Calculate p0340 = 3. |
F07985 Drive: Speed controller optimization (oscillation test) | Cause: A fault has occurred during the vibration test. Fault value (r0949, interpret decimal): 1: The speed did not reach a steady-state condition. 2: The speed setpoint was not able to be approached as the minimum limiting is active. 3: The speed setpoint was not able to be approached as the suppression (skip) bandwidth is active. 4: The speed setpoint was not able to be approached as the maximum limiting is active. 5: Torque limits too low for a torque step. 6: No suitable speed controller setting was found. Remedy: For fault value = 1: – check the motor parameters (rating plate data). After the change: Calculate p0340 = 3. – check the moment of inertia (p0341, p0342). After the change: Calculate p0340 = 3. – carry out a motor data identification routine (p1910). – if required, reduce the dynamic factor (p1967 < 25 %). For fault value = 2: – adapt the speed setpoint (p1965) or adapt the minimum limit (p1080). For fault value = 3: – adapt the speed setpoint (p1965) or suppression (skip) bandwidths (p1091 … p1094, p1101). For fault value = 4: – adapt the speed setpoint (p1965) or maximum limit (p1082, p1083 and p1086). For fault value = 5: – increase the torque limits (e.g. p1520, p1521). For fault value = 6: – reduce the dynamic factor (p1967). – disable the vibration test (p1959.4 = 0) and repeat the rotating measurement. |
F07986 Drive: Rotating measurement ramp-function generator | Cause: During the rotating measurements, problems with the ramp-function generator occurred. Fault value (r0949, interpret decimal): 1: The positive and negative directions are inhibited. Remedy: For fault value = 1: Enable the direction (p1110 or p1111). |
A07987 Drive: Rotating measurement, no encoder available | Cause: No encoder available. The rotating measurement was carried out without encoder. Remedy: Connect encoder or select p1960 = 1, 3. |
F07988 Drive: Rotating measurement, no configuration selected | Cause: When configuring the rotating measurement (p1959), no function was selected. Remedy: Select at least one function for automatic optimization of the speed controller (p1959). |
F07989 Drive: Rotating measurement leakage inductance (q-axis) | Cause: An error has occurred while measuring the dynamic leakage inductance. Fault value (r0949, interpret decimal): 1: The speed did not reach a steady-state condition. 2: The speed setpoint was not able to be approached as the minimum limiting is active. 3: The speed setpoint was not able to be approached as the suppression (skip) bandwidth is active. 4: The speed setpoint was not able to be approached as the maximum limiting is active. 5: The 100% flux setpoint was not reached. 6: No Lq measurement possible because field weakening is active. 7: Speed actual value exceeds the maximum speed p1082 or 75% of the rated motor speed. 8: Speed actual value is below 2% of the rated motor speed. Remedy: For fault value = 1: – check the motor parameters. – carry out a motor data identification routine (p1910). – if required, reduce the dynamic factor (p1967 < 25 %). For fault value = 2: – adapt the speed setpoint (p1965) or adapt the minimum limit (p1080). For fault value = 3: – adapt the speed setpoint (p1965) or suppression (skip) bandwidths (p1091 … p1094, p1101). For fault value = 4: – adapt the speed setpoint (p1965) or maximum limit (p1082, p1083 and p1086). For fault value = 5: – flux setpoint p1570 = 100 % and current setpoint p1610 = 0 % kept during the Lq measurement. For fault value = 6: – reduce the regenerative load so that the drive does not reach field weakening when accelerating. – reduce p1965 so that the q leakage inductance is recorded at lower speeds. For fault value = 7: – increase p1082 if this is technically permissible. – reduce p1965 so that the q leakage inductance is recorded at lower speeds. For fault value = 8: – reduce the load when motoring so that the drive is not braked. – increase p1965 so that the measurement may be taken at higher speeds. |
F07990 Drive: Incorrect motor data identification | Cause: A fault has occurred during the identification routine. Fault value (r0949, interpret decimal): 10: Data set changeover during motor data identification. 101: Voltage amplitude even at 30% maximum current amplitude is too low to measure the inductance. 102, 104: Voltage limiting while measuring the inductance. 103: Maximum frequency exceeded during the rotating inductance measurement. 110: Motor not finely synchronized before the rotating measurement. 111: The zero mark is not received within 2 revolutions. 112: Fine synchronization is not realized within 8 seconds after the zero mark has been passed. 113: The power, torque or current limit is zero. 115: U/f control is active. 120: Error when evaluating the magnetizing inductance. 125: Cable resistance greater than the total resistance. 126: Series inductance greater than the total leakage inductance. 127: Identified leakage inductance negative. 128: Identified stator resistance negative. 129: Identified rotor resistance negative. 130: Drive data set changeover during the motor data identification routine. 140: The setpoint channel inhibits both directions. 160: Accelerating when determining kT, moment of inertia or reluctance torque too short or the accelerating time is too long. 173: Internal problem. 180: Identification speed (maximum speed, rated speed, 0.9 x p0348) less than p1755. 190: Speed setpoint not equal to zero. 191: An actual speed of zero is not reached. 192: Speed setpoint not reached. 193: Inadmissible motion of the motor when identifying the voltage emulation error. 194: Supplementary torque (r1515) not equal to zero. 195: Closed-loop torque control active. 200, 201: Not possible to identify the voltage emulation error characteristic of the drive converter (p1952, p1953). Remedy: For fault value = 10: – do not initiate a data set changeover during the motor data identification. For fault value = 101: – increase current limit (p0640) or torque limit (p1520, p1521). – check current controller gain (p1715). – reduce current controller sampling time (p0115). – suppress meas. (p1909, p1959). Re fault value = 102, 104: – reduce current limit (p0640). – check current controller P gain. – suppress meas. (p1909, p1959). For fault value = 103: – increase external moment of inertia (if possible). – reduce current controller sampling time (p0115). – suppress meas. (p1909, p1959). For fault value = 110: – before rotating measurement, traverse motor over zero mark. For fault value = 111: – it is possible that encoder does not have zero mark. Correct setting in p0404.15. – encoder pulse number was incorrectly entered. Correct setting in p0408. – if zero mark signal is defective, replace encoder. For fault value = 112: – upgrade encoder software. For fault value = 113: – check the limits (p0640, p1520, p1521, p1530, p1531), correct the zero values. For fault value = 115: – de-select U/f control (p1317 = 0). For fault value = 120: – check current controller P gain (p1715) and if required, reduce. – increase the pulse frequency (p1800). For fault value = 125: – reduce cable resistance (p0352). For fault value = 126: – reduce series inductance (p0353). Re fault = 127, 128, 129: – it is possible that current controller is oscillating. Reduce p1715 before next measurement. For fault value = 130: – do not initiate a drive data set changeover during motor ident. routine. For fault value = 140: – before the measurement, enable at least one direction (p1110 = 0 or p1111 = 0 or p1959.14 = 1 or p1959.15 = 1). For fault value = 160: – extend accelerating time when determining kT, moment of inertia and reluctance torque, e.g. by increasing max. speed (p1082), increasing moment of inertia or reducing max. current (p0640). – in encoderless operation with load moment of inertia, parameterize the load moment of inertia (p1498). – reduce the ramp-up time (p1958). – increase speed controller P-gain (p1460). – suppress meas. (p1959). For fault value = 180: – increase max. speed (p1082). – reduce p1755. – suppress meas. (p1909, p1959). For fault value = 190: – set speed setpoint to zero. For fault value = 191: – do not start motor data identification routine while motor is still rotating. For fault value = 192: – check closed-loop speed control (motor rotor may be locked or closed-loop speed control is not functioning). – for p1215 = 1, 3 (brake the same as the sequence control) check the control sense (p0410.0). – ensure that enable signals are present during measurement. – remove any pulling loads from motor. – increase max. current (p0640). – reduce max. speed (p1082). – suppress meas. (p1959). For fault value = 193: – the motor has moved through more than 5° electrical (r0093). Lock motor rotor at one of these pole position angles (r0093): 90°, 210° or 330° (+/-5°) and then start identification. For fault value = 194: – switch out all supplementary torques (e.g. Cl: p1511). – for hanging/suspended axes: Lock motor rotor at one of these pole position angles (r0093): 90°, 210° or 330° (+/- 1°) and then start identification. For fault value = 195: – de-select closed-loop torque control (p1300 = 21 or 20, or set the signal source in p1501 to a 0 signal). Re fault value = 200, 201: – set pulse frequency to 0.5 x current controller frequency (e.g. 4 kHz for a current controller sampling time = 125 us). – reduce cable length between Motor Module and motor. – read-out measured values (r1950, r1951) and therefore determine suitable values for p1952, p1953 according to your own estimation. |
F07990 Drive: Incorrect motor data identification | Cause: A fault has occurred during the identification routine. Fault value (r0949, interpret decimal): 1: Current limit value reached. 2: Identified stator resistance lies outside the expected range 0.1 … 100% of Zn. 3: Identified rotor resistance lies outside the expected range 0.1 … 100% of Zn. Separately excited synchronous motors: damping resistance outside 1.0…15 % of Zn. 4: Identified stator reactance lies outside the expected range 50 … 900 % of Zn. Separately excited synchronous motors: stator reactance outside 20 …500 % of Zn. 5: Identified magnetizing reactance lies outside the expected range 50 … 900 % of Zn. Separately excited synchronous motors: magnetizing reactance outside 20 …500 % of Zn. 6: Identified rotor time constant lies outside the expected range 10 ms … 5 s. Separately-excited synchronous motors: damping time constant outside of 5 ms … 1 s. 7: Identified total leakage reactance lies outside the expected range 4 … 100 % of Zn. 8: Identified stator leakage reactance lies outside the expected range 2 … 50 % of Zn. Separately excited synchronous motors: stator leakage reactance outside 2 …40 % of Zn. 9: Identified rotor leakage reactance lies outside the expected range 2 … 50 % of Zn. Separately excited synchronous motors: damping leakage reactance outside 1.5 …20 % of Zn. 10: Motor has been incorrectly connected. 11: Motor shaft rotates. 12: Ground fault detected. 15: Pulse inhibit occurred during motor data identification 20: Identified threshold voltage of the semiconductor devices lies outside the expected range 0 … 10 V. 30: Current controller in voltage limiting. 40: At least one identification contains errors. The identified parameters are not saved to prevent inconsistencies. 50: The selected sampling time is too low for the motor identification (p0115[0]). Remedy: Re fault value = 1 … 40: – check whether motor data have been correctly entered in p0300, p0304 … p0311. – is there an appropriate relationship between the motor power rating and that of the Motor Module? The ratio of the Motor Module to the rated motor current should not be less than 0.5 and not be greater than 4. – check configuration (star-delta). Re fault value = 11 in addition: – Deactivate oscillation monitoring (p1909.7 = 1). For fault value = 2: – for parallel circuits, check the motor winding system in p7003. If, for power units connected in parallel, a motor is specified with a single-winding system (p7003 = 0), although a multi-winding system is being used, then a large proportion of the stator resistance is interpreted as feeder cable resistance and entered in p0352. Re fault value = 4, 7: – check whether inductances are correctly set in p0233 and p0353. – check whether motor has been correctly connected (star-delta). – Set p1909.0 = 1. For fault value = 12: – check the power cable connections. – check the motor. – check the CT. For fault value = 50: – Perform a motor data identification with a higher sampling time, and after this, change to the required higher sampling time (p0115[0]). |
F07990 Drive: Identification incorrect | Cause: A fault has occurred during the identification routine. Fault value (r0949, interpret decimal): 1: piston calibration without absolute position (p1407.3 = 0). 2: determining the control sense without moving in both directions. 3: determining the control sense without a clear result. 4: determining the valve offset without moving. 5: traversing range identification without absolute position or piston calibration. 6: The measured piston stroke differs from the parameterized piston stroke (p0313) by more than 20 %. 7: For the characteristic measurement, the drive comes to a standstill before reaching the parameterized free distance. 8: The loop gain of the force controller is incorrect. At the positive end stop, pA (r0067) < pB (r0068). 100: Position and speed actual value inversion differ (p0410). 101: Start of measuring range > end of measuring range (p1955[0] > p1955[1]). 102: Minimum measuring travel > maximum measuring travel (p1956[0] > p1956[1]). 190: Velocity setpoint is not zero. Remedy: For fault value = 1: – home the drive before calibrating the piston (p1407.3 must be = 1). Re fault value = 2, 3: – drive must be able to be moved. – check system pressure and shutoff valves. – increase the settling time (p1958[1]). For fault value = 4: – drive must be able to be moved. – check system pressure and shutoff valves. For fault value = 5: – home the drive before the traversing range identification (p1407.3 must be = 1) and calibrate the piston (p1909.1 = 1 or p1959.2 = 1 and p1960 = 1). For fault value = 6: – there is an obstruction in the traversing range. If necessary, remove the obstruction. If the measuring travel with obstruction is sufficient, no measure has to be applied. – the piston stroke was incorrectly parameterized. If the actual piston stroke is less than the parameterized stroke, correct it (p0313). A piston stroke that has been parameterized too low, is automatically corrected. For fault value = 7: – piston calibration was incorrectly carried out. Correct the piston calibration or automatically calibrate it (p1959.2 = 1 and p1960 = 1). – the minimum or maximum parameterized measuring travel cannot be traversed as there is an obstruction in the path or the piston stroke was incorrectly parameterized. If required, correct the measuring travel (p1956[0], p1956[1]), correct the piston stroke or automatically calibrate it (p1959.x = 1 and p1960 = 1). – drive cannot be traversed, because the shutoff valve does not open, the system pressure is not available, encoder or valve are not connected. Check the shutoff valve, system pressure, encoder and valve connection. For fault value = 8: – interchange the connectors of pressure sensors A and B or invert the direction of motion (invert p1820 and p0410) and repeat the complete moving measurement. – check the reference values for pressure sensors (p0240, p0242). For fault value = 100: – Set the position and speed actual value inversion the same (p0410 = 0 or p0410 = 3). For fault value = 101: – Start of measuring range must be parameterized less than the end of measuring range (p1955[0] > p1955[1]). For fault value = 102: – Minimum measuring travel must be parameterized less than the maximum measuring travel (p1956[0] > p1956[1]). For fault value = 190: – During the identification, the velocity setpoint must be zero. |
A07991 (N) Drive: Motor data identification activated | Cause: The motor data identification routine is activated. The motor data identification routine is carried out at the next power-on command. Remedy: Not necessary. The alarm automatically disappears after the motor data identification routine has been successfully completed or for the setting p1910 = 0 or p1960 = 0. If a POWER ON or a warm restart is performed with motor data identification selected, the motor data identification request will be lost. If motor data identification is required, it will need to be selected again manually following ramp-up. |
F07993 Drive: Incorrect direction of rotation of the field or encoder actual value inversion | Cause: Either the direction of the rotating field or the encoder actual value has an incorrect sign. The motor data identification automatically changed the actual value inversion (p0410) in order to correct the control sense. This can result in a direction of rotation change. Remedy: To acknowledge this fault, the correctness of the direction of rotation must first be acknowledged with p1910 = -2. Check the direction of rotation (also for the position controller, if one is being used). If the direction of rotation is correct, the following applies: No additional measures are required (except set p1910 = -2 and acknowledge fault). If the direction of rotation is incorrect, the following applies: To change the direction of rotation, two phases must be interchanged and the motor identification routine must be repeated. |
A07994 (F, N) Drive: motor data identification not performed | Cause: The “vector control” mode has been selected and a motor data identification has still not been performed. The alarm is initiated when changing the drive data set (see r0051) in the following cases: – vector control is parameterized in the actual drive data set (p1300 >= 20). and – motor data identification has still not been performed in the actual drive data set (see r3925). Remedy: – Perform motor data identification (see p1900). – If required, parameterize “U/f control” (p1300 < 20). – switch over to a drive data set, in which the conditions do not apply. |
F07995 Drive: Pole position identification not successful | Cause: The pole position identification routine was unsuccessful. Fault value (r0949, interpret decimal): 1: No current is established. 2: The starting current is not zero. 3: The selected max. distance was exceeded (p1981). 4x: The measuring signal does not permit a clear evaluation. 5: The max. current was exceeded during the measurement. 6: The current measurement must be re-calibrated. 7x: The Sensor Module does not support the pole position identification routine. 8: The pole position identification routine current required is greater than the max. current. 9: The set pole position identification routine current is zero. 10: Data set changeover during the pole position identification. 11: The encoder adjustment to determine the commutation angle is active (p1990 = 1) and the encoder without zero mark is not finely synchronized or does not have any valid data. 100: Motion-based pole position identification, 1st and 2nd measurement different. Motor blocked or current (p1993) too low. 101: Motion-based position position identification, insufficient motion, motor blocked or current (p1993) too low. 102: Motion-based pole position identification, brake is being used and is closed. The motion-based position position identification in conjunction with the brake is not permitted. 103: Motion-based pole position identification without encoder. 104: Motion-based pole position identification, speed actual value not zero after stabilizing time. 200: Elasticity-based pole position identification, internal error in the arctan calculation (0 / 0 ). 201: Elasticity-based pole position identification, too few measuring points that can be evaluated. 202: Elasticity-based pole position identification, outliers in the measurement series. 203: Elasticity-based pole position identification, maximum rotation without current. 204: Elasticity-based pole position identification, no positive edge found. 205: Elasticity-based pole position identification, the result of the Fourier transformation differs by more than 480 ° electrical / p3093 from the rough estimate. 206: Elasticity-based pole position identification, plausibility test unsuccessful. 207: Elasticity-based pole position identification, no negative measured value found. 208: Elasticity-based pole position identification, measuring current is 0. 209: Elasticity-based pole position identification, the selected max. distance was exceeded (p3095). 210: Elasticity-based pole position identification without encoder. 250 … 260: Elasticity-based pole position identification, more than 3 attempts have been made and fault value 200 … 210 output. Remedy: For fault value = 1: – check the motor connection and DC link voltage. – for the following parameters, set practical values that are not zero (p0325, p0329). Re fault value = 1, 2: – in the case of a large computing time load (e.g., 6 drives with Safety Integrated), set the computing dead time of the current controller to late transfers (p0117 = 3). For fault value = 3: – increase the max. distance (p1981). – reduce the currents for the pole position identification routine (p0325, p0329). – stop the motor in order to carry out the pole position identification routine. For fault value = 5: – reduce the currents for the pole position identification routine (p0325, p0329). For fault value = 6: – re-calibrate the Motor Module. For fault value = 8: – reduce the currents for the pole position identification routine (p0329, p0325, p1993). – the power unit cannot provide the necessary pole position identification routine current (p0209 < p0329, p0325, p1993), replace the power unit with a power unit with a higher max. current. For fault value = 9: – enter a value not equal to zero in the pole position identification routine current (p0329, p0325, p1993). For fault value = 10: – do not initiate a data set changeover during the pole position identification. For fault value = 11: – for incremental encoders without commutation with zero mark (p0404.15 = 0), it does not make sense to adjust the encoder to determine the commutation angle (p1990 = 1). In this case, the function should be de-selected (p1990 = 0) or, for an encoder with suitable zero mark, commutation with zero mark should be selected (p0404.15 = 1). – for absolute encoders, only adjust the encoder to determine the commutation angle (p1990 = 1) if the encoder supplies commutation information and is finely synchronized (p1992.8 = 1 and p1992.10 = 1). The encoder is possibly parked, de-activated (p0145), not ready for operation or signals a fault condition. – de-select the encoder adjustment to determine the commutation angle (set p1990 to 0). Re fault value = 40 … 49: – increase the currents for the pole position identification routine (p0325, p0329). – stop the motor in order to carry out the pole position identification routine. – select another technique for pole position identification routine (p1980). – use another motor, absolute encoder or Hall sensors. Re fault value = 70 … 79: – upgrade the software in the Sensor Module. Re fault value = 100, 101: – check and ensure that the motor is free to move. – increase the current for motion-based pole position identification (p1993). For fault value = 102: – if the motor is to be operated with a brake: Select a different technique to identify the pole position (p1980). – if the motor can be operated without a brake: Open the brake (p1215 = 2). For fault value = 103: – the motion-based pole position identification can only be carried out using an encoder. Connect an encoder or select another technique for pole position identification routine (p1980). For fault value = 104: – pole position identification, increase the smoothing time, motion-based (p1997). – pole position identification, increase the rise time, motion-based (p1994). – pole position identification, check the gain, motion-based (p1995). – pole position identification, check the integral time, motion-based (p1996). – for motor encoders with track A/B sq-wave (p0404.3 = 1) and flank time measurement (p0430.20 = 0), disable the integral time (p1996 = 0). For fault value = 200: – check parameter setting (p3090 … p3096). For fault value = 201: – check parameter setting (p3090 … p3096). – reduce p3094. For fault value = 202: – check parameter setting (p3090 … p3096). – fault has occurred during the identification. Repeat the measurement. – check the brake or brake control. For fault value = 203: – check the brake or brake control. – check the measuring current (p3096). – increase p3094. For fault value = 204: – check parameter setting (p3090 … p3096). For fault value = 205: – check parameter setting (p3090 … p3096). For fault value = 206: – check parameter setting (p3090 … p3096). – fault has occurred during the identification. Repeat the measurement. – check the brake or brake control. For fault value = 207: – reduce the expected deflection (p3094). – increase the measuring current (p3096). For fault value = 208: – set the measuring current (p3096). For fault value = 209: – check parameter setting p3095. – check the brake or brake control. For fault value = 210: – the elasticity-based pole position identification can only be carried out using an encoder. Connect an encoder or select another technique for pole position identification routine (p1980). Re fault value = 250 … 260: – check parameter setting (p3090 … p3096, p1980). |
F07996 Drive: Pole position identification routine not carried out | Cause: In operation, the operating mode that requires a pole position identification was changed over, which is not possible in this state. – the drive was changed over, flying, from encoderless operation to operation with encoder without having previously carried out a pole position identification for the encoder. p1404 is then at a value between zero and the max. speed and the pulses in the speed range above p1404 were enabled without a pole position ident. routine having been previously carried out in operation with encoder. – in operation, an EDS changeover was made to an encoder where it is necessary to carry out a pole position identification. However, this has still not been carried out (p1982 = 1 or 2 and p1992.7 = 0). Remedy: – for a flying changeover between operation with and without encoder with pole position identification after POWER ON or commissioning (p0010 not equal to zero) enable the pulses once at zero speed. This means that the pole position identification routine is carried out and the result is available for operation. – carry out the EDS changeover with the pulses inhibited, or, before the changeover, carry out a pole position identification using this data set. |
A07998 Drive: Motor data identification active on another drive | Cause: The motor data identification is activated on the drive object specified in the fault value and interlocks the other drive objects so they cannot be powered up. Fault value (r0949, interpret decimal): Drive object with the active motor data identification. Remedy: – wait for the complete execution of the motor data identification of the drive object designated in the fault value. – de-select the motor data identification for the drive object designated in the fault value (p1910 = 0 or p1960 = 0). |
A07999 Drive: Motor data identification cannot be activated | Cause: Closed-loop control is enabled on a SERVO drive object type. To select motor data identification, pulses must be suppressed for all SERVO drive objects. Fault value (r0949, interpret decimal): Drive object with enabled closed-loop control. Remedy: Withdraw the pulse enable on all drives and re-activate the motor data identification. |
F08000 (N, A) TB: +/-15 V power supply faulted | Cause: Terminal Board 30 detects an incorrect internal power supply voltage. Fault value (r0949, interpret decimal): 0: Error when testing the monitoring circuit. 1: Fault in normal operation. Remedy: – replace Terminal Board 30. – replace Control Unit. |
F08010 (N, A) TB: Analog-digital converter | Cause: The analog/digital converter on Terminal Board 30 has not supplied any converted data. Remedy: – check the power supply. – replace Terminal Board 30. |
F08500 (A) COMM BOARD: Monitoring time configuration expired | Cause: The monitoring time for the configuration has expired. Fault value (r0949, interpret decimal): 0: The transfer time of the send configuration data has been exceeded. 1: The transfer time of the receive configuration data has been exceeded. Remedy: Check communications link. |
F08501 (N, A) PN/COMM BOARD: Setpoint timeout | Cause: The reception of setpoints from the COMM BOARD has been interrupted. – bus connection interrupted. – controller switched off. – controller set into the STOP state. – COMM BOARD defective. Remedy: – Restore the bus connection and set the controller to RUN. – check the set monitoring time if the error persists (p2040). |
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: – check communications link. – check COMM BOARD. |
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, interpret decimal): Only for internal Siemens troubleshooting. Remedy: Check the parameterizing telegram (Ti, To, Tdp, etc.). |
F08510 (A) PN/COMM BOARD: Send configuration data invalid | Cause: COMM BOARD did not accept the send-configuration data. Fault value (r0949, interpret decimal): Return value of the send-configuration data check. Remedy: Check the send configuration data. |
A08511 (F) PN/COMM BOARD: Receive configuration data invalid | Cause: The drive unit did not accept the receive configuration data. Alarm value (r2124, interpret decimal): Return value of the receive configuration data check. 1: Connection established to more drive objects than configured in the device. The drive objects for process data exchange and their sequence are defined in p0978. 2: Too many PZD data words for output or input to a drive object. The number of possible PZD items in a drive object is determined by the number of indices in r2050/p2051 for PZD IF1, and in r8850/p8851 for PZD IF2. 3: Uneven number of bytes for input or output. 4: Setting data for synchronization not accepted. For more information, see A01902. 5: Cyclic operation not active. 17: CBE20 Shared Device: Configuration of the F-CPU has been changed. 223: Illegal clock synchronization for the PZD interface set in p8815[0]. 500: Illegal PROFIsafe configuration for the interface set in p8815[1]. 501: PROFIsafe parameter error (e.g. F_dest). 503: PROFIsafe connection is rejected as long as there is no isochronous connection (p8969). Remedy: Check the receive configuration data. Re alarm value = 1, 2: – Check the list of the drive objects with process data exchange (p0978). With p0978[x] = 0, all of the following drive objects in the list are excluded from the process data exchange. Re alarm value = 2: – Check the number of data words for output and input to a drive object. Re alarm value = 17: – CBE20 Shared Device: Unplug/plug A-CPU. Re alarm value = 223, 500: – Check the setting in p8839 and p8815. – Ensure that only one PZD interface is operated in clock synchronism or with PROFIsafe. Re alarm value = 501: – Check the set PROFIsafe address (p9610). |
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 (r2124, interpret decimal): 0: Error in the buffer status. 1: Error in the memory. Remedy: Check communications link. |
A08526 (F) PN/COMM BOARD: No cyclic connection | Cause: There is no cyclic connection to the control. Remedy: Establish the cyclic connection and activate the control with cyclic operation. For PROFINET, check the parameters “Name of Station” and “IP of Station” (r61000, r61001). If a CBE20 is inserted and PROFIBUS is to communicate via PZD Interface 1, then this must be parameterized using the STARTER commissioning tool or directly using p8839. |
A08561 IE: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration (p8905) for the Industrial Ethernet interface (X127). Alarm value (r2124, interpret decimal): 0: general consistency error 1: error in the IP configuration (IP address, subnet mask or standard gateway). 2: Error in the station names. 5: standard gateway is also set at the PROFINET onboard interface. 6: the station name is also set at the PROFINET onboard interface. 7: IP address is located in the same subnet as the IP address of the PROFINET onboard interface. Remedy: Check the required interface configuration (p8900 and following), correct if necessary, and activate (p8905). or Reconfigure the station via the “Edit Ethernet node” screen form (e.g. with STARTER commissioning software). |
A08562 PROFINET: Syntax error in configuration file | Cause: A syntax error has been detected in the ASCII configuration file for the onboard PROFINET interface. The saved configuration file has not been loaded. Remedy: Check the interface configuration (p8920 and following), correct if necessary, and activate (p8925 = 1). or – Save the parameters for interface configuration (e.g. p8925 = 2). – Reconfigure the station via the “Edit Ethernet node” screen form (e.g. with STARTER commissioning software). |
A08563 PROFINET: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration (p8925) for the PROFINET interface. Alarm value (r2124, interpret decimal): 0: general consistency error 1: error in the IP configuration (IP address, subnet mask or standard gateway). 2: Error in the station names. 3: DHCP was not able to be activated, as a cyclic PROFINET connection already exists. 4: a cyclic PROFINET connection is not possible as DHCP is activated. 5: standard gateway is also set at the Industrial Ethernet interface (X127). 6: standard station name is also set at the Industrial Ethernet interface (X127). 7: IP address is located in the same subnet as the IP address of the Industrial Ethernet interface (X127). Remedy: Check the required interface configuration (p8940 and following), correct if necessary, and activate (p8945). or – Reconfigure the station via the “Edit Ethernet node” screen form (e.g. with STARTER commissioning software). |
A08564 CBE20: Syntax error in configuration file | Cause: A syntax error has been detected in the ASCII configuration file for the Communication Board Ethernet 20 (CBE20). The saved configuration file has not been loaded. Remedy: Check the CBE20 configuration (p8940 and following), correct if necessary, and activate (p8945 = 2). Note: The configuration is not applied until the next POWER ON! – reconfigure the CBE20 (e.g. using the STARTER commissioning software) |
A08565 PNCOMM BOARD : Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration (p8945) for the Communication Board Ethernet 20 (CBE20). Alarm value (r2124, interpret decimal): 0: general consistency error 1: error in the IP configuration (IP address, subnet mask or standard gateway). 2: Error in the station names. 3: DHCP was not able to be activated, as a cyclic PROFINET connection already exists. 4: a cyclic PROFINET connection is not possible as DHCP is activated. Remedy: Check the required interface configuration (p8940 and following), correct if necessary, and activate (p8945). or Reconfigure the station via the “Edit Ethernet node” screen form (e.g. with STARTER commissioning software). |
F08700 (A) CAN: Communications error | Cause: A CAN communications error has occurred. Fault value (r0949, interpret decimal): 1: The error counter for the send telegrams has exceeded the BUS OFF value 255. The bus disables the CAN controller. – bus cable short circuit. – incorrect baud rate. – incorrect bit timing. 2: The master no longer interrogated the CAN node status longer than for its “life time”. The “life time” is obtained from the “guard time” (p8604[0]) multiplied by the “life time factor” (p8604[1]). – bus cable interrupted. – bus cable not connected. – incorrect baud rate. – incorrect bit timing. – master fault. Remedy: – check the bus cable – check the baud rate (p8622). – check the bit timing (p8623). – check the master. The CAN controller must be manually restarted with p8608 = 1 after the cause of the fault has been resolved! |
F08701 CAN: NMT state change | Cause: A CANopen NMT state transition from “operational” to “pre-operational” or after “stopped”. Fault value (r0949, interpret decimal): 1: CANopen NMT state transition from “operational” to “pre-operational”. 2: CANopen NMT state transition from “operational” to “stopped”. Remedy: Not necessary. Acknowledge the fault and continue operation. |
F08702 (A) CAN: RPDO Timeout | Cause: The monitoring time of the CANopen RPDO telegram has expired because the bus connection was either interrupted or the CANopen Master was switched-off. Remedy: – check the bus cable – check the master. – If required, increase the monitoring time (p8699). |
F08703 (A) CAN: Maximum number of drive objects exceeded | Cause: The maximum number of 8 drive objects with the “CAN” function module was exceeded. Remedy: New commissioning of maximum 8 drive objects with the “CAN” function module in the topology. For the drive objects, if required, deselect the “CAN” function module (r0108.29). |
A08751 (N) CAN: Telegram loss | Cause: The CAN controller has lost a receive message (telegram). Remedy: Reduce the cycle times of the receive messages. |
A08752 CAN: Error counter for error passive exceeded | Cause: The error counter for the send or receive telegrams has exceeded the value 127. Remedy: – check the bus cable – set a higher baud rate (p8622). – check the bit timing and if required optimize (p8623). |
A08753 CAN: Message buffer overflow | Cause: A message buffer overflow. Alarm value (r2124, interpret decimal): 1: Non-cyclic send buffer (SDO response buffer) overflow. 2: Non-cyclic receive buffer (SDO receive buffer) overflow. 3: Cyclic send buffer (PDO send buffer) overflow. Remedy: – check the bus cable. – set a higher baud rate (p8622). – check the bit timing and if required optimize (p8623). Re alarm value = 2: – reduce the cycle times of the SDO receive messages. – SDO request from master only after SDO feedback for previous SDO request. |
A08754 CAN: Incorrect communications mode | Cause: In the “operational” mode, an attempt was made to change parameters p8700 … p8737. Remedy: Change to the “pre-operational” or “stopped” mode. |
A08755 CAN: Obj cannot be mapped | Cause: The CANopen object is not provided for the Process Data Object (PDO) Mapping. Remedy: Use a CANopen object intended for the PDO mapping or enter 0. The following objects can be mapped in the Receive Process Data Object (RPDO) or Transmit Process Data Object (TPDO): – RPDO: 6040 hex, 6060 hex, 60FF hex, 6071 hex; 5800 hex – 580F hex; 5820 hex – 5827 hex – TPDO: 6041 hex, 6061 hex, 6063 hex, 6069 hex, 606B hex, 606C hex, 6074 hex; 5810 hex – 581F hex; 5830 hex – 5837 hex Only sub-index 0 of the specified objects can be mapped. |
A08756 CAN: Number of mapped bytes exceeded | Cause: The number of bytes of the mapped objects exceeds the telegram size for net data. A max. of 8 bytes is permissible. Remedy: Map fewer objects or objects with a smaller data type. |
A08757 CAN: Set COB-ID invalid | Cause: For online operation, the appropriate COB-ID must be set invalid before mapping. Example: Mapping for RPDO 1 should be changed (p8710[0]). –> set p8700[0] = C00006E0 hex (invalid COB-ID) –> set p8710[0] as required. –> p8700[0] enter a valid COB-ID Remedy: Set the COB-ID to invalid. |
A08758 CAN: Maximum number of valid PDO exceeded | Cause: The maximum number of valid PDO was exceeded. Alarm value (r2124, interpret decimal): 1: The total number of valid RPDO of all CANopen supported drive objects was exceeded. As a result of the hardware, the limit is 25 valid RPDO. 2: The total number of valid TPDO of all CANopen supported drive objects was exceeded. The limit is defined by the following ratio: CAN sampling time (p8848) / current controller sampling time (p0115[0]) Remedy: Comply with the limit for the maximum number of valid RPDO or TPDO. Apply one of the following options to delete the alarm: – POWER ON (off/on). – carry out a warm restart (p0009 = 30, p0976 = 2). – execute CANopen NMT command reset node. – change CANopen NMT state. – delete alarm buffer [0…7] (p2111 = 0). |
A08759 CAN: PDO COB-ID already available | Cause: An existing PDO COB-ID was allocated. Remedy: Select another PDO COB-ID. |
A08760 CAN: maximum size of the IF PZD exceeded | Cause: The maximum size of the IF PZD was exceeded. Alarm value (r2124, interpret decimal): 1: error for IF PZD receive. 2: error for IF PZD send. Remedy: Map fewer process data in PDO. Apply one of the following options to delete the alarm: – POWER ON (off/on). – carry out a warm restart (p0009 = 30, p0976 = 2). – execute CANopen NMT command reset node. – change CANopen NMT state. – delete alarm buffer [0…7] (p2111 = 0). |
A08800 PROFlenergy energy-saving mode active | Cause: The PROFlenergy energy-saving mode is active Alarm value (r2124, interpret decimal): Mode ID of the active PROFlenergy energy-saving mode. Remedy: The alarm automatically disappears when the energy-saving mode is exited. |
A08802 PROFlenergy not possible to switch off incremental encoder supply | Cause: The incremental encoder is used for the closed-loop position control. This means that its power supply cannot be switched off during the PROFlenergy energy-saving mode, otherwise it would lose its position actual value. Alarm value (r2124, interpret decimal): Encoder number Remedy: The alarm automatically disappears when the energy-saving mode is exited. |
A13000 License not adequate | Cause: – for the drive unit, the options that require a license are being used but the licenses are not sufficient. – an error occurred when checking the existing licenses. Alarm value (r2124, interpret decimal): 0: The existing license is not sufficient. 1: An adequate license was not able to be determined as the memory card with the required licensing data was withdrawn in operation. 2: An adequate license was not able to be determined as there is no licensing data available on the memory card. 3: An adequate license was not able to be determined as there is a checksum error in the license key. 4: An internal error occurred when checking the license. Remedy: Re alarm value = 0: Additional licenses are required and these must be activated (p9920, p9921). Re alarm value = 1: With the system powered down, re-insert the memory card that matches the system. Re alarm value = 2: Enter and activate the license key (p9920, p9921). Re alarm value = 3: Compare the license key (p9920) entered with the license key on the certificate of license. Re-enter the license key and activate (p9920, p9921). Re alarm value = 4: – carry out a POWER ON. – upgrade firmware to later version. – contact the Hotline. |
A13001 Error in license checksum | Cause: When checking the checksum of the license key, an error was detected. Remedy: Compare the license key (p9920) entered with the license key on the certificate of license. Re-enter the license key and activate (p9920, p9921). |
F13009 Licensing OA application not licensed | Cause: At least one OA application which is under license does not have a license. Remedy: – enter and activate the license key for OA applications under license (p9920, p9921). – if necessary, de-activate unlicensed OA applications (p4956). |
F13010 Licensing function module not licensed | Cause: At least one function module which is under license does not have a license. Fault value (r0949, interpret hexadecimal): Bit x = 1: The corresponding function module does not have a license. Remedy: – enter and activate the license key for function modules under license (p9920, p9921). – if necessary, de-activate unlicensed function modules (p0108, r0108). |
F13020 Licensing not sufficient in the control | Cause: For the drive unit, the options that require a license are being used but the licenses are not sufficient. Remedy: – enter and activate the license key for options that require a license. – if necessary, de-activate unlicensed options. |
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: For fault value = 0: – Insert the correct memory card and carry out POWER ON. Re fault value = 2, 3, 12, 13: – contact the responsible OEM. – Deactivate copy protection (p7765) and acknowledge the fault (p3981). – Deactivate know-how protection (p7766… p7768) and acknowledge the fault (p3981). |
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: – insert the memory card and carry out POWER ON. – Try to activate copy protection again (p7765). |
F13102 Know-how protection: Consistency error of the protected data | Cause: An error was identified when checking the consistency of the protected files. As a consequence, the project on the memory card cannot be run. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex: yyyy = object number, xxxx = fault cause 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 (download from the memory card), are inconsistent. Remedy: – Replace the project on the memory card or replace project files for download from the memory card. – Restore the factory setting and download again. |
F30001 Power unit: Overcurrent | Cause: The power unit has detected an overcurrent condition. – closed-loop control is incorrectly parameterized. – motor has a short-circuit or fault to ground (frame). – U/f operation: Up ramp set too low. – U/f operation: Rated motor current is significantly greater than that of the Motor Module. – infeed: High discharge and post-charging currents for voltage dip. – infeed: High post-charging currents for overload when motoring and DC link voltage dip. – infeed: Short-circuit currents at power-up due to the missing line reactor. – power cables are not correctly connected. – the power cables exceed the maximum permissible length. – power unit defective. – line phase interrupted. Additional causes for a parallel switching device (r0108.15 = 1): – a power unit has tripped (powered down) due to a ground fault. – the closed-loop circulating current control is either too slow or has been set too fast. Fault value (r0949, interpret bitwise binary): Bit 0: Phase U. Bit 1: Phase V. Bit 2: Phase W. Bit 3: Overcurrent in the DC link. Remedy: – check the motor data – if required, carry out commissioning. – check the motor circuit configuration (star/delta). – U/f operation: Increase up ramp. – U/f operation: Check the assignment of the rated currents of the motor and Motor Module. – infeed: Check the line supply quality. – infeed: Reduce the motor load. – infeed: Check the correct connection of the line filter and the line commutating reactor. – check the power cable connections. – check the power cables for short-circuit or ground fault. – check the length of the power cables. – replace power unit. – check the line supply phases. For a parallel switching device (r0108.15 = 1) the following additionally applies: – check the ground fault monitoring thresholds (p0287). – check the setting of the closed-loop circulating current control (p7036, p7037). |
F30002 Power unit: DC link voltage overvoltage | Cause: The power unit has detected overvoltage in the DC link. – motor regenerates too much energy. – device connection voltage too high. – when operating with a Voltage Sensing Module (VSM), the phase assignment L1, L2, L3 at the VSM differs from the phase assignment at the power unit. – line phase interrupted. Fault value (r0949, interpret decimal): DC link voltage at the time of trip [0.1 V]. Remedy: – increase the ramp-down time – activate the DC link voltage controller (p1240) – use a brake resistor or Active Line Module – increase the current limit of the infeed or use a larger module (for the Active Line Module) – check the device supply voltage – check and correct the phase assignment at the VSM and at the power unit – check the line supply phases. – set the rounding times (p1130, p1136). This is particularly recommended in U/f operation to relieve the DC link voltage controller with rapid ramp-down times of the ramp-function generator. |
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: – check the line supply voltage – check the line supply infeed and observe the fault messages relating to it (if there are any) – check the line supply phases. – check the line supply voltage setting (p0210). – booksize units: check the setting of p0278. |
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. Fault value (r0949): Temperature [1 bit = 0.01 °C]. Remedy: – check whether the fan is running. – check the fan elements. – check whether the ambient temperature is in the permissible range. – check the motor load. – reduce the pulse frequency if this is higher than the rated pulse frequency. |
F30005 Power unit: Overload I2t | Cause: The power unit was overloaded (r0036 = 100 %). – the permissible rated power unit current was exceeded for an inadmissibly long time. – the permissible load duty cycle was not maintained. Fault value (r0949, interpret decimal): I2t [100 % = 16384]. Remedy: – reduce the continuous load. – adapt the load duty cycle. – check the motor and power unit rated currents. – increase p0294 |
F30006 Power unit: Thyristor Control Board | Cause: The Thyristor Control Board (TCB) of the Basic Line Module signals a fault. – there is no line supply voltage. – the line contactor is not closed. – the line supply voltage is too low. – line supply frequency outside the permissible range (45 … 66 Hz). – there is a DC link short-circuit. – there is a DC link short-circuit (during the pre-charging phase). – voltage supply for the Thyristor Control Board outside the nominal range (5 … 18 V) and line voltage >30 V. – there is an internal fault in the Thyristor Control Board. Remedy: The faults must be saved in the Thyristor Control Board and must be acknowledged. To do this, the supply voltage of the Thyristor Control Board must be switched out for at least 10 s! – check the line supply voltage – check or energize the line contactor. – check the monitoring time and, if required, increase (p0857). – if required, observe additional power unit messages/signals. – check the DC link regarding short-circuit or ground fault. – evaluate diagnostic LEDs for the Thyristor Control Board. |
F30008 Power unit: Sign-of-life error cyclic data | Cause: The Control Unit has not punctually updated the cyclic setpoint telegram. The number of consecutive sign-of-life errors has exceeded the fault threshold (p7789). Remedy: – check the electrical cabinet design and cable routing for EMC compliance – for projects with the VECTOR drive object, check whether p0117 = 6 has been set on the Control Unit. – increase the fault threshold (p7789). |
A30010 (F) Power unit: Sign-of-life error cyclic data | Cause: A DRIVE-CLIQ communication error has occurred between the Control Unit and the power unit involved. The cyclic setpoint telegrams of the Control Unit were not received on time by the power unit for at least one clock cycle. Remedy: Check the electrical cabinet design and cable routing for EMC compliance. |
F30011 Power unit: Line phase failure in main circuit | Cause: At the power unit, the DC link voltage ripple has exceeded the permissible limit value. Possible causes: – A line phase has failed. – The 3 line phases are inadmissibly unsymmetrical. – The capacitance of the DC link capacitor forms a resonance frequency with the line inductance and the reactor integrated in the power unit. – the fuse of a phase of a main circuit has ruptured. – A motor phase has failed. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: – check the main circuit fuses. – Check whether a single-phase load is distorting the line voltages. – Detune the resonant frequency with the line inductance by using an upstream line reactor. – Dampen the resonant frequency with the line inductance by switching over the DC link voltage compensation in the software (see p1810) – or increase the smoothing (see p1806). However, this can have a negative impact on the torque ripple at the motor output. – check the motor feeder cables. |
F30012 Power unit: Temperature sensor heat sink wire breakage | Cause: The connection to a heat sink temperature sensor in the power unit is interrupted. Fault value (r0949, interpret hexadecimal): Bit 0: Module slot (electronics slot) Bit 1: Air intake Bit 2: Inverter 1 Bit 3: Inverter 2 Bit 4: Inverter 3 Bit 5: Inverter 4 Bit 6: Inverter 5 Bit 7: Inverter 6 Bit 8: Rectifier 1 Bit 9: Rectifier 2 Remedy: Contact the manufacturer. |
F30013 Power unit: Temperature sensor heat sink short-circuit | Cause: The heat sink temperature sensor in the power unit is short-circuited. Fault value (r0949, interpret hexadecimal): Bit 0: Module slot (electronics slot) Bit 1: Air intake Bit 2: Inverter 1 Bit 3: Inverter 2 Bit 4: Inverter 3 Bit 5: Inverter 4 Bit 6: Inverter 5 Bit 7: Inverter 6 Bit 8: Rectifier 1 Bit 9: Rectifier 2 Remedy: Contact the manufacturer. |
F30015 (N, A) Power unit: Phase failure motor cable | Cause: A phase failure in the motor feeder cable was detected. The signal can also be output in the following case: – the motor is correctly connected, however the closed-speed control is instable and therefore an oscillating torque is generated. Remedy: – check the motor feeder cables. – check the speed controller settings. – increase the ramp-up or ramp-down time (p1120) if the drive has stalled in U/f control. |
A30016 (N) Power unit: Load supply switched out | Cause: The DC link voltage is too low. Alarm value (r2124, interpret decimal): DC link voltage at the time of trip [0.1 V]. Remedy: – switch on load supply. – check the line supply if necessary. |
F30017 Power unit: Hardware current limit has responded too often | Cause: The hardware current limitation in the relevant phase (see A30031, A30032, A30033) has responded too often. The number of times the limit has been exceeded depends on the design and type of power unit. For infeed units, the following applies: – closed-loop control is incorrectly parameterized. – load on the infeed is too high. – Voltage Sensing Module incorrectly connected. – line reactor missing or the incorrect type. – power unit defective. The following applies to Motor Modules: – closed-loop control is incorrectly parameterized. – fault in the motor or in the power cables. – the power cables exceed the maximum permissible length. – motor load too high – power unit defective. Fault value (r0949, interpret binary): Bit 0: Phase U Bit 1: Phase V Bit 2: Phase W Remedy: For infeed units, the following applies: – check the controller settings and reset and identify the controller if necessary (p0340 = 2, p3410 = 5) – reduce the load and increase the DC-link capacitance or use a higher-rating infeed if necessary – check the connection of the optional Voltage Sensing Module – check the connection and technical data of the line reactor – check the power cables for short-circuit or ground fault. – replace power unit. The following applies to Motor Modules: – check the motor data and if required, recalculate the controller parameters (p0340 = 3). As an alternative, run a motor data identification (p1910 = 1, p1960 = 1). – check the motor circuit configuration (star-delta). – check the motor load. – check the power cable connections. – check the power cables for short-circuit or ground fault. – check the length of the power cables. – replace power unit. |
F30020 Power unit: 26.5 V supply voltage fault | Cause: For a drive that has been enabled, it has been identified that the 26.5 V supply voltage for the Hydraulic Module has a fault (X271). Permissible range: 26.0 … 27.0 V Fault value (r0949, interpret decimal): Voltage value [0.1 V]. Remedy: – check the 26.5 V supply voltage (X271). |
F30020 Power unit: Configuration not supported | Cause: A configuration is requested that is not supported by the power unit. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex: xxxx = fault cause, yyyy = additional information (internal Siemens) xxxx = 0: Autonomous operation is requested but is not supported. xxxx = 1: The requested DRIVE-CLiQ timing is not permissible. xxxx = 2: A PM260 has been detected with PS-ASIC version 2. This combination is not supported. xxxx = 3: Initialization was not able to be successfully completed. It is possible that the Control Unit was withdrawn from the power module before or during power-up. xxxx = 4: The combination of power unit and Control Unit or Control Unit Adapter is not supported. xxxx = 5: The higher current controller dynamic performance is not supported. Remedy: Re fault cause = 0: – If required, deactivate an active internal voltage protection (p1231). Re fault cause = 1: – Update the Control Unit firmware or change the DRIVE-CLIQ topology. Re fault cause = 2: – Replace the power unit with a PM260 with PS-ASIC version 3 (or higher). Re fault cause = 3, 4: – Insert a Control Unit or Control Unit Adapter (CUAxx) on an appropriate Power Module and perform a POWER ON for the Control Unit or the Control Units Adapter. Re fault cause = 5: – use a booksize format power unit. – for a Double Motor Module operate the two drive controls with the same current controller sampling time (p0115[0]). Otherwise, the higher current controller dynamics can only be activated on the drive with the longer sampling time. – If required, de-select the higher current controller dynamic performance (p1810.11 = 0). After deselecting the computing dead time, recalculate the controller gains (p0340 = 4). If required, optimize the speed controller. |
F30021 Power unit: Ground fault | Cause: The Power unit has detected a ground fault. Possible causes: – ground fault in the power cables. – Ground fault at the motor. – CT defective. – when the brake closes, this causes the hardware DC current monitoring to respond. – short-circuit at the braking resistor. – the closed-loop circulating current control for devices connected in parallel (r0108.15 = 1) is either too slow or has been set too fast. Fault value (r0949, interpret decimal): 0: – the hardware DC current monitoring has responded. – short-circuit at the braking resistor. > 0: Absolute value, total current amplitude [20479 = r0209 * 1.4142]. Remedy: – check the power cable connections. – check the motor. – check the CT. – check the cables and contacts of the brake connection (a wire is possibly broken). – check the braking resistor. For parallel switching devices (r0108.15 = 1) the following additionally applies: – check the ground fault monitoring thresholds (p0287). – check the setting of the closed-loop circulating current control (p7036, p7037). |
F30022 Power unit: Monitoring U_ce | Cause: In the power unit, the monitoring of the collector-emitter voltage (U_ce) of the semiconductor has responded. Possible causes: – fiber-optic cable interrupted. – power supply of the IGBT gating module missing. – short-circuit at the power unit output. – defective semiconductor in the power unit. Fault value (r0949, interpret binary): Bit 0: Short-circuit in phase U Bit 1: Short circuit in phase V Bit 2: Short-circuit in phase W Bit 3: Light transmitter enable defective Bit 4: U_ce group fault signal interrupted Remedy: – check the fiber-optic cable and if required, replace. – check the power supply of the IGBT gating module (24 V). – check the power cable connections. – select the defective semiconductor and replace. |
F30024 Power unit: Overtemperature thermal model | Cause: The temperature difference between the heat sink and chip has exceeded the permissible limit value. – the permissible load duty cycle was not maintained. – insufficient cooling, fan failure. – overload. – ambient temperature too high. – pulse frequency too high. Remedy: – adapt the load duty cycle. – check whether the fan is running. – check the fan elements. – check whether the ambient temperature is in the permissible range. – check the motor load. – reduce the pulse frequency if this is higher than the rated pulse frequency. |
F30025 Power unit: Chip overtemperature | Cause: The chip temperature of the semiconductor has exceeded the permissible limit value. – the permissible load duty cycle was not maintained. – insufficient cooling, fan failure. – overload. – ambient temperature too high. – pulse frequency too high. Fault value (r0949, interpret decimal): Temperature difference between the heat sink and chip [0.01 °C]. Remedy: – adapt the load duty cycle. – check whether the fan is running. – check the fan elements. – check whether the ambient temperature is in the permissible range. – check the motor load. – reduce the pulse frequency if this is higher than the rated pulse frequency. |
F30027 Power unit: Precharging DC link time monitoring | Cause: The power unit DC link was not able to be pre-charged within the expected time. 1) There is no line supply voltage connected. 2) The line contactor/line side switch has not been closed. 3) The line supply voltage is too low. 4) Line supply voltage incorrectly set (p0210). 5) The pre-charging resistors are overheated as there were too many pre-charging operations per time unit. 6) The pre-charging resistors are overheated as the DC link capacitance is too high. 7) The pre-charging resistors are overheated because when there is no “ready for operation” (r0863.0) of the infeed unit, power is taken from the DC link. 8) The pre-charging resistors are overheated as the line contactor was closed during the DC link fast discharge through the Braking Module. 9) The DC link has either a ground fault or a short-circuit. 10) The pre-charging circuit is possibly defective (only for chassis units). 11) Infeed is defective and/or fuse has ruptured in the Motor Module (only Booksize units). Remedy: In general: – check the line supply voltage at the input terminals. – check the line supply voltage setting (p0210). For booksize drive units, the following applies: – wait (approx. 8 minutes) until the pre-charging resistors have cooled down. For this purpose, preferably disconnect the infeed unit from the line supply. Re 5): – carefully observe the permissible pre-charging frequency (refer to the appropriate Equipment Manual). Re 6): – check the total capacitance of the DC link and reduce in accordance with the maximum permissible DC-link capacitance if necessary (refer to the appropriate Equipment Manual) Re 7): – interconnect the ready-for-operation signal from the infeed unit (r0863.0) in the enable logic of the drives connected to this DC link Re 8): – check the connections of the external line contactor. The line contactor must be open during DC-link fast discharge. Re 9): – check the DC link for ground faults or short circuits. Re 11): – Check the DC link voltage of the infeed (r0070) and Motor Modules (r0070). If the DC link voltage generated by the infeed (or external) is not displayed for the Motor Modules (r0070), then a fuse has ruptured in the Motor Module. |
A30030 Power unit: Internal overtemperature alarm | Cause: The temperature inside the drive converter has exceeded the permissible temperature limit. – insufficient cooling, fan failure. – overload. – ambient temperature too high. Remedy: – possibly use an additional fan. – check whether the ambient temperature is in the permissible range. |
A30031 Power unit: Hardware current limiting in phase U | Cause: Hardware current limit for phase U responded. The pulsing in this phase is inhibited for one pulse period. – closed-loop control is incorrectly parameterized. – fault in the motor or in the power cables. – the power cables exceed the maximum permissible length. – motor load too high – power unit defective. Remedy: – check the motor data and if required, recalculate the control parameters (p0340 = 3). As an alternative, run a motor data identification (p1910 = 1, p1960 = 1). – check the motor circuit configuration (star/delta). – check the motor load. – check the power cable connections. – check the power cables for short-circuit or ground fault. – check the length of the power cables. |
A30032 Power unit: Hardware current limiting in phase V | Cause: Hardware current limit for phase V responded. The pulsing in this phase is inhibited for one pulse period. – closed-loop control is incorrectly parameterized. – fault in the motor or in the power cables. – the power cables exceed the maximum permissible length. – motor load too high – power unit defective. Remedy: – check the motor data and if required, recalculate the control parameters (p0340 = 3). As an alternative, run a motor data identification (p1910 = 1, p1960 = 1). – check the motor circuit configuration (star/delta). – check the motor load. – check the power cable connections. – check the power cables for short-circuit or ground fault. – check the length of the power cables. |
A30033 Power unit: Hardware current limiting in phase W | Cause: Hardware current limit for phase W responded. The pulsing in this phase is inhibited for one pulse period. – closed-loop control is incorrectly parameterized. – fault in the motor or in the power cables. – the power cables exceed the maximum permissible length. – motor load too high – power unit defective. Remedy: – check the motor data and if required, recalculate the control parameters (p0340 = 3). As an alternative, run a motor data identification (p1910 = 1, p1960 = 1). – check the motor circuit configuration (star/delta). – check the motor load. – check the power cable connections. – check the power cables for short-circuit or ground fault. – check the length of the power cables. |
A30034 Power unit: Internal overtemperature | Cause: The alarm threshold for internal overtemperature has been reached. If the temperature inside the unit continues to increase, fault F30036 may be triggered. – ambient temperature might be too high. – insufficient cooling, fan failure. Remedy: – check the ambient temperature. – check the fan for the inside of the unit. |
F30035 Power unit: Air intake overtemperature | Cause: The air intake in the power unit has exceeded the permissible temperature limit. For air-cooled power units, the temperature limit is at 55 °C. – ambient temperature too high. – insufficient cooling, fan failure. Remedy: – check whether the fan is running. – check the fan elements. – check whether the ambient temperature is in the permissible range. |
F30036 Power unit: Internal overtemperature | Cause: The temperature inside the drive converter has exceeded the permissible temperature limit. – insufficient cooling, fan failure. – overload. – ambient temperature too high. Remedy: – check whether the fan is running. – check the fan elements. – check whether the ambient temperature is in the permissible range. |
F30037 Power unit: Rectifier overtemperature | Cause: The temperature in the rectifier of the power unit has exceeded the permissible temperature limit. – insufficient cooling, fan failure. – overload. – ambient temperature too high. – line supply phase failure. Remedy: – check whether the fan is running. – check the fan elements. – check whether the ambient temperature is in the permissible range. – check the motor load. – check the line supply phases. |
A30038 Power unit: Capacitor fan monitoring | Cause: The capacitor fan signals a fault. Remedy: Replace the capacitor fan in the power unit. |
F30039 Power unit: Failure capacitor fan | Cause: The capacitor fan has failed. Remedy: Replace the capacitor fan in the power unit. |
F30040 Power unit: Undervolt 24 V | Cause: The undervoltage threshold of the 24 V power supply for the power unit was fallen below for longer than 3 ms. Remedy: – Check the power supply of the power unit. – carry out a POWER ON (power off/on) for the component. |
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: – Check the power supply of the power unit. – carry out a POWER ON (power off/on) for the component. |
A30041 (F) Power unit: Undervoltage 24 V alarm | Cause: For the power unit power supply, the lower threshold has been violated. Remedy: – Check the power supply of the power unit. – carry out a POWER ON (power off/on) for the component. |
A30042 Power unit: Fan has reached the maximum operating hours | Cause: The maximum operating time of at least one fan will soon be reached, or has already been exceeded. Remedy: For the fan involved, carry out the following: – replace the fan. – reset the operating hours counter (p0251, p0254). |
F30043 Power unit: Overvolt 24 V | Cause: For the power unit power supply, the upper threshold has been violated. Remedy: Check the power supply of the power unit. |
A30044 (F) Power unit: Overvoltage 24 V alarm | Cause: For the power unit power supply, the upper threshold has been violated. Remedy: Check the power supply of the power unit. |
F30045 Power unit: Supply undervoltage | Cause: Power supply fault in the power unit. – The voltage monitor signals an undervoltage fault on the module. Remedy: – Check the power supply of the power unit. – carry out a POWER ON (power off/on) for the component. – replace the module if necessary. |
A30046 (F) Power unit: Undervoltage alarm | Cause: Before the last restart, a problem occurred at the power unit power supply. The voltage monitor in the internal FPGA of the PSA signals an undervoltage fault on the module. Remedy: – check the 24 V DC voltage supply to power unit. – carry out a POWER ON (power off/on) for the component. – replace the module if necessary. |
F30047 Cooling unit: Cooling medium flow rate too low | Cause: The flowrate of the cooling unit has fallen below the fault threshold. Remedy: – Check the feedback signals and parameter assignment (p0260 … p0267). – Check the coolant feed. – Check the thermal conductivity of the coolant. – Check the coolant concentration. |
A30048 Power unit: External fan faulty | Cause: The feedback signal from the external fan indicates a fault. – fan faulty, blocked. – feedback signal inaccurate. Remedy: – check the external fan and replace if necessary. – if you are using an external fan with feedback, check its wiring (X12.2 or X13.2). |
A30049 Power unit: Internal fan faulty | Cause: The internal fan has failed. Remedy: Check the internal fan and replace if necessary. |
F30050 Power unit: 24 V supply overvoltage | Cause: The voltage monitor signals an overvoltage fault on the module. Remedy: – check the 24 V power supply. – replace the module if necessary. |
F30051 Power unit: Motor holding brake short circuit detected | Cause: A short-circuit at the motor holding brake terminals has been detected. Remedy: – check the motor holding brake for a short-circuit. – check the connection and cable for the motor holding brake. |
F30052 EEPROM data error | Cause: EEPROM data error of the power unit module. Fault value (r0949, interpret decimal): 0, 2, 3, 4: The EEPROM data read in from the power unit module are incorrect. 1: EEPROM data is not compatible to the firmware of the power unit application. Remedy: Re fault value = 0, 2, 3, 4: – Replace the power unit module or update the EEPROM data. For fault value = 1: – The following applies for CU31x and CUA31: Update the firmware \SIEMENS\SINAMICS\CODE\SAC\cu31xi.ufw (cua31.ufw) |
F30053 FPGA data faulty | Cause: The FPGA data of the power unit are faulty. Remedy: Replace the power unit or update the FPGA data. |
A30054 (F, N) Power unit: Undervoltage when opening the brake | Cause: When the brake is being opened, it is detected that the power supply voltage is less than 24 V – 10% = 21.6V. Remedy: Check the 24 V voltage for stability and value. |
F30055 Power unit: Braking chopper overcurrent | Cause: An overcurrent condition has occurred in the braking chopper. Remedy: – check whether the braking resistor has a short circuit. – for an external braking resistor, check whether the resistor may have been dimensioned too small. |
A30057 Power unit: Line asymmetry | Cause: Frequencies have been detected on the DC link voltage that would suggest line asymmetry or failure of a line phase. It is also possible that a motor phase has failed. Fault F30011 is output if the alarm is present and at the latest after 5 minutes. Remedy: – check the line phase connection. – check the motor feeder cable connections. – If there is no phase failure of the line or motor, then line asymmetry is involved. – reduce the power in order to avoid fault F30011. |
F30059 Power unit: Internal fan faulty | Cause: The internal power unit fan has failed and is possibly defective. Remedy: Check the internal fan and replace if necessary. |
F30060 (A) Pre-charge contactor state monitoring | Cause: A feedback signal for the pre-charging contactor (ALM, SLM, BLM diode) or the line contactor (BLM thyristor) interconnected and the monitoring activated. After switching-in/switching-out the contactor, a correct feedback signal was not received within the monitoring time set in p0255[0]. Remedy: – check the monitoring time setting (p0255[0]). – check the contactor wiring and activation. – replace the contactor. |
F30061 (A) Bridging contactor monitoring | Cause: A feedback signal for the bypass contactor is interconnected and the monitoring activated. After switching-in/switching-out the contactor, a correct feedback signal was not received within the monitoring time set in p0255[1]. Remedy: – check the monitoring time setting (p0255[1]). – check the contactor wiring and activation. – replace the contactor. |
A30065 (F, N) Voltage measured values not plausible | Cause: The voltage measurement supplies values that are not plausible Remedy: – Deactivate voltage measurement (p247.0 = 0). – Deactivate flying restart with voltage measurement (p247.5 = 0) and deactivate fast flying restart (p1780.11 = 0). |
F30070 Cycle requested by the power unit module not supported | Cause: A cycle is requested that is not supported by the power unit. Remedy: The power unit only supports the following cycles: 62.5 μs, 125 μs, 250 μs and 500 μs For fault value = 0: – Set a permitted current control cycle. For fault value = 1: – Set a permitted DRIVE-CLIQ cycle. Re fault value = 2, 3: – Contact the manufacturer (you may have an incompatible firmware version). |
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: Check the interface (adjustment and locking) to the power unit module. |
F30072 Setpoints are no longer being transferred to the power unit | Cause: The following applies for CU31x and CUA31: More than one setpoint telegram was not able to be transferred to the power unit module. Remedy: The following applies for CU31x and CUA31: Check the interface (adjustment and locking) to the power unit module. |
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: Wait until synchronization is re-established. |
F30074 (A) Communication error between the Control Unit and Power Module | Cause: Communications between the Control Unit (CU) and Power Module (PM) via the interface no longer possible. The CU may have been withdrawn or is incorrectly inserted. Remedy: Reinsert the Control Unit (CU) or the Control Unit adapter (CUAxx) onto the original Power Module and continue operation. If required, carry out a POWER ON for the CU and/or the CUA. |
F30075 Configuration of the power unit unsuccessful | Cause: A communication error has occurred while configuring the power unit using the Control Unit. The cause is not clear. Remedy: – acknowledge the fault and continue operation. – if the fault reoccurs, carry out a POWER ON (switch off/on). – if required, replace the power unit. |
F30080 Power unit: Current increasing too quickly | Cause: The power unit has detected an excessive rate of rise in the overvoltage range. – closed-loop control is incorrectly parameterized. – motor has a short-circuit or fault to ground (frame). – U/f operation: Up ramp set too low. – U/f operation: rated current of motor much greater than that of power unit. – infeed: High discharge and post-charging currents for voltage dip. – infeed: High post-charging currents for overload when motoring and DC link voltage dip. – infeed: Short-circuit currents at power-up due to the missing line reactor. – power cables are not correctly connected. – power cables exceed the maximum permissible length. – power unit defective. Remedy: – check the motor data – if required, carry out commissioning. – check the motor circuit configuration (star-delta) – U/f operation: Increase up ramp. – U/f operation: Check assignment of rated currents of motor and power unit. – infeed: Check the line supply quality. – infeed: Reduce the motor load. – infeed: Correct connection of the line reactor. – check the power cable connections. – check the power cables for short-circuit or ground fault. – check the length of the power cables. – replace power unit. For a parallel switching device (r0108.15 = 1) the following additionally applies: – check the ground fault monitoring thresholds (p0287). – check the setting of the closed-loop circulating current control (p7036, p7037). |
F30081 Power unit: Switching operations too frequent | Cause: The power unit has executed too many switching operations for current limitation. – closed-loop control is incorrectly parameterized. – motor has a short-circuit or fault to ground (frame). – U/f operation: Up ramp set too low. – U/f operation: rated current of motor much greater than that of power unit. – infeed: High discharge and post-charging currents for voltage dip. – infeed: High post-charging currents for overload when motoring and DC link voltage dip. – infeed: Short-circuit currents at power-up due to the missing line reactor. – power cables are not correctly connected. – power cables exceed the maximum permissible length. – power unit defective. Remedy: – check the motor data – if required, carry out commissioning. – check the motor circuit configuration (star-delta) – U/f operation: Increase up ramp. – U/f operation: Check assignment of rated currents of motor and power unit. – infeed: Check the line supply quality. – infeed: Reduce the motor load. – infeed: Correct connection of the line reactor. – check the power cable connections. – check the power cables for short-circuit or ground fault. – check the length of the power cables. – replace power unit. For a parallel switching device (r0108.15 = 1) the following additionally applies: – check the ground fault monitoring thresholds (p0287). – check the setting of the closed-loop circulating current control (p7036, p7037). |
F30105 PU: Actual value sensing fault | Cause: At least one incorrect actual value channel was detected on the Power Stack Adapter (PSA). The incorrect actual value channels are displayed in the following diagnostic parameters. Remedy: Evaluate the diagnostic parameters. If the actual value channel is incorrect, check the components and if required, replace. |
F30314 Power unit: 24 V power supply overloaded by PM | Cause: The 24 V power supply through the Power Module (PM) is overloaded. An external 24 V power supply via X124 on the Control Unit is not connected. Remedy: Connect an external 24 V power supply via X124 at the Control Unit. |
A30315 (F) Power unit: 24 V power supply overloaded by PM | Cause: The 24 V power supply through the Power Module (PM) is overloaded. An external 24 V power supply via X124 on the Control Unit is not connected. Remedy: Connect an external 24 V power supply via X124 at the Control Unit. |
A30502 Power unit: DC link overvoltage | Cause: The power unit has detected overvoltage in the DC link on a pulse inhibit. – device connection voltage too high. – line reactor incorrectly dimensioned. Remedy: – check the device supply voltage (p0210). – check the dimensioning of the line reactor. |
F30600 SI P2: STOP A initiated | Cause: The drive-integrated “Safety Integrated” function in monitoring channel 2 has detected a fault and initiated a STOP A (STO via the safety shutdown path of monitoring channel 2). – forced checking procedure of the safety shutdown path of monitoring channel 2 unsuccessful. – subsequent response to fault F30611 (defect in a monitoring channel). Fault value (r0949, interpret decimal): 0: Stop request from the Control Unit. 1005: STO active although STO not selected and there is no internal STOP A present. 1010: STO inactive although STO is selected or an internal STOP A is present. 1011: internal error for STO deselected in monitoring channel 2. 1020: Internal software error in the “Internal voltage protection” function. The “internal voltage protection” function is withdrawn. A STOP A that cannot be acknowledged is initiated. 9999: Subsequent response to fault F30611. Remedy: – select Safe Torque Off and de-select again. – carry out a POWER ON (power off/on) for all components. – replace the Motor Module/Hydraulic Module involved. For fault value = 1020: – upgrade the Motor Module/Hydraulic Module software. – replace the Motor Module/Hydraulic Module. For fault value = 9999: – carry out diagnostics for fault F30611. |
F30611 (A) SI P2: Defect in a monitoring channel | Cause: The drive-integrated “Safety Integrated” function on processor 2 has detected a fault in the crosswise data comparison between the two monitoring channels and has initiated a STOP F. As a result of this fault, after the parameterized transition has expired (p9858), fault F30600 is output (SI MM: STOP A initiated). Fault value (r0949, interpret decimal): 0: Stop request from the Control Unit. 1 … 999: Number of the cross-compared data that resulted in this fault. 1000: Watchdog timer has expired. 1001, 1002: Initialization error, change timer / check timer. 1950: Module temperature outside the permissible temperature range. 1951: Module temperature not plausible. 1952: S120M: hardware access fault 2000: Status of the STO selection for both monitoring channels are different. 2001: Feedback signals of STO shutdown for both monitoring channels are different. 2002: Statuses of the delay timer SS1 on both monitoring channels are different. 2003: Status of the STO terminal for both monitoring channels are different. 6000 … 6999: Error in the PROFIsafe control. Remedy: Re fault value = 1 … 5 and 7 … 999: – check the cross data comparison that resulted in a STOP F. – carry out a POWER ON (power off/on) for all components. – upgrade the Motor Module software. – upgrade the Control Unit software. For fault value = 6: – carry out a POWER ON (power off/on) for all components. – upgrade the Motor Module software. – upgrade the Control Unit software. For fault value = 1000: – check the wiring of the safety-relevant inputs (SGE) on the Control Unit (contact problems). – PROFIsafe: Remove contact problems/faults at the PROFIBUS master/PROFINET controller. – check the wiring of the failsafe inputs at the TM54F (contact problems). – check the tolerance time F-DI changeover and if required, increase the value (p9650/p9850). Re fault value = 1001, 1002: – carry out a POWER ON (power off/on) for all components. – upgrade the Motor Module software. – upgrade the Control Unit software. For fault value = 1950: – operate the module in the permissible range. – check the module fan, replace the Motor Module involved. For fault value = 1951: – operate the module in the permissible range. – replace the Motor Module involved. For fault value = 1952: – replace the Motor Module involved. Re fault value = 2000, 2001, 2002, 2003: – check the tolerance time SGE changeover and if required, increase the value (p9650/p9850, p9652/p9852). – check the wiring of the safety-relevant inputs (SGE) (contact problems). – check why STO was selected in r9872. When the SMM functions are active (p9501 = 1), STO can also be selected using these functions. – replace the Motor Module involved. Re fault value = 6000 … 6999: – Refer to the description of the message values in safety message C01711. |
N30620 (F, A) SI P2: Safe Torque Off active | Cause: The “Safe Torque Off” (STO) function of the basic functions has been selected in monitoring channel 2 using the input terminal and is active. Remedy: Not necessary. |
N30621 (F, A) SI P2: Safe Stop 1 active | Cause: The “Safe Stop 1” function (SS1) was selected in monitoring channel 2 and is active. Remedy: Not necessary. |
F30625 SI P2: Sign-of-life error in safety data | Cause: The drive-integrated “Safety Integrated” function in monitoring channel 2 has detected an error in the sign-of-life of the safety data between the two monitoring channels and initiated a STOP A. – there is either a DRIVE-CLiQ communication error or communication has failed. – a time slice overflow of the safety software has occurred. – The enable of the safety functions in both monitoring channels is inconsistent (p9601 = 0, p9801 <> 0). Remedy: – select Safe Torque Off and de-select again. – carry out a POWER ON (power off/on) for all components. – Check whether there is a DRIVE-CLiQ communication error between the two monitoring channels and, if required, carry out a diagnostics routine for the faults identified. – de-select all drive functions that are not absolutely necessary. – reduce the number of drives. – check the electrical cabinet design and cable routing for EMC compliance – Check the enable of the safety functions for both of the monitoring channels and if required, correct (p9601, p9801). |
F30630 SI P2: Brake control error | Cause: The “Safety Integrated” function integrated in the drive on the Motor Module (MM) has detected a brake control error and initiated a STOP A. – motor cable is not shielded correctly. – defect in control circuit of the Motor Module. Fault value (r0949, interpret decimal): 10: Fault in “open holding brake” operation. 30: Fault in “close holding brake” operation. 40: Fault in “brake closed” state. 60, 70: Fault in the brake control circuit of the Control Unit or communication fault. 81: Safe Brake Adapter: Fault in “brake closed” state. 82: Safe Brake Adapter: Fault for the operation “open brake”. 83: Safe Brake Adapter: Fault for the operation “close brake”. 84, 85: Safe Brake Adapter: Fault in the brake control circuit or communication fault. 90: Brake released for service purposes (X4). 91: Fault in “open holding brake” operation. Remedy: – check parameter p1278 (for SBC, only p1278 = 0 is permissible). – select Safe Torque Off and de-select again. – check the motor holding brake connection. – check the function of the motor holding brake. – check for DRIVE-CLiQ communication error and run diagnostics. – check for EMC compliance. – replace the Motor Module involved. Operation with Safe Brake Module or Safe Brake Adapter: – check the Safe Brake Module or Safe Brake Adapter connection. – Replace the Safe Brake Module or Safe Brake Adapter. |
F30631 Brake control: External release active | Cause: For mounting purposes, the brake is supplied with voltage via terminal X4.1 and released. Remedy: If required, again remove the power supply at X4.1. |
F30632 SI P2: shutoff valve control/feedback signal error | Cause: The drive-integrated “Safety Integrated” function on the Hydraulic Module (monitoring channel 2) has detected a fault for the control/feedback signal of the shutoff valve and initiated a STOP A. Possible causes: – shutoff valve not connected or incorrectly connected (X272). – feedback signal of the shutoff valve not connected or incorrectly connected (X281/X282). – feedback signal of the shutoff valve incorrectly set (p9626/p9826). – shutoff valve defective. – Hydraulic Module defective. Remedy: – check the shutoff valve connection (X272). – check the feedback signals of the shutoff valve (X281, X282). – check the configuration of the feedback signals of the shutoff valve (p9626/p9826). – Check for EMC-compliant control cabinet design and cable routing. – if necessary, replace the shutoff valve. – if necessary, replace the Hydraulic Module. |
A30640 (F) SI P2: Fault in the shutdown path of the second channel | Cause: The Motor Module or Hydraulic Module has detected a communication error with the higher-level control or the TM54F to transfer the safety-relevant information, or there is a communication error between modules connected in parallel. Remedy: For the higher-level control, the following applies: – check the PROFIsafe address in the higher-level control and modules and if required, align. – save all parameters (p0977 = 1). – carry out a POWER ON (power off/on) for all components. For TM54F, carry out the following steps: – start the copy function for the node identifier (p9700 = 1D hex). – acknowledge hardware CRC (p9701 = EC hex). – save all parameters (p0977 = 1). – carry out a POWER ON (power off/on) for all components. For a parallel connection, the following applies: – check the PROFIsafe address in both monitoring channels and if required, align. The following generally applies: – upgrade the Motor Module/Hydraulic Module software. |
F30649 SI P2: Internal software error | Cause: An internal error in the Safety Integrated software in monitoring channel 2 has occurred. Remedy: – carry out a POWER ON (power off/on) for all components. – re-commission the Safety Integrated function and carry out a POWER ON. – upgrade the Motor Module/Hydraulic Module software. – contact the Hotline. – replace the Motor Module/Hydraulic Module. |
F30650 SI P2: Acceptance test required | Cause: The “Safety Integrated” function on monitoring channel 2 requires an acceptance test. Fault value (r0949, interpret decimal): 130: Safety parameters for monitoring channel 2 not available. 1000: Reference and actual checksum in monitoring channel 2 are not identical (booting). 2000: Reference and actual checksum in monitoring channel 2 are not identical (commissioning mode). 2003: Acceptance test is required as a safety parameter has been changed. 2005: The safety logbook has identified that the safety checksums have changed. An acceptance test is required. 3003: Acceptance test is required as a hardware-related safety parameter has been changed. 9999: Subsequent response of another safety-related fault. Remedy: For fault value = 130: – carry out safety commissioning routine. For fault value = 1000: – check the Safety Integrated Basic Functions (r9880) and adapt the reference checksum (p9899). – again carry out safety commissioning routine. – Using STARTER, activate the safety parameters for the drive involved. – switch off and switch on the drive unit and DRIVE-CLiQ components. For fault value = 2000: – check the safety parameters on monitoring channel 2 and adapt the reference checksum (p9899). Re fault value = 2003, 2005: – Carry out an acceptance test and generate an acceptance report. For fault value = 3003: – carry out the function checks for the modified hardware and generate an acceptance report. For fault value = 9999: – carry out diagnostics for the other safety-related fault that is present. |
F30651 SI P2: Synchronization with Control Unit unsuccessful | Cause: The drive-integrated “Safety Integrated” function requires synchronization of the safety time slices in both monitoring channels. This synchronization routine was unsuccessful. Remedy: – carry out a POWER ON (power off/on) for all components. – upgrade the Motor Module/Hydraulic Module software. – upgrade the Control Unit software. |
F30652 SI P2: Illegal monitoring clock cycle | Cause: The Safety Integrated monitoring clock cycle cannot be maintained due to the communication conditions requested in the system. Remedy: – if fault F01652 simultaneously occurs, apply the remedy/countermeasure described there. – upgrade the firmware of the Motor Module/Hydraulic Module to a later version. |
F30655 SI P2: Align monitoring functions | Cause: An error has occurred when aligning the Safety Integrated monitoring functions of both monitoring channels. No common set of supported SI monitoring functions was able to be determined. – there is either a DRIVE-CLiQ communication error or communication has failed. – Safety Integrated software releases on the Control Unit and Motor Module/Hydraulic Module are not compatible with one another. Remedy: – carry out a POWER ON (power off/on) for all components. – upgrade the Motor Module/Hydraulic Module software. – upgrade the Control Unit software. – check the electrical cabinet design and cable routing for EMC compliance |
F30656 SI P2: Motor Module parameter error | Cause: When accessing the Safety Integrated parameters for monitoring channel 2 in the non-volatile memory, an error has occurred. Remedy: – re-commission the safety functions. – upgrade the Control Unit software. – upgrade the Motor Module/Hydraulic Module software. – replace the memory card or Control Unit. For fault value = 129: – activate the safety commissioning mode (p0010 = 95). – adapt the PROFIsafe address (p9610). – start the copy function for SI parameters (p9700 = D0 hex). – acknowledge data change (p9701 = DC hex). – exit the safety commissioning mode (p0010 = 0). – save all parameters (p0977 = 1 or “copy RAM to ROM”). – carry out a POWER ON (power off/on) for all components. |
F30657 SI P2: PROFIsafe telegram number invalid | Cause: The PROFIsafe telegram number set in p9811 is not valid. When PROFIsafe is enabled (p9801.3 = 1), then a telegram number greater than zero must be entered in p9811. Remedy: Check the telegram number setting (p9811). |
F30659 SI P2: Write request for parameter rejected | Cause: The write request for one or several Safety Integrated parameters in monitoring channel 2 was rejected. Fault value (r0949, interpret decimal): 10: An attempt was made to enable the STO function although this cannot be supported. 11/13: An attempt was made to enable the SBC/SS1 function although this cannot be supported. 14/15: An attempt was made to enable motion monitoring functions although these cannot be supported. 16/18: An attempt was made to enable PROFIsafe communication although this cannot be supported. 19: For ESR, an attempt was made to enable the delay for pulse suppression, although this cannot be supported. 27: An attempt was made to activate the Basic Functions by controlling via TM54F although this cannot be supported. 33: An attempt was made to enable the motion monitoring functions without selection integrated in the drive, although this cannot be supported. Remedy: Re fault value = 10, 11, 13, 14, 15, 16, 18, 19: – check whether there are faults in the safety function alignment between the two monitoring channels (F01655, F30655) and if required, carry out diagnostics for the faults involved. – use a Motor/Hydraulic Module that supports the required function. – upgrade the Motor/Hydraulic Module software. – upgrade the Control Unit software. For fault value = 33: – Deselect motion monitoring functions without selection integrated in drive and select safety functions that are supported. or: – use a Motor/Hydraulic Module that supports the required function. |
F30664 Error while booting | Cause: An error has occurred during booting. Remedy: – carry out a POWER ON (power off/on). – upgrade firmware to later version. – contact the Hotline. |
F30665 SI P2: System is defective | Cause: A system defect was detected before the last boot or in the actual one. The system might have been rebooted (reset). Remedy: – carry out a POWER ON (power off/on). – upgrade firmware to later version. – contact the Hotline. For fault value = 2: – check parameters p9500 and p9300 to see if they are the same. Re fault value = 400000 hex: – ensure that the Control Unit is connected to the Power Module. |
A30666 (F) SI Motion P2: Steady-state (static) 1 signal at the F-DI for safe acknowledgment | Cause: A logical 1 signal is present at the F-DI configured in p10106 for more than 10 seconds. If at the F-DI no acknowledgment was performed for safe acknowledgment, then a steady-state logical and 0 signal must be present. Remedy: Set the fail-safe digital input (F-DI) to a logical 0 signal (p10106). |
F30672 SI P2: Control Unit software incompatible | Cause: The existing Control Unit software does not support the safe drive-based motion monitoring function. Remedy: – check whether there are faults in the safety function alignment between the two monitoring channels (F01655, F30655) and if required, carry out diagnostics for the faults involved. – use a Control Unit that supports the safe motion monitoring function. – upgrade the Control Unit software. |
F30674 SI Motion P2: Safety function not supported by PROFIsafe telegram | Cause: The monitoring function enabled in p9301 and p9801 is not supported by the currently set PROFIsafe telegram (p9811). Remedy: – deselect the monitoring function involved (p9301, p9801). – set the matching PROFIsafe telegram (p9811). |
F30680 SI Motion P2: Checksum error safety monitoring functions | Cause: The actual checksum calculated by the Motor Module/Hydraulic Module and entered in r9398 over the safety-relevant parameters does not match the reference checksum saved in p9399 at the last machine acceptance. Safety-relevant parameters have been changed or a fault is present. Remedy: – check the safety-relevant parameters and if required, correct. – set the reference checksum to the actual checksum. – execute the function “Copy RAM to ROM”. – perform a POWER ON if safety parameters requiring a POWER ON have been modified. – carry out an acceptance test. |
F30681 SI Motion P1: Incorrect parameter value | Cause: The parameter cannot be parameterized with this value. Fault value (r0949, interpret decimal): xxxx = 9301: It is not permissible to enable certain functions in conjunction with others. xxxx = 9334 or 9335: The limit values of SLP have been set too high (absolute values). xxxx = 9385: For Safety without encoder and synchronous motor, p9385 must be set to 4. xxxx = 9801: Various combinations of PROFIsafe and other functions are not permissible. Remedy: Correct parameter (if required, also on another monitoring channel, p9601). If xxxx = 9301: Correct parameters p9501.16 and p9301.16 or deselect the extended functions without selection (p9801.5). If xxxx = 9501 and yyyy = 8: Inhibit referencing via SCC (p9501.27 = 1) or enable an absolute motion monitoring function (p9501.1 or p9501.2). If xxxx = 9334 or 9335: Reduce the limit values (absolute values) of SLP. If xxxx = 9801: yyyy = 1: Only enable motion monitoring functions integrated in the drive (p9801.2 = 1) and extended functions without selection (p9801.5 = 1) – or only PROFIsafe (p9801.3 = 1). yyyy = 2, 3: Enable motion monitoring functions integrated in the drive (p9801.2 = 1). yyyy = 5, 6, 7: To transfer certain values via PROFIsafe, you must also enable PROFIsafe (p9801.3 =1) and motion monitoring functions integrated in the drive (p9801.2 = 1). |
F30682 SI Motion P2: Monitoring function not supported | Cause: The monitoring function enabled in p9301, p9501, p9601, p9801, p9307 or p9507 is not supported in this firmware version. Remedy: – de-select the monitoring function involved (p9301, p9501, p9601, p9801, p9307, p9507). – Upgrade the Motor Module/Hydraulic Module firmware. |
F30683 SI Motion P2: SOS/SLS enable missing | Cause: The safety-relevant basic function “SOS/SLS” is not enabled in p9301 although other safety-relevant monitoring functions are enabled. Remedy: Enable the function “SOS/SLS” (p9301.0) and carry out a POWER ON. |
F30684 SI Motion P2: Safely limited position limit values interchanged | Cause: For the function “Safely Limited Position” (SLP), a lower value is in p9334 than in p9335. Remedy: – correct the lower and upper limit values (p9335, p9334). – carry out a POWER ON (power off/on). |
| Fault Code and Meaning | Cause and Remedy |
F30685 SI Motion P2: Safely-limited speed limit value too high | Cause: The limit value for the function “Safely-Limited Speed” (SLS) is greater than the speed that corresponds to an encoder limit frequency of 500 kHz. Remedy: Correct the limit values for SLS and carry out a POWER ON. |
F30688 SI Motion P2: Actual value synchronization not permissible | Cause: – It is not permissible to enable actual value synchronization for a 1-encoder system. – It is not permissible to simultaneously enable actual value synchronization and a monitoring function with absolute reference (SCA/SLP). – It is not permissible to simultaneously enable actual value synchronization and safe position via PROFIsafe. Remedy: – Either select the “actual value synchronization” function or parameterize a 2-encoder system. – Either de-select the function “actual value synchronization” or the monitoring functions with absolute reference (SCA/SLP) and carry out a POWER ON. – Either deselect the “actual value synchronization” function or do not enable “Safe position via PROFIsafe”. |
F30692 SI Motion P2: Parameter value not permitted for encoderless | Cause: The parameter cannot be parameterized with this value if encoderless motion monitoring functions have been parameterized in p9306. Remedy: – Correct the parameter specified in the fault value. – If necessary, de-select encoderless motion monitoring functions (p9306). |
A30693 (F) SI P2: Safety parameter settings changed, warm restart/POWER ON required | Cause: Safety parameters have been changed; these will only take effect following a warm restart or POWER ON. Remedy: – carry out a warm restart (p0009 = 30, p0976 = 2, 3). – carry out a POWER ON (power off/on) for all components. |
C30700 SI Motion P2: STOP A initiated | Cause: The drive is stopped via a STOP A (STO via the safety shutdown path of the Control Unit). Possible causes: – stop request from the Control Unit. – STO not active after a parameterized time (p9357) after test stop selection. – subsequent response to various C307xx messages. Remedy: – remove the cause to the fault on the Control Unit. – check the value in p9357, if required, increase the value. – check the shutdown path of the Control Unit (check DRIVE-CLiQ communication). – carry out a diagnostics routine for the respective C307xx messages. – replace the Motor Module, Power Module or Hydraulic Module. – replace Control Unit. This message can only be acknowledged via the Terminal Module 54F (TM54F) or PROFIsafe. |
C30701 SI Motion P2: STOP B initiated | Cause: The drive is stopped via a STOP B (braking along the OFF3 ramp). After the time parameterized in p9356 has expired or a speed threshold is passed, message C30700 “SI Motion MM: STOP A initiated” is output. Possible causes: – stop request from the Control Unit. – subsequent response to various C307xx messages. Remedy: – remove the cause to the fault on the Control Unit. – carry out a diagnostics routine for the respective messages. This message can only be acknowledged via the Terminal Module 54F (TM54F) or PROFIsafe. |
C30706 SI Motion P2: SAM/SBR limit exceeded | Cause: After initiating STOP B (SS1) or STOP C (SS2), the speed has exceeded the selected tolerance. For encoderless functions, after initiating STOP B or an SLS changeover, the speed has exceeded the tolerance. The drive is shut down by message C30700 “SI Motion MM: STOP A initiated”. Remedy: Check the braking behavior and, if necessary, adapt the parameterization of the “SAM” or the “SBR” function. This message can be acknowledged without a POWER ON via Terminal Module 54F (TM54F) or PROFIsafe. |
C30707 SI Motion P2: Tolerance for safe operating stop exceeded | Cause: The actual position has distanced itself further from the target position than the standstill tolerance. The drive is shut down by the message C30701 “SI Motion MM: STOP B initiated”. Remedy: – check whether safety faults are present and if required carry out the appropriate diagnostic routines. – check whether the standstill tolerance matches the accuracy and control dynamic performance of the axis. This message can only be acknowledged via the Terminal Module 54F (TM54F) or PROFIsafe. |
C30708 SI Motion P2: STOP C initiated | Cause: The drive is stopped via a STOP C (braking along the OFF3 ramp). “Safe Operating Stop” (SOS) is activated after the parameterized time has expired. Possible causes: – stop request from the higher-level control. – subsequent response to messages C30714, C01715, or C30716. Remedy: – remove the cause of the fault at the control. – carry out a diagnostics routine for messages C30714, C30715, C30716. This message can only be acknowledged via the Terminal Module 54F (TM54F) or PROFIsafe. |
C30709 SI Motion P2: STOP D initiated | Cause: The drive is stopped via a STOP D (braking along the path). “Safe Operating Stop” (SOS) is activated after the parameterized time has expired. Possible causes: – stop request from the Control Unit. – subsequent response to messages C30714, C01715, or C30716. Remedy: – remove the cause of the fault at the control. – carry out a diagnostics routine for messages C30714, C30715, C30716. This message can only be acknowledged via the Terminal Module 54F (TM54F) or PROFIsafe. |
C30710 SI Motion P2: STOP E initiated | Cause: The drive is stopped via a STOP E (retraction motion). “Safe Operating Stop” (SOS) is activated after the parameterized time has expired. Possible causes: – stop request from the higher-level control. – subsequent response to messages C30714, C01715, or C30716. Remedy: – remove the cause of the fault at the control. – carry out a diagnostics routine for messages C30714, C30715, C30716. This message can only be acknowledged via the Terminal Module 54F (TM54F) or PROFIsafe. |
C30711 SI Motion P2: Defect in a monitoring channel | Cause: When cross-comparing the two monitoring channels, the drive detected a difference between the input data or results of the monitoring functions and initiated a STOP F. One of the monitoring functions no longer reliably functions. Message value (r9749, interpret decimal): 0 … 999: Number of the cross-compared data that resulted in this message. 1000-1045: Various internal errors like watchdog timer, user agreement issues, plausibility violations, communication failures, etc. 5000-7002: PROFIsafe message values. Remedy: – For various message values, perform safe acknowledgment, check mechanical systems, check encoder parameters, upgrade firmware, check communication links, or replace hardware. – The significance of specific message values is described in safety messages C01711 or F01611. – This message can only be acknowledged via the Terminal Module 54F (TM54F) or PROFIsafe. |
C30712 SI Motion P2: Defect in F-IO processing | Cause: When cross checking and comparing the two monitoring channels, the drive detected a difference between parameters or results of the F-IO processing and initiated a STOP F. Remedy: – check parameterization in the parameters involved and correct if required. – ensure equality by copying the SI data to the second channel and then carry out an acceptance test. – check monitoring clock cycle for equality (p9500, p9300). |
C30714 SI Motion P2: Safely-Limited Speed exceeded | Cause: The drive had moved faster than that specified by the velocity limit value (p9331). The drive is stopped as a result of the configured stop response (p9363). Message value (r9749, interpret decimal): 100-400: SLS1-SLS4 exceeded. 1000: Encoder limit frequency exceeded. Remedy: – check the traversing/motion program in the control. – check the limits for “SLS” function and if required, adapt (p9331). |
C30715 SI Motion P2: Safely-Limited Position exceeded | Cause: The axis has moved past a parameterized position that is monitored by the “SLP” function. Message value (r9749, interpret decimal): 10: SLP1 violated. 20: SLP2 violated. Remedy: – check the traversing/motion program in the control. – check the limits for “SLP” function and if required, adapt (p9534, p9535). |
C30716 SI Motion P2: Tolerance for safe motion direction exceeded | Cause: The tolerance for the “safe motion direction” function was exceeded. The drive is stopped as a result of the configured stop response (p9366). Remedy: – check the traversing/motion program in the control. – check the tolerance for “SDI” function and if required, adapt (p9364). – Deselect the “SDI” function and select again. – Perform a safe acknowledgment via F-DI or PROFIsafe. |
C30730 SI Motion P2: Reference block for dynamic safely limited speed invalid | Cause: The reference block transferred via PROFIsafe is negative. A reference block is used to generate a referred velocity limit value based on the reference quantity “Velocity limit value SLS1” (p9331[0]). Remedy: In the PROFIsafe telegram, input data S_SLS_LIMIT_IST must be corrected. |
C30770 SI Motion P2: Discrepancy error of the fail-safe inputs/outputs | Cause: The fail-safe digital inputs/digital outputs (F-DI/F-DO) show a different state longer than that parameterized in p10002 / p10102. Remedy: – check the wiring of the F-DI (contact problems). – For cyclic switching operations, it may be necessary to adapt the discrepancy time to the switching frequency based on the provided formulas. |
A30772 SI Motion P2: Test stop failsafe inputs/outputs active | Cause: The test stop for the fail-safe digital inputs (F-DI) and/or fail-safe digital outputs (F-DO) is presently being performed. Remedy: The alarm disappears automatically after successfully ending or canceling the test stop. |
F30773 SI Motion P2: Test stop fault Motor Module | Cause: A fault has occurred on the MM side during the test stop for the fail-safe outputs. Fault value indicates the reason, channels involved, and state of the test stop. Remedy: Check the wiring of the F-DOs and restart the test stop. |
A30788 Automatic test stop: wait for STO deselection via SMM | Cause: The STO function is selected via Safety Extended Functions or a safety message is present, which results in STO. The automatic test stop was not able to be carried out since the power up. Remedy: – Deselect STO via Safety Extended Functions. – Remove the cause of the safety message and acknowledge the fault. |
C30797 SI Motion P2: Axis not safely referenced | Cause: The standstill position saved before powering down does not match the actual position determined at power-up. Message value (r9749, interpret decimal): 1: Axis not safely referenced. 2: User agreement missing. Remedy: If safe automatic referencing is not possible the user must issue a user agreement for the new position using the softkey. |
C30798 SI Motion P2: Test stop running | Cause: The test stop is active. Remedy: Not necessary. The message is withdrawn when the test stop is finished. |
C30799 SI Motion P2: Acceptance test mode active | Cause: The acceptance test mode is active. This means the setpoint velocity limiting is deactivated and standard limit switches are deactivated during the test. Remedy: Not necessary. The message is withdrawn when exiting the acceptance test mode. |
N30800 (F) Power unit: Group signal | Cause: The power unit has detected at least one fault. Remedy: Evaluate the other messages that are presently available. |
F30801 Power unit DRIVE-CLiQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. The computing time load might be too high. Remedy: – check the electrical cabinet design and cable routing for EMC compliance – remove DRIVE-CLiQ components that are not required. – de-select functions that are not required. – if required, increase the sampling times (p0112, p0115). – replace the component involved. |
F30802 Power unit: Time slice overflow | Cause: A time slice overflow has occurred. Remedy: – carry out a POWER ON (power off/on) for all components. – upgrade firmware to later version. – contact the Hotline. |
F30804 (N, A) Power unit: CRC | Cause: A CRC error has occurred for the power unit. Remedy: – carry out a POWER ON (power off/on) for all components. – upgrade firmware to later version. – contact the Hotline. |
F30805 Power unit: EEPROM checksum error | Cause: Internal parameter data is corrupted. Remedy: Replace the module. |
F30809 Power unit: Switching information not valid | Cause: For 3P gating unit, the following applies: The last switching status word in the setpoint telegram is identified by the end ID. Such an end ID was not found. Remedy: – carry out a POWER ON (power off/on) for all components. – upgrade firmware to later version. – contact the Hotline. |
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: – carry out a POWER ON (power off/on) for all components. – upgrade firmware to later version. – contact the Hotline. |
F30820 Power unit DRIVE-CLiQ: Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. Various fault causes are possible, including checksum errors, incorrect telegram length, type, or address, and synchronization issues. Remedy: – carry out a POWER ON (power off/on). – check the electrical cabinet design and cable routing for EMC compliance – check the DRIVE-CLiQ wiring (interrupted cable, contacts, …). |
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: – carry out a POWER ON. – replace the component involved. |
F30836 Power unit DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. Data were not able to be sent. Remedy: Carry out a POWER ON. |
F30837 Power unit DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. 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: – check the DRIVE-CLiQ wiring (interrupted cable, contacts, …). – check the electrical cabinet design and cable routing for EMC compliance – if required, use another DRIVE-CLiQ socket (p9904). – replace the component involved. |
A30840 Power unit DRIVE-CLiQ: error below the signaling threshold | Cause: A DRIVE-CLiQ error has occurred below the signaling threshold. Various fault causes are possible, including checksum errors, incorrect telegrams, timeouts, and buffer memory errors. Remedy: – check the electrical cabinet design and cable routing for EMC compliance – check the DRIVE-CLiQ wiring (interrupted cable, contacts, …). |
| 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:
|
| A30853 Power unit: Sign-of-life error cyclic data | Cause: The power unit has detected that the cyclic setpoint telegrams of the Control Unit have not been updated on time. At least two sign-of-life errors have occurred within the window set in p7788. Remedy:
|
| F30860 Power unit DRIVE-CLiQ (CU): Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the power unit to the Control Unit involved. Fault cause: A detailed list of fault causes from 1 to 25 is provided in the document. Remedy: Not explicitly listed, but generally involves checking communications and connections. |
| F30875 Power unit 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. 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 codes include 26, 33, 34, 64, 98 hex. 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. Various fault causes are listed, including telegram header errors, buffer memory errors, and response time issues. 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: If required, the significance of this new fault can be read about in a more recent description of the Control Unit. |
| F30903 Power unit: I2C bus error occurred | Cause: Communications error with an EEPROM or A/D converter. Remedy:
|
| F30907 Power unit: FPGA configuration unsuccessful | Cause: During initialization within the power unit, an internal software error has occurred. Remedy:
|
| A30919 Power unit: Temperature monitoring failed | Cause: The temperature monitoring in the power unit has failed. Fault-free operation of the drive system is no longer guaranteed. 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:
|
| A30930 (N) Power unit: Component trace has saved data | Cause: Trace data was saved in the component. Remedy:
|
| F30950 Power unit: Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Information about the fault source. Only for internal Siemens troubleshooting. Remedy:
|
| 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. For distance-coded encoders, the zero mark distance is determined from zero marks detected pairs. 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: Amplitude error track R | Cause: The amplitude of the reference track signal (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: Serial communication protocol transfer error between the encoder and evaluation module. Fault value (r0949, interpret binary) indicates specific issues like CRC error, no response, etc. Remedy: Remedies are provided for each specific fault bit (0-14), generally involving:
|
| F31111 (N, A) Encoder 1: Absolute encoder internal error | Cause: The absolute encoder fault word supplies fault bits that have been set. The fault value indicates specific issues such as lighting system failure, low signal amplitude, power supply issues, or battery problems. Remedy: Remedies are specific to the fault bit and generally involve:
|
| F31112 (N, A) Encoder 1: Error bit set in the serial protocol | Cause: The encoder sends a set error bit via the serial protocol. Fault value (r0949, interpret binary): Bit 0: Fault bit in the position protocol. Remedy:
|
| F31115 (N, A) Encoder 1: Amplitude error track A or B (A^2 + B^2) | Cause: The amplitude (root of A^2 + B^2) for encoder 1 exceeds the permissible tolerance. Remedy:
|
| F31116 (N, A) Encoder 1: Amplitude error monitoring track A + B | Cause: The amplitude of the rectified encoder signals A and B and the amplitude from the roots of A^2 + B^2 for encoder 1 are not within the tolerance bandwidth. Remedy:
|
| F31117 (N, A) Encoder 1: Inversion error signals A/B/R | Cause: For a square-wave encoder (bipolar, double ended) signals A*, B* and R* are not inverted with respect to signals A, B and R. Remedy:
|
| F31118 (N, A) Encoder 1: Speed difference outside the tolerance range | Cause: For an HTL/TTL encoder, the speed difference has exceeded the value in p0492 over several sampling cycles. Remedy:
|
| F31120 (N, A) Encoder 1: Power supply voltage fault | Cause: A power supply fault was detected for encoder 1. Fault value indicates specific issues like undervoltage, overcurrent, or overload. Remedy: Remedies are specific to the fault bit and generally involve:
|
| F31121 (N, A) Encoder 1: Coarse position error | Cause: For the actual value sensing, an error was detected on the module. As a result of this error, it must be assumed that the actual value sensing supplies an incorrect coarse position. Remedy:
|
| F31122 Encoder 1: Internal power supply voltage faulty | Cause: Fault in internal reference voltage of ASICs for encoder 1. Fault values indicate reference voltage error, internal undervoltage, or internal overvoltage. Remedy:
|
| F31123 (N, A) Encoder 1: Signal level A/B unipolar outside tolerance | Cause: The unipolar level (AP/AN or BP/BN) for encoder 1 is outside the permissible tolerance. Remedy:
|
| F31125 (N, A) Encoder 1: Amplitude error track A or B overcontrolled | Cause: The amplitude of track A or B for encoder 1 exceeds the permissible tolerance band. This fault also occurs if the A/D converter is overcontrolled. Remedy:
|
| F31126 (N, A) Encoder 1: Amplitude AB too high | Cause: The amplitude (root of A^2 + B^2 or |A| + |B|) for encoder 1 exceeds the permissible tolerance. Remedy:
|
| F31129 (N, A) Encoder 1: Position difference hall sensor/track C/D and A/B too large | Cause: The error for track C/D is greater than +/-15° mechanical or +/-60° electrical or the error for the Hall signals is greater than +/-60° electrical. 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. Fine synchronization was not carried out. Remedy:
|
| F31135 Encoder 1: Fault when determining the position | Cause: The encoder supplies status information bit by bit in an internal status/fault word. Some of these bits cause this fault to be triggered. Other bits are status displays. The status/fault word is displayed in the fault value. The fault value (r0949, interpret binary) provides a detailed bit-by-bit breakdown of the specific error source. Remedy:
|
| F31136 Encoder 1: Error when determining multiturn information | Cause: The encoder supplies status information bit by bit in an internal status/fault word. Some of these bits cause this fault to be triggered. The status/fault word is displayed in the fault value, which provides a detailed bit-by-bit breakdown of the error. Remedy:
|
| F31137 Encoder 1: Internal fault when determining the position | Cause: A position determination fault has occurred in the DRIVE-CLiQ encoder. The fault value (r0949, interpret binary) provides a bit-coded reason for the fault, which depends on the encoder version. For version yy = 08 hex, specific bits correspond to signal monitoring, safety status, LED monitoring, multiturn fault, and temperature issues. Remedy:
|
| F31138 Encoder 1: Internal error when determining multiturn information | Cause: A position determination fault has occurred in the DRIVE-CLiQ encoder. The fault value (r0949, interpret binary) provides a bit-coded reason for the fault. For version yy = 08 hex, specific bits correspond to signal monitoring and safety status display. 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 is not operating correctly. The fault value (r0949, interpret hexadecimal) indicates an encoder malfunction, with the bit assignment corresponding to that of p0404 (e.g. bit 5 set: Error track C/D). 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: Maximum input frequency exceeded | Cause: The maximum input frequency of the encoder evaluation has been exceeded. The actual input frequency in Hz is shown in the fault value (r0949). 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. Fault value indicates a data length incorrect error. Remedy:
|
| F31160 (N, A) Encoder 1: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. The fault value indicates whether the voltage is outside the detectable range (1), outside the set range (2), or has exceeded the absolute range limit (3). Remedy:
|
| F31161 (N, A) Encoder 1: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. The fault value indicates whether the voltage is outside the detectable range (1), outside the set range (2), or has exceeded the absolute range limit (3). 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. The fault value indicates whether the position is from the LVDT sensor (1) or the encoder characteristic (2). Remedy:
|
| A31400 (F, N) Encoder 1: Alarm threshold zero mark distance error | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. For distance-coded encoders, the zero mark distance is determined from zero marks detected pairs. Remedy:
|
| A31401 (F, N) Encoder 1: Alarm threshold zero mark failed | Cause: The 1.5 x parameterized zero mark distance was exceeded. The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder). Remedy:
|
| F31405 (N, A) Encoder 1: Temperature in the encoder evaluation inadmissible | Cause: The encoder evaluation for a motor with DRIVE-CLiQ has detected an inadmissible temperature. The fault threshold is 125 ° C. Remedy:
|
| A31407 (F, N) Encoder 1: Function limit reached | Cause: The encoder has reached one of its function limits. A service is recommended. Alarm values can indicate issues with incremental signals, absolute track, or code connection. Remedy:
|
| A31410 (F, N) Encoder 1: Serial communications | Cause: Serial communication protocol transfer error between the encoder and evaluation module. The alarm value (r2124, interpret binary) indicates the specific error, such as alarm bit, incorrect quiescent level, no response, CRC error, etc. Remedy:
|
| A31411 (F, N) Encoder 1: Absolute encoder signals internal alarms | Cause: The absolute encoder fault word includes alarm bits that have been set. The alarm value (r2124, interpret binary) specifies the alarm, such as frequency/temperature exceeded, battery discharged, or internal data errors. Remedy:
|
| A31412 (F, N) Encoder 1: Error bit set in the serial protocol | Cause: The encoder sends a set error bit via the serial protocol. The alarm value (r2124, interpret binary) indicates a fault bit or alarm bit in the position protocol. Remedy:
|
| A31414 (F, N) Encoder 1: Amplitude error track C or D (C^2 + D^2) | Cause: The amplitude (C^2 + D^2) of track C or D of the encoder or from the Hall signals, is not within the tolerance bandwidth. Remedy:
|
| N31415 (F, A) Encoder 1: Amplitude alarm track A or B (A^2 + B^2) | Cause: The amplitude (root of A^2 + B^2) for encoder 1 exceeds the permissible tolerance. Remedy:
|
| A31418 (F, N) Encoder 1: Speed difference per sampling rate exceeded | Cause: For an HTL/TTL encoder, the speed difference between two sampling cycles has exceeded the value in p0492. The change to the averaged speed actual value is monitored. 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. Specific limits for amplitude error, phase, and offset correction are defined. Remedy:
|
| A31421 (F, N) Encoder 1: Coarse position error | Cause: For the actual value sensing, an error was detected. As a result of this error, it must be assumed that the actual value sensing supplies an incorrect coarse position. Alarm value 3 indicates 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 and re-parameterized fault 31131 if the accumulator contains larger values than p4683 or p4684. 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 with the incorrect rotational sense. Remedy:
|
| A31431 (F, N) Encoder 1: Deviation position incremental/absolute too large | Cause: When the zero pulse is passed, a deviation in the incremental position was detected. For equidistant zero marks, subsequent marks must have n times the distance of the first. For distance-coded marks, subsequent pairs must have the expected distance. Remedy:
|
| A31432 (F, N) Encoder 1: Rotor position adaptation corrects deviation | Cause: For track A/B, pulses have been lost or too many have been counted. These pulses are presently being corrected. Remedy:
|
| A31442 (F, N) Encoder 1: Battery voltage pre-alarm | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The multiturn information can no longer be buffered if the battery voltage drops even further. Remedy:
|
| A31443 (F, N) Encoder 1: Unipolar CD signal level outside specification | Cause: The unipolar level (CP/CN or DP/DN) for encoder 1 is outside the permissible tolerance. The unipolar nominal signal level must be in the range 2500 mV +/- 500 mV. Remedy:
|
| A31460 (N) Encoder 1: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Alarm value indicates if voltage is outside detectable range, outside set range, or has exceeded range limit. Remedy:
|
| A31461 (N) Encoder 1: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Alarm value indicates if voltage is outside detectable range, outside set range, or has exceeded range limit. 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 indicates if the value is from the LVDT sensor or the encoder characteristic. Remedy:
|
| A31470 (F, N) Encoder 1: Soiling detected | Cause: In the case of the alternative encoder system interface on the Sensor Module Cabinet 30 (SMC30), encoder soiling is signaled via a 0 signal at terminal X521.7. Remedy:
|
| F31500 (N, A) Encoder 1: Position tracking traversing range exceeded | Cause: For a configured linear axis without modulo correction, the drive/encoder has exceeded the maximum possible traversing range. Remedy:
|
| F31501 (N, A) Encoder 1: Position tracking encoder position outside tolerance window | Cause: When powered down, the drive/encoder was moved through a distance greater than was parameterized in the tolerance window. It is possible that there is no longer any reference between the mechanical system and encoder. Remedy:
|
| 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:
|
| A31700 Encoder 1: Effectivity test does not supply the expected value | Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Fault value (r0949, 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. Remedy:
|
| F31802 (N, A) Encoder 1: Time slice overflow | Cause: A time slice overflow has occurred in encoder 1. The fault value (r0949, interpret hexadecimal) indicates the specific time slice that overflowed (e.g., fast, average, slow). Remedy:
|
| F31804 (N, A) Encoder 1: Checksum error | Cause: A checksum error has occurred when reading-out the program memory on the Sensor Module. The fault value (r0949, interpret hexadecimal) indicates the memory area involved and the checksum difference. Remedy:
|
| F31805 (N, A) Encoder 1: 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:
|
| F31806 (N, A) Encoder 1: Initialization error | Cause: The encoder was not successfully initialized. The fault value (r0949, interpret hexadecimal) provides a detailed list of bit-coded causes, including unsuccessful mid-voltage matching for various tracks, internal ADC or register faults, and EnDat 2.2 initialization errors. Remedy:
|
| A31811 (F, N) Encoder 1: Encoder serial number changed | Cause: The serial number of the motor encoder has changed. This can be due to:
Remedy:
|
| F31812 (N, A) Encoder 1: Requested cycle or RX-/TX timing not supported | Cause: A cycle requested from the Control Unit or RX/TX timing is not supported. The fault value (r0949, interpret decimal) specifies the exact issue: 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 DRIVE-CLiQ encoder fault word supplies fault bits that have been set. 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. Multiple fault causes are possible, including checksum error, incorrect telegram length/type/address, or timing issues (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: Can be due to a cyclic telegram not being received, or a timeout in the receive or 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 causes can be an error in the telegram header or a send/receive error where the telegram buffer memory contains an error. Remedy:
|
| A31840 Encoder 1 DRIVE-CLIQ: error below the signaling threshold | Cause: A DRIVE-CLIQ error has occurred below the signaling threshold. There is an extensive list of possible fault causes, including CRC error, incorrect telegram length/type, sync telegram errors, sign-of-life bit not set, synchronization error, and buffer memory errors. 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. The fault value (r0949, interpret decimal) gives a detailed code for the specific error, ranging from blocked time slices and checksum errors to issues with EEPROM data, AD converter communication, and DRIVE-CLiQ initialization. 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. An extensive list of possible fault causes is provided, including checksum errors, incorrect telegram length/type/address, and timing issues (telegram too early/late). Remedy:
|
| F31875 (N, A) Encoder 1 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. 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 causes include sign-of-life bit not set and telegram too early, cyclic telegram not received, or timeout in send/receive list. 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: Errors in the telegram header, or send/receive errors in the telegram buffer memory. 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), specified by the fault value, have changed in an incompatible fashion with respect to the properties when booted. One cause can be, e.g. that a DRIVE-CLiQ cable or DRIVE-CLiQ component has been replaced. Remedy:
|
| F31899 (N, A) Encoder 1: Unknown fault | Cause: A fault occurred on the Sensor Module for encoder 1 that cannot be interpreted by the Control Unit firmware. 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. The fault value is for internal Siemens troubleshooting. Remedy:
|
| A31903 (F, N) Encoder 1: I2C-BUS error occurred | Cause: Error when operating the internal I2C bus. The fault value is for internal Siemens troubleshooting. Remedy:
|
| F31905 (N, A) Encoder 1: Parameterization error | Cause: A parameter of encoder 1 was detected as being incorrect. It is possible that the parameterized encoder type does not match the connected encoder. The fault value provides detailed information on the specific error, such as unsupported HTL level, incorrect SSI encoder configuration, or mismatched pole pair width. Remedy:
|
| F31912 Encoder 1: Device combination is not permissible | Cause: The selected device combination is not supported. The fault value gives specific reasons, e.g., the connected measuring unit cannot be operated with the EnDat 2.2 converter, the measuring unit type is not supported, or the maximum EnDat transfer duration was exceeded. Remedy:
|
| A31915 (F, N) Encoder 1: 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 that can no longer be represented within 32 bits. Remedy:
|
| F31916 (N, A) Encoder 1: Parameterization fault | Cause: A parameter of encoder 1 was detected as being incorrect. The parameterized encoder type may not match the connected encoder, or for the ENCODER drive object, the selected type (rotary/linear) might not match the function module setting (r0108.12). Remedy:
|
| A31920 (F, N) Encoder 1: Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred. Fault cause: 1 (= 01 hex): Wire breakage or sensor not connected (KTY: R > 1630 Ohm). 2 (= 02 hex): Measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm). 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 in the folder /USER/SINAMICS/DATA/. Remedy:
|
| A31940 (F, N) Encoder 1: Spindle sensor S1 voltage incorrect | Cause: The voltage of analog sensor S1 is outside the permissible range. The fault value (r0949, interpret decimal) indicates the signal level from sensor S1. Remedy:
|
| F31950 Encoder 1: Internal software error | Cause: An internal software error has occurred. The fault value (r0949, interpret decimal) contains information regarding the fault source, which is for internal Siemens troubleshooting only. Remedy:
|
| A31999 (F, N) Encoder 1: Unknown alarm | Cause: An alarm has occurred on the Sensor Module for encoder 1 that cannot be interpreted by the Control Unit firmware. 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. For distance-coded encoders, the zero mark distance is determined from zero marks detected pairs. Remedy:
|
| F32101 (N, A) Encoder 2: 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:
|
| F32103 (N, A) Encoder 2: Amplitude error track R | Cause: The amplitude of the reference track signal (track R) does not lie within the tolerance bandwidth for encoder 2. The fault can be initiated when the unipolar voltage level is exceeded or if the differential amplitude is undershot. Remedy:
|
| F32110 (N, A) Encoder 2: Serial communications error | Cause: Serial communication protocol transfer error between the encoder and evaluation module. The fault value (r0949, interpret binary) gives a detailed bit-by-bit cause (e.g., CRC error, no response, timeout). Remedy:
|
| F32111 (N, A) Encoder 2: Absolute encoder internal fault | Cause: The absolute encoder fault word supplies fault bits that have been set. The fault value (r0949, interpret binary) gives a detailed bit-by-bit cause (e.g., lighting system failed, low signal amplitude, power supply over/undervoltage, battery change required). Remedy:
|
| F32112 (N, A) Encoder 2: Error bit set in the serial protocol | Cause: The encoder sends a set error bit via the serial protocol. Fault value (r0949, interpret binary): Bit 0: Fault bit in the position protocol. Remedy:
|
| F32115 (N, A) Encoder 2: Amplitude error track A or B (A^2 + B^2) | Cause: The amplitude (root of A^2 + B^2) for encoder 2 exceeds the permissible tolerance. Remedy:
|
| F32116 (N, A) Encoder 2: Amplitude error monitoring track A + B | Cause: The amplitude of the rectified encoder signals A and B and the amplitude from the roots of A^2 + B^2 for encoder 2 are not within the tolerance bandwidth. Remedy:
|
| F32117 (N, A) Encoder 2: Inversion error signals A/B/R | Cause: For a square-wave encoder (bipolar, double ended), signals A*, B*, and R* are not inverted with respect to signals A, B, and R. The fault value indicates which track has an error. Remedy:
|
| F32118 (N, A) Encoder 2: Speed difference outside the tolerance range | Cause: For an HTL/TTL encoder, the speed difference has exceeded the value in p0492 over several sampling cycles. Remedy:
|
| F32120 (N, A) Encoder 2: Power supply voltage fault | Cause: A power supply fault was detected for encoder 2. The fault value (r0949, interpret binary) gives a detailed bit-by-bit cause (e.g., undervoltage, overcurrent, overload, or hardware fault at the EnDat connection). Remedy:
|
| F32121 (N, A) Encoder 2: Coarse position error | Cause: For the actual value sensing, an error was detected on the module. As a result, it must be assumed that the actual value sensing supplies an incorrect coarse position. Remedy:
|
| F32122 Encoder 2: Internal power supply voltage faulty | Cause: Fault in internal reference voltage of ASICs for encoder 2. The fault value (r0949, interpret decimal) indicates if it is a reference voltage error, internal undervoltage, or internal overvoltage. Remedy:
|
| F32123 (N, A) Encoder 2: Signal level A/B unipolar outside tolerance | Cause: The unipolar level (AP/AN or BP/BN) for encoder 2 is outside the permissible tolerance. The nominal signal level must be in the range 2500 mV +/- 500 mV. Remedy:
|
| F32125 (N, A) Encoder 2: Amplitude error track A or B overcontrolled | Cause: The amplitude of track A or B for encoder 2 exceeds the permissible tolerance band. This fault also occurs if the A/D converter is overcontrolled. Remedy:
|
| F32126 (N, A) Encoder 2: Amplitude AB too high | Cause: The amplitude (root of A^2 + B^2 or |A| + |B|) for encoder 2 exceeds the permissible tolerance. Remedy:
|
| F32129 (N, A) Encoder 2: Position difference hall sensor/track C/D and A/B too large | Cause: The error for track C/D is greater than +/-15° mechanical or +/-60° electrical, or the error for the Hall signals is greater than +/-60° electrical. Remedy:
|
| F32130 (N, A) Encoder 2: Zero mark and position error from the coarse synchronization | Cause: After initializing the pole position, the zero mark was detected outside the permissible range. Fine synchronization was not carried out. Remedy:
|
| F32131 (N, A) Encoder 2: Deviation position incremental/absolute too large | Cause: Absolute encoder: When cyclically reading the absolute position, an excessively high difference to the incremental position was detected. Incremental encoder: When the zero pulse is passed, a deviation in the incremental position was detected. Remedy:
|
| F32135 Encoder 2: Fault when determining the position | Cause: The encoder supplies status information bit by bit in an internal status/fault word. Some of these bits trigger the fault. The fault value (r0949, interpret binary) provides a detailed bit-by-bit breakdown of the error. Remedy:
|
| F32136 Encoder 2: Error when determining multiturn information | Cause: The encoder supplies status information bit by bit in an internal status/fault word. The fault value (r0949, interpret binary) provides a detailed bit-by-bit breakdown of the error related to multiturn information. Remedy:
|
| F32137 Encoder 2: Internal fault when determining the position | Cause: A position determination fault has occurred in the DRIVE-CLiQ encoder. The fault value (r0949, interpret binary) provides a bit-coded reason, specific to the encoder version. Remedy:
|
| F32138 Encoder 2: Internal error when determining multiturn information | Cause: A position determination fault has occurred in the DRIVE-CLiQ encoder. The fault value (r0949, interpret binary) provides a bit-coded reason, specific to the encoder version. Remedy:
|
| F32142 (N, A) Encoder 2: Battery voltage fault | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The battery voltage is no longer sufficient to check the multiturn information. Remedy:
|
| F32150 (N, A) Encoder 2: Initialization error | Cause: Encoder functionality selected in p0404 is not operating correctly. The fault value indicates an encoder malfunction, and the bit assignment corresponds to p0404. Remedy:
|
| F32151 (N, A) Encoder 2: Encoder speed for initialization AB too high | Cause: The encoder speed is too high while initializing the Sensor Module. Remedy:
|
| F32152 (N, A) Encoder 2: Maximum input frequency exceeded | Cause: The maximum input frequency of the encoder evaluation has been exceeded. The fault value shows the 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. Remedy:
|
| F32160 (N, A) Encoder 2: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. The fault value indicates if the voltage is outside the detectable range, outside the set range, or has exceeded the absolute range limit. Remedy:
|
| F32161 (N, A) Encoder 2: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. The fault value indicates if the voltage is outside the detectable range, outside the set range, or has exceeded the absolute range limit. 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. The fault value indicates if the position value is from the LVDT sensor or the encoder characteristic. Remedy:
|
| A32400 (F, N) Encoder 2: Alarm threshold zero mark distance error | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. Remedy:
|
| A32401 (F, N) Encoder 2: Alarm threshold zero mark failed | Cause: The 1.5 x parameterized zero mark distance was exceeded. Remedy:
|
| F32405 (N, A) Encoder 2: Temperature in the encoder evaluation inadmissible | Cause: The encoder evaluation for a motor with DRIVE-CLiQ has detected an inadmissible temperature. The fault threshold is 125 °C. Remedy:
|
| A32407 (F, N) Encoder 2: Function limit reached | Cause: The encoder has reached one of its function limits. A service is recommended. Alarm value indicates the specific limit reached (e.g., incremental signals, absolute track). Remedy:
|
| A32410 (F, N) Encoder 2: Serial communications | Cause: Serial communication protocol transfer error between the encoder and evaluation module. The alarm value (r2124, interpret binary) indicates the specific issue (e.g., Alarm bit, incorrect quiescent level, CRC error). Remedy:
|
| A32411 (F, N) Encoder 2: Absolute encoder signals internal alarms | Cause: The absolute encoder fault word includes alarm bits that have been set. The alarm value (r2124, interpret binary) provides details on the specific alarm (e.g., frequency exceeded, temperature exceeded, battery discharged). Remedy:
|
| A32412 (F, N) Encoder 2: Error bit set in the serial protocol | Cause: The encoder sends a set error bit via the serial protocol. The alarm value (r2124, interpret binary) indicates a fault or alarm bit in the position protocol. Remedy:
|
| A32414 (F, N) Encoder 2: Amplitude error track C or D (C^2 + D^2) | Cause: The amplitude of track C or D of the encoder or from the Hall signals is not within the tolerance bandwidth. Remedy:
|
| N32415 (F, A) Encoder 2: Amplitude alarm track A or B (A^2 + B^2) | Cause: The amplitude (root of A^2 + B^2) for encoder 2 exceeds the permissible tolerance. Remedy:
|
| A32418 (F, N) Encoder 2: Speed difference per sampling rate exceeded | Cause: For an HTL/TTL encoder, the speed difference between two sampling cycles has exceeded the value in p0492. Remedy:
|
| A32419 (F, N) Encoder 2: Track A or B outside tolerance | Cause: The amplitude/phase/offset correction for track A or B is at the limit. Remedy:
|
| A32421 (F, N) Encoder 2: Coarse position error | Cause: For the actual value sensing, an error was detected. As a result of this error, it must be assumed that the actual value sensing supplies an incorrect coarse position. Remedy:
|
| A32422 (F, N) Encoder 2: Pulses per revolution square-wave encoder outside tolerance bandwidth | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. Remedy:
|
| A32429 (F, N) Encoder 2: Position difference hall sensor/track C/D and A/B too large | Cause: The error for track C/D is greater than +/-15° mechanical or +/-60° electrical or the error for the Hall signals is greater than +/-60° electrical. Remedy:
|
| A32431 (F, N) Encoder 2: Deviation position incremental/absolute too large | Cause: When the zero pulse is passed, a deviation in the incremental position was detected. Remedy:
|
| A32432 (F, N) Encoder 2: Rotor position adaptation corrects deviation | Cause: For track A/B, pulses have been lost or too many have been counted. These pulses are presently being corrected. Remedy:
|
| A32442 (F, N) Encoder 2: Battery voltage pre-alarm | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The multiturn information can no longer be buffered if the battery voltage drops even further. Remedy:
|
| A32443 (F, N) Encoder 2: Unipolar CD signal level outside specification | Cause: The unipolar level (CP/CN or DP/DN) for encoder 2 is outside the permissible tolerance. Remedy:
|
| A32460 (N) Encoder 2: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
| A32461 (N) Encoder 2: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
| A32462 (N) Encoder 2: Analog sensor no channel active | Cause: Channel A and B are not activated for the analog sensor. Remedy:
|
| A32463 (N) Encoder 2: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Remedy:
|
| A32470 (F, N) Encoder 2: Soiling detected | Cause: In the case of the alternative encoder system interface on the Sensor Module Cabinet 30 (SMC30), encoder soiling is signaled via a 0 signal at terminal X521.7. Remedy:
|
| F32500 (N, A) Encoder 2: Position tracking traversing range exceeded | Cause: For a configured linear axis without modulo correction, the drive/encoder has exceeded the maximum possible traversing range. Remedy:
|
| F32501 (N, A) Encoder 2: Position tracking encoder position outside tolerance window | Cause: When powered down, the drive/encoder was moved through a distance greater than was parameterized in the tolerance window. Remedy:
|
| F32502 (N, A) Encoder 2: Encoder with measuring gear without valid signals | Cause: The encoder with measuring gear no longer provides any valid signals. Remedy:
|
| F32503 (N, A) Encoder 2: Position tracking cannot be reset | Cause: The position tracking for the measuring gear cannot be reset. Remedy:
|
| A32700 Encoder 2: Effectivity test does not supply the expected value | Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Fault value (r0949, 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. The sign-of-life bit in the receive telegram is not set. Remedy:
|
| F32802 (N, A) Encoder 2: Time slice overflow | Cause: A time slice overflow has occurred in encoder 2. Remedy:
|
| F32804 (N, A) Encoder 2: Checksum error | Cause: A checksum error has occurred when reading-out the program memory on the Sensor Module. Remedy:
|
| F32805 (N, A) Encoder 2: EEPROM checksum error | Cause: Internal parameter data is corrupted. Remedy:
|
| F32806 (N, A) Encoder 2: Initialization error | Cause: The encoder was not successfully initialized. The fault value indicates the specific error with bit-coding. Remedy:
|
| A32811 (F, N) Encoder 2: Encoder serial number changed | Cause: The encoder serial number has changed (e.g., the encoder was replaced). 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. Remedy:
|
| F32813 Encoder 2: Hardware logic unit failed | Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set (ALU watchdog or 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. (Checksum error, telegram too short/long, etc.) Remedy:
|
| F32835 (N, A) Encoder 2 DRIVE-CLIQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred. The nodes do not send and receive in synchronism. Remedy:
|
| F32836 (N, A) Encoder 2 DRIVE-CLIQ: Send error for DRIVE-CLIQ data | Cause: A DRIVE-CLiQ communication error has occurred. Data were not able to be sent because the telegram type does not match the send list. Remedy:
|
| F32837 (N, A) Encoder 2 DRIVE-CLIQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded (e.g., error in telegram header/buffer). Remedy:
|
| A32840 Encoder 2 DRIVE-CLIQ: error below the signaling threshold | Cause: A DRIVE-CLiQ error has occurred below the signaling threshold. (Multiple possible telegram-related causes). 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 due to a synchronization error during alternating cyclic data transfer. 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. 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 sign-of-life bit in the receive telegram is not set. 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. Remedy:
|
F32875 (N, A) Encoder 2 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. Remedy:
|
F32885 (N, A) Encoder 2 DRIVE-CLIQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. The nodes do not send and receive in synchronism. Remedy:
|
F32886 (N, A) Encoder 2 DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. Data were not able to be sent. 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. Remedy:
|
F32895 (N, A) Encoder 2 DRIVE-CLIQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLIQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. Remedy:
|
F32896 (N, A) Encoder 2 DRIVE-CLIQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (Sensor Module for encoder 2), specified by the fault value, have changed in an incompatible fashion with respect to the properties when booted. One cause can be, e.g. that a DRIVE-CLiQ cable or DRIVE-CLiQ component has been replaced. Remedy:
|
F32899 (N, A) Encoder 2: Unknown fault | Cause: A fault occurred on the Sensor Module for encoder 2 that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. 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: Parameterization error | Cause: A parameter of encoder 2 was detected as being incorrect. It is possible that the parameterized encoder type does not match the connected encoder. Remedy:
|
F32912 Encoder 2: Device combination is not permissible | Cause: The selected device combination is not supported. Remedy:
|
A32915 (F, N) Encoder 2: Configuration error | Cause: The configuration for encoder 2 is incorrect. Remedy:
|
F32916 (N, A) Encoder 2: Parameterization fault | Cause: A parameter of encoder 2 was detected as being incorrect. It is possible that the parameterized encoder type does not match the connected encoder. Remedy:
|
A32920 (F, N) Encoder 2: Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred. Remedy:
|
A32930 (N) Encoder 2: Data logger has saved data | Cause: For the activated function “Data logger” (p0437.0 = 1) a fault has occurred with the Sensor Module. This alarm indicates that the diagnostics data corresponding to the fault was saved on the memory card. Remedy: Not necessary. The alarm disappears automatically. The data logger is ready to record the next fault case. |
A32940 (F, N) Encoder 2: Spindle sensor S1 voltage incorrect | Cause: The voltage of analog sensor S1 is outside the permissible range. Remedy:
|
F32950 Encoder 2: Internal software error | Cause: An internal software error has occurred. Remedy:
|
A32999 (F, N) Encoder 2: Unknown alarm | Cause: An alarm has occurred on the Sensor Module for encoder 2 that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Remedy:
|
F33100 (N, A) Encoder 3: Zero mark distance error | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. Remedy:
|
F33101 (N, A) Encoder 3: Zero mark failed | Cause: The 1.5 x parameterized zero mark distance was exceeded. Remedy:
|
F33103 (N, A) Encoder 3: Amplitude error track R | Cause: The amplitude of the reference track signal (track R) does not lie within the tolerance bandwidth for encoder 3. Remedy:
|
F33110 (N, A) Encoder 3: Serial communications error | Cause: Serial communication protocol transfer error between the encoder and evaluation module. Remedy:
|
F33111 (N, A) Encoder 3: Absolute encoder internal fault | Cause: The absolute encoder fault word supplies fault bits that have been set. Remedy:
|
F33112 (N, A) Encoder 3: Error bit set in the serial protocol | Cause: The encoder sends a set error bit via the serial protocol. Remedy: In the case of an EnDat encoder, F31111 may provide further details. |
F33115 (N, A) Encoder 3: Amplitude error track A or B (A^2 + B^2) | Cause: The amplitude (root of A^2 + B^2) for encoder 3 exceeds the permissible tolerance. Remedy:
|
F33116 (N, A) Encoder 3: Amplitude error monitoring track A + B | Cause: The amplitude of the rectified encoder signals A and B and the amplitude from the roots of A^2 + B^2 for encoder 3 are not within the tolerance bandwidth. Remedy:
|
F33117 (N, A) Encoder 3: Inversion error signals A/B/R | Cause: For a square-wave encoder (bipolar, double ended) signals A*, B* and R* are not inverted with respect to signals A, B and R. Remedy:
|
F33118 (N, A) Encoder 3: Speed difference outside the tolerance range | Cause: For an HTL/TTL encoder, the speed difference has exceeded the value in p0492 over several sampling cycles. Remedy:
|
F33120 (N, A) Encoder 3: Power supply voltage fault | Cause: A power supply fault was detected for encoder 3. Remedy:
|
F33121 (N, A) Encoder 3: Coarse position error | Cause: For the actual value sensing, an error was detected on the module. As a result of this error, it must be assumed that the actual value sensing supplies an incorrect coarse position. Remedy: Replace the motor with DRIVE-CLiQ or the appropriate Sensor Module. |
F33122 Encoder 3: Internal power supply voltage faulty | Cause: Fault in internal reference voltage of ASICs for encoder 3. Remedy: Replace the motor with DRIVE-CLiQ or the appropriate Sensor Module. |
F33123 (N, A) Encoder 3: Signal level A/B unipolar outside tolerance | Cause: The unipolar level (AP/AN or BP/BN) for encoder 3 is outside the permissible tolerance. Remedy:
|
F33125 (N, A) Encoder 3: Amplitude error track A or B overcontrolled | Cause: The amplitude of track A or B for encoder 3 exceeds the permissible tolerance band. Remedy:
|
F33126 (N, A) Encoder 3: Amplitude AB too high | Cause: The amplitude (root of A^2 + B^2 or |A| + |B|) for encoder 3 exceeds the permissible tolerance. Remedy:
|
F33129 (N, A) Encoder 3: Position difference hall sensor/track C/D and A/B too large | Cause: The error for track C/D is greater than +/-15° mechanical or +/-60° electrical or the error for the Hall signals is greater than +/-60° electrical. Remedy:
|
F33130 (N, A) Encoder 3: Zero mark and position error from the coarse synchronization | Cause: After initializing the pole position using track C/D, Hall signals or pole position identification routine, the zero mark was detected outside the permissible range. Remedy:
|
F33131 (N, A) Encoder 3: Deviation position incremental/absolute too large | Cause: 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. Incremental encoder: When the zero pulse is passed, a deviation in the incremental position was detected. Remedy:
|
F33135 Encoder 3: Fault when determining the position | Cause: The encoder supplies status information bit by bit in an internal status/fault word. Some of these bits cause this fault to be triggered. Other bits are status displays. The status/fault word is displayed in the fault value. Remedy:
|
F33136 Encoder 3: Error when determining multiturn information | Cause: The encoder supplies status information bit by bit in an internal status/fault word. Some of these bits cause this fault to be triggered. Other bits are status displays. The status/fault word is displayed in the fault value. Remedy:
|
F33137 Encoder 3: Internal fault when determining the position | Cause: A position determination fault has occurred in the DRIVE-CLIQ encoder. Remedy:
|
F33138 Encoder 3: Internal error when determining multiturn information | Cause: A position determination fault has occurred in the DRIVE-CLIQ encoder. 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 to check the multiturn information. Remedy:
|
F33150 (N, A) Encoder 3: Initialization error | Cause: Encoder functionality selected in p0404 is not operating correctly. Remedy:
|
F33151 (N, A) Encoder 3: Encoder speed for initialization AB too high | Cause: The encoder speed is too high while initializing the Sensor Module. Remedy:
|
F33152 (N, A) Encoder 3: Maximum input frequency exceeded | Cause: The maximum input frequency of the encoder evaluation has been exceeded. Remedy:
|
F33153 (N, A) Encoder 3: Identification error | Cause: An error has occurred when identifying the encoder (waiting) p0400=10100. The connected encoder was not able to be identified. Remedy:
|
F33160 (N, A) Encoder 3: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
F33161 (N, A) Encoder 3: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
F33163 (N, A) Encoder 3: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Remedy:
|
A33400 (F, N) Encoder 3: Alarm threshold zero mark distance error | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. Remedy:
|
A33401 (F, N) Encoder 3: Alarm threshold zero mark failed | Cause: The 1.5 x parameterized zero mark distance was exceeded. Remedy:
|
F33405 (N, A) Encoder 3: Temperature in the encoder evaluation inadmissible | Cause: The encoder evaluation for a motor with DRIVE-CLiQ has detected an inadmissible temperature. The fault threshold is 125 °C. Remedy:
|
A33407 (F, N) Encoder 3: Function limit reached | Cause: The encoder has reached one of its function limits. A service is recommended. Remedy:
|
A33410 (F, N) Encoder 3: Serial communications | Cause: Serial communication protocol transfer error between the encoder and evaluation module. Remedy:
|
A33411 (F, N) Encoder 3: Absolute encoder signals internal alarms | Cause: The absolute encoder fault word includes alarm bits that have been set. Remedy:
|
A33412 (F, N) Encoder 3: Error bit set in the serial protocol | Cause: The encoder sends a set error bit via the serial protocol. Remedy:
|
A33414 (F, N) Encoder 3: Amplitude error track C or D (C^2 + D^2) | Cause: The amplitude (C^2 + D^2) of track C or D of the encoder or from the Hall signals, is not within the tolerance bandwidth. Remedy:
|
N33415 (F, A) Encoder 3: Amplitude alarm track A or B (A^2 + B^2) | Cause: The amplitude (root of A^2 + B^2) for encoder 3 exceeds the permissible tolerance. Remedy:
|
A33418 (F, N) Encoder 3: Speed difference per sampling rate exceeded | Cause: For an HTL/TTL encoder, the speed difference between two sampling cycles has exceeded the value in p0492. Remedy:
|
A33419 (F, N) Encoder 3: Track A or B outside tolerance | Cause: The amplitude/phase/offset correction for track A or B is at the limit. Remedy:
|
A33421 (F, N) Encoder 3: Coarse position error | Cause: For the actual value sensing, an error was detected. As a result of this error, it must be assumed that the actual value sensing supplies an incorrect coarse position. Remedy:
|
A33422 (F, N) Encoder 3: Pulses per revolution square-wave encoder outside tolerance bandwidth | Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. Remedy:
|
A33429 (F, N) Encoder 3: Position difference hall sensor/track C/D and A/B too large | Cause: The error for track C/D is greater than +/-15° mechanical or +/-60° electrical or the error for the Hall signals is greater than +/-60° electrical. Remedy:
|
A33431 (F, N) Encoder 3: Deviation position incremental/absolute too large | Cause: When the zero pulse is passed, a deviation in the incremental position was detected. Remedy:
|
A33432 (F, N) Encoder 3: Rotor position adaptation corrects deviation | Cause: For track A/B, pulses have been lost or too many have been counted. These pulses are presently being corrected. Remedy:
|
A33442 (F, N) Encoder 3: Battery voltage pre-alarm | Cause: When switched-off, the encoder uses a battery to back up the multiturn information. The multiturn information can no longer be buffered if the battery voltage drops even further. Remedy:
|
A33443 (F, N) Encoder 3: Unipolar CD signal level outside specification | Cause: The unipolar level (CP/CN or DP/DN) for encoder 3 is outside the permissible tolerance. Remedy:
|
A33460 (N) Encoder 3: Analog sensor channel A failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
A33461 (N) Encoder 3: Analog sensor channel B failed | Cause: The input voltage of the analog sensor is outside the permissible limits. Remedy:
|
A33462 (N) Encoder 3: Analog sensor no channel active | Cause: Channel A and B are not activated for the analog sensor. Remedy:
|
A33463 (N) Encoder 3: Analog sensor position value exceeds limit value | Cause: The position value has exceeded the permissible range of -0.5 … +0.5. Remedy:
|
A33470 (F, N) Encoder 3: Soiling detected | Cause: In the case of the alternative encoder system interface on the Sensor Module Cabinet 30 (SMC30), encoder soiling is signaled via a 0 signal at terminal X521.7. Remedy:
|
F33500 (N, A) Encoder 3: Position tracking traversing range exceeded | Cause: For a configured linear axis without modulo correction, the drive/encoder has exceeded the maximum possible traversing range. Remedy:
|
F33501 (N, A) Encoder 3: Position tracking encoder position outside tolerance window | Cause: When powered down, the drive/encoder was moved through a distance greater than was parameterized in the tolerance window. It is possible that there is no longer any reference between the mechanical system and encoder. Remedy:
|
F33502 (N, A) Encoder 3: Encoder with measuring gear without valid signals | Cause: The encoder with measuring gear no longer provides any valid signals. Remedy:
|
F33503 (N, A) Encoder 3: Position tracking cannot be reset | Cause: The position tracking for the measuring gear cannot be reset. 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:
|
N33800 (F) Encoder 3: Group signal | Cause: The motor encoder has detected at least one fault. Remedy:
|
F33801 (N, A) Encoder 3 DRIVE-CLIQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Remedy:
|
F33802 (N, A) Encoder 3: Time slice overflow | Cause: A time slice overflow has occurred in encoder 3. Remedy:
|
F33804 (N, A) Encoder 3: Checksum error | Cause: A checksum error has occurred when reading-out the program memory on the Sensor Module. Remedy:
|
F33805 (N, A) Encoder 3: EEPROM checksum error | Cause: Internal parameter data is corrupted. Remedy:
|
F33806 (N, A) Encoder 3: Initialization error | Cause: The encoder was not successfully initialized. Remedy:
|
A33811 (F, N) Encoder 3: Encoder serial number changed | Cause: The encoder serial number has changed. The change is only checked for encoders with serial number (e.g. EnDat encoders). The encoder was replaced. Remedy:
|
F33812 (N, A) Encoder 3: Requested cycle or RX-/TX timing not supported | Cause: A cycle requested from the Control Unit or RX/TX timing is not supported. Remedy:
|
F33813 Encoder 3: Hardware logic unit failed | Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Remedy:
|
F33820 (N, A) Encoder 3 DRIVE-CLIQ: Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. Remedy:
|
F33835 (N, A) Encoder 3 DRIVE-CLIQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. The nodes do not send and receive in synchronism. Remedy:
|
F33836 (N, A) Encoder 3 DRIVE-CLIQ: Send error for DRIVE-CLIQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Data were not able to be sent. Remedy:
|
F33837 (N, A) Encoder 3 DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLIQ component concerned. Faulty hardware cannot be excluded. Remedy:
|
A33840 Encoder 3 DRIVE-CLIQ: error below the signaling threshold | Cause: A DRIVE-CLIQ error has occurred below the signaling threshold. Remedy:
|
F33845 (N, A) Encoder 3 DRIVE-CLIQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Remedy:
|
F33850 (N, A) Encoder 3: Encoder evaluation internal software error | Cause: An internal software error has occurred in the Sensor Module of encoder 3. Remedy:
|
F33851 (N, A) Encoder 3 DRIVE-CLIQ (CU): Sign-of-life missing | Cause: A DRIVE-CLIQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit. The DRIVE-CLIQ component did not set the sign-of-life to the Control Unit. Remedy:
|
F33860 (N, A) Encoder 3 DRIVE-CLIQ (CU): Telegram error | Cause: A DRIVE-CLIQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit. Remedy:
|
F33875 (N, A) Encoder 3 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. Remedy:
|
F33885 (N, A) Encoder 3 DRIVE-CLIQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLIQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit. The nodes do not send and receive in synchronism. Remedy:
|
F33886 (N, A) Encoder 3 DRIVE-CLIQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLIQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit. Data were not able to be sent. Remedy:
|
F33887 (N, A) Encoder 3 DRIVE-CLIQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLIQ component involved (Sensor Module for encoder 3). Faulty hardware cannot be excluded. Remedy:
|
F33895 (N, A) Encoder 3 DRIVE-CLIQ (CU): Alternating cyclic data transfer error | Cause: A DRIVE-CLIQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit. Remedy:
|
F33896 (N, A) Encoder 3 DRIVE-CLIQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLIQ component (Sensor Module for encoder 3), 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:
|
F33899 (N, A) Encoder 3: Unknown fault | Cause: A fault occurred on the Sensor Module for encoder 3 that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Remedy:
|
A33902 (F, N) Encoder 3: SPI-BUS error occurred | Cause: Error when operating the internal SPI bus. Remedy:
|
A33903 (F, N) Encoder 3: I2C-BUS error occurred | Cause: Error when operating the internal I2C bus. Remedy:
|
F33905 (N, A) Encoder 3: Parameterization error | Cause: A parameter of encoder 3 was detected as being incorrect. It is possible that the parameterized encoder type does not match the connected encoder. Remedy:
|
F33912 Encoder 3: Device combination is not permissible | Cause: The selected device combination is not supported. Remedy:
|
A33915 (F, N) Encoder 3: Configuration error | Cause: The configuration for encoder 3 is incorrect. Remedy:
|
F33916 (N, A) Encoder 3: Parameterization fault | Cause: A parameter of encoder 3 was detected as being incorrect. It is possible that the parameterized encoder type does not match the connected encoder. Remedy:
|
A33920 (F, N) Encoder 3: Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred. Remedy:
|
A33930 (N) Encoder 3: Data logger has saved data | Cause: For the activated function “Data logger” (p0437.0 = 1) a fault has occurred with the Sensor Module. This alarm indicates that the diagnostics data corresponding to the fault was saved on the memory card. Remedy: Not necessary. The alarm disappears automatically. The data logger is ready to record the next fault case. |
A33940 (F, N) Encoder 3: Spindle sensor S1 voltage incorrect | Cause: The voltage of analog sensor S1 is outside the permissible range. Remedy:
|
F33950 Encoder 3: Internal software error | Cause: An internal software error has occurred. Remedy:
|
A33999 (F, N) Encoder 3: Unknown alarm | Cause: An alarm has occurred on the Sensor Module for encoder 3 that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Remedy:
|
F34207 (N, A) VSM: Temperature fault threshold exceeded | Cause: The temperature (r3666) measured using the Voltage Sensing Module (VSM) has exceeded the threshold value (p3668). Remedy:
|
A34211 (F, N) VSM: Temperature alarm threshold exceeded | Cause: The temperature (r3666) measured using the Voltage Sensing Module (VSM) has exceeded the threshold value (p3667). Remedy:
|
N34800 (F) VSM: Group signal | Cause: The Voltage Sensing Module (VSM) has detected at least one fault. Remedy:
|
F34801 VSM DRIVE-CLiQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module (VSM). Remedy:
|
F34805 VSM: EEPROM checksum error | Cause: Internal parameter data is corrupted. Remedy:
|
F34806 VSM: Initialization | Cause: For the Voltage Sensing Module (VSM), a fault has occurred while initializing. Remedy:
|
A34807 (F, N) VSM: Sequence control time monitoring | Cause: Error, timeout in the sequence control on the Voltage Sensing Module (VSM). Remedy:
|
F34820 VSM DRIVE-CLiQ: Telegram error | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module involved. Remedy:
|
F34835 VSM DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module involved. The nodes do not send and receive in synchronism. Remedy:
|
F34836 VSM DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module. Data were not able to be sent. Remedy:
|
F34837 VSM DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. Remedy:
|
A34840 VSM DRIVE-CLiQ: error below the signaling threshold | Cause: A DRIVE-CLiQ error has occurred below the signaling threshold. Remedy:
|
F34845 VSM DRIVE-CLIQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module (VSM). Remedy:
|
F34850 VSM: Internal software error | Cause: An internal software error in the Voltage Sensing Module (VSM) has occurred. Remedy:
|
F34851 VSM DRIVE-CLIQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit. The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit. Remedy:
|
F34860 VSM DRIVE-CLiQ (CU): Telegram error | Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit. Remedy:
|
F34875 VSM 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. Remedy:
|
F34885 VSM DRIVE-CLIQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit. The nodes do not send and receive in synchronism. Remedy:
|
F34886 VSM DRIVE-CLIQ (CU): Error when sending DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit. Data were not able to be sent. Remedy:
|
F34887 VSM DRIVE-CLiQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLiQ component (Voltage Sensing Module) 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 from the Voltage Sensing Module involved (VSM) to the Control Unit. Remedy:
|
F34896 VSM DRIVE-CLiQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (Voltage Sensing Module), specified by the fault value, have changed in an incompatible fashion with respect to the properties when booted. One cause can be, e.g. that a DRIVE-CLiQ cable or DRIVE-CLiQ component has been replaced. Remedy:
|
F34899 (N, A) VSM: Unknown fault | Cause: A fault occurred on the Voltage Sensing Module that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Remedy:
|
A34903 (F, N) VSM: I2C bus error occurred | Cause: An error has occurred when accessing the module-internal I2C bus. Remedy:
|
A34904 (F, N) VSM: EEPROM | Cause: An error has occurred accessing the non-volatile memory on the Terminal Module. Remedy:
|
A34905 (F, N) VSM: Parameter access | Cause: The Control Unit attempted to write an illegal parameter value to the Voltage Sensing Module (VSM). Remedy:
|
F34920 (N, A) VSM: Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred. Remedy:
|
F34950 VSM: Internal software error | Cause: An internal software error in the Voltage Sensing Module (VSM) has occurred. Remedy:
|
A34999 (F, N) VSM: Unknown alarm | Cause: A fault occurred on the Voltage Sensing Module (VSM) an alarm has occurred that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Remedy:
|
F35000 TM54F: Sampling time invalid | Cause: The set sampling time is invalid. Remedy:
|
F35001 TM54F: Parameter value invalid | Cause: The functionality of the basic functions via TM54F is used. TM54F has been incorrectly parameterized (incorrect parameter assignment). Remedy:
|
F35002 TM54F: Commissioning not possible | Cause: The commissioning mode activation was rejected because at least one drive belonging to the TM54F is enabled for operation. Remedy:
|
F35003 TM54F: Acknowledgement on the Control Unit is required | Cause: A fault on the Terminal Module 54F (TM54) was acknowledged using the safe acknowledgement (p10006). An additional acknowledgement is also required at the Control Unit. Remedy:
|
F35004 TM54F: communication cycle invalid | Cause: The communication cycle specified in p10000[x] does not correspond with the monitoring cycle of the drive object which was specified in p10010[x]. Remedy:
|
F35005 TM54F:parallel connection not supported | Cause: The TM54F function with Basic Safety Functions is used. This function is not supported when power units are connected in parallel. Remedy:
|
F35006 TM54F: drive groups invalid | Cause: The functionality of the basic functions via TM54F is used. Drive groups have been incorrectly parameterized (incorrect parameter assignment). Remedy:
|
F35009 TM54F: Safety commissioning drive incomplete | Cause: In the configuration of the TM54F, a drive object of the TM54F was assigned, that has no safety functions or has incorrectly parameterized safety functions. Remedy:
|
F35011 TM54F: Drive object number assignment illegal | Cause: A drive object number was assigned twice. Each drive object number can be assigned only once. Remedy:
|
A35012 TM54F: Test stop active | Cause: The test stop for the Terminal Module 54F (TM54F) is presently being executed. Remedy: The alarm disappears automatically after successfully ending or canceling (when a fault condition occurs) the test stop. |
F35013 TM54F: Test stop error | Cause: An error was detected when carrying out the test stop on the TM54F. Failsafe control signals (failsafe values) are transferred to the safety functions. Remedy:
|
A35014 TM54F: Test stop required | Cause: After powering up the drive, a test stop has still not been carried out. A new test stop is required after commissioning. The time to carry out the forced checking procedure (test stop) has expired (p10003). Remedy:
|
A35015 TM54F: Motor/Hydraulic Module replaced or configuration inconsistent | Cause: Cyclic communication of at least one drive with the Terminal Module 54F (TM54F) is not active. Remedy:
|
A35016 TM54F: Net data communication with drive not established | Cause: The cyclic net data communication within the Terminal Module 54F (TM54F) is still not active for at least one drive. Remedy:
|
F35040 TM54F: 24 V undervoltage | Cause: For the 24 V power supply for the Terminal Module 54F (TM54F) an undervoltage condition was detected. Remedy:
|
F35043 TM54F: 24 V overvoltage | Cause: For the 24 V power supply for the Terminal Module 54F (TM54F) an overvoltage condition was detected. Remedy:
|
F35051 TM54F: Defect in a monitoring channel | Cause: The Terminal Module 54F (TM54F) has identified an error in the crosswise data comparison between the two control channels. Remedy:
|
F35052 (A) TM54F: Internal hardware error | Cause: An internal software/hardware error has been detected on the Terminal Module 54F (TM54F). Remedy:
|
F35053 TM54F: Temperature fault threshold exceeded | Cause: The temperature measured using the temperature sensing on the TM54F has exceeded the threshold value to initiate this fault. Remedy:
|
A35054 TM54F: Temperature alarm threshold exceeded | Cause: The temperature measured using the temperature sensing on the TM54F has exceeded the threshold value to initiate this alarm. Remedy:
|
A35075 (F) TM54F: Error during internal communication | Cause: An internal communications error has occurred in the Terminal Module 54F (TM54F). Remedy:
|
A35080 (F) TM54F: Checksum error safety parameters | Cause: The calculated checksum entered in r10004 over the safety-relevant parameters does not match the reference checksum saved in p10005 at the last machine acceptance. Remedy:
|
A35081 (F) TM54F: Static (steady state) 1 signal at the F-DI for safe acknowledgment | Cause: A logical 1 signal is present at the F-DI configured in p10006 for more than 10 seconds. Remedy:
|
F35150 TM54F: Communication error | Cause: A communication error between the TM54F master and Control Unit or between the TM54F slave and the Motor Module/Hydraulic Module was detected. Remedy:
|
F35151 TM54F: Discrepancy error | Cause: The safety input terminals or output terminals show a different state longer than that parameterized in p10002. Remedy:
|
F35152 TM54F: Internal software error | Cause: An internal software error has occurred in the Terminal Module 54F (TM54F). The fail-safe digital inputs and digital outputs (F-DI, F-DO) on the TM54F have been set to the safe state. Remedy:
|
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: For the temperature evaluation via the Terminal Module (TM), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[0], p4103[0]), or fault threshold exceeded (p4102[1]). Remedy:
|
F35208 (N, A) TM: Temperature fault/alarm threshold channel 1 exceeded | Cause: For the temperature evaluation via the Terminal Module (TM), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[2], p4103[1]), or fault threshold exceeded (p4102[3]). Remedy:
|
F35209 (N, A) TM: Temperature fault/alarm threshold channel 2 exceeded | Cause: For the temperature evaluation via the Terminal Module (TM), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[4], p4103[2]), or fault threshold exceeded (p4102[5]). Remedy:
|
F35210 (N, A) TM: Temperature fault/alarm threshold channel 3 exceeded | Cause: For the temperature evaluation via the Terminal Module (TM), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[6], p4103[3]), or fault threshold exceeded (p4102[7]). Remedy:
|
A35211 (F, N) TM: Temperature alarm threshold channel 0 exceeded | Cause: The temperature measured using the temperature sensing of the Terminal Module (TM) (r4105[0]) has exceeded the threshold value to initiate this alarm (p4102[0]). Remedy:
|
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. 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. Remedy:
|
A35223 (F, N) TM: Zero mark offset not permissible | Cause: The entered zero mark offset is not permissible. Remedy:
|
A35224 (N) TM: Zero mark synchronization interrupted | Cause: The zero mark synchronization with the encoder to be emulated was interrupted. Remedy: Not necessary. |
A35225 TM: Zero mark synchronization held – encoder not in the ready state | Cause: The zero mark synchronization with the encoder to be emulated was held. The encoder is not in the “ready” state. Remedy:
|
A35226 TM: Tracks A/B are de-activated | Cause: There is no frequency setpoint for the Terminal Module 41 (TM41). The output of tracks A/B has been held (frozen). Remedy:
|
A35227 EDS changeover/encoder data set change not supported | Cause: Terminal Module 41 (TM41) does not support the following application cases: the encoder interconnected via connector input p4420 has carried out an EDS changeover, the encoder interconnected with the TM41 was re-parameterized so that the position actual value of the encoder must be newly interpreted. Remedy:
|
A35228 (F, N) TM: Sampling time p4099[3] invalid | Cause: The sampling time set in p4099[3] for incremental encoder emulation in Terminal Module 41 (TM41) does not correspond to the valid value. Remedy:
|
F35229 TM: Time slice de-activated | Cause: The required value of a cycle time in p4099[0…2] is invalid. The corresponding time slice was not activated. 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:
|
A35231 TM: Master control by PLC missing | Cause: The “master control by PLC” signal was missing in operation. Remedy:
|
A35232 TM41: Zero mark no longer synchronous POWER ON required | Cause: When parameterizing a Terminal Module 41 (TM41) or when operating a TM41 Module, an operating state was reached which required a POWER ON. Remedy:
|
F35233 DRIVE-CLIQ component function not supported | Cause: A function requested by the Control Unit is not supported by a DRIVE-CLIQ component. Remedy:
|
F35400 (N, A) TM: Temperature fault/alarm threshold channel 4 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[8], p4103[4]), or fault threshold exceeded (p4102[9]). Remedy:
|
F35401 (N, A) TM: Temperature fault/alarm threshold channel 5 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[10], p4103[5]), or fault threshold exceeded (p4102[11]). Remedy:
|
F35402 (N, A) TM: Temperature fault/alarm threshold channel 6 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[12], p4103[6]), or fault threshold exceeded (p4102[13]). Remedy:
|
F35403 (N, A) TM: Temperature fault/alarm threshold channel 7 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[14], p4103[7]), or fault threshold exceeded (p4102[15]). Remedy:
|
F35404 (N, A) TM: Temperature fault/alarm threshold channel 8 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[16], p4103[8]), or fault threshold exceeded (p4102[17]). Remedy:
|
F35405 (N, A) TM: Temperature fault/alarm threshold channel 9 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[18], p4103[9]), or fault threshold exceeded (p4102[19]). Remedy:
|
F35406 (N, A) TM: Temperature fault/alarm threshold channel 10 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[20], p4103[10]), or fault threshold exceeded (p4102[21]). Remedy:
|
F35407 (N, A) TM: Temperature fault/alarm threshold channel 11 exceeded | Cause: For the temperature evaluation via the Terminal Module 150 (TM150), at least one of the following conditions to initiate this fault is fulfilled: alarm threshold has been exceeded longer than that set in the timer (p4102[22], p4103[11]), or fault threshold exceeded (p4102[23]). Remedy:
|
A35410 (F, N) TM: Temperature alarm threshold channel 4 exceeded | Cause: The temperature (r4105[4]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[8]). Remedy:
|
A35411 (F, N) TM: Temperature alarm threshold channel 5 exceeded | Cause: The temperature (r4105[5]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[10]). Note: For sensor type “PTC thermistor” and “Bimetallic NC contact” (p4100[5] = 1, 4), the following applies: – if r4101[5] > 1650 ohms, the temperature r4105[5] = 250 °C – if r4101[5] <= 1650 ohms, the temperature r4105[5] = -50 °C Alarm value (r2124, interpret decimal): Temperature actual value at the time of initiation [0.1 °C]. Remedy: Allow the temperature sensor to cool down to below p4102[10] – hysteresis (p4118[5]). See also: p4102 |
A35412 (F, N) TM: Temperature alarm threshold channel 6 exceeded | Cause: The temperature (r4105[6]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[12]). Note: For sensor type “PTC thermistor” and “Bimetallic NC contact” (p4100[6] = 1, 4), the following applies: – if r4101[6] > 1650 ohms, the temperature r4105[6] = 250 °C – if r4101[6] <= 1650 ohms, the temperature r4105[6] = -50 °C Alarm value (r2124, interpret decimal): Temperature actual value at the time of initiation [0.1 °C]. Remedy: Allow the temperature sensor to cool down to below p4102[12] – hysteresis (p4118[6]). See also: p4102 |
A35413 (F, N) TM: Temperature alarm threshold channel 7 exceeded | Cause: The temperature (r4105[7]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[14]). Note: For sensor type “PTC thermistor” and “Bimetallic NC contact” (p4100[7] = 1, 4), the following applies: – if r4101[7] > 1650 ohms, the temperature r4105[7] = 250 °C – if r4101[7] <= 1650 ohms, the temperature r4105[7] = -50 °C Alarm value (r2124, interpret decimal): Temperature actual value at the time of initiation [0.1 °C]. Remedy: Allow the temperature sensor to cool down to below p4102[14] – hysteresis (p4118[7]). See also: p4102 |
A35414 (F, N) TM: Temperature alarm threshold channel 8 exceeded | Cause: The temperature (r4105[8]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[16]). Note: For sensor type “PTC thermistor” and “Bimetallic NC contact” (p4100[8] = 1, 4), the following applies: – if r4101[8] > 1650 ohms, the temperature r4105[8] = 250 °C – if r4101[8] <= 1650 ohms, the temperature r4105[8] = -50 °C Alarm value (r2124, interpret decimal): Temperature actual value at the time of initiation [0.1 °C]. Remedy: Allow the temperature sensor to cool down to below p4102[16] – hysteresis (p4118[8]). See also: p4102 |
A35415 (F, N) TM: Temperature alarm threshold channel 9 exceeded | Cause: The temperature (r4105[9]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[18]). Note: For sensor type “PTC thermistor” and “Bimetallic NC contact” (p4100[9] = 1, 4), the following applies: – if r4101[9] > 1650 ohms, the temperature r4105[9] = 250 °C – if r4101[9] <= 1650 ohms, the temperature r4105[9] = -50 °C Alarm value (r2124, interpret decimal): Temperature actual value at the time of initiation [0.1 °C]. Remedy: Allow the temperature sensor to cool down to below p4102[18] – hysteresis (p4118[9]). See also: p4102 |
A35416 (F, N) TM: Temperature alarm threshold channel 10 exceeded | Cause: The temperature (r4105[10]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[20]). Note: For sensor type “PTC thermistor” and “Bimetallic NC contact” (p4100[10] = 1, 4), the following applies: – if r4101[10] > 1650 ohms, the temperature r4105[10] = 250 °C – if r4101[10] <= 1650 ohms, the temperature r4105[10] = -50 °C Alarm value (r2124, interpret decimal): Temperature actual value at the time of initiation [0.1 °C]. Remedy: Allow the temperature sensor to cool down to below p4102[20] – hysteresis (p4118[10]). See also: p4102 |
A35417 (F, N) TM: Temperature alarm threshold channel 11 exceeded | Cause: The temperature (r4105[11]) measured using the temperature sensing of the Terminal Module 150 (TM150) has exceeded the threshold value to initiate this alarm (p4102[22]). Note: For sensor type “PTC thermistor” and “Bimetallic NC contact” (p4100[11] = 1, 4), the following applies: – if r4101[11] > 1650 ohms, the temperature r4105[11] = 250 °C – if r4101[11] <= 1650 ohms, the temperature r4105[11] = -50 °C Alarm value (r2124, interpret decimal): Temperature actual value at the time of initiation [0.1 °C]. Remedy: Allow the temperature sensor to cool down to below p4102[22] – hysteresis (p4118[11]). See also: p4102 |
N35800 (F) TM: Group signal | Cause: The Terminal Module has detected at least one fault. Remedy: Evaluates other actual messages. |
A35801 (F, N) TM DRIVE-CLiQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred between the Control Unit and the Terminal Module involved. Fault cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
A35802 (F, N) TM: Time slice overflow | Cause: A time slice overflow has occurred on the Terminal Module. Remedy: Replace the Terminal Module. |
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. Fault value (r0949, interpret hexadecimal): Difference between the checksum at POWER ON and the actual checksum. Remedy:
|
A35805 (F, N) TM: EEPROM checksum error | Cause: Internal parameter data is corrupted. Alarm value (r2124, interpret hexadecimal): 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy:
|
A35807 (F, N) TM: Sequence control time monitoring | Cause: Error, timeout, sequence control on the Terminal Module. Remedy: Replace the Terminal Module. |
F35820 TM DRIVE-CLiQ: Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the Terminal Module involved. Fault cause: 1 (= 01 hex): Checksum error (CRC error). 2 (= 02 hex): Telegram is shorter than specified in the length byte or in the receive list. 3 (= 03 hex): Telegram is longer than specified in the length byte or in the receive list. 4 (= 04 hex): The length of the receive telegram does not match the receive list. 5 (= 05 hex): The type of the receive telegram does not match the receive list. 6 (= 06 hex): The address of the component in the telegram and in the receive list do not match. 7 (= 07 hex): A SYNC telegram is expected – but the received telegram is not a SYNC telegram. 8 (= 08 hex): No SYNC telegram is expected – but the received telegram is one. 9 (= 09 hex): The error bit in the receive telegram is set. 16 (= 10 hex): The receive telegram is too early. Remedy:
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
F35835 TM DRIVE-CLiQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the Terminal Module involved. The nodes do not send and receive in synchronism. Fault cause: 33 (= 21 hex): The cyclic telegram has not been received. 34 (= 22 hex): Timeout in the telegram receive list. 64 (= 40 hex): Timeout in the telegram send list. Remedy:
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
F35836 TM DRIVE-CLiQ: Send error for DRIVE-CLiQ data | Cause: A DRIVE-CLiQ communication error has occurred between the Control Unit and the Terminal Module involved. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy: Carry out a POWER ON. |
F35837 PTM DRIVE-CLiQ: Component fault | Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. Fault cause: 32 (= 20 hex): Error in the telegram header. 35 (= 23 hex): Receive error: The telegram buffer memory contains an error. 66 (= 42 hex): Send error: The telegram buffer memory contains an error. 67 (= 43 hex): Send error: The telegram buffer memory contains an error. Remedy:
|
A35840 TM DRIVE-CLiQ: error below the signaling threshold | Cause: A DRIVE-CLiQ error has occurred below the signaling threshold. 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. 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. 16 (= 10 hex): The receive telegram is too early. 32 (= 20 hex): Error in the telegram header. 33 (= 21 hex): The cyclic telegram has not been received. 34 (= 22 hex): Timeout in the telegram receive list. 35 (= 23 hex): Receive error: The telegram buffer memory contains an error. 64 (= 40 hex): Timeout in the telegram send list. 65 (= 41 hex): Telegram type does not match send list. 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:
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
F35845 TM DRIVE-CLIQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred between the Control Unit and the Terminal Module (TM) involved. Fault cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
F35850 TM: Internal software error | Cause: An internal software error in the Terminal Module (TM) has occurred. Fault value (r0949, interpret decimal): 1: Background time slice is blocked. 2: Checksum over the code memory is not OK. Remedy:
|
F35851 TM DRIVE-CLIQ (CU): Sign-of-life missing | Cause: A DRIVE-CLiQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit. The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit. Fault cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy: Upgrade the firmware of the component involved. |
F35860 TM DRIVE-CLIQ (CU): Telegram error | Cause: A DRIVE-CLiQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit. Fault cause: 1 (= 01 hex): Checksum error (CRC error). 2 (= 02 hex): Telegram is shorter than specified in the length byte or in the receive list. 3 (= 03 hex): Telegram is longer than specified in the length byte or in the receive list. 4 (= 04 hex): The length of the receive telegram does not match the receive list. 5 (= 05 hex): The type of the receive telegram does not match the receive list. 6 (= 06 hex): The address of the power unit in the telegram and in the receive list do not match. 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 that specified in the length byte or in the receive list and the receive telegram is too early. 19 (= 13 hex): The telegram is longer than that specified in the length byte or in the receive list and the receive telegram is too early. 20 (= 14 hex): The length of the receive telegram does not match the receive list and the receive telegram is too early. 21 (= 15 hex): The type of the receive telegram does not match the receive list and the receive telegram is too early. 22 (= 16 hex): The address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early. 25 (= 19 hex): The error bit in the receive telegram is set and the receive telegram is too early. Remedy:
See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master) |
F35875 TM 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. Remedy:
|
F35885 TM DRIVE-CLIQ (CU): Cyclic data transfer error | Cause: A DRIVE-CLiQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit. The nodes do not send and receive in synchronism. Fault cause: 26 (= 1A hex): Sign-of-life bit in the receive telegram not set and the receive telegram is too early. 33 (= 21 hex): The cyclic telegram has not been received. 34 (= 22 hex): Timeout in the telegram receive list. 64 (= 40 hex): Timeout in the telegram send list. 98 (= 62 hex): Error at the transition to cyclic operation. Remedy:
See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master) |
F35886 TM DRIVE-CLIQ (CU): Error when sending DRIVE-CLIQ data | Cause: A DRIVE-CLiQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy: Carry out a POWER ON. |
F35887 TM DRIVE-CLiQ (CU): Component fault | Cause: Fault detected on the DRIVE-CLiQ component (Terminal Module) involved. Faulty hardware cannot be excluded. Fault cause: 32 (= 20 hex): Error in the telegram header. 35 (= 23 hex): Receive error: The telegram buffer memory contains an error. 66 (= 42 hex): Send error: The telegram buffer memory contains an error. 67 (= 43 hex): Send error: The telegram buffer memory contains an error. 96 (= 60 hex): Response received too late during runtime measurement. 97 (= 61 hex): Time taken to exchange characteristic data too long. 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: Carry out a POWER ON. See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master) |
F35896 TM DRIVE-CLIQ (CU): Inconsistent component properties | Cause: The properties of the DRIVE-CLiQ component (Terminal Module), specified by the fault value, have changed in an incompatible fashion with respect to the properties when booted. One cause can be, e.g. that a DRIVE-CLiQ cable or DRIVE-CLiQ component has been replaced. 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: Replace the Terminal Module. |
A35904 (F, N) TM: EEPROM | Cause: An error has occurred accessing the non-volatile memory on the Terminal Module. Remedy: Replace the Terminal Module. |
A35905 (F, N) TM: Parameter access | Cause: The Control Unit attempted to write an illegal parameter value to the Terminal Module. Remedy:
|
A35906 (F, N) TM: 24 V power supply missing | Cause: The 24 V power supply for the digital outputs is missing. Alarm value (r2124, interpret hexadecimal): 01: TM17 24 V power supply for DI/DO 0 … 7 missing. 02: TM17 24 V power supply for DI/DO 8 … 15 missing. 04: TM15 24 V power supply for DI/DO 0 … 7 (X520) missing. 08: TM15 24 V power supply for DI/DO 8 … 15 (X521) missing. 10: TM15 24 V power supply for DI/DO 16 … 23 (X522) missing. 20: TM41 24 V power supply for DI/DO 0 … 3 missing. Remedy: Check the terminals for the power supply voltage (L1+, L2+, L3+, M or +24 V_1 for TM41). |
A35907 (F, N) TM: Hardware initialization error | Cause: The Terminal Module was not successfully initialized. Alarm value (r2124, interpret hexadecimal): 01: TM17 or TM41 – incorrect configuration request. 02: TM17 or TM41 – programming not successful. 04: TM17 or TM41 – invalid time stamp Remedy: Carry out a POWER ON. |
A35910 (F, N) TM: Module overtemperature | Cause: The temperature in the module has exceeded the highest permissible limit. Remedy:
|
A35911 (F, N) TM: Clock synchronous operation sign-of-life missing | Cause: The maximum permissible number of errors in the master sign-of-life (clock synchronous operation) has been exceeded in cyclic operation. Remedy:
|
A35920 (F, N) TM: Error temperature sensor channel 0 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 1630 Ohm (TM150: R > 2170 Ohm), PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 50 Ohm (TM150: R < 180 Ohm), PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
A35921 (F, N) TM: Error temperature sensor channel 1 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 1630 Ohm (TM150: R > 2170 Ohm), PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 50 Ohm (TM150: R < 180 Ohm), PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
A35922 (F, N) TM: Error temperature sensor channel 2 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 1630 Ohm (TM150: R > 2170 Ohm), PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 50 Ohm (TM150: R < 180 Ohm), PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
A35923 (F, N) TM: Error temperature sensor channel 3 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 1630 Ohm (TM150: R > 2170 Ohm), PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 50 Ohm (TM150: R < 180 Ohm), PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
A35924 (F, N) TM: Error temperature sensor channel 4 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 2170 Ohm, PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 180 Ohm, PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
A35925 (F, N) TM: Error temperature sensor channel 5 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 2170 Ohm, PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 180 Ohm, PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
A35926 (F, N) TM: Error temperature sensor channel 6 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 2170 Ohm, PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 180 Ohm, PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
A35927 (F, N) TM: Error temperature sensor channel 7 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 2170 Ohm, PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 180 Ohm, PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
A35928 (F, N) TM: Error temperature sensor channel 8 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 2170 Ohm, PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 180 Ohm, PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
A35929 (F, N) TM: Error temperature sensor channel 9 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 2170 Ohm, PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 180 Ohm, PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
A35930 (F, N) TM: Error temperature sensor channel 10 | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected. KTY84: R > 2170 Ohm, PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 180 Ohm, PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
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. KTY84: R > 2170 Ohm, PT100: R > 194 Ohm, PT1000: R > 1944 Ohm 2: Measured resistance too low. PTC thermistor: R < 20 Ohm, KTY84: R < 180 Ohm, PT100: R < 60 Ohm, PT1000: R < 603 Ohm Remedy:
|
F35950 TM: Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Information about the fault source. Only for internal Siemens troubleshooting. Remedy:
|
A35999 (F, N) TM: Unknown alarm | Cause: An alarm has occurred on the Terminal Module that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Alarm value (r2124, interpret decimal): Alarm number. Remedy:
|
F36207 (N, A) Hub: Overtemperature component | Cause: The temperature on the DRIVE-CLIQ Hub Module has exceeded the fault threshold. Fault value (r0949, interpret decimal): Actual temperature in 0.1 °C resolution. Remedy:
|
A36211 (F, N) Hub: Overtemperature alarm component | Cause: The temperature on the DRIVE-CLIQ Hub Module has exceeded the alarm threshold. Alarm value (r2124, interpret decimal): Actual temperature in 0.1 °C resolution. Remedy:
|
F36214 (N, A) Hub: overvoltage fault 24 V supply | Cause: The 24 V power supply on the DRIVE-CLIQ Hub Module has exceeded the fault threshold. Fault value (r0949, interpret decimal): Actual operating voltage in 0.1 °C resolution. Remedy:
|
F36216 (N, A) Hub: undervoltage fault 24 V supply | Cause: The 24 V power supply on the DRIVE-CLIQ Hub Module has undershot the fault threshold. Fault value (r0949, interpret decimal): Actual operating voltage in 0.1 °C resolution. Remedy:
|
A36217 (N) Hub: undervoltage alarm 24 V supply | Cause: The 24 V power supply on the DRIVE-CLIQ Hub Module has undershot the alarm threshold. Alarm value (r2124, interpret decimal): Actual operating voltage in 0.1 °C resolution. Remedy:
|
N36800 (F) Hub: Group signal | Cause: The DRIVE-CLIQ Hub Module has detected at least one fault. Remedy: Evaluates other actual messages. |
A36801 (F, N) Hub DRIVE-CLIQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the DRIVE-CLIQ Hub Module involved. Fault cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
F36802 (N, A) Hub: Time slice overflow | Cause: A time slice overflow has occurred on the DRIVE-CLIQ Hub Module. Fault value (r0949, interpret decimal): xx: Time slice number xx Remedy:
|
F36804 (N, A) Hub: Checksum error | Cause: A checksum error has occurred when reading out the program memory on the DRIVE-CLIQ Hub Module. Alarm value (r2124, interpret hexadecimal): Difference between the checksum at POWER ON and the actual checksum. Remedy:
|
A36805 (F, N) Hub: EEPROM checksum incorrect | Cause: The internal parameter data on the DRIVE-CLiQ Hub Module is incorrect. Alarm value (r2124, interpret hexadecimal): 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy:
|
F36820 Hub DRIVE-CLIQ: Telegram error | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the DRIVE-CLIQ Hub Module involved. 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:
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
F36835 Hub DRIVE-CLIQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the DRIVE-CLIQ Hub Module involved. The nodes do not send and receive in synchronism. Fault cause: 33 (= 21 hex): The cyclic telegram has not been received. 34 (= 22 hex): Timeout in the telegram receive list. 64 (= 40 hex): Timeout in the telegram send list. Remedy:
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
F36836 Hub DRIVE-CLIQ: Send error for DRIVE-CLIQ data | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the DRIVE-CLIQ Hub Module involved. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy: Carry out a POWER ON. |
F36837 Hub 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:
|
A36840 Hub DRIVE-CLiQ: error below the signaling threshold | Cause: A DRIVE-CLIQ error has occurred below the signaling threshold. Fault cause: (Multiple causes listed, including…) 1 (= 01 hex): Checksum error (CRC error). 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. 33 (= 21 hex): The cyclic telegram has not been received. 35 (= 23 hex): Receive error: The telegram buffer memory contains an error. 66 (= 42 hex): Send error: The telegram buffer memory contains an error. Remedy:
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
F36845 Hub DRIVE-CLIQ: Cyclic data transfer error | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the DRIVE-CLIQ Hub Module involved. Fault cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
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: Upgrade the firmware of the component involved. |
F36860 Hub DRIVE-CLiQ (CU): Telegram error | Cause: DRIVE-CLIQ communication error from DRIVE-CLIQ Hub Module in question to Control Unit. Fault cause: (Multiple causes listed, including…) 1 (= 01 hex): Checksum error (CRC error). 9 (= 09 hex): The error bit in the receive telegram is set. 16 (= 10 hex): The receive telegram is too early. 18 (= 12 hex): The telegram is shorter than specified in the length byte or in the receive list and the receive telegram is too early. 25 (= 19 hex): The error bit in the receive telegram is set and the receive telegram is too early. Remedy:
|
F36875 HUB 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. 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: Carry out a POWER ON. |
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: Carry out a POWER ON. See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master) |
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:
|
F36899 (N, A) Hub: Unknown fault | Cause: A fault occurred on the DRIVE-CLIQ Hub 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:
|
F36950 Hub: Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Information about the fault source. Only for internal Siemens troubleshooting. Remedy:
|
A36999 (F, N) Hub: Unknown alarm | Cause: An alarm occurred on the DRIVE-CLIQ Hub 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:
|
F37001 HF damping module: overcurrent | Cause: The power unit has detected an overcurrent condition.
Remedy:
|
F37002 HF damping module: Damping voltage too high | Cause: The damping voltage has reached an inadmissibly high value.
Remedy:
|
F37003 HF damping module: Damping voltage not established | Cause: A damping voltage was not able to be established. Remedy: Check the HF Damping Module wiring. See also: r5171 (HF damping voltage actual value) |
F37004 HF damping module: Heat sink overtemperature | Cause: The temperature of the heat sink in the HF damping module has exceeded the permissible limit value.
Remedy:
|
F37005 HF damping module: I2t overload | Cause:
Remedy:
|
F37012 HF damping module: Heat sink temperature sensor wire breakage | Cause: The connection to one of the heat sink temperature sensors in the HF Damping Module is interrupted. Remedy: Contact the manufacturer. |
F37013 HF Damping Module: Heat sink temperature sensor short-circuit | Cause: The heat sink temperature sensor in the HF Damping Module is short-circuited. Remedy: Contact the manufacturer. |
F37024 HF Damping Module: Overtemperature thermal model | Cause: The temperature difference between the heat sink and chip has exceeded the permissible limit value.
Remedy:
|
F37025 HF Damping Module: Chip overtemperature | Cause: The chip temperature has exceeded the permissible limit value.
Remedy:
|
A37034 HF Damping Module: Internal overtemperature | Cause: The alarm threshold for internal overtemperature has been reached. If the temperature inside the unit continues to increase, fault F37036 may be triggered.
Remedy:
|
F37036 HF Damping Module: Internal overtemperature | Cause: The temperature inside the HF Damping Module has exceeded the permissible temperature limit.
Remedy:
|
F37040 HF Damping Module: 24 V undervoltage | Cause: Failure of the 24 V power supply for the HF Damping Module. – The undervoltage threshold was undershot for longer than 3 ms. Remedy:
|
A37041 (F) HF Damping Module: 24 V undervoltage alarm | Cause: Fault in the 24 V power supply for the HF Damping Module. – the 16 V threshold was undershot. Remedy:
|
F37043 HF Damping Module: 24 V overvoltage | Cause: Overvoltage of the 24 V power supply for the HF Damping Module. – the 31.5 V threshold was exceeded for more than 3 ms. Remedy: Check the 24 V DC voltage supply of the HF Damping Module. |
A37044 (F) HF Damping Module: 24 V overvoltage alarm | Cause: Fault in the 24 V power supply for the HF Damping Module. – the 32.0 V threshold was exceeded. Remedy: Check the 24 V DC voltage supply of the HF Damping Module. |
F37045 HF Damping Module: Supply undervoltage | Cause: Power supply fault in the HF Damping Module. The voltage monitor signals an undervoltage fault on the module. Remedy:
|
A37049 HF Damping Module: Internal fan defective | Cause: The internal fan of the HF Damping Module has failed. Remedy: Check the internal fan of the HF Damping Module and replace if necessary. |
F37050 HF Damping Module: 24 V overvoltage fault | Cause: The voltage monitor signals an overvoltage fault on the module. Remedy:
|
F37052 HF Damping Module: EEPROM data error | Cause: EEPROM data error of the HF Damping Module. Fault value (r0949, interpret hexadecimal): 0: The EEPROM data read in from the HF Damping Module is inconsistent. 1: EEPROM data is not compatible to the firmware of the HF Damping Module. Remedy: For fault value = 0: Replace the HF Damping Module or update the EEPROM data. For fault value = 1: If necessary, upgrade the firmware to a later version. |
A37056 (F) HF damping module: Heat sink overtemperature | Cause: The temperature of the HF Damping Module heat sink has exceeded the permissible limit value.
Remedy:
|
A37310 (F) HF Choke Module: Overtemperature | Cause: The temperature of the HF Choke Module heat sink has exceeded the permissible limit value.
Remedy:
|
F37311 HF Choke Module: Heat sink overtemperature | Cause: The temperature of the HF Choke Module heat sink has exceeded the permissible limit value.
Remedy:
|
A37312 (F) HF Choke Module: Overtemperature or fan failure | Cause: The HF Choke Module signals an overtemperature or fan failure. Fault F37313 is output if the alarm is present for longer than 30 s. – The cable between the HF Choke Module and the HF Damping Module has been withdrawn or is defective (X21). Remedy:
|
F37313 HF Choke Module: Overtemperature or fan failure | Cause: Alarm A37312 to display overtemperature or fan failure in the HF Choke Module was signaled for longer than 30 s. Remedy:
|
A37502 (F) HF damping module: Damping voltage too high | Cause: The damping voltage has exceeded the alarm threshold.
If the damping voltage exceeds an inadmissibly high value, F37002 is output. Remedy:
|
N37800 (F) HF Damping Module: Group signal | Cause: The HF Damping Module has detected at least one fault. Remedy: Evaluates other actual messages. |
A37801 (F, N) HF Damping Module: Sign-of-life missing | Cause: There is a DRIVE-CLIQ communication error between the Control Unit and the HF Damping Module. Fault cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
F37802 HF damping module: time slice overflow | Cause: A time slice overflow has occurred. Remedy:
|
F37804 (N, A) HF Damping Module: CRC | Cause: A CRC error has occurred for the HF Damping Module. Remedy:
|
F37805 HF Damping Module: EEPROM checksum incorrect | Cause: Internal parameter data is corrupted. Fault value (r0949, interpret hexadecimal): 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy: Replace the module. |
F37820 HF Damping Module: Telegram error | Cause: A DRIVE-CLIQ communication error has occurred from the Control Unit to the damping module. 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:
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
F37835 HF Damping Module: Cyclic data transmission error | Cause: There is a DRIVE-CLIQ communication error between the Control Unit and the HF Damping Module. 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:
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
F37836 HF Damping Module: Send error for DRIVE-CLIQ data | Cause: There is a DRIVE-CLIQ communication error between the Control Unit and the HF Damping Module. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy: Carry out a POWER ON. |
F37837 HF Damping Module: Component faulted | 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:
|
A37840 HF Damping Module DRIVE-CLiQ: error below the signaling threshold | Cause: A DRIVE-CLIQ error has occurred below the signaling threshold. Fault cause: (Multiple causes including CRC error, telegram length mismatch, sync errors, timeouts, and buffer memory errors are listed with corresponding hex codes.) Remedy:
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
F37845 HF Damping Module: Cyclic data transmission error | Cause: There is a DRIVE-CLIQ communication error between the Control Unit and the HF Damping Module. Fault cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON. See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
F37850 HF Damping Module: Internal software error | Cause: An internal software error in the HF Damping Module has occurred. Remedy:
|
F37851 HF Damping Module (CU): Sign-of-life missing | Cause: DRIVE-CLIQ communication error from the HF Damping Module 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: Upgrade the firmware of the component involved. |
F37860 HF Damping Module (CU): Telegram error | Cause: DRIVE-CLIQ communication error from the HF Damping Module to the Control Unit. Fault cause: (Multiple causes including CRC error, telegram length mismatch, and timing issues are listed with corresponding hex codes.) Remedy:
|
F37875 HF Damping Module (CU): Supply voltage has 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:
|
F37885 HF Damping Module (CU): Cyclic data transmission error | Cause: DRIVE-CLIQ communication error from the damping module 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:
|
F37886 HF Damping Module (CU): Error when sending DRIVE-CLIQ data | Cause: DRIVE-CLIQ communication error from the HF Damping Module to the Control Unit. Data were not able to be sent. Fault cause: 65 (= 41 hex): Telegram type does not match send list. Remedy: Carry out a POWER ON. |
F37887 HF Damping Module (CU): Component faulted | Cause: Fault detected on the DRIVE-CLiQ component (HF Damping 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:
|
F37895 HF Damping Module (CU): Alternating cyclic data transmission error | Cause: DRIVE-CLIQ communication error from the HF Damping Module to the Control Unit. Fault cause: 11 (= 0B hex): Synchronization error during alternating cyclic data transfer. Remedy: Carry out a POWER ON. See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master) |
F37896 HF Damping Module (CU): Component properties inconsistent | Cause: The properties of the DRIVE-CLIQ component (HF Damping 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:
|
F37899 (N, A) HF Damping Module: Unknown fault | Cause: A fault has occurred on the HF Damping 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:
|
F37903 HF Damping Module: I2C bus error occurred | Cause: Communications error with an EEPROM or A/D converter. Fault value (r0949, interpret hexadecimal): 80000000 hex: – internal software error. 00000001 hex … 0000FFFF hex: – module fault. Remedy: Re fault value = 80000000 hex: upgrade firmware to later version. Re fault value = 00000001 hex … 0000FFFF hex: – replace the module. |
F37950 HF Damping Module: Internal software error | Cause: An internal software error has occurred. Remedy:
|
A37999 (F, N) HF Damping Module: Unknown alarm | Cause: An alarm has occurred on the HF Damping 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:
|
F40000 Fault at DRIVE-CLIQ socket X100 | Cause: A fault has occurred at the drive object at the DRIVE-CLIQ socket X100. Remedy: Evaluate the fault buffer of the specified object. |
F40001 Fault at DRIVE-CLIQ socket X101 | Cause: A fault has occurred at the drive object at the DRIVE-CLIQ socket X101. Remedy: Evaluate the fault buffer of the specified object. |
F40002 Fault at DRIVE-CLIQ socket X102 | Cause: A fault has occurred at the drive object at the DRIVE-CLIQ socket X102. Remedy: Evaluate the fault buffer of the specified object. |
F40003 Fault at DRIVE-CLIQ socket X103 | Cause: A fault has occurred at the drive object at the DRIVE-CLIQ socket X103. Remedy: Evaluate the fault buffer of the specified object. |
F40004 Fault at DRIVE-CLIQ socket X104 | Cause: A fault has occurred at the drive object at the DRIVE-CLIQ socket X104. Remedy: Evaluate the fault buffer of the specified object. |
F40005 Fault at DRIVE-CLIQ socket X105 | Cause: A fault has occurred at the drive object at the DRIVE-CLIQ socket X105. Remedy: Evaluate the fault buffer of the specified object. |
A40100 Alarm at DRIVE-CLIQ socket X100 | Cause: An alarm has occurred at the drive object at the DRIVE-CLIQ socket X100. Remedy: Evaluate the alarm buffer of the specified object. |
A40101 Alarm at DRIVE-CLIQ socket X101 | Cause: An alarm has occurred at the drive object at the DRIVE-CLIQ socket X101. Remedy: Evaluate the alarm buffer of the specified object. |
A40102 Alarm at DRIVE-CLIQ socket X102 | Cause: An alarm has occurred at the drive object at the DRIVE-CLIQ socket X102. Remedy: Evaluate the alarm buffer of the specified object. |
A40103 Alarm at DRIVE-CLIQ socket X103 | Cause: An alarm has occurred at the drive object at the DRIVE-CLIQ socket X103. Remedy: Evaluate the alarm buffer of the specified object. |
A40104 Alarm at DRIVE-CLIQ socket X104 | Cause: An alarm has occurred at the drive object at the DRIVE-CLIQ socket X104. Remedy: Evaluate the alarm buffer of the specified object. |
A40105 Alarm at DRIVE-CLIQ socket X105 | Cause: An alarm has occurred at the drive object at the DRIVE-CLIQ socket X105. Remedy: Evaluate the alarm buffer of the specified object. |
F40799 CX32: Configured transfer end time exceeded | Cause: The configured transfer end time when transferring the cyclic actual values was exceeded. Remedy:
|
F40801 CX32 DRIVE-CLiQ: Sign-of-life missing | Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the controller extension involved. Fault cause: 10 (= 0A hex): The sign-of-life bit in the receive telegram is not set. Remedy:
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
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: (Multiple causes including CRC error, telegram length mismatch, sync errors, and timing issues are listed with corresponding hex codes.) Remedy:
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
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:
See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
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: Carry out a POWER ON (power off/on). |
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. Remedy: Carry out a POWER ON (power off/on). See also: p9916 (DRIVE-CLiQ data transfer error shutdown threshold slave) |
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. Remedy: Upgrade the firmware of the component involved. |
F40860 CX32 DRIVE-CLiQ (CU): Telegram error | Cause: A DRIVE-CLIQ communications error has occurred from the controller extension involved to the Control Unit. Fault cause: (Multiple causes including CRC error, telegram length mismatch, and timing issues are listed with corresponding hex codes.) Remedy:
See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master) |
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. 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:
See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master) |
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: Carry out a POWER ON (power off/on). |
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: Carry out a POWER ON (power off/on). See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master) |
F49150 Cooling unit: Fault occurred | Cause: The cooling unit signals a general fault. Remedy: – check the wiring between the cooling unit and the input terminal (Terminal Module). – check the external control device for the cooling unit. See also: p0266 (Cooling unit feedback signals signal source) |
F49151 Cooling unit: Conductivity has exceeded the fault threshold | Cause: The conductivity of the cooling liquid has exceeded the selected fault threshold (p0269[2]). Remedy: Check the device to de-ionize the cooling liquid. |
F49152 Cooling unit: ON command feedback signal missing | Cause: The feedback signal of the ON command of the cooling unit is missing. – after the ON command, the feedback signal has not been received within the selected starting time (p0260). – the feedback signal has failed in operation. Remedy: – check the wiring between the cooling unit and the input terminal (Terminal Module). – check the external control device for the cooling unit. |
F49153 Cooling unit: Liquid flow too low | Cause: The drive converter cooling unit signals that the cooling liquid flow is too low. – after the ON command, the feedback signal has not been received within the selected starting time (p0260). – in operation, the feedback signal has failed for longer than the permitted failure time (p0263). Remedy: – check the wiring between the cooling unit and the input terminal (Terminal Module). – check the external control device for the cooling unit. |
F49154 (A) Cooling unit: Liquid leak is present | Cause: The liquid leakage monitoring function has responded. Remedy: – check the cooling system for leaks in the cooling circuit. – check the wiring of the input terminal (Terminal Module) used to monitor leaking fluid. |
F49155 Cooling unit: Power Stack Adapter, firmware version too old | Cause: The firmware version in the Power Stack Adapter (PSA) is too old and does not support the liquid cooling. Remedy: Upgrade the firmware. Check EEPROM data. |
F49156 Cooling unit: Cooling liquid temperature has exceeded the fault threshold | Cause: The cooling liquid intake temperature has exceeded the specified fault threshold. Remedy: Check the cooling system and the ambient conditions. |
A49170 Cooling unit: Alarm has occurred | Cause: The cooling unit signals a general alarm. Remedy: – check the wiring between the cooling unit and the input terminal (Terminal Module). – check the external control device for the cooling unit. |
A49171 Cooling unit: Conductivity has exceeded the alarm threshold | Cause: The conductivity of the cooling liquid has exceeded the selected alarm threshold (p0269[1]). OR Conductivity monitoring is set for the cooling liquid (r0267.7, from p0266[7]). Remedy: Check the device to de-ionize the cooling liquid. |
A49172 Cooling unit: Conductivity actual value is not valid | Cause: When monitoring the conductivity of the cooling liquid, there is a fault in the wiring or in the sensor. Remedy: – check the wiring between the cooling unit and the Power Stack Adapter (PSA). – check the function of the sensor to measure the conductivity. |
A49173 Cooling unit: Cooling liquid temperature has exceeded the alarm threshold | Cause: The cooling liquid intake temperature has exceeded the specified alarm threshold. Remedy: Check the cooling system and the ambient conditions. |
F49200 Excitation group signal fault | Cause: The excitation sequence control signals a fault. Fault value (r0949, interpret hexadecimal): Bit 0: When powered down or when powering down the excitation, the signal “excitation ready feedback signal” was not received within the monitoring time. Bit 1: After an ON command, the signal “excitation ready feedback signal” was not received within the monitoring time. Bit 2: After the pulses were enabled, the signal “excitation operational feedback signal” was not received within the monitoring time. Bit 3: The “excitation group signal fault” signal is present. Bit 4: The switch-on command for the excitation was reset, although pulse enable (r0899.11) is still available, or the excitation current actual value has still not fallen below a minimum value. Remedy: – check the excitation. – check commands, feedback signals and BICO interconnections. – re bit 4: increase the switch-off delay time p1647. |
A49201 (F) Excitation group signal alarm | Cause: The “excitation group signal alarm” signal is present. Remedy: Check the excitation equipment. |
A49204 (N) Excitation switch-off alarm | Cause: When switching off the excitation, after the delay time p1647 has expired, the excitation current has still not decayed to zero. Remedy: Extend the switch-off delay time in p1647. The alarm is reset if p1647 is adapted. |
A49920 (F) Protective breaker main circuit tripped | Cause: The protective breaker in the main circuit of the power supply has tripped. Remedy: Check the main circuit. |
A49921 (F) Protective breaker redundant main circuit tripped | Cause: The protective breaker in the main circuit for the redundant feed to the power supply has tripped. Remedy: Check the redundant main circuit. |
A49922 (F) Protective breaker 24 V circuit has tripped | Cause: A protective breaker in the 24 V circuit has tripped. Remedy: Check the 24 V circuit. |
A49923 (F) Protective breaker terminal strip 24 V circuit has tripped | Cause: A protective breaker for the terminal strip in the 24 V circuit has tripped. Remedy: Check the terminal strip for the 24 V circuit. |
A49924 (F) Protective breaker power unit supply circuit tripped | Cause: A protective breaker in the circuit of the power unit supply has tripped. Remedy: Check the power unit supply circuit. |
A49926 (F) Protective breaker synchronizing voltage tripped | Cause: A protective breaker for the synchronizing voltage has tripped. Remedy: Check the synchronizing voltage. |
A49927 (F) Protective breaker auxiliary fan circuit has tripped | Cause: The protective breaker in the fan circuit of the auxiliary fan has tripped. Remedy: Check the auxiliary fan. |
A49933 (F) Protective breaker excitation 230 V AC circuit tripped | Cause: The protective breaker in the 230 V AC circuit of the excitation has tripped. Remedy: Check the 230 V AC circuit of the excitation. |
A49934 (F) Protective breaker output cooling unit 230 V AC circuit tripped | Cause: The protective breaker in the 230 V AC circuit of the outgoing feeder of the cooling unit has tripped. Remedy: Check the 230 V AC circuit of the outgoing feeder of the cooling unit. |
A49935 (F) Protective breaker power unit door solenoids 24 V circuit has tripped | Cause: The protective breaker in the 24 V circuit of the door solenoids in the power unit has tripped. Remedy: Check the 24 V circuit of the door solenoids in the power unit. |
A49936 Prot. breaker lighting supply/socket outlets 230V AC cct has tripped | Cause: The protective breaker in the 230 V AC circuit for the lighting supply/socket outlets has tripped. Remedy: Check the 230V AC circuit for the lighting supply/socket outlets. |
A49937 (F) UPS not ready | Cause: The UPS is not ready. Remedy: Check the UPS. |
A49938 (F) UPS battery operation | Cause: The UPS is in battery operation. Remedy: Check the power supply of the control cabinet. |
A49939 (F) UPS battery discharged | Cause: The UPS battery is discharged. Remedy: Check the UPS battery. |
A49998 Recorder trigger event occurred | Cause: A recorder trigger event has occurred. The data are then written to the memory card, specifying the event number. Remedy: Not necessary. This message disappears automatically. |
A50001 (F) PN/COMM BOARD: Configuration error | Cause: A PROFINET controller attempts to establish a connection using an incorrect configuring telegram. The “Shared Device” function has been activated (p8829 = 2). Alarm values indicate issues like receiving a PROFIsafe telegram when not expected, incorrect PZD telegrams, or mismatches in PROFIsafe subslots. Remedy: Check the configuration of the PROFINET controllers as well as the p8829 and p9601.3 setting. |
A50002 (F) COMM BOARD: Alarm 2 | Cause: CBE20 SINAMICS Link: A specific telegram word (send) is being used twice. Remedy: Correct the parameter assignment. See also: p8871 (SINAMICS Link send telegram word PZD). |
A50003 (F) COMM BOARD: Alarm 3 | Cause: CBE20 SINAMICS Link: A specific telegram word (receive) is being used twice. Remedy: Correct the parameter assignment. |
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. – drive object number p8872 > 16 with p8811 = 16. Remedy: In the case of CBE20 SINAMICS Link: Correct the parameter assignment. |
A50005 (F) COMM BOARD: Alarm 5 | Cause: CBE20 SINAMICS Link: Sender not found on SINAMICS Link. Remedy: Check the connection to the sender. |
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. Remedy: In the case of CBE20 SINAMICS Link: Correct the parameter assignment. All p8872[index] must be set to a value not equal to p8836. |
A50010 (F) PN/COMM BOARD: Station name invalid | Cause: CBE20: PROFINET Name of Station is invalid. Remedy: Correct the name of the station (p8940) and activate (p8945 = 2). |
A50020 (F) PNCOMM BOARD: Second controller missing | Cause: CBE20: The PROFINET function “Shared Device” has been activated (p8829 = 2). However, only the connection to a PROFINET controller is present. Remedy: Check the configuration of the PROFINET controllers as well as the p8829 setting. |