Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
General Information
The Dzero Gateway 4X is a device that can be used to readout modern utility meters with standardized infrared "INFO" interface.
The meter outputs over its infrared "INFO" interface a serial protocol conforming to the Smart Meter Language Protocol 1.04 (SML) or IEC 62056-21 protocol. This interface is intended to be used by end-users and not for billing purposes of the electricity supplier.
The read information normally contains the current consumption values of the meter and gets interpreted and forwarded by the Dzero Gateway 4X via a LoRaWAN or Nb-IoT to web based applications interested in further processing this data.
| Warning | ||
|---|---|---|
| ||
Older meters with "infrared pulse" output are not compatible to the Dzero Gateway 4X. Please check our list of compatible meters to make sure it is equipped with the correct interface. |
| Note | ||
|---|---|---|
| ||
Consider using the latest firmware on your hardware
|
Compatible utility meters
Any meter that adheres to the standard can be read. The following list contains meters that we successfully tested.
Electricity meter | Manufacturer |
|---|---|
| DTZ541-ZEBA | Holley |
| LK13 series | Logarex |
| OpenWay® 3.HZ | iTron |
| SGM-C4 series | efr |
| SGM-D series | efr |
| eHZ-K series | EMH |
| mMe4.0 series | EMH |
| ED300 series | EMH |
| eBZD series | EMH |
| E320 | Landis+Gyr |
| MT681 | ISKRA |
Quickstart
- Connect to the device with the Lobaro Tool using the Lobaro Config Adapter
- Under Configuration click "Reload Config" and change the fields "ReadCron" and "ObisCode" for all connected heads as needed as well as choosing the desired Network Connection by setting the "WAN" followed by clicking on "Write to Device".
- If you selected lorawan as WAN: Register the device in your LoRaWAN network
- Place the EDL21 opto head on the "Info" interface
- Restart the device by pressing the reset button
Configuration
The configuration is done using Lobaro Maintenance Tool and the Lobaro USB PC adapter or remote via LoRaWAN downlink (see LoRaWAN Downlink Config) or LTE.
Network (general)
| Name#LoRaWAN-RemoteConfiguration | Description | Default Value | Value Description & Examples |
|---|---|---|---|
WAN | Radio technology used for connection to backend | lte |
|
Host |
PortPort number of the Lobaro Platform API
Not used for LoRaWAN uplink
5683
LoRaWAN
The connection to the LoRaWAN network is defined by multiple configuration parameters. This need to be set according to your LoRaWAN network and the way your device is supposed to be attached to it, or the device will not be able to send any data.
For a detailed introduction into how this values need to be configured, please refer to the chapter LoRaWAN configuration in our LoRaWAN background article.
| Name#LoRaWAN-RemoteConfiguration | Description | Default Value | Value Description & Examples |
|---|---|---|---|
LostReboot | Days without downlink before reboot (triggers downlinks) | 5 | days, 0=don't reboot |
DevEUI | DevEUI used to identify the Device | e.g. 0123456789abcdef | |
AppKey | Key used for OTAA (v1.0 and v1.1) | ||
NwkKey | Key used for OTAA (v1.1 only) | ||
JoinEUI | Used for OTAA (called AppEUI in v1.0) | e.g. 0123456789abcdef | |
SF | Spreading Factor | 12 |
LTE
| Name#LoRaWAN-RemoteConfiguration | Description | Default Value | Value Description & Examples |
|---|---|---|---|
Host | Hostname / IP of the Lobaro Platform API | coaps://platform.lobaro.com,coap://platform.lobaro.com | |
Operator | Mobile Operator Code (optional) | 26201 | 26201 (=Deutsche Telekom), for other operators, see above. Empty = Auto detect (longer connecting time) |
Band | NB-IoT Band | "8", "20", "8,20", Empty = Auto detect (longer connecting time) | |
APN | Mobile operator APN (optional) | * | 1nce: iot.1nce.net Vodafone Easy Connect: lpwa.vodafone.com (l = littel L) |
PIN | SIM PIN (optional) | Empty or 4 digits (e.g. 1234) | |
DNS | DNS Server | 9.9.9.9,1.1.1.1 | |
UseNbiot | true | ||
UseLtem | true |
wMBus (experimental)
| Name#LoRaWAN-RemoteConfiguration | Description | Default Value | Value Description & Examples |
|---|---|---|---|
EncryptionMode | 7 | 7 | 5 or 7 |
Operation
Configuration values defining the behaviour of the device.
| Name#LoRaWAN-RemoteConfiguration | Description | Default Value | Value Description & Examples |
|---|---|---|---|
ObisCode1 | Comma separated list of ObisCodes to select a subset of the available information on port 1 | ||
ObisCode2 | Comma separated list of ObisCodes to select a subset of the available information on port 2 | ||
ObisCode3 | Comma separated list of ObisCodes to select a subset of the available information on port 3 | ||
ObisCode4 | Comma separated list of ObisCodes to select a subset of the available information on port 4 | ||
PayloadFormat | Format used for data upload (include timestamps or not) | int | 1=no timestamp, 2=include timestamp |
ReadCron | Cron expression defining when to read and upload | 0 0/15 * * * * | 0 0/15 * * * * for every 15 minutes |
VerboseLogging | Enables additional Debug output | false | true = enabled, false = disabled |
See also our Introduction to Cron expressions and our Introduction to Obis Codes.
| Table of Contents |
|---|