How to Commission a Variable Frequency Drive Step by Step

A variable frequency drive that is wired correctly but commissioned poorly is not a functional drive. It is a liability, one that may run the motor without immediate complaint but will generate nuisance trips, damage insulation, fail to respond to control signals correctly, or operate outside its protective envelope until something fails. Commissioning is where the hardware investment either pays off or quietly begins to fail.

The commissioning procedure is not a formality. It is the technical handover between installation and operation, and every step omitted during this phase eventually reappears as a fault during production.

This guide covers the complete VFD commissioning sequence from pre-energization checks through parameter configuration, motor run-up, and system integration verification, grounded in the procedures that experienced automation engineers follow on actual installations.

---

What VFD Commissioning Actually Involves

Commissioning a variable frequency drive (VFD) is the structured process of verifying installation integrity, configuring operational parameters to match the motor and mechanical load, testing protective functions, and confirming correct response to control signals from PLCs, SCADA systems, or local operator interfaces. It spans everything from insulation resistance testing before first energization to a full-load run under process conditions before handover.

A drive that runs is not the same as a drive that is commissioned. The distinction matters when the first process upset occurs.

The procedure applies across all major drive families: Siemens SINAMICS G120, ABB ACS880, Allen-Bradley PowerFlex 755, Danfoss FC302, Schneider Electric Altivar 630, and Yaskawa GA800 all follow the same commissioning logic even though their keypad navigation and parameter numbering differ.

---

Pre-Energization Checks

Never energize a VFD installation before completing the pre-power checks. The cost of a missed insulation fault at this stage is measured in damaged drive components. The cost of missing it after energization is measured in unplanned downtime and component replacement.

Incoming Supply Verification

Confirm that the incoming supply voltage, phase configuration, and frequency match the drive's nameplate rating before connecting power. Applying 480V to a 400V-rated drive, or connecting a single-phase supply to a three-phase input, causes immediate and irreversible damage to the rectifier section. Check the supply with a calibrated multimeter at the terminal strip, not at the upstream breaker, to account for any wiring errors between the panel and the drive.

Verify that the upstream protective device, whether a fused disconnect, MCCB, or combination motor controller, is correctly rated for the drive's input current. Undersized protection creates nuisance tripping during the drive's inrush on first power-up. Oversized protection creates a safety gap if an internal fault occurs.

Motor Cable Insulation Testing

The motor cable must be disconnected from the drive output terminals before performing insulation resistance testing. Testing an insulation resistance (IR) on motor cables with the cable still connected to the drive exposes the IGBT output stage to the megohmmeter test voltage, which exceeds the IGBTs' maximum collector-emitter voltage rating and can cause latent damage that presents as premature IGBT failure weeks later.

With the cable disconnected at the drive, apply the megohmmeter between each phase conductor and ground at 500V DC for standard 400V applications. A reading below 1 megohm indicates a cable insulation fault that must be resolved before proceeding. After IR testing, reconnect the motor cables at the drive output terminals, verifying phase sequence against the motor's intended rotation direction.

Ground Continuity and Shielding

Confirm that the motor frame earth is continuous back to the panel earth bus and that the supply earth is present and correctly landed. Cable shield terminations, particularly for the motor cable shield, must be terminated at the drive end to the PE terminal and left unterminated at the motor end in single-point grounding arrangements. Double-terminating a motor cable shield creates a ground loop that carries high-frequency common-mode current back through the control cable routing, generating noise that affects analog input signals and encoder feedback.

---

Initial Power-Up and Basic Configuration

First Energization Sequence

With pre-energization checks complete, apply power to the drive with the output to the motor disconnected at the drive terminals or with the motor physically isolated from the mechanical load. The drive should power up to a ready state without immediate faults. Any fault on first energization indicates either a wiring error or an internal drive issue that must be resolved before proceeding.

Most modern drives display a startup wizard on first power-up. Follow the wizard for basic supply voltage confirmation and motor data entry rather than dismissing it, as the wizard often configures internal compensation algorithms that affect performance throughout commissioning.

Keypad and Communication Verification

Verify that the operator keypad responds correctly and that the display is readable and undamaged. If the commissioning includes PC-based configuration software, such as Siemens STARTER, ABB Drive Composer, or Allen-Bradley Connected Components Workbench, establish communication with the drive at this stage and confirm that the software reads the drive's firmware version and parameter set correctly.

A communication failure between commissioning software and the drive at this stage is far less expensive to resolve than discovering it after parameters have been entered at the keypad and the software shows a configuration mismatch.

---

Motor Nameplate Parameter Entry

This is the most consequential configuration step in the entire commissioning procedure. Every protective function, every thermal model calculation, and every vector control algorithm in the drive depends on accurate motor data. Entering incorrect nameplate values does not produce an immediate fault. It produces a drive that appears to work while running the motor outside its design envelope.

Enter the following motor data from the nameplate exactly as printed: Motor rated voltage (V), motor rated current (A), motor rated frequency (Hz), motor rated speed (RPM), motor rated power (kW or HP), motor power factor (cos f where available).

For applications using vector control rather than V/Hz control, the drive will require an additional motor identification run after nameplate data entry. The identification run, sometimes called an autotune or motor ID, applies a series of test voltages to the stationary or rotating motor to characterize its electrical parameters: stator resistance, rotor resistance, leakage inductance, and magnetizing inductance. These measured values replace the default calculated estimates and significantly improve torque accuracy and speed regulation, particularly at low speeds.

Choosing V/Hz vs. Vector Control Mode

The control mode selection affects everything from starting torque to dynamic speed accuracy. Selecting V/Hz for an application that requires precise speed control under variable load is one of the most common commissioning errors on manufacturing lines.

V/Hz control maintains a fixed ratio between output voltage and frequency. It is suitable for centrifugal pumps and fans where the load torque increases predictably with speed and where precise speed regulation is not critical. It is not suitable for applications with high static torque requirements at low speeds, such as extruders, mixers, and winders.

Vector control, either open-loop (sensorless) or closed-loop (with encoder feedback), calculates and regulates actual motor flux and torque. It is the correct choice for constant-torque loads, precision speed applications, and any application requiring controlled torque at zero or near-zero speed.

---

Control Wiring and Signal Verification

Analog Input Verification

Before enabling run commands from external control, verify each analog input signal independently. For a 4 to 20 mA speed reference from a PLC analog output module, source the signal at 4 mA and confirm the drive registers the correct minimum frequency value. Source at 20 mA and confirm the drive registers the configured maximum frequency. Check the midpoint at 12 mA against the expected 50 percent frequency output.

This verification catches wiring errors, incorrect PLC scaling, and analog input configuration issues before the drive is ever started. A 0 to 20 mA signal applied to a drive input configured for 4 to 20 mA produces a 0 Hz command at minimum signal, creating an apparent dead band that can be misdiagnosed as a drive fault.

Digital Input and Run/Stop Logic Verification

Map every digital input against the P&ID and electrical schematic. Verify that the enable signal, run signal, direction command, and any external fault inputs operate as designed before the motor is connected to the mechanical load. Use a multimeter to confirm 24V DC logic levels at the drive input terminals, not at the PLC output card, to verify that the wiring from the panel terminal strip through the cable run to the drive is intact.

Confirm that the drive's safe torque off (STO) inputs, where present, are correctly wired to the safety relay or safety PLC output designated in the safety circuit design. A drive with STO incorrectly wired or bridged will appear to function normally until the safety circuit is tested, at which point the failure to stop on demand is a safety integrity violation that requires a formal corrective action.

---

Protective Function Configuration

Thermal Overload Settings

Configure the drive's motor thermal overload function using the motor's rated current and service factor from the nameplate. The drive's internal thermal model tracks estimated motor temperature based on output current, ambient temperature compensation (if configured), and the motor's thermal time constant. Setting the overload trip threshold above the motor's rated current to avoid nuisance trips is a commissioning error that removes the motor's primary thermal protection.

Ramp Times

Acceleration and deceleration ramp times must be matched to the mechanical load characteristics. An acceleration ramp that is too fast causes motor overcurrent trips on loads with high inertia. A deceleration ramp that is too fast for a drive without a braking resistor causes DC bus overvoltage trips when regenerative energy from the decelerating motor charges the bus beyond its rated level.

For centrifugal pump applications, the deceleration ramp should be long enough to prevent water hammer in the piping system. For conveyor applications, acceleration ramp needs to match belt tension limits. These are process constraints, not drive defaults, and they require input from the mechanical engineering team during commissioning.

Frequency and Speed Limits

Configure the minimum and maximum frequency limits to match the application's operational range. A pump with a minimum runnable speed below which cavitation occurs needs a minimum frequency limit set above that threshold. A fan with a mechanical resonance band at a particular speed needs a skip frequency configured to prevent operation at that resonance point.

---

Motor Run-Up Procedure

No-Load Initial Run

With the motor uncoupled from the mechanical load where possible, command a slow-speed run at 5 to 10 Hz and observe the motor for unusual noise, vibration, or abnormal current draw. Confirm that the motor rotates in the correct direction. A three-phase motor's rotation direction is reversed by swapping any two output phase connections at the drive's U, V, W terminals, not at the incoming supply.

Never swap phases at the incoming supply to correct motor rotation on a VFD installation. The drive's output phase assignment is what determines motor rotation, and the drive output must be treated as a controlled three-phase source.

Increase speed in steps: 10 Hz, 25 Hz, 50 Hz, 100% of maximum frequency. Observe output current at each step and compare against the expected no-load current for the motor. A reading significantly above expected no-load current at low speed indicates a motor wiring fault or a parameter entry error.

Loaded Run and Performance Verification

Couple the load and run at minimum, 50 percent, and full speed under representative process conditions. Record output voltage, output current, output frequency, and DC bus voltage at each operating point. These become the baseline commissioning data against which future diagnostic readings are compared.

Verify that the drive responds correctly to speed changes from the control reference, reaches setpoint within the configured ramp time, and holds speed within the tolerance required by the process. For applications with closed-loop PID control through the drive, verify that the PID setpoint, feedback input scaling, and loop gains produce stable control without sustained oscillation or setpoint offset.

---

System Integration: PLC and SCADA Verification

Communication Protocol Verification

For drives integrated into a PLC or DCS via PROFINET, EtherNet/IP, PROFIBUS-DP, or Modbus TCP, verify the cyclic data exchange at this stage. Confirm that the PLC program is reading the drive's actual speed, output current, fault status, and ready state correctly. Confirm that PLC-commanded speed references and run/stop commands reach the drive and produce the expected response.

A drive that responds correctly to local keypad commands but not to PLC commands has a communication configuration issue, not a hardware fault. The most common cause is a mismatch between the drive's configured process data (PZD) word mapping and the PLC program's data read/write addresses.

HMI Visualization Verification

Verify that the HMI screens displaying drive status, speed, and fault information update correctly and that any drive fault strings are mapped accurately to the HMI alarm system. An HMI that displays a generic "Drive Fault" for all fault types provides less diagnostic information than one that maps individual fault codes to descriptive alarm messages, and the difference in maintenance response time during a production fault event is significant.

---

Troubleshooting Scenario: Drive Trips on First Run

A plastics processing facility was commissioning a new Allen-Bradley PowerFlex 755 on a 110 kW pelletizer extruder. The drive had been wired, parameterized with motor nameplate data, and was ready for first run. On the initial run command at 10 Hz, the drive tripped immediately on an "Output Phase Loss" fault.

The commissioning engineer verified the motor cable connections at the drive output terminals and found all three phases landed correctly. He verified continuity from the drive terminals to the motor terminal box, which also showed continuity on all three phases. The fault persisted on reset and rerun.

The root cause was found by disconnecting the motor cable at the terminal box and checking phase-to-phase resistance at the motor terminals directly. The W-phase winding showed an open circuit, indicating an internal motor fault. The motor had been damaged during installation when the cable pulling crew dragged the motor across the concrete pad without the shaft support frame, straining the internal winding connections.

The drive's output phase loss detection had functioned exactly as designed. The fault was in the motor, not the drive. Replacing the motor resolved the trip. The lesson from this commissioning exercise was that drive faults during initial run should always be traced back to the complete system, including the motor and load, before assuming a drive or wiring problem.

---

Documentation and Handover

The commissioning record is the starting point for every future maintenance and diagnostic activity on the drive. A complete record includes the full parameter printout from the drive's configuration, the as-built wiring documentation, the as-found and as-commissioned values for motor data, the baseline operating data from the loaded run, and the verified communication configuration between the drive and the control system.

A drive that has been thoroughly commissioned and poorly documented is half of a job done. The documentation is what makes the commissioning work useful to the next technician, engineer, or integrator who interacts with that drive.

For plants using a CMMS such as SAP PM or Maximo, the drive's serial number, firmware version, parameter backup file, and commissioning date should be entered as an equipment record. This creates the maintenance history baseline and enables work order tracking for future calibration or replacement activities.

If you need support commissioning or troubleshooting VFDs, selecting the right drive parameters, or integrating motor control systems with your PLC network, Techno Control Corp's engineering team can help. Reach out through TechnoControlCorp to discuss your project requirements.