Code identifies protection
It narrows the failure family but does not identify a failed drive, motor or cable by itself.
Drive trip diagnosis
VFD Fault Codes: Treat the Code as a Protection Clue, Not a Parts Verdict
A drive fault code tells you which protection or diagnostic function operated. It rarely proves which component failed. The same overcurrent code can follow a shorted cable, seized load, wrong motor data or an acceleration ramp that demands more torque than the system can deliver. Reliable diagnosis preserves the first code and operating evidence, then proves one boundary at a time.
Fault names, thresholds, reset rules and parameter numbers are manufacturer-, model- and firmware-specific. The product uses a vendor-neutral D-01 training code and a simulated diagnosis bay; real equipment work requires the exact installed-drive manual, electrical safety procedure and machine risk controls.
Preserve trip
Record active and historical code, timestamp, run state, speed reference, current, DC bus and temperature.
Classify boundary
Decide whether evidence points first to supply, drive, motor/cable, mechanical load, control or environment.
Prove safely
Use authorised isolated measurements, inspection and controlled low-risk tests one hypothesis at a time.
Remove / recover
Correct the active cause, clear demand, reset once and prove normal operation under the original condition.
Preserve the first-changing evidence before power cycling. Secondary faults after the motor stops can distract from the initiating condition.
Answer first
How should you diagnose a VFD fault code?
Record the exact code and trip history before clearing it, then capture command source, speed reference, actual speed, output current, DC-bus voltage, temperature, load state and recent changes. Use the manufacturer manual to interpret that code on the installed model. Classify the likely boundary, make the equipment electrically and mechanically safe, perform one proving test, remove the active cause, clear run demand and reset according to the approved procedure. A successful reset is not proof of repair.
Context separates causes
Current, bus, temperature, speed, command and load immediately before the trip distinguish plausible hypotheses.
Reset ends diagnosis only after proof
Repeated resets can damage equipment, erase history and expose people to an unresolved fault.
Before reset or power cycle
Capture the trip snapshot while the drive still remembers the event
The first active fault and its measurements are usually more diagnostic than the cascade that follows a stop.
01
Identity / code
Drive model, firmware, active fault, historical order and timestamp define the manual and event.
02
Command / reference
Run source, run demand, direction, requested frequency and control mode show what was requested.
03
Electrical state
Output current, DC bus, input status and temperature identify the operated protection boundary.
04
Mechanical context
Actual speed, load, process condition and machine transition explain what the motor was doing.
Use the exact drive’s history and monitor features. Not every model stores the same fields or sample timing.
Do not begin with reset. Photograph or export the active code and history, including order. Record the full model number, firmware and relevant option cards because one manufacturer can use different meanings across product families. Note whether the event occurred on acceleration, steady running, deceleration, direction change, restart or idle. That operating phase can eliminate many generic cause lists.
Capture command and reference paths. A drive can trip after receiving an unexpected fieldbus command, missing analog reference or rapid direction change even when power wiring is healthy. Record local/remote mode, selected run source, selected speed source, requested frequency, actual frequency, control mode and active limits.
Preserve measured values available in the drive: phase or output current, DC-bus voltage, heatsink or power-module temperature, motor thermal estimate, line voltage status and torque estimate. Values may be filtered or calculated, so they guide the next test but do not replace approved electrical measurements where required.
Add machine context: product, load, jam state, valve or damper position, ambient temperature, recent maintenance, parameter download and time since startup. A fault that begins immediately after motor replacement has a different prior probability from one that appears only after two hours in a hot cabinet.
| Evidence | Record | Diagnostic use | Common loss |
|---|---|---|---|
| Drive identity | Manufacturer, family, rating, firmware, options | Selects the correct code definition and limits | Using a manual for a similar-looking model |
| Fault order | First active code and following codes | Separates initiator from consequences | Reset or power cycle clears the useful order |
| Command / reference | Source, direction, requested and actual speed | Finds control and handover causes | Only recording the final stopped state |
| Electrical values | Current, bus, line status, temperature | Routes supply, load, braking or thermal checks | Assuming displayed values are calibrated test measurements |
| Machine state | Load, transition, process and recent changes | Explains when torque or energy demand changed | Troubleshooting the drive outside the original condition |
Protection categories
Translate vendor code text into an electrical, thermal, mechanical or control question
Classification routes the next safe test; it does not authorize replacing the component named in the message.
01
Supply / DC bus
Undervoltage, overvoltage, phase loss, precharge or braking-energy evidence.
02
Output / motor
Overcurrent, ground fault, overload, current imbalance or stall evidence.
03
Thermal / environment
Drive, motor, resistor, cabinet temperature, cooling and duty evidence.
04
Control / communications
Command source, reference, fieldbus, feedback, parameter and internal diagnostic evidence.
Several families can interact. A supply dip can create undervoltage first and communication loss after the controller restarts.
Supply and DC-bus faults require attention to line quality and machine energy flow. Undervoltage can follow a supply dip, undersized source, loose connection or blown phase. Overvoltage during deceleration often indicates regenerated mechanical energy, an aggressive ramp or unavailable braking path—not excessive incoming voltage alone. Measure only under authorized procedures and compare with the exact drive limits.
Output and motor faults cover more than a failed motor. Overcurrent can arise from phase-to-phase or ground faults, incorrect wiring, a seized or suddenly loaded machine, wrong motor data, unstable control tuning or an acceleration demand beyond available torque. Isolate and test cable, motor and load using the site procedure; never megger through a connected drive unless the manufacturer procedure explicitly permits it.
Thermal faults need time and airflow context. Check ambient and cabinet temperature, fan operation, filters, heatsink contamination, switching frequency, carrier settings, motor current and duty. A drive that trips after a repeatable warm-up period points differently from an instantaneous trip at start. Do not defeat a temperature sensor or raise a thermal limit to keep production running.
Control and communication faults can leave healthy power hardware idle. Verify selected command/reference source, network connection state, control word, speed reference quality, encoder or process feedback and configured loss response. Preserve whether the drive stopped because communication failed or communication failed because the drive or upstream power disappeared.
| Family | First evidence | Proving boundary | Do not conclude |
|---|---|---|---|
| Undervoltage / phase loss | Line status, DC bus, contactor and other loads | Supply and connections under the event | The power module is failed |
| DC-bus overvoltage | Trip phase, decel time, load inertia, brake state | Regeneration and braking path | Incoming voltage is always too high |
| Overcurrent / ground fault | Current, speed, ramp, cable/motor/load state | Safely isolate electrical and mechanical boundaries | Replace the drive from code alone |
| Overload / stall | Current duration, torque, actual vs reference speed | Sizing, motor data, jam and acceleration demand | Raise current limit until it runs |
| Overtemperature | Temperature, time, airflow, duty and ambient | Cooling path and load over time | Resetting after cooldown is a repair |
| Communication / feedback | Connection, control word, quality, source selection | Network, sensor and configured loss behavior | The motor circuit caused the message |
Most misdiagnosed family
Separate instantaneous electrical current from sustained overload and mechanical stall
Timing, speed and current shape distinguish several conditions that share “too much current” in casual language.
01
Instant at enable
Suspect cable, motor insulation, wiring, power stage or severe parameter mismatch before load heating.
02
During acceleration
Compare ramp, inertia, load, boost, current limit and whether actual speed follows reference.
03
After sustained load
Compare RMS current, motor thermal model, cooling, duty and mechanical demand.
04
On one condition
Direction, cable movement, contactor state or process jam may reproduce a specific boundary.
The drive’s code definitions and stored trace decide which protection actually operated; these patterns organize hypotheses.
An instantaneous trip when output is enabled calls for a different test than a thermal overload after twenty minutes. Preserve whether the motor began turning. Inspect approved wiring changes, output contactors, cable damage and motor insulation after isolation. Confirm the drive is configured for the connected motor and supply. Do not repeatedly energize a suspected short to collect more data.
A trip during acceleration may come from excessive torque demand. Compare reference ramp and actual speed. If current reaches limit while speed fails to rise, inspect load, brake release, mechanical jam, motor sizing and motor data. Lengthening the ramp can reduce acceleration demand, but it is not a repair for a seized bearing or incorrectly connected motor.
Sustained overload evidence needs current over time, duty cycle and cooling. A self-cooled motor at low speed may overheat while current remains within a drive limit. The drive thermal model depends on correct motor nameplate data. Verify actual mechanical load and process changes before altering protection settings.
Ground-fault or earth-leakage codes require the manufacturer’s isolation and test procedure. Separate motor and cable only when safe and permitted, protect the drive from insulation-test voltage, and document each boundary result. Moisture, damaged cable and motor winding insulation can be intermittent with position or temperature.
Energy path
Read DC-bus faults in the direction energy was flowing
The bus falls when input energy disappears and rises when a decelerating load returns more energy than the drive can absorb or dissipate.
01
Incoming supply
Fuses, disconnects, contactors, phases, source impedance and voltage quality feed the rectifier.
02
Rectifier / precharge
Input conversion and precharge establish the DC bus before the inverter is enabled.
03
Inverter / motor
The drive converts bus energy to controlled motor voltage and frequency under load.
04
Regeneration / braking
Decelerating inertia can return energy to the bus for dissipation or regenerative handling.
Line, bus and mechanical evidence should agree. A code without the operating phase cannot show the direction of the energy imbalance.
For undervoltage, ask whether other equipment dipped, whether a line contactor opened, whether one phase or fuse was lost and whether the event occurred during high plant demand. Loose connections can appear only under current. Follow the authorized measurement procedure and consider that the drive display may disappear during the event, making an upstream recorder valuable.
For overvoltage, distinguish steady incoming voltage from a rise during deceleration. Record speed, decel command, ramp, inertia, DC bus and braking-unit state. Lengthening deceleration or using an appropriately engineered braking solution may be required, but the correct response depends on the machine stop requirement and manufacturer design.
Power cycling destroys the bus history on many systems and can make an intermittent supply issue vanish temporarily. Preserve the event, inspect other devices and correlate timestamps before isolating one drive. Repeated precharge or contactor cycling can also create its own wear and faults.
Time and signal context
Use warm-up curves and signal-source evidence for thermal and communication trips
Some drive faults are best diagnosed by a time trend rather than a static electrical reading.
01
Load / current
Shows whether thermal rise follows process duty, jam, repeated starts or low-speed torque.
02
Temperature / cooling
Shows warm-up rate, fan response, cabinet ambient and recovery after stop.
03
Command / reference
Shows local, terminal or fieldbus ownership and unexpected mode or reference changes.
04
Connection / feedback
Shows stale, lost or contradictory network, encoder and process signals.
Align timestamps and quality. A flat zero after connection loss is not proof the physical quantity became zero.
Trend temperature against current, speed and cabinet conditions. A blocked filter or failed fan may show normal starting followed by predictable heating. A process change may increase torque only at one recipe step. Check the manufacturer maintenance instructions before cleaning or replacing cooling components and respect stored-energy discharge time.
For communication faults, record network topology, drive identity, controller connection, update interval, control word, status word and the configured communication-loss action. Prove whether the run command disappeared before the trip, at the trip or because the upstream controller also faulted. Link lights alone do not prove cyclic application data.
Feedback faults require source and plausibility checks. Encoder supply, wiring, shielding, configuration and mechanical coupling can produce missing or contradictory speed. Process feedback used by a drive PID needs scale, quality and failure policy. A bad sensor can command the drive toward a limit while the power stage behaves exactly as instructed.
Controlled return
Reset only after the active cause and run demand are controlled
A reset acknowledges protection. It does not remove a short circuit, jam, overheated cabinet or invalid command.
01
Evidence saved
Keep code order and operating context before history or values change.
02
Cause removed
Prove the supply, motor, cable, load, cooling or control issue is no longer active.
03
Demand cleared
Remove run, direction and reference demands that could cause immediate restart.
04
Reset / prove
Reset once, observe readiness and run a controlled test under the original condition.
Some faults require power removal or service. Follow the exact manual and do not bypass lockout or stored-energy wait requirements.
Classify reset permission. Some faults are resettable from keypad, terminal or network after the condition clears. Others require power removal, cooldown, hardware service or qualified inspection. Automatic reset can be appropriate only for explicitly assessed transient conditions with controlled restart. It is hazardous when a returning drive can move equipment unexpectedly.
Clear every command path before reset: local keypad command, terminal input, fieldbus control word, maintained two-wire circuit and PLC latch. Confirm the machine can restart without trapped material, personnel exposure or an invalid sequence. Restore guards and safety functions according to the site procedure.
After reset, run at a controlled condition and watch the evidence that separated the cause. Then reproduce the original load, ramp, temperature or network transition where safe. Verify that current, bus, speed and temperature remain within the approved envelope and the code does not recur. Close with the corrected parameter or hardware record and fault-history attachment.
- Never use repeated resets as a diagnostic method for suspected electrical faults.
- Verify all local, terminal and network run demands before clearing the trip.
- Prove the repair under the condition that originally caused the event.
- Record the as-left parameters, hardware change and test evidence.
Training workflow
Practise the evidence sequence in a vendor-neutral VFD diagnosis bay
A simulator can teach hypothesis order and measurement relationships without claiming parity with a real manufacturer code.
01
Baseline
Record healthy run source, reference, speed, current, bus, temperature and load.
02
Inject one fault
Apply a named supply, load, thermal or control condition and preserve the first code and values.
03
Choose boundary test
Use the evidence to select one next measurement or isolation step.
04
Repair / repeat
Remove the condition, reset correctly and rerun the same operating point.
Keep motor, load and command constant while changing one injected condition so the diagnostic difference remains interpretable.
Begin with the healthy baseline. Select the run and reference source, operate at a known frequency and load, then record the simulated current, DC bus, temperature and status. Without a baseline, a learner may call any large-looking number abnormal. State the acceptance envelope before injection.
Inject one condition and write down the first code before changing parameters. Compare actual speed with reference, current with load, bus with acceleration/deceleration phase and temperature with elapsed duty. Choose the likely boundary and explain which alternate causes remain plausible.
Remove the injected condition, clear run demand and reset. Repeat the same operating point. The pass condition is restored evidence, not merely a blank fault display. Transfer the method—not the training code—to real equipment, then use the manufacturer manual and approved testing procedure.
Related technical cluster
Continue through the connected PLC evidence path
These are the closest supporting owners and product surfaces. Each link advances a specific part of the same engineering task instead of sending you to a generic content index.
Interactive VFD commissioning simulatorOperate commands, references, control modes, parameters, trips and modeled motor response.VFD current limit and stall protectionCompare current limiting, speed error, torque demand and overload evidence.VFD ramp, coast and braking stop modesSee how deceleration choice changes current, torque and DC-bus behavior.VFD run-command source diagnosisSeparate keypad, terminal and fieldbus ownership from speed reference.Motor-control circuit troubleshooting simulatorTrace command, contactor, overload and physical feedback outside the drive.PLC and drive signal-path diagnosisUse first disagreement and controlled proving tests across automation boundaries.
Verified product surface
What you can practise here today
The shipped VFD simulator has a function-lab route for the vendor-neutral D-01 diagnosis lesson and exposes modeled motor, load, speed, current, DC bus, temperature and control behavior.
Fault injection
The diagnosis bay can introduce controlled training faults so learners compare healthy and failing evidence.
Drive and motor signals
Modeled frequency, current, bus, temperature, command and load state support boundary-based reasoning.
Reset workflow
The lesson connects active condition removal, cleared command and observable return to operation.
Vendor-neutral codes
Stable simulator codes avoid pretending to be ABB, Danfoss, Rockwell, Siemens or another model’s parameter map.
Product boundary
The browser model is educational. It does not emulate a specific drive power stage, protection thresholds, manufacturer code table, motor insulation, harmonics, EMC, field measurements, safety functions or certified fault response. Real diagnosis requires qualified personnel, the exact installed-drive manual, safe isolation, stored-energy controls and approved test instruments.
Answer-engine questions
Direct answers to the questions engineers ask
What does a VFD fault code mean?
It identifies a protection or diagnostic condition recognized by that drive. It narrows the fault family but usually does not prove which component or setting caused it.
Should I reset a VFD fault immediately?
No. Preserve the active and historical code plus operating values first. Remove the active cause and clear run demand before resetting according to the exact manual and site procedure.
What causes a VFD overcurrent fault?
Possible causes include cable or motor faults, ground faults, a seized or suddenly loaded machine, wrong motor data, unstable control settings or an acceleration demand beyond available torque.
What causes VFD DC-bus overvoltage?
A common pattern is regenerative energy during aggressive deceleration of an inertial load, though high supply voltage or braking-system faults may also apply. Use the event phase and bus evidence.
What causes a VFD undervoltage fault?
Supply dips, phase or fuse loss, loose connections, contactor problems, weak sources or precharge issues may lower the DC bus. Correlate line and bus evidence with other equipment.
Can a mechanical jam cause a VFD trip?
Yes. A jam or brake that fails to release can prevent acceleration, increase current and activate current limit, stall, overload or overcurrent protection depending on the drive.
How do you troubleshoot an intermittent VFD fault?
Trend code order, command, reference, speed, current, bus, temperature, connection and process state with aligned timestamps, then test the first boundary that changes before the trip.
Can I insulation-test a motor while it is connected to a VFD?
Do not assume so. Isolate the drive and follow the manufacturer and site test procedure; insulation-test voltage can damage connected electronics.
When is automatic VFD fault reset acceptable?
Only for explicitly assessed transient conditions with controlled restart, limited attempts and a proven safe machine state. It is not a general remedy for unresolved electrical or mechanical faults.
Are the simulator VFD codes manufacturer codes?
No. The simulator uses stable vendor-neutral training codes. Exact codes, thresholds, reset rules and parameters must come from the installed drive manual and firmware.
Primary sources
Check the standard and vendor documentation
This guide separates transferable engineering practice from product-specific behavior. Use the primary sources below for exact standard wording, target-controller support, firmware behavior and production design decisions.
- Rockwell PowerFlex 520-series user manualOfficial manufacturer manual with fault, diagnostic, parameter and safe-service guidance for the named family.
- Siemens SINAMICS G120 function manualOfficial function documentation for drive behavior and diagnosis on the named family.
- Danfoss VLT AutomationDrive programming guideOfficial programming and diagnostic reference for the named drive family.
- ABB ACS580 manual directoryOfficial source directory for ACS580 hardware, firmware and safety documentation.
Turn the guide into evidence
Preserve the first trip, then prove one boundary
Run the D-01 fault lab once healthy and once with a single injected condition. Explain the next test from current, bus, temperature, speed, command and load evidence before pressing reset.