An RS-485 port defines the electrical bus and nothing about who initiates a Modbus RTU transaction. The master and slave roles live in each device's documented driver, so check the role for your exact panel and software before wiring a multidrop link. When the panel is master-only, put a gateway in that answers the central system as the slave.
A central system wants to poll four local control panels, the panels share one twisted pair, and nothing answers. The mistake usually happens before the first cable is pulled: the RS-485 port was read as a role. An RS-485 port defines the electrical bus, the wire pair, the drive levels and a load budget. The Modbus RTU master and slave roles are set inside each device's serial driver, and the two facts are independent. This page separates them, gives the numbers that size a real trunk, and shows the gateway architecture that connects a central master to panels whose drivers only ever initiate.
What RS-485 defines, and what it leaves to the protocol
The standard behind an RS-485 port is TIA/EIA-485. It specifies a differential electrical interface: a shared pair (or two pairs on four-wire links), the driver output levels, the receiver thresholds, and how much load each device may hang on the bus. Load is measured in unit loads, and the standard sizes one bus segment at 32 unit loads. Every receiver hears every transmission. The standard carries no addressing, no message format and no turn-taking rule, and two transmitters can drive the same pair, so the electrical layer has no way to stop two devices from initiating at once. Turn-taking is the protocol's job.
What master and slave mean on a Modbus RTU trunk
Modbus RTU allows one master per serial trunk. The master builds every transaction: an address field of eight bits in RTU, then the function code, the data and the error check, per the Modbus specification. Devices configured as slaves listen, and only the slave whose configured address matches the field answers. The specification assigns RTU slave addresses 1 to 247, one per slave per trunk; the master carries no slave address of its own, because nothing ever addresses it. A slave never initiates.
Two initiators on the same trunk produce overlap: slaves hear mixed frames and answer garbage or stay silent. That failure and its fix are worked through in two Modbus RTU masters on one RS-485 bus.
Where the role is written down
The role lives in the device's serial driver. Many HMI panel families ship drivers built to poll: the panel is the master and the controller behind it is the slave, which is why the HMI panel is often the serial master on the link. The same port hardware serves both roles: RS-485 transceivers appear in master and slave devices alike, so the port type tells you the wiring and nothing about who asks first.
Check three things for the exact hardware and software you will buy:
- The model number and the programming-software or firmware version, read from the unit or its order documents.
- The serial driver page in that version's documentation, which states whether the driver initiates requests, answers them, or both. The phrase Modbus RTU appears on master drivers and slave drivers alike, so the role is a separate line.
- Written confirmation from the vendor's official support channel, requested whenever the role is unstated for that exact combination.
A capability slide or a family comparison can describe a different model, a different driver, or a slave role on a different connection type. Match every role claim to the model, driver name and version before it becomes the basis of a wiring plan. The driver list comes before any serial tuning; check the panel driver list first sets that order out.
How many devices one trunk carries
Two budgets apply to the same pair of wires, and they are independent.
The electrical budget is 32 unit loads per segment, from the TIA/EIA-485 unit-load definition. A transceiver datasheet prints its load as 1, 1/2, 1/4 or 1/8 of a unit load. Add the figures for every device on the segment and stay at 32 or below. Modern transceivers commonly present 1/8 unit load each, so 32 ÷ 0.125 = 256 devices; older full-load designs give 32 ÷ 1 = 32 devices. Walk the sum device by device from each datasheet's stated load figure, and keep the running total at 32 or under.
The address budget comes from Modbus: slave addresses 1 to 247. A segment of 256 one-eighth-load transceivers is electrically legal and still runs out of slave addresses at 247, so on a bus of 1/8-load devices the address budget is the tighter of the two.
Example: a dispatch PC and four local panels
Scenario: a control-room PC polls Modbus RTU slaves through an RS-485 converter. Four local control panels around the plant each have an RS-485 port, and the plan is one trunk through the building. The unit-load figures below use the common 1/8 value; read the real ones from each datasheet.
Case 1, the panels have documented slave drivers. Wire one master and four slaves. Set panel addresses 1, 2, 3 and 4. Load: 5 devices × 0.125 = 0.625 unit loads of the 32-unit-load budget, leaving 31.375 unit loads spare, room for 251 more 1/8-load devices (256 − 5). The dispatcher polls addresses 1 to 4 in turn and the design is finished.
Case 2, the panel drivers are master-only. The dispatcher's polls get no answer: the PC would be a second master on a one-master trunk, and a master-only panel has no slave endpoint to answer at any address from 1 to 247. Change the architecture:
- Fit a protocol gateway between the two sides. On the dispatcher's trunk the gateway answers as a Modbus RTU slave at address 1. Load: converter 0.125 + gateway 0.125 = 0.25 unit loads of 32, leaving 31.75 unit loads spare.
- On the panel side the gateway meets each panel on the panel's documented terms: the panel initiates, as its driver requires, and the gateway serves it the registers the project needs. Each panel link is its own segment, so one master per segment still holds everywhere.
- Write down which device owns each value and what the dispatcher shows when the gateway loses a panel link. A heartbeat counter makes the loss visible; verify the link with a PLC heartbeat counter shows the pattern.
Decision: with slave-capable drivers, one trunk carries four addressed panels on 0.625 unit loads. With master-only drivers, the gateway answers the dispatcher at address 1 while every panel keeps its documented role. If a panel value drives an operator action, treat a silent link as a fault to show at both ends, and never leave a frozen screen looking live.
The decision for each case
- Driver documentation for your exact model and software version states a slave role: build one master polling slaves, with distinct addresses from 1 to 247 and datasheet unit loads summed to 32 or less per segment.
- The driver is master-only: give the central system a gateway that answers as the Modbus RTU slave, and put the panel on a link where it keeps initiating. Extra ports on the central system give it more links, and a panel that never listens answers on none of them.
- Two devices both need to initiate: split them onto separate trunks, one master each.
- No document states the role: get written confirmation from the vendor before ordering panels or cable.
Recommendation: read the serial driver's stated role for your exact panel model and software version before you order hardware or pull cable. Build the trunk as one master polling slaves when that slave role is written for your combination, with slave addresses from 1 to 247 and unit loads summed to 32 or under per segment. When the panel is master-only, budget a protocol gateway that answers the central system as the slave and lets the panel initiate on its own link, and make a lost link visible at both ends. If the project also wants a plant notice board or andon screen next to the panels, that is a separate screen: see our shop-floor displays, which play offline from files with no subscription.
Questions
Can two Modbus RTU masters share one RS-485 trunk?
No. Modbus RTU defines a single master per serial link, and two initiators drive overlapping frames onto the pair: one side logs no-reply errors while the other sees address or CRC errors. Give each master its own trunk, or place a protocol gateway between them so exactly one device initiates on each segment. The electrical standard has no rule against the overlap, because it defines wire levels and the load budget, and turn-taking belongs to the protocol.
How many devices can one RS-485 bus segment carry?
Two budgets apply. Electrically, TIA/EIA-485 sizes a segment at 32 unit loads; with 1/8-load transceivers that is 32 ÷ 0.125 = 256 devices, and with full-load transceivers 32 ÷ 1 = 32 devices. Sum each device's datasheet unit-load figure and stay at 32 or below. In parallel, Modbus RTU assigns slave addresses 1 to 247, so a fully packed electrical segment runs out of protocol addresses at 247 slaves. On a bus of one-eighth-load devices, the address budget is the tighter limit.
What happens when two slaves share one Modbus RTU address?
Both devices answer one request at the same time, their frames overlap on the pair, and the master sees a CRC error or a garbled response for that address. Addresses 1 to 247 must be unique per trunk. Check each slave's configured address against a written address plan whenever a new device joins the bus; duplicate addresses are the most common cause of a trunk that works until one specific node is added.
Does adding serial ports to the central system let it poll a master-only panel?
No. Extra ports give the central system more links, and a master-only panel presents no slave endpoint on any of them. The role is implemented in the panel's driver, so the two paths that work are a documented slave-capable driver for that exact model and software version, or a protocol gateway that answers the central system as the Modbus RTU slave while the panel keeps initiating on its own link. Confirm the documented role before buying either.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.