Protocol note
Modbus to LoRaWAN: How to Connect Existing Meters and Controllers Wirelessly
Register maps, polling strategy, payload size and downlink writes — the details that decide whether a Modbus-to-LoRaWAN retrofit works.
MatrixAI LoRaWAN engineering team · · 7 min read
Why convert Modbus to LoRaWAN?
Energy meters, chillers, VFDs, pumps and PLCs very often speak Modbus RTU over RS485. Connecting them normally means cabling a bus back to a controller. A Modbus-to-LoRaWAN converter sits next to the device, polls the registers you need and sends them wirelessly — ideal when cabling is disruptive, expensive or physically difficult.
How the conversion works
- The converter acts as a Modbus master on the local RS485 bus.
- It reads a configured list of registers (address, function code, data type) at a set interval.
- Values are packed into a compact LoRaWAN payload and sent as an uplink.
- A decoder on the network server or IoT platform converts the payload back into engineering values.
- Optionally, downlink commands are translated into Modbus write operations.
Five checks before you buy converters
- Obtain the correct register map for the exact device model and firmware.
- Confirm data types, scaling and byte/word order (e.g. 32-bit floats).
- Count the registers needed per interval — LoRaWAN payloads are small, so select only what matters.
- Confirm power: mains-powered converters allow shorter intervals; battery units need a careful budget.
- Verify RF coverage at the device location, especially in plant rooms and basements.
Designing the reporting strategy
A common mistake is to send every available register. A better design sends cumulative values (such as kWh) at regular intervals and instantaneous values only where they are needed for control or alarms. Alarms can be sent immediately on change. This keeps airtime low, protects battery life and scales to many devices per gateway.
Writing to Modbus over LoRaWAN
Downlink writes are useful for setpoints, enable/disable commands and configuration. Because downlinks are slower than wired control and depend on device class, they should be used for supervisory commands rather than fast control loops, with confirmation of the resulting state.
Project-dependent compatibility
Compatibility is confirmed per device. Vendor-specific register behaviour, timing, security features and certification requirements can all affect an integration, so MatrixAI validates each device type during design and commissioning.