How PLC Controls VFD: Indian Plant Wiring Guide

How a PLC Controls a VFD in India

At 2 AM during a line changeover, a VFD that refuses a speed reference from the PLC puts the entire night shift on hold. That failure usually traces back to a control wiring detail or a parameter mismatch, not to the drive itself. A PLC controls a VFD by sending low-voltage signals through a hardwired control circuit or a fieldbus network, telling the drive when to run, stop, and change speed.

In Indian MSME plants, this usually works through digital start-stop wires, analog 0-10V or 4-20mA speed references, or protocols like Modbus RTU. The core of it is simple; the practical wiring is where production lines stall.

Why a PLC and VFD Need to Communicate

A VFD runs the motor, but it is a power stage that needs a command source. Someone has to tell it to ramp up, hold speed, and ramp down safely. That is the PLC's job. The PLC reads inputs from sensors, pushbuttons, and interlocks, then decides the motor state based on the machine logic.

On a CNC line in Kattedan, for example, the PLC coordinates spindle speed with axis movement and coolant flow. Without a stable PLC-to-VFD link, the spindle runs at the wrong speed or ignores the stop command, and the whole machining cycle is lost. The benefit of letting the PLC handle it is that drive decisions become part of the machine sequence, not a manual operator call. That matters on a three-shift line where the electrician is not standing at the panel at midnight.

Four Ways a PLC Sends Commands to a VFD

Digital run commands. The most common method in Indian MSME panels. Two wires from PLC outputs connect to the VFD digital input terminals, usually labelled FWD and REV. A 24V DC signal tells the drive to start; removing the signal stops it. Simple, reliable, and easy for a plant electrician to trace with a multimeter.

Analog speed reference. The PLC analog output module sends 0-10V DC or 4-20mA to the VFD's analog input terminal. The drive maps that signal to a frequency range. For example, 0V means minimum speed, 10V means maximum. This is the standard choice for continuous speed control on conveyor systems or pumps. In many Indian plants, 4-20mA is preferred in dusty environments because the current loop is less sensitive to voltage drop and noise than a 0-10V signal.

Fieldbus communication. Modbus RTU over RS-485 is the most common in mid-sized Indian plants, with Profibus and EtherNet/IP appearing in newer lines. The PLC writes speed setpoints and run commands as register values directly into the drive's memory. This method saves wiring when multiple VFDs run on one line, but it brings parameter matching and address mapping into the picture. A single register mismatch can leave the drive idle while the PLC shows a healthy output.

VFD terminal strip as a simple interface. In older plants, the VFD has its own keypad and the PLC just provides a dry contact for start-stop. This is not really communication; it is a start signal. Fine for basic machines, but it gives the PLC no feedback on actual speed or load current.

Most plants end up using a mix: digital wires for safety interlocks and analog or fieldbus for speed control. That hybrid setup is where most wiring errors happen.

How to Wire and Configure the Control Circuit

Step 1: Check the PLC output type. A transistor output (sourcing) and a relay output (dry contact) wire differently. Match the PLC output to the VFD's input requirement, usually 24V DC. Do not feed 230V AC from a relay output into a 24V DC input terminal.

Step 2: Identify the VFD control terminals. Open the drive manual for your specific model and firmware version. Find the digital input common, the FWD terminal, and the analog input terminals, typically AI1 and AI2. Note whether the analog input is set for voltage or current in the parameters.

Step 3: Run shield and power cable separately. Control wiring from the PLC to the VFD must run in a separate conduit from the motor power cable. The motor cable carries high-frequency noise that couples into low-voltage control signals and causes nuisance trips. In dusty textile units and grinding shops, this is a frequent root cause of erratic drive behaviour.

Step 4: Set the matching parameters. The VFD must be told where its run command comes from and which source it should use for the speed reference. If the PLC sends 4-20mA but the drive is set to 0-10V, the motor runs at full speed when it should be idle. This mismatch is the single most commonly missed item during commissioning.

Step 5: Verify the common reference. The PLC and VFD must share a common ground reference for their control signals. A floating common causes the input voltage to drift, and the drive picks up false run commands. Check the manufacturer's diagram for where to move the common jumper. In panels powered by a single 24V SMPS shared across the PLC, sensors, and solenoids, a loaded supply rail will also drag the reference down and trigger erratic behaviour.

Common PLC-to-VFD Faults and Safe Isolation Checks

VFD ignores the start command. Check the digital input status from the VFD keypad, not the PLC program. If the terminal does not show active, the problem is the wire, the PLC output, or a dead 24V supply. Trace it back from the drive terminal to the PLC output card.

Drive trips when the PLC sends a run command. This is usually not a communication fault. The most common causes are a dry earth connection, loose motor terminals, or a parameter mismatch in the motor nameplate data. Three-phase supply dips and phase imbalance are common on many Indian industrial feeders, and they show up as undervoltage trips on drives that otherwise test clean. A plant electrician can safely check the incoming supply voltage and phase balance with a multimeter at the VFD input while the panel is live, but do not open the drive cover while energised.

PLC shows run output but motor speed is wrong. The drive is getting the signal, but the speed reference is wrong. Verify whether the VFD is in manual mode from a hand-held keypad, whether the analog input is configured for the right signal type, and whether the maximum frequency parameter matches the motor rating.

VFD picks up random run commands. Check for induced voltage from a parallel cable run, moisture bridging terminals in monsoon season, or a floating common. These faults are intermittent by nature and often surface during the first heavy rain of the year. Hyderabad's humidity does this to panels that ran fine through winter. Condensation on the terminal strip or the feedback encoder connector is a frequent culprit in coastal and high-humidity belts.

The isolation sequence. For anything beyond a voltage check, isolate the panel and lock it out before touching the drive terminals. The DC bus in a VFD holds a dangerous charge long after the AC supply is off. Measure the bus voltage across DC+ and DC- and wait for it to discharge fully. If the fault is inside the drive module itself, that is beyond a plant electrician's scope and needs a controls engineer with the right test equipment. An ITI-trained electrician can verify supply and phase balance confidently, but drive-internal fault finding is a different skill set.

The Real Cost of a Wrong Wiring Diagram

A single swapped wire or a mismatched parameter rarely shows up during the trial run. It shows up at 2 AM on a Sunday when the line supervisor needs to changeover for the Monday dispatch, and the VFD simply refuses to take a speed reference from the PLC. The production manager calls the owner, the owner calls the electrician, and the electrician is checking a mechanical fault because the symptoms look like a motor problem.

The sequence is predictable: half an hour of phone calls, an hour of guessing, a wrong hypothesis that wastes another hour, and a few hours of lost production before someone with drive experience is actually at the panel. For an MSME working on thin margins, that line-down time is real money. Getting the wiring right the first time is cheaper than any service call; getting it wrong costs production, overtime wages, and a missed delivery commitment.

This is why the diagnosis matters, not the parts swap. A control system fault is a path, not a component. The wiring mismatch, the parameter error, and the communication setting are all part of that path. When a fault is beyond a plant electrician's scope, a verified controls expert can trace that entire path efficiently. That is the gap MachineryFix covers: technicians vetted for hands-on PLC and VFD experience, not just board-swapping.

Summary Checklist for PLC-to-VFD Integration

• Confirm your PLC output type matches the VFD input requirement before wiring anything
• Check the VFD manual for the exact terminal names and the common configuration for your firmware
• Route control cables separately from motor power cables to avoid noise-induced trips
• Set the VFD parameters for the correct run command source and analog signal type
• Verify the common ground reference between PLC and VFD
• Test the digital input status from the VFD keypad when a start command is ignored
• Check supply voltage and phase balance before suspecting the drive itself
• Lock out and isolate the panel, and measure DC bus discharge, before any drive module work
• Escalate to a controls engineer when the fault path goes beyond safe field checks

If you want to understand common failure patterns with specific equipment, our guide on PLC and VFD repair and diagnostics walks through the fault families and what an MSME plant can safely handle in-house.

Related Services

• VFD and AC drive repair in Hyderabad

Related Reading

- Plant Preventive Maintenance Checklist: A Practical Guide - Hitachi WJ200 Drive Fault Diagnosis: Hyderabad Plant Steps - Hitachi SJ700 Drive Faults: Diagnosis Steps for Indian Plants - Maintenance Data History That Works: Hyderabad Guide - Plant Preventive Maintenance Checklist Hyderabad: Cut Stops