Siemens G120P Drive

Siemens G120P 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: carry out a POWER ON (power off/on) for all components. upgrade firmware to later version. contact the Hotline. replace the Control Unit.
F01001 Floating point exception	Cause: A floating point exception has occurred. The error can be caused by the basic system, DCC, FBLOCKS or OA_applications. Remedy: carry out a POWER ON (power off/on) for all components. check configuration and signals of the free function blocks. check configuration and signals of the DCC charts. upgrade firmware to later version. contact the Hotline.
F01002 Internal software error	Cause: An internal software error has occurred. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: carry out a POWER ON (power off/on) for all components. upgrade firmware to later version. contact the Hotline.
F01003 Acknowledgement delay when accessing the memory	Cause: A memory area was accessed that does not return a “READY”. Remedy: carry out a POWER ON (power off/on) for all components. contact the Hotline.
N01004 (F, A) Internal software error	Cause: An internal software error has occurred. Remedy: read out diagnostics parameter (r9999). contact the Hotline. 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 implies specific checksum or length errors. Remedy: save suitable firmware file or EEPROM file for upload or download in folder “/ee_sac/” on the micro 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: check the air intake for the Control Unit. check the fan for the Control Unit (only for CU310). Note: The alarm automatically disappears after the limit value has been undershot.
F01010 Drive type unknown	Cause: An unknown drive type was found. Remedy: Replace Power Module. carry out a POWER ON (power off/on). upgrade firmware to later version. contact the Hotline.
F01015 Internal software error	Cause: An internal software error has occurred. Remedy: carry out a POWER ON (power off/on) for all components. upgrade firmware to later version. contact the Hotline.
A01016 (F) Firmware changed	Cause: At least one firmware file in the directory /SIEMENS/SINAMICS/ has been changed without authorization. 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.
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. Remedy: For the memory card file involved, restore the status originally supplied from the factory.
F01018 Booting has been interrupted several times	Cause: Module booting was interrupted several times (e.g., POWER OFF, CPU crash, USER data invalid). Remedy: Power down the module and power it up again. Note: After switching on, the module reboots from the USER data (if available).
A01019 Writing to the removable data medium unsuccessful	Cause: The write access to the removable data medium was unsuccessful. Remedy: Remove and check the removable data medium. Then run the data backup again.
F01023 Software timeout (internal)	Cause: An internal software timeout has occurred. Remedy: carry out a POWER ON (power off/on) for all components. upgrade firmware to later version. contact the Hotline.
A01028 Configuration error	Cause: The parameterization that was downloaded was generated with a different module type. Remedy: (Check module type and configuration).
F01030 Sign-of-life failure for master control	Cause: For active PC master control, no sign-of-life was received within the monitoring time. Remedy: Set the monitoring time higher at the PC or, if required, completely disable the monitoring function.
A01035 (F) ACX: Boot from the back-up parameter back-up files	Cause: When the Control Unit is booted, no complete data set was found. Instead, a back-up data set was downloaded. Remedy: If you have saved the project using the commissioning software, carry out a new download for your project. Save using the function “Copy RAM to ROM” or with p0971 = 1.
F01036 (A) ACX: Parameter back-up file missing	Cause: When downloading the device parameterization, a parameter back-up file associated with a drive object cannot be found. 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.
F01037 (A) ACX: Re-naming the parameter back-up file unsuccessful	Cause: Re-naming after saving a parameter back-up file in the non-volatile memory was unsuccessful (possibly “read only”). Remedy: check whether one of the files to be overwritten has the attribute “read only” and change to “writable”. replace the memory card or Control Unit.
F01038 (A) ACX: Loading the parameter back-up file unsuccessful	Cause: An error has occurred when downloading PSxxxyyy.ACX or PTxxxyyy.ACX files from non-volatile memory. 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. replace the memory card or Control Unit.
F01039 (A) ACX: Writing to the parameter back-up file was unsuccessful	Cause: Writing to at least one parameter back-up file in the non-volatile memory was unsuccessful (read only, no space, or defective). Remedy: check the file attribute of the files and change from “read only” to “writable”. check the free memory space in the non-volatile memory (Approx 80 kbyte required). replace the memory card or Control Unit.
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: Save parameters (p0971). Switch Control Unit OFF/ON (POWER ON).
F01042 Parameter error during project download	Cause: An error was detected when downloading a project (e.g. incorrect parameter value or limits exceeded). Remedy: enter the correct value in the specified parameter. identify the parameter that restricts the limits of the specified parameter.
F01043 Fatal error at project download	Cause: A fatal error was detected when downloading a project using the commissioning software. Remedy: use the current version of the commissioning software. modify the offline project and download again. change the drive state. carefully note any other messages/signals and remove their cause.
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. Remedy: Restore the factory setting using (p0970 = 1) and re-load the project to the drive unit. After downloading the project, save the parameters in STARTER using “Copy RAM to ROM” or with p0971 = 1.
A01049 It is not possible to write to file	Cause: It is not possible to write into a write-protected file. The write request was interrupted. Remedy: Check whether the “write protected” attribute has been set for the files in the non-volatile memory. When required, remove write protection and save again.
A01064 (F) CU: Internal error (CRC)	Cause: CRC error in the Control Unit program memory. Remedy: carry out a POWER ON (power off/on) for all components. upgrade firmware to later version. contact the Hotline.
A01066 Buffer memory: 70% fill level reached or exceeded	Cause: The non-volatile buffer memory for parameter changes is filled to at least 70%. Remedy: If required, deactivate the buffer memory (p0014 = 0) and clear. If required, clear the buffer memory (p0014 = 2). p0971 = 1 power down/power up the Control Unit
A01067 Buffer memory: 100 % fill level reached	Cause: The non-volatile buffer memory for parameter changes is filled to 100%. Remedy: If required, deactivate the buffer memory (p0014 = 0) and clear. If required, clear the buffer memory (p0014 = 2). p0971 = 1 power down/power up the Control Unit
A01098 RTC: Date and time setting required	Cause: The power supply for the Control Unit was interrupted. The date and time on the real-time clock are no longer accurate. Remedy: Set the date and time on the real-time clock.
F01105 (A) CU: Insufficient memory	Cause: Too many data sets are configured on this Control Unit. 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 (defective, full, or write error). Remedy: try to save again. replace the memory card or Control Unit.
F01112 CU: Power unit not permissible	Cause: The connected power unit cannot be used together with this Control Unit. 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. Remedy: carry out a POWER ON (power off/on) for all components. upgrade firmware to later version. contact the Hotline. replace the Control Unit.
F01122 (A) Frequency at the measuring probe input too high	Cause: The frequency of the pulses at the measuring probe input is too high. Remedy: Reduce the frequency of the pulses at the measuring probe input.
F01205 CU: Time slice overflow	Cause: Insufficient computation time. Remedy: Contact the Hotline.
F01250 CU: CU-EEPROM incorrect read-only data	Cause: Error when reading the read-only data of the EEPROM in the Control Unit. Remedy: carry out a POWER ON. replace the Control Unit.
A01251 CU: CU-EEPROM incorrect read-write data	Cause: Error when reading the read-write data of the EEPROM in the Control Unit. Remedy: For alarm value r2124 < 256: carry out a POWER ON, replace Control Unit. For alarm value r2124 >= 256: clear the fault memory (p0952 = 0), replace the Control Unit.
F01505 (A) BICO: Interconnection cannot be established	Cause: A PROFIdrive telegram has been set. An interconnection contained in the telegram was not able to be established. Remedy: Establish another interconnection.
F01510 BICO: Signal source is not float type	Cause: The requested connector output does not have the correct data type. Remedy: Interconnect this connector input with a connector output having a float data type.
F01511 (A) BICO: Interconnection between different normalizations	Cause: The requested interconnection was established, but a conversion is made between different normalized units. Remedy: No correction needed.
F01512 BICO: No normalization available	Cause: An attempt was made to determine a conversion factor for a normalization that does not exist. Remedy: Apply normalization or check the transfer value.
A01514 (F) BICO: Error when writing during a reconnect	Cause: During a reconnect operation a parameter was not able to be written to. Remedy: None necessary.
F01515 (A) BICO: Writing to parameter not permitted as the master control is active	Cause: While changing the number of CDS or when copying from CDS, the master control was active. Remedy: None necessary.
A01590 (F) Drive: Motor maintenance interval expired	Cause: The selected service/maintenance interval for this motor was reached. Remedy: carry out service/maintenance and reset the service/maintenance interval (p0651).
F01662 Error internal communications	Cause: A module-internal communication error has occurred. Remedy: carry out a POWER ON (power off/on). upgrade firmware to later version. contact the Hotline.
A01900 (F) PROFIBUS: Configuration telegram error	Cause: A PROFIBUS master attempts to establish a connection using an incorrect configuring telegram. Remedy: Check the bus configuration on the master and slave sides.
A01901 (F) PROFIBUS: Parameterizing telegram error	Cause: A PROFIBUS master attempts to establish a connection using an incorrect parameterizing telegram. Remedy: Check the bus configuration: bus addresses, slave configuring.
F01910 (N, A) Fieldbus interface setpoint timeout	Cause: The reception of setpoints from the fieldbus interface has been interrupted. Remedy: Ensure bus connection has been established and switch on communication peer. (Specific remedies for CU230P-2 HVAC/DP available in manual).
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.
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 was aborted. Remedy: check the PROFIBUS cables. check the state of the Publisher that has the aborted connection.
A02150 OA: Application cannot be loaded	Cause: The system was not able to load an OA application. Remedy: carry out a POWER ON (power off/on) for all components. upgrade firmware to later version. contact the Hotline.
F02151 (A) OA: Internal software error	Cause: An internal software error has occurred within an OA application. Remedy: carry out a POWER ON (power off/on) for all components. upgrade firmware to later version. contact the Hotline. replace the Control Unit.
F02152 (A) OA: Insufficient memory	Cause: Too many functions have been configured on this Control Unit. Remedy: change the configuration on this Control Unit (e.g. fewer drives, function modules, data sets). use an additional Control Unit.
F03000 NVRAM fault on action	Cause: A fault occurred during execution of action p7770 = 1, 2 for the NVRAM data. Remedy: (No specific remedy listed in source).
F03001 NVRAM checksum incorrect	Cause: A checksum error occurred when evaluating the non-volatile data (NVRAM). The NVRAM data affected was deleted. Remedy: Carry out a POWER ON (power off/on) for all components.
F03505 (N, A) CU: Analog input wire breakage	Cause: The input current of the analog input has undershot the threshold value. Remedy: Check the connection to the signal source for interruptions. Check the magnitude of the injected current – it is possible that the infed signal is too low.
A03520 (F, N) CU: Temperature sensor fault	Cause: When evaluating the temperature sensor, an error occurred. This message is only output when p0756[2…3] = 6 or 7 is set. Alarm value (r2124, interpret decimal): z = 1: Wire breakage or sensor not connected. z = 2: Measured resistance too low. Remedy: make sure that the sensor is connected correctly. replace the sensor. switch analog input type (p0756) to “no sensor connected” = 8.
F03590 (N, A) TM: Module not ready	Cause: The Terminal Module involved does not send a ready signal and no valid cyclic data. Remedy: check the 24 V power supply. check the DRIVE-CLiQ connection. check whether the sampling time of the drive object involved is not equal to zero (p4099[0]).
A05000 (N) Power unit: Overtemperature heat sink AC inverter	Cause: The alarm threshold for overtemperature at the inverter heat sink has been reached. Remedy: is the ambient temperature within the defined limit values? have the load conditions and the load duty cycle been appropriately dimensioned? has the cooling failed?
A05001 (N) Power unit: Chip overtemperature	Cause: Alarm threshold for overtemperature of the power semiconductor in the AC converter has been reached. Remedy: is the ambient temperature within the defined limit values? have the load conditions and the load duty cycle been appropriately dimensioned? has the cooling failed? pulse frequency too high?
A05002 (N) Power unit: Air intake overtemperature	Cause: For chassis power units: The alarm threshold for the air intake overtemperature has been reached (42 °C). Remedy: is the ambient temperature within the defined limit values? has the fan failed? Check the direction of rotation.
A05003 (N) Power unit: Internal overtemperature	Cause: For chassis power units: The alarm threshold for internal overtemperature has been reached. Remedy: is the ambient temperature within the defined limit values? has the fan failed? Check the direction of rotation.
A05006 (N) Power unit: Overtemperature thermal model	Cause: The temperature difference between the chip and heat sink has exceeded the permissible limit value. Remedy: None necessary. The alarm disappears automatically once the limit value is undershot.
F06310 (A) Supply voltage (p0210) incorrectly parameterized	Cause: The measured DC voltage lies outside the tolerance range after pre-charging has been completed. Remedy: check the parameterized supply voltage and if required change (p0210). check the line supply voltage.
F07011 Drive: Motor overtemperature	Cause: KTY/PTC/Bimetallic: The motor temperature has exceeded the fault threshold or timer has expired. Possible causes: motor overloaded, ambient temperature too high, wire breakage. Remedy: reduce the motor load. check the ambient temperature. check the wiring and sensor connector.
A07012 (N) Drive: I2t motor model overtemperature	Cause: The thermal I2t motor model (for synchronous motors) identified that the temperature alarm threshold was exceeded. Remedy: check the motor load and if required, reduce. check the motor ambient temperature. check the thermal time constant p0611. check the overtemperature fault threshold p0605.
A07015 Drive: Motor temperature sensor alarm	Cause: An error was detected when evaluating the temperature sensor set in p0601 (e.g. wire breakage or resistance too low). Remedy: make sure that the sensor is connected correctly. check the parameterization (p0601).
F07016 Drive: Motor temperature sensor fault	Cause: An error was detected when evaluating the temperature sensor set in p0601 (wire breakage or resistance too low). Remedy: make sure that the sensor is connected correctly. check the parameterization (p0601). induction motors: Deactivate temperature sensor fault (p0607 = 0).
F07080 Drive: Incorrect control parameter	Cause: The closed-loop control parameters have been parameterized incorrectly. Fault value implies specific parameter number. Remedy: Modify the parameter indicated in the fault value (r0949).
F07082 Macro: Execution not possible	Cause: The macro cannot be executed. Fault value indicates preliminary parameter number and cause (e.g. file not valid, data type incorrect, etc.). Remedy: check the parameter involved. check the macro file and BICO interconnection.
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: check whether the file is saved in the appropriate directory on the memory card.
F07084 Macro: Condition for WaitUntil not fulfilled	Cause: The WaitUntil condition set in the macro was not fulfilled in a certain number of attempts. Remedy: Check and correct the conditions for the WaitUntil loop.
A07200 Drive: Master control ON/OFF1 command present	Cause: The ON/OFF1 command is not 0, either via binector input p0840 or in control word bit 0 via the master control. Remedy: Both the signal at binector input p0840 and bit 0 via the master control must be 0.
F07220 (N, A) Drive: Master control by PLC missing	Cause: The “master control by PLC” signal was missing in operation (incorrect interconnection, signal withdrawn, or interrupted). Remedy: check the interconnection of the binector input for “master control by PLC” (p0854). check the “master control by PLC” signal and, if required, switch in. check the data transfer via the fieldbus (master/drive).
F07311 Bypass motor switch	Cause: Fault value: Bit field BYPASS_CONTACTOR_ERROR_STATE (e.g., feedback missing, too slow, inconsistency). Remedy: check the transfer of the feedback signals. check the switch.
F07312 Bypass LSS	Cause: Fault value: Bit field BYPASS_CONTACTOR_ERROR_STATE regarding Line Side Switch (feedback missing, too slow, inconsistency). Remedy: check the transfer of the feedback signals. check the switch.
F07320 Drive: Automatic restart interrupted	Cause: The specified number of restart attempts has been used up, no active ON command, or monitoring time expired. Remedy: increase the number of restart attempts (p1211). increase the delay time in p1212 and/or monitoring time in p1213. issue an ON command (p0840). Reduce the waiting time for resetting the fault counter p1213[1].
A07321 Drive: Automatic restart active	Cause: The automatic restart (AR) is active. Remedy: the automatic restart (AR) should, if required, be inhibited (p1210 = 0). an automatic restart can be directly interrupted by withdrawing the power-on command (BI: p0840).
A07325 Drive: Hibernation active – drive reactivated automatically	Cause: The hibernation function is active (p2398). The drive automatically powers itself up again as soon as restart conditions are present. Remedy: None necessary. The alarm disappears when the motor is restarted automatically or switched off manually.
F07330 Flying restart: Measured search current too low	Cause: During a flying restart, the search current reached is too low. Possible motor not connected. Remedy: Check the motor feeder cables.
F07331 FlyRestart: Not supported	Cause: It is not possible to power up with the motor rotating (no flying restart). E.g., Perm.-magnet synch. motors with V/f char. Remedy: deactivate the “flying restart” function (p1200 = 0).
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. Remedy: increase the ramp-down times. shut down the Vdc_max controller (p1280 = 0). use a chopper or regenerative feedback unit.
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 disabled. Remedy: check whether the input voltage is within the permissible range. check whether the load duty cycle and load limits are within the permissible limits.
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. Remedy: The alarm disappears when power supply returns.
F07405 (N, A) Drive: Kinetic buffering minimum speed not reached	Cause: During kinetic buffering the speed fell below minimum speed and the line supply did not return. Remedy: Check the speed threshold for the Vdc_min controller (kinetic buffering) (p1257, p1297).
F07406 (N, A) Drive: Kinetic buffering maximum time exceeded	Cause: The maximum buffer time has been exceeded without the line supply having returned. Remedy: Check the time threshold for Vdc-min controller (kinetic buffering) (p1255, p1295).
A07409 Drive: V/f control, current limiting controller active	Cause: The current limiting controller of the V/f control was activated because the current limit was exceeded. Remedy: The alarm is automatically withdrawn when increasing the current limit (p0640), reducing the load or using a slower up ramp.
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 (e.g., motor not connected, power unit defective). Remedy: connect the motor or check the motor contactor. check the motor parameterization and connection configuration. check the DC link voltage. activate the “flying restart” function (p1200).
F07411 Drive: Flux controller output limited	Cause: When quick magnetizing is configured, the specified flux setpoint is not reached. Remedy: correct the motor data. Perform motor data identification. correct the current limits (p0640). reduce the induction motor load. increase p0346.
A07416 Drive: Flux controller configuration	Cause: The configuration of the flux control (p1401) is contradictory. Remedy: Re error ID 1: De-energize soft starting or quick magnetizing. Re error ID 3: Re-parameterize Rs identification or de-energize quick magnetizing.
F07426 (A) Technology controller actual value limited	Cause: The actual signal of the technology controller has reached its limit. Remedy: Adapt the limits in P2267, P2268 to the signal level. Scaling of the actual signal.
A07427 Motor staging alarm	Cause: Technology controller is not active or external motor operating time limit exceeded. Remedy: Alarm value = 1: enable technology controller (p2200) or set technology controller mode p2251 = 0. Alarm value = 2: increase p2381, p2382 or set p2380 to zero.
F07435 (N) Drive: Setting the ramp-function generator for encoderless vector control	Cause: During operation with encoderless vector control, the ramp-function generator was stopped (p1141). Remedy: deactivate the holding command for the ramp-function generator (p1141). suppress the fault (p2101, p2119).
F07436 (A) Free technology controller 0 actual value limited	Cause: The actual signal of the free technology controller 0 has reached its limit. Remedy: Adapt the limits in P11067, P11068 to the signal level. Check scaling of the actual signal.
F07437 (A) Free technology controller 1 actual value limited	Cause: The actual signal of the free technology controller 1 has reached its limit. Remedy: Adapt the limits in P11167, P11168 to the signal level. Check scaling of the actual signal.
F07438 (A) Free technology controller 2 actual value limited	Cause: The actual signal of the free technology controller 2 has reached its limit. Remedy: Adapt the limits in P11267, P11268 to the signal level. Check scaling of the actual signal.
A07530 Drive: Drive Data Set DDS not present	Cause: The selected drive data set is not available (p0837 > p0180). Remedy: select the existing drive data set. set up additional drive data sets.
F07800 Drive: No power unit present	Cause: The power unit parameters cannot be read, connection interrupted, or incorrect topology selected. Remedy: connect the data line to power unit and restart the Control Unit (POWER ON). check or replace the Control Unit. check the cable between the Control Unit and Motor Module.
F07801 Drive: Motor overcurrent	Cause: The permissible motor limit current was exceeded (e.g., short circuit, ground fault, incorrect settings). Remedy: check the current limits (p0640). vector control: Check the current controller (p1715, p1717). check the motor and motor cables for short-circuit and ground fault. check the power unit and motor combination.
F07802 Drive: Infeed or power unit not ready	Cause: After an internal power-on command, the infeed or drive does not signal ready. Remedy: increase the monitoring time (p0857). ensure that there is a DC link voltage. replace the associated infeed or drive.
A07805 (N) Drive: Power unit overload I2t	Cause: Alarm threshold for I2t overload (p0294) of the power unit exceeded. Remedy: reduce the continuous load. adapt the load duty cycle. check the assignment of the motor and power unit rated currents.
F07806 Drive: Regenerative power limit exceeded (F3E)	Cause: For blocksize power units (PM250/PM260), the regenerative rated power r0206[2] was exceeded for more than 10 s. Remedy: increase the down ramp. reduce the driving load. use a power unit with a higher regenerative feedback capability.
F07810 Drive: Power unit EEPROM without rated data	Cause: No rated data are stored in the power unit EEPROM. Remedy: Replace the power unit or inform Siemens Customer Service.
A07850 (F) External alarm 1	Cause: The BICO signal for “external alarm 1” was triggered. Remedy: Eliminate the causes of this alarm.
A07851 (F) External alarm 2	Cause: The BICO signal for “external alarm 2” was triggered. Remedy: Eliminate the causes of this alarm.
A07852 (F) External alarm 3	Cause: The BICO signal for “external alarm 3” was triggered. Remedy: Eliminate the causes of this alarm.
F07860 (A) External fault 1	Cause: The BICO signal “external fault 1” was triggered. Remedy: Eliminate the causes of this fault.
F07861 (A) External fault 2	Cause: The BICO signal “external fault 2” was triggered. Remedy: Eliminate the causes of this fault.
F07862 (A) External fault 3	Cause: The BICO signal “external fault 3” was triggered. Remedy: Eliminate the causes of this fault.
F07900 (N, A) Drive: Motor blocked	Cause: Motor has been operating at the torque limit longer than specified time and below speed threshold. Remedy: check that the motor can rotate freely. check the torque limit. check the parameter, message “Motor locked”.
F07901 Drive: Motor overspeed	Cause: The maximum permissible speed was either positively or negatively exceeded. Remedy: check r1084 and if required, correct p1082, CI:p1085 and p2162. Activate pre-control of the speed limiting controller. Increase the hysteresis for the overspeed signal p2162.
F07902 (N, A) Drive: Motor stalled	Cause: For a vector drive 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). 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 carried out (see also p1900, r3925). Check whether the drive stalls solely due to the load in controlled mode or when the speed setpoint is still zero. If yes, then increase the current setpoint using p1610. If the motor excitation time (p0346) was significantly reduced and the drive stalls when it is switched on and run immediately, p0346 should be increased again. Check the current limits (p0640, r0067, r0289). If the current limits are too low, then the drive cannot be magnetized. Check whether a line phase failure is affecting power unit PM230, PM250, PM260. Check whether the motor cables are disconnected. 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 could be: 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 closed-loop torque control, the speed setpoint does not track the speed actual value. for active Vdc controller. For V/f control, the overload condition is detected as the Imax controller is active. See also: p2149 (Monitoring configuration) Remedy: increase p2163 and/or p2166. increase the torque/current/power limits. for closed-loop torque control: The speed setpoint should track the speed actual value. deactivate alarm with p2149.0 = 0.
A07910 (N) Drive: Motor overtemperature	Cause: KTY or no sensor: The measured motor temperature or the temperature of the thermal model 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): 1: No output current reduction. 2: Output current reduction active. See also: p0604, p0610 Remedy: check the motor load. check the motor ambient temperature. check KTY84. check temperatures of the thermal model (p0626 … 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: check the connection between the motor and load. adapt the parameterization corresponding to the load.
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: Check the connection between the motor and load. Adapt the parameterization according to the load.
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: Check the connection between the motor and load. Adapt the parameterization according to the load.
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: Check the connection between the motor and load. Adapt the parameterization according to the load.
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: Check the connection between the motor and load. Adapt the parameterization according to the load.
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: Check the connection between the motor and load. Adapt the parameterization according to the load.
A07926 Drive: Envelope curve, parameter invalid	Cause: Invalid parameter values were entered for the envelope characteristic of the load monitoring. Rules for speed thresholds: p2182 < p2183 < p2184 Rules for torque thresholds: p2185 > p2186, p2187 > p2188, p2189 > p2190 Alarm value (r2124): Number of the parameter with the invalid value. Remedy: Set the parameters for the load monitoring according to the applicable rules or deactivate load monitoring (p2181 = 0; p2193 = 0).
A07927 DC brake active	Cause: The motor is braked with a DC current, the DC current brake is active. 1) An alarm with response DCBRAKE is active. 2) DC braking has been activated at binector input p1230 with the DC brake set (p1230 = 4). Remedy: None necessary.
A07929 (F) Drive: No motor detected	Cause: The absolute current value is so small after enabling the inverter pulses that no motor is detected. See also: p2179 (Output load identification current limit) Remedy: check the motor feeder cables. reduce the threshold value (p2179) (e.g. for synchronous motors). check the voltage boost of the V/f control (p1310). carry out a standstill measurement to set the stator resistance (p0350).
F07936 Drive: load failure	Cause: Load monitoring: load failure detected. Remedy: Check the sensor. Switch out the monitoring (p2193). See also: p2193, p3232
F07937 (N) Drive: Speed deviation between motor model and external speed	Cause: The absolute value of the speed difference from the two actual values (r2169, r1443) exceeds the tolerance threshold (p3236) for longer than the time set in p3238. Possible causes: – External encoder signal wired incorrectly (p1440) – Speed encoder for external encoder signal faulty – Encoder signal’s polarity or gain incorrect – Smoothing time constant for model speed too high or threshold values too low. Remedy: Check that the external speed (see p1440, r1443) matches the motor speed. Check the polarity of the external speed (r1443). Check connector connection p1440.
F07950 (A) Motor parameter incorrect	Cause: – the motor parameters were incorrectly entered while commissioning (e.g. p0300 = 0, no motor) – The braking resistor (p6811) has still not been parameterized. Fault value (r0949): The parameter number involved. Remedy: Compare the motor data with the rating plate data and if required, correct. See also: p0300, p0301, p0304, p0305, p0307, p0310, p0311, p0314, p0316, p0320, p0322, p0323
F07967 Drive: Pole position identification internal fault	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): 10: Ratio between measured current and zero current too low. 12: Max current exceeded. 15: Second harmonic too low. 16: Drive converter too small. 17: Abort due to pulse inhibit. Remedy: Re fault value = 10: Check motor connection. Replace power unit. Deactivate technique (p1909). Re fault value = 12: Check motor data entry. Deactivate technique (p1909). Re fault value = 16: Deactivate technique (p1909). Re 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) indicates specific stage failures (e.g., 10, 11, 12, 13, 14, 15, 16, 17, 18, 20). Remedy: Depends on Fault Value (r0949): Val 1: Check motor connection/data. Replace power unit. Val 2: Bring motor to no-load condition. Val 10: p1980=4 -> Increase p0325. p1980=1 -> Increase p0329. Check connections. Val 11: Increase p0329. Check connections. Val 12: p1980=4 -> Reduce p0325. p1980=1 -> Reduce p0329. Check data. Val 13: Reduce p0329. Check data. Val 14: Increase p0329. Val 15: Increase p0325. Change technique (p1980 = 1 or 10). Val 16: Change technique (p1980). Val 17: Repeat technique. Val 18: Increase p0329. Saturation not sufficient, change technique (p1980=10). Val 20: Ensure motor shaft is absolutely stationary.
A07980 Drive: Rotating measurement activated	Cause: The rotating measurement (automatic speed controller optimization) is activated and will be carried out at the next power-on command. See also: p1960 Remedy: None necessary. The alarm disappears automatically after completion or setting p1900 = 0.
A07981 Drive: Enable signals for the rotating measurement missing	Cause: The rotating measurement cannot be started due to missing enable signals. Remedy: acknowledge faults that are present. establish missing enable signals. See also: r0002, r0046
F07983 Drive: Rotating measurement saturation characteristic	Cause: A fault has occurred while determining the saturation characteristic. Fault value (r0949): 1-10 indicating specific issues (speed not reached, flux issues, timeouts). Remedy: Val 1: Total moment of inertia too high. Deselect p1960, enter inertia p0342 manually, recalculate p0340=4. Val 1..2: Increase measuring speed (p1961), repeat. Val 1..4: Check motor parameters. Calculate p0340=3. Check inertia. Carry out motor data ident (p1910). Val 5: Speed setpoint p1961 too high. Reduce speed. Val 6: Adapt p1961 or minimum limiting (p1080). Val 7: Adapt p1961 or suppression bandwidths. Val 8: Adapt p1961 or maximum limits. Val 9, 10: Load torque too high. Select more suitable operating point. Note: Can be disabled using p1959.1.
F07984 Drive: Speed controller optimization, moment of inertia	Cause: A fault has occurred while identifying the moment of inertia. Fault value (r0949): 1-11 indicating specific convergence or plausibility issues. Remedy: Val 1: Check parameters. Calculate p0340=3. Check inertia. Carry out p1910. Reduce dynamic factor (p1967). Val 2, 5: Adapt speed setpoint (p1965) or min limit (p1080). Val 3, 6: Adapt p1965 or suppression bandwidths. Val 4, 7: Adapt p1965 or max limits. Val 8: Total inertia far higher than motor. Deselect p1960, enter p0342 manually, recalculate p0340=4. Val 9: Check moment of inertia (p0341, p0342). Recalculate p0340=3 or 4. Val 10: Check moment of inertia. Calculate p0340=3. Note: Can be disabled using p1959.2.
F07985 Drive: Speed controller optimization (oscillation test)	Cause: A fault has occurred during the vibration test. Fault value (r0949): 1-6 indicating steady-state issues or limit problems. Remedy: Val 1: Check parameters. Calculate p0340=3. Check inertia. Carry out p1910. Reduce dynamic factor. Val 2: Adapt p1965 or min limit (p1080). Val 3: Adapt p1965 or suppression bandwidths. Val 4: Adapt p1965 or max limits. Val 5: Increase torque limits (p1520, p1521). Val 6: Reduce dynamic factor (p1967). Disable vibration test (p1959.4=0).
F07986 Drive: Rotating measurement ramp-function generator	Cause: During the rotating measurements, problems with the ramp-function generator occurred. Fault value (r0949): 1: The positive and negative directions are inhibited. Remedy: Re 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).
F07990 Drive: Incorrect motor data identification	Cause: A fault has occurred during the identification routine. Fault value (r0949): Values 1-40 indicating out of range resistance, reactance, or leakage values. Remedy: Val 0: Check motor connection. Observe configuration (star-delta). Val 1…40: Check whether motor data have been correctly entered in p0300, p0304 … p0311. Check relationship between motor power rating and power unit (ratio 0.5 to 4). Check configuration (star-delta). Val 4, 7: Check whether inductances are correctly entered in p0233. Check whether motor has been correctly connected (star-delta).
A07991 (N) Drive: Motor data identification activated	Cause: The motor data ident. routine is activated and will be carried out at the next power-on command. Remedy: None necessary. The alarm disappears automatically after completion or setting p1900 = 0.
A07994 (N) Drive: motor data identification not performed	Cause: Motor data identification has not yet been performed with the actual data set. Triggered if data set changes (r0051) and vector control is parameterized. Remedy: Perform motor data identification (see p1900). Return data set. Parameterize V/f control (p1300 < 20).
F08010 (N, A) CU: Analog-to-digital converter	Cause: The analog-to-digital converter on the CU has not supplied any converted data. Remedy: check the power supply. replace the CU.
F08700 (A) CAN: Communications error	Cause: A CAN communications error has occurred. Fault value (r0949): 1: Error counter exceeded BUS OFF value (255). (Short circuit, bad baud rate, bit timing). 2: Master no longer interrogated CAN node status (Guard time error). Remedy: check the bus cable (short circuit, interruption). check the baud rate (p8622). check the bit timing (p8623). check the master. The CAN controller must be manually restarted with p8608 = 1 after resolving the fault.
F08701 CAN: NMT state change	Cause: A CANopen NMT state transition from “operational” to “pre-operational” or “stopped”. Remedy: None necessary. Acknowledge the fault and continue operation.
A08751 CAN: Telegram loss	Cause: The CAN controller has lost a receive message (telegram). Remedy: Reduce the cycle times of the receive messages.
A08752 CAN: Error counter for error passive exceeded	Cause: The error counter for the send or receive telegrams has exceeded the value 127. Remedy: check the bus cable set a higher baud rate (p8622). check the bit timing and if required optimize (p8623).
A08753 CAN: Message buffer overflow	Cause: A message buffer overflow. 1: Non-cyclic send buffer overflow. 2: Non-cyclic receive buffer overflow. 3: Cyclic send buffer overflow. Remedy: Check the bus cable. Set a higher baud rate (p8622). Check bit timing (p8623). For val 2: Reduce cycle times of SDO receive messages. SDO request from master only after SDO feedback.
A08754 CAN: Incorrect communications mode	Cause: In the “operational” mode, an attempt was made to change parameters p8700 … p8737. Remedy: Change to the “pre-operational” or “stopped” mode.
A08755 CAN: Object cannot be mapped	Cause: The CANopen object is not provided for the Process Data Object (PDO) Mapping. Remedy: Use a CANopen object intended for the PDO mapping or enter 0. Note: As long as A08755 is present, the COB-ID cannot be set to valid.
A08756 CAN: Number of mapped bytes exceeded	Cause: The number of bytes of the mapped objects exceeds the telegram size for net data. A max. of 8 bytes is permissible. Remedy: Map fewer objects or objects with a smaller data type.
A08757 CAN: Set COB-ID invalid	Cause: For online operation, the appropriate COB-ID must be set invalid before mapping. Remedy: Set the COB-ID to invalid (e.g., set bit 31 to 1).
A08759 CAN: PDO COB-ID already available	Cause: An existing PDO COB-ID was allocated. Remedy: Select another PDO COB-ID.
F30001 Power unit: Overcurrent	Cause: The power unit has detected an overcurrent condition. – Closed-loop control incorrectly parameterized. – Short-circuit/fault to ground. – V/f operation: Up ramp too low or rated current too high. – Line supply voltage interruptions or phase interrupted. – Power unit defective. Remedy: check the motor data – if required, carry out commissioning. check the motor circuit configuration (star-delta). V/f operation: Increase up ramp. Check assignment of rated currents. check the line supply quality. Reduce motor load. Correct connection of line reactor. check power cables for short-circuit or ground fault. replace power unit.
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. – DC-link voltage controller excessive or insufficient. Remedy: increase the ramp-down time (p1121). set the rounding times (p1130, p1136). Activate the DC link voltage controller (p1240, p1280). adapt the dynamic response of the DC-link voltage controller. Check the line connection voltage (p0210). check the line supply phases.
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: check the line supply voltage check the line supply 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. – pulse frequency too high. Remedy: check whether the fan is running. check the fan elements. check whether the ambient temperature is in the permissible range. check the motor load. reduce the pulse frequency if this is higher than the rated pulse frequency.
F30005 Power unit: Overload I2t	Cause: The power unit was overloaded (r0036 = 100 %). – permissible rated power unit current exceeded for too long. – permissible load duty cycle not maintained. Remedy: reduce the continuous load. adapt the load duty cycle. check the motor and power unit rated currents. Reduce the current limit p0640.
F30006 Power unit: Thyristor Control Board	Cause: The Thyristor Control Board (TCB) of the Basic Line Module signals a fault. – no line supply voltage or line contactor not closed. – DC link short-circuit. – voltage supply for TCB out of range. – internal fault in TCB. Remedy: check the line supply voltage. check or energize the line contactor. check the monitoring time (p0857). check the DC link regarding short-circuit or ground fault. evaluate diagnostic LEDs for the Thyristor Control Board.
F30011 Power unit: Line phase failure in main circuit	Cause: A line phase failure was detected at the power unit. – fuse ruptured. – DC link voltage ripple exceeded limit. Remedy: check the main circuit fuses. check the motor feeder cables.
F30012 Power unit: Temperature sensor heat sink wire breakage	Cause: The connection to one of the heat sink temperature sensors in the power unit is interrupted. Fault value indicates specific sensor (Air intake, 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. Fault value indicates specific sensor. Remedy: Contact the manufacturer.
F30015 Power unit: Phase failure motor feeder cable	Cause: A phase failure was detected at the power unit output (motor feeder cable). Remedy: 1. Check the motor feeder cables. 2. If the drive has stalled in V/f control, the acceleration or deceleration time (p1120) should be increased.
A30016 (N) Power unit: Load supply switched out	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 in the relevant phase has responded too often. The number of times the limit has been exceeded depends on the design and type of power unit. – closed-loop control is incorrectly parameterized. – fault in the motor or in the power cables. – the power cables exceed the maximum permissible length. – motor load too high. – power unit defective. Remedy: check the motor data. check the motor circuit configuration (star-delta). check the motor load. check the power cable connections. check the power cables for short-circuit or ground fault. check the length of the power cables. replace power unit.
F30021 Power unit: Ground fault	Cause: Power unit has detected a ground fault. – ground fault in the power cables. – winding fault or ground fault at the motor. – CT defective. – when the brake is applied, this causes the hardware DC current monitoring to respond. Fault value (r0949): Absolute value, summation current. Remedy: check the power cable connections. check the motor. check the CT. check the cables and contacts of the brake connection (a wire is possibly broken). See also: p0287
F30022 Power unit: Monitoring V_ce	Cause: In the power unit, the monitoring of the collector-emitter voltage (V_ce) of the semiconductor has responded. Possible causes: – fiber-optic cable interrupted. – power supply of the IGBT gating module missing. – short-circuit at the power unit output. – defective semiconductor in the power unit. Remedy: check the fiber-optic cable and if required, replace. check the power supply of the IGBT gating module (24 V). check the power cable connections. select the defective semiconductor and replace.
F30024 Power unit: Overtemperature thermal model	Cause: The temperature difference between the heat sink and chip has exceeded the permissible limit value. – the permissible load duty cycle was not maintained. – insufficient cooling, fan failure. – overload. – ambient temperature too high. – pulse frequency too high. Remedy: adapt the load duty cycle. check whether the fan is running. check the fan elements. check whether the ambient temperature is in the permissible range. check the motor load. reduce the pulse frequency if this is higher than the rated pulse frequency. if DC brake is active: reduce braking current (see p1232).
F30025 Power unit: Chip overtemperature	Cause: Chip temperature of the semiconductor has exceeded the permissible limit value. – the permissible load duty cycle was not maintained. – insufficient cooling, fan failure. – overload. – ambient temperature too high. – pulse frequency too high. Remedy: adapt the load duty cycle. check whether the fan is running. check the fan elements. check whether the ambient temperature is in the permissible range. check the motor load. reduce the pulse frequency if this is higher than the rated pulse frequency.
F30027 Power unit: Precharging DC link time monitoring	Cause: The power unit DC link was not able to be pre-charged within the expected time. 1) No line supply voltage connected. 2) Line contactor not closed. 3) Line supply voltage too low. 4) Line supply voltage incorrectly set (p0210). 5) Pre-charging resistors overheated (too many operations). 6) Pre-charging resistors overheated (capacitance too high). 7) DC link ground fault or short-circuit. 8) Pre-charging circuit defective. Remedy: In general: Check line supply voltage, input terminals, and p0210. Wait for resistors to cool. Re 5): Carefully observe the permissible pre-charging frequency. Re 6): Check capacitance of DC link; reduce if necessary. Re 7): Check the DC link for a ground fault or short circuit.
A30031 Power unit: Hardware current limiting, 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. – power cables exceed max length. – motor load too high. – power unit defective. Remedy: check the motor data. check the motor circuit configuration (star-delta). check the motor load. check the power cable connections. check the power cables for short-circuit or ground fault. check the length of the power cables.
A30032 Power unit: Hardware current limiting, phase V	Cause: Hardware current limit for phase V responded. The pulsing in this phase is inhibited for one pulse period. Remedy: check the motor data. check the motor circuit configuration (star-delta). check the motor load. check the power cable connections. check the power cables for short-circuit or ground fault. check the length of the power cables.
A30033 Power unit: Hardware current limiting, phase W	Cause: Hardware current limit for phase W responded. The pulsing in this phase is inhibited for one pulse period. Remedy: check the motor data. check the motor circuit configuration (star-delta). check the motor load. check the power cable connections. check the power cables for short-circuit or ground fault. check the length of the power cables.
A30034 Power unit: Internal overtemperature	Cause: The alarm threshold for internal overtemperature has been reached. If the temperature continues to increase, fault F30036 may be triggered. – ambient temperature might be too high. – insufficient cooling, fan failure. Remedy: check the ambient temperature. check the fan for the inside of the unit.
F30035 Power unit: Air intake overtemperature	Cause: The air intake in the power unit has exceeded the permissible temperature limit (55 °C for air-cooled). – ambient temperature too high. – insufficient cooling, fan failure. Remedy: check whether the fan is running. check the fan elements. check whether the ambient temperature is in the permissible range.
F30036 Power unit: Internal overtemperature	Cause: The temperature inside the drive converter has exceeded the permissible temperature limit. – insufficient cooling, fan failure. – overload. – ambient temperature too high. Remedy: check whether the fan is running. check the fan elements. check whether the ambient temperature is in the permissible range.
F30037 Power unit: Rectifier overtemperature	Cause: The temperature in the rectifier of the power unit has exceeded the permissible temperature limit. – insufficient cooling, fan failure. – overload. – ambient temperature too high. – line supply phase failure. Remedy: check whether the fan is running. check the fan elements. check whether the ambient temperature is in the permissible range. check the motor load. check the line supply phases.
A30042 Power unit: Fan operating time reached or exceeded	Cause: The maximum operating time of the fan in the power unit is set in p0252. 0: Max time is 500 hours. 1: Max time exceeded. Remedy: Replace the fan in the power unit and reset the operating hours counter to 0 (p0251 = 0).
A30046 (F) Power unit: Undervoltage, alarm	Cause: Before the last restart, a problem occurred at the power unit power supply. The voltage monitor in the internal FPGA signals an undervoltage fault. Remedy: check the 24 V DC voltage supply to power unit. carry out a POWER ON for the component. replace the module if necessary.
A30048 Power unit: External fan faulty	Cause: The feedback signal from the external fan indicates a fault. – fan faulty, blocked. – feedback signal inaccurate. Remedy: check the external fan and replace if necessary. if using an external fan with feedback, check its wiring (X12.2 or X13.2). if using external fan without feedback, check that the feedback terminal wiring is connected to ground.
A30049 Power unit: Internal fan faulty	Cause: The internal fan has failed. Remedy: Check the internal fan and replace if necessary.
F30052 EEPROM data error	Cause: EEPROM data error of the power unit module. 0: Data inconsistent. 1: Data not compatible with CU firmware. Remedy: Replace power unit module.
F30053 FPGA data faulty	Cause: Power unit module FPGA data error. Remedy: Replace the power unit module or update the FPGA data.
F30060 (A) Pre-charge contactor monitoring	Cause: At the end of the monitoring time (p0255[0]), the actual state of the pre-charge contactor does not match the desired state. Remedy: check the monitoring time setting p0255[0]. check the contactor wiring and activation. replace the contactor.
F30061 (A) Bridging contactor monitoring	Cause: At the end of the monitoring time (p0255[1]), the actual state of the bridging contactor does not match the desired state. Remedy: check the monitoring time setting p0255[1]. check the contactor wiring and activation. replace the contactor.
F30062 (N, A) Bypass contactor has been opened under current	Cause: The bypass contactor for the infeed has been damaged due to (multiple) opening under current. Remedy: Damaged infeeds must be replaced, to prevent serious damage to the entire converter line-up.
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: Check the interface (adjustment and locking) to the power unit module.
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: Check the interface (adjustment and locking) to the power unit module.
F30074 Communication error to the Power Module	Cause: Communication is not possible with the power unit module via the plug connection. Remedy: Either replace the Control Unit or the power unit.
F30080 Power unit: Current increasing too quickly	Cause: The power unit has detected an excessive rate of rise in the overvoltage range. – closed-loop control is incorrectly parameterized. – short-circuit or fault to ground. – infeed: High discharge/post-charging currents. – power cables not correctly connected or too long. – power unit defective. Remedy: check the motor data. check the motor circuit configuration (star-delta). V/f operation: Increase up ramp. infeed: Check line supply quality. Reduce motor load. Correct connection of line reactor. check power cable connections and length. check for short-circuit or ground fault. replace power unit.
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. – V/f operation: Up ramp set too low. – infeed: High discharge/post-charging currents. – power cables not correctly connected or too long. Remedy: check the motor data. check the motor circuit configuration (star-delta). V/f operation: Increase up ramp. Check assignment of rated currents. infeed: Check line supply quality. Reduce motor load. Correct connection of line reactor. check power cable connections and length. check for short-circuit or ground fault. replace power unit.
F30105 PU: Actual value sensing fault	Cause: At least one incorrect actual value channel was detected on the Power Stack Adapter (PSA). Remedy: Evaluate the diagnostic parameters. If the actual value channel is incorrect, check the components and if required, replace.
A30502 Power unit: DC link voltage, overvoltage	Cause: The power unit has detected overvoltage in the DC link on a pulse inhibit. – device connection voltage too high. – line reactor incorrectly dimensioned. Remedy: check the device supply voltage (p0210). check the dimensioning of the line reactor.
F30662 Error in internal communications	Cause: A module-internal communication error has occurred. Remedy: carry out a POWER ON (power off/on). upgrade firmware to later version. contact the Hotline.
F30664 Error while booting	Cause: An error has occurred during booting. Remedy: carry out a POWER ON (power off/on). upgrade firmware to later version. contact the Hotline.
N30800 (F) Power unit: Group signal	Cause: The power unit has detected at least one fault. Remedy: Evaluates other actual messages.
F30802 Power unit: Time slice overflow	Cause: Time slide overflow. Remedy: carry out a POWER ON (power off/on) for all components. upgrade firmware to later version. contact the Hotline.
A30804 (F) Power unit: CRC	Cause: CRC error actuator. Remedy: carry out a POWER ON (power off/on) for all components. upgrade firmware to later version. contact the Hotline.
F30805 Power unit: EPROM checksum error	Cause: Internal parameter data is corrupted. 01: EEPROM access error. 02: Too many blocks in the EEPROM. Remedy: Replace the module.
F30809 Power unit: Switching information not valid	Cause: For 3P gating unit: The last switching status word in the setpoint telegram is identified by the end ID. Such an end ID was not found. Remedy: carry out a POWER ON. upgrade firmware to later version. contact the Hotline.
A30810 (F) Power unit: Watchdog timer	Cause: When booting it was detected that the cause of the previous reset was an SAC watchdog timer overflow. Remedy: carry out a POWER ON. upgrade firmware to later version. contact the Hotline.
F30850 Power unit: Internal software error	Cause: An internal software error has occurred in the power unit. Remedy: replace power unit. if required, upgrade the firmware in the power unit. contact the Hotline.
F30899 (N, A) Power unit: Unknown fault	Cause: A fault occurred on the power unit that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Remedy: replace the firmware on the power unit by an older firmware version (r0128). upgrade the firmware on the Control Unit (r0018).
F30903 Power unit: I2C bus error occurred	Cause: Communications error with an EEPROM or A/D converter. Fault value indicates internal software error or module fault. Remedy: Re fault value = 80000000 hex: upgrade firmware to later version. Re fault value = 00000001 … 0000FFFF hex: replace the module.
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: make sure that the sensor is connected correctly. replace the sensor.
A30999 (F, N) Power unit: Unknown alarm	Cause: An alarm occurred on the power unit that cannot be interpreted by the Control Unit firmware. Remedy: replace the firmware on the power unit by an older firmware version (r0128). upgrade the firmware on the Control Unit (r0018).
F50510 FBLOCKS: Logon of the run-time group rejected	Cause: When the run-time groups of the free function blocks attempted to log on with the internal interface, the logon of at least one run-time group was rejected. Remedy: Check number of available hardware sampling times (T_sample < 8 ms) (r7903).
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: None
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. Remedy: Set another value that is still available on this drive object for the run sequence.
A50517 FBLOCKS: Int. meas. active	Cause: A Siemens internal measurement has been activated. Remedy: Carry out a POWER ON (power off/on) for the Control Unit involved.