18. VFD Technician Field Guide: Startup, Troubleshooting, Replacement, and Best Practices (18 of 19)
Introduction
A Variable Frequency Drive is one of the most important devices an automation technician will work with in the field.
A VFD controls motor speed, direction, acceleration, deceleration, torque behavior, protection, feedback, and communication. It may be controlled locally from a HIM, remotely from terminal wiring, through analog signals, or over an industrial network from a PLC.
Because a VFD is both a power device and a programmed control device, troubleshooting it requires more than simply replacing hardware or pressing reset.
A professional technician should understand:
Safety
Motor nameplate data
VFD parameters
Power wiring
Control wiring
Grounding
Start source
Speed reference
Feedback
Fault codes
Backups
PLC/HMI integration
Communication
Application behaviorThis final guide summarizes the most important VFD concepts from the series into one practical field reference.
1. Safety First: Before Touching a VFD
Before working on a VFD, remember this:
A stopped drive is not automatically a safe drive.
A blank display is not automatically a safe drive.VFDs contain high-voltage components and DC bus capacitors that can remain charged after power is removed.
The PowerFlex manual warns that the drive contains high-voltage capacitors that require time to discharge after removing mains power, and that dark display LEDs do not mean the capacitors are discharged. It also states that only qualified personnel familiar with adjustable frequency AC drives should install, start up, or maintain the system.
Safety Checklist
[ ] Notify affected personnel.
[ ] Stop the machine normally.
[ ] Follow Lockout/Tagout.
[ ] Isolate incoming power.
[ ] Wait the manufacturer-required DC bus discharge time.
[ ] Verify absence of voltage with a properly rated meter.
[ ] Check for separate control power.
[ ] Check for external 24 VDC circuits.
[ ] Check for remote start commands.
[ ] Confirm the machine cannot start unexpectedly.Important Safety Reminder
Display OFF does not mean DC bus discharged.
Always verify before touching.2. Understand the Basic VFD Power Flow
A VFD is not simply a voltage controller. Internally, it converts power.
Basic internal flow:
AC Input
↓
Rectifier
↓
DC Bus
↓
DC Bus Capacitors
↓
Inverter / IGBTs
↓
Controlled AC Output to MotorThe VFD training material explains that a VFD first converts incoming AC power into intermediate DC power using a rectifier bridge, then controls voltage and frequency to operate the motor.
Simple Explanation
AC in → DC inside → controlled AC outWhy This Matters
Many faults are connected to one section of the VFD:
| VFD Section | Common Problems |
|---|---|
| Input / Rectifier | Power loss, undervoltage, phase loss |
| DC Bus | Overvoltage, undervoltage, regeneration |
| Capacitors | Stored energy, ripple, aging |
| Inverter | Overcurrent, ground fault, output short |
| Control Board | Parameters, I/O, communication |
| Cooling System | Overtemperature, fan failure |
3. Match the VFD to the Motor
A VFD must be configured with the correct motor nameplate data.
The drive does not automatically know the motor connected to it.
Important motor data:
Motor voltage
Motor FLA
Motor frequency
Motor RPM
Motor horsepower / kW
Service factor
Wiring configuration
Inverter-duty rating, if applicablePowerFlex parameters include values such as Motor NP Volts, Motor NP Hertz, and Motor OL Current, which are used to match the drive to the motor and protect it correctly.
Critical Rule
Do not set motor current based only on drive size.
Set motor overload/current based on the motor nameplate FLA.Motor Data Checklist
[ ] Motor voltage entered correctly.
[ ] Motor FLA entered correctly.
[ ] Motor frequency entered correctly.
[ ] Motor RPM documented.
[ ] Motor HP/kW documented.
[ ] Motor wiring matches voltage.
[ ] Drive output current rating is adequate.
[ ] Motor is suitable for VFD operation.4. Know the Core VFD Parameters
A VFD may have hundreds of parameters, but a technician should always know the basic ones.
| Parameter Group | What It Controls |
|---|---|
| Motor Data | Motor voltage, FLA, frequency |
| Speed Limits | Minimum and maximum frequency |
| Start Source | Who starts the drive |
| Speed Reference | Who controls speed |
| Stop Mode | How the drive stops |
| Accel/Decel | How fast speed changes |
| Digital Inputs | Terminal input functions |
| Relay Outputs | Feedback/status functions |
| Analog Inputs | Speed reference or feedback |
| Communication | Network address, data rate, loss action |
| Fault Reset | How faults are cleared |
| Protection | Current limit, overload, braking |
PowerFlex documentation organizes parameters into Display, Basic Program, and Advanced Program groups, including parameters for motor data, start source, stop mode, speed reference, acceleration, deceleration, digital inputs, relay outputs, and communication.
Field Rule
Parameters define drive behavior.
Wrong parameters create wrong machine behavior.5. Start Source vs Speed Reference
This is one of the most important VFD troubleshooting concepts.
Start Source = Who tells the drive to run?
Speed Reference = Who tells the drive how fast to run?Example:
Start Source = Terminal Block
Speed Reference = Analog InputThat means a hardwired input starts the drive, but an analog signal controls speed.
Another example:
Start Source = Communication
Speed Reference = CommunicationThat means the PLC controls both run command and speed over a network.
PowerFlex documentation explains that the start command is defined by Start Source, while the speed reference is defined separately by Speed Reference.
Troubleshooting Question
When a drive does not respond, ask:
Is the drive configured to listen to the correct command source?6. 2-Wire vs 3-Wire Control
VFD terminal control is commonly configured as 2-wire or 3-wire.
2-Wire Control
Run signal ON = Motor runs
Run signal OFF = Motor stopsBest for:
PLC output
Maintained selector switch
Relay command
Automated control3-Wire Control
Press Start = Motor runs
Press Stop = Motor stopsBest for:
Local pushbutton stations
Standalone panels
Traditional starter-style controlPowerFlex troubleshooting guidance states that 2-wire control requires Run Forward, Run Reverse, or Jog input, while 3-wire control requires Start and Stop inputs.
Important
2-wire maintained commands may restart the drive when a stop condition clears.
Always verify restart behavior.7. Power Wiring, Control Wiring, and Grounding
A good VFD installation protects the drive, motor, and control system.
The PowerFlex manual states that many start-up difficulties are caused by incorrect wiring, and that wiring instructions should be read and understood before installation.
Power Wiring Checks
[ ] Input voltage matches drive rating.
[ ] Branch protection is correct.
[ ] Input terminals are tight.
[ ] Motor output wiring is correct.
[ ] Motor ground is connected.
[ ] PE safety ground is connected.
[ ] Motor cable is suitable for VFD use.
[ ] No capacitors installed on VFD output.
[ ] Motor is not meggered while connected to drive.Control Wiring Checks
[ ] Stop input present.
[ ] Enable input present, if required.
[ ] SNK/SRC setting matches wiring.
[ ] Digital common is correct.
[ ] Analog input type is correct.
[ ] Analog shield is terminated correctly.
[ ] Relay output function is correct.
[ ] Communication cable is correct.Grounding Reminder
Safety Ground ≠ Digital CommonThe VFD training material states that I/O terminals labeled Common are not safety grounds; they are shared source terminals.
8. Acceleration, Deceleration, Coast, Ramp, and Braking
A VFD controls how a motor starts and stops.
Acceleration
Acceleration = controlled speed increaseIf acceleration is too fast, the drive may trip on overcurrent or motor stalled fault.
Deceleration
Deceleration = controlled speed decreaseIf deceleration is too fast on a high-inertia load, the motor may regenerate energy back into the DC bus and cause overvoltage.
The PowerFlex troubleshooting table notes that overvoltage can be caused by motor regeneration and recommends extending deceleration time or installing dynamic braking.
Stop Modes
| Stop Mode | Basic Meaning |
|---|---|
| Coast Stop | Drive output removed, motor freewheels |
| Ramp Stop | Drive controls slowdown |
| DC Brake | Drive injects DC braking torque |
| Dynamic Braking | Braking resistor dissipates regenerated energy |
Technician Rule
Start problem → check accel time, load, current limit.
Stop problem → check decel time, stop mode, regeneration, braking.9. HIM: Your Direct Window into the Drive
The HIM, or Human Interface Module, allows direct access to the VFD.
A HIM may be used to:
View parameters
View output frequency
View output current
View DC bus voltage
View fault codes
Change parameters
Reset faults
Control locally, if enabled
Upload/download parameters, if CopyCat is supportedPowerFlex documentation lists remote HIM options with LCD display, digital speed control, full numeric keypad options, and CopyCat capability on supported modules.
HIM vs HMI
HIM = direct drive interface
HMI = machine/operator interfaceHIM Troubleshooting Values
Output Frequency
Commanded Frequency
Output Current
DC Bus Voltage
Drive Status
Control Source
Digital Input Status
Fault CodeWarning
Do not press Start from the HIM unless the machine is safe to run.10. Backups Are Not Optional
A VFD replacement is not complete without the correct parameters.
Backup methods include:
HIM CopyCat
DriveTools SP
DriveExplorer
Connected Components Workbench
Manual parameter record
Photos and documentationPowerFlex documentation states that DriveExplorer can save, restore, print, compare, edit, upload, and download parameters, while DriveTools SP supports online/offline programming and parameter editing.
Backup Rule
A VFD without its parameters is just a box with factory defaults.Backup Checklist
[ ] Upload parameters if software is available.
[ ] Use HIM CopyCat if supported.
[ ] Record motor nameplate data.
[ ] Record start source.
[ ] Record speed reference.
[ ] Record accel/decel.
[ ] Record stop mode.
[ ] Record I/O functions.
[ ] Record communication settings.
[ ] Take wiring photos.
[ ] Save final as-left backup.11. Replacing a VFD Professionally
A VFD replacement should follow a process:
Safety → Document → Backup → Remove → Install → Restore → Verify → Test → SaveBefore Removal
[ ] Follow LOTO.
[ ] Verify zero energy.
[ ] Identify old drive.
[ ] Identify motor.
[ ] Take wiring photos.
[ ] Backup parameters.
[ ] Record fault history.
[ ] Verify replacement compatibility.After Installation
[ ] Restore parameters.
[ ] Verify motor data.
[ ] Verify start source.
[ ] Verify speed reference.
[ ] Verify I/O.
[ ] Verify communication.
[ ] Test direction.
[ ] Test local mode, if allowed.
[ ] Test auto mode.
[ ] Verify HMI feedback.
[ ] Save as-left backup.Important
Do not replace a VFD using factory defaults.12. Common VFD Faults
VFD faults are information. Do not reset blindly.
The VFD training material explains that the drive monitors its condition and uses keypad fault codes and indicators to notify the technician when a fault occurs.
Common Fault Categories
| Fault | Think About |
|---|---|
| Power Loss | Input power, fuses, breaker, terminals |
| Undervoltage | Low line voltage, phase loss, sag |
| Overvoltage | Decel too fast, regeneration, braking |
| Motor Stalled | Load jam, accel too short, current limit |
| Motor Overload | Motor FLA, load, cooling |
| Overtemperature | Fan, heatsink, cabinet cooling |
| Overcurrent | Short, load jam, accel, motor cable |
| Ground Fault | Motor insulation, cable, moisture |
| Analog Input Loss | 4–20 mA, 0–10 V, wiring, scaling |
| Communication Loss | Cable, adapter, IP/node, timeout |
Troubleshooting Flow
Fault Code → When It Happened → What the Drive Saw → Field Check → Corrective Action → Safe RestartGolden Rule
Do not just reset the fault.
Use the fault to find the cause.13. PLC Control of a VFD
A PLC can control a VFD using hardwired I/O or communication.
Hardwired Control
PLC DO → VFD Run Input
PLC AO → VFD Speed Reference
VFD Relay Output → PLC DI Running/Faulted
VFD AO → PLC AI Frequency/Current FeedbackNetwork Control
PLC Command Word → VFD
PLC Speed Reference → VFD
VFD Status Word → PLC
VFD Fault Code → PLC
VFD Feedback Data → PLCPowerFlex communication documentation shows command bits for stop, start, jog, clear faults, direction, accel/decel selection, and frequency source selection. It also shows status bits for ready, running, accelerating, decelerating, alarm, faulted, and at reference.
Command vs Feedback
Command = What the PLC asks for.
Feedback = What the drive actually reports.Important HMI Rule
Do not use PLC command as running status.
Use real VFD feedback when available.14. Communication Basics
When using communication, verify:
[ ] Correct protocol.
[ ] Correct IP or node address.
[ ] Correct baud/data rate.
[ ] Correct communication format.
[ ] Correct Start Source.
[ ] Correct Speed Reference.
[ ] Correct command word mapping.
[ ] Correct status word mapping.
[ ] Correct speed scaling.
[ ] Correct fault code reading.
[ ] Correct communication loss action.PowerFlex communication setup includes parameters for communication data rate, node address, communication loss action, communication loss time, and communication format.
Communication Loss Question
If communication is lost, should the drive fault, stop, coast, ramp, hold speed, or continue?That answer must be defined by the application and safety requirements.
15. Fans and Pumps
Fans and pumps are common VFD applications because speed control can improve process control and reduce energy use.
PowerFlex 400 documentation describes fan and pump features including Hand-Off-Auto, PID control, damper control, fire/life safety integration, analog I/O, relay outputs, and communication options.
Basic Fan/Pump Control Loop
Setpoint → PID Controller → VFD Speed → Motor → Fan/Pump → Process FeedbackCommon Feedback Signals
Pressure
Flow
Level
Static pressure
TemperatureTechnician Rule
Verify the drive.
Verify the motor.
Verify the process sensor.
Verify the mechanical path.
Verify the PID loop.16. Professional VFD Troubleshooting Process
When responding to a VFD issue, use this process:
1. Make the machine safe.
2. Record the symptom.
3. Record the fault code.
4. Identify when the fault happened.
5. Check display values.
6. Check input power.
7. Check motor/load condition.
8. Check control signals.
9. Check parameters.
10. Check feedback.
11. Correct the cause.
12. Test safely.
13. Document the result.Questions to Ask
Did it happen at power-up?
Did it happen during acceleration?
Did it happen during steady run?
Did it happen during deceleration?
Did it happen after replacement?
Did someone change parameters?
Did the process load change?
Is the VFD actually receiving the command?
Is the drive returning feedback?17. Technician Field Checklist
Before Startup
[ ] Safety procedures followed.
[ ] Drive model verified.
[ ] Input voltage verified.
[ ] Branch protection verified.
[ ] Motor nameplate data recorded.
[ ] Motor wiring verified.
[ ] Grounding verified.
[ ] Control wiring verified.
[ ] Stop/Enable input verified.
[ ] SNK/SRC verified.
[ ] Parameters entered.
[ ] Backup saved.Before Troubleshooting
[ ] Exact fault code recorded.
[ ] Fault timing identified.
[ ] Display values checked.
[ ] Input voltage checked.
[ ] Output current checked.
[ ] DC bus voltage checked.
[ ] Motor/load checked.
[ ] Control source checked.
[ ] Speed reference checked.
[ ] Feedback checked.Before Replacement
[ ] Old drive identified.
[ ] Motor identified.
[ ] Fault history reviewed.
[ ] Parameter backup uploaded.
[ ] HIM CopyCat used, if supported.
[ ] Wiring photos taken.
[ ] Replacement compatibility verified.
[ ] Critical parameters documented.After Replacement
[ ] Parameters restored.
[ ] Motor data verified.
[ ] Start Source verified.
[ ] Speed Reference verified.
[ ] Direction verified.
[ ] Local mode tested.
[ ] Auto mode tested.
[ ] PLC/HMI feedback verified.
[ ] Final as-left backup saved.18. Common Mistakes to Avoid
[ ] Resetting faults without recording the code.
[ ] Assuming every fault means the drive is bad.
[ ] Replacing a drive without backup.
[ ] Using factory defaults after replacement.
[ ] Forgetting motor FLA.
[ ] Confusing Start Source with Speed Reference.
[ ] Using PLC command as running feedback.
[ ] Not checking Stop/Enable input.
[ ] Ignoring SNK/SRC wiring.
[ ] Not checking analog scaling.
[ ] Ignoring communication loss action.
[ ] Not verifying motor rotation.
[ ] Not saving final documentation.Simple Technician Explanation
A simple way to summarize VFD work is:
A VFD controls the motor, but the parameters control the VFD.
The PLC may command the VFD, but feedback confirms what actually happened.
Faults tell the story, and backups protect the machine.Or even shorter:
Configure it correctly.
Wire it correctly.
Command it correctly.
Verify feedback.
Back it up.Final Thoughts
Understanding VFDs is a major skill for any automation technician.
A good VFD technician does not just replace drives or reset faults. A good technician understands how the drive fits into the complete system:
Power system
Motor
Mechanical load
Control wiring
PLC logic
HMI feedback
Communication
Parameters
Fault history
Process behaviorThe strongest VFD mindset is:
Safety first.
Understand the application.
Verify the wiring.
Verify the parameters.
Read the fault.
Check the feedback.
Document everything.When you follow that process, VFD troubleshooting becomes logical, professional, and repeatable.