CMi6160
User’s Manual English
CMi6160
User’s Manual English
page | 23 (38)
[2022-10]
v1.4
Field
Description
Date and Time
(see Note 1)
6
INT32
Date and Time (Type F),
e.g. 046Dxxxxxxxx
M-Bus Format F for Date & Time
Meter ID
(see Note 1)
10
INT64
(Enhanced) Identification
e.g. 0779xxxxxxxxxxxxxxxx
Enhanced Meter Address for Diehl Sharky
Energy
6--7
INT32
Energy consumption (Wh, J)
e.g. 0406xxxxxxxx = xxxxxxxx
* 0.001 MWh (kWh)
Tariff 1 Energy
6-7?
INT32
Tariff register 1 or cooling energy in combined meters
Tariff 2 Energy
6-7?
INT32
Tariff register 2 or heat energy in combined meters
Volume
6
INT32
Volume (m3)
e.g. 0413xxxxxxxx = xxxxxxxx * 0.001 m3
Power
4
INT16
Power (W)
e.g. 022Bxxxxxx = xxxxxx * 0.001 kW (W)
Flow
4
INT16
Flow (m3/h)
e.g. 023Bxxxxxx = xxxxxx * 0.001 m3/h
Fw temp
4
INT16
Forward temperature (°C)
e.g. 025Axxxx = xxxx * 0.1 °C
Rt temp
4
INT16
Return temperature (°C)
e.g. 025Exxxx = xxxx * 0.1
°C
Alarm codes
4
INT8
Alarm codes
e.g. 01FD17xx
Error Codes for Diehl Sharky 775
Table 7. Meter register, tariff message
7.4.2 Message encoding
7.4.2.1 M-Bus
In message format M-Bus, data will be M-Bus encoded. Data will be divided into Data Information Blocks
(DIB) that include Data information field (DIF code), Value information field (VIF code) and a data field
(DATA) where the actual payload is stored (illustrated in )
Figure 7: DIB structure
7.4.2.2 JSON
The payload of message format JSON consists of one object with a list of key
– value pairs. The names
of each value type and unit is presented in . The values are encoded as numbers or strings and the units
are encoded as strings.
Field
JSON key
Meter ID
ID
Meter date / time
TS
Energy
E
