Modbus Gateway with external power supply. Upload data via NB-IoT, LET-CatM1, LoRaWAN or LAN.
Support for Modbus ASCII, RTU and TCP.
The current Firmware does not support Modbus TCP or LAN/Ethernet connections, yet. Some features will be implemented in a future release and do not work yet. LoRaWAN Class C is currently not supported.
8000159 - Hybrid Modbus Gateway (ext. Power, Din-Rail)
8000166 - Hybrid Modbus Gateway (ext. Power, 230V)
Including: Antenna, 2x cable feedthrough
|8000171 - Hybrid Modbus Gateway V2 (Battery)|
Table of Content
The Lobaro Hybrid Modbus Gateway is a simple to use, cost and energy efficient device that reads, caches and forwards data via Modbus from any number of Modbus enabled devices into the Internet.
The Gateway can be used to communicate with Modbus Slave devices (ASCII/RTU on a RS-485 bus, TCP on over Ethernet) over NB-IoT, LTE-CatM1, LoRaWAN or LAN. Modbus commands can be transmitted via Downlink message to the Gateway and are forwarded by the Bridge to the connected Slave Devices. Received responses are forwarded as Uplink messages to the Lobaro IoT Platform. The Modbus Gateway can also be configured to execute Modbus commands regularly and report the responses at time of execution.
The Modbus Gateway supports reading of all four object types that can be provided by Modbus slave devices: Coil, Discrete Input, Input Register, and Holding Register. It also supports writing values to all writable objects: Coils and Holding Registers. Multiple different slave devices on the Bus can be accessed individually by a single Gateway device, even if the slave devices have a different Modbus configuration. Reading intervals and register definitions can be configured very flexibly to suit individual requirements.
Quick start guide
For details about each Steps please refer to the related detailed sections of the Manual below.
- Make sure the SIM card is inserted correctly when using NB-IoT or LTE-CatM1.
- Connect the Modbus Gateway to your Modbus Slave Devices
- Via RS485 connector using a twisted pair cable:
GNDis not strictly necessary but enhances the connection. Not all slave devices supply a
- Via ETH connector for Modbus TCP using a RJ45 LAN cable(externally powered variants only).
- Via RS485 connector using a twisted pair cable:
- Connect the Modbus Bridge to a computer using the Lobaro Configuration Adapter and the Lobaro Maintenance Tool.
- Connect power to the device - powering with the configuration adapter does not work.
- Make sure the configuration is correct to connect to the Internet (depends on you connection method: Mobile, LoRaWAN or LAN.
- Make sure the configuration is correct to read out your desired Modbus device (e.g. ASCII/RTU, Baud, Data Length, Stop Bits, Parity and Modbus Command).
- Optionally: Switch to the Log tab of the Lobaro Tool to see if the device is connecting and working as expected.
- Go to The Lobaro Platform and log into your account.
- Go to "Devices" and select your "Hybrid Modbus Gateway".
- If you have several Gateways: the "Address" is printed on the device's case as "DevEUI".
- You should see all Uplinks the Gateway collected sent far. Next step is to configure your individual Device Type to display you slaves data or forward data to your own IT.
The Lobaro Modbus Gateway works with all devices that act as a Modbus Client using RTU, ASCII (or, in a future release TCP). Some devices that have been used successfully with the Gateways are:
|Octave Ultrasonic Meter||Water meter||Arad Group||External Link|
|ECL Controller||Heat/Hot Water Regulation||Danfoss||External Link|
|UMD 97||Smart Grid Power Meter||PQ Plus||External Link (German)|
|DRS458DE||Power Meter||B+G E-Tech GmbH||External Link|
|Feuchtemessumformer PCE-P18 Modbus RTU||Humidity / Temperature sensor||PCE-Intruments||External Link (German)|
|Lobaro Pressure Sensor||Pressure Sensor||Lobaro||Sample Implementations|
For an overview about the Modbus protocol please refer to our documentation page about Modbus.
For a deeper introduction into Modbus please visit https://en.wikipedia.org/wiki/Modbus, which is a good place to start.
Please be aware that to configure the Gateway correctly, you will need to know the details of your installation and the slave devices you are trying to connect. Debugging a failing Modbus setup is quite complex, as there are many potential errors that cause the problems.
Please also note that even when you succeed in reading the data you need from the correct registers, neither the Gateway, nor the Lobaro Platform can know, what that data means. There is no semantic defined in Modbus; without additional information, the data is just bytes, that need to be interpreted by custom software. Registers can hold boolean values, signed or unsigned integers, floating point numbers or anything else. Often values span over multiple registers (each register holds exactly 2 bytes, so that e.g. 32bit integers will need two registers. There is also no dedicated byte order for Modbus, so that is not even trivial to read integers. This is a problem that is intrinsic to using Modbus and cannot be solved easily by a generic bridge device.
If you need support for creating a custom parser that processes the Uplinks and convert it to an easy to use format, please contact us, so that we can send you an offer for your individual use case.
Setting up the device
Connections as on the label:
- Vin - Supply voltage 12 - 24 Volt DC
- GND - Ground
- Vout - same as Vin
- A - Modbus ASCII/RTU line
- B - Modbus ASCII/RTU line
- GND - Ground
- ETH - Ethernet connection for LAN Uplink or Modbus TCP
- Connected cables must be between 0.05 mm² (AWG30) and 1.31 mm² (AWG16).
- Inserted cable length must be between 6mm and 7mm.
- Recommended wire termination:
- Weidmüller: H0,14/10 GR SV, Article No.: 9005180000, 8mm/6mm, max. AWG26
- Cables must not be connected or disconnected while the device is powered.
- Vout only supports small consumers like sensors with ≤ 1W. If in doubt, connect sensors to a dedicated power supply according to their manufacturer's instructions.
- Power supply via external mains adapter with 12 - 24 Volt DC
- Power output must be at least 2W and maximum 100W.
Radio (LoRa, FSK, NB-IoT, LTE Cat-M1)
|Female SMA Connector||Antenna||Nano SIM (4FF) for mobile connectivity|
The antenna is used for different radio technologies based on LoRa, FSK including LoRaWAN® and wireless MBUS S1, C1/T1 Modes (868 MHz), OMS v3 & v4.
The same antenna is also used for communication via NB-IoT and LTE Cat-M1. A Nano SIM (4FF) is required for mobile connectivity.
The SIM Card must not be inserted or removed while the device is powered.
Properties of compatible SMA Antennas:
|SMA Joint Rod Antenna (LTE, LoRa)|
|Frequency range||698-960 / 1710-2700 MHz|
|Antenna Gain||2 dBi|
|Max. Power||5 W|
|Material of dome||TPE|
|Lobaro Article No.||3000413|
The device was only tested with the listed antenna. Lobaro does not take liability for use with different antennas.
- Press the RESET Button to restart the device
- The RESET Button can be pressed through a small hole in the cover (e.g. with a paper clip). The position is marked with a ring on the label.
- The config port can only be reached when the cover is removed
- The configuration port is compatible with our 6-pin Lobaro USB Configuration Adapter (Article No. 8000005).
- A free to use configuration tool can be downloaded from the Lobaro website.
- Status information is visualized via the RGB LED
Mobile operator and LTE band configuration
If you are using a different mobile operator than pre-configured, you should change the mobile operator code set in the Config Parameters
Operator and (LTE)
Band Operator codes are 5 digit codes that indicate country and operator.
For details about configuration for mobile network operation please refer to our article about Mobile Network Connection
The device is shipped with default configuration parameters. The configuration can be changed via the 6-pin config port using the Lobaro USB Configuration Adapter.
More information about the usage of the configuration tools can be found in our documentation.
Remote Configuration is also supported after initial network connection.
Networking Parameters (NB-IoT / LoRaWAN)
|Name#LoRaWAN-RemoteConfiguration||Description||Default Value||Value Description & Examples|
|Radio technology used for connection to backend||lte|
Hostname / IP of the Lobaro Platform API
Not used for LoRaWAN uplink
|220.127.116.11 = platform.lobaro.com DNS is not supported yet|
Port number of the Lobaro Platform API
Not used for LoRaWAN uplink
NB-IoT Parameters (WAN = "lte", "nbiot", "ltem")
The LTE functionality is enabled if the
WAN parameter is set to
ltem. Using this mode requires an appropriate SIM-Card to be inserted.
|Name||Description||Default Value||Value Description & Examples|
|Mobile Operator Code (optional)|
|NB-IoT Band||"8", "20", "8,20", Empty = Auto detect (longer connecting time)|
|Mobile operator APN (optional)|
Vodafone Easy Connect: lpwa.vodafone.com (l = littel L)
|SIM PIN (optional)||Empty or 4 digits (e.g. |
LoRaWAN Parameters (WAN = "lorawan", "lorawan-abp")
|Name||Description||Default Value||Value Description & Examples||Since|
|DevEUI used to identify the Device||Device's own DevEUI as printed on label||8 bytes = 16 hex digits, e.g. |
|EUI used for OTAA (aka ||Individual default value for each device||8 bytes = 16 hex digits, e.g. |
|AES Key used for LoRaWAN||Individual default value for each device||16 bytes = 32 hex digits, e.g. |
|Minimal Spreading Factor used|
|LoRaWAN Operation Mode||v0.2.1|
Keep the value of
AppKey secret. If you change it, make sure you are using a good random source.
OTAA - Over the Air Activation
The preferred method to use LoRaWAN is Over The Air Activation (OTAA). When
WAN="lorawan" the device uses the values to perform an OTAA Join with the LoRaWAN Network Server. Make sure the values for DevEUI, JoinEUI, and AppKey match.
The device is manufactured with a globally unique EUI64 that is used as DevEui. This EUI is printed on the devices label and can be used to identify a device. You can change the DevEUI used for LoRaWAN by changing the configuration parameter
DevEUI. The device will still keep it's unique EUI64 it was delivered with. You can see it in the Log output during booting, even if a different value is used for the DevEUI.
Each Device will be configured with a unique JoinEUI and AppKey that are generated using a cryptographic hashing algorithm. Those values will seem random and are very likely to be unique for each device. These values are known to Lobaro but will not be made public. You can change the
AppKey if you prefere to have Keys that are known only to you. Be sure to use a good random source when generating keys.
ABP - Activation by personalisation
Our devices support activation by personalisation (ABP) when
WAN="lorawan-abp". This mode is useful for devices that have a bad reception. You will have to synchronise session keys by hand between the device and your Network Server when using ABP.
When using ABP, the device will use the parameters
AppKey for generating the session parameters:
DevAddrwill consist of the last for bytes of
NetSKeywill be cryptographically derived from
AppSKeywill be cryptographically derived from
The Values will be printed out in the Log after boot, so you can copy them to the configuration in your Network Server. Do change the
DevAddr, alter the
DevEUI value in the configuration. To create a different pair of session keys, change the value of
AppKey in the configuration. Best practise is, to change it to randomly generated bytes coming from a good random source. The generated Session Keys will be deterministic for a given value of
AppKey, even if used on different devices.
LAN Parameters (WAN = "lan")
Connection via LAN/Ethernet is not supported, yet.
Modbus related Parameters
|Name||Description||Default Value||Values Description & Examples|
|List of Modbus Commands with Cron and Modbus parameters (see below).||One or more entries of Modbus commands to be executed by the device. Each entry starts with a Cron expression defining when to execute the commands followed by the bus parameters used to address the Modbus slave devices. Each entry can contain multiple commands. See description below for a detailed explanation. †|
† See also our Introduction to Cron expressions.
MbCmd defines, what Modbus commands are executed on the Bus, when, and what Modbus Configuration to use for them. The configuration is very flexible and allows complex setups, that include executing different commands at individual intervals or times or using multiple different Modbus parameters to address incompatible Slaves on the same installation. Any Modbus command can be sent, including writing registers or diagnostic messages.
The command is entered in Hex and without any check sums and is 6 bytes long (12 hexdigits). The default value is
010300000003, it consists of 4 hex parts:
Address of the Slave Device. 1 byte: often 01 new devices
What kind of Modbus Register to read. 1 byte. 03 stand for Holding Register.
Number/address of the first register to read. 2 bytes. Many devices have some value to read out at 0000.
Number of consecutive registers to read from the first register. 2 bytes. This would read the registers #0, #1, and #2 in one command.
The default value of
0 0/5 * * * *:R,9600,8N1:010300000003 shows a very basic example with a single entry executed every 5 minutes using Modbus RTU to read 3 consecutive holding registers from a single slave device.
The parameter consists of up to 32 entries, separated by semicolons. Each entry consists of three parts, separated by colons: its individual Cron expression, the Modbus configuration used, and the Modbus commands to be executed. Each entry can have multiple Modbus commands to execute on activation, separated by comma. A Modbus command must be written as the Bytes to be sent on the bus in Hex notation. The check sums will be added by the device according to the protocol used.
Modes of operation (work cycle)
Subject to change! This product is still very young and experience might lead to adjustments in the future.
This chapter explains how the device starts and works to collect and upload data.
The starting process of the device is linear and executed the following steps in the order given here. The startup is triggered on power on or after a reset was triggered; this can happen over the reset button, by using the Lobaro tool over the config adapter, by sending a reboot command via Downlink, of if a fatal error occurs during operation of the device.
- On power on (or after a reset), the device will start by verifying the signature of the installed firmware. It will only continue the boot process if the signature is valid.
- The device will then activate the Arm TrustZone of its central processor, to prepare an isolated environment for the actual firmware to run. This activates hardware security mechanisms that protect the device from a wide range of errors and manipulations while it is running.
- Only then, the application program is started, having restricted access to the hardware.
- The application reads and outputs the configuration parameters programmed into it and verifies the configuration does not contain any obvious errors (like invalid syntax or impossible value combinations). If any fatal errors exist, the device will output information about it in the Log and then reboot, so that you spot invalid configurations directly when you set them.
- At this point the RGB-LED starts to continuously output the state of the Modbus connection and the connection to the backend.
- The device will try and execute every Modbus command from every entry in the configuration parameter
MbCmd, using the Modbus configuration of the entry (writing operations are skipped to avoid side effects). This allows you to check your Modbus configuration and the connection to the slave devices early on boot and even without a config adapter attached. The device will continue execution, even if the Modbus Commands fail, so that you can check the connection to the backend even when not connected to the Modbus slaves.
- After testing Modbus, the device will try to connect to the network for connection to the backend. The exact action will depend on your configuration:
- For NB-IoT or LTE-M the Gateway will activate its Modem and try to attach to the mobile provider. If that succeeds, it will try to connect to the backend configured (normally an instance of the Lobaro Platform). If that succeeds, the device will upload some information about itself to the backend (including its configuration) and than synchronise its internal clock over the connection. Only if all this succeeds, the device will move on.
- For LoRaWAN with OTAA, the device will perform an OTAA Join operation with the LoRaWAN Network Server. If that succeeds, the device will upload a Status Message that will also be used to synchronise its internal clock with the network. Only if that succeeds, the device will move on. On failure, the device will retry with increasing timeouts to perform the join operation and time sync, until it succeeds.
- For LoRaWAN with ABP there is no explicit joining operation, as the session must already exist between Network Server and Device. It simply uploads a Status Message that will also be used to synchronise the internal clock. If the synching fails multiple times, the device will skip synchronisation and just move on to start normal operations. Be aware that this can lead to the Device operating with a clock that does not match real time. The Modbus Commands will be executed according to that clock, which will most likely not be consistent with what you expect. This exception is introduced on purpose, as ABP is meant to make the device usable in locations, where there is poor Downlink reception from the Network, where an OTAA Join cannot be performed, but Uplink messages still might be coming through to the Network. The device will continue to try and synchronise its clock every day and might succeed at some point in the future. The changing of the clock will be compensated as well as possible, but the exact times when commands are executed is most likely to change at that point.
- When the connection to the backend has been established (this is not certain to have succeeded when using LoRaWAN ABP), the device will start its internal scheduler and will from this moment on be running in normal operation mode.
The actions executed by the device during normal operation are controlled by a scheduler that executes a list of jobs whenever it is their time to run. Only a single job will be executed at any time, so if a job is running for some time, other jobs will be executed delayed (but the execution will not be skipped). Each entry you add to the
MbCmd config parameter will have its own job in the scheduler. The Cron Expression of the entry will control, how often and when the job will be executed. In addition to that there will be a Status job which runs once every day and triggers the upload of a status message which will also perform a clock synchronisation. When your configuration has multiple entries that are scheduled for the same time, they will be executed in the order you put them in the configuration.
The jobs will generate Uplink messages that need to be uploaded. Those will be queued and upload in the order they are generated. The device will continue to execute jobs while handling uploads. When Uplinks are generated faster than they can be sent, the queue will run full and new Uplinks will be dropped silently. This is most likely to happen when using LoRaWAN on higher spreading factors, as the Gateway can read data over Modbus much faster than it can be sent over LoRaWAN.
After each Uplink sent, the device will look for Downlinks coming from the Network (this is done for both, LoRaWAN and LTE configurations). Downlinks can contain remote commands controlling the device (like configuration changes, reboot requests, or (for LTE only) remote firmware updates). There can also be Modbus commands sent via Downlink that will be executed on the bus by the Gateway directly (the response from the slave will be sent as Uplink). Downlink Modbus commands are currently only supported for LoRaWAN.
The daily Status message Uplink makes sure that the device can be reached for remote configuration within 24 hours, independent of the current configuration.
Changing configuration or performing a firmware update will result in the Gateway rebooting. We try our best to keep our devices from ever reaching a state that makes them unreachable. A new configuration set via Downlink will be temporary until a connection to the Network can be established again. If the new configuration fails to connect to the Network, the previous configuration is restored.
Mobile data consumption
Uploading one Uplink with 400 bytes including all metadata (might be less, depending on the configuration).
|Telegram upload interval||Monthly NB-IoT data usage|
|1 each Day||~12 kB|
|8 each Day (every 3h)||~100 kB|
|400 each Week||~700 kB|
|250 each Day||~3 MB|
All calculations are estimations and might vary depending on the configuration
The Lobaro Platform
The easiest way to work with the Lobaro Modbus Gateway is the Lobaro Platform. You can find it under https://platform.lobaro.com – Log in with the credentials provided by Lobaro.
Your Gateways should be listed under "Devices". If you have multiple devices in your account, you can distinguish them by the field "Address". The Address is printed on the box of the Gateway (the Address is the IMEI of the modem used by the device; that is the unique hardware address used for mobile communication).
Data messages differ between LoRaWAN and LTE/LAN upload. While LoRaWAN messages are defined by Port and Byte pattern, LTE/LAN Uplinks are encoded as structured data (CBOR).
Since LoRaWAN Uplinks are limited to ~50 Bytes some information that are available on other transport might be skipped.
For now please refer to our Modbus LoRaWAN Bridge - We try to keep the payloads similar.