click2electro

F1000 fault in Siemens V70 Drive indicates an Internal software error. This means the drive's firmware has encountered an unexpected condition or crash, requiring a reboot or firmware update to recover. 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 fault in Siemens V70 Drive indicates a Floating Point exception. This means the internal processor attempted an invalid mathematical operation, usually caused by a firmware bug. 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 fault in Siemens V70 Drive indicates an Internal software error. This means the system's firmware encountered a critical execution fault and requires a power cycle to restore normal operation. 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 fault in Siemens V70 Drive indicates an Acknowledgement delay when accessing the memory. This means the internal processor could not read or write to the memory module in time, suggesting a hardware or memory corruption issue. 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 fault in Siemens V70 Drive indicates an Internal software error. This means the drive's internal control software experienced a severe fault, requiring a power cycle or firmware upgrade. 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 fault in Siemens V70 Drive indicates Booting has been interrupted several times. This means the drive failed to complete its startup sequence repeatedly, often due to power instability or corrupted parameters, and has booted with factory settings. 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...

F1030 fault in Siemens V70 Drive indicates a Sign-of-life failure for master control. This means the drive lost its cyclic communication signal from the active PC master, triggering a safety timeout. Cause: For active PC master control, no sign-of-life was received within the monitoring time. Remedy: Contact the Hotline.

F1611 fault in Siemens V70 Drive indicates a Safety Integrated (SI) Defect Detected on the Control Unit. This means the internal safety monitoring system found a critical fault and triggered a Safe Torque Off (STO) to protect the machine. 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 fault in Siemens V70 Drive indicates a Drive Bus Setpoint timeout. This means the reception of setpoints from the Drive Bus interface has been interrupted due to a bus failure or controller stop. 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 fault in Siemens V70 Drive indicates a Drive Bus clock cycle synchronous operation clock cycle failure. This means the global control telegram to synchronize the clock cycles has failed or violated the time grid over several cycles. 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 fault in Siemens V70 Drive indicates a Clock cycle synchronous operation sign-of-life failure. This means the maximum permissible number of errors in the controller sign-of-life has been exceeded in cyclic operation. 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 fault in Siemens V70 Drive indicates Motor overtemperature. This means the motor's temperature sensor or internal thermal model shows it is running dangerously hot, usually due to an overload or poor cooling. 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 fault in Siemens V70 Drive indicates Open-loop/closed-loop control parameters changed. This means the drive automatically adjusted your control parameters because they exceeded hardware limits or were incompatible with the current hardware features. 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 fault in Siemens V70 Drive indicates the Lower DC link voltage threshold was reached. This means the internal DC bus voltage dropped below the required operating level while the drive was running, usually caused by a dip in the main supply voltage. 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 fault in Siemens V70 Drive indicates the Upper DC link voltage threshold was reached. This means the internal DC bus voltage spiked too high during operation, typically caused by rapid motor deceleration feeding energy back into the drive. 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 fault in Siemens V70 Drive indicates the Current controller output is limited. This means the drive is trying to output voltage to push current, but the current remains zero, usually because the motor is disconnected or a contactor is open. 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 fault in Siemens V70 Drive indicates an incorrect Commutation angle. This means the drive cannot correctly determine the rotor's magnetic position, often caused by a misaligned or damaged motor encoder. 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 resistanc...

F7414 fault in Siemens V70 Drive indicates the Encoder serial number changed. This means the drive detected a different encoder serial number than what was previously saved, requiring a new pole position adjustment. 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 a...

F7420 fault in Siemens V70 Drive indicates Drive: Current setpoint filter natural frequency > Shannon frequency. This means the configured filter frequency is too high for the drive's sampling rate and must be reduced. 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 fault in Siemens V70 Drive indicates Standstill monitoring has responded. This means the axis drifted out of the defined standstill window after it was supposed to be stopped, often due to mechanical overload or poor position loop tuning. 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 fault in Siemens V70 Drive indicates the Following error is too high. This means the actual position of the motor has fallen too far behind the commanded position profile, usually due to mechanical binding or torque limitations. 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 fault in Siemens V70 Drive indicates a Motor overcurrent. This means the motor drew more current than its permissible limit, which can be caused by a short circuit, aggressive ramping, or a heavy mechanical jam. 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 fault in Siemens V70 Drive indicates the Infeed or power unit is not ready. This means the internal power components failed to signal a ready state after startup, often due to a missing DC link voltage or hardware failure. 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 fault in Siemens V70 Drive indicates the Power unit has been changed. This means the control unit recognizes that it is connected to a different physical power module than the one previously saved in its configuration. 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 fault in Siemens V70 Drive indicates the Motor is blocked or the speed controller is at its limit. This means the drive has been outputting maximum torque for too long without the motor reaching the target speed, indicating a mechanical jam or disconnected encoder. 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 fault in Siemens V70 Drive indicates Motor overspeed. This means the actual motor speed exceeded the maximum safe speed limit configured in the drive parameters. Cause: The maximum permissible speed has been exceeded. Remedy: Check and correct the maximum speed (p1082).

F7995 fault in Siemens V70 Drive indicates a Pole position identification not successful. This means the drive could not successfully perform its initial pole position identification routine. Cause: The pole position identification routine was unsuccessful. Remedy: Contact the Hotline.

F30001 fault in Siemens V70 Drive indicates Power unit Overcurrent. This means the inverter detected a severe current spike in its output stages, usually due to a short-circuit in the motor cables or a ground fault. 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...

F30002 fault in Siemens V70 Drive indicates a DC link overvoltage. This means the internal DC bus voltage spiked too high, typically caused by rapid motor deceleration regenerating too much energy back into the drive. 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 fault in Siemens V70 Drive indicates a DC link undervoltage. This means the internal DC bus voltage dropped too low, caused by a failure or dip in the incoming AC line supply. 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 fault in Siemens V70 Drive indicates Drive heat sink overtemperature. This means the power module's heat sink is dangerously hot, usually due to a failed cooling fan, poor ventilation, or continuous overload. 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 fault in Siemens V70 Drive indicates Power unit Overload I2t. This means the inverter has been pushed past its continuous thermal current rating for too long, requiring a reduction in load to prevent hardware damage. 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 fault in Siemens V70 Drive indicates a Line phase failure in the main circuit. This means the drive detected excessive ripple on the DC bus, usually indicating that one of the incoming AC supply phases has been lost or a fuse has blown. 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 fault in Siemens V70 Drive indicates a Phase failure in the motor cable. This means the drive detected a loss of current in one or more output phases to the motor, suggesting a disconnected wire or unstable control loop. 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 fault in Siemens V70 Drive indicates a Ground fault. This means electrical current is escaping to the earth ground, usually caused by damaged insulation on the motor cables or inside the motor windings. 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 fault in Siemens V70 Drive indicates a Precharging DC link time monitoring failure. This means the internal DC bus could not charge up to the required voltage within the expected timeframe, often due to a low supply voltage or a damaged pre-charge resistor. 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 shor...

F30036 fault in Siemens V70 Drive indicates Internal overtemperature. This means the ambient temperature inside the drive's control electronics has exceeded safe limits, indicating a cooling failure or extreme room temperatures. 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 fault in Siemens V70 Drive indicates a 24 V supply overvoltage. This means the external 24V DC control power connected to the drive has spiked above safe hardware limits. Cause: The voltage monitor signals an overvoltage fault on the module. Remedy: Check the 24 V power supply. Replace the module if necessary.

F30074 fault in Siemens V70 Drive indicates a Communication error between the Control Unit and Power Module. This means the data link between the drive's logic board and its power stages is broken, possibly because the module was improperly seated or removed during operation. 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...

F31100 fault in Siemens V70 Drive indicates a Zero mark distance error. This means the physical distance measured between the encoder's zero marks does not match the expected parameterized distance, pointing to electrical noise or a faulty encoder. 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 fault in Siemens V70 Drive indicates a Serial communications error. This means the drive cannot correctly read data from the absolute encoder due to a protocol transfer failure. Cause: Serial communication protocol transfer error between the encoder and evaluation module. Remedy: Check the encoder cable and shielding connection. Replace the motor.

F31112 fault in Siemens V70 Drive indicates an Error bit set in the serial protocol. This means the absolute encoder is actively broadcasting an internal error code to the drive over the serial connection. Cause: The encoder sends a set error bit via the serial protocol. Remedy: Check the encoder cable and shielding connection. Replace the motor.

F31117 fault in Siemens V70 Drive indicates an Inversion error on signals A/B/R. This means the differential (inverted) tracks from a square-wave encoder are missing or mismatched with the primary tracks. 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 fault in Siemens V70 Drive indicates a Zero mark and position error from coarse synchronization. This means the encoder's zero mark was detected outside its expected phase window after initial pole position identification. 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 fault in Siemens V70 Drive indicates an Initialization error. This means the drive could not successfully boot or communicate with the connected encoder upon startup. 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 fault in Siemens V70 Drive indicates the Absolute encoder motor has changed. This means the drive detects a different motor ID than the one it was originally commissioned with, prompting an automatic reconfiguration. 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 fault in Siemens V70 Drive indicates an Absolute encoder motor mismatch. This means the currently connected motor is not compatible with or supported by this specific servo drive hardware. 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 fault in Siemens V70 Drive indicates No encoder detected. This means the drive cannot see an encoder connected to it and this particular servo drive does not support encoderless operation. 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 fault in Siemens V70 Drive indicates the Incremental encoder motor is not configured. This means the motor failed to complete its initial commissioning and needs its motor ID manually 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 fault in Siemens V70 Drive indicates the Absolute encoder motor is wrong. This means the motor's internally programmed ID is incorrect or not supported by the current drive software version. 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 fault in Siemens V70 Drive indicates the Absolute encoder was replaced. This means the drive detects corrupted or mismatched absolute encoder data, usually after hardware tampering or replacement. Cause: Incorrect absolute encoder data. Remedy: Contact the Hotline.

A1009 alarm in Siemens V70 Drive indicates Control module overtemperature. This means the internal temperature of the control unit board is approaching its maximum limit, warning of a potential failure if cooling isn't improved. 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 alarm in Siemens V70 Drive indicates Writing to the removable data medium was unsuccessful. This means the drive failed to save data to the inserted SD card or memory module. 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 alarm in Siemens V70 Drive indicates All parameters must be saved. This means some object-specific parameters were altered and saved, but a complete backup of the entire drive system is required for a safe restart. 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 alarm in Siemens V70 Drive indicates Configuring data is invalid. This means the drive detected corrupted parameter files in its non-volatile memory during startup, which must be overwritten. 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 alarm in Siemens V70 Drive indicates Drive Bus receive setpoints after To. This means the network output data (setpoints) arrived too late within the synchronized communication clock cycle. 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 alarm in Siemens V70 Drive indicates Drive Bus clock cycle synchronization is missing for DSC. This means Dynamic Servo Control is enabled but the required network clock synchronization signal is missing. 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 alarm in Siemens V70 Drive indicates Drive heat sink overtemperature. This means the power stage is getting too hot and is within 5°C of triggering a critical fault shutdown. 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 alarm in Siemens V70 Drive indicates Motor temperature model overtemperature. This means the software's internal calculation of the motor's heat is approaching the maximum thermal threshold due to high loads. 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 alarm in Siemens V70 Drive indicates an Encoder error in encoder interface. This means the drive detected an anomaly with the encoder signals via the control word status flag. 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 alarm in Siemens V70 Drive indicates Encoderless operation is active due to a fault. This means the drive detected a problem with the encoder and has automatically fallen back to an open-loop control mode. 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 alarm in Siemens V70 Drive indicates a Save is required. This means the motor's angular commutation offset has been newly calculated but needs to be saved to non-volatile memory to be permanent. 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 alarm in Siemens V70 Drive indicates Angular commutation offset determination is activated. This means the drive is scheduled to automatically determine the encoder's electrical angle during the next power-on cycle. 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 alarm in Siemens V70 Drive indicates Motor data identification is activated. This means the drive is scheduled to automatically measure the motor's electrical characteristics at the next run command. 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 alarm in Siemens V70 Drive indicates the Load supply is switched off. This means the internal DC bus voltage is too low, suggesting the main AC incoming power has been removed. Cause: The DC link voltage is too low. Remedy: Switch on the load supply. Check the line supply if necessary.

A30031 alarm in Siemens V70 Drive indicates Hardware current limiting in phase U. This means the drive detected a critical current peak in one of the motor phases and temporarily paused output pulses to protect the transistors. 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 alarm in Siemens V70 Drive indicates the Absolute encoder signals internal alarms. This means the encoder is sending an internal warning flag to the drive, indicating it may be failing. Cause: The absolute encoder fault word includes alarm bits that have been set. Remedy: Replace the encoder.

A31412 alarm in Siemens V70 Drive indicates an Error bit set in the serial protocol. This means the absolute encoder detected an error and is broadcasting a fault bit across the serial communication link. 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 alarm in Siemens V70 Drive indicates a Failure during data copying. This means an SD card operation was interrupted because the card was removed or the drive was not in a stopped state. 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.

A0046 alarm in WEG CFW500 Drive  indicates a Motor Overload. This means the calculated motor temperature model exceeded safe limits due to sustained excessive load.   Cause: Settings of parameters P0156, P0157, and P0158 are configured too low for the used motor. Overload on the motor shaft. Remedy: Verify if parameters P0156 , P0157 , and P0158 are configured correctly according to the motor's actual capacity. Inspect the motor shaft and machine for mechanical blocks.

A0047 alarm in WEG CFW500 Drive  indicates an IGBT Overload. This means the inverter's power modules are operating near their maximum current capacity limits, warning of a potential thermal trip.   Cause: Inverter output overcurrent condition. Remedy: Analyze operating load levels and duty cycles to lower active output current. Check for mechanical drag.

A0050 alarm in WEG CFW500 Drive  indicates Power Module Overtemperature. This means the internal power components are running unusually hot, warning of potential cooling issues.   Cause: High ambient temperature around the inverter (> 50 °C (> 122 °F)) and high output current. Blocked or defective cooling fan. Heatsink is dirty, preventing proper cooling airflow. Remedy: Inspect cooling fan operation and clean any dust or debris from heatsink fins. Improve room/enclosure ventilation as needed.

A0090 alarm in WEG CFW500 Drive  indicates an External Alarm. This means a peripheral safety or sensor switch connected to the digital inputs has triggered a warning state.   Cause: Wiring on DI1 to DI8 inputs is open or has poor contact. Remedy: Inspect terminal connections for digital inputs DI1 through DI8. Secure loose terminals and ensure reliable contact switch states.

A0098 alarm in WEG CFW500 Drive  indicates an Interruption of Self-tuning. This means the drive's automatic motor parameter identification process was halted prematurely by a disabled input command.   Cause: The drive was disabled via digital input DIx when self-tuning was run (parameter P0408 ). Remedy: Ensure the digital input assigned to keep the drive enabled remains active during the entire self-tuning routine execution.

A0128 alarm in WEG CFW500 Drive  indicates a Telegram Reception Timeout. This means the inverter stopped receiving valid serial communication data from the master controller within the expected timeframe.   Cause: Broken communication cable, general installation grounding faults, or loose terminal contacts. The master controller is not polling the drive within the timeout window set in parameter P0314. Remedy: Verify serial communication cabling, connections, and grounding lines. Ensure the master's polling interval is shorter than parameter P0314 , or disable this timeout check in parameter P0314.

A0133 alarm in WEG CFW500 Drive  indicates No Supply on the CAN Interface. This means the required 24V external power supply is missing from the CAN network connector.   Cause: Power supply cables are misconnected or inverted. Poor contact on the cable or connector of the CAN interface. Remedy: Measure if there is voltage within the allowed range between pins 1 and 5 of the CAN interface connector. Check terminal strip alignment and cable contact.

A0134 alarm in WEG CFW500 Drive  indicates a Bus Off condition on the CAN interface. This means the network experienced too many data errors and isolated itself from the bus to prevent further issues.   Cause: Short circuit on the CAN circuit transmission cable. CAN cables are misconnected or inverted. Mismatched baud rates among network devices. Termination resistors with the right value were not installed correctly (should only be at the physical ends of the main bus). CAN network was improperly installed. Remedy: Check CAN high and low wires for short circuits or inverted signals. Match node baud rates across the network. Check termination resistor values and placement.

A0135 alarm in WEG CFW500 Drive  indicates a Node Guarding or Heartbeat error. This means the CANopen network lost synchronization or dropped connection with the master controller.   Cause: Mismatched message exchange times between the master and slave. Master controller is not sending guarding telegrams within the assigned interval. Transmission delays or signal loss on the communication line. Remedy: Check the times set on both master and slave. To prevent conflicts, configure the error detection time on the slave to be a multiple of the master's exchange interval. Verify guarding telegram transmission.

A0136 alarm in WEG CFW500 Drive  indicates an Idle Master on the DeviceNet network. This means the network PLC master is physically connected but is currently in a stopped or idle state.   Cause: The master operation switch or run-bit is in the IDLE state in the host software. Remedy: Configure the master switch or corresponding bit to RUN in the configuration word of the master software. Refer to specific master software documentation.

A0137 alarm in WEG CFW500 Drive  indicates a DeviceNet Connection Timeout. This means the DeviceNet network stopped polling the inverter before the safety timeout expired.   Cause: Problem with the network master status. Issues in the network installation, broken cable, or poor contact on the network connections/grounding. Remedy: Verify the DeviceNet master status. Check general cable routing, connection shield lines, and grounding terminals.

A0138 alarm in WEG CFW500 Drive  indicates the Profibus DP Interface is in Clear Mode. This means the Profibus master has instructed all slaves to drop to a safe or cleared state.   Cause: The network master status is not in run mode. Remedy: Verify the network master status, making sure it is in execution mode (Run).

A0139 alarm in WEG CFW500 Drive  indicates the Profibus DP Interface is Offline. This means the physical Profibus network link to the master PLC has been broken or disrupted.   Cause: The network master is not configured or operating normally. Short circuit or loose contact on the communication cables. Cables are misconnected or inverted. Improperly placed termination resistors (should only be installed at the physical ends of the main bus). Profibus DP network cable routing or grounding is inadequate. Remedy: Check the PLC state. Check general cable routing, connection shield lines, and grounding terminals. Refer to the Profibus DP communication manual.

A0140 alarm in WEG CFW500 Drive  indicates a Profibus DP Module Access Error. This means the internal connection between the drive and the Profibus option card is failing.   Cause: The Profibus DP module is not seated properly in the slot. Hardware errors due to improper handling or installation of the accessory module. Remedy: Verify Profibus module mounting in slot. Replace communication module if handling errors damaged the pins.

A0148 alarm in WEG CFW500 Drive  indicates an Ethernet Interface Access Error. This means the drive's main control board cannot correctly communicate with the attached Ethernet module.   Cause: Ethernet module is not properly connected to the product. The drive firmware version does not support the module. Hardware errors caused by improper handling or installation of the accessory. Remedy: Ensure the Ethernet module is physically secure and correctly seated. Verify that the drive's firmware version is compatible with the module. Replace the card if the hardware is damaged.

A0149 alarm in WEG CFW500 Drive  indicates Ethernet Offline. This means the network connection between the Ethernet module and the master controller has been lost.   Cause: The network master is not configured or operating normally. Short-circuit or bad contact in the communication cables. General installation grounding/cable routing issues. Remedy: Check network configuration. Inspect the cabling and general installation routing for grounding integrity or line faults.

A0163 alarm in WEG CFW500 Drive  indicates a Signal Fault on AIx. This means the 4-20mA signal on the analog input has dropped below 2mA, indicating a broken wire or lost sensor connection.   Cause: Current signal on the analogue input AIx is interrupted or null. Parameterization error on analogue input AIx. Remedy: Check current loop wiring on analogue input AIx for breaks or open circuits. Verify terminal screw contacts and parameter configuration settings for AIx.

A0168 alarm in WEG CFW500 Drive  indicates the Speed Error is too High. This means the actual motor speed is deviating significantly from the commanded speed, usually because the drive is limiting torque.   Cause: The inverter is operating in Torque Current Limitation mode. Remedy: Check if the motor is stalled or heavily overloaded. Verify load status. If appropriate, adjust torque current limits in P0360.

A0177 alarm in WEG CFW500 Drive  indicates Fan Replacement is required. This means the main heatsink cooling fan has exceeded its 50,000-hour design lifespan and should be swapped out.   Cause: The heatsink fan maximum number of operating hours has been reached. Remedy: Perform preventive fan replacement maintenance.

A0700 alarm in WEG CFW500 Drive  indicates a Communication Fault with Remote HMI. This means the serial data link to the keypad broke, but no critical frequency references were active at the time.   Cause: HMI cable is disconnected. Communication interface with the HMI is incorrectly configured in parameter P0312. Remedy: Check parameter P0312 to verify that the HMI communication interface is configured correctly. Reconnect or replace the HMI serial cable.

A0702 alarm in WEG CFW500 Drive  indicates the Inverter is Disabled. This means a SoftPLC movement block is attempting to execute, but the drive's General Enable command is currently inactive.   Cause: The General Enable command for the drive is not active. Remedy: Check the drive control terminal states to ensure the General Enable input command is active.

A0704 alarm in WEG CFW500 Drive  indicates Two Movements Enabled. This means the SoftPLC user program has conflicting logic that is attempting to activate multiple movement blocks simultaneously.   Cause: Logic block overlap in the user program. Remedy: Check the user’s SoftPLC program logic to ensure only one movement block is active at any given time.

A0706 alarm in WEG CFW500 Drive  indicates an Unprogrammed SoftPLC Reference. This means a movement block was activated in the PLC program, but no valid speed reference was configured.   Cause: Speed reference is missing or incorrectly routed in the local or remote configuration (parameters P0221 and P0222). Remedy: Check and verify the speed reference configuration in parameters P0221 and P0222 (Local and Remote modes).

A0708 alarm in WEG CFW500 Drive  indicates the SoftPLC Application is Stopped. This means the custom logic program has been halted either by user parameter command or due to firmware incompatibility.   Cause: SoftPLC Application is stopped (parameters set as: P1001 = 0 and P1000 = 3 ). SoftPLC application code is incompatible with the CFW500 firmware version. Remedy: Verify runtime parameters. Upload an application version compatible with the inverter's active firmware version.

A0710 alarm in WEG CFW500 Drive  indicates the SoftPLC Program is Bigger than 8 KB. This means the downloaded user logic exceeds the drive's maximum allowable memory capacity.   Cause: The program size of the SoftPLC logic exceeded 8 KBytes. Remedy: Check project size. Optimize and compress the SoftPLC code structure to fit within permitted memory limits.

A0750 alarm in WEG CFW500 Drive  indicates an unprogrammed Analog Input for the Main PID. This means the PID controller is active, but no analog input has been assigned to read the process feedback variable.   Cause: Parameter P0231 or P0236 was not programmed for 5 or 6. Remedy: Configure parameter P0231 or P0236 to option 5 or 6 according to the PID loop feedback setup.

A0752 alarm in WEG CFW500 Drive  indicates an unprogrammed Digital Input for PID Auto/Manual selection. This means the drive requires a digital input to toggle PID modes, but none is configured.   Cause: Parameter P0263 , P0264 , P0265 , or P0266 was not programmed for 20. Remedy: Set the assigned digital input parameter (P0263 to P0266) to 20 to enable automatic/manual control routing.

A0754 alarm in WEG CFW500 Drive  indicates the Local Reference is not programmed for SoftPLC. This means the main PID controller is active in local mode, but the speed reference origin is incorrectly set.   Cause: The main PID controller is enabled ( P1017 set to 1 or 2) and the CFW500 frequency inverter is running the motor in LOCAL mode, but parameter P0221 is not programmed for 7. Remedy: Set parameter P0221 to 7 if utilizing the PID controller in local mode.

A0756 alarm in WEG CFW500 Drive  indicates the Remote Reference is not programmed for SoftPLC. This means the main PID controller is active in remote mode, but the speed reference origin is incorrectly set.   Cause: The main PID controller is enabled ( P1017 set to 1 or 2) and the CFW500 frequency inverter is running the motor in REMOTE mode, but parameter P0222 is not programmed for 7. Remedy: Set parameter P0222 to 7 if utilizing the PID controller in remote mode.

A0758 alarm in WEG CFW500 Drive  indicates the Engineering Unit is not programmed for Hz or rpm. This means the display unit parameter for motor speed needs to be explicitly configured.   Cause: Parameter P0516 was not programmed for 13 (Hz) or 3 (rpm). Remedy: Configure parameter P0516 to option 13 (Hz) or 3 (rpm) to match your application units.

A0760 alarm in WEG CFW500 Drive  indicates a Low Level of the Main PID Process Variable. This means the feedback sensor reading has dropped below the minimum programmed process threshold.   Cause: Parameter P1030 is programmed for 1, and the process variable value has dropped below the threshold in P1031 for the time programmed in P1032 . Remedy: Verify the process feedback sensor. Adjust parameters P1031 (threshold) and P1032 (delay time) if necessary.

A0762 alarm in WEG CFW500 Drive  indicates a High Level of the Main PID Process Variable. This means the feedback sensor reading has exceeded the maximum programmed process threshold.   Cause: Parameter P1030 is programmed for 1, and the process variable value has exceeded the threshold in P1033 for the time programmed in P1034 . Remedy: Check for high limits in the process line (overpressure, high flow, etc.). Verify parameters P1033 and P1034.

A0764 alarm in WEG CFW500 Drive  indicates the Frequency Inverter is in Sleep Mode. This means the PID controller has put the drive into a standby state because the process demand dropped below the configured sleep threshold.   Cause: The main PID controller is active in automatic mode, and the motor speed remained below the speed programmed in P1036 for the duration set in P1037 . Remedy: Informational alarm status indicating sleep mode has engaged. To adjust this behavior, modify parameters P1036 (sleep speed) or P1037 (sleep delay time).

A0766 alarm in WEG CFW500 Drive  indicates a Dry Pump Detected. This means the inverter senses high motor speed with unusually low torque, suggesting the pump has lost fluid prime.   Cause: Parameter P1042 is programmed for 1, the motor speed is above the speed programmed in P1043, and the motor torque has remained below the value programmed in P1044 for the time programmed in P1045. Remedy: Verify the fluid flow to the pump and check for blockages or dry lines. Verify the parameter configurations for P1042 , P1043 , P1044 , and P1045 .

A0768 alarm in WEG CFW500 Drive  indicates a Broken Belt Detected. This means the inverter senses high motor speed with unusually low torque, suggesting the mechanical transmission belt has snapped.   Cause: Parameter P1046 is programmed for 1, the motor speed is above the speed programmed in P1047, and the motor torque has remained below the value programmed in P1048 for the time programmed in P1049. Remedy: Check the mechanical coupling belt/pulley state. Verify the parameter configurations for P1046 , P1047 , P1048 , and P1049 .

A0770 alarm in WEG CFW500 Drive  indicates Filter Maintenance is needed. This means the running hours of the system have exceeded the programmed threshold for filter replacement.   Cause: Parameter P1050 is programmed for 1, and the total motor operation time shown in P1052 is above the value programmed in P1051. Remedy: Perform scheduled maintenance to replace the system filter. Reset the elapsed timer if required.

A0780 alarm in WEG CFW500 Drive  indicates an unprogrammed Analog Input for the External PID. This means the external PID controller is active, but no analog input is assigned to its process feedback.   Cause: Parameter P0231 or P0236 was not programmed for option 8. Remedy: Set parameter P0231 or P0236 to option 8 to correctly route the external PID process feedback.

A0782 alarm in WEG CFW500 Drive  indicates an unprogrammed Digital Input for External PID Auto/Manual selection. This means the external PID requires a toggle input, but none is configured.   Cause: Parameter P0263, P0264, P0265, or P0266 was not programmed for option 21. Remedy: Set the assigned digital input parameter (P0263 to P0266) to 21 to enable manual/automatic switching functions.

A0784 alarm in WEG CFW500 Drive  indicates an unprogrammed Analog Output for the External PID. This means the external PID controller is active, but its output signal isn't mapped to an analog terminal.   Cause: Parameter P0251 or P0254 was not programmed for option 16. Remedy: Configure parameter P0251 or P0254 to option 16 to set the analog output target.

A0786 alarm in WEG CFW500 Drive  indicates a Low Level of the External PID Process Variable. This means the external PID feedback sensor reading has dropped below its minimum programmed threshold.   Cause: Parameter P1075 is programmed for 1, and the process variable of the external PID controller remained below the value programmed in P1076 for the duration set in P1077. Remedy: Verify the process feedback loops and verify configurations in parameters P1075 , P1076 , and P1077 .

A0788 alarm in WEG CFW500 Drive  indicates a High Level of the External PID Process Variable. This means the external PID feedback sensor reading has exceeded its maximum programmed threshold.   Cause: Parameter P1075 is programmed for 1, and the process variable of the external PID controller remained above the value programmed in P1078 for the duration set in P1079. Remedy: Verify process line sensors. Check parameter thresholds set in P1075 , P1078 , and P1079 .

F0021 fault in WEG CFW500 Drive  indicates Undervoltage on the DC Link. This means the internal DC bus voltage has dropped too low, often caused by input power dips or phase loss.   Cause: Wrong voltage supply (comply with inverter rating plate and parameter P0296 ). Mains voltage dropped producing a DC Link voltage below the minimum value (monitored in P0004 ): Ud < 200 Vdc in 200-240 Vac (P0296 = 0). Ud < 360 Vdc in 380-480 Vac (P0296 = 1). Ud < 500 Vdc in 500-600 Vac (P0296 = 2). Phase fault on the input. Fault in the pre-charge circuit. Remedy: Check input mains voltages. Check terminal blocks and check for missing phases. Verify parameters in P0296.

F0022 fault in WEG CFW500 Drive  indicates Overvoltage on the DC Link. This means the internal DC bus voltage has spiked too high, typically caused by rapid deceleration of a high-inertia load.   Cause: Wrong voltage supply (comply with inverter rating plate and parameter P0296 ). DC link voltage exceeded permissible limits (monitored in P0004 ): Ud > 410 Vdc in 200-240 Vac (P0296 = 0). Ud > 810 Vdc in 380-480 Vac (P0296 = 1). Ud > 1000 Vdc in 500-600 Vac (P0296 = 2). Load inertia is too high or deceleration ramp is too fast. Parameters P0151 , P0153 , or P0185 are set too high. Remedy: Verify incoming mains supply. Increase deceleration time. Adjust parameters P0151, P0153, or P0185.

F0031 fault in WEG CFW500 Drive  indicates a Communication Fault with the Plug-in Module. This means the drive's main control board has lost connection with the attached expansion module.   Cause: Plug-in module is damaged. Plug-in module is not properly connected/seated. Problem in the identification of the plug-in module (refer to P0027 ). Remedy: Check the physical fit and terminal pin contacts of the plug-in card. Replace the card if damaged. Verify identification parameter P0027.

F0032 fault in WEG CFW500 Drive  indicates a Fault in the Plug-in Module Connection. This means the plugin module was unexpectedly disconnected or seated improperly while the drive was powered.   Cause: Plug-In Module was unplugged while inverter power was active. Plug-In Module is damaged or not properly connected. Problem in module identification (refer to P0027 ). Remedy: Ensure drive power is isolated before disconnecting accessory cards. Inspect the plugin board pins and re-seat correctly.

F0033 fault in WEG CFW500 Drive  indicates a Self-tuning Fault. This means the inverter failed to accurately measure the motor's stator resistance during the automatic setup procedure.   Cause: Stator resistance value in parameter P0409 does not comply with the inverter power rating. Motor connection error. Connected motor power rating is too low or too high in relation to the inverter capacity. Remedy: Turn off the power supply and inspect all connections at the motor terminal box. Verify if stator resistance parameter P0409 and motor power ratings are configured correctly.

F0048 fault in WEG CFW500 Drive  indicates an Overload on the IGBTs. This means the internal power transistors experienced sustained excessive current and tripped to prevent thermal damage.   Cause: Inverter output overcurrent is greater than 2xInom. Remedy: Check active load levels to lower current spikes. Inspect system sizing.

F0051 fault in WEG CFW500 Drive  indicates IGBTs Overtemperature. This means the internal power transistors have exceeded their safe thermal limits and the drive has tripped to prevent hardware damage.   Cause: High ambient temperature around the inverter (> 50 °C (> 122 °F)) and high output current. Blocked or defective cooling fan. Heatsink is dirty, preventing proper cooling airflow. Remedy: Ensure ambient room temperature is within limits. Clean heatsink fins and verify that the cooling fan is operating correctly.

F0068 fault in WEG CFW500 Drive  indicates Motor Overtemperature on a dedicated input. This means the motor's PTC thermistor detected excessive heat, triggering a hardware-level thermal protection trip.   Cause: Overload on the motor shaft. High start/stop duty cycle. High ambient temperature around the motor. Loose contact or short circuit (3 k9 < R PTC < 0 k1). Motor thermistor is not installed. Motor shaft is stuck. Remedy: Check the motor shaft and driven load for mechanical blockages. Optimize duty cycles. Measure thermistor circuit resistances and secure connections.

F0070 fault in WEG CFW500 Drive  indicates Overcurrent or Short circuit. This means a massive current spike was detected, usually caused by a physical short in the motor phases or aggressive acceleration.   Cause: Short-circuit between two motor phases. Short-circuit of the rheostatic braking resistor connection cables. IGBTs module is short-circuited or damaged. Drive started with an acceleration ramp that is too short. Drive started with the motor already spinning without using the Flying Start function. Remedy: Verify motor winding and connection cables for phase-to-phase shorts. Increase the acceleration ramp time. Enable the Flying Start function if the motor is prone to rotating during startup.