IoTServa Get Started
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.

5 minute readUpdated

A DIN-rail IoT gateway with RS-485 terminal blocks

A wrong word order looks plausible but is wrong. Always check one reading against a value you trust.

Four Tables, No Names

Modbus exposes four tables: coils, discrete inputs, input registers and holding registers. A register is just a 16-bit number. Nothing in the protocol says what it measures, so the manufacturer map is essential.

The Address Offset Trap

Manuals write addresses in two ways. Some use the traditional 40001 style, where 40012 is the 12th holding register, which is address 11 (counting from zero) on the wire. Others use the raw protocol address. Confirm which style the manual uses before polling, or you will read the neighbouring register.

Data Types Across Registers

Larger values span two or more registers. A 32-bit float uses two registers, and the device decides whether the high word or the low word comes first. This is word order, separate from byte order within each register. A mismatch gives values that look reasonable but are wrong.

Scaling and Units

Many devices store integers and expect a scale factor, so 2301 may mean 230.1 volts. Record the scale and unit in the profile once, rather than leaving every consumer to guess.

Verify One Reading

Before rolling out, compare one reading with a known value from the device display or a handheld meter. A single correct comparison catches offset, word order and scaling errors in one step.

Common Questions

What is a Modbus register map?

A register map is the manufacturer's table that says what each Modbus address holds: its meaning, data type, scale factor and unit. Modbus itself sends only 16-bit numbers, so without the map a value such as 2301 could be a voltage, a temperature or a counter.

Why is my Modbus value off by a factor or garbled?

The usual causes are a wrong scale factor, a wrong word order on 32-bit values, an address off by one from the 40001 convention, or reading a signed value as unsigned. Compare one reading with the device display to find which of these it is.

References

Start with One Site. Prove It on Real Devices.

Tell us which protocols are on site. We will scope a pilot that reads your real devices.

WhatsApp