How Peripheral Nodes Send Telemetry Data Directly to the Main Hub via Modbus Protocol

Architecture of Direct Modbus Telemetry

In industrial IoT and SCADA systems, peripheral nodes-such as sensors, actuators, and remote terminal units-often need to report telemetry data (temperature, pressure, vibration, flow) to a central controller. The most reliable method is direct communication using the Modbus protocol. Each peripheral node acts as a Modbus slave, while the main hub operates as the Modbus master. This eliminates intermediate gateways, reducing latency and points of failure.

The physical layer can be RS-485, RS-232, or TCP/IP over Ethernet. For long distances (up to 1200 meters), RS-485 is preferred due to its differential signalling and multi-drop capability. Each node is assigned a unique slave ID (1–247). The master polls each slave cyclically, requesting specific register values. This deterministic polling ensures that telemetry data arrives in a predictable sequence.

Polling Cycle and Data Integrity

A typical polling cycle involves the master sending a read-holding-registers request (function code 0x03) to a slave. The slave responds with 2-byte data per register, plus a CRC-16 check. The master validates the CRC and discards corrupted frames. This guarantees that telemetry data is correct even in electrically noisy environments. Cycle times can be as low as 10 ms per node, depending on baud rate and number of registers.

Implementation Details for Reliable Transmission

To implement direct Modbus telemetry, each peripheral node must contain a Modbus stack. For microcontroller-based nodes, libraries like FreeModbus or libmodbus are common. The node’s firmware maps sensor readings to predefined holding registers (e.g., register 0x0001 for temperature, 0x0002 for pressure). The main hub’s software, often a PLC or a PC with OPC server, reads these registers at fixed intervals.

Baud rate selection is critical. For 10–20 nodes, 115200 bps works well. For larger networks (up to 247 nodes), 9600 bps ensures signal integrity. Termination resistors (120 Ω) are mandatory at both ends of the RS-485 bus to prevent reflections. Bias resistors keep the bus in a known state when idle.

Error Handling and Retry Logic

If a slave does not respond within a timeout (typically 100 ms), the master retries twice. After three failures, the node is marked as offline. This mechanism prevents a single faulty node from stalling the entire network. Some implementations use broadcast messages (slave ID 0) for time synchronization, but telemetry data always uses addressed requests.

Advantages Over Alternative Architectures

Direct Modbus transmission avoids the complexity of MQTT brokers, OPC-UA servers, or cloud intermediaries. This reduces hardware cost and software overhead. For example, a temperature sensor with an RS-485 transceiver and a low-power MCU can cost under $15. The main hub can be a simple Raspberry Pi running a Python script, handling 50 nodes without issues.

Security is limited in plain Modbus, but for isolated industrial networks, this is acceptable. If remote access is needed, a VPN tunnel or a serial-to-Ethernet converter can be added at the main hub side, without changing the peripheral nodes. The protocol remains the same-Modbus RTU over serial or Modbus TCP over Ethernet.

FAQ:

What is the maximum number of peripheral nodes on one Modbus bus?

Up to 247 nodes with unique slave IDs, but practical limits are around 100 nodes due to polling time constraints.

Can Modbus telemetry work over wireless links?

Yes, using radio modems or Wi-Fi serial bridges, but latency increases and packet loss must be handled with retries.

Do peripheral nodes need external power?

Most do, but some low-power sensors can use power-over-Modbus (PoM) if the master provides DC voltage on the same twisted pair.

How is telemetry data timestamped?

The main hub assigns timestamps upon receipt. Peripheral nodes typically do not maintain real-time clocks.

Reviews

Marcus K.

We replaced a cloud-based system with direct Modbus from 40 sensors. Latency dropped from 2 seconds to 50 ms. Maintenance is trivial.

Elena R.

I implemented this in a water treatment plant. The RS-485 bus runs 800 meters with 32 nodes. Zero data loss in six months.

David L.

Using a Raspberry Pi as the main hub with libmodbus. Handles 60 temperature sensors flawlessly. Cost was under $200 for the whole setup.