VFD Communication: Modbus, PROFINET and EtherNet/IP

What is fieldbus communication on a VFD? It is the digital link — Modbus RTU, PROFINET, PROFIBUS DP, EtherNet/IP, or EtherCAT — that lets a PLC or SCADA system write a speed reference and read status, fault codes, and process values from the drive over one cable instead of a rack of discrete terminals. Pick the wrong protocol and the drive becomes an integration problem: a plant standardized on PROFINET cannot cheaply talk to a drive that only ships with EtherNet/IP, and a serial-only unit cannot join a real-time EtherCAT motion ring. This article covers embedded Modbus RTU, the three dominant industrial Ethernet protocols, option-card limits, cyclic versus acyclic data, RS-485 timing, and the wiring practices that keep a fieldbus segment from dropping packets.

Embedded Modbus RTU: The Default Serial Link

Modbus RTU ships embedded on most general-purpose drives — no option card required. It runs over RS-485, half-duplex, two wires plus a common. Device addresses run 1 to 247; a single segment supports up to 32 unit loads without a repeater, fewer if any device presents more than one unit load. Baud rate is configurable, typically 9600 to 115200 bps, and both ends of the segment need it set the same or the drive never responds.

Three function codes cover almost every VFD integration: 03 (read holding registers) for status word, actual speed, output current, and fault code; 06 (write single register) for a single speed reference or control bit; 16 (write multiple registers) for a control word plus reference in one transaction. Register maps are drive-specific — ABB, Siemens, and Schneider each publish their own holding-register layout, so the PLC program has to match the exact drive family, not just "Modbus."

What we see in the field: a segment wired without termination resistors runs fine at low baud rate over a short cable, then faults intermittently the day someone extends it to 60-80 m or adds a third device. The symptom looks like a bad drive. It is usually a missing 120 Ω resistor.

Industrial Ethernet: PROFINET, EtherNet/IP and EtherCAT

PROFINET, maintained by PROFIBUS & PROFINET International, runs standard Ethernet cabling with M12 connectors common in the field. Its RT (real-time) class updates in single-digit milliseconds; IRT (isochronous real-time) pushes into the sub-millisecond range for motion-synchronized applications. Engineering uses a GSDML file that describes the drive's parameters and process data to the PLC configuration tool.

EtherNet/IP runs on standard TCP/IP and UDP/IP and carries CIP (Common Industrial Protocol), the same application layer used across ODVA's device family. Two ports on most drives allow daisy-chaining without a switch; some brands add DLR (Device Level Ring) for a fault-tolerant loop topology. EtherNet/IP's cyclic update is comparable to PROFINET RT, generally a few milliseconds.

EtherCAT, developed by Beckhoff and governed by the EtherCAT Technology Group, processes frames on the fly — each slave reads and writes its data as the single frame passes through, rather than waiting for its own polling cycle. Cycle times under 100 µs are common, which is why EtherCAT dominates coordinated multi-axis motion rather than single-drive process control.

PROFIBUS DP: Legacy Fieldbus Still in the Field

PROFIBUS DP predates PROFINET and still runs in a large installed base. It is RS-485 based like Modbus RTU but faster, up to 12 Mbit/s, with its own addressing and a GSD file for configuration. DP-V1 adds acyclic parameter access alongside the cyclic process data. New installations default to PROFINET; PROFIBUS DP shows up mainly in retrofits where ripping out the existing trunk cable and repeaters is not in the budget.

Option Cards and Multi-Protocol Gateways

A drive with embedded Modbus RTU on its control-board terminals typically accepts one plug-in option card for one industrial Ethernet protocol — PROFINET, EtherNet/IP, or EtherCAT, not two at once. ABB's FBA cards, Siemens' Communication Boards on the G120 Control Unit, and Schneider's VW3A3 series on the Altivar range follow this same pattern: pick the card that matches the plant network before the drive is ordered, not after it arrives.

Need a drive on a network its option-card lineup doesn't cover? A protocol gateway (Modbus TCP to PROFINET, EtherNet/IP to Modbus RTU, and similar combinations) bridges the two, at the cost of one more device to power, address, and maintain. It is a workable fallback, not a design goal.

Cyclic vs Acyclic Data: What the PLC Actually Exchanges

Cyclic data is the process data object exchanged every scan: control word, speed reference, status word, actual speed, output current, and active fault code, refreshed continuously whether anything changed or not. Acyclic data is everything else — parameter reads and writes during commissioning, diagnostic detail, firmware-level settings — transferred on request rather than every cycle, since none of it needs millisecond currency.

Modbus RTU Frame Timing

Modbus RTU has no explicit end-of-message marker. A receiver instead treats a silence of 3.5 character times as the frame boundary — anything shorter is assumed to be a gap inside the same message, anything longer starts a new one. At low baud rates that silence window is tens of milliseconds; get the wiring or the master's polling interval wrong and frames run into each other.

At 9600 bps that works out to roughly 4 ms of silence before the next frame is valid; at 115200 bps it drops to well under a millisecond. Polling a drive faster than its own response time plus this silence window is the most common cause of sporadic timeouts on an otherwise correctly wired segment.

Wiring, Grounding and Choosing a Protocol by Plant Standard

RS-485 and Fieldbus Cable Practice

RS-485 wants a daisy chain, not a star — stub lengths beyond a few centimeters reflect signal and corrupt frames. Terminate both physical ends of the segment with a 120 Ω resistor; mid-segment devices leave termination off. Route communication cable separate from motor power cable wherever the tray allows, since PWM switching noise couples into unshielded signal pairs — the same reflected-wave mechanism covered in VFD harmonics and EMC filter requirements is part of why that separation matters, and long motor runs bring their own cable-length limits, detailed in VFD output filters and cable length limits.

Matching the Protocol to the Existing Network

The practical selection rule has little to do with which protocol is technically superior and everything to do with what the plant already runs. A Siemens-standardized facility on TIA Portal gets the smoothest commissioning from a drive with native PROFINET, which is why Siemens builds it into the G120C's compact control unit. A Rockwell- or Schneider-leaning plant on EtherNet/IP gets the same benefit from a CIP-native drive. Multi-axis motion cells lean EtherCAT regardless of PLC brand, because the cycle-time floor of PROFINET RT or EtherNet/IP is not tight enough for coordinated axes. The comparison in ABB ACS580 vs Schneider ATV630 vs Siemens G120 covers how each brand's default fieldbus support lines up against the others. See the full VFD engineering guide for how communication fits alongside sizing and control-method selection, and the variable frequency drives collection for models with embedded PROFINET, EtherNet/IP, or EtherCAT.

Conclusion

Fieldbus choice is a plant-standard decision more than a technical one. Modbus RTU covers simple single-drive retrofits at low cost. PROFINET, EtherNet/IP, and EtherCAT each require an option card and match a specific automation ecosystem — Siemens/PI, Rockwell/CIP, or coordinated motion, respectively. Get the protocol right before the drive ships, wire the RS-485 segment with proper termination and daisy-chain topology, and keep signal cable away from motor power runs. Getting any of these wrong turns a communication question into a commissioning delay.