Drives are excellent witnesses but imperfect detectives. Their alarms describe electrical or operating conditions; they do not always identify the physical root cause.
Five Principles to Use in the Field
- Record the exact code and context. A fault after acceleration is different from the same code at steady speed. Note speed, load, direction, product, and whether the fault is repeatable.
- Separate drive, motor, and machine. Use safe isolation and testing to determine whether the issue follows the drive, the motor, the cable, or the mechanical load.
- Check supply quality. Phase loss, undervoltage, loose terminals, and DC bus problems can create faults that appear to be downstream.
- Use current as process evidence. Phase current, imbalance, and current trend can reveal mechanical binding, overload, or wiring problems.
- Do not erase parameters casually. A factory reset can transform a known fault into a commissioning project. Back up and document before changing configuration.
Pressure Mistakes to Avoid
- Replacing a VFD because it reports overcurrent.
- Megger-testing a motor through a connected drive.
- Changing acceleration time to hide a mechanical jam.
- Ignoring motor cooling and low-speed duty during repeated restarts.
A Practical Breakdown Method
- Capture fault history and operating state.
- Check incoming power and drive health.
- Inspect motor cable and connections.
- Assess the mechanical load and freedom of movement.
- Measure current and compare phases where appropriate.
- Make one controlled change or test at a time and verify under real load.
Scenario: A mixer drive trips only after twenty minutes. The code indicates overload. Cold tests appear normal. Trend data shows current slowly rising as the gearbox warms. Inspection reveals low gearbox oil and increasing friction. The drive was protecting the system correctly; replacing it would have achieved nothing.
Train This Before the Next Callout
Choose one critical machine you know and apply the ideas from this chapter while it is healthy. For motors and vfds: read the symptom, not just the fault code, write down the normal sequence, the key evidence you would want to preserve, and the first three checks you would make if the machine stopped. Then compare your plan with the electrical drawings, PLC diagnostics, maintenance history, and the experience of another technician. A ten-minute rehearsal in daylight can remove several minutes of confusion at night.
3 AM Rule: A drive fault code is a measurement of what the drive experienced, not a verdict on which component failed.
Chapter Checklist
- Can I describe the symptom without naming an unproven cause?
- Have I preserved the evidence that could disappear after a reset or restart?
- Do I know which system boundary I am testing next and why?
- Have I kept safety controls and temporary changes visible and controlled?
- Can I explain my current facts, hypothesis, and next action in under thirty seconds?