Siemens V70 Drive

Siemens V70 Drive Fault Codes:

Fault Code and Meaning	Cause and Remedy
F1000 Internal software error Reaction: OFF2 Acknowledgement: POWER ON	Cause: An internal software error has occurred. Remedy: Evaluate fault buffer. Carry out a POWER ON (power off/on) for all components. Upgrade firmware to later version. Contact the Hotline. Replace the Control Unit.
F1001 Floating Point exception Reaction: OFF2 Acknowledgement: POWER ON	Cause: An exception occurred during an operation with the Floating Point data type. Remedy: Carry out a POWER ON (power off/on) for all components. Upgrade firmware to later version. Contact the Hotline.
F1002 Internal software error Reaction: OFF2 Acknowledgement: IMMEDIATELY	Cause: An internal software error has occurred. Remedy: Carry out a POWER ON (power off/on) for all components. Upgrade firmware to the latest version. Contact the Hotline.
F1003 Acknowledgement delay when accessing the memory Reaction: OFF2 Acknowledgement: IMMEDIATELY	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.
F1015 Internal software error Reaction: OFF2 Acknowledgement: POWER ON	Cause: An internal software error has occurred. Remedy: Carry out a POWER ON (power off/on) for all components. Upgrade firmware to the latest version. Contact the Hotline.
F1018 Booting has been interrupted several times Reaction: NONE Acknowledgement: POWER ON	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. After this fault is output, then the module is booted with the factory settings. Remedy: Carry out a POWER ON (power off/on). After switching on, the module reboots from the valid parameterization (if available). Restore the valid parameterization. Examples: Carry out a first commissioning, save, carry out a POWER ON (switch-off/switch-on). Load another valid parameter backup (e.g. from the memory card), save, carry out a POWER ON (switch-off/switch-on). Note: If the fault situation is repeated, then this fault is again output after several interrupted boots.
F1030 Sign-of-life failure for master control Reaction: OFF3 Acknowledgement: IMMEDIATELY	Cause: For active PC master control, no sign-of-life was received within the monitoring time. Remedy: Contact the Hotline.
F1611 SI CU: Defect detected Reaction: OFF2 Acknowledgement: IMMEDIATELY	Cause: The drive-integrated “Safety Integrated” (SI) function on the Control Unit (CU) has detected an error and initiated an STO. Remedy: Carry out a POWER ON (power off/on) for all components. Upgrade software. Replace the Control Unit.
F1910 Drive Bus: Setpoint timeout Reaction: OFF3 Acknowledgement: IMMEDIATELY	Cause: The reception of setpoints from the Drive Bus interface has been interrupted. Bus connection interrupted. Controller switched off. Controller set into the STOP state. Remedy: Restore the bus connection and set the controller to RUN.
F1911 Drive Bus clock cycle synchronous operation clock cycle failure Reaction: OFF1 Acknowledgement: IMMEDIATELY	Cause: The global control telegram to synchronize the clock cycles has failed – in cyclic operation – for several Drive Bus clock cycles or has violated the time grid specified in the parameterizing telegram over several consecutive Drive Bus clock cycles. Remedy: Check the physical bus configuration (cable, connector, Drive Bus terminator, shielding, etc.). Check whether communication was briefly or permanently interrupted. Check the bus and controller for utilization level (e.g. bus cycle time was set too short).
F1912 Clock cycle synchronous operation sign-of-life failure Reaction: OFF1 Acknowledgement: IMMEDIATELY	Cause: The maximum permissible number of errors in the controller sign-of-life (clock synchronous operation) has been exceeded in cyclic operation. Remedy: Physically check the bus (cables, connectors, terminating resistor, shielding, etc.). Correct the interconnection of the controller sign-of-life. Check whether the controller correctly sends the sign-of-life. Check the permissible telegram failure rate. Check the bus and controller for utilization level (e.g. bus cycle time was set too short).
F7011 Motor overtemperature Reaction: OFF2 Acknowledgement: IMMEDIATELY	Cause: Motor overloaded Motor ambient temperature too high Wire breakage or sensor not connected Motor temperature model incorrectly parameterized Remedy: Reduce the motor load. Check the ambient temperature and the motor ventilation. Check the wiring and the connection. Check the motor temperature model parameters.
F7085 Open-loop/closed-loop control parameters changed Reaction: NONE Acknowledgement: IMMEDIATELY	Cause: Open-loop/closed-loop control parameters have had to be changed for the following reasons: As a result of other parameters, they have exceeded the dynamic limits. They cannot be used due to the fact that the hardware detected not having certain features. Remedy: It is not necessary to change the parameters as they have already been correctly limited.
F7403 Lower DC link voltage threshold reached Reaction: OFF1 Acknowledgement: IMMEDIATELY	Cause: The DC link voltage monitoring is active and the lower DC link voltage threshold was reached in the “Operation” state. Remedy: Check the line supply voltage. Check the infeed. Reduce the lower DC link threshold. Switch out (disable) the DC link voltage monitoring.
F7404 Upper DC link voltage threshold reached Reaction: OFF2 Acknowledgement: IMMEDIATELY	Cause: The DC link voltage monitoring is active and the upper DC link voltage threshold was reached in the “Operation” state. Remedy: Check the line supply voltage. Check the infeed module or the brake module. Increase the upper DC link voltage threshold. Switch out (disable) the DC link voltage monitoring.
F7410 Current controller output limited Reaction: OFF2 Acknowledgement: IMMEDIATELY	Cause: The condition “I_act = 0 and Uq_set_1 longer than 16 ms at its limit” is present and can be caused by the following: Motor not connected or motor contactor open. No DC link voltage present. Motor Module defective. Remedy: Connect the motor or check the motor contactor. Check the DC link voltage. Check the Motor Module.
F7412 Commutation angle incorrect (motor model)	Cause: An incorrect commutation angle was detected that can result in a positive coupling in the speed controller. Possible causes: The motor encoder is incorrectly adjusted with respect to the magnet position. The motor encoder is damaged. Data to calculate the motor model has been incorrectly set. Pole position identification might have calculated an incorrect value when activated. The motor encoder speed signal is faulted. The control loop is unstable due to incorrect parameterization. Remedy: If the encoder mounting was changed, re-adjust the encoder. Replace the defective motor encoder. Correctly set the motor stator resistance, cable resistance and motor-stator leakage inductance. Calculate cable resistance from cross-section/length. Check inductance/stator resistance using motor data sheet. Measure stator resistance (e.g. multimeter). With pole position identification activated, check the procedure and force a new identification procedure by means of deselection followed by selection.
F7414 Encoder serial number changed	Cause: The encoder was replaced. A third-party, build-in or linear motor was re-commissioned. The motor with integrated and adjusted encoder was replaced. The firmware was updated to a version that checks the encoder serial number. Remedy: Re causes 1, 2: Carry out an automatic adjustment using the pole position identification routine. Acknowledge the fault. Initiate the pole position identification routine. Check that the pole position identification routine is correctly executed. SERVO: If a pole position identification technique is selected, and if p0301 does not contain a motor type with an encoder adjusted in the factory, then p1990 is automatically activated. Mechanically adjust the encoder. Accept the new serial number. Re causes 3, 4: Accept the new serial number with p0440 = 1.
F7420 Drive: Current setpoint filter natural frequency > Shannon frequency	Cause: One of the filter natural frequencies is greater than the Shannon frequency (2KHz). Filter 1 (p1658, p1660) Filter 2 (p1663, p1665) Filter 3 (p1668, p1670) Filter 4 (p1673, p1675) Remedy: Reduce the numerator or denominator natural frequency of the current setpoint filter involved at the control system side. Switch out the filter involved (p1656).
F7450 Standstill monitoring has responded	Cause: After the standstill monitoring time expired, the drive left the standstill window. Position loop gain too low. Position loop gain too high (instability/oscillation). Mechanical overload. Connecting cable, motor/drive converter incorrect (phase missing, interchange). Remedy: Check the causes and resolve.
F7452 Following error too high	Cause: The difference between the position setpoint position actual value (following error dynamic model) is greater than the tolerance. The drive torque or accelerating capacity exceeded. Position measuring system fault. Position control sense incorrect. Mechanical system locked. Excessively high traversing velocity or excessively high position reference value (setpoint) differences. Remedy: Check the causes and resolve.
F7801 Motor overcurrent	Cause: The permissible motor limit current was exceeded. Effective current limit set too low. Current controller not correctly set. Motor was braked with an excessively high stall torque correction factor. 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 the current of Motor Module. Remedy: Reduce the stall torque correction factor. Increase the up ramp or reduce the load. Check the motor and motor cables for short-circuit and ground fault. Check the Motor Module and motor combination.
F7802 Infeed or power unit not ready	Cause: After an internal power-on command, the infeed or drive does not signal ready because of one of the following reasons: Monitoring time is too short. DC link voltage is not present. Associated infeed or drive of the signaling component is defective. Remedy: Ensure that there is a DC link voltage. Check the DC link busbar. Enable the infeed. Replace the associated infeed or drive of the signaling component.
F7815 Power unit has been changed	Cause: The code number of the actual power unit does not match the saved number. Remedy: Connect the original power unit and power up the Control Unit again (POWER ON).
F7900 Motor blocked/speed controller at its limit	Cause: The servo motor has been operating at the torque limit longer than 1s and below the speed threshold of 120 rpm. This signal can also be initiated if the speed actual value is oscillating and the speed controller output repeatedly goes to its limit. Remedy: Check whether the servo motor can rotate freely or not. Check the torque limit. Check the inversion of the actual value. Check the motor encoder connection. Check the encoder pulse number.
F7901 Motor overspeed	Cause: The maximum permissible speed has been exceeded. Remedy: Check and correct the maximum speed (p1082).
F7995 Pole position identification not successful	Cause: The pole position identification routine was unsuccessful. Remedy: Contact the Hotline.
F30001 Power unit: Overcurrent	Cause: The power unit has detected an overcurrent condition. Closed-loop control is incorrectly parameterized. Motor has a short-circuit or fault to ground (frame). Power cables are not correctly connected. Power cables exceed the maximum permissible length. Power unit defective. Line phase interrupted. Remedy: Check the motor data – if required, carry out commissioning. Check the motor circuit configuration (star-delta). Check the power cable connections. Check the power cables for short-circuit or ground fault. Check the length of the power cables. Replace power unit. Check the line supply phases. Check the external braking resistor connection.
F30002 DC link voltage, overvoltage	Cause: The power unit has detected overvoltage in the DC link. Motor regenerates too much energy. Device connection voltage too high. Line phase interrupted. Remedy: Increase the ramp-down time. Activate the DC link voltage controller. Use a braking resistor. Increase the current limit of the infeed or use a larger module. Check the device supply voltage. Check the line supply phases.
F30003 DC link voltage, undervoltage	Cause: The power unit has detected an undervoltage condition in the DC link. Line supply failure. Line supply voltage below the permissible value. Line supply infeed failed or interrupted. Line phase interrupted. Remedy: Check the line supply voltage. Check the line supply infeed and observe the fault messages relating to it (if there are any). Check the line supply phases. Check the line supply voltage setting.
F30004 Drive heat sink overtemperature	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. The permissible rated power unit current was exceeded for an inadmissibly long time. The permissible load duty cycle was not maintained. Remedy: Reduce the continuous load. Adapt the load duty cycle. Check the motor and power unit rated currents.
F30011 Line phase failure in main circuit	Cause: At the power unit, the DC link voltage ripple has exceeded the permissible limit value. Possible causes: A line phase has failed. The 3 line phases are inadmissibly unsymmetrical. The fuse of a phase of a main circuit has ruptured. A motor phase has failed. Remedy: Check the main circuit fuses. Check whether a single-phase load is distorting the line voltages. Check the motor feeder cables.
F30015 Phase failure motor cable	Cause: A phase failure in the motor feeder cable was detected. The signal can also be output in the following case: The motor is correctly connected, however the closed-speed control is instable and therefore an oscillating torque is generated. Remedy: Check the motor feeder cables. Check the speed controller settings.
F30021 Ground fault	Cause: Power unit has detected a ground fault. Ground fault in the power cables. Winding fault or ground fault at the motor. Remedy: Check the power cable connections. Check the motor.
F30027 Precharging DC link time monitoring	Cause: The power unit DC link was not able to be pre-charged within the expected time. There is no line supply voltage connected. The line contactor/line side switch has not been closed. The line supply voltage is too low. The pre-charging resistors are overheated as there were too many pre-charging operations per time unit. The pre-charging resistors are overheated as the DC link capacitance is too high. The pre-charging resistors are overheated. The pre-charging resistors are overheated as the line contactor was closed during the DC link fast discharge through the Braking Module. The DC link has either a ground fault or a short-circuit. The pre-charging circuit is possibly defective. Remedy: Check the line supply voltage at the input terminals.
F30036 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. Notice: This fault can only be acknowledged once the permissible temperature limit minus 5 K has been fallen below.
F30050 24 V supply overvoltage	Cause: The voltage monitor signals an overvoltage fault on the module. Remedy: Check the 24 V power supply. Replace the module if necessary.
F30074 Communication error between the Control Unit and Power Module	Cause: Communications between the Control Unit (CU) and Power Unit (PU) via the interface no longer possible. The CU may have been withdrawn or is incorrectly inserted. Fault value (r0949, interpret hexadecimal): 0 hex: a Control Unit with external 24 V supply was withdrawn from the Power Unit during operation; or with the Power Unit switched off, the external 24 V supply for the Control unit was interrupted for some time. 1 hex: The Control Unit was withdrawn from the Power Unit during operation, although the encoderless safe motion monitoring functions are enabled (not supported). 20A hex: The Control Unit was inserted on a Power Unit, which has another code number. 20B hex: The Control Unit was inserted on a Power Unit, which although it has the same code number, has a different serial number. 601 hex: The Control Unit was inserted on a Power Unit, whose power/performance class (chassis unit) is not supported. Remedy: Reinsert the Control Unit (CU) or the Control Unit adapter (CUAxx) onto the original Power Unit (PU) and continue operation. If required, carry out a POWER ON for the CU and/or the CUA.
F31100 Zero mark distance error	Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. For distance-coded encoders, the zero mark distance is determined from zero marks detected pairs. If a zero mark is missing, depending on the pair generation, this cannot result in a fault and also has no effect in the system. Remedy: Check that the encoder cables are routed in compliance with EMC. Check the plug connections. Check the encoder type (encoder with equidistant zero marks). Replace the encoder or encoder cable.
F31110 Serial communications error	Cause: Serial communication protocol transfer error between the encoder and evaluation module. Remedy: Check the encoder cable and shielding connection. Replace the motor.
F31112 Error bit set in the serial protocol	Cause: The encoder sends a set error bit via the serial protocol. Remedy: Check the encoder cable and shielding connection. Replace the motor.
F31117 Inversion error signals A/B/R	Cause: For a square-wave encoder (bipolar, double ended) signals A*, B* and R* are not inverted with respect to signals A, B and R. Remedy: Check the encoder/cable. Does the encoder supply signals and the associated inverted signals?
F31130 Zero mark and position error from the coarse synchronization	Cause: After initializing the pole position using track C/D, Hall signals or pole position identification routine, the zero mark was detected outside the permissible range. For distance-coded encoders, the test is carried out after passing 2 zero marks. Fine synchronization was not carried out. Remedy: Check that the encoder cables are routed in compliance with EMC. Check the plug connections. If the Hall sensor is used as an equivalent for track C/D, check the connection. Check the connection of track C or D. Replace the encoder or encoder cable.
F31150 Initialization error	Cause: Encoder functionality is not operating correctly. Remedy: Check the encoder type used (incremental/absolute) and the encoder cable. If relevant, note additional fault messages that describe the fault in detail.
F52980 Absolute encoder motor changed	Cause: The servo motor with absolute encoder is changed. Actual motor ID is different from commissioned motor ID. Remedy: The servo motor will be automatically configured after the acknowledgement of this fault.
F52981 Absolute encoder motor mismatched	Cause: Connected absolute encoder motor cannot be operated. The servo drive in use does not support the Motor ID. Remedy: Use a suitable absolute encoder motor.
F52983 No encoder detected	Cause: The servo drive in use does not support encoderless operation. Remedy: Check the encoder cable connection between the servo drive and the servo motor. Use a servo motor with encoder.
F52984 Incremental encoder motor not configured	Cause: Commissioning of the servo motor has failed. The incremental encoder motor is connected but fails to commission. Remedy: Configure the motor ID by setting the parameter p29000.
F52985 Absolute encoder motor wrong	Cause: Motor ID is downloaded wrong during manufacture. The software of the servo drive does not support the Motor ID. Remedy: Update the software. Use a correct absolute encoder motor.
F52987 Absolute encoder replaced	Cause: Incorrect absolute encoder data. Remedy: Contact the Hotline.
A1009 Control module overtemperature	Cause: The temperature of the control module (Control Unit) has exceeded the specified limit value. Remedy: Check the air intake for the Control Unit. Check the Control Unit fan. Note: The alarm automatically disappears after the limit value has been undershot.
A1019 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.
A1032 All parameters must be saved	Cause: The parameters of an individual drive object were saved, although there is still no backup of all drive system parameters. The saved object-specific parameters are not loaded the next time that the system powers up. Remedy: Save all parameters.
A1045 Configuring data invalid	Cause: An error was detected when evaluating the parameter files saved in the non-volatile memory. Remedy: Save the parameterization using the “SAVE” function on the BOP. This overwrites the incorrect parameter files in the non-volatile memory and the alarm is withdrawn.
A1920 Drive Bus: Receive setpoints after To	Cause: Output data of Drive Bus master (setpoints) received at the incorrect instant in time within the Drive Bus clock cycle. Remedy: Check bus configuration. Check parameters for clock cycle synchronization (ensure To > Tdx). Note: To: Time of setpoint acceptance, Tdx: Data exchange time.
A1932 Drive Bus clock cycle synchronization missing for DSC	Cause: There is no clock synchronization or clock synchronous sign of life and DSC is selected. Remedy: Set clock synchronization across the bus configuration and transfer clock synchronous sign-of-life.
A5000 Drive heat sink overtemperature	Cause: The alarm threshold for overtemperature at the inverter heat sink has been reached. If the temperature rises by an additional 5 K, fault F30004 is initiated. Remedy: Check the following: Is the ambient temperature within the defined limit values? Have the load conditions and the load duty cycle been appropriately dimensioned? Has the cooling failed?
A7012 Motor temperature model 1/3 overtemperature	Cause: The motor temperature model 1/3 identified that the alarm threshold was exceeded. Remedy: Check the motor load and reduce it if required. Check the motor ambient temperature.
A7565 Encoder error in encoder interface	Cause: An encoder error was signaled for encoder via the encoder interface (G1_ZSW.15). Remedy: Acknowledge the encoder error using the encoder control word (G1_STW.15 = 1).
A7576 Encoderless operation due to a fault active	Cause: Encoderless operation is active due to a fault. Remedy: Remove the cause of a possible encoder fault. Carry out a POWER ON (power off/on) for all components.
A7965 Save required	Cause: The angular commutation offset was re-defined and has still not been saved. Remedy: This alarm automatically disappears after the data has been saved.
A7971 Angular commutation offset determination activated	Cause: The automatic determination of the angular commutation offset (encoder adjustment) is activated. The automatic determination is carried out at the next power-on command. Remedy: The alarm automatically disappears after determination.
A7991 Motor data identification activated	Cause: The motor data identification routine is activated. The routine is carried out at the next power-on command. Remedy: The alarm automatically disappears after the motor data identification routine has been successfully completed. If a POWER ON or a warm restart is performed with motor data identification selected, the motor data identification request will be lost. If motor data identification is required, it will need to be selected again manually following ramp-up.
A30016 Load supply switched off	Cause: The DC link voltage is too low. Remedy: Switch on the load supply. Check the line supply if necessary.
A30031 Hardware current limiting in phase U	Cause: Hardware current limit for phase U responded. The pulsing in this phase is inhibited for one pulse period. Closed-loop control is incorrectly parameterized. Fault in the motor or in the power cables. The power cables exceed the maximum permissible length. Motor load too high. Power unit defective. Remedy: Check the motor data. As an alternative, run a motor data identification. 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.
A31411 Absolute encoder signals internal alarms	Cause: The absolute encoder fault word includes alarm bits that have been set. Remedy: Replace the encoder.
A31412 Error bit set in the serial protocol	Cause: The encoder sends a set error bit via the serial protocol. Remedy: Carry out a POWER ON (power off/on) for all components. Check that the encoder cables are routed in compliance with EMC. Check the plug connections. Replace the encoder.
A52900 Failure during data copying	Cause: Copying is halted. The SD card was plugged out. The drive is not in the stop state. Remedy: Re-plug in the SD card. Make sure the drive is in the stop state.