Allen Bradley PowerFlex 700 Drive Fault Codes List

Complete guide to Allen Bradley PowerFlex 700 fault codes. Troubleshoot DPI Port faults, Precharge errors, and access diagnostic queues using the HIM or Studio 5000.

PowerFlex 700 Fault Codes Reference Table

Fault Codes	Cause & Solutions
F29 Analog In Loss	Cause: An analog input is configured to fault on signal loss. A signal loss has occurred. - Configure with [Anlg In 1, 2 Loss]. Solution: - Check the parameters. - Check for broken/loose connections at inputs.
F108 Anlg Cal Chksum	Cause: The checksum read from the analog calibration data does not match the checksum that is calculated. Solution: - Replace the drive.
F33 Auto Rstrt Tries	Cause: Drive unsuccessfully attempted to reset a fault and resume running for the programmed number of [Flt RstRun Tries]. - Enable/Disable with [Fault Config 1]. Solution: - Correct the cause of the fault and manually clear.
F80 AutoTune Aborted	Cause: Autotune function was canceled by the user or a fault occurred. Solution: - Restart the procedure.
F2 Auxiliary Input	Cause : Auxiliary input interlock is open. Solution: - Check remote wiring. - Verify communications programming for intentional fault.
F55 Cntl Bd Overtemp	Cause: The temperature sensor on the Main Control Board detected excessive heat. Solution: - Check Main Control Board fan. - Check surrounding air temperature. - Verify proper mounting/ cooling.
F69 DB Resistance	Cause: The resistance of the internal DB unit is out of range. Solution: - Replace the resistor.
F24 Decel Inhibit	Cause: The drive is not following a commanded acceleration or deceleration because it is attempting to limit bus voltage. Solution: - Verify that input voltage is within drive specified limits. - Verify that system ground impedance follows proper grounding techniques. - Disable bus regulation and/or add dynamic brake resistor and/or extend deceleration time.
F64 Drive Overload	Cause: Drive rating of 110% for 1 minute or 150% for 3 seconds has been exceeded. Solution: Reduce load or extend Accel Time.
F49 Drive Powerup	No fault is displayed. Used as a Powe r Up Marker in the Fault Queue indicating that the drive power has been cycled.
F79 Excessive Load	Cause: Motor did not come up to speed in the allotted time during autotune. Solution: - Uncouple load from motor. - Repeat Autotune.
F91 Encoder Loss	Cause: Requires differential encoder. One of the 2 encoder channel signals is missing. Solution: - Check Wiring. - Replace encoder.
F90 Encoder Quad Err	Cause: Both encoder channels changed state within one clock cycle. Solution: - Check for externally induced noise. - Replace encoder.
F52 Faults Cleared	No fault displayed. Used as a marker in the Fault Queue indicating that the fault clear function was performed.
F51 Flt QueueCleared	No fault displayed. Used as a marker in the Fault Queue indicating that the clear queue function was performed.
F78 FluxAmpsRef Rang	Cause: The value for flux amps determined by the Autotune procedure exceeds the programmed [Motor NP FLA]. Solution: - Reprogram [Motor NP FLA] with the correct motor nameplate value. - Repeat Autotune.
F13 Ground Fault	Cause: A current path to earth ground has been detected at one or more of the drive output terminals. Solution: - Check the motor and external wiring to the drive output terminals for a grounded condition.
F93 Hardware Fault	Cause: Hardware enable is disabled (jumpered high) but logic pin is still low. Solution: - Check jumper. - Replace Main Control Board.
F130 Hardware Fault	Cause: Gate array load error. Solution: - Cycle power. - Replace Main Control Board.
F131 Hardware Fault	Cause: Dual port failure. Solution: - Cycle power. - Replace Main Control Board.
F8 Heatsink OvrTmp	Cause: Heatsink/Power Module temperature exceeds a predefined value. Solution: - Check for blocked or dirty heatsink fins. Verify that ambient temperature has not exceeded the rated ambient temperature. - Check fan.
F12 HW OverCurrent	Cause: The drive output current has exceeded the hardware current limit. Solution: - Check output of drive or motor for shorts. - Check programming. - Check for excess load, improper DC boost setting, DC brake volts set too high, or other causes of excess current.
F106 Incompact MCB-PB	Cause: Drive rating information that is stored on the power board is incompatible with the main control board. Solution: Load compatible version files into drive.
F121 I/O Comm Loss	Cause: I/O Board lost communications with the Main Control Board. Solution: - Check connector. - Check for induced noise. - Replace I/O board or Main Control Board.
F122 I/O Failure	Cause: - I/O was detected, but failed the powerup sequence. - I/O Board is separate in Standard & integral in Vector Control. Solution: - Replace I/O Board (Standard Control) or Main Control Board (Vector Control).
F120 I/O Mismatch	Cause: I/O board configuration not the same from last time drive was powered up. Solution: - Verify configuration.
F17 Input Phase Loss	Cause: The DC bus ripple has exceeded a preset level. Solution: - Check incoming power for a missing phase/blown fuse.
F77 IR Volts Range	Cause: “Calculate” is the autotune default and the value that is determined by the autotune procedure for IR Drop Volts is not in the range of acceptable values. Solution: - Re-enter motor nameplate data.
F87 IXo VoltageRange	Cause: Voltage calculated for motor inductive impedance exceeds 25% of [Motor NP Volts]. Solution: - Check for proper motor sizing. - Check for correct programming of [Motor NP Volts], parameter 41. - Additional output impedance can be required.
F15 Load Loss	Cause: Drive output torque current is below [Load Loss Level] for a time period greater than [Load Loss time]. Solution: - Verify connections between motor and load. - Verify level and time requirements.
F7 Motor OverLoad	Cause: - Internal electronic overload trip. - Enable/Disable with [Fault Config 1]. Solution: - An excessive motor load exists. - Reduce load so drive output current does not exceed the current set by [Motor NP FLA].
F16 Motor Thermistor	Cause: Thermistor output is out of range. Solution: - Verify that thermistor is connected. - Motor is overheated. Reduce load.
F109 NVS I/O Checksum	Cause: EEprom checksum error. Solution: - Cycle power and repeat function. - Replace Main Control Board.
F110 NVS I/O Failure	Cause: EEprom I/O error. Solution: - Cycle power and repeat function. - Replace Main Control Board.
F21 Output PhaseLoss	Cause: Current in one or more phases has been lost or remains below a preset level. Solution: - Check the drive and motor wiring. - Check for phase-to-phase continuity at the motor terminals. - Check for disconnected motor leads.
F25 OverSpeed Limit	Cause: Functions such as Slip Compensation or Bus Regulation have attempted to add an output frequency adjustment greater than that programmed in [Overspeed Limit]. Solution: - Remove excessive load or overhauling conditions or increase [Overspeed Limit].
F5 OverVoltage	Cause: DC bus voltage exceeded max value. Solution: - Monitor the AC line for high line voltage or transient conditions. - Bus overvoltage can also be caused by motor regeneration. - Extend the decel time or install dynamic brake option.
F100 Parameter Chksum	Cause: The checksum read from the board does not match the checksum calculated. Solution: - Restore defaults. - Reload User Set if used.
F48 Params Defaulted	Cause: The drive was commanded to write default values to EEPROM. Solution: - Clear the fault or cycle power to the drive. - Program the drive parameters as needed.
F38 Phase U to Gnd	Cause: A phase to ground fault has been detected between the drive and motor in this phase. Solution: - Check the wiring between the drive and motor. - Check motor for grounded phase. - Replace drive if fault cannot be cleared.
F39 Phase V to Gnd	Cause: A phase to ground fault has been detected between the drive and motor in this phase. Solution: - Check the wiring between the drive and motor. - Check motor for grounded phase. - Replace drive if fault cannot be cleared.
F40 Phase W to Gnd	Cause: A phase to ground fault has been detected between the drive and motor in this phase. Solution: - Check the wiring between the drive and motor. - Check motor for grounded phase. - Replace drive if fault cannot be cleared.
F41 Phase UV Short	Cause: Excessive current has been detected between these two output terminals. Solution: - Check the motor and drive output terminal wiring for a shorted condition. - Replace drive if fault cannot be cleared.
F42 Phase UW Short	Cause: Excessive current has been detected between these two output terminals. Solution: - Check the motor and drive output terminal wiring for a shorted condition. - Replace drive if fault cannot be cleared.
F43 Phase VW Short	Cause: Excessive current has been detected between these two output terminals. Solution: - Check the motor and drive output terminal wiring for a shorted condition. - Replace drive if fault cannot be cleared.
Port 1…5 DPI Loss F81…F85	Cause: - DPI port stopped communicating. - A SCANport device was connected to a drive operating DPI devices at 500k baud. Solution: - If adapter was not intentionally disconnected, check wiring to the port. Replace wiring, port expander, adapters, Main Control Board, or complete drive as required. - Check HIM connection. - If an adapter was intentionally disconnected and the [Logic Mask] bit for that adapter is set to “1”, this fault occurs. To disable this fault, set the [Logic Mask] bit for the adapter to “0.”
F71…F75 Port 1…5 Adapter	Cause: The communications card has a fault. Solution: - Check DPI device event queue and corresponding fault information for the device.
F3 Power Loss	Cause: Excessive DC Bus voltage ripple. Solution: - Monitor the incoming AC line for low voltage or line power interruption. - Check input fuses. - Reduce load.
F70 Power Unit	Cause: One or more of the output transistors were operating in the active region instead of desaturation. This can be caused by excessive transistor current or insufficient base drive voltage. Solution: - Check for damaged output transistors. - Replace drive.
F92 Pulse In Loss	Cause: Z Channel is selected as a pulse input and no signal is present. Solution: - Check wiring. - Replace pulse generator.
F104 Pwr Brd Chksum1	Cause: The checksum read from the EEPROM does not match the checksum that is calculated from the EEPROM data. Solution: - Clear the fault or cycle power to the drive.
F105 Pwr Brd Chksum2	Cause: The checksum read from the board does not match the checksum that is calculated. Solution: - Cycle power to the drive. - If problem persists, replace drive.
F107 Replaced MCB-PB	Cause: Main Control Board was replaced and parameters were not programmed. Solution: - Restore defaults. - Reprogram parameters.
F63 Shear Pin	Cause: Programmed [Current Lmt Val] has been exceeded. Enable/Disable with [Fault Config 1]. Solution: Check load requirements and [Current Lmt Val] setting.
F88 Software Fault	Cause: Microprocessor handshake error. Solution: - Replace Main Control Board.
F89 Software Fault	Cause: Microprocessor handshake error. Solution: - Replace Main Control Board.
F36 SW OverCurrent	Cause: Drive output current has exceeded the 1 ms current rating. - This rating is greater than the 3-second current rating and less than the hardware overcurrent fault level. - It is typically 200…250% of the drive continuous rating. Solution: - Check for excess load, improper DC boost setting. DC brake volts set  too high. - If enabled, check level of flux braking in parameter P549 [Flux Braking %].
F20 TorqPrv Spd Band	Cause: Difference between [Commanded Speed] and [Encoder Speed] has exceeded the level set in [Spd Dev Band] for a time period greater than [Spd Band Integrat]. Solution: - Check wiring between drive and motor. - Check release of mechanical brake.
F9 Trnsistr OvrTemp	Cause: Output transistors have exceeded their maximum operating temperature. Solution: - Verify that maximum ambient temperature has not been exceeded. - Check fan. - Check for excessive load.
F4 UnderVoltage	Cause: DC bus voltage fell below the min value. Solution: Monitor the incoming AC line for low voltage or line power interruption.
F101 UserSet1 Chksum	Cause: The checksum read from the user set does not match the checksum that is calculated. Solution: - Re-save user set.
F102 UserSet2 Chksum	Cause: The checksum read from the user set does not match the checksum that is calculated. Solution: - Re-save user set.
F103 UserSet3 Chksum	Cause: The checksum read from the user set does not match the checksum that is calculated. Solution: - Re-save user set.

 

How to Read PowerFlex 700 Faults

Diagnosing the PowerFlex 700 involves navigating the LCD menu or using Rockwell software. Here are the best methods for 2026:

• The HIM (LCD Display): The HIM provides a “Fault Queue” and an “Alarm Queue.”
  • Press the Diagnostics soft key (if available) or navigate to Diagnostics > Faults > View Fault Queue.
  • This displays the last 8 faults with timestamps and text descriptions.
• Port Identification: The PowerFlex 700 uses the DPI protocol. Faults often reference a specific “Port”:
  • Port 0: The Drive itself.
  • Port 1: The HIM (Keypad).
  • Port 5: The Communication Adapter (Ethernet, ControlNet, etc.).
• Studio 5000 / CCW: Connect via the Ethernet module or the serial port on the HIM (using a 1203-USB). In the drive properties, the “Faults” tab provides a snapshot of the drive status bits (DC Bus Volts, Amps, Speed) at the exact moment the trip occurred.

Frequently Asked Questions (FAQ)

Q: How do I reset a PowerFlex 700 fault?

A: You can reset the drive using:

• The “Clear Fault” soft key on the LCD HIM.
• The red Stop button (if the fault is clearable and the drive is stopped).
• A Digital Input configured for “Clear Fault.”
• Cycling the main power.

Q: What is the “F75 Port 5 Adapter Loss” fault?

A: This is the most common communication fault. It means the drive lost contact with the communication card in Slot 5 (usually the 20-COMM-E Ethernet card).

• Check if the ribbon cable connecting the card to the drive is loose.
• Check if the PLC has stopped communicating (the card may be set to fault on idle).

Q: What does “F3 Power Loss” or “Precharge Fault” mean?

A: These indicate input power issues.

• F3 Power Loss: The DC bus dropped below the trip level (monitoring parameter 196). Common during brownouts.
• Precharge Fault: The drive failed to charge the DC bus capacitors within the allotted time. This often indicates a failed input bridge or a damaged precharge resistor inside the drive.