Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC PAS 62030:2004 — MODBUS Application Protocol and RTPS Wire Protocol for Fieldbus
IEC PAS 62030:2004 is a publicly available specification that defines two complementary communication protocols for industrial measurement and control systems: the MODBUS Application Protocol Specification (V1.1a) and the Real-Time Publish-Subscribe (RTPS) Wire Protocol (Version 1.0). Together, these protocols cover both traditional master-slave polling communication (MODBUS) and modern publish-subscribe data distribution (RTPS) for real-time industrial automation networks.
Design Insight: The combination of MODBUS and RTPS in a single PAS reflects the industry’s need for both deterministic request-response communication (for configuration and supervisory control) and high-speed data distribution (for real-time process data sharing between controllers, HMIs, and historians) on the same network infrastructure.
1. MODBUS Application Protocol (Section 1)
The MODBUS Application Protocol section defines a complete application-layer messaging specification for client-server communication between industrial devices. MODBUS supports both serial-line transmission (MODBUS RTU/ASCII using RS-232 or RS-485) and TCP/IP-based communication (MODBUS TCP). The protocol uses a simple function-code-based request-response model where the client sends a request PDU (Protocol Data Unit) and the server returns a response PDU.
| Function Code | Name | Description |
|---|---|---|
| 01 (0x01) | Read Coils | Read binary outputs from the server |
| 02 (0x02) | Read Discrete Inputs | Read binary inputs from the server |
| 03 (0x03) | Read Holding Registers | Read 16-bit analog output registers |
| 04 (0x04) | Read Input Registers | Read 16-bit analog input registers |
| 05 (0x05) | Write Single Coil | Write a single binary output |
| 06 (0x06) | Write Single Register | Write a single 16-bit analog register |
| 15 (0x0F) | Write Multiple Coils | Write multiple binary outputs |
| 16 (0x10) | Write Multiple Registers | Write multiple 16-bit registers |
| 23 (0x17) | Read/Write Multiple Registers | Atomic read and write in single transaction |
The MODBUS data model is organized into four primary data blocks: Discrete Inputs (read-only bits), Coils (read-write bits), Input Registers (read-only 16-bit words), and Holding Registers (read-write 16-bit words). This simple, flat addressing model makes MODBUS extremely easy to implement even on resource-constrained microcontrollers, contributing to its enduring popularity in industrial automation.
Important: MODBUS TCP uses port 502 and wraps the standard MODBUS PDU inside a TCP/IP frame with a 7-byte MBAP (MODBUS Application Protocol) header. While this makes it simple to route over standard Ethernet networks, it also means MODBUS TCP has no built-in security (no authentication, no encryption). For installations requiring cybersecurity, MODBUS TCP should be deployed within a VPN or at minimum on a physically isolated network segment.
The standard defines three transmission modes for serial-line MODBUS: RTU mode (binary encoding with CRC-16 error checking, 8-bit data, 1 start bit, 1-2 stop bits, parity configurable), ASCII mode (hexadecimal character encoding with LRC error checking), and the overall frame format. RTU mode is the most widely adopted due to its higher data throughput compared to ASCII mode, which doubles the number of transmitted bytes.
2. Real-Time Publish-Subscribe (RTPS) Protocol (Section 2)
The RTPS Wire Protocol defines a publish-subscribe data distribution mechanism designed for real-time industrial control applications. Unlike MODBUS’s client-server model, RTPS allows data producers (publishers) to broadcast data to multiple consumers (subscribers) without requiring explicit polling from each subscriber. This significantly reduces network traffic and ensures that all subscribers receive data simultaneously, within deterministic time bounds.
| Feature | MODBUS (Client-Server) | RTPS (Publish-Subscribe) |
|---|---|---|
| Communication Model | Request-Response (polling) | Push-based (event-driven) |
| Data Flow | Point-to-point | One-to-many, many-to-many |
| Timing | Deterministic (poll interval) | Real-time (periodic or on-change) |
| Network Efficiency | Lower (each device polled) | Higher (data published once) |
| Use Case | Configuration, SCADA polling | Real-time process data, alarms |
The RTPS protocol uses the concept of a “discovery” phase where publishers and subscribers announce their presence and data topics on the network. After discovery, data flows directly from publishers to subscribers using a real-time transport mechanism. The specification defines data serialization formats, QoS policies (reliability, durability, deadline), and transport mappings (UDP/IP, TCP/IP). This protocol later evolved into the core of the OMG DDS (Data Distribution Service) standard, which has become widely used in autonomous systems, defense, and industrial IoT applications.
Design Insight: For applications requiring both configuration access and real-time data, a hybrid approach is effective: use MODBUS for device configuration, parameter adjustment, and supervisory polling (low rate, request-response), while using RTPS for high-speed process variable distribution (high rate, publish-subscribe). This dual-protocol approach leverages the strengths of each without compromising on either functionality or performance.
3. TCP Connection Management and Implementation Guidelines
The PAS provides detailed implementation guidance for MODBUS/TCP connection management. It distinguishes between automatic and explicit TCP connection management. For most applications, automatic management is recommended: the MODBUS client stack automatically opens, maintains, and closes TCP connections as needed. A key recommendation is that each TCP frame should carry exactly one MODBUS ADU (Application Data Unit); sending multiple MODBUS requests or responses in the same TCP segment is discouraged.
Critical: The standard advises against opening and closing TCP connections for each MODBUS transaction. The recommended approach is to keep a persistent TCP connection between a client and server, reusing it across multiple transactions. Opening a new TCP connection for every request incurs the overhead of the TCP three-way handshake and slow-start congestion control, which can increase transaction latency by several hundred milliseconds in high-latency networks.
For bi-directional communication scenarios where each device acts as both client and server, separate TCP connections should be established for the client data flow and the server data flow. The standard also specifies minimum connection limits and the behavior when connection limits are reached, managing TCP resources according to device capabilities.
Frequently Asked Questions
Q: Is IEC PAS 62030 the same as the MODBUS specification from Modicon?
A: IEC PAS 62030 formally adopts the MODBUS Application Protocol Specification V1.1a as an IEC publicly available specification. The technical content is identical to the MODBUS specification published by the MODBUS Organization. The IEC PAS format provides international recognition and a stable reference for regulatory and procurement purposes.
Q: Can RTPS and MODBUS operate simultaneously on the same network?
A: Yes, provided the network infrastructure supports both UDP (for RTPS) and TCP (for MODBUS TCP). On Ethernet networks, both protocols can coexist without interference as they use different transport layer ports (MODBUS TCP on port 502, RTPS on dynamically assigned ports via the discovery mechanism). However, network bandwidth planning must account for the combined traffic.
Q: What are the key differences between MODBUS RTU and MODBUS TCP that engineers should consider in system design?
A: Key differences include: (1) addressing — RTU uses device addresses (1-247) while TCP uses IP addresses; (2) error checking — RTU uses CRC-16 computed per frame, TCP relies on the TCP/IP stack’s built-in checksums; (3) timing — RTU requires inter-frame timing of 3.5 character times, TCP has no such constraint; (4) cabling — RTU typically uses RS-485 multi-drop with maximum 1200 m, TCP uses standard Ethernet with up to 100 m per segment (extendable via switches).
Q: Has IEC PAS 62030 been superseded by newer standards?
A: The MODBUS specification has been maintained by the MODBUS Organization independently. The RTPS protocol defined in Section 2 has evolved into the OMG DDS (Data Distribution Service) standard (formalized as IEC/ISO 19459 in some domains). However, IEC PAS 62030 remains historically significant as it documents the foundational protocol versions that established the widespread adoption of both MODBUS and publish-subscribe industrial communication patterns.
