Table of Contents
Advertisement
6.6
Message formats
The LoRa Module has several different message formats. Each one will be described in detail in this section.
6.6.1
Message structure
Message formats Standard, Compact, Scheduled – Daily redundant, Scheduled Extended, Combined heat/cooling
and Sensus are encoded in M-Bus format (M-Bus standard EN 13757-3:2013). Message format JSON is encoded in
JSON format.
All messages begin with one byte specifying the message format used. All M-Bus encoded messages begin with
one byte specifying the message format used. Then follows a sequence of data information blocks (DIBs), each one
containing a data information field (DIF), a value information field (VIF) and a data field (DATA). The structure of the
telegram is illustrated in Figure 5.
For message type JSON, the data is presented as plain text.
Field
Size
Message format
1 byte
* Sensus telegram 2 cannot be selected as a telegram type. It is the ID of the second telegram when using
message format Sensus.
6.6.2
Structure and payload
In this section, a detailed description of each message format payload is provided. All numbers in the payload are
given in hexadecimal unless otherwise stated.
DIB
Field
0
Message
format
1
Energy
Description
0x24 = Standard 0x25 = Compact 0x26 = JSON
0x27 = Scheduled – daily redundant
0x28 = Scheduled - Extended
0x29 = Combined heat/cooling
0x2C = Sensus telegram 1
0x2D = Sensus telegram 2*
Size
Data type
1 byte
-
6-7 bytes
INT32
Figure 5: LoRa Module M-Bus message structure
Description
0x24 (= Standard)
Energy consumption (Wh, J, Cal, MBTU)
0406xxxxxxxx = MWh, 3 decimals = kWh
040Exxxxxxxx = GJ, 3 decimals
04FB0Dxxxxxxxx = Gcal, 3 decimals
04863Dxxxxxxxx = MMBTU, 3 decimals
Table 7: LoRa Module Message formats
12
Advertisement
Table of Contents
