CMi416
0 User’s Manual English
CMi416
0 User’s Manual English
page | 14 (28)
[2020-10]
V1.3
Message format JSON is encoded on 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 4.
Figure 4: CMi4160 M-Bus message structure
Field
Size
Description
Message
format
identifier
1 byte
0x1E = Standard
0x1F = Compact
0x20 = JSON
0x21 = Scheduled
– Daily redundant
0x22 = Scheduled - Extended
0x23 = Combined heat/cooling
Table 4: CMi4160 message formats
6.7.2 Structure and payload
In this section, a detailed description of the structure and payload for each message format is presented.
Standard
Figure 5 illustrates the structure of message format
Standard
. For a detailed description of the payload,
see Table 5.
Figure 5: Structure, message format Standard
DIB
Field
Size
Data type
Description
0
Message
format
identifier
1 byte
-
0x1E (Standard)
1
Energy
6-7 bytes INT32
Energy consumption (Wh, J, Cal)
