Overview
Modbus cable length is not a single number. The maximum supported distance depends entirely on the physical layer in use: RS-232 point-to-point, RS-485 multi-drop, or the proprietary Modbus Plus token-passing bus. A Schneider Electric Modicon PLC and a Siemens SIMATIC TP270 HMI can exchange Modbus RTU data over any of these media provided the correct transceiver, cable, termination, and baud rate are applied. The most common engineering error is to assume that "Modbus = RS-485 = 1200 m" without considering the topology, branch length, baud rate, and grounding rules defined by the Modbus over serial line specification.
This reference consolidates the published physical-layer limits, the converter and bridge options, the cable selection rules, and the commissioning checks for a Modbus link between a Modicon controller and a Siemens TP270 panel. It also documents the path to extend distance by moving from RS-232 onto RS-485, and the path to integrate the link into a Modbus Plus plant network using a Modicon Bridge Plus.
Modbus Physical Layer Options
Modbus is a master/slave application protocol that runs over three principal physical implementations relevant to the TP270 ↔ Modicon case:
- RS-232 (EIA-232) — point-to-point, unbalanced, 3- or 5-wire, single driver/receiver pair. The historical default for many HMI-to-PLC links.
- RS-485 (EIA-485 / TIA-485-A) — 2-wire (half-duplex) or 4-wire (full-duplex) differential multi-drop. Up to 32 unit loads on a single segment, expandable with repeaters.
- Modbus Plus — Schneider Electric proprietary 1 Mbit/s token-passing bus on a shielded twin-axial or fiber medium. Peer-to-peer and not the same protocol as Modbus RTU/ASCII.
Other media exist (Modbus TCP over Ethernet, Modbus over UDP, and serial-over-fiber) but they fall outside the scope of cable-length for an RS-232/RS-485/Modbus Plus link.
RS-232 Modbus Cable Length
The original Modicon Modbus implementation over RS-232 was specified for short service connections:
- Maximum length: typically 15 m (≈50 ft) at baud rates up to 19.2 kbps, per the practical RS-232 limit adopted by Modicon and documented in legacy Modicon Modbus Reference Guides. The EIA-232 standard itself lists 15 m as the recommended upper bound for reliable operation at 19.2 kbps with a 2500 pF load budget.
- Drivers: single-ended ±5 V to ±15 V swings. Vulnerable to common-mode noise and ground potential differences between PLC chassis and HMI chassis.
- Topology: strictly 1 driver to 1 receiver. The TP270's COM1 port is RS-232 only; no multi-drop is possible on this port.
- Connectors: DB-9 male on the TP270 side; pinout must be cross-over (null-modem) for DTE-DCE links, or straight-through when the Modicon serial port is wired as DCE.
For most factory floors, 15 m is insufficient. A shielded RS-232 cable (Belden 9925 or equivalent) with the shield bonded at the HMI end only can extend the useful range to ≈20–25 m in low-noise cabinets, but this is outside the Modicon specification and should be verified with a Modbus poll test before being relied upon for production.
RS-485 Modbus Cable Length
RS-485 is the recommended physical layer for any Modbus link beyond 15 m. The published maximums are:
| Topology | Maximum length | Source |
|---|---|---|
| RS-485 daisy-chain, no branches | 1000 m (3280 ft) | Schneider Electric FAQ FA346620 |
| RS-485 with branching (stub length total) | 15 m cumulative stub length | Schneider Electric FAQ FA346620 |
| RS-485 segment with repeaters | 1000 m per segment, multiple segments in series | Modbus over Serial Line spec, TIA-485-A |
| RS-485 full-duplex (4-wire) point-to-point | 1200 m at ≤100 kbps | TIA-485-A annex |
The 1000 m figure is the conservative Modbus-over-serial-line guideline at 9600 baud. At higher baud rates the maximum drops:
| Baud rate (bps) | Typical RS-485 max length (m) | Notes |
|---|---|---|
| 1200 | 1200 | Conservative ceiling for slow Modbus ASCII |
| 9600 | 1200 | Modicon BM85 bridge default |
| 19200 | 1000 | Typical TP270 default |
| 38400 | 750 | Marginal; verify with field test |
| 57600 | 500 | Industrial installations begin to fail |
| 115200 | 250 | Short-run option only |
The relationship between bit time, cable propagation, and stub reflection defines the limit. Rule of thumb used by Schneider integration engineers: distance in meters × baud in bps should not exceed 10⁸. A link at 19200 bps must stay under ≈5200 m on paper, but the 1000 m practical limit is governed by the 2500 pF cable budget of the receiver and the 120 Ω termination conditions of the bus.
RS-485 Cable, Shielding, and Termination
Use a cable designed for RS-485 / Modbus RTU. Recommended characteristics:
- Impedance: 120 Ω ± 10 % characteristic at 1 MHz.
- Conductor: 24 AWG (0.22 mm²) or 22 AWG (0.34 mm²) stranded twisted pair; use a second pair for signal common.
- Shield: overall foil + braid (Belden 3106A, Belden 3072A, Lapp EIB 2×2×0.8, or equivalent).
- Capacitance: ≤ 42 pF/m between conductors, ≤ 75 pF/m conductor-to-shield.
Termination and biasing (mandatory for reliable Modbus RTU at any length over 10 m):
| Component | Value | Location |
|---|---|---|
| Termination resistor | 120 Ω, 1 %, 1/4 W | Across D+/D- at each physical end of the bus only |
| Fail-safe bias (D+) | 680 Ω to +5 V (or 4.7 kΩ to Vterm) | Master end only |
| Fail-safe bias (D-) | 680 Ω to GND (or 4.7 kΩ to GND) | Master end only |
| Common-mode reference | 100 Ω in series with shield to GND | Both ends, low-impedance at one end only |
Shield grounding rule: bond the shield to chassis ground at the HMI end only, with the PLC end connected through a 100 Ω resistor (or 100 nF capacitor in parallel) to chassis. Avoid grounding the shield at both ends to prevent 50/60 Hz ground-loop currents from inducing noise into the data pair.
Topology Rules: Daisy-Chain, Branches, and Stars
RS-485 is a bus topology, not a star. The published Modbus limit of 1000 m assumes a single daisy-chained run. The 15 m branch limit applies when you must drop a short spur from the trunk to a device:
| Topology | Allowed length | Reason |
|---|---|---|
| Trunk daisy-chain, no stubs | 1000 m | No stub reflections, 120 Ω terminations absorb cleanly |
| Single branch (one device, T-tap) | ≤ 15 m of stub | Stubs longer than λ/10 of the bit time act as transmission-line discontinuities |
| Star (4-way split at one point) | ≤ 15 m total stub length across all arms | Same stub-reflection rule; star is the worst case |
| Daisy-chain with 3 short branches (≤ 5 m each) | Trunk 1000 m + 3 × 5 m stubs = 1015 m | Schneider "short branch" rule |
If a star is unavoidable, place an RS-485 repeater (e.g., Schneider SR2MBD01, Phoenix Contact PSM-ME-RS485, or any TIA-485-A compliant repeater) at the branch point. The repeater electrically isolates the segments and re-clocks the signal, restoring the 1000 m budget per output leg.
RS-232 to RS-485 Conversion
Because the TP270's COM1 is RS-232 and most Modicon serial ports (e.g., on a Modicon M340 BMX P34 CPU) support RS-485 natively, the typical upgrade path is to install an RS-232 ↔ RS-485 converter at one end of the link. The other end can then use the Modicon's RS-485 port directly. This converts the link from a 15 m point-to-point cable into a 1000 m multi-drop bus.
Recommended converter characteristics:
- Industrial-grade, optically isolated, surge-protected (≥ 1 kV).
- Auto-direction switching for 2-wire half-duplex (no RTS toggling required by the TP270).
- Switchable 120 Ω termination, internal fail-safe bias, and a removable ground strap.
- Configurable baud rate from 1200 to 115.2 kbps.
Representative products:
- Phoenix Contact PSM-ME-RS232/RS485-P (order no. 2313726)
- Weidmüller WDS2-RS232/485 (order no. 8615830000)
- Schneider Electric SR2MBD01 (Zelio Logic interface converter)
- Black Box IC166A-R2 / IC247A-R3
Wiring example (2-wire half-duplex):
TP270 COM1 DB-9 Phoenix PSM-ME Modicon M340 BMX P34
Pin 2 TX ───────────► RS-232 input
Pin 3 RX ◄─────────── RS-232 output
Pin 5 GND ──────────── GND
RS-485 D+ ────────────────► D+ (terminal D1)
RS-485 D- ────────────────► D- (terminal D0)
120 Ω term ON 120 Ω term ON at last device
Fail-safe bias ON
On the M340, the RS-485 port is on the CPU's removable terminal block; the two wire positions are labelled D1 (D+) and D0 (D-). A 120 Ω termination resistor is placed across the bus at the physical end of the trunk — not at every device.
Modbus Plus Architecture
Modbus Plus is not Modbus. It is a deterministic 1 Mbit/s token-passing peer bus designed by Modicon (now Schneider Electric) for high-speed PLC networking. Key electrical parameters:
| Parameter | Value |
|---|---|
| Data rate | 1 Mbit/s |
| Medium | Shielded twin-axial (Modbus Plus cable) or fiber |
| Max nodes per segment | 32 (with Modbus Plus tap, address 1–64) |
| Trunk length, no repeaters | Up to 450 m (1476 ft) with standard Modbus Plus cable |
| Trunk length, with repeaters | Up to 1800 m total, max 2 repeaters in cascade, 450 m per segment |
| Maximum number of repeaters | 3 repeaters, 4 segments, ≈ 1800 m total |
| Node addressing | 1–64 (node 0 reserved for broadcast) |
| Token rotation | Deterministic, max 80 ms with 32 nodes at default settings |
Modbus Plus uses a proprietary shielded twin-axial cable with a characteristic impedance of 120 Ω and a heavy-gauge center conductor. Approved cable part numbers include Belden 9681 and Schneider 490- NAW-010 (former Modicon part). Connecting a non-approved cable is one of the most common causes of intermittent Modbus Plus faults because the 1 Mbit/s edge rate creates severe reflections on mismatched impedance.
Bridging Modbus to Modbus Plus
To put a Modbus RTU device (the TP270 over RS-485, or any Modbus slave) onto a Modbus Plus trunk, a bridging gateway is required. The Schneider Electric part for this function is the Modicon Bridge Plus, also referred to historically as the Bridge Multiplexer in the BM85C family. Two implementations are commonly used:
- Modicon Bridge Plus (BMx85C001 / BM85C002 family) — a DIN-rail module that mounts on the Modbus Plus trunk and exposes one or two RS-232/RS-485 serial ports for downstream Modbus RTU slaves. The bridge participates in the Modbus Plus token ring and forwards Modbus Plus routing tables to a remote master.
- Modicon NWM / BM85 Bridge Multiplexer (legacy) — predecessor product, still in service on many plants with TSX Quantum and Premium PLCs. Provides 4–8 RS-232 ports and acts as both a router and a transparent serial concentrator.
Configuration steps for a Modbus device to appear on Modbus Plus through a Bridge Plus:
- Set the bridge's Modbus Plus node address with the rotary switches (e.g., address 12).
- Assign a destination Modbus Plus routing path (segment 1, node 12, sub-path) in the upstream Modicon PLC using the
PEERorMSTRinstruction in Unity Pro / EcoStruxure Control Expert. - Configure the bridge's downstream port: baud rate (default 9600), parity (Even, default for Modbus RTU), 8 data bits, 1 stop bit.
- On the TP270 (or the Modicon RS-485 device), set the matching baud, parity, and slave address. The TP270 can be configured as a Modbus master in WinCC flexible; each Modicon register is then mapped to a TP270 tag.
- Power up the bridge last, monitor the
ACTIVELED (green steady = on ring), and verify traffic with a Modbus Plus protocol analyzer (e.g., Schneider's TMS Toolkit or an oscilloscope on the tap).
Important: the Bridge Plus is a Modbus Plus node, not a simple media converter. It must be counted in the 32-node segment limit, and it must be added to the upstream Modicon PLC's routing table before any slave behind it can be polled.
Connecting the Siemens TP270 to a Modicon PLC
The Siemens SIMATIC TP270 is a 6-inch or 10-inch multi-protocol HMI from the ProTool/WinCC flexible generation. Its COM1 port is RS-232, and the COM2 port on the 10-inch variant supports RS-422/485. The TP270 is configured as a Modbus RTU master in WinCC flexible by selecting the "Modicon Modbus RTU" (sometimes labelled "Modicon 984" or "Modbus Master (RTU)") driver and binding each tag to a holding-register or input-register address on the Modicon slave.
Typical wiring (TP270 COM1 RS-232 to Modicon M340 CPU serial port configured as RS-232):
TP270 COM1 (DB-9 male) M340 CPU serial port
Pin 2 RXD ◄─────────────── TXD
Pin 3 TXD ────────────────► RXD
Pin 5 GND ──────────────── SG (signal ground)
Pin 7 RTS ────────────────► CTS (only for hardware flow control)
Pin 8 CTS ◄─────────────── RTS
This is a null-modem (crossover) cable. If the M340 serial port is configured as RS-485 instead, replace the TP270 end with an RS-232-to-RS-485 converter as described in the previous section, and run a single twisted pair (D+/D-) up to 1000 m.
Commissioning Checklist
- Verify the TP270's driver matches the Modicon family (M340, Premium, Quantum) and the register type (4x holding, 3x input, 1x coil).
- Match baud rate and parity on both ends; Modbus RTU defaults are 9600 / 8N1 for many Modicon CPUs, but M340 often uses 19200 / 8E1 for Modbus RTU master mode.
- Set the Modicon CPU's Modbus port to RTU (not ASCII). For BMX P34 20xx, this is set in Unity Pro under Serial Port > Modbus Master or Modbus Slave.
- Confirm the slave address is unique on the bus (1–247, default 1).
- Check shield grounding: bond at one end, 100 Ω at the other.
- Verify 120 Ω termination at both physical ends of the trunk; remove from middle devices.
- Poll a known holding register from the TP270 and verify a round-trip latency under one second at 9600 baud with one slave.
- Run the link for 24 h, logging CRC error counters; a healthy Modbus RTU link should show < 1 CRC error per million frames.
Troubleshooting Matrix
| Symptom | Likely cause | Fix |
|---|---|---|
| No response at all (TP270 shows "Communication error") | RS-232 wiring straight-through instead of null-modem; or parity mismatch (TP270 sends 8N1, M340 expects 8E1) | Rewire per the pinout table; set matching parity on both ends |
| Intermittent timeouts on long RS-485 runs (> 500 m) | Missing 120 Ω termination at one or both ends, or bias resistors absent | Install 120 Ω at both physical ends; add 680 Ω fail-safe bias at the master end |
| Some slaves respond, others don't | Each slave is on a star branch, exceeding 15 m of stub | Re-topology to a single daisy-chained trunk; place repeaters at branch points |
| CRC errors rise at night when HVAC loads change | Ground loop through both-end shield bonding | Remove shield bond from one end, or replace bond with 100 Ω / 100 nF |
| Modbus Plus device invisible after adding a Bridge Plus | Routing table in the upstream Modicon PLC does not contain the bridge's path; or node address conflicts | Add the bridge to the routing table via MSTR block or Unity Pro Peer Cop; verify node 0 (broadcast) is not assigned to the bridge |
| Bridge Plus ACTIVE LED stays off | Twin-axial cable reversed at one tap; or trunk exceeds 450 m without a repeater | Verify cable polarity at every tap; add a Modbus Plus repeater (NW-RR85C001) to extend the trunk |
| TP270 sees 19200 baud error at 19.2 kbps on 800 m RS-485 | Baud/length ratio too aggressive; cable capacitance too high | Drop to 9600 baud, replace cable with lower-capacitance type, or insert a repeater |
Distance Decision Flow
Use the following decision path when planning a Modbus link between a Modicon PLC and a Siemens TP270:
- Distance < 15 m? Use RS-232 with a null-modem cable. No converter needed.
- Distance 15 m to 1000 m, single device? Use RS-485 with an RS-232-to-RS-485 converter at the TP270 end. Daisy-chain only, 120 Ω at both ends.
- Distance 15 m to 1000 m, multiple devices? Use RS-485 with a master at one end. Add a repeater at any star point.
- Distance > 1000 m on the same plant backbone? Consider Modbus Plus with a Bridge Plus to bring the TP270 RS-485 trunk onto the higher-speed Modbus Plus ring.
- Multiple TP270s across the plant? Modbus Plus is the conventional Schneider-bus path; an Ethernet/Modbus TCP network with a BMX NOE 01x0 module is the modern alternative.
Field-Proven Caveats
- Never coil surplus RS-485 cable — the coil becomes a common-mode choke and a transmission-line stub simultaneously. Cut to length.
- Do not run RS-485 in the same conduit as VFD output cables (typically 480 V, 4–16 kHz PWM). Maintain ≥ 300 mm separation, or cross at 90°.
- If the TP270 must share a 24 VDC supply with a noisy device (solenoid, contactor), power the HMI from a separate 24 V branch with its own decoupling capacitor (≥ 470 µF).
- On Modbus Plus, a 1 Mbit/s signal will not pass through a 25-pin D-sub backshell; use approved Modbus Plus taps (e.g., 990XCP97000 / AS-MBII-001) and strain-relief the cable to the trunk.
- For any RS-485 segment above 600 m, prefer a cable with ≥ 95 % braid coverage and double-shield construction; this typically buys 10–15 dB of margin against impulse noise.
Related Standards and Documentation
- Schneider Electric FAQ FA346620 — Modbus RS-485 maximum length with and without branching
- Modbus over Serial Line Specification V1.02 — Modbus Organization
- Modbus Application Protocol V1.1b3 — Modbus Organization
- Modicon Modbus Plus BM85 Bridge Multiplexer user guide
- Siemens Industry Online Support — SIMATIC TP270 product documentation
Frequently Asked Questions
What is the maximum Modbus RS-485 cable length without branching?
1000 m (3280 ft) at baud rates up to 19200 bps, per Schneider Electric's Modbus-over-serial-line guidance. This drops to roughly 250 m at 115200 bps.
What is the RS-232 Modbus cable length limit?
15 m (≈50 ft) is the practical Modicon/EIA-232 limit at 19200 bps. The TP270's COM1 port is RS-232 only, so distances beyond 15 m require an RS-232-to-RS-485 converter.
How do I extend a Modbus link to a Modbus Plus plant network?
Use a Modicon Bridge Plus (BM85C family) on the Modbus Plus trunk. The bridge acts as a Modbus Plus node and forwards Modbus RTU traffic from one or two RS-232/RS-485 ports. The bridge must be added to the upstream Modicon PLC's routing table.
Does the TP270 support Modbus RTU master or slave mode over RS-485?
The TP270 can be configured as a Modbus RTU master in WinCC flexible, polling holding and input registers on a Modicon slave. It does not function as a Modbus Plus device. For Modbus Plus connectivity, choose a Siemens panel from the MP370 or later series that supports MPI/Profibus or Ethernet-based protocols.
Why do I need a 120 Ω resistor on the RS-485 bus?
RS-485 cable has a characteristic impedance of 120 Ω. Placing a 120 Ω termination at each physical end of the trunk absorbs signal reflections that would otherwise corrupt the differential waveform. Without termination, you will see CRC errors, especially above 500 m or above 38400 bps.