A drive fault code is a clue captured by a protective device. Preserve it before you clear it.
SURVIVAL RULE: Record the fault before reset.
Read the drive before resetting it
A VFD usually records a fault code or diagnostic state that disappears from the operator’s attention after reset. Before clearing anything, record the exact code, operating state, speed reference, load condition, and whether the event is repeatable. Drive faults are often protective reactions to something elsewhere.
An overcurrent fault during acceleration may indicate too short an acceleration time, a jammed load, motor/cable problem, or sudden torque demand. An undervoltage fault may point toward supply issues rather than the drive power stage.
Field habit: Photograph or write the fault display and timestamp before reset if site rules allow.
Common trap: Do not treat ‘reset worked’ as root cause.
Separate reference, enable, and power
For a drive to run, it usually needs power, no active protective fault, a run/enable command, and a valid speed or torque reference. These can come from terminals, network, PLC logic, or local keypad. Troubleshooting becomes easier when you determine which source is intended.
A drive display may show ready but zero frequency because the speed reference is missing. Another may show the correct reference but refuse to run because an external enable or safe-torque-off circuit is not satisfied.
Field habit: Check status words, terminal states, and reference values before changing parameters.
Common trap: Do not change control source or parameter groups unless you understand how the machine was designed.
Quick check
What should be true at this point in the sequence?
What evidence can prove or eliminate this section of the system?
What changed recently or only under the failing condition?
The drive is part of a motor system
A VFD cannot compensate for a failed motor bearing, damaged cable, poor grounding, contaminated cooling path, wrong motor data, or mechanical jam. Likewise, motor symptoms can come from incorrect drive setup. Diagnose drive, motor, cable, and load as one system.
If the drive faults only at high speed, consider load curve, cooling, cable insulation, resonance, and motor condition. If it faults immediately on run, the diagnostic direction may be different.
Field habit: Compare the failure condition with a known-good operating point and record motor current, speed, and fault history.
Common trap: Avoid replacing an expensive drive because the fault code mentions current or voltage without testing the surrounding system.
Parameter changes require discipline
Drive parameters can alter acceleration, protection, motor model, braking, communications, and safety-related behavior. A casual change may hide the symptom while creating another failure later. Before changing, record the original value, reason, authorization, and expected effect.
If a machine once worked with a 10-second acceleration and now trips unless changed to 30 seconds, the longer ramp may hide increasing mechanical load rather than solve it.
Field habit: Use backups or parameter records where available and restore known-good settings after uncontrolled changes.
Common trap: Never copy a complete parameter set from a similar-looking drive without confirming motor, option, firmware, and machine differences.
Quick check
What should be true at this point in the sequence?
What evidence can prove or eliminate this section of the system?
What changed recently or only under the failing condition?
Field Exercise
Record the normal run command source, reference source, current, and status for one VFD.
PART III
FLUID POWER, MECHANICS, AND NETWORKS