VFD Faults & Motor Drive Diagnostics
When a drive faults, the most valuable clue is usually not the code by itself — it is when in the cycle the fault appeared. Startup, acceleration, steady load, deceleration and after warmup point in different directions.
What the symptom actually tells you
A variable-frequency drive spends its working life protecting a motor and itself. So a fault indication is best read as: the drive noticed something and stopped. Whether the cause sits in the load, the mechanics, the motor, the incoming supply, the cooling air path, the network or the drive itself is exactly what a diagnostic visit is for.
Timing separates the categories quickly. A fault at the instant of starting suggests something different from one that appears part-way through acceleration. A fault under steady load after twenty minutes of running raises temperature and ventilation questions that a cold start does not. A fault during deceleration raises the regenerative question, because a decelerating load pushes energy back toward the drive. And a fault that follows a network event belongs in its own category again.
The useful groupings are overcurrent and overload conditions, supply undervoltage, overvoltage during deceleration, ventilation and temperature conditions, and loss of communication. Those categories are recognisable across the industry, but the codes that express them are not: do not assume the same code has the same meaning across brands or model families; read the manual for the exact model. Fault availability depends on model and configuration; for example, some PowerFlex 525 faults do not apply to PowerFlex 523. One more distinction worth stating plainly — a DC drive is not an AC variable-frequency drive, and documentation KONGRA cites elsewhere for a DC drive family covers that family only.
KONGRA LLC is independent and is not affiliated with, endorsed by or authorized by Rockwell Automation or any other manufacturer. Drive and motor work is performed within KONGRA's current legal license scope, and coordinated with properly licensed independent contractors where the scope requires it.
When did the fault appear?
These are categories to narrow the question before a visit, not a remote diagnosis. Confirmation requires on-site measurement.
- At startup, before the machine really movesPoints toward supply, control sequence, motor connection or a load that is already resisting. Record what the display showed at that instant.
- During accelerationRaises current and mechanical-resistance questions. Note how quickly the machine is asked to come up to speed and what it was carrying.
- Under steady load, often after the line has warmed upBrings ventilation, ambient temperature, filter and enclosure condition into the picture alongside load.
- During deceleration or stoppingA decelerating load can push energy back toward the drive, which is a distinct category from overcurrent while driving.
- After a network or communication eventRecorded as a communication observation. Note whether other devices on the same network were affected.
What you can safely observe yourself
Record everything you can from the normal operator position before anyone resets the drive — a reset can change the display and, depending on the controller, what history remains.
- Record the exact drive model and catalogue or part number from the label
- Record the motor nameplate details and what the motor drives
- Photograph the fault code or message exactly as displayed
- Note precisely when it faulted: startup, acceleration, steady load, deceleration, or after a network event
- Note how long the machine had been running and what it was carrying or processing
- Note any fault history the drive still shows, if that is readable from the normal display
- Note recent changes: product, speed settings changed by others, service, or a supply event on site
- Do not clear or erase fault history before it has been recorded
- Do not reset and restart repeatedly to see whether it will run
- Do not change parameters, perform a factory reset, or alter wiring
- Do not update firmware or bypass a safe-torque-off or other protective function
- Do not open a sealed drive chassis
What requires a technician on site
- Fault code and any retained history read against the manual for that exact model
- Incoming supply conditions measured, including behaviour under load
- Motor condition and connections assessed rather than assumed from the code
- Driven load and mechanical resistance evaluated as a possible cause
- Cooling air path, enclosure and ambient temperature conditions inspected
- Communication and control conditions separated from power-side conditions
- No code table is generalized across brands, and no parameter values are published here
- Fault availability depends on model and configuration; for example, some PowerFlex 525 faults do not apply to PowerFlex 523
- DC drive documentation is never applied to AC variable-frequency drives
- Internal repair of a sealed drive chassis is not offered; replacement may be the recommendation
- Regulated electrical work is performed only within KONGRA's legal license scope, or coordinated with properly licensed independent contractors
- KONGRA is independent and is not affiliated with, endorsed by or authorized by any manufacturer named here
What to send with your request
The more of this arrives up front, the more useful the first visit is.
- Exact drive model and catalogue number, and the motor nameplate
- The fault code or message as displayed, photographed
- When in the cycle it faulted, and how long the machine had been running
- What the motor drives, and the load at the time
- Any retained fault history visible on the normal display
These details are optional and help us prepare for your visit.
Manufacturer references
- Allen-Bradley PowerFlex 523 and 525 AC drive user manual 520-UM001O-EN-E (PDF)PowerFlex 523 and PowerFlex 525 only; publication 520-UM001O-EN-E (letter O), September 2025, 274 pages. Chapter 4, printed pages 159–166, consulted for fault types, fault categories and symptom material, and page 144 onward for controller display and fault-history behaviour. PowerFlex 523 does not include every fault listed for PowerFlex 525, and none of this material applies to other manufacturers' drives. A model-specific example, not a general code table.
Related drive and industrial pages
Frequently asked questions
The drive threw a fault. Does that mean the drive is defective?+
No. A fault means the drive detected a condition it is built to react to. That condition can be in the driven load, the mechanics, the motor, the incoming supply, the cooling, or the network — and sometimes in the drive itself. The code narrows the category; it does not name the failed part.
Can you give me a code table so I can look it up?+
Not a general one. Do not assume the same code has the same meaning across brands or model families; read the manual for the exact model. Fault availability depends on model and configuration; for example, some PowerFlex 525 faults do not apply to PowerFlex 523.
Should we reset it and see if it runs?+
Record first. Note the exact code, what the machine was doing at the moment it faulted, and any history the drive still shows, before anyone resets it. Repeated restarts add stress and can push older entries out of whatever history the controller keeps.
Do you open the drive and repair the electronics inside?+
No. A sealed drive chassis is not treated as a user-serviceable assembly here. The work is diagnosis of the drive in its installed context — supply, motor, load, cooling and control — and a written recommendation, which may be replacement of a unit rather than internal repair.