GUIDE5 min readUpdated Jun 2026

Raspberry Pi Modbus (TCP & RTU)

The workhorse fieldbus of brownfield automation — and the fastest way to make a Pi talk to existing PLCs and meters.

SHORT ANSWER

Modbus is the lingua franca of industrial gear, and a Pi speaks it fluently as both master and slave over TCP (Ethernet) and RTU (RS-485 serial). With a library like pymodbus or a Node-RED/OpenPLC node, a Pi reads registers from existing PLCs, drives, and energy meters — making it the simplest bridge from legacy equipment to modern dashboards.

TCP & RTU
both transports supported
Modbus spec
RS-485
the serial layer for RTU
spec
Master/slave
a Pi can be either
pymodbus

01TCP vs RTU

Modbus TCP runs over Ethernet and is simplest where the network exists. Modbus RTU runs over RS-485 serial and is everywhere in older plants. An industrial Pi with an isolated RS-485 port handles both, so it bridges legacy serial gear to a TCP/MQTT world.

02Using it well

Poll at a sane rate, handle timeouts and CRC errors gracefully, and map registers explicitly. A Pi makes a reliable Modbus gateway when the polling loop is written defensively — which is exactly the kind of plumbing we standardize on our gateway builds.

Common questions

The ones we're asked on every first call.

Yes — that's one of the most common Pi deployments: read brownfield equipment over Modbus RTU/TCP and republish to MQTT or OPC-UA for dashboards and the cloud, without touching the control loop.

Want this run on your numbers?

Send us your current stack and what it needs to do. A controls engineer replies with a candid one-page teardown — no deck, no sales call.

Request a teardown