LoRaWAN DETAILSStatus Message - Device Status
Message sent to LoRaWAN Port number 1 in every connection to LoRaWAN Server
4 Bytes: LKM Device Id
1 Byte: Frame Type (Lower 4 bits) and Package Number (Upper 4 bits). If Package Number is 1 or more that means the package splitted.
0x00 : means status package for device status and package is the first package
1 Byte: Number of Meters configured to be read1 Byte: Number of OBIS Codes configured to be read
1 Byte: LoRaWAN Port of the package4 Bytes: RTC Time
3 Bytes: LKM Device firmware version
N Bytes (maximum 22): LKM Device name configured by userStatus Message - OBIS DetailsMessage sent to LoRaWAN Port number 1 in every connection to LoRaWAN Server if enabled by user
4 Bytes: LKM Device Id1 Byte: Frame Type (Lower 4 bits) and Package Number (Upper 4 bits). If Package Number is 1 or more that means the package splitted.
0x01 : means status package for OBIS details and package is the first package
OBIS Frames are shared 1 by 1 in following format, qty is given in Device Status message
1 Byte: OBIS Code Number in same sequence configured from web interface1 Byte: Hexadecminal character 0x1F as seperator character
N Bytes
(maximum 15): Configured OBIS Code itself like "1.8.0", each character in ASCII format1 Byte: Hexadecminal character 0x1F as seperator character
....Next Obis Frame that maximum payload size allows.
Meter Data Message - Parsed from Meter ReadingMessage sent to LoRaWAN configured port and minimum send interval can be configured by user
4 Bytes: LKM Device Id
1 Byte: Frame Type (Lower 4 bits) and Package Number (Upper 4 bits). If Package Number is 1 or more that means the package splitted.
0x02 : means meter data package and package is the first package1 Byte:
Read Meter number in same sequence configured from web interface1 Byte: Data Starting OBIS Code Number in same sequence configured from web interface
1 Byte: Total Data Size in Payload
Meter Data Frames are shared 1 by 1 in following format, each data is 4 Bytes
4 Bytes: Meter Data
....Next data that maximum payload size allows.
MODBUS DETAILSUp to 20 meters can be read and mapped to Modbus Registers
Up to 48 OBIS values can be mapped into Modbus Registers
Gateway Modbus AddressDefault value is 1User can change from web interface
Modbus Data and AddressesData can be read via Function Code 3
Read Holding Registers (4x)
all registers are "long" data
Adress of 1st Meter Data:Hex: 0x00 00
Decimal: 0
Quantity: 96 (only available if 48 registers are enabled, it changes based on enabled regsiters quantity)
Adress of 2nd Meter Data:Hex: 0x01 00
Decimal: 256
Quantity: 96 (only available if 48 registers are enabled, it changes based on enabled regsiters quantity)
Adress of 3th Meter Data:Hex: 0x02 00
Decimal: 512
Quantity: 96 (only available if 48 registers are enabled, it changes based on enabled regsiters quantity)
.....
Adress of 20th Meter Data:Hex: 0x13 00
Decimal: 4864
Quantity: 96 (only available if 48 registers are enabled, it changes based on enabled regsiters quantity)
MQTT DETAILSMQTT Publisher can be enabled and can be used in parallel with Modbus conversion (or stand alone)
MQTT ConnectionBroker IP and Port can be entered
Client ID , User name and Password can be set
Publish Topic and Subscribe Topic can be defined from web interface
Data Send IntervalUser can send Data send interval in seconds
Default is 60 seconds and LKM will send meter data to MQTT server in that interval
NTP ServerNTP server time will be added to each MQTT message
Data FormatThere are 2 predefined formats
OBIS Values As Objects: Sends OBIS values and then mapped values in ASCII readable fromat
OBIS Values as Modbus Frame: Send just like the response of Modbus query as hex data (smaller data size)