Modbus
Modbus in Niagara looks simple on paper – registers in, values out. In practice the work is in the register maps: undocumented scaling, packed bits, byte-order surprises, and meters that answer slowly enough to stall a poll cycle. Software Pile integrates Modbus TCP and RTU devices into Niagara stations so the data is right, not just present.
What We Handle
- Register mapping from vendor documentation – or reverse-engineering when the documentation is wrong or missing
- Data-type handling: signed/unsigned, 32-bit floats across register pairs, byte and word order, bitfields
- Poll-cycle design for mixed-speed devices on shared RTU trunks, so one slow meter does not starve the rest
- Gateway topologies: serial devices behind TCP gateways, addressing and timeout behavior included
- Histories, alarms, and totalization on Modbus points that arrive as raw counts
Energy Metering, Done Right
Most of our Modbus work is meters: power, gas, water, BTU. We validate scaling against the meter face before histories start recording, because a wrong multiplier discovered six months later poisons every report built on it.
Getting Started
Send the device list and register maps you have – plus your Niagara version and whether devices are TCP or RTU behind gateways. If the documentation is missing, say so; that changes the approach, not the feasibility.