Siemens G120X Drive Fault Codes:
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| F01000 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01001 FloatingPoint exception | Cause: An exception occurred for an operation with the FloatingPoint data type. The error 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 FloatingPoint 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 Acknowledgment delay when accessing the memory | Cause: A memory area was accessed that does not return a “READY”. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| N01004 (F, A) Internal software error | Cause: An internal software error has occurred. Fault value (r0949, hexadecimal): Only for internal Siemens troubleshooting. Remedy:
See also: r9999 (Software error internal supplementary diagnostics) |
| F01005 File upload/download error | Cause: The upload or download of EEPROM data was unsuccessful. Fault value (r0949, interpret hexadecimal): yyxxxx hex: yy = component number, xxxx = fault cause xxxx = 000B hex = 11 dec: Power unit component has detected a checksum error. xxxx = 000F hex = 15 dec: The selected power unit will not accept the content of the EEPROM file. xxxx = 0011 hex = 17 dec: Power unit component has detected an internal access error. xxxx = 0012 hex = 18 dec: After several communication attempts, no response from the power unit component. xxxx = 008B hex = 140 dec: EEPROM file for the power unit component not available on the memory card. xxxx = 008D hex = 141 dec: An inconsistent length of the firmware file was signaled. It is possible that the download/upload has been interrupted. xxxx = 0090 hex = 144 dec: When checking the file that was loaded, the component detected a fault (checksum). It is possible that the file on the memory card is defective. xxxx = 0092 hex = 146 dec: This SW or HW does not support the selected function. xxxx = 009C hex = 156 dec: Component with the specified component number is not available (p7828). xxxx = Additional values: Only for internal Siemens troubleshooting. Remedy: Save a suitable firmware file or EEPROM file for upload or download in folder “/ee_sac/” on the memory card. |
| 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 is automatically withdrawn once the limit value has been fallen below. |
| F01010 Drive type unknown | Cause: An unknown drive type was found. Remedy:
|
| F01015 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01016 (F) Firmware changed | Cause: At least one firmware file in the directory was illegally changed on the non-volatile memory (memory card/device memory) with respect to the version when shipped from the factory. Alarm value (r2124, interpret decimal): 0: Checksum of one file is incorrect. 1: File missing. 2: 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. |
| 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 Remedy: For the file on the memory card involved, restore the status originally supplied from the factory. |
| F01018 Booting has been interrupted several times | Cause: Module booting was interrupted several times. As a consequence, the module boots with the factory setting. Possible reasons for booting being interrupted: – Power supply interrupted. – CPU crashed. – Parameterization invalid. Remedy:
Examples: a) Carry out a first commissioning, save, carry out a POWER ON (switch-off/switch-on). b) Load another valid parameter backup (e.g. from the memory card), save, carry out a POWER ON (switch-off/switch-on). Note: If the fault situation is repeated, then this fault is again output after several interrupted boots. |
| A01019 Writing to the removable data medium unsuccessful | Cause: The write access to the removable data medium was unsuccessful. Remedy:
|
| A01020 Writing to RAM disk unsuccessful | Cause: A write access to the internal RAM disk was unsuccessful. Remedy: Adapt the file size for the system logbook to the internal RAM disk (p9930). See also: p9930 (System logbook activation) |
| A01021 Removable data medium as USB data storage medium from the PC used | Cause: The removable data medium is used as USB data storage medium from a PC. As a consequence, the drive cannot access the removable data medium. When backing up, the configuration data cannot be saved on the removable data medium. Alarm value (r2124, interpret decimal): 1: The know-how protection as well as the copy protection for the removable data medium is active. Backup is inhibited. 2: The configuration data are only backed up in the Control Unit. Remedy: Deactivate the USB connection to the PC and back up the configuration data. Note: The alarm is automatically canceled when disconnecting the USB connection or when removing the removable data medium. |
| F01023 Software timeout (internal) | Cause: An internal software timeout has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01028 (F) Configuration error | Cause: The parameterization that was downloaded was generated with a different module type (Order No., MLFB). Remedy: Save parameters in a non-volatile fashion (p0971 = 1). |
| 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: Drive -> Commissioning -> Control panel -> Button “Fetch master control” -> A window is displayed to set the monitoring time in milliseconds. Notice: The monitoring time should be set as short as possible. A long monitoring time means a late response when the communication fails! |
| 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: p0505, p0595 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:
|
| 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 internal backup data record was loaded. The parameterization must be checked. It is recommended that the parameterization is downloaded again. aa = 03 hex: The last available data record from the memory card was loaded. The parameterization must be checked. aa = 04 hex: An invalid data backup was loaded from the memory card into the drive. The drive is in the factory setting. dd, cc, bb: Only for internal Siemens troubleshooting. See also: p0971 (Save parameters) Remedy:
|
| F01036 (A) ACX: Parameter back-up file missing | Cause: When downloading the device parameterization, a parameter back-up file PSxxxyyy.ACX associated with a drive object cannot be found. 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 p0971 = 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:
|
| 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 = 099 –> PROFIBUS parameter back-up file b = xxx in the file names PSxxxyyy.*** b = 000 –> data save started with p0971 = 1 b = 010 –> data save started with p0971 = 10 b = 011 –> data save started with p0971 = 11 b = 012 –> data save started with p0971 = 12 d, c: Only for internal Siemens troubleshooting. Remedy:
|
| F01040 Save parameter settings and carry out a POWER ON | Cause: A parameter has been changed that requires the parameters to be backed up and the Control Unit to be switched OFF and ON again. 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 0: Parameter number illegal. 1: Parameter value cannot be changed. 2: Lower or upper value limit exceeded. 3: Sub-index incorrect. 4: No array, no sub-index. 5: Data type incorrect. 6: Setting not permitted (only resetting). 7: Descriptive element cannot be changed. 9: Descriptive data not available. 11: No master control. 15: No text array available. 17: Task cannot be executed due to operating state. 20: Illegal value. 21: Response too long. 22: Parameter address illegal. 23: Format illegal. 24: Number of values not consistent. 108: Unit unknown. Additional values: Only for internal Siemens troubleshooting. 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): 1: Device status cannot be changed to Device Download (drive object ON?). 2: Incorrect drive object number. 8: Maximum number of drive objects that can be generated exceeded. 11: Error while generating a drive object (global component). 12: Error while generating a drive object (drive component). 13: Unknown drive object type. 14: Drive status cannot be changed to “ready for operation” (r0947 and r0949). 15: Drive status cannot be changed to drive download. 16: Device status cannot be changed to “ready for operation”. 18: A new download is only possible if the factory settings are restored for the drive unit. 20: The configuration is inconsistent. 21: Error when accepting the download parameters. 22: SW-internal download error. 100: The download was canceled, because no write requests were received from the commissioning client (e.g. for communication error). 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 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:
See also: r9406, r9407, r9408 |
| A01049 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 p0971 to 1). |
| 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). Remedy: For fault value = 1, 5:
When using the Drive Control Chart (DCC) or free function blocks (FBLOCKS), the following applies:
|
| A01066 Buffer memory: 70% fill level reached or exceeded | Cause: The non-volatile buffer memory for parameter changes is filled to at least 70%. This can also occur if the buffer memory is active (p0014 = 1) and parameters are continually changed via a fieldbus system. Remedy:
In the following cases, the entries in the buffer memory are transferred into the ROM and then the buffer memory is cleared:
See also: p0014 (Buffer memory mode) |
| A01067 Buffer memory: 100 % fill level reached | Cause: The non-volatile buffer memory for parameter changes is filled to 100%. All additional parameter changes will no longer be taken into account in the non-volatile buffer memory. However, parameter changes can still be made in the volatile memory (RAM). This can also occur if the buffer memory is active (p0014 = 1) and parameters are continually changed via a fieldbus system. Remedy:
In the following cases, the entries in the buffer memory are transferred into the ROM and then the buffer memory is cleared:
See also: p0014 (Buffer memory mode) |
| 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:
|
| 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:
|
| A01098 RTC: Date and time setting required | Cause: The power supply for the Control Unit was interrupted for an extended period. The date and time displayed on the real-time clock are no longer accurate. Note: This alarm is only output when p8405 = 1 (factory setting). Remedy: Set the date and time on the real-time clock. See also: p8400, p8401 |
| N01101 (A) CU: memory card not available | Cause: The memory card is not available for the drive. Remedy: Insert a memory card. |
| F01105 (A) CU: Insufficient memory | Cause: Too many data sets are configured on this Control Unit. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: Reduce the number of data sets. |
| F01107 Save to memory card unsuccessful | Cause: A data save to the memory card was not able to be successfully carried out. – Memory card defective – Insufficient space on memory card. Fault value (r0949, interpret decimal): 1: The file on the RAM was not able to be opened. 2: The file on the RAM was not able to be read. 3: A new directory could not be created on the memory card. 4: A new file could not be created on the memory card. 5: A new file could not be written on the memory card. Remedy:
|
| F01112 CU: Power unit not permissible | Cause: The connected power unit cannot be used together with this Control Unit. Fault value (r0949, interpret decimal): 1: Power unit is not supported (e.g. PM340). 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:
|
| 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:
|
| F01205 CU: Time slice overflow | Cause: Insufficient computation time. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: Contact Technical Support. |
| 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:
|
| F01257 CU: Firmware version out of date | Cause: The Control Unit firmware is too old. Fault value (r0949, interpret hexadecimal): bbbbbbaa hex: aa = unsupported component aa = 01 hex = 1 dec: The firmware being used does not support the Control Unit. aa = 02 hex = 2 dec: The firmware being used does not support the Control Unit. aa = 03 hex = 3 dec: The firmware being used does not support the Power Module. aa = 04 hex = 4 dec: The firmware being used does not support the Control Unit. Remedy: For fault value = 1, 2, 4:
For fault value = 3:
|
| F01340 Topology: Too many components on one line | Cause: For the selected communications clock cycle, too many DRIVE-CLiQ components are connected to one line of the Control Unit. Fault value (r0949, interpret hexadecimal): xyy hex: x = fault cause, yy = component number or connection number. 1yy: The communications clock cycle of the DRIVE-CLiQ connection on the Control Unit is not sufficient for all read transfers. 2yy: The communications clock cycle of the DRIVE-CLiQ connection on the Control Unit is not sufficient for all write transfers. 3yy: Cyclic communication is fully utilized. 4yy: The DRIVE-CLiQ cycle starts before the earliest end of the application. An additional dead time must be added to the control. Sign-of-life errors can be expected. 5yy: Internal buffer overflow for net data of a DRIVE-CLiQ connection. 6yy: Internal buffer overflow for receive data of a DRIVE-CLiQ connection. 7yy: Internal buffer overflow for send data of a DRIVE-CLiQ connection. 8yy: The component clock cycles cannot be combined with one another. 900: The lowest common multiple of the clock cycles in the system is too high to be determined. 901: The lowest common multiple of the clock cycles in the system cannot be generated with the hardware. Remedy:
For fault value = 1yy – 4yy in addition:
For fault value = 8yy in addition:
For fault value = 9yy in addition:
|
| 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. |
| 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. 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. 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, p0651 Remedy: Carry out service/maintenance and reset the service/maintenance interval (p0651). |
| F01662 Error internal communications | Cause: A module-internal communication error has occurred. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01900 (F) PROFIBUS: Configuration telegram error | Cause: A PROFIBUS master attempts to establish a connection using an incorrect configuring telegram. Alarm value (r2124, interpret decimal): 2: Too many PZD data words for input or output. The number of possible PZD is specified by the number of indices in r2050/p2051. 3: Uneven number of bytes for input or output. 211: Unknown parameterizing block. Additional values: Only for internal Siemens troubleshooting. Remedy: Check the bus configuration on the master and the slave sides. For alarm value = 2: Check the number of data words for input and output. For alarm value = 211: Ensure offline version <= online version. |
| F01910 (N, A) Fieldbus interface setpoint timeout | Cause: The reception of setpoints from the fieldbus interface has been interrupted. – bus connection interrupted. – communication partner switched off. CU230P-2 DP: PROFIBUS master set into the STOP state. See also: p2040, p2047 Remedy: Ensure bus connection has been established and switch on communication partner. CU230P-2 BT, CU230P-2 HVAC: If required, adapt p2040. CU230P-2 DP:
|
| 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. Note: If there is no communication to a higher-level control system, then p2030 should be set = 0 to suppress this message. |
| A01945 PROFIBUS: Connection to the Publisher failed | Cause: For PROFIBUS peer-to-peer data transfer, the connection to at least one Publisher has failed. Alarm value (r2124, interpret binary): Bit 0 = 1: Publisher with address in r2077[0], connection failed. … Bit 15 = 1: Publisher with address in r2077[15], connection failed. Remedy: Check the PROFIBUS cables. See also: r2077 (PROFIBUS diagnostics peer-to-peer data transfer addresses) |
| F01946 (A) PROFIBUS: Connection to the Publisher aborted | Cause: The connection to at least one Publisher for PROFIBUS peer-to-peer data transfer in cyclic operation has been aborted. Fault value (r0949, interpret binary): Bit 0 = 1: Publisher with address in r2077[0], connection aborted. … Bit 15 = 1: Publisher with address in r2077[15], connection aborted. Remedy:
See also: r2077 (PROFIBUS diagnostics peer-to-peer data transfer addresses) |
| A02050 Trace: Start not possible | Cause: The trace has already been started. See also: p4700 (Trace control) 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. Alarm value (r2124, interpret decimal): 1: Recorder 0 2: Recorder 1 3: Recorders 0 and 1 See also: p4700, p4711, p4730, p4731, p4732, p4733, p4734, p4735, p4736, p4737 Remedy:
|
| A02055 Trace: Recording time too short | Cause: The trace duration is too short. The minimum is twice the value of the trace clock cycle. See also: p4721 (Trace recording time) Remedy: Check the selected recording time and, if necessary, adjust. |
| A02056 Trace: Recording cycle too short | Cause: The selected recording clock cycle is lower than the basic clock cycle 500µs. See also: p4720 (Trace recording cycle) Remedy: Increase the value for the trace cycle. |
| A02057 Trace: Time slice clock cycle invalid | Cause: The time slice clock cycle selected does not match any of the existing time slices. See also: p4723 (Trace time slice cycle) Remedy: Enter an existing time slice clock cycle. The existing time slices can be read out via p7901. |
| A02058 Trace: Time slice clock cycle for endless trace not valid | Cause: The selected time slice clock cycle cannot be used for the endless trace. See also: p4723 (Trace time slice cycle) Remedy: Enter the clock cycle of an existing time slice with a cycle time >= 2 ms for up to 4 recording channels or >= 4 ms from 5 recording channels per trace. The existing time slices can be read out via p7901. |
| A02059 Trace: Time slice clock cycle for 2 x 8 recording channels not valid | Cause: The selected time slice clock cycle cannot be used for more than 4 recording channels. See also: p4723 (Trace time slice cycle) Remedy: 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:
See also: p4730, p4731, p4732, p4733 Remedy:
|
| A02061 Trace: Invalid signal | Cause:
See also: p4730, p4731, p4732, p4733 Remedy:
|
| A02062 Trace: Invalid trigger signal | Cause:
See also: p4711 (Trace trigger signal) Remedy: Specify a valid trigger signal. |
| A02063 Trace: Invalid data type | Cause: The specified data type to select a signal using a physical address is invalid. See also: p4711, p4730, p4731, p4732, p4733 Remedy: Use a valid data type. |
| A02070 Trace: Parameter cannot be changed | Cause: The trace parameter settings cannot be changed when the trace is active. See also: p4700, p4710, p4711, p4712, p4713, p4714, p4715, p4716, p4720, p4721, p4722, p4730, p4731, p4732, p4733, p4780, p4781, p4782, p4783, p4789, p4795 Remedy:
|
| A02075 Trace: Pretrigger time too long | Cause: The selected pretrigger time must be shorter than the trace time. See also: p4721, p4722 Remedy:
|
| F02080 Trace: Parameterization deleted due to unit changeover | Cause: The trace parameterization in the drive unit was deleted due to a unit changeover or a change in the reference parameters. Remedy:
|
| A02095 MTrace 0: multiple trace cannot be activated | Cause: The following functions or settings are not permissible in conjunction with a multiple trace (trace recorder 0): – measuring function – long-time trace – trigger condition “immediate recording start” (IMMEDIATE) – trigger condition “start with function generator” (FG_START) Remedy:
|
| A02096 MTrace 0: cannot be saved | Cause: It is not possible to save the measurement results of a multiple trace on the memory card (trace recorder 0). A multiple trace is not started or is canceled. Alarm value (r2124, interpret decimal): 1: Memory card cannot be accessed (card not inserted or blocked). 3: Data save operation too slow. 4: Data save operation canceled (file not found). Remedy:
|
| A02097 MTrace 1: multiple trace cannot be activated | Cause: The following functions or settings are not permissible in conjunction with a multiple trace (trace recorder 1): – measuring function – long-time trace – trigger condition “immediate recording start” (IMMEDIATE) – trigger condition “start with function generator” (FG_START) Remedy:
|
| A02098 MTrace 1: cannot be saved | Cause: It is not possible to save the measurement results of a multiple trace on the memory card (trace recorder 1). Alarm value (r2124): 1: Memory card cannot be accessed. 3: data save operation too slow. 4: Data save operation canceled. Remedy:
|
| A02099 Trace: Insufficient Control Unit memory | Cause: The memory space still available on the Control Unit is no longer sufficient for the trace function. Remedy:
|
| A02150 OA: Application cannot be loaded | Cause: The system was not able to load an OA application. Alarm value (r2124, hex): 16: The interface version in the DCB user library is not compatible to the DCC standard library that has been loaded. Remedy:
|
| F02151 (A) OA: Internal software error | Cause: An internal software error has occurred within an OA application. Remedy:
|
| 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:
|
| F03000 NVRAM fault on action | Cause: A fault occurred during execution of action p7770 = 1 or 2 for the NVRAM data. Fault value (r0949, hex): yy = 1: Action p7770 = 1 not supported by this version. yy = 2: Data length mismatch. yy = 3: Data checksum in p7774 is not correct. yy = 4: No data available to load. Remedy:
|
| F03001 NVRAM checksum incorrect | Cause: A checksum error occurred when evaluating the non-volatile data (NVRAM) on the Control Unit. The NVRAM data affected was deleted. Remedy:
|
| F03505 (N, A) Analog input wire breakage | Cause: The wire-break monitoring for an analog input has responded. The input value has undershot the threshold value parameterized in p0761. Remedy:
|
| A03510 (F, N) Calibration data not plausible | Cause: During booting, the calibration data for the analog inputs is read and checked with respect to plausibility. At least one calibration data point was determined to be invalid. Remedy:
|
| A03520 (F, N) Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124): 33: AI2 wire breakage or sensor not connected. 34: AI2 measured resistance too low. 49: AI3 wire breakage or sensor not connected. 50: AI3 measured resistance too low. Remedy:
|
| A05000 (N) Power unit: Overtemperature heat sink AC inverter | Cause: The alarm threshold for overtemperature at the inverter heat sink has been reached. Remedy:
|
| A05001 (N) Power unit: Overtemperature depletion layer chip | Cause: Alarm threshold for overtemperature of the power semiconductor in the AC converter has been reached. Remedy:
|
| A05002 (N) Power unit: Air intake overtemperature | Cause: The alarm threshold for the air intake overtemperature has been reached. For air-cooled power units, the threshold is 42 °C. Remedy:
|
| A05003 (N) Power unit: Internal overtemperature | Cause: For chassis power units, the alarm threshold for internal overtemperature has been reached. Remedy:
|
| A05004 (N) Power unit: Rectifier overtemperature | Cause: The alarm threshold for the overtemperature of the rectifier has been reached. Remedy:
|
| A05006 (N) Power unit: Overtemperature thermal model | Cause: The temperature difference between the chip and heat sink has exceeded the permissible limit value. Remedy:
|
| A05065 (F, N) Voltage measured values not plausible | Cause: The voltage measurement does not supply any plausible values and is not used. Alarm value (r2124): Bit 1: Phase U, Bit 2: Phase V, Bit 3: Phase W. Remedy:
|
| F06310 (A) Supply voltage (p0210) incorrectly parameterized | Cause: The measured DC voltage lies outside the tolerance range after precharging has been completed. Permissible range: 1.16 * p0210 < r0070 < 1.6 * p0210 Remedy:
|
| A06921 (N) Braking resistor phase asymmetry | Cause: – the three resistors of the braking chopper are not symmetrical. – DC link voltage oscillations caused by fluctuating loads. Remedy:
|
| F06922 Braking resistor phase failure | Cause: A phase failure for the brake resistor was detected. Fault value (r0949): 11: Phase U, 12: Phase V, 13: Phase W. Remedy:
|
| F07011 Drive: Motor overtemperature | Cause: The motor temperature has exceeded the fault threshold. Possible causes: – motor is overloaded. – motor ambient temperature too high. – wire breakage or sensor not connected. Remedy:
|
| A07012 (N) Drive: Motor temperature model 1/3 overtemperature | Cause: The motor temperature model 1/3 identified that the alarm threshold was exceeded. Alarm value (r2124): 200: Model 1 (I2t) too high. 300: Model 3 too high. Remedy:
|
| A07014 (N) Drive: Motor temperature model configuration alarm | Cause: A fault has occurred in the configuration of the motor temperature model. Alarm value (r2124): 1: All motor temperature models: It is not possible to save the model temperature. Remedy:
|
| A07015 Drive: Motor temperature sensor alarm | Cause: An error was detected when evaluating the temperature sensor set in p0601. Possible causes: – wire breakage or sensor not connected. – measured resistance too low. Remedy:
|
| F07016 Drive: Motor temperature sensor fault | Cause: An error was detected when evaluating the temperature sensor set in p0601. Remedy:
|
| F07080 Drive: Incorrect control parameter | Cause: The closed-loop control parameters have been parameterized incorrectly (e.g. p0356 = L_spread = 0). The fault value (r0949) includes the parameter number involved. Remedy:
|
| F07082 Macro: Execution not possible | Cause: The macro cannot be executed. Fault value (r0949) provides specific causes (e.g., 19: Called file not valid, 24: Data type incorrect). 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:
|
| 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:
|
| 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 | Cause: An attempt was made to activate a function module. This is not permissible if the units have already been changed over. Remedy:
|
| A07094 General parameter limit violation | Cause: As a result of the violation of a parameter limit, the parameter value was automatically corrected. 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. – interconnection of the binector input is incorrect. – data transfer via the fieldbus was interrupted. Remedy:
|
| F07300 (A) Drive: Line contactor feedback signal missing | Cause: – the line contactor was not able to be closed or opened within the time in p0861. – the line contactor dropped out during operation. Remedy:
|
| F07311 Bypass motor switch | Cause: Drive switch feedback signal not consistent with the bypass state. Bit 1: Switch “Closed” feedback signal missing. Bit 2: Switch “Open” feedback signal missing. Remedy:
|
| F07312 Bypass Line Side Switch | Cause: Line Side Switch feedback signal not consistent with the bypass state. Bit 1: Switch “Closed” feedback signal missing. Bit 2: Switch “Open” feedback signal missing. Remedy:
|
| F07320 Drive: Automatic restart interrupted | Cause: – specified number of restart attempts (p1211) used up. – monitoring time for power unit expired (p0857). Remedy:
|
| A07321 Drive: Automatic restart active | Cause: The automatic restart (AR) is active. When the line supply returns, the drive is automatically restarted. Remedy:
|
| A07325 Drive: Hibernation mode active – drive automatically switched-on again | Cause: The “hibernation” function is active (p2398). The drive automatically powers itself up again as soon as the restart conditions are present. Remedy:
|
| F07330 Flying restart: Measured search current too low | Cause: During a flying restart, it was identified that the search current reached is too low. It is possible that the motor is not connected. Remedy:
|
| F07331 Flying restart: Function not supported | Cause: It is not possible to power up with the motor rotating (no flying restart). e.g., PMSM with U/f characteristic. Remedy:
|
| F07332 Flying restart: maximum speed reduced | Cause: The maximum speed that can be reached is reduced; at very high speeds problems associated with the flying restart can be encountered. Remedy:
|
| A07352 Drive: Limit switch signals not plausible | Cause: Limit switch signals are not plausible. Possible causes: BICO interconnections are not OK, or sensors are not supplying a valid signal. Remedy:
|
| A07353 Drive: DC quantity control deactivated | Cause: The DC quantity control has deactivated itself. The manipulated variable was at its limit. Remedy:
|
| F07390 Drive: DC link capacitor forming fault | Cause: The “DC link capacitor forming” function was canceled with fault. The expected DC link voltage is out of tolerance. Remedy:
|
| A07391 Drive: DC link capacitor forming active | Cause: The “DC link capacitor forming” function is active. Remedy:
|
| A07400 (N) Drive: DC link voltage maximum controller active | Cause: The DC link voltage controller has been activated because the upper switch-in threshold has been exceeded. The ramp-down times are automatically increased. Remedy:
|
| A07401 (N) Drive: DC link voltage maximum controller deactivated | Cause: The Vdc_max controller can no longer maintain the DC link voltage below the limit value and was therefore switched out. Remedy:
|
| A07402 (N) Drive: DC link voltage minimum controller active | Cause: The DC link voltage controller has been activated as the lower switch-in threshold has been undershot. The kinetic energy of the motor is used to buffer the DC link. Remedy:
|
| F07404 Drive: DC link voltage monitoring Vdc_max | Cause: The monitoring of the DC link voltage p1284 has responded (only U/f control). Remedy:
|
| F07405 (N, A) Drive: Kinetic buffering minimum speed fallen below | Cause: During kinetic buffering the speed fell below minimum speed and the line supply did not return. Remedy:
|
| F07406 (N, A) Drive: Kinetic buffering maximum time exceeded | Cause: The maximum buffer time has been exceeded without the line supply having returned. Remedy:
|
| A07409 (N) Drive: U/f control, current limiting controller active | Cause: The current limiting controller of the U/f control was activated because the current limit was exceeded. Remedy:
|
| F07410 Drive: Current controller output limited | Cause: The condition “I_act = 0 and Uq_set_1 longer than 16 ms at its limit” is present. – motor not connected or motor contactor open. – motor data/configuration mismatch. – power unit defective. Remedy:
|
| F07411 Drive: Flux setpoint not reached when building up excitation | Cause: When quick magnetizing is configured the specified flux setpoint is not reached. – incorrect motor data. – current limit too low. – power unit too small. Remedy:
|
| A07416 Drive: Flux controller configuration | Cause: The configuration of the flux control (p1401) is contradictory. 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:
|
| A07427 Motor switch-in alarm | Cause: 1: Technology controller not active or used for main setpoint. 2: Operating time limits exceeded in at least one external motor. Remedy:
|
| A07428 (N) Technology controller parameterizing error | Cause: The technology controller has a parameterizing error. The upper output limit in p2291 is set lower than the lower output limit in p2292. Remedy:
|
| F07435 (N) Drive: Setting the ramp-function generator for sensorless vector control | Cause: During operation with sensorless vector control the ramp-function generator was stopped. An internal setting command caused the setpoint speed to be frozen. Remedy:
|
| F07436 (A) Free tec_ctrl 0 actual value limited | Cause: The actual value for the free technology controller 0 has reached the limit. Remedy:
|
| F07437 (A) Free tec_ctrl 1 actual value limited | Cause: The actual value for the free technology controller 1 has reached the limit. Remedy:
|
| F07438 (A) Free tec_ctrl 2 actual value limited | Cause: The actual value for the free technology controller 2 has reached the limit. Remedy:
|
| A07444 PID autotuning is activated | Cause: Automatic setting of the PID controller parameters (PID autotuning) was activated. Remedy:
|
| F07445 PID autotuning canceled | Cause: The PID autotuning was canceled as a result of an error. Remedy:
|
| A07530 Drive: Drive Data Set DDS not present | Cause: The selected drive data set is not available. 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. See also: p0810, p0811, p0812, p0813, r0836 Remedy:
|
| F07800 Drive: No power unit present | Cause: The power unit parameters cannot be read or no parameters are stored in the power unit. Note: This fault also occurs if an incorrect topology was selected in the commissioning software and this parameterization is then downloaded to the Control Unit. See also: r0200 (Power unit code number actual) Remedy:
|
| F07801 Drive: Motor overcurrent | Cause: The permissible motor limit current was exceeded. – effective current limit set too low. – current controller not correctly set. – U/f operation: Up ramp was set too short or the load is too high. – U/f operation: Short-circuit in the motor cable or ground fault. – U/f operation: Motor current does not match current of power unit. – Switch to rotating motor without flying restart function (p1200). Note: Limit current = 2 x minimum (p0640, 4 x p0305 x p0306) >= 2 x p0305 x p0306 Remedy:
|
| F07802 Drive: Infeed or power unit not ready | Cause: After an internal switch-on command, the infeed or drive does not signal ready. – Monitoring time is too short. – DC link voltage is not present. – Associated infeed or drive of the signaling component is defective. – Supply voltage incorrectly set. Remedy:
See also: p0857 (Power unit monitoring time) |
| A07805 (N) Drive: Power unit overload I2t | Cause: Alarm threshold for I2t overload (p0294) of the power unit exceeded. The response parameterized in p0290 becomes active. See also: p0290 Remedy:
|
| F07806 Drive: Regenerative power limit exceeded (F3E) | Cause: For blocksize power units, types PM250 and PM260, the regenerative rated power r0206[2] was exceeded for more than 10 s. See also: r0206, p1531 Remedy:
|
| F07807 Drive: Short-circuit/ground fault detected | Cause: A phase-phase short-circuit or ground fault was detected at the motor-side output terminals of the converter. Fault value (r0949, interpret decimal): 1: Short-circuit, phase UV. 2: Short-circuit, phase UW. 3: Short-circuit, phase VW. 4: Ground fault with overcurrent. 5: Motor cable phase U interrupted 6: Motor cable phase V interrupted 7: Motor cable phase W interrupted 8: Short-circuit with hardware shutdown 1yxxx: Ground fault with current in phase U detected (y = pulse number, xxxx = component of the current in phase V in per mille). 2yxxx: Ground fault with current in phase V detected (y = pulse number, xxxx = component of the current in phase U in per mille). Note: Also when interchanging the line and motor cables is identified as a motor-side short circuit. The ground fault test only functions when the motor is stationary. Connecting to a motor that is either not de-energized or partially de-energized is possibly detected as ground fault. Remedy:
For a ground fault the following applies:
|
| F07810 Drive: Power unit EEPROM without rated data | Cause: No rated data are stored in the power unit EEPROM. See also: p0205, r0206, r0207, r0208, r0209 Remedy: Replace the power unit or inform Siemens Customer Service. |
| A07850 (F) External alarm 1 | Cause: The condition for “External alarm 1” is satisfied. Note: The “External alarm 1” is initiated by a 1/0 edge via binector input p2112. See also: p2112 (External alarm 1) Remedy: Eliminate the causes of this alarm. |
| A07851 (F) External alarm 2 | Cause: The condition for “External alarm 2” is satisfied. Note: The “External alarm 2” is initiated by a 1/0 edge via binector input p2116. See also: p2116 (External alarm 2) Remedy: Eliminate the causes of this alarm. |
| A07852 (F) External alarm 3 | Cause: The condition for “External alarm 3” is satisfied. Note: The “External alarm 3” is initiated by a 1/0 edge via binector input p2117. See also: p2117 Remedy: Eliminate the causes of this alarm. |
| F07860 (A) External fault 1 | Cause: The condition for “External fault 1” is satisfied. Note: The “External fault 1” is initiated by a 1/0 edge via binector input p2106. See also: p2106 (External fault 1) Remedy:
|
| F07861 (A) External fault 2 | Cause: The condition for “External fault 2” is satisfied. Note: The “External fault 2” is initiated by a 1/0 edge via binector input p2107. See also: p2107 (External fault 2) Remedy:
|
| F07862 (A) External fault 3 | Cause: The condition for “External fault 3” is satisfied. Note: The “External fault 3” is initiated by a 1/0 edge via the following parameters. – AND logic operation, binector input p2108, p3111, p3112. – switch-on delay p3110. See also: p2108, p3110, p3111, p3112 Remedy:
|
| A07891 Drive: Load monitoring pump/fan blocked | Cause: The load monitoring is configured for a pump or fan (p2193 = 4, 5). The monitoring function detects when the pump/fan is blocked. It is possible that the blocking torque threshold (p2168) is set too low (e.g. heavy duty starting). See also: p2165, p2168, p2181, p2193 Remedy:
|
| A07892 Drive: Load monitoring pump/fan no load condition | Cause: The load monitoring is configured for a pump or fan (p2193 = 4, 5). The monitoring function detects when the pump/fan is operating under no load conditions. The pump is running in the dry state (no medium to be pumped) – or the fan has a broken belt. It is possible that the detection torque threshold is too low (p2191). See also: p2181, p2191, p2193 Remedy:
|
| A07893 Drive: Load monitoring pump leakage | Cause: The load monitoring is configured for a pump (p2193 = 4). The monitoring function detects a leak in the pump circuit. In this case, the pump requires a torque that is lower than in normal operation to pump the reduced quantity. See also: p2181, p2182, p2183, p2184, p2186, p2188, p2190, p2193 Remedy:
|
| F07894 Drive: Load monitoring pump/fan blocked | Cause: The load monitoring is configured for a pump or fan (p2193 = 4, 5). The monitoring function detects when the pump/fan is blocked. It is possible that the blocking torque threshold (p2168) is set too low (e.g. heavy duty starting). See also: p2165, p2168, p2181, p2193 Remedy:
|
| F07895 Drive: Load monitoring pump/fan no load condition | Cause: The load monitoring is configured for a pump or fan (p2193 = 4, 5). The monitoring function detects when the pump/fan is operating under no load conditions. The pump is running in the dry state (no medium to be pumped) – or the fan has a broken belt. It is possible that the detection torque threshold is too low (p2191). See also: p2181, p2191, p2193 Remedy:
|
| F07896 Drive: Load monitoring pump leakage | Cause: The load monitoring is configured for a pump (p2193 = 4). The monitoring function detects a leak in the pump circuit. In this case, the pump requires a torque that is lower than in normal operation to pump the reduced quantity. See also: p2181, p2182, p2183, p2184, p2186, p2188, p2190, p2193 Remedy:
|
| F07900 (N, A) Drive: Motor blocked | Cause: Motor has been operating at the torque limit longer than the time specified in p2177 and below the speed threshold in p2175. This signal can also be triggered if the speed is oscillating and the speed controller output repeatedly goes to its limit. It may also be the case that thermal monitoring of the power unit reduces the current limit (see p0290), thereby causing the motor to decelerate. See also: p2175, p2177 Remedy:
|
| F07901 Drive: Motor overspeed | Cause: The maximum permissible speed was either positively or negatively exceeded. The maximum permissible positive speed is formed as follows: Minimum (p1082, CI: p1085) + p2162 The maximum permissible negative speed is formed as follows: Maximum (-p1082, CI: 1088) – p2162 Remedy: The following applies for a positive direction of rotation:
The following applies for a negative direction of rotation:
|
| F07902 (N, A) Drive: Motor stalled | Cause: The system has identified that the motor has stalled for a time longer than is set in p2178. Fault value (r0949, interpret decimal): 1: Reserved. 2: Stall detection using r1408.12 (p1745) or via (r0084 … r0083). See also: p2178 (Motor stalled delay time) Remedy: Steps should always be taken to ensure that both motor data identification and the rotating measurement were (if possible) carried out (see p1900, r3925).
If there is no fault, then the fault tolerance (p1745) or the delay time (p2178) can be increased.
|
| A07903 Drive: Motor speed deviation | Cause: The absolute value of the speed difference from the setpoint (p2151) and the speed actual value (r2169) exceeds the tolerance threshold (p2163) longer than tolerated (p2164, p2166). The alarm is only enabled for p2149.0 = 1. Possible causes: – The load torque is greater than the torque setpoint. – When accelerating, the torque/current/power limit is reached. If the limits are not sufficient, then it is possible that the drive has been dimensioned too small. – For active Vdc controller. For U/f control, the overload condition is detected as the I_max controller is active. See also: p2149 (Monitoring configuration) Remedy:
|
| A07910 (N) Drive: Motor overtemperature | Cause: KTY84/PT1000/PT100 or no sensor: The measured motor temperature or the temperature of the motor temperature model 2 has exceeded the alarm threshold (p0604). The response parameterized in p0610 becomes active. PTC or bimetallic NC contact: The response threshold of 1650 Ohm was exceeded or the NC contact opened. Alarm value (r2124, interpret decimal): 11: No output current reduction. 12: Output current reduction active. See also: p0604, p0610 Remedy:
See also: p0612, p0617, p0618, p0619, p0625, p0626, p0627, p0628 |
| A07920 Drive: Torque/speed too low | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic (too low). For p2193 = 2: The speed signal from the external encoder (refer to p3230) deviates from the speed (r2169) (too low). See also: p2181 (Load monitoring response) Remedy:
|
| A07921 Drive: Torque/speed too high | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic (too high). For p2193 = 2: The speed signal from the external encoder (refer to p3230) deviates from the speed (r2169) (too high). Remedy:
|
| A07922 Drive: Torque/speed out of tolerance | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic. For p2193 = 2: The speed signal from the external encoder (refer to p3230) deviates from the speed (r2169). Remedy:
|
| F07923 Drive: Torque/speed too low | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic (too low). For p2193 = 2: The speed signal from the external encoder (refer to p3230) deviates from the speed (r2169) (too low). Remedy:
|
| F07924 Drive: Torque/speed too high | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic (too high). For p2193 = 2: The speed signal from the external encoder (refer to p3230) deviates from the speed (r2169) (too high). Remedy:
|
| F07925 Drive: Torque/speed out of tolerance | Cause: For p2193 = 1: The torque deviates from the torque/speed envelope characteristic. For p2193 = 2: The speed signal from the external encoder (refer to p3230) deviates from the speed (r2169). Remedy:
|
| A07926 Drive: Envelope curve parameter invalid | Cause: Invalid parameter values were entered for the envelope characteristic of the load monitoring. The following rules apply for the speed thresholds: p2182 < p2183 < p2184 The following rules apply for the torque thresholds: p2185 > p2186, p2187 > p2188, p2189 > p2190 Load monitoring configuration and response must match. It is not permissible that the individual load torque monitoring areas overlap. Alarm value (r2124, interpret decimal): Number of the parameter with the invalid value. The load torque monitoring has not been activated as long as the alarm is active. Remedy:
|
| A07927 DC braking active | Cause: The motor is braked with DC current. DC braking is active. 1) A message with response DCBRK is active. The motor is braked with the braking current set in p1232 for the duration set in p1233. If the standstill threshold p1226 is undershot, then braking is prematurely canceled. 2) DC braking has been activated at binector input p1230 with the DC braking set (p1230 = 4). Braking current p1232 is injected until this binector input becomes inactive. Remedy: Not necessary. The alarm automatically disappears once DC braking has been executed. |
| A07929 (F) Drive: No motor detected | Cause: The absolute current value is so small after enabling the inverter pulses that no motor is detected. Note: – in the case of vector control and an induction motor, this alarm is followed by fault F07902. – PM330: Correction currents are calculated and displayed in the optimized pulse pattern range. See also: p2179 (Output load identification current limit) Remedy:
|
| F07936 Drive: load failure | Cause: The load monitoring has detected a load failure. Remedy:
See also: p2193, p3232 |
| F07950 (A) Motor parameter incorrect | Cause: The motor parameters were incorrectly entered while commissioning (e.g. p0300 = 0, no motor) Fault value (r0949, interpret decimal): Parameter number involved. See also: p0300, p0301, p0304, p0305, p0307, p0310, p0311, p0314, p0315, p0316, p0320, p0322, p0323 Remedy: Compare the motor data with the rating plate data and if required, correct. |
| F07967 Drive: Incorrect pole position identification | Cause: A fault has occurred during the pole position identification routine. Only for internal Siemens troubleshooting. Remedy: Carry out a POWER ON. |
| F07968 Drive: Lq-Ld measurement incorrect | Cause: A fault has occurred during the Lq-Ld measurement. Fault value (r0949, interpret decimal): 10: Stage 1: The ratio between the measured current and zero current is too low. 12: Stage 1: The maximum current was exceeded. 15: Second harmonic too low. 16: Drive converter too small for the measuring technique. 17: Abort due to pulse inhibit. Remedy: For fault value = 10:
For fault value = 12:
For fault value = 16:
For fault value = 17:
|
| F07969 Drive: Incorrect pole position identification | Cause: A fault has occurred during the pole position identification routine. Fault value (r0949, interpret decimal): 1: Current controller limited 2: Motor shaft locked. 10: Stage 1: The ratio between the measured current and zero current is too low. 11: Stage 2: The ratio between the measured current and zero current is too low. 12: Stage 1: The maximum current was exceeded. 13: Stage 2: The maximum current was exceeded. 14: Current difference to determine the +d axis too low. 15: Second harmonic too low. 16: Drive converter too small for the measuring technique. 17: Abort due to pulse inhibit. 18: First harmonic too low. 20: Pole position identification requested with the motor shaft rotating and activated “flying restart” function. Remedy: For fault value = 1:
For fault value = 2:
For fault value = 10:
For fault value = 11:
For fault value = 12:
For fault value = 13:
For fault value = 14:
For fault value = 15:
For fault value = 16:
For fault value = 17:
For fault value = 18:
For fault value = 20:
|
| A07980 Drive: Rotating measurement activated | Cause: The rotating measurement (automatic speed controller optimization) is activated. The rotating measurement is carried out at the next switch-on command. Note: During the rotating measurement it is not possible to save the parameters (p0971). See also: p1960 (Rotating measurement selection) Remedy: Not necessary. The alarm disappears automatically after the speed controller optimization has been successfully completed or for the setting p1900 = 0. |
| A07981 Drive: Enable signals for the rotating measurement missing | Cause: The rotating measurement cannot be started due to missing enable signals. 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:
See also: r0002, r0046 |
| 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. 5: Field weakening active. 6: The speed setpoint was not able to be approached as the minimum limiting is active. 7: The speed setpoint was not able to be approached as the suppression (skip) bandwidth is active. 8: The speed setpoint was not able to be approached as the maximum limiting is active. 9: Several values of the determined saturation characteristic are not plausible. 10: Saturation characteristic could not be sensibly determined because load torque too high. Remedy: For fault value = 1:
For fault value = 1 … 2:
For fault value = 1 … 4:
For fault value = 5:
For fault value = 6:
For fault value = 7:
For fault value = 8:
For fault value = 9, 10:
Note: The saturation characteristic identification routine can be disabled using p1959.1. See also: p1959 |
| 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. The measured moment of inertia is less than the 0.1x or greater than 500x the preset moment of inertia of the motor p0341. Remedy: For fault value = 1:
For fault value = 2, 5:
For fault value = 3, 6:
For fault value = 4, 7:
For fault value = 8:
For fault value = 9:
For fault value = 10:
For fault value = 11:
Note: The moment of inertia identification routine can be disabled using p1959.2. See also: p1959 |
| 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:
For fault value = 2:
For fault value = 3:
For fault value = 4:
For fault value = 5:
For fault value = 6:
See also: p1959 |
| 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). |
| 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). See also: p1959 |
| 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. 4: identified stator reactance lies outside the expected range 50 … 500 % of Zn. 5: identified magnetizing reactance lies outside the expected range 50 … 500 % of Zn. 6: Identified rotor time constant lies outside the expected range 10 ms … 5 s. 7: identified total leakage reactance lies outside the expected range 4 … 50 % of Zn. 8: Identified stator leakage reactance lies outside the expected range 2 … 50% of Zn. 9: Identified rotor leakage reactance lies outside the expected range 2 … 50% 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. 60: Incorrect power stack data for the calibration of the converter output voltage 61: Incorrect measured values for the calibration of the converter output voltage Note: Percentage values are referred to the rated motor impedance: Zn = Vmot.nom / sqrt(3) / Imot,nom Remedy: For fault value = 1 … 40:
For fault value = 4, 7:
For fault value = 11 in addition:
For fault value = 12:
|
| 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 switch-on command. If rotating measurement is selected (see p1900, p1960), it will not be possible to save the parameter assignment. Once motor data identification has been completed or deactivated, the option to save the parameter assignment will be made available again. See also: p1910 Remedy: Not necessary. The alarm automatically disappears after the motor data identification routine has been successfully completed or for the setting p1900 = 0. |
| A07994 (F, N) Drive: motor data identification not performed | Cause: The “Vector control” mode or application class “Standard Drive Control, STC” (p0096 = 1) 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). Note: For SINAMICS G120, a check is made and the alarm is output also when exiting commissioning and when the system powers up. Remedy:
|
| F08010 (N, A) CU: Analog-to-digital converter | Cause: The analog-to-digital converter on the Control Unit has not supplied any converted data. Remedy:
|
| F08501 (N, A) PROFINET: Setpoint timeout | Cause: The reception of setpoints from PROFINET has been interrupted. – bus connection interrupted. – controller switched off. – controller set into the STOP state. Remedy:
|
| F08502 (A) PROFINET: Monitoring time sign-of-life expired | Cause: The monitoring time for the sign-of-life counter has expired. The connection to the PROFINET interface was interrupted. Remedy:
|
| A08511 (F) PROFINET: 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. 2: Too many PZD data words for input or output. The number of possible PZD is specified by the number of indices in r2050/p2051. 3: Uneven number of bytes for input or output. Remedy: Check the receive configuration data. For alarm value = 2: Check the number of data words for output and input. |
| A08526 (F) PROFINET: No cyclic connection | Cause: There is no connection to a PROFINET controller. Remedy: Establish the cyclic connection and activate the controller with cyclic operation. Check the parameters “Name of Station” and “IP of Station” (r61000, r61001). |
| A08564 PN/COMM BOARD: syntax error in the configuration file | Cause: A syntax error has been detected in the ASCII configuration file for the Communication Board Ethernet. The saved configuration file has not been loaded. Remedy:
Note: The configuration is not applied until the next POWER ON! See also: p8925 (Activate PN interface configuration) |
| A08565 PROFINET: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration (p8925) for the PROFINET interface. The currently set configuration has not been activated. 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. See also: p8920 (PN Name of Station), p8921 (PN IP address), p8922 (PN Default Gateway), p8923 (PN Subnet Mask) Remedy:
See also: p8925 (Activate PN interface configuration) |
| A08565 PROFINET: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration (p8925) for the PROFINET interface. The currently set configuration has not been activated. Alarm value (r2124): 0: general consistency error, 1: IP config error, 2: Station name error, 3: DHCP conflict, 4: DHCP active. Remedy:
|
| A08800 PROFIenergy energy-saving mode active | Cause: The PROFIenergy energy-saving mode is active. Remedy:
|
| F13009 Licensing OA application not licensed | Cause: At least one OA application which is under license does not have a license. Remedy:
|
| F13100 Know-how protection: Copy protection error | Cause: The know-how protection with copy protection for the memory card is active. An error has occurred when checking the memory card. Fault value (r0949): 0: Not inserted, 1: Invalid (not Siemens), 2: Invalid, 3: Used in another CU. Remedy:
|
| F13101 Know-how protection: Copy protection cannot be activated | Cause: An error occurred when attempting to activate the copy protection for the memory card. Fault value: 0: Card not inserted, 1: Invalid memory card. Remedy:
|
| F13102 Know-how protection: Consistency error of the protected data | Cause: An error was identified when checking the consistency of the protected files. The project cannot be run. Remedy:
|
| F30001 Power unit: Overcurrent | Cause: The power unit has detected an overcurrent condition. – closed-loop control incorrectly parameterized. – motor has short-circuit or fault to ground. – U/f operation: Up ramp set too low or rated current mismatch. – power cables not correctly connected or too long. – power unit defective. Remedy:
|
| F30002 Power unit: DC link voltage overvoltage | Cause: The power unit has detected an overvoltage condition in the DC link. – motor regenerates too much energy. – line supply voltage too high. – line phase interrupted. – dynamic response of DC link voltage controller excessive. Remedy:
|
| F30003 Power unit: DC link voltage undervoltage | Cause: The power unit has detected an undervoltage condition in the DC link. – line supply failure. – line supply voltage below permissible value. – line phase interrupted. Remedy:
|
| F30004 Power unit: Overtemperature heat sink AC inverter | Cause: The temperature of the power unit heat sink has exceeded the permissible limit value. – insufficient cooling, fan failure. – overload. – ambient temperature too high. – pulse frequency too high. Remedy:
|
| F30005 Power unit: Overload I2t | Cause: The power unit was overloaded. – permissible rated power unit current exceeded for too long. – permissible load duty cycle not maintained. Remedy:
|
| F30011 Power unit: Line phase failure in main circuit | Cause: At the power unit, the DC link voltage ripple has exceeded the permissible limit value. – a line phase has failed. – the 3 line phases are inadmissibly asymmetrical. – fuse of a phase has ruptured. – motor phase has failed. Remedy:
|
| F30012 Power unit: Temperature sensor heat sink wire breakage | Cause: The connection to a heat sink temperature sensor in the power unit is interrupted. Remedy:
|
| F30013 Power unit: Temperature sensor heat sink short-circuit | Cause: The heat sink temperature sensor in the power unit is short-circuited. Remedy:
|
| F30015 (N, A) Power unit: Phase failure motor cable | Cause: A phase failure in the motor feeder cable was detected. – motor correctly connected but drive stalled in U/f control. – closed-speed control is instable. Remedy:
|
| A30016 (N) Power unit: Load supply switched off | Cause: The DC link voltage is too low. Remedy:
|
| F30017 Power unit: Hardware current limit has responded too often | Cause: The hardware current limitation in the relevant phase has responded too often. – closed-loop control incorrectly parameterized. – fault in motor or power cables. – motor load too high. – power unit defective. Remedy:
|
| F30021 Power unit: Ground fault | Cause: The power has detected a ground fault. – ground fault in power cables or motor. – CT defective. – short-circuit at braking resistor. Remedy:
|
| F30022 Power unit: Monitoring U_ce | Cause: In the power unit, the monitoring of the collector-emitter voltage (U_ce) of the semiconductor has responded. – fiber-optic cable interrupted. – power supply of IGBT gating module missing. – short-circuit at power unit output. – defective semiconductor. Remedy:
|
| F30024 Power unit: Overtemperature thermal model | Cause: The temperature difference between the heat sink and chip has exceeded the permissible limit value. – permissible load duty cycle not maintained. – insufficient cooling. – overload. Remedy:
|
| F30025 Power unit: Chip overtemperature | Cause: The chip temperature of the semiconductor has exceeded the permissible limit value. Remedy:
|
| F30027 Power unit: Precharging DC link time monitoring | Cause: The power unit DC link was not able to be precharged within the expected time. – no line supply connected. – line contactor/switch not closed. – line supply voltage too low. – precharging resistors overheated. – DC link ground fault or short-circuit. Remedy:
|
| A30030 Power unit: Internal overtemperature alarm | Cause: The temperature inside the drive converter has exceeded the permissible temperature limit. – insufficient cooling, fan failure. – overload. – ambient temperature too high. Remedy:
|
| A30031 Power unit: Hardware current limiting in phase U | Cause: Hardware current limit for phase U responded. The pulsing in this phase is inhibited for one pulse period. – closed-loop control incorrectly parameterized. – fault in motor/cables. – power cables too long. Remedy:
|
| A30032 Power unit: Hardware current limiting in phase V | Cause: Hardware current limit for phase V responded. Remedy:
|
| A30033 Power unit: Hardware current limiting in phase W | Cause: Hardware current limit for phase W responded. Remedy:
|
| A30034 Power unit: Internal overtemperature | Cause: The alarm threshold for internal overtemperature has been reached. Remedy:
|
| F30035 Power unit: Air intake overtemperature | Cause: The air intake in the power unit has exceeded the permissible temperature limit (55°C for air-cooled). Remedy:
|
| F30036 Power unit: Internal overtemperature | Cause: The temperature inside the drive converter has exceeded the permissible temperature limit. Remedy:
|
| F30037 Power unit: Rectifier overtemperature | Cause: The temperature in the rectifier of the power unit has exceeded the permissible temperature limit. Remedy:
|
| 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:
|
| A30049 Power unit: Internal fan faulty | Cause: The internal fan has failed. Remedy:
|
| F30051 Power unit: Motor holding brake short circuit detected | Cause: A short-circuit at the motor holding brake terminals has been detected. Remedy:
|
| F30052 EEPROM data error | Cause: EEPROM data error of the power unit module. Remedy:
|
| F30055 Power unit: Braking chopper overcurrent | Cause: An overcurrent condition has occurred in the braking chopper. Remedy:
|
| A30057 Power unit: Line asymmetry | Cause: Frequencies have been detected on the DC link voltage that would suggest line asymmetry or failure of a line phase. Remedy:
|
| F30059 Power unit: Internal fan faulty | Cause: The internal power unit fan has failed and is possibly defective. Remedy:
|
| A30065 (F, N) Voltage measured values not plausible | Cause: The voltage measurement is not supplying any plausible values. Remedy:
|
| F30068 Power unit: undertemperature inverter heat sink | Cause: The actual inverter heat sink temperature is below the permissible minimum value. Remedy:
|
| F30071 No new actual values received from the Power Module | Cause: More than one actual value telegram from the power unit module has failed. Remedy:
|
| F30072 Setpoints can no longer be transferred to the Power Module | Cause: More than one setpoint telegram was not able to be transferred to the power unit module. Remedy:
|
| F30074 (A) Communication error between the Control Unit and Power Module | Cause: Communications between the Control Unit (CU) and Power Module (PM) via the interface no longer possible. Remedy:
|
| F30075 Configuration of the power unit unsuccessful | Cause: A communication error has occurred while configuring the power unit using the Control Unit. Remedy:
|
| 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 incorrectly parameterized. – short-circuit or ground fault. – power unit defective. Remedy:
|
| F30081 Power unit: Switching operations too frequent | Cause: The power unit has executed too many switching operations for current limitation. Remedy:
|
| F30105 PU: Actual value sensing fault | Cause: At least one incorrect actual value channel was detected on the Power Stack Adapter (PSA). Remedy:
|
| 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:
|
| F30662 Error in internal communications | Cause: A module-internal communication error has occurred. Remedy:
|
| F30664 Error while booting | Cause: An error has occurred during booting. Remedy:
|
| N30800 (F) Power unit: Group signal | Cause: The power unit has detected at least one fault. Remedy:
|
| F30802 Power unit: Time slice overflow | Cause: A time slice overflow has occurred. Remedy:
|
| F30804 (N, A) Power unit: CRC | Cause: A checksum error (CRC error) has occurred for the power unit. Remedy:
|
| F30805 Power unit: EEPROM checksum error | Cause: Internal parameter data is corrupted. Remedy:
|
| F30809 Power unit: Switching information not valid | Cause: For 3P gating unit, the switching status word was not found. Remedy:
|
| A30810 (F) Power unit: Watchdog timer | Cause: SAC watchdog timer overflow during booting. Remedy:
|
| F30850 Power unit: Internal software error | Cause: An internal software error has occurred in the power unit. Remedy:
|
| F30903 Power unit: I2C bus error occurred | Cause: Communications error with an EEPROM or an analog/digital converter. Remedy:
|
| A30920 (F) Temperature sensor fault | Cause: Error evaluating temperature sensor. Remedy:
|
| F30950 Power unit: Internal software error | Cause: An internal software error has occurred. Remedy:
|
| A30999 (F, N) Power unit: Unknown alarm | Cause: An alarm occurred on the power unit that cannot be interpreted by the Control Unit firmware (firmware mismatch). Remedy:
|
| F35950 TM: Internal software error | Cause: An internal software error has occurred in the Terminal Module. Remedy:
|
| A50010 (F) PROFINET: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration (p8925) for the PROFINET interface. Remedy:
|
| A50011 (F) Ethernet/IP: configuration error | Cause: An EtherNet/IP controller attempts to establish a connection using an incorrect configuring telegram. Remedy:
|
| F50510 FBLOCKS: Logon of the runtime group rejected | Cause: Logon of at least one runtime group was rejected (too many different hardware sampling times). Remedy:
|
| F50511 FBLOCKS: Memory no longer available for free function blocks | Cause: More memory was requested than was available on the Control Unit. Remedy:
|
| A50513 (F) FBLOCKS: Run sequence value already assigned | Cause: An attempt was made to assign a run sequence value already assigned to another function block. Remedy:
|
| A50517 FBLOCKS: Int. meas. active | Cause: A Siemens internal measurement has been activated. Remedy:
|
| F50518 FBLOCKS: Sampling time of free runtime group differs at download | Cause: In the STARTER/SCOUT project, the hardware sampling time of a free runtime group was set to a value that was either too low or too high. Remedy:
|
| F52960 Cavitation protection failure | Cause: Conditions exist for cavitation damage (fluid not flowing sufficiently). Remedy:
|
| A52961 Cavitation protection warning | Cause: Conditions for possible cavitation damage are detected. Remedy:
|
| A52962 Mpc operating time limit exceeded | Cause: The continuous operating time of at least one motor has exceeded the limit. Remedy:
|
| A52963 Mpc PID deviation exceeded | Cause: The technology controller system deviation has exceeded the threshold. Remedy:
|
| A52964 Mpc one motor available | Cause: Only one motor is not under service or locked manually. Remedy:
|
| F52965 Mpc no motor available | Cause: All motors are under service or locked manually. Remedy:
|
| F52966 Mpc motor quantity not matched | Cause: p29521 and digital output settings do not match. Remedy:
|