Back to all posts
Projects & Retrofits8 min read·November 8, 2026

A VFD Commissioning Checklist: From Nameplate to Handover

TB
ThynkBlox Automation Team
Automation Engineering

A VFD commissioning checklist should take the drive from a verified safe, de-energised installation to a documented, tested and backed-up configuration. Do the work in order: confirm the installation and safe state, enter the motor nameplate data and application parameters, test direction and ramps uncoupled where possible, prove stop and fault behaviour, verify PLC communication, then back up the parameters and hand over the records. This article gives you a structure for that work. It does not replace the drive manufacturer's manual or your site's safety procedures, and both take precedence over anything written here.

Why does a VFD need its own commissioning checklist?

A drive can power up, accept a run command and turn the motor while still being set up wrongly. The motor data may be incorrect, the stop mode may not suit the load, or a fault may not reach the PLC. These problems often stay hidden until the motor overheats, a conveyor overruns or an operator cannot tell why a machine stopped.

A written checklist makes each test deliberate and leaves a record of it. That record is what the maintenance team uses when the drive is replaced or a parameter is questioned months later.

Drive commissioning is usually one part of a wider startup. Instrument loop checks, site acceptance testing and the punch list all depend on it. See performing instrument loop checks before startup and managing a controls commissioning punch list.

What should be confirmed before the drive is energised?

Do not energise anything until the installation has been inspected against the drawings and the manufacturer's installation requirements. Then confirm:

  • The drive rating suits the motor and supply, according to the drive and motor documentation.
  • Supply, motor and control wiring matches the approved drawings, including terminations and cable glands.
  • Earthing and cable screen terminations follow the manufacturer's guidance.
  • Upstream protection and isolation are installed as designed.
  • The enclosure and its ventilation meet the drive's stated requirements.
  • Any bypass contactor, output contactor or motor isolator is interlocked as the design specifies.
  • Isolation, lock-out and permit-to-work arrangements are agreed with the site.

Drives can hold hazardous stored energy after isolation. Follow the manufacturer's stated discharge wait time and the site's procedure for proving the drive dead before any work inside the enclosure.

If the drive forms part of a safety function, for example through a safe torque off input, the design and validation of that function belong to a qualified assessor working to the site's safety process. Commissioning confirms that the installation matches the approved design. It does not decide whether the design is adequate. See planning a safety assessment for a machine retrofit.

How should nameplate data and parameters be entered?

Read the values from the motor nameplate itself. Do not rely on a datasheet or an old parameter file. Photograph the nameplate and attach the photo to the commissioning record.

Parameter groupSourceWhat to check
Motor rated voltage, current, frequency, speed, powerMotor nameplateValues match the connection actually used, for example star or delta
Motor control modeFunctional design specificationMode suits the load and the manufacturer's guidance
Minimum and maximum frequency or speedProcess requirement and mechanical limitsLimits agreed with the mechanical or process owner
Acceleration and deceleration rampsProcess requirementTimes suit the load, and braking capability is considered
Stop modeFunctional design specificationRamp or coast, as specified for the machine
Control and reference sourceControl designTerminal, keypad or fieldbus, as designed
Motor protection settingsMotor data and manufacturer's manualThermal protection configured as the manual describes
Fault reset and auto-restartFunctional design specificationAuto-restart enabled only where the design and risk assessment permit it

Run any motor identification or auto-tune routine only as the manufacturer describes. Some routines rotate the shaft and others do not, so confirm which kind it is and whether the load must be uncoupled before you start it.

Record every parameter you change from its default, with the reason. The functional design specification should be the reference for the application values. If it says nothing about a setting, raise a query instead of guessing.

How do you test direction and ramps safely?

Test rotation first at low speed and, wherever practical, with the motor uncoupled from the load. Use the drive's local control or jog function under the site's permit arrangements, with the area clear and a person able to stop the drive.

  1. Confirm the required direction of rotation with the mechanical owner before the test.
  2. Give a brief run command at low speed and observe the shaft.
  3. If the direction is wrong, correct it the way the design specifies, either in wiring or in a parameter, and record which method was used.
  4. Increase the speed in steps across the operating range. Check for unusual noise, vibration or heating.
  5. Check acceleration and deceleration with the load coupled, and watch for overcurrent or overvoltage warnings.

Illustrative example: a conveyor drive is specified with a ramp of several seconds. With product loaded, deceleration trips the drive on DC bus overvoltage. The team records the trip, then reviews the ramp time and braking arrangement with the designer before changing anything. They do not simply lengthen the ramp until the trip stops. The numbers and behaviour here are illustrative, not measured results.

How should stop and fault behaviour be proved?

Test every stop path defined in the design, not only the normal stop:

  • Normal stop from the PLC or HMI.
  • Local stop, if fitted.
  • Emergency stop and any safe torque off function, tested only under the validation procedure approved for that safety function.
  • Loss of run command or enable signal.
  • Loss of the speed reference.

For faults, simulate conditions the manufacturer's manual says are safe to simulate, such as an external fault input or a communication timeout. Then confirm:

  • The drive takes the fault action set in the design.
  • The fault reaches the PLC and the HMI with a meaningful description.
  • The reset procedure works as specified and does not restart the motor unexpectedly.

The restart behaviour after a fault or power loss needs particular care. See defining machine restart after power loss and designing HMI screens for fault diagnosis.

What should be checked on PLC communication?

Whether the drive is controlled through hardwired I/O or over a fieldbus, check every signal end to end.

  • Each control word bit and status word bit, toggled and observed at both ends.
  • Speed reference scaling: the PLC value, the drive value and the actual speed agree across the range.
  • Feedback values such as speed, current and fault code, with their engineering units confirmed.
  • Network address and device configuration match the network design.
  • Behaviour when communication is lost, tested by disconnecting the link under controlled conditions.

The drive's communication-loss action and the PLC's response must be designed together. A drive that keeps running at its last speed may be acceptable on one machine and dangerous on another. See defining PLC behaviour on communication loss.

How should parameters be backed up and handed over?

When testing is complete, back up the final parameter set using the manufacturer's tool or the drive's storage option. Then:

  • Store the backup with a clear name that identifies the drive tag and version.
  • Record the firmware version of the drive and any option modules.
  • Test that the backup can be read back. Where practical, compare it against the drive.
  • Keep a printed or exported list of the changed parameters with the commissioning record.

The handover pack should contain the completed checklist, the nameplate photo, the test results with signatures and dates, any deviations and open punch items, the backup files and the firmware details. Store it with the rest of the control system records. See control system handover files and access and backing up and restoring PLC programs.

What are the common mistakes?

Copying parameters from a similar drive. Motor data and application settings differ between machines, even when the hardware is identical.

Testing direction with the load coupled. Wrong rotation can damage pumps, gearboxes and product. Uncouple wherever practical.

Testing only the normal stop. Fault, communication-loss and emergency paths are where the risk sits.

Enabling auto-restart for convenience. It must be a design decision supported by the risk assessment.

Leaving the backup on a laptop. If the site cannot find the backup when a drive fails, it does not have one.

Changing parameters after handover without a record. Put drive settings under the same change control as PLC code. See controlling plant software changes after commissioning.

When does this checklist not apply as written?

Some drives call for a different or additional procedure. These include drives with integrated safety functions, regenerative or common-bus systems, drives in hazardous areas, medium-voltage drives and drives supplied as part of a packaged machine with the vendor's own commissioning. In those cases the manufacturer's procedure and the site's safety requirements lead, and this checklist serves only as a prompt for what to record.

Frequently asked questions

Can the parameter backup from the old drive be loaded into a replacement?

Sometimes. Confirm with the manufacturer that the model and firmware are compatible, then repeat the direction, stop and communication tests before running in production.

Who should sign the commissioning record?

The person who carried out the tests and a representative of the site who accepts the result. Agree the signatories before commissioning starts.

Is an auto-tune always required?

No. Follow the manufacturer's guidance for the control mode and load you are using, and record whether one was run and which type.

Should a drive be commissioned before the PLC program is finished?

Local tests on direction, ramps and motor data can often be done first. Communication and stop-path tests need the final PLC logic and should be repeated if that logic changes.

If you want support planning drive commissioning within a wider retrofit, see our services or contact us.

Next step

Want to apply this to your plant?

Every project starts with a fixed-fee assessment, and you can stop after the report.