Modbus Plus is one of the more confusingly named protocols in industrial automation, because despite sharing part of a name with Modbus it is a completely different network. It was Modicon's peer-to-peer plant network, a fast token-passing bus that let programmable controllers exchange data among themselves without a single master polling everyone. Decades of installed base mean it still runs in older process plants, and a SCADA modernisation project quite often runs into a Modbus Plus segment that has to be brought into an IP world. This guide explains what Modbus Plus actually is, how its rotating token and Global Database work, and why aging segments usually need a bridge or gateway rather than a direct connection.
Modbus Plus in one line: Modbus Plus is Schneider Electric's legacy Modicon peer-to-peer network running at 1 Mbit/s over shielded twisted pair, using a rotating token to give each node a turn to talk. It is distinct from Modbus RTU and Modbus TCP; it is a deterministic token-passing bus rather than a request-response protocol, and nodes share data through a Global Database mechanism. Because it is not IP-based, connecting Modbus Plus to a modern SCADA almost always requires a dedicated bridge or gateway.
The name causes endless confusion, so it is worth being blunt: Modbus Plus is not a faster version of Modbus. Modbus RTU and Modbus ASCII are simple serial request-response protocols where a master polls slaves over RS-485 or RS-232, and Modbus TCP is that same request-response model carried over Ethernet. Modbus Plus is architecturally different. It is a peer-to-peer local area network in which every node is equal, there is no single master polling the others, and access to the wire is governed by a token that circulates among the nodes. The two families share a corporate heritage at Modicon and can carry Modbus-style data, but they are separate technologies with separate cabling, chips and behaviour.
Physically, Modbus Plus runs at 1 Mbit/s over a single shielded twisted-pair cable in a daisy-chained bus, with terminators at the ends and taps for each node. It uses an HDLC-derived framing at the link level, and interfacing to it historically meant a dedicated Modbus Plus adapter card or a controller with a built-in Modbus Plus port, because ordinary serial or Ethernet hardware cannot speak it. A segment supports a limited number of nodes, and larger networks are built by joining segments through bridge devices that relay traffic between them.
This distinction matters the moment someone tries to connect to a Modbus Plus network expecting it to behave like Modbus TCP. There is no IP address to point a SCADA driver at, no port to open a socket on, and no simple polling handshake. The data is real and often valuable, but reaching it means dealing with a genuinely different network rather than reusing a familiar Modbus configuration.
Access to a Modbus Plus network is controlled by a logical token that passes from node to node in order of station address. Only the node holding the token may initiate traffic, and when it has finished its transactions it passes the token to the next active address, so the right to transmit rotates continuously around the network. Each node has a station address, historically set with switches, that determines its place in the token rotation and must be unique on the segment. Because exactly one node transmits at a time and the token visits every node in a bounded cycle, the network is deterministic: a designer can reason about the worst-case time before any given node next gets to speak.
A distinctive feature of Modbus Plus is Global Data, sometimes called the Global Database. When a node passes the token, it can attach a block of data that every other node on the segment can read. This gives an efficient broadcast mechanism: rather than each controller having to poll every other controller for the handful of values it cares about, a controller simply publishes its shared values with the token pass and any interested node picks them up. It is a natural fit for the peer-to-peer intent of the network, where controllers coordinating a process want to share state among themselves rather than route everything through a central master.
Alongside Global Data, nodes can also perform explicit read and write transactions to specific other nodes while they hold the token, addressing data in the familiar Modicon register layout. So a Modbus Plus network typically mixes two styles of communication: efficient periodic sharing of common values through Global Data, and directed point-to-point reads and writes for everything else. Understanding both is important when mapping a legacy network, because some of the values a SCADA project wants may only exist in the Global Data stream rather than being available through a direct read.
Because Modbus Plus is neither serial Modbus nor IP-based, a modern SCADA host cannot poll it directly, and the standard route into it is a protocol gateway. Such a gateway has a Modbus Plus interface on one side, where it joins the token rotation as a node and gathers the data it needs, and an Ethernet interface on the other, where it presents that data as Modbus TCP or another routable protocol the SCADA can read. From the supervisory system's point of view the gateway looks like an ordinary IP device with a set of registers, hiding the token-passing network behind it entirely.
These bridges vary in sophistication. Some are simple one-to-one converters that expose a fixed block of Modbus Plus data on a TCP port; others can join the Global Data stream, perform directed reads across several nodes, and assemble a consolidated register map that mirrors many devices at once. In every case the gateway has to be configured with the station addresses and register locations of the Modbus Plus nodes it is reading, which requires knowing the legacy network's layout. Recovering that documentation from an old plant is often the harder half of the job.
For a cloud SCADA project the pattern is clear: Modbus Plus data reaches the platform through an edge gateway that translates it into an IP protocol, and from there it is trended, alarmed and stored like any other tag. The token-passing network keeps running unchanged underneath, its determinism and its Global Data sharing intact for the controllers that depend on it, while the gateway acts as a one-way window into that world. Recognising early that a Modbus Plus segment needs a bridge, rather than a driver, prevents the common mistake of scoping a modernisation as if the network were just another flavour of Modbus.
No. Modbus RTU and Modbus TCP are simple request-response protocols where a master polls slaves, whereas Modbus Plus is a peer-to-peer token-passing network running at 1 Mbit/s over shielded twisted pair. They share a Modicon heritage and can carry similar register data, but they use different cabling, hardware and access methods. You cannot connect to Modbus Plus with an ordinary serial or Ethernet Modbus driver.
Modbus Plus runs at 1 Mbit/s on its signalling cable, which was fast for a plant network when it was introduced. Because access is governed by a rotating token rather than continuous polling, the network is deterministic, and a designer can bound the worst-case time before any node next gets to transmit. Effective throughput for application data is lower than the raw rate once token passing and framing overhead are accounted for.
You use a protocol gateway or bridge. The gateway joins the Modbus Plus network as a node to collect data, then presents that data on Ethernet as Modbus TCP or another routable protocol the SCADA can poll. It must be configured with the station addresses and register locations of the legacy nodes, so recovering the old network's documentation is usually a key part of the work.
This page references the standards, specifications, and official documentation published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.