Table of Contents
Advertisement
Quick Links
Manual wMBUS Bridge v1.x
Outdated Version v1.x
Outdated product version
This manual is only valid for firmwares version up to
Firmware V1.6.0 is deprecated since 02/2020. For revision v2.x please refer to the
documentation v2.x
Overview
The Lobaro wireless M-Bus (wMBUS) to LoRaWAN Bridge is a cost-effective & energy efficient device
that receives, caches and transparently forwards wireless M-Bus metering data from up to 500
consumption meters via any LoRaWAN network onto the Internet.
Many gas, water, electricity and heat meters can be read wirelessly today using the common short range
Wireless M-Bus standard. Because such wMBUS enabled meters use the classical energy saving FSK
radio modulation, the wireless range is often limited to less than 50m and therefore requires the use of
additional longer-range radio technologies to forward the metering data onto the Internet. The advanced
LoRa radio modulation used inside the Lobaro wMBUS to LoRaWAN Bridge is such a key technology.
blocked URL
LoRaWAN based LPWANs (Low Power wide area networks) allow connections to the Internet from small
battery powered devices with wireless ranges of up to 5 kilometers between the transmitter and receiving
gateway antenna - without the usual cellular network costs in classical M2M or smart metering solutions.
Also - unlike with cellular networks - it's possible to setup own gateways if needed. This often results in
much lower operational costs with the Lobaro wMBUS bridge compared to conventional remote meter
reading via LTE networks. The metering data will not be decrypted by the LoRaWAN Bridge, instead an
unchanged 1:1 forwarding takes place via one or more LoRaWAN packets (depending on the wMBUS
telegram byte size). Thus the end-to-end encryption of sensitive wireless MBUS consumption data is
preserved. Initial configuration, firmware updates & status readouts are done user-friendly via USB on
the PC with the Lobaro Tool (Windows, Linux, Mac). An additional possibility of configuration in the field
"over the air" by means of LoRaWAN downlinks will soon also be available via firmware update.
Please read the manual carefully before operating the device. A safe operation of the device is
only possible if you follow the guides provided in this manual. Using the device differently than
intended by Lobaro may cause damage to people, the environment, or the device.
Consider using the latest firmware on your hardware
See available firmware downloads
The Device
Variants no longer available
These device variants are no longer available. Please see current documentation for available
options.
Please refer to the
current documentation v2.x
Variant with compact housing (2xAA batteries)
wMBUS LoRaWAN Bridge (AA-cells, compact IP65 housing), Order number: -
blocked URL
Variant with D-cell battery
wMBUS LoRaWAN Bridge (XH battery-connector, IP67 housing), Order number: -
blocked URL
Device installation
.
.
V1.6.0
and hardware revisions
Overview
The Device
V1.x
!
current
Work Cycle
Configuration
LoRaWAN Data Upload
Formats
Technical characteristics
Target Measurement / Purpose
Parser
CE Declaration of Conformity /
PDF Manual
Firmware v1.x
Variant with compact
housing (2xAA
batteries)
Variant with D-cell
battery
Device installation
Power Supply
Battery life time
Example
calculation
Usage
scenario
recommenda
tions
Initial Phase
LoRaWAN Join
Phase
Data Collection Phase
Data Transfer Phase
Sleep Phase
The Lobaro
Maintenance Tool
Connecting the USB
config adapter
System parameters
LoRaWAN
network
parameters
wMBUS
bridge
parameters
Cron
expressions
Status Packet
Data Packet
Examples
Upload Rate
Decoding
wireless M-
Bus
Housing Dimensions
TTN
v1.6.0 (20.05.2019)
v1.5.8 (18.02.2019)
v1.5.7 (07.01.2019)
v1.5.6 (20.11.2018)
v1.5.5 (14.11.2018)
v1.5.4 (25.10.2018)
v1.5.3 (18.10.2018)
v1.5.2
v1.5.1
v1.5.0
v1.4.1
v1.4.0
v1.3.1
v1.3.0
v1.2.0
v1.1.0
Advertisement
Table of Contents
Related Manuals for Lobaro wMBUS
Summary of Contents for Lobaro wMBUS
- Page 1 LoRaWAN Join additional longer-range radio technologies to forward the metering data onto the Internet. The advanced Phase LoRa radio modulation used inside the Lobaro wMBUS to LoRaWAN Bridge is such a key technology. Data Collection Phase Data Transfer Phase blocked URL...
-
Page 2: Power Supply
M-Bus listen period of 20 seconds by setting the bridge configuration parameter cmodeDurSec to a value of 20 (refer to section "wMBUS bridge parameters"). This will ensure that all meters of interest sent their consumption telegrams at least onces during the configured listen period of the bridge. For a worst-case battery-lifetime calculation the weakest possible LoRaWAN connectivity has been selected. -
Page 3: Work Cycle
23.0 Usage scenario recommendations As a simple rule of thumb using the Lobaro wireless M-Bus over LoRaWAN bridge is a good fit in applications that require daily (or less often) consumption values of 1 to 40 installed wireless M-Bus meters. For installations with a higher meter count simply more Lobaro bridges may be used. Another... - Page 4 Data Collection Phase During the wMBUS collection phase the device receives any wireless M-Bus data with valid CRC and stores it for the following LoRaWAN upload phase but only if the received telegram passes the user defined white list filters. Similar telegrams of one identical meter may be received multiple times during this phase.
- Page 5 Should be chosen in relation the wMBUS sendout interval of the target meter. devFilter string wMBUS device id white-list filter using 8 digits with leading zeros list separated by ','. Example '88009035,06198833'. (blank = filter inactive) mFilter string wMBUS manufacturer white-list filter separated by ',' . Example: 'DME,QDS' for receiving just telegrams from Diehl Metering GmbH and Qundis GmbH meters.
-
Page 6: Status Packet
The Things Network Data Packet After each wMBUS collecting phase, all saved telegrams (up to 500 can be stored) will be uploaded via LoRaWAN uplink messages as fast as possible. The received wMBUS telegrams that did pass the configured white list filters will be uploaded without any modification in one or more LoRaWAN messages. -
Page 7: Technical Characteristics
Examples Examples (with loraMaxMsgSize = 50): A 48 Byte wMBUS telegram will be send on LoRaWAN port 11. Port 11 says it is the first message of only one message (no splitting). A 75 byte wMBUS telegram will be send in two messages on LoRaWAN ports 12 and 22. Port 12 means this part one of a wMBUS telegram that got splitted into two LoRaWAN messages. -
Page 8: Housing Dimensions
Power Supply Nominal Supply Voltage Supply Voltage Range 2.2V - 3.7V Power supply 2xAA battery, 1.5V (LR6/FR6) 5V USB powered over Lobaro Adapter On Request: 230V mains adapter, 3.6V Battery Current consumption @3V Normal 3 mA Wireless M-BUS RX 14 mA... - Page 9 = bytes[6]; decoded.data0 = bytes[7]; decoded.data1 = bytes[8]; decoded.data2 = bytes[9]; // example decoder for status packet by lobaro if (port === 1 && bytes.length == 9) { // status packet decoded.FirmwareVersion = String.fromCharCode.apply(null, bytes. slice(0, 5)); // byte 0-4 decoded.Vbat = (bytes[5] | bytes[6] <<...
- Page 10 Add additional config parameter "cmodeCompatibility" to allow wideband receive as fallback fix issue with crc validation of unencrypted meters v1.5.8 (18.02.2019) Reduce chance to miss wMbus packet when there is a lot of traffic v1.5.7 (07.01.2019) Fix issue with very large T1 mode telegrams v1.5.6 (20.11.2018)
- Page 11 v1.3.0 Allow to enable ADR (default: enabled) v1.2.0 Increase config version (Config will be reset) Introduce LoRaWAN default parameter v1.1.0 New Filter: device id (devFilter), device type (typFilter), manufacturer (mFilter)
Need help?
Do you have a question about the wMBUS and is the answer not in the manual?
Questions and answers