Siemens G115D 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. 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:
|
| 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:
|
| 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:
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 Remedy:
|
| F01018 Booting has been interrupted several times | Cause: Module booting was interrupted several times. As a consequence, the module boots with the factory setting. Possible reasons 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). |
| 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:
|
| 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:
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:
|
| F01029 DIP switch and parameter inconsistent | Cause: Different settings between the parameters and the DIP switch were identified. Fault value (r0949, interpret decimal): 0: The setting for 87 Hz operation using DIP switch DIP1.6 is different for the configuration using parameter p0133.1. The setting of DIP switch DIP1.6 was transferred into p0133.1. 1: The setting for the motor type using DIP switch DIP1.5 differs from the configuration using parameter p0300/p0301. The setting of DIP switch DIP1.5 was transferred into p0300/p0301. 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:
For the commissioning software, the monitoring time is set as follows: |
| F01033 Units changeover: Reference parameter value invalid | Cause: When changing over the units to the referred representation type, it is not permissible for any of the required reference parameters to be equal to 0.0 Fault value (r0949, parameter): Reference parameter whose value is 0.0. Remedy:
|
| F01034 Units changeover: Calculation parameter values after reference value change unsuccessful | Cause: The change of a reference parameter meant that for an involved parameter the selected value was not able to be re-calculated in the per unit representation. The change was rejected and the original parameter value restored. Fault value (r0949, parameter): Parameter whose value was not able to be re-calculated. 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. 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). Remedy:
|
| F01038 (A) ACX: Loading the parameter back-up file unsuccessful | Cause: An error has occurred when downloading PSxxxyyy.ACX or PTxxxyyy.ACX files from the non-volatile memory. Fault value (r0949, interpret hexadecimal): Byte 1: yyy in the file name PSxxxyyy.ACX. Byte 2: 255 (Incorrect drive object type) or 254 (Topology comparison unsuccessful). Remedy:
|
| F01039 (A) ACX: Writing to the parameter back-up file was unsuccessful | Cause: Writing to at least one parameter back-up file PSxxxyyy.*** in the non-volatile memory was unsuccessful. – 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. 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. (See manual for full list of fault causes 3-108). 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. (See manual for full list of fault values 11-100). Remedy:
|
| F01044 CU: Descriptive data error | Cause: An error was detected when loading the descriptive data saved in the non-volatile memory. Remedy:
|
| A01045 Configuring data invalid | Cause: An error was detected when evaluating the parameter files 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. Remedy:
|
| 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:
|
| 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]). Remedy:
|
| A01064 (F) CU: Internal error (CRC) | Cause: A checksum error (CRC error) has occurred in the Control Unit program memory. Remedy:
|
| 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:
|
| 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). 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. Remedy:
|
| F01072 Memory card restored from the backup copy | Cause: The Control Unit was switched-off while writing to the memory card. This is why the visible partition became defective. After switching on, the data from the non-visible partition (backup copy) were written to the visible partition. Remedy:
|
| A01073 (N) POWER ON required for backup copy on memory card | Cause: The parameter assignment on the visible partition of the memory card has changed. In order that the backup copy on the memory card is updated on the non-visible partition, it is necessary to carry out a POWER ON or hardware reset (p0972) of the Control Unit. Remedy:
|
| N01101 (A) CU: memory card not available | Cause: The memory card is not available for the drive. Remedy:
|
| F01105 (A) CU: Insufficient memory | Cause: Too many data sets are configured on this Control Unit. Remedy:
|
| F01107 Save to memory card unsuccessful | Cause: A data save to the memory card was not able to be successfully carried out. – Memory card is 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:
|
| F01120 (A) Terminal initialization has failed | Cause: An internal software error occurred while the terminal functions were being initialized. Remedy:
|
| F01122 (A) Frequency at the measuring probe input too high | Cause: The frequency of the pulses at the measuring probe input is too high. Fault value (r0949, interpret decimal): 1: DI 1 (term. 6) 2: DI 3 (term. 8) 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. Remedy:
|
| F01250 CU: CU-EEPROM incorrect read-only data | Cause: Error when reading the read-only data of the EEPROM in the Control Unit. Remedy:
|
| A01251 CU: CU-EEPROM incorrect read-write data | Cause: Error when reading the read-write data of the EEPROM in the Control Unit. Remedy:
|
| 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:
|
| 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. 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:
|
| 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. Remedy:
|
| 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. Remedy:
|
| F01511 (A) BICO: Interconnection with different scalings | Cause: The requested BICO interconnection was established. However, a conversion is made between the BICO output and BICO input using the reference values. – the BICO output has different normalized units than the BICO input. – message only for interconnections within a drive object. Remedy:
|
| F01512 BICO: No scaling available | Cause: An attempt was made to determine a conversion factor for a scaling that does not exist. Remedy:
|
| F01513 (N, A) BICO: Interconnection cross DO with different scalings | Cause: The requested BICO interconnection was established. However, a conversion is made between the BICO output and BICO input using the reference values. An interconnection is made between different drive objects and the BICO output has different normalized units than the BICO input. Remedy:
|
| 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. Remedy:
|
| F01515 (A) BICO: Writing to parameter not permitted as the master control is active | Cause: When changing the number of CDS or when copying from CDS, the master control is active. Remedy:
|
| A01590 (F) Drive: Motor maintenance interval expired | Cause: The selected service/maintenance interval for this motor was reached. Remedy:
|
| F01600 SI P1 (CU): STOP A initiated | Cause: The drive-integrated “Safety Integrated” function on processor 1 has detected an error and initiated a STOP A. – forced checking procedure (test stop) of the safety switch-off signal path on processor 1 unsuccessful. – subsequent response to fault F01611 (defect in a monitoring channel). Fault value (r0949, interpret decimal): 0: Stop request from processor 2. 1005: Pulses suppressed although STO not selected and there is no internal STOP A present. 1010: Pulses enabled although STO is selected or an internal STOP A is present. 1011: Internal fault for the pulse enable in the Power Module. 9999: Subsequent response to fault F01611. Remedy:
|
| 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 data cross-check between the two monitoring channels and has initiated a STOP F. Fault F01600 (SI P1: STOP A initiated) is output as a consequence of this fault. Fault value (r0949, interpret decimal): 0: Stop request from the other monitoring channel. 1…999: Number of the cross-compared data that resulted in this fault. (See r9795). 1000: Watchdog timer has expired. 1001, 1002: Initialization error, change timer / check timer. 2000: Status of the STO selection for both monitoring channels different. 6000…6166: PROFIsafe fault values. Remedy:
|
| N01620 (F, A) SI P1 (CU): Safe Torque Off active | Cause: The “Safe Torque Off” (STO) function has been selected on processor 1 using the input terminal and is active. Note: This message does not result in a safety stop response. Remedy: Not necessary. Note: STO: Safe Torque Off |
| F01625 SI P1 (CU): Sign-of-life error in safety data | Cause: The drive-integrated “Safety Integrated” function on processor 1 has detected an error in the sign-of-life of the safety data and initiated a STOP A.
Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. 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):
Remedy:
Note: In addition to the fault, diagnostics bits r9776.2 and r9776.3 are set. See also: r9776 (SI diagnostics). |
| 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. 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. Fault value (r0949, interpret binary):
Remedy:
See also: r9776 (SI diagnostics) |
| F01649 SI P1 (CU): Internal software error | Cause: An internal error in the Safety Integrated software on processor 1 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 processor 1 requires an acceptance test. Fault value (r0949, interpret decimal):
Remedy: For fault value = 130:
For fault value = 1000:
For fault value = 2000:
For fault value = 2001:
For fault value = 2002:
For fault value = 2003, 2004, 2005:
For fault value = 2020:
For fault value = 9999:
|
| F01651 SI P1 (CU): Synchronization safety time slices unsuccessful | Cause: The “Safety Integrated” function requires synchronization of the safety time slices between processor 1 and processor 2. This synchronization routine was unsuccessful. Note: This fault results in a STOP A that cannot be acknowledged. Remedy: Carry out a POWER ON (switch-off/switch-on). |
| 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. Fault value (r0949, interpret decimal):
Remedy: The following generally applies:
For fault value = 250:
For 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. Alarm value (r2124, interpret decimal):
Remedy:
For alarm value = 1:
For alarm value = 2:
|
| F01655 SI P1 (CU): Align monitoring functions | Cause: An error has occurred when aligning the Safety Integrated monitoring functions on processor 1 and processor 2. No common set of supported SI monitoring functions was able to be determined. – there is a communication error between processor 1 and processor 2 or communication has failed. Note: This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| F01656 SI P1 (CU): Parameter processor 2 error | Cause: When accessing the Safety Integrated parameters for the processor 2 in the non-volatile memory, an error has occurred. Fault value (r0949, interpret decimal):
Remedy:
For fault value = 129:
For fault value = 132:
|
| F01658 SI P1 (CU): PROFIsafe telegram number differ | Cause: The PROFIsafe telegram number in p60022 is unsuitable for the enabled safety functions. Possible causes:
Remedy: Select the telegram number that matches the Safety functions that have been enabled. |
| F01659 SI P1 (CU): Write request for parameter rejected | Cause: The write request for one or several Safety Integrated parameters on processor 1 was rejected. Fault value (r0949, interpret decimal):
Remedy: For fault value = 1:
For fault value = 2:
For fault value = 3:
For fault value = 10, 14, 15, 18:
For fault value = 20:
For fault value = 26:
For fault value = 28:
|
| F01660 SI P1 (CU): Safety-related functions not supported | Cause: The Power Module does not support the safety-related functions. Safety Integrated cannot be commissioned. Remedy: Use a Power Module that supports the safety-related functions. |
| F01662 Error internal communications | Cause: A module-internal communication error has occurred. Remedy:
|
| F01663 SI P1 (CU): Copying the SI parameters rejected | Cause: In p9700, the value 208 is saved or was entered offline. An attempt is made to copy Safety Integrated parameters from processor 1 to processor 2. However, no safety-relevant function has been selected on processor 1 (p9601 = 0). Remedy:
|
| 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):
Remedy:
|
| 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). Fault value:
Remedy: For fault value = 0:
For fault value = 1:
|
| A01693 (F) SI P1 (CU): Safety parameter setting changed, POWER ON required | Cause: Safety parameters have been changed; these will only take effect following a POWER ON. Remedy:
|
| 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. Remedy: Not necessary. |
| A01699 (F) SI P1 (CU): Test stop for STO required | Cause: The time set in p9659 for the forced checking procedure (test stop) for the “STO” function has been exceeded. A new forced checking procedure is required. Remedy: Select STO and then de-select again. |
| A01788 SI: Automatic test stop waits for STO deselection via motion monitoring functions | Cause: The automatic test stop (forced checking procedure) was not able to be carried out after powering up. Possible causes:
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. Alarm value (r2124): 3: Wait for communication to be established to PROFIsafe F-Host. Remedy: If, after a longer period of time, the message is not automatically withdrawn:
|
| F01910 (N, A) Fieldbus: setpoint timeout | Cause: The reception of setpoints from the fieldbus interface has been interrupted.
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: Check the PROFIBUS cables. |
| 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. Remedy:
|
| F01951 CU SYNC: Synchronization application clock cycle missing | Cause: Internal synchronization of the application cycles unsuccessful. Remedy:
|
| A01953 CU SYNC: Synchronization not completed | Cause: After the drive system was switched on, synchronization between the basic clock cycle and application clock cycle was started but was not completed within the selected time tolerance. Remedy: Carry out a POWER ON (switch-off/switch-on). |
| A01991 AS-i: parameter setting inconsistent | Cause: Settings have been made using parameter p2013, which conflict with the setting made via p0015.
Remedy:
Depending on the alarm value perform the remedy (see manual for detailed bit/value mappings for Single/Dual slave). |
| 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:
|
| A02055 Trace: Recording time too short | Cause: The trace duration is too short. The minimum is twice the value of the trace clock cycle. Remedy: Check the selected recording time and, if necessary, adjust. |
| A02056 Trace: Recording cycle too short | Cause: The selected recording clock cycle is lower than the basic clock cycle 500µs. 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. |
| A02059 Trace: Time slice clock cycle for 2 x 8 recording channels not valid | Cause: The selected time slice clock cycle cannot be used for more than 4 recording channels. Remedy: Enter the clock cycle of an existing time slice with a cycle time >= 4 ms or reduce the number of recording channels to 4 per trace. |
| A02060 Trace: Signal to be traced missing | Cause:
Remedy:
|
| A02061 Trace: Invalid signal | Cause:
Remedy:
|
| A02062 Trace: Invalid trigger signal | Cause:
Remedy: Specify a valid trigger signal. |
| A02063 Trace: Invalid data type | Cause: The specified data type to select a signal using a physical address is invalid. Remedy: Use a valid data type. |
| A02070 Trace: Parameter cannot be changed | Cause: The trace parameter settings cannot be changed when the trace is active. Remedy:
|
| A02075 Trace: Pretrigger time too long | Cause: The selected pretrigger time must be shorter than the trace time. Remedy: Check the pretrigger time setting and change if necessary. |
| F02080 Trace: Parameterization deleted due to unit changeover | Cause: The trace parameterization in the drive unit was deleted due to a unit changeover or a change in the reference parameters. Remedy: Restart trace. |
| A02095 MTrace 0: multiple trace cannot be activated | Cause: The following functions or settings are not permissible in conjunction with a multiple trace (trace recorder 0):
Remedy:
|
| 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).
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, etc). 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). (Same causes as A02096). Remedy: (Same remedies as A02096). |
| 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:
|
| A02150 OA: Application cannot be loaded | Cause: The system was not able to load an OA application. Alarm value (r2124): 16: The interface version in the DCB user library is not compatible to the DCC standard library. 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. Remedy:
|
| F03000 NVRAM fault on action | Cause: A fault occurred during execution of action p7770 = 1 or 2 for the NVRAM data. Fault value:
Remedy:
|
| F03001 NVRAM checksum incorrect | Cause: A checksum error occurred when evaluating the non-volatile data (NVRAM) on the Control Unit. The NVRAM data affected was deleted. Remedy: Carry out a POWER ON (switch-off/switch-on) for all components. |
| 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. 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:
|
| A03560 LRC: keyswitch in the off position | Cause: The drive cannot be moved as a result of a local remote control feedback signal. Alarm value:
Remedy: For alarm value = 0:
For alarm value = 5:
For alarm value = 6:
|
| A03561 LRC: keyswitch in the manual operation position | Cause: For local remote control, the keyswitch is in the “Manual operation” position. Remedy: For alarm value = 0:
For alarm value = 1:
|
| 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:
|
| 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:
|
| A05002 (N) Power unit: Air intake overtemperature | Cause: The alarm threshold for the air intake overtemperature has been reached. Remedy: Check the following:
|
| A05004 (N) Power unit: Rectifier overtemperature | Cause: The alarm threshold for the overtemperature of the rectifier has been reached. Remedy: Check the following:
|
| 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. |
| 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) Precharging contactor simultaneity monitoring time exceeded | Cause: A feedback signal for the precharging contactor (ALM, SLM, BLM diode) or the line contactor (BLM thyristor) interconnected and the simultaneity monitoring activated. Remedy:
|
| F05119 (A) Bypass contactor simultaneity monitoring time exceeded | Cause: A feedback signal for the bypass contactor is interconnected and the simultaneity monitoring (p0255[5, 7]) 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. Fault value (r0949, interpret binary): Bit 0 = 1: simultaneity error when closing the contactors. Bit 1 = 1: simultaneity error when opening the contactors. Bit 16 = 1: PDS0 contactor is closed. Bit 17 = 1: PDS1 contactor is closed. Bit 18 = 1: PDS2 contactor is closed. Bit 19 = 1: PDS3 contactor is closed. Bit 20 = 1: PDS4 contactor is closed. Bit 21 = 1: PDS5 contactor is closed. Bit 22 = 1: PDS6 contactor is closed. Bit 23 = 1: PDS7 contactor is closed. Note: PDS: Power unit Data Set 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.8 * p0210 Note: The fault can only be acknowledged when the drive is switched off. See also: p0210 (Drive unit line supply voltage) Remedy:
|
| A06921 (N) Braking resistor phase asymmetry | Cause:
Remedy:
|
| F06922 Braking resistor phase failure | Cause: A phase failure for the brake resistor was detected. Fault value (r0949, interpret decimal): 11: Phase U 12: Phase V 13: Phase W See also: p3235 (Phase failure signal motor monitoring time) Remedy:
|
| F07011 Drive: Motor overtemperature | Cause: KTY84/PT1000: The motor temperature has exceeded the fault threshold (p0605) or the timer (p0606) after the alarm threshold was exceeded (p0604) has expired. The response parameterized in p0610 becomes active. The alarm is withdrawn if the response threshold for wire breakage or sensor not connected is exceeded (R > 2120 Ohm). PTC or bimetallic NC contact: The response threshold of 1650 Ohm was exceeded or the NC contact opened and the timer (p0606) has expired. The response parameterized in p0610 becomes active. Possible causes: – motor is overloaded. – motor ambient temperature too high. – wire breakage or sensor not connected. Fault value (r0949, interpret decimal): 200 (Motor temperature model 1 (I2t): temperature too high). Remedy:
|
| A07012 (N) Drive: Motor temperature model 1/3 overtemperature | Cause: The motor temperature model 1/3 identified that the alarm threshold was exceeded. Hysteresis: 2K. Alarm value (r2124, interpret decimal): 200: Motor temperature model 1 (I2t): temperature too high. 300: Motor temperature model 3: temperature too high. See also: r0034, p0605, p0611, p0612, p0613 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, interpret decimal): 1: All motor temperature models: It is not possible to save the model temperature. See also: p0610 (Motor overtemperature response) Remedy:
|
| A07015 Drive: Motor temperature sensor alarm | Cause: An error was detected when evaluating the temperature sensor set in p0601. With the fault, the time in p0607 is started. If the fault is still present after this time has expired, then fault F07016 is output; however, at the earliest, 50 ms after alarm A07015. Possible causes: – wire breakage or sensor not connected (KTY: R > 2120 Ohm, PT1000: R > 2120 Ohm). – measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm, PT1000: R < 603 Ohm). Remedy:
|
| F07016 Drive: Motor temperature sensor fault | Cause: An error was detected when evaluating the temperature sensor set in p0601. Possible causes: – wire breakage or sensor not connected (KTY: R > 2120 Ohm, PT1000: R > 2120 Ohm). – measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm, PT1000: R < 603 Ohm). Note: If alarm A07015 is present, the time in p0607 is started. If the fault is still present after this time has expired, then fault F07016 is output. Remedy:
|
| F07080 Drive: Incorrect control parameter | Cause: The closed-loop control parameters have been parameterized incorrectly (e.g. p0356 = L_spread = 0). Fault value (r0949, interpret decimal): The fault value includes the parameter number involved. See also: p0310, p0311, p0341, p0344, p0350, p0354, p0356, p0357, p0358, p0360, p0400, p0408, p0640, p1082, p1300 Remedy:
|
| F07082 Macro: Execution not possible | Cause: The macro cannot be executed. Fault value (r0949, interpret hexadecimal): ccccbbaa hex (cccc = preliminary parameter number, bb = supplementary information, aa = fault cause). Fault causes for the trigger parameter itself: 19-23: Called file is not valid for various parameters. 24: Data type of a TAG is incorrect. Fault causes for the parameters to be set: 25-61: Various parameter setting errors (e.g., undefined value, value not “DEFAULT”, trigger recursively called, write permission denied). 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. Fault value (r0949, interpret decimal): Parameter number with which the execution was started. Remedy:
|
| F07084 Macro: Condition for WaitUntil not fulfilled | Cause: The WaitUntil condition set in the macro was not fulfilled in a certain number of attempts. Fault value (r0949, interpret decimal): Parameter number for which the condition was set. 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. The values of the parameters were set to the corresponding violated minimum limit/maximum limit or to the factory setting. Possible causes: The steady-state minimum limit/maximum limit or that defined in the application was violated. Remedy:
|
| F07088 Units changeover: Parameter limit violation due to units changeover | Cause: A changeover of units was initiated. This resulted in a violation of a parameter limit. Possible causes: When rounding off a parameter corresponding to its decimal places, the steady-state minimum limit or maximum limit was violated. Inaccuracies for the data type “FloatingPoint”. Fault value (r0949, interpret decimal): Diagnostics parameter r9451 to display all parameters whose value had to be adapted. 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. See also: p0100 (IEC/NEMA Standards), p0505 (Selecting the system of units) Remedy:
|
| A07092 Drive: moment of inertia estimator still not ready | Cause: The moment of inertia estimator still has no valid values. The acceleration cannot be calculated. The moment of inertia estimator is ready, if the frictional values (p1563, p1564) as well as the moment of inertia value (p1493) have been determined (r1407.26 = 1). Remedy:
|
| A07094 General parameter limit violation | Cause: As a result of the violation of a parameter limit, the parameter value was automatically corrected. Minimum limit violated –> parameter is set to the minimum value. Maximum limit violated –> parameter is set to the maximum value. Alarm value (r2124, interpret decimal): Parameter number, whose value had to be adapted. Remedy:
|
| A07200 Drive: Master control ON command present | Cause: The ON/OFF1 command is present (no 0 signal). The command is either influenced via binector input p0840 (current CDS) or control word bit 0 via the master control. 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 for “master control by PLC” is incorrect (p0854). – the higher-level control has withdrawn the “master control by PLC” signal. – data transfer via the fieldbus (master/drive) was interrupted. Remedy:
|
| F07300 (A) Drive: Line contactor feedback signal missing | Cause:
Remedy:
|
| F07320 Drive: Automatic restart interrupted | Cause:
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:
|
| 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). 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. Possible causes: power ratio, power unit/motor too high. Remedy:
Note: A flying restart at speeds above 3000 rpm should be avoided. |
| A07352 Drive: Stop sensor not plausible | Cause: The stop sensors are not plausible. Possible causes: – BICO interconnections are not OK (p3384, p3385, p3386). – sensors are not supplying a valid signal (both supply a 0 signal or a 1 signal). Remedy:
|
| A07353 Drive: DC quantity control deactivated | Cause: The DC quantity control has deactivated itself. The manipulated variable of the DC quantity control was at its limit. 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 (r1242, r1282). The ramp-down times are automatically increased in order to maintain the DC link voltage (r0070) within the permissible limits. When the DC link voltage controller is switched out (disabled), this is the reason that the ramp-function generator output is set to the speed actual value. Remedy:
|
| A07401 (N) Drive: DC link voltage maximum controller deactivated | 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). – the line supply voltage is permanently higher than specified for the power unit. – the motor is permanently in the regenerative mode as a result of a load that is driving the motor. Remedy:
|
| A07402 (N) Drive: DC link voltage minimum controller active | Cause: The DC link voltage controller has been activated as the lower switch-in threshold has been undershot (r1246, r1286). The kinetic energy of the motor is used to buffer the DC link. The drive is therefore braked. 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 (p1257 or p1297) 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) 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 and motor configuration (star-delta) do not match. – no DC link voltage present. – power unit defective. – the “flying restart” function is not activated. Remedy:
|
| F07411 Drive: Flux setpoint not reached when building up excitation | Cause: When quick magnetizing is configured (p1401.6 = 1) the specified flux setpoint is not reached although 90% of the maximum current is specified. – incorrect motor data. – motor data and configuration do not match. – current limit set too low. – induction motor in I2t limiting. – power unit too small. – magnetizing time too short. Remedy:
|
| A07416 Drive: Flux controller configuration | Cause: The configuration of the flux control (p1401) is contradictory. Fault value (r2124, interpret hexadecimal): ccbbaaaa hex (cc = fault cause). 1: Quick magnetizing (p1401.6) for soft starting (p1401.0). 2: Quick magnetizing for flux build-up control (p1401.2). 3: Quick magnetizing (p1401.6) for Rs identification after restart (p0621 = 2). Remedy:
|
| F07426 (A) Technology controller actual value limited | Cause: The actual value for the technology controller has reached a limit. Fault value (r0949): 1 (upper limit), 2 (lower limit). Remedy:
|
| A07428 (N) Technology controller parameterizing error | Cause: The technology controller has a parameterizing error. Alarm value (r2124): 1 (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 (r1407.1) the ramp-function generator was stopped (p1141). An internal setting command of the ramp-function generator output caused the set setpoint speed to be frozen. Remedy:
|
| A07530 Drive: Drive Data Set DDS not present | Cause: The selected drive data set is not available (p0837 > p0180). Remedy:
|
| A07531 Drive: Command Data Set CDS not present | Cause: The selected command data set is not available (p0836 > p0170). Remedy:
|
| F07754 Drive: Incorrect shutoff valve configuration | Cause: An incorrect shutoff valve configuration was detected. Fault value (r0949, interpret decimal): 100: Enable Safety Integrated, but p0218.0 = 0. 101: Manipulated variable inhibit time less than wait time for feedback (shutoff valve open). 102: Manipulated variable inhibit time less than wait time for feedback (shutoff valve closed). Remedy:
|
| F07800 Drive: No power unit present | Cause: The power unit parameters cannot be read or no parameters are stored in the power unit. 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. – Short-circuit in the motor cable or ground fault. – Motor current does not match current of power unit. – Switch to rotating motor without flying restart function. 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:
|
| 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. 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-3: Short-circuit phase UV, UW, VW. 4: Ground fault with overcurrent. 5-7: Motor cable phase U, V, W interrupted. 8: Short-circuit with hardware shutdown. See also: interchanging line and motor cables, ground fault test. Remedy:
|
| F07810 Drive: Power unit EEPROM without rated data | Cause: No rated data are stored in the power unit EEPROM. Remedy:
|
| A07850 (F) External alarm 1 | Cause: The condition for “External alarm 1” is satisfied. The “External alarm 1” is 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. The “External alarm 2” is 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. The “External alarm 3” is 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. The “External fault 1” is 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. The “External fault 2” is 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. The “External fault 3” is initiated by a 1/0 edge via the following parameters: AND logic operation, binector input p2108, 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. Remedy:
|
| A07892 Drive: Load monitoring pump/fan no load condition | Cause: The monitoring function detects when the pump/fan is operating under no load conditions. The pump is running in the dry state or the fan has a broken belt. Remedy:
|
| A07893 Drive: Load monitoring pump leakage | Cause: The monitoring function detects a leak in the pump circuit. The pump requires a torque that is lower than in normal operation. Remedy:
|
| F07894 Drive: Load monitoring pump/fan blocked | Cause: 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). Remedy:
|
| F07895 Drive: Load monitoring pump/fan no load condition | Cause: The monitoring function detects when the pump/fan is operating under no load conditions. The pump is running in the dry state or the fan has a broken belt. Remedy:
|
| F07896 Drive: Load monitoring pump leakage | Cause: The monitoring function detects a leak in the pump circuit. 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 set in p2175. Can also be triggered if speed is oscillating or by thermal monitoring reducing current limit. 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 setpoint (p2151) and the speed actual value (r2169) exceeds the tolerance threshold (p2163) longer than tolerated (p2164, p2166). Remedy:
|
| A07910 (N) Drive: Motor overtemperature | Cause:
Remedy:
|
| A07920 Drive: Torque/speed too low | Cause: The torque deviates from the torque/speed envelope characteristic (too low) or speed signal deviates from the speed (too low). Remedy:
|
| A07921 Drive: Torque/speed too high | Cause: The torque deviates from the torque/speed envelope characteristic (too high) or speed signal deviates from the speed (too high). Remedy:
|
| A07922 Drive: Torque/speed out of tolerance | Cause: The torque deviates from the torque/speed envelope characteristic or speed signal deviates from the speed. Remedy:
|
| F07923 Drive: Torque/speed too low | Cause: The torque deviates from the torque/speed envelope characteristic (too low) or speed signal deviates from the speed (too low). Remedy:
|
| F07924 Drive: Torque/speed too high | Cause: The torque deviates from the torque/speed envelope characteristic (too high) or speed signal deviates from the speed (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 Alarm value (r2124, interpret decimal): Number of the parameter with the invalid value. 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. 2) DC braking has been activated at binector input p1230 with the DC braking set. 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. Remedy:
|
| F07936 Drive: load failure | Cause: The load monitoring has detected a load failure. Remedy:
|
| 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. Remedy: Compare the motor data with the rating plate data and if required, correct. |
| A07960 Drive: Incorrect friction characteristic | Cause: The friction characteristic is incorrect. Alarm value (r2124, interpret decimal):
Remedy:
|
| A07961 Drive: Friction characteristic record activated | Cause: The automatic friction characteristic record is activated. The friction characteristic is recorded at the next switch-on command. Remedy: Not necessary. The alarm disappears automatically after the friction characteristic record has been successfully completed or deactivated. |
| F07963 Drive: Friction characteristic record interrupted | Cause: The conditions to record the friction characteristic are not fulfilled. Fault value (r0949):
Remedy: Fulfill the conditions to record the friction characteristic. For fault value = 0046: establish missing enable signals. For fault value = 1082…1087: Select the highest speed value to be approached (p3829) less than maximum speed. For fault value = 1110, 1111, 1198: Enable the permitted direction. For fault value = 3845: Activate the friction characteristic record (p3845). |
| F07967 Drive: Incorrect pole position identification | Cause: A fault has occurred during the pole position identification routine. 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):
Remedy: For fault value = 10: Check motor connection, replace power unit, deactivate technique (p1909). For fault value = 12: Check whether motor data is correct, deactivate technique. For fault value = 16: Deactivate technique. For fault value = 17: Repeat technique. |
| F07969 Drive: Incorrect pole position identification | Cause: A fault has occurred during the pole position identification routine. Fault value (r0949):
Remedy: For fault value = 1: Check motor connection/data, replace power unit. For fault value = 2: Bring motor to no-load condition. For fault value = 10, 11: Increase value for p0325/p0329, check motor connection. For fault value = 12: Reduce value for p0325/p0329. For fault value = 20: Ensure motor shaft is absolutely stationary. |
| A07980 Drive: Rotating measurement activated | Cause: The rotating measurement (automatic speed controller optimization) is activated and carried out at next switch-on. Note: During rotating measurement, parameters cannot be saved (p0971). Remedy: Not necessary. The alarm disappears automatically after completion. |
| A07981 Drive: Enable signals for the rotating measurement missing | Cause: The rotating measurement cannot be started due to missing enable signals. Enable signals for ramp-function generator or speed controller integrator missing. Remedy:
|
| F07983 Drive: Rotating measurement saturation characteristic | Cause: A fault has occurred while determining the saturation characteristic. Fault value (r0949):
Remedy: For fault value = 1: De-select rotating measurement, enter moment of inertia p0342, re-calculate speed controller. For fault value = 1…4: Increase measuring speed, check motor parameters. For fault value = 9, 10: Measurement carried out where load torque is too high. Select more suitable operating point. |
| F07984 Drive: Speed controller optimization, moment of inertia | Cause: A fault has occurred while identifying the moment of inertia. Fault value (r0949): 1 (Speed not steady), 2-7 (Setpoint not reached due to limits), 8 (Torque difference too low), 11 (Identified inertia not plausible). Remedy: For fault value = 1: Check motor parameters, moment of inertia. For fault value = 8: Total drive moment of inertia is far higher than that of the motor. For fault value = 11: Reduce moment of inertia (p0341). |
| F07985 Drive: Speed controller optimization (oscillation test) | Cause: A fault has occurred during the vibration test. Fault value (r0949): 1 (Speed not steady), 2-4 (Limits active), 5 (Torque limits too low). Remedy: For fault value = 1: Check motor parameters, moment of inertia, carry out motor data ID. For fault value = 5: Increase torque limits (p1520, p1521). For fault value = 6: Reduce dynamic factor (p1967), disable vibration test. |
| F07986 Drive: Rotating measurement ramp-function generator | Cause: During rotating measurements, problems with the ramp-function generator occurred (e.g. directions inhibited). Remedy: 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). |
| F07990 Drive: Incorrect motor data identification | Cause: A fault has occurred during the identification routine. Fault value (r0949): 1 (Current limit), 2-9 (Resistance/Reactance outside expected range), 10 (Incorrect connection), 11 (Shaft rotates), 12 (Ground fault), 40 (Identification errors). Remedy:
|
| A07991 (N) Drive: Motor data identification activated | Cause: The motor data identification routine is activated and carried out at next switch-on. Remedy: Not necessary. |
| 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. 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, controller switched off/STOP). Remedy:
|
| F08502 (A) PROFINET: Monitoring time sign-of-life expired | Cause: The monitoring time for the sign-of-life counter has expired. Connection interrupted. Remedy:
|
| A08511 (F) PROFINET: Receive configuration data invalid | Cause: The drive unit did not accept the receive configuration data. Alarm value: 2 (Too many PZD data words), 3 (Uneven bytes), 501 (PROFIsafe parameter error), 502 (PROFIsafe telegram mismatch). Remedy:
|
| A08526 (F) PROFINET: No cyclic connection | Cause: There is no connection to a PROFINET controller. Remedy: Establish the cyclic connection and activate the controller. Check “Name of Station” and “IP of Station”. |
| 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. Remedy:
|
| A08565 PROFINET: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration (p8925). Alarm value: 0 (general), 1 (IP config error), 2 (Station name error), 3 (DHCP error). Remedy:
|
| A08800 PROFIenergy energy-saving mode active | Cause: The PROFIenergy energy-saving mode is active. Remedy: The alarm is automatically withdrawn when the energy-saving mode is exited (command received, or higher-level control STOP). |
| 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. Error checking memory card. Fault value: 0 (Not inserted), 1 (Invalid/not Siemens), 12 (OEM input incorrect). 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. Remedy:
|
| F13102 Know-how protection: Consistency error of the protected data | Cause: An error was identified when checking the consistency of the protected files. Project cannot be run. Fault value xxxx: 1 (Checksum error), 2 (Files not consistent), 3 (Project files inconsistent). 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. – power cables not correctly connected or too long. Fault value (r0949): Bit 0 (Phase U), Bit 1 (Phase V), Bit 2 (Phase W), Bit 3 (DC link overcurrent). 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. – DC link voltage controller excessive or insufficient. Remedy:
|
| F30003 Power unit: DC link voltage undervoltage | Cause: The power unit has detected an undervoltage condition in the DC link (line supply failure, phase interrupted). Remedy: Check the line supply voltage and phases. |
| 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. Remedy:
|
| F30005 Power unit: Overload I2t | Cause: The power unit was overloaded (r0036 = 100 %). Permissible rated power unit current exceeded or 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 ruptured. 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. Fault value indicates module slot or specific inverter/rectifier. 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. Remedy: Contact the manufacturer. |
| F30015 (N, A) Power unit: Phase failure motor cable | Cause: A phase failure in the motor feeder cable was detected (0 A measured in one phase). Remedy:
|
| A30016 (N) Power unit: Load supply switched off | Cause: The DC link voltage is too low. Remedy: Under certain circumstances, the AC line supply is not switched on. |
| F30017 Power unit: Hardware current limit has responded too often | Cause: The hardware current limitation has responded too often. – closed-loop control incorrectly parameterized. – fault in motor or cables. – motor load too high. Remedy:
|
| F30021 Power unit: Ground fault | Cause: The power has detected a ground fault in cables, motor, or CT defective. Remedy:
|
| F30022 Power unit: Monitoring U_ce | Cause: Monitoring of the collector-emitter voltage (U_ce) of the semiconductor has responded (short-circuit, defective semiconductor). Remedy: Check the power unit and replace if necessary. |
| 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. Remedy:
|
| F30025 Power unit: Chip overtemperature | Cause: The chip temperature of the semiconductor has exceeded the permissible limit value. – permissible load duty cycle not maintained. – insufficient cooling. 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. 1) There is no line supply voltage connected. 2) The line contactor/line side switch has not been closed. 3) The line supply voltage is too low. 4) Line supply voltage incorrectly set (p0210). 5) The precharging resistors are overheated as there were too many precharging operations per time unit. 6) The precharging resistors are overheated as the DC link capacitance is too high. 7) The DC link has either a ground fault or a short-circuit. 8) Precharging circuit may be defective. Fault value (r0949, interpret binary): yyyyxxxx hex (See manual for detailed bit breakdown). Remedy: In general:
For 5):
For 6):
For 7):
|
| 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:
Notice: This fault can only be acknowledged once the permissible temperature limit minus 5 K has been fallen below. |
| 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:
|
| 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:
|
| 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:
|
| 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:
|
| 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:
|
| 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:
Notice: This fault can only be acknowledged once the permissible temperature limit minus 5 K has been fallen below. |
| 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:
Notice: This fault can only be acknowledged after the alarm threshold for alarm A05004 has been undershot. |
| 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. Alarm value (r2124, interpret binary): Bit 0: heat sink fan will reach the maximum operating time in 500 hours. Bit 1: heat sink fan has exceeded the maximum operating time. Bit 8: internal device fan will reach the maximum operating time in 500 hours. Bit 9: internal device fan has exceeded the maximum operating time. Remedy: For the fan involved, carry out the following:
|
| A30048 Power unit: External fan faulty | Cause: The feedback signal from the external fan indicates a fault. – fan faulty, blocked. – feedback signal inaccurate. 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. Fault value (r0949, interpret decimal): 0, 2, 3, 4: The EEPROM data read in from the power unit module is inconsistent. 1: EEPROM data is not compatible to the firmware of the Control Unit. Remedy:
|
| 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 21.4 V. Remedy:
|
| F30055 Power unit: Braking chopper overcurrent | Cause: An overcurrent condition has occurred in the braking chopper. Remedy:
Note: The braking chopper is only enabled again at pulse enable after the fault has been acknowledged. |
| 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. Alarm value (r2124, interpret bitwise binary): Bit 1: Phase U. Bit 2: Phase V. Bit 3: Phase W. Remedy:
|
| F30068 Power unit: undertemperature inverter heat sink | Cause: The actual inverter heat sink temperature is below the permissible minimum value. Possible causes: – the power unit is being operated at an ambient temperature that lies below the permissible range. – the temperature sensor evaluation is defective. 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. The CU may have been withdrawn or is incorrectly inserted. Remedy: For fault value = 0 and 20A hex:
For fault value = 1 hex:
|
| 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. 0: The output filter initialization was unsuccessful. 1: Activation/deactivation of the regenerative feedback functionality was unsuccessful. 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 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. – power cables are not correctly connected. – power cables exceed the maximum permissible length. – power unit defective. Remedy:
|
| 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. – power cables are not correctly connected. – power cables exceed the maximum permissible length. – power unit defective. Remedy:
|
| 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:
|
| 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:
|
| F30600 SI P2: STOP A initiated | Cause: The drive-integrated “Safety Integrated” function on processor 2 has detected an error and initiated a STOP A. – forced checking procedure (test stop) of the safety switch-off signal path on processor 2 unsuccessful. – subsequent response to fault F30611 (defect in a monitoring channel). Remedy:
|
| 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 data cross-check between the two monitoring channels and has initiated a STOP F. Remedy: For fault values 1 … 999 described in “Cause”:
For fault value = 1000:
For fault value = 1001, 1002:
For fault value = 2000, 2001, 2003:
For fault value = 6000 … 6999:
For fault values that are described in “Cause”:
|
| N30620 (F, A) SI P2: Safe Torque Off active | Cause: The “Safe Torque Off” (STO) function has been selected on processor 2 using the input terminal and is active. Note: This message does not result in a safety stop response. Remedy: Not necessary. |
| F30625 SI P2: Sign-of-life error in safety data | Cause: The drive-integrated “Safety Integrated” function on processor 2 has detected an error in the sign-of-life of the safety data and initiated a STOP A. – there is a communication error between processor 1 and processor 2 or communication has failed. – a time slice overflow of the safety software has occurred. Remedy:
|
| F30649 SI P2: Internal software error | Cause: An internal error in the Safety Integrated software on processor 2 has occurred. Note: This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| F30650 SI P2: Acceptance test required | Cause: The drive-integrated “Safety Integrated” function on processor 2 requires an acceptance test. Note: This fault results in a STOP A that can be acknowledged. Remedy: For fault value = 130:
For fault value = 1000:
For fault value = 2000:
For fault value = 2003:
For fault value = 2010:
For fault value = 9999:
|
| F30651 SI P2: Synchronization with Control Unit unsuccessful | Cause: The drive-integrated “Safety Integrated” function requires synchronization of the safety time slices on processor 1 and processor 2. This synchronization routine was unsuccessful. Note: This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| F30655 SI P2: Align monitoring functions | Cause: An error has occurred when aligning the Safety Integrated monitoring functions on processor 1 and processor 2. No common set of supported SI monitoring functions was able to be determined. – there is a communication error between processor 1 and processor 2 or communication has failed. Note: This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| F30656 SI P2: Parameter processor 2 parameter error | Cause: When accessing the Safety Integrated parameters for the processor 2 in the non-volatile memory, an error has occurred. Note: This fault results in a STOP A that can be acknowledged. 129: Safety parameters for processor 2 corrupted. 131: Internal software error on processor 1. 255: Internal software error on processor 2. Remedy:
For fault value = 129:
|
| F30659 SI P2: Write request for parameter rejected | Cause: The write request for one or several Safety Integrated parameters on processor 2 was rejected. Note: This fault does not result in a safety stop response. Remedy: For fault value = 10, 15, 16, 18:
For fault value = 28:
|
| 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:
|
| 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). Fault value (r0949, interpret hexadecimal): 200000 hex, 400000 hex: fault in the actual booting/operation. Remedy:
For fault value = 400000 hex:
|
| F30682 SI Motion P2: Monitoring function not supported | Cause: The monitoring function enabled in p9301, p9501, p9601 or p9801 is not supported in this firmware version. Note: This message does not result in a safety stop response. Remedy:
|
| A30693 (F) SI P2: Safety parameter settings changed, POWER ON required | Cause: Safety parameters have been changed; these will only take effect following a POWER ON. Notice: All changed parameters of the safety motion monitoring functions will only take effect following a POWER ON. Remedy:
|
| A30788 Automatic test stop: wait for STO deselection via SMM | Cause: The automatic test stop was not able to be carried out after powering up. Possible causes: – the STO function is selected via Safety Extended Functions. – a safety message is present, that resulted in a STO. 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. Fault value (r0949, interpret hexadecimal): 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy:
|
| F30809 Power unit: Switching information not valid | Cause: The last switching status word in the setpoint telegram is identified by the end ID. Such an end ID was not found. Remedy:
|
| A30810 (F) Power unit: Watchdog timer | Cause: When booting it was detected that the cause of the previous reset was an SAC watchdog timer overflow. Remedy:
|
| 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. – internal software error. – module fault. Remedy:
|
| A30920 (F) Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred. 1: Wire breakage or sensor not connected. 2: Measured resistance too low. 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. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Remedy:
|
| F35950 TM: Internal software error | Cause: An internal software error has occurred. Remedy:
|
| A50001 (F) PROFINET configuration error | Cause: A PROFINET controller attempts to establish a connection using an incorrect configuring telegram. The “Shared Device” function has been activated (p8929 = 2). Remedy:
|
| A50010 (F) 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. 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:
|
| A50011 (F) Ethernet/IP: configuration error | Cause: An EtherNet/IP controller attempts to establish a connection using an incorrect configuring telegram. The telegram length set in the controller does not match the parameterization in the drive device. Remedy:
|
| A50020 (F) 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:
|
| F50510 FBLOCKS: Logon of the runtime group rejected | Cause: When the runtime groups of the free function blocks attempted to log on with the sampling time management, the logon of at least one runtime group was rejected. Too many different hardware sampling times may have been assigned to the free function blocks. Remedy:
|
| F50511 FBLOCKS: Memory no longer available for free function blocks | Cause: When the free function blocks were activated, more memory was requested than was available on the Control Unit. Remedy: Not necessary. |
| A50513 (F) FBLOCKS: Run sequence value already assigned | Cause: An attempt was made to assign a run sequence value already assigned to a function block on this drive object to another additional function block on the same drive object. 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 that was downloaded, the hardware sampling time of a free runtime group was set to a value that was either too low or too high. Remedy:
|