VFD Fundamentals, Commissioning & Trip Diagnosis
Learn how a variable frequency drive controls an AC motor, how to commission a drive without losing design intent, and how to separate supply, command, drive, motor and mechanical-load evidence when a trip occurs.
Prerequisites and learning outcomes
This guide assumes basic familiarity with three-phase motors, control circuits and approved electrical-safety practices. It does not authorize electrical work. After completing it, you should be able to explain the drive power path, trace a missing run command, record useful trip evidence, plan a controlled commissioning test and identify when OEM or specialist support is required.
How a VFD controls a motor
Most industrial drives use three main power stages. A rectifier converts incoming AC to DC, a DC bus smooths and stores energy, and an inverter switches that DC to create a controlled output for the motor. The drive changes output frequency to influence motor speed and coordinates output voltage and current according to its control mode, motor data and configured limits.
The drive is only one part of the operating system. A complete diagnosis considers five paths:
- Supply path: incoming isolator, protection, phase condition, terminals and drive input.
- Command path: local/remote selection, run command, permissives, interlocks, emergency stops and communications.
- Reference path: keypad setpoint, analogue signal, preset speed, PLC value or network reference.
- Output path: drive output, motor cable, motor windings, earthing and connection arrangement.
- Mechanical and process path: coupling, bearings, fan or pump, dampers or valves, product load and process demand.
Preserve trip evidence before resetting
Do not begin with repeated resets or parameter changes. Record the exact alarm text or code, timestamp, running frequency, current, DC-bus or input information available on the display, operating mode, speed reference, load condition and recent machine event. Save the event-history sequence when the drive provides one. The first alarm may identify the initiating condition; later alarms can be consequences of the stop.
| Observed condition | Evidence to collect | Diagnostic direction |
|---|---|---|
| Trip during acceleration | Acceleration time, current trend, motor data, load release and brake status | Excess starting demand, restricted load, incorrect motor data or unsuitable ramp |
| Trip during deceleration | Deceleration time, DC-bus trend, braking equipment and load inertia | Regenerative energy, short ramp or braking-system issue |
| Trip after steady running | Current, frequency, temperature, cooling condition and process load | Overload, ventilation, ambient, supply or intermittent mechanical condition |
| Drive ready but motor stopped | Run status, permissives, interlocks, local/remote state and reference value | Command or reference path rather than an assumed power-stage failure |
| Unequal or abnormal measurements | All phase readings under a known condition and instrument suitability | Supply, connection, motor, waveform or measurement-method investigation |
Alarm names and thresholds are manufacturer- and model-specific. Use the exact installed revision’s OEM manual; do not infer a universal cause from a generic label or copy settings from another machine.
Common trip categories
- Overcurrent: investigate the operating point, acceleration, motor data, cable and motor condition, and mechanical restriction before changing any limit.
- DC-bus overvoltage: examine deceleration, load inertia, braking arrangement and supply condition. A longer ramp is not automatically acceptable if the process requires a controlled stop.
- Undervoltage or input loss: verify the supply event, phase condition, terminals, upstream equipment and control-power behavior.
- Overtemperature: check filters, heat sinks, fans, enclosure ventilation, ambient temperature, switching/loading history and installation clearances.
- Earth or ground fault: treat this as an electrical-safety condition. Follow the OEM-approved isolation and test method for the drive, cable and motor.
- Communication or external fault: verify network health, control power, PLC/interlock status and the source that asserted the external trip.
Controlled VFD commissioning checklist
Commissioning should demonstrate that the installed drive, motor, protection, control logic and driven equipment match the approved design. Record results so a future technician has a known good baseline.
- Confirm documentation: approved drawings, drive and motor details, control narrative, OEM instructions, parameter list, risk assessment and test plan.
- Inspect the installation: rating and enclosure, ventilation clearances, contamination control, earthing, cable routing, screening/termination method, motor connection and braking components where fitted.
- Verify isolation and readiness: apply approved PTW/LOTO and test-before-touch requirements. Confirm mechanical work is complete, guards are restored and the driven system is ready for the planned test.
- Enter verified motor data: use the installed motor nameplate and OEM guidance. Do not guess current, voltage, frequency, speed or power values.
- Review control parameters: command source, speed-reference source, minimum and maximum limits, ramps, stop mode, current/torque limits, digital and analogue I/O, communications and restart behavior.
- Perform the OEM-approved identification routine: only when permitted by the motor, load and process arrangement. Secure the area against unexpected rotation.
- Prove direction and controls at low risk: use the approved test plan to confirm rotation, start/stop, local/remote selection, permissives, interlocks, emergency functions and feedback indications.
- Test across the authorized operating range: record stable voltage/current or drive-displayed values, frequency, reference, load/process response, vibration or abnormal noise, cooling and relevant process variables.
- Verify abnormal-state behavior: prove only those alarms, interlocks and safe-stop functions included in the approved commissioning method. Never create an uncontrolled hazardous condition to test a trip.
- Close out: save an approved parameter backup, record firmware and configuration revisions, label the asset, document baseline readings and obtain the required handover acceptance.
Evidence-led troubleshooting sequence
- Define the symptom and the last known normal operating state.
- Make the system safe using approved site and OEM procedures.
- Capture alarms, commands, references and operating evidence before disturbing the condition.
- Decide which path—supply, command, reference, output or load—best fits the evidence.
- Test one hypothesis at a time with a suitable method and instrument.
- Correct the confirmed cause without bypassing protection or concealing the initiating condition.
- Restore safeguards, run the authorized functional test and compare results with the baseline.
- Document the cause, action, verification and any follow-up monitoring.
Control parameter changes
A parameter change is an engineering change, not a convenient reset method. Record the previous value, proposed value, reason, technical authority, date and verification result. Check the effect on protection, stopping, process performance, motor heating and upstream/downstream controls. Maintain a recoverable approved backup and avoid copying a complete parameter set between assets unless the equipment, motor, options, firmware and application have been verified as equivalent.
VFD preventive maintenance
Build maintenance tasks from the drive OEM’s instructions, installation environment and failure history. Typical checks include enclosure condition, contamination, filters, heat sinks, cooling fans, terminal condition where approved, event logs, control-panel ventilation, corrosion or moisture, and trend comparison under a repeatable operating condition. Replacement intervals for fans, capacitors or other life-limited components must come from the applicable OEM guidance and duty conditions—not a universal interval.
For critical drives, retain controlled backups, spare-part compatibility details, firmware/configuration records and baseline operating evidence. Trend recurring alarms rather than clearing them from the history without review.