PROFINET vs EtherNet/IP vs Modbus TCP: Which Industrial Ethernet Protocol?
Choose by PLC ecosystem first and by timing class second. The same motor bit takes a different path on each stack.
Choose first
PLC ecosystem
PROFINET RT
EtherType 0x8892
EtherNet/IP
44818 and UDP 2222
Modbus TCP
TCP 502
Quick answer
Start with the controller you already have. A Siemens line in Europe is almost always PROFINET. A Rockwell line in North America is almost always EtherNet/IP. A supervisory system that only needs to read and write simple points on many vendors is almost always Modbus TCP.
Timing is the second question, not the first. PROFINET and EtherNet/IP are both cyclic industrial Ethernet. PROFINET puts real-time I/O in Layer 2 frames and uses IRT when the machine needs the sub-millisecond class. EtherNet/IP puts cyclic I/O in CIP implicit messages on UDP, produced at a requested packet interval (RPI). Modbus TCP is a client poll on TCP. It is usually the wrong tool for tight closed-loop motion, and a good tool for monitoring.
Devices that share a switch still do not share a conversation. A peer has to speak the same protocol, or a gateway has to translate. Managed switches, VLANs, and QoS are the normal way to let the three coexist. PROFINET IRT also needs IRT-capable switches.
Side-by-side
This is the canonical comparison. The PROFINET and EtherNet/IP guides keep a short table and point here. Cycle time for a real machine comes from the controller, the device, and the topology. The table below names the class of exchange, the owner, and the public identifiers. It does not rank products by a microsecond figure.
| Topic | PROFINET | EtherNet/IP | Modbus TCP |
|---|---|---|---|
| Owner | PI. Strong Siemens ecosystem. | ODVA. Strong Rockwell ecosystem. | Modbus Organization. |
| Application layer | PROFINET IO | CIP (Common Industrial Protocol) | Modbus PDU, coils and registers |
| Real-time mechanism | Cyclic RT I/O in Layer 2 frames. IRT is the sub-millisecond class. | Cyclic implicit I/O at a configured RPI. Explicit is request and response. | No built-in cyclic I/O. The client polls. |
| Transport | RT and IRT on Ethernet. Config and diagnostics on TCP/IP and UDP/IP. | CIP over TCP and UDP, over IP | Modbus over TCP |
| Ports / EtherType | RT EtherType 0x8892. Not an IP port. | Explicit messaging: TCP and UDP 44818. Implicit I/O: UDP 2222. | TCP 502 |
| Cycle-time class | RT class, plus IRT for sub-millisecond motion. | Implicit class, one RPI per connection. | Poll class. The client application chooses when to ask. |
| Switches | Managed Ethernet. IRT needs IRT-capable switches. | Managed Ethernet. IGMP snooping for multicast I/O. | Standard Ethernet switches. |
| Diagnostics | Alarms and diagnostic records in PROFINET IO. | CIP diagnostic objects, read with explicit services. | Exception codes. No standard device model. |
| Device file | GSDML | EDS | Vendor register map |
| Safety | PROFIsafe profile | CIP Safety profile | No safety profile in the base protocol |
| Complexity | Moderate to high | Moderate | Low |
The same I/O value on each stack
Take one conveyor motor. The controller must set Run and a speed setpoint, and it must read back Running and actual speed. The meaning of those four items does not change. The frame that carries them does.
PROFINET: Layer 2 RT, EtherType 0x8892
The IO controller keeps a process image. Run and the speed setpoint live in the output image. Each RT cycle, that image leaves as an Ethernet frame whose EtherType is 0x8892. The IO device applies the outputs and returns Running and actual speed in the same exchange. That RT frame is not an IP packet, so it has no TCP or UDP port. On the OSI model cheat sheet, this payload is identified at Layer 2 and handed to PROFINET IO.
Cyclic RT path (controller and device)
Ethernet header, EtherType 0x8892, PROFINET RT, output process data (Run, speed), input process data (Running, actual speed)
Setup, records, and diagnostics use the IP channel beside these frames. The GSDML file tells the controller which bits are Run and which word is speed.
IRT keeps a reserved schedule for the sub-millisecond class, and that segment needs IRT-capable switches. Parameterization still uses the IP channel. The PROFINET guide covers the IO controller, IO device, and IO supervisor roles.
EtherNet/IP: CIP implicit UDP 2222, explicit TCP/UDP 44818
EtherNet/IP carries CIP on the normal IP stack. Cyclic I/O is an implicit connection. The output assembly holds Run and speed, and the adapter consumes it from UDP port 2222 at the connection RPI. The input assembly returns Running and actual speed on that connection. The input is often multicast so several consumers can listen.
Implicit I/O path (cyclic)
Ethernet, IP, UDP port 2222, CIP I/O, assembly data (Run, speed, and the return status)
Explicit path (open, configure, diagnose)
Ethernet, IP, TCP or UDP port 44818, CIP explicit service (forward open, identity, parameters)
The EDS file describes the assemblies and objects. The bits are CIP members, not Modbus register numbers.
The scanner opens that connection, and a tool reads parameters later, with explicit CIP services on TCP or UDP port 44818. Keep the motor data on the implicit assembly. The EtherNet/IP guide covers the scanner, adapter, and producer-consumer model. Implicit I/O rides UDP, while explicit sessions often ride TCP.
Modbus TCP: client poll on TCP 502
A Modbus TCP client opens a TCP connection to port 502 and asks. The server answers that one request. A vendor map might put Run in a coil and speed in a holding register. Another vendor packs both into one holding register. The map is the vendor's document. The specification defines function codes and the MBAP header, not a conveyor object.
Poll path (client to server)
TCP port 502, MBAP header, PDU function code, coil or register address from the vendor map, Run and speed data
Response path (server to client)
Same TCP connection, MBAP transaction id echoed, function echo or exception code, Running and actual speed if the client asked for them
Nothing sends the next update until the client asks again. Decode a real frame in the Modbus TCP parser. The Modbus TCP guide shows the MBAP layout.
The same motor is easy to watch from SCADA or a short script, and a poor fit for coordinated motion. The protocol has no RPI and no RT cycle. If the points still live on serial Modbus RTU, a TCP-to-RTU gateway uses the Unit ID to pick the downstream device. That is a different job from translating PROFINET into CIP.
Real-time and determinism
What you can rely on is the shape of the exchange. PROFINET and EtherNet/IP schedule it. Modbus TCP waits for the client application to ask.
On PROFINET, the IO controller owns the RT cycle. Outputs and inputs move as EtherType 0x8892 frames. IRT adds a reserved schedule for the sub-millisecond class, and the switches in that segment have to participate. A switch that treats every frame the same will not carry an IRT design.
On EtherNet/IP, the scanner and adapter agree on an RPI when the implicit connection opens. Implicit I/O on UDP 2222 then keeps producing at that project setting. Explicit traffic on 44818 stays available for configuration and one-off reads. Leave the cyclic motor data on the implicit path.
On Modbus TCP, the client program is the schedule. A host that polls once a second gets one-second data, and a faster client still waits on the TCP round trip and on every other client of that server. Tight closed-loop control and motion usually need a cyclic class. Supervisory display, meters, and slow setpoints fit the poll. Simplicity and the number of vendors on port 502 are the reason to pick it.
A measured cycle time still depends on the controller scan, the device, the connection count, and the switches. Take that number from the vendor's data for the product you are buying. Use this page to choose the class of exchange.
Network design
All three can share one switched Ethernet network. They do not collide at the identifier level. PROFINET RT is recognized by EtherType 0x8892. EtherNet/IP implicit I/O is UDP 2222, and explicit messaging is TCP or UDP 44818. Modbus TCP is TCP 502. A switch forwards the frames. It does not translate them. The port list on the common ports cheat sheet includes 502, 44818, and 2222.
Use managed switches. Give real-time VLANs and QoS priority over file copies, cameras, and backups. IGMP snooping matters on EtherNet/IP because implicit I/O is often multicast, and without it every port sees traffic that only two devices needed.
PROFINET uses DCP (Discovery and Configuration Protocol) so a controller can find a device by name and assign the IP address of the non-real-time channel. DCP is a link-local setup step. It is not the cyclic I/O path, and Modbus or CIP devices do not answer it. Keep IRT on IRT-capable switches. RT and ordinary IP traffic can use managed switches that honor priority.
PROFINET RT frames and TCP/IP frames are meant to share a network, with the real-time frames identified at Layer 2. EtherNet/IP already is TCP and UDP, so firewalls that understand TCP and UDP can see ports 44818 and 2222. Put 502, 44818, and 2222 on the OT firewall policy.
Config files: GSDML, EDS, and register maps
The controller cannot guess which byte is the motor Run bit. Each ecosystem ships that description in a different file.
- GSDML (General Station Description Markup Language) is the PROFINET file. The engineering tool imports it so the IO controller knows the modules, the cyclic lengths, and the parameters it may write.
- EDS (Electronic Data Sheet) is the EtherNet/IP file. It describes CIP objects, assemblies, and connections so the scanner can build implicit I/O and the explicit parameter path.
- A register map is the Modbus TCP equivalent. It is a vendor list of coils, discrete inputs, input registers, and holding registers. The server is not required to hand you a standard file. Someone copies the map into the client.
On startup, a PROFINET or EtherNet/IP device usually comes from a catalog after the GSDML or EDS is installed. A Modbus TCP device is a list of addresses typed in and checked with a live read. That path is easier to explain and easier to miss by one offset.
Gateways and mixing
A Siemens PLC does not natively speak CIP, and a Rockwell PLC does not natively speak PROFINET IO. Putting both on the same switch only means both frames are on the wire. The controller still needs a partner that speaks its protocol.
Use a protocol gateway, a remote I/O head with a second port, or a PLC card for the other ecosystem. The gateway copies the points you mapped. It does not extend the RT cycle or the RPI across the translation. A cyclic producer on one side becomes whatever the other side can do, often a poll.
Modbus TCP is the usual common denominator for a simple foreign device. Drives, meters, and packaged skids often expose a small register set beside a PROFINET or EtherNet/IP line controller. Use that path for setpoints and status, and keep coordinated motion on the native cyclic protocol. A Modbus TCP client can also reach Modbus RTU through a gateway that uses the Unit ID as the serial address. That gateway does not connect a PROFINET IO device to a CIP adapter. Map those points on their own translator and test them.
Decision table
Use the scenario, not a generic ranking. If two rows seem to apply, the PLC ecosystem row wins for I/O inside the cell, and the Modbus row wins for slow points outside it.
| Scenario | Choose | Why |
|---|---|---|
| New line, Siemens PLC, Europe | PROFINET | Native I/O for that ecosystem. RT for the cell, IRT if the motion needs the sub-millisecond class. |
| New line, Rockwell PLC, North America | EtherNet/IP | Native CIP. Implicit I/O on UDP 2222 at the RPI you configure. |
| Supervisory poll across many vendors | Modbus TCP | Simple points, wide support, client poll on TCP 502. |
| Tight motion in a Siemens cell | PROFINET IRT | IRT class, which means IRT-capable switches in that segment. |
| Cyclic drive I/O on a Rockwell cell | EtherNet/IP implicit | Assemblies on UDP 2222. Open and diagnose the connection on 44818. |
| One cabinet, Siemens and Rockwell | Gateway, or a controller that has both | A shared switch does not make the protocols interoperable. |
| Plant network already carries all three | Keep them, segment with VLAN and QoS | Sharing the cable is normal. Peers still speak one protocol each. |
| Telemetry to a broker or dashboard | MQTT above the PLC | Publish/subscribe for data that has left the cell. Not a replacement for cyclic I/O. |
Where EtherCAT, OPC UA, and MQTT fit
EtherCAT is a separate industrial Ethernet, usually with its own master inside a machine. Machine builders use it as a motion segment on the device side of a controller. It leaves the plant-level choice between PROFINET and EtherNet/IP in place. This site has no EtherCAT page yet.
OPC UA is how many controllers expose tags to SCADA, MES, and historians. It models information above the PLC. A line can run PROFINET or EtherNet/IP for I/O and OPC UA toward the rest of the plant. The guide covers the information model, TCP port 4840, and where MQTT Sparkplug B fits beside it.
MQTT publishes messages to a broker. A gateway or the PLC can publish motor status after the I/O protocol has done its job. MQTT has no RPI, RT cycle, GSDML, or EDS. Use it for telemetry and for commands that can tolerate broker delivery. Keep the conveyor Run bit on PROFINET, EtherNet/IP, or a supervisory Modbus TCP poll.
Facts you can check
The identifiers in this guide are public registry entries and published descriptions from the organizations that own the protocols. Speed claims that depend on a lab setup are left to vendor documentation.
| Statement on this page | Where to check it |
|---|---|
| Modbus TCP uses TCP port 502 | IANA service name mbap, port 502, assignee modbus.org. The Modbus TCP mapping uses TCP. See the IANA service name registry. |
| EtherNet/IP explicit messaging uses port 44818 | IANA service name EtherNet-IP-2, TCP and UDP 44818, described as EtherNet/IP messaging. ODVA publishes the CIP behavior that runs there. |
| EtherNet/IP implicit I/O uses UDP port 2222 | IANA service name EtherNet-IP-1, UDP 2222, described as EtherNet/IP I/O. |
| PROFINET RT frames use EtherType 0x8892 | PI describes PROFINET RT frames with EtherType 0x8892, carried from Layer 2 to the application rather than through TCP/IP. IRT is the separate isochronous class and needs IRT-capable switches. |
Frequently Asked Questions
What is the difference between PROFINET and EtherNet/IP?
Both are cyclic industrial Ethernet. EtherNet/IP is CIP over TCP and UDP: implicit I/O on UDP port 2222 at the connection RPI, and explicit messaging on TCP or UDP port 44818. PROFINET puts RT I/O in Layer 2 frames with EtherType 0x8892, and uses IRT for the sub-millisecond class. EtherNet/IP is the usual Rockwell and North American choice. PROFINET is the usual Siemens and European choice. A gateway has to sit between them.
Is Modbus TCP real-time enough?
For tight closed-loop control or motion, usually no. For supervisory monitoring, slow setpoints, and multi-vendor register devices, yes. The client polls over TCP port 502, and the protocol has no built-in cyclic I/O. Simplicity and vendor support are why it is still on so many skids.
Can PROFINET, EtherNet/IP, and Modbus TCP share one network?
Yes, on switched Ethernet. Frames are distinguished by EtherType 0x8892, by UDP 2222 and port 44818, and by TCP 502. Each peer still speaks one protocol, unless a gateway translates. Use managed switches, VLAN, and QoS. PROFINET IRT needs IRT-capable switches. Use IGMP snooping where EtherNet/IP implicit I/O is multicast.
Can a Siemens PLC talk directly to a Rockwell PLC?
Sharing a switch is not enough. Siemens cell I/O is PROFINET, and Rockwell cell I/O is EtherNet/IP. You need a gateway, a multi-protocol module, or a PLC interface for the other stack. Modbus TCP is a common middle ground for simple points. Leave cyclic motor data on the native protocol.
Which file do I import for a new device?
Import a GSDML for PROFINET and an EDS for EtherNet/IP. For Modbus TCP, copy the vendor register map into the client. Modbus TCP has no standard device file for the server to hand you. One wrong address writes a different point from the motor bit you intended.
Do EtherCAT, OPC UA, or MQTT replace these three?
They sit beside this choice. EtherCAT is a machine-level industrial Ethernet with its own master. OPC UA exposes information above the controller. MQTT publishes telemetry to a broker. The cyclic path between a Siemens or Rockwell PLC and its drives stays PROFINET or EtherNet/IP, or Modbus TCP when the job is only a poll. Add OPC UA or MQTT when the data leaves the cell.
Related Protocols
- PROFINET, EtherNet/IP, and Modbus TCP each have a full guide. Modbus RTU is the serial version.
- OPC UA and MQTT for data above the cell. TCP and UDP under EtherNet/IP and Modbus TCP.
- Common ports, the OSI model cheat sheet, and the Modbus TCP parser.