4. Conguration
4.3.2. wMBUS bridge parameters
Table 4 lists all parameters that a relevant for wireless M-Bus bridge rmware behavior:
Name
Type
Description
loraMaxMsgSize int
Received wireless M-Bus telegrams might have a byte size big-
ger than a single LoRaWAN message can hold. This parameter
denes the bytes per LoRaWAN message before a partition over
multiple LoRaWAN Uplink msg appears. (Range 10-50 bytes)
resetHours
int
Hours after which the rmware will reset and rejoin the net-
work. Can support the change of LoRaWAN network providers
with already deployed devices. (0 = never)
cmodeCron
string Cron Expression dening when the device starts wMBUS
T1/C1 mode receive phases. Please refer to chapter 4.3.3
for an introduction. (blank = no T1/C1 receive)
cmodeDurSec
int
Duration in seconds for each C1/T1-mode wMBUS receive
phase, if cmodeCron != blank. Should be chosen in relation
the wMBUS sendout interval of the target meter.
smodeCron
string Cron Expression dening when the device starts wMBUS S1
mode receive phases. Please refer to chapter 4.3.3 for an in-
troduction. (blank = no S1 receive)
smodeDurSec
int
Duration in seconds for each S1-mode wMBUS receive phase, if
smodeCron != blank. Should be chosen in relation the wMBUS
sendout interval of the target meter.
devFilter
string wMBUS device id white-list lter using 8 digits with leading
zeros list separated by `,'. Example `88009035,06198833'.
(blank = lter inactive)
mFilter
string wMBUS manufacturer white-list lter separated by `,' . Ex-
ample: `DME,QDS' for receiving just telegrams from Diehl
Metering GmbH and Qundis GmbH meters. Telegrams with
dierent 3 character wMBUS manufacturer id will not be up-
loaded via LoRaWAN. (blank = lter inactive)
typFilter
string wMBUS device type white-list lter list separated by `,'. Ex-
ample: `08,07' for Heat-Cost and Water meters. Please refer
to appendix B.1 for a list of possible values. (blank = lter
inactive)
Table 4: wMBUS bridge parameters
wMBUS over LoRaWAN Bridge
13
