IoTServa Get Started
Protocol Support

Modbus Integration

Poll Modbus RTU and Modbus TCP devices, decode registers with the right word order and scaling, and publish clean engineering values.

Standard
Modbus Application Protocol (Modbus Organization)
Medium
RS-485 or RS-232 (RTU), Ethernet port 502 (TCP)
Topology
Client and server (master and slave)
Data Model
Four tables: coils, discrete inputs, input registers, holding registers
A DIN-rail IoT gateway with RS-485 terminal blocks, the wiring used to reach Modbus RTU meters and drives

What Modbus Is

Modbus is the simplest and most widespread industrial protocol. A client asks a server for a block of registers and gets numbers back. The numbers have no names or units, so the real work is the register map: which address is the voltage, how many registers make a 32-bit float, and which word comes first.

Native Address

Unit 5 (RTU, 9600 baud, 8E1)
Holding register 40012
INT16 raw 1842, scale 0.1

Node

Plant 1 > MDB-03 > Active Power

184.2kW

How IoTServa Connects Modbus

Register Map Profiles

Describe a device once as a profile of addresses, data types, scale factors and units, then reuse it across every identical meter.

Byte and Word Order

Choose big or little endian and word swap per register block, so a 32-bit float reads correctly the first time.

RTU and TCP Together

Poll serial devices on RS-485 and Ethernet devices on port 502 in one project, with per-device timing.

Polite Polling

Group contiguous registers into single requests and set per-bus timing so a long daisy chain stays responsive.

Typical Jobs

  • Sub-metering and power quality
  • Variable frequency drive status and faults
  • PLC and generator data into one history
  • Retrofitting old equipment with no network

Plan for These

  • Register addresses are written two ways: with or without the 40001 offset. Confirm against the device manual.

  • RS-485 needs correct termination, biasing and a unique slave address per device.

  • A value with a wrong word order looks plausible but is wrong. Always check one reading against a known value.

Learn More About Modbus

BACnet vs Modbus: Which Protocol Fits Which Job

BACnet and Modbus both run buildings and plants, but they model data differently. Compare their networks, discovery and addressing, and see where each fits.

Read the Guide

Modbus Register Maps: Addresses, Word Order, Scaling

A Modbus reading is only as good as its register map. Learn the 40001 address offset, word order and scaling mistakes that give plausible but wrong values.

Read the Guide

Modbus to MQTT: Publishing Register Values as Topics

How to turn Modbus registers into MQTT topics: polling, decoding scale and word order, topic and payload design, QoS, retained values and failure handling.

Read the Guide

Modbus RTU vs Modbus TCP: Wiring, Addressing, Speed

Compare Modbus RTU over RS-485 with Modbus TCP over Ethernet: wiring and termination, device addressing, speed, converters and when to choose each.

Read the Guide

Alert Rules for Silent IoT Sensors and Low Batteries

A threshold alert cannot see a dead sensor. Learn rules for missing data, low battery, weak signal and rate of change, with delays that avoid false alarms.

Read the Guide

Energy Sub-Metering with Modbus: Setup Guide

Read Modbus energy meters and inverters with consistent units, correct scaling and a balance check against the main incomer, for tenants, lines and solar.

Read the Guide

RS-485 Wiring Best Practices: Cable, Termination, Biasing

Daisy-chain topology, 120 ohm termination, bias resistors, shielded twisted pair, grounding and length limits. Get the RS-485 trunk right before the software.

Read the Guide

Modbus RTU Troubleshooting: Timeouts, CRC Errors and Silence

Work through serial settings, addresses, wiring, termination and timing when a Modbus RTU device does not answer or keeps returning damaged frames.

Read the Guide

Cold Room Temperature Monitoring: Sensors and Alerts

Where to place temperature sensors in a cold room, how often to read them, how to alert without false alarms from door openings, and what records to keep.

Read the Guide

Data Quality in IoT: Why a Stale Reading Is Worse Than a Gap

What good, stale and bad quality flags mean, how store and forward keeps history honest during outages, and why dashboards should never repeat an old value.

Read the Guide

Commercial Buildings

HVAC, metering and lighting from different vendors, in one view.

See the Solution

Factories and Plants

Drives, meters and PLCs trended together, with alarms that mean something.

See the Solution

Energy and Solar

Generation and consumption reconciled in one view.

See the Solution

Cold Chain

Temperature coverage for cold rooms, with sensor health tracked.

See the Solution

Hotels and Campuses

Rooms, plant and meters across many buildings.

See the Solution

Estates and Agriculture

Sensors across land where Wi-Fi and cables never reach.

See the Solution

Look Up a Term in the Glossary or check devices on the Hardware Page

Works Alongside the Others

A site rarely runs a single protocol. The same project can read all eight.

Modbus Questions

Do I need to write the register map myself?

You can, or send the device manual and the engineering team builds and verifies the profile. A profile records addresses, data types, scaling and units once, then applies to every identical device, so the second meter or drive is configuration rather than new engineering work.

Can IoTServa read both serial and Ethernet Modbus?

Yes. Modbus RTU over RS-485 and Modbus TCP are both supported and can sit in the same project, each with its own timing. Serial trunks are read through a gateway wired to the bus, and Ethernet devices are read over the network on port 502.

What is the difference between Modbus RTU and Modbus TCP?

Modbus RTU sends binary frames over a serial line such as RS-485, with a CRC for error checking, and the bus is shared by many devices. Modbus TCP wraps the same register model in a TCP packet on Ethernet, normally on port 502. The registers mean the same thing in both; only the transport differs.

Why does a Modbus register read the wrong value?

The common causes are an address off by one from the 40001 offset convention, a wrong word order on 32-bit values, a missing scale factor, or the wrong signed or unsigned type. Check the manufacturer register map and compare one reading against the device display before trusting the rest.

Bring Your Modbus Devices. We Will Read Them.

Tell us the make and model of what is on site. We will scope a pilot against your real equipment.

WhatsApp