Industrial and automotive systems require communication protocols that TCP/IP alone cannot provide: deterministic timing, fault tolerance, noise immunity, and real-time behaviour. Choosing the wrong protocol adds cost, constraints, and integration risk that are difficult to reverse at a later stage. This guide covers the major protocols, their characteristics, and the selection framework that maps application requirements to the right choice.
This guide covers: the five major industrial communication protocols and their distinguishing characteristics (POINT 01); a side-by-side comparison table for rapid protocol evaluation (POINT 02); the six selection criteria that map application requirements to protocol choice (POINT 03); the hardware components required for implementation — PHY, protocol controllers, isolation, and connectors (POINT 04); and a protocol-to-application matrix for common industrial and automotive deployment scenarios (POINT 05).
Industrial communication protocols differ from consumer networking protocols in their emphasis on determinism (predictable delivery timing), fault tolerance (graceful behaviour under node failure or bus errors), and noise immunity (reliable operation in electrically harsh factory, automotive, and outdoor environments). Each protocol below occupies a distinct position in the performance-cost-complexity space.
The table below compares the five primary protocols across the dimensions most relevant to protocol selection. Use it as a rapid first-pass filter before deeper investigation of conformance requirements and hardware availability for your specific application.
| Protocol | Physical Layer | Max Speed | Cycle Time | Max Nodes | Primary Market | Certification |
|---|---|---|---|---|---|---|
| CAN | ISO 11898 (2-wire) | 1 Mbps | ~1 ms typical | ~127 / segment | Automotive, robotics, medical | ISO 11898 |
| CAN-FD | ISO 11898-1 (2-wire) | 8 Mbps (data) | < 1 ms | ~127 / segment | Automotive next-gen, robotics | ISO 11898-1 |
| Modbus RTU | RS-485 serial | ~115 kbps | 10–1,000 ms | 247 / segment | SCADA, BMS, energy meters | None required |
| Modbus TCP | Ethernet 100/1000 | 100+ Mbps | 10–1,000 ms | Ethernet-scale | SCADA, BMS, process control | None required |
| EtherCAT | 100BASE-TX Ethernet | 100 Mbps | < 100 µs | 65,535 | Motion control, CNC, robotics | ETG conformance test |
| PROFINET IO | 100/1000BASE Ethernet | 100 Mbps | 1–512 ms | Ethernet-scale | European factory automation | PI certification |
| PROFINET IRT | 100BASE Ethernet (managed) | 100 Mbps | 250 µs | Ethernet-scale | European precision motion | PI certification |
| EtherNet/IP | Ethernet 100/1000 | 100 Mbps | 1–500 ms | Ethernet-scale | North American factory automation | ODVA conformance test |
Protocol selection should proceed from application requirements, not from the protocol's marketing materials. The six criteria below cover the dimensions that most frequently determine which protocol is the correct choice for a given application.
Every industrial communication protocol requires hardware beyond the application microcontroller. The four hardware categories below cover the implementation chain from the protocol layer to the physical connector, with the key supplier options for each.
The matrix below maps the most common industrial and automotive application domains to the protocol that is most frequently selected, with the primary rationale. This is a starting point for protocol selection, not a prescriptive rule — project-specific factors (existing infrastructure, customer specification, cost constraint) may override the general pattern.
Industrial communication protocol selection requires mapping application requirements to protocol capabilities across six dimensions: real-time performance (cycle time and jitter), target market and infrastructure fit, node count and topology, implementation cost and complexity, development tool availability, and certification requirements and timeline. The five primary protocols occupy distinct positions: CAN/CAN-FD for automotive, mobile machinery, and noise-critical embedded applications; Modbus for low-cost, universal monitoring and control at moderate update rates; EtherCAT for maximum-performance synchronised motion control; PROFINET for European factory automation with Siemens PLC integration; and EtherNet/IP for North American factory automation with Rockwell/Allen-Bradley integration. For each protocol, implementation requires selecting the appropriate physical layer transceiver or Ethernet PHY, a protocol controller IC or certified software stack, galvanic isolation appropriate for the industrial environment, and IP-rated industrial connectors for the deployment environment. Select the protocol based on your application's control loop requirements and target market — not on marketing claims of "real-time" performance that may not reflect worst-case production network behaviour.
Was this guide useful?
Denro Keikaku is a cross-border electronics procurement specialist and direct partner of Chengde Technology — a Foshan-based PCB manufacturer with a strong track record in volume supply for Japanese and international customers.