Allen-Bradley PowerFlex AC drives / VFDs
Technical records for Allen-Bradley PowerFlex industrial drives, beginning with PowerFlex 520 and 750 service routes for hardware overcurrent, ground fault, DC-bus overvoltage/undervoltage and DPI port-loss communication symptoms.
Scope of this technical record
Rockwell Automation coverage is focused on Allen-Bradley PowerFlex 520 and 750 class service searches where the user has a fault number, a stopped machine and a need to separate external motor wiring, DC-bus conditions, dynamic-brake hardware and DPI/HIM communication faults before replacing a drive assembly.
Use this page only for qualified industrial-drive personnel. PowerFlex drives contain hazardous input, output and DC-link voltages. Isolate supply, verify discharge and follow the machine lockout procedure before motor-cable, braking or internal inspection work.
PowerFlex evidence routing map
Preserve the first fault and prove the external boundary before ordering a drive, module or HIM.
PowerFlex output and DPI evidence map
What this brand page should answer
PowerFlex searches are strong because they are normally fault-number searches: F12, F13, F5, F4, F81 or a related port-loss code. The user is rarely reading for education. They are trying to decide whether the fault belongs to the motor/cable path, the power stage, the incoming supply, the brake circuit, the HIM/DPI path or a noise/cable-routing issue.
A useful Rockwell page should be a triage map rather than a brochure. It should help the technician preserve the fault queue, identify trip timing and collect enough evidence to avoid replacing the drive while a grounded motor cable remains in place, or replacing a HIM/adapter while the actual problem is DPI cable routing, noise, power cycling or a loose port connection.
PowerFlex fault families covered first
The current batch focuses on three fault groups. The first group is output-current and ground-fault protection: F12 hardware overcurrent and F13 ground fault. The second group is DC-link condition: F5 DC bus overvoltage and F4 undervoltage. The third group is communication loss around the DPI/HIM/adapter path: F81 through F86 style port-loss complaints.
These groups match common field-support boundaries. Output faults begin outside the drive until the motor and cable are proven. DC-bus faults begin with line, regeneration and braking evidence. DPI faults begin with port identity, connected device, cable quality, cabinet routing and whether the loss follows a particular HIM, cable, adapter or drive.
PowerFlex quick index
| User search | Service boundary | Evidence to collect first |
|---|---|---|
| PowerFlex F12 HW Overcurrent | Output current, load, power stage, current feedback | Trip timing, load condition, motor/cable isolation, fault queue order |
| PowerFlex F13 Ground Fault | Motor insulation, output cable, moisture, output leakage, current-sense boundary | Insulation result, cable route, terminal box condition, whether F13 appears with motor disconnected |
| PowerFlex F5 DC Bus Overvoltage | Line voltage, regeneration, braking resistor/chopper, deceleration command | DC-bus value, decel ramp, brake resistor measurement, load inertia |
| PowerFlex F4 Undervoltage | Input supply, phase loss, precharge, DC link | Terminal voltage under load, upstream fuse/contactors, bus behaviour during start |
| PowerFlex F81-F86 DPI / HIM Port Loss | HIM, DPI cable, adapter, port power, noise and routing | Port number, connected device, cable photos, whether fault follows the device or the drive |
Avoiding repeat failure after replacement
A repeat failure often happens when the recorded fault was treated as the failed part rather than the observed protection boundary. F12 and F13 can be created by external motor insulation, wet terminal boxes, cable damage, a stuck mechanical load or a brake that has not released. A new drive connected to the same fault can trip instantly or suffer secondary damage.
F5 can return if the brake resistor path is open, the resistor value is wrong, the chopper path is damaged or the deceleration command is too aggressive for the load inertia. F81-F86 communication faults can return if the cabinet routing, shield practice or adapter/HIM cabling is unchanged. The repair record should therefore close the external cause before documenting the drive-side conclusion.
Minimum evidence for a useful PowerFlex request
| Evidence area | Why it matters | Good field note |
|---|---|---|
| Nameplate and frame | Fault handling and hardware boundaries vary by family and frame | PowerFlex 525 or 755 type code, voltage class, frame and firmware where known |
| Fault queue | The first fault is more valuable than the displayed last message | F13 appeared before F12 after rain exposure; F5 only during decel |
| Trip timing | Routes the cause to enable, acceleration, load, decel, heat or communication | Trips at start command before motor rotation |
| Motor/cable insulation | Output faults must be separated from external ground/short conditions | Motor disconnected from drive; insulation test performed at motor/cable boundary |
| DC bus and brake path | Overvoltage/undervoltage decisions depend on supply and regeneration evidence | Brake resistor measured; DC-bus value recorded during decel |
| DPI/HIM evidence | Port-loss faults often follow cable, device or routing rather than main drive hardware | Port number, cable length/routing, connected HIM/adapter and swap result |
Field record checklist
- PowerFlex family, type code, voltage class and frame
- Fault number and queue order
- Trip timing and load state
- Motor/cable insulation and terminal-box evidence for F12/F13
- DC-bus, line and dynamic-brake evidence for F4/F5
- Port number, HIM/adapter identity and DPI cable route for F81-F86
Technical basis and reference documents
This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.
Internal service-map layer for PowerFlex fault routing and evidence collection.