Wireless M-Bus NB-IoT Gateway with external power supply.
Model | LOB-GW-DINRAIL-HYB-WMBUS |
Order number |
|
8000157 - Wireless M-Bus Gateway (ext. Power, Din-Rail) Including: Antenna | 8000158 - Wireless M-Bus Gateway (ext. Power, 230V) Including: Antenna, 1x cable feedthrough |
Table of Content
Table of Contents | ||
---|---|---|
|
...
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.
...
Properties of compatible SMA Antennas:
SMA Joint Rod Antenna (LTE, LoRa) | |
---|---|
Frequency range | 698-960 / 1710-2700 MHz |
Length | 108 mm |
Antenna Gain | 2 dBi |
V.S.W.R | <= 2.5 |
Radiation | Omnidirektional |
Polarisation | Vertical |
Max. Power | 5 W |
Impedance | 50 Ohm |
Connector | SMA Male |
Material of dome | TPE |
Lobaro Article Nr. | 3000413 |
Note |
---|
The device was only tested with the listed antenna. Lobar does not take liability for the use with other antennas. |
...
Info |
---|
For details about configuration for mobile network operation please refer to our article about Mobile Network ConnectionLTE / NB-IoT Networks |
Configuration
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.
...
Info |
---|
Remote Configuration is also supported after initial network connection. |
Connection Parameters
Name | Description | Default Value | Value Description & Examples |
---|---|---|---|
WAN | Uplink techoology | lte | Possible values: lte , lorawan |
LoRaWAN Parameters
Name | Description | Default Value | Value Description & Examples |
---|---|---|---|
OTAA | Activation: OTAA or ABP | true | true = use OTAA, false = use ABP |
DevEUI | DevEUI used to identify the Device | e.g. 0123456789abcdef | |
JoinEUI | Used for OTAA (called AppEUI in v1.0) | e.g. 0123456789abcdef | |
AppKey | Key used for OTAA (LoRaWAN v1.0.x and v1.1) | ||
NwkKey | Key used for OTAA (LoRaWAN v1.1 only) | ||
| Initial and maximum Spearding Factor | 12 | |
ADR | Adaptiv Data Rate (ADR) enabled | true | |
TimeSync | Days after which to sync time over LoRaWAN | 0 | days, 0 =don't sync time |
RemoteConf | Allow remote config via LoRaWAN | true | |
LostReboot | Days without downlink before reboot | 7 | days, 0 =never reboot |
PayloadFormat |
| 0 | For details see manual of wMBUS LoRaWAN bridge |
NB-IoT Parameters
The NB-IoT functionality is enabled if the WAN
parameter is set to "lte". A SIM-Card has to inserted.
Name | Description | Default Value | Value Description & Examples | |
---|---|---|---|---|
Host | Hostname / IP of the Lobaro Platform API | 94.130.20.37 | 94.130.20.37 = backend.lobaro.com DNS is not supported yet | |
Port | Port number of the Lobaro Platform API | 5683 | ||
Operator | Mobile Operator Code | 26201 | 26201 (=Deutsche Telekom), for other operators, see above. | |
Band | NB-IoT Band | 8 | "8", "20", "8,20", Empty = Auto detect (longer connecting time) | |
APN | Mobile operator APN | iot.1nce.net | 1nce: iot.1nce.net Vodafone Easy Connect: lpwa.vodafone.com (l = |
little L) | ||||
PIN | SIM PIN (since v0.7.0) | Empty or 4 digits (e.g. 1234) | ||
UseNbiot | Try to connect with NB-IoT | true | ||
UseLtem | Try to fallback to LTE-M when supported by the Modem | false | not supported with all Hardware revisions |
Metering reception Parameters
Name | Description | Default Value | Default Values & Examples | |||||
---|---|---|---|---|---|---|---|---|
cmodeDurSec | Duration (Seconds) of wireless M-Bus C1/T1-mode receive | 300 | 0 = Do not collect C1/T1 mode | |||||
smodeDurSec | Duration (Seconds) of wireless M-Bus S1-mode receive | 0 | 0 = Do not collect S1 mode | |||||
xmodeDurSec | Duration (Seconds) of Sensus RF receive | 0 | 0 = Do not collect Sensus RF telegrams | |||||
mFilter | wMBus manufacturer filter sep. by , e.g. dme,itw (Comma separated list WITHOUT spaces) | blank = no filter, not used for xmode (Sensus RF) | ||||||
typFilter | meter device type filter e.g. 08,07 for Heat Cost and Water (Comma separated list WITHOUT spaces) |
| ||||||
devFilter | meter id filter e.g.
| blank = no filter | ||||||
maxTelegrams | Maximum number of telegrams to receive. If reached, the upload is started. | 0 | ||||||
listenCron | Cron expression† defining when to receive wMBUS | 0 0 12 * * * | 0 0 12 * * * = (once per day) | |||||
extRam | Configure paramters for the external ram in format: <bytes>,<type>
| empty |
|
† See also our Introduction to Cron expressions.
...
Uploading one wMbus telegram consumes approximately 400 bytes data including all metadata.
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 varry depending on the configuration
...
CE Declaration of Conformity
View file | ||||
---|---|---|---|---|
|