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.
Poll Modbus RTU and Modbus TCP devices, decode registers with the right word order and scaling, and publish clean engineering values.

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.
site.plant-1.mdb-03.active-power
184.2kW
Describe a device once as a profile of addresses, data types, scale factors and units, then reuse it across every identical meter.
Choose big or little endian and word swap per register block, so a 32-bit float reads correctly the first time.
Poll serial devices on RS-485 and Ethernet devices on port 502 in one project, with per-device timing.
Group contiguous registers into single requests and set per-bus timing so a long daisy chain stays responsive.
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.
You can, or send the device manual and the engineering team will build the profile. Profiles are reused for every identical device.
Yes. Modbus RTU over RS-485 and Modbus TCP are both supported and can sit in the same project.
Tell us the make and model of what is on site. We will scope a pilot against your real equipment.