Elvaco CMi4130, User Manual

Page: 20 / 25

CMi413
0 User’s Manual English
CMi413
0 User’s Manual English
page | 20 (25) [2020-06]
V1.1
0413xxxxxxxx = xxxxxxxx * 0.001 m
3
0414xxxxxxxx = xxxxxxxx * 0.01 m
3
0415xxxxxxxx = xxxxxxxx * 0.1 m
3
0416xxxxxxxx = xxxxxxxx m
3
0417xxxxxxxx = xxxxxxxx * 10 m
3
4 Fw temp 4 bytes INT16
Forward temperature (°C)
0258xxxx = xxxx * 0.001 °C
0259xxxx = xxxx * 0.01 °C
025Axxxx = xxxx * 0.1 °C
025Bxxxx = xxxx °C
5 Rt temp 4 bytes INT16
Return temperature (°C)
025Cxxxx = xxxx * 0.001 °C
025Dxxxx = xxxx * 0.01 °C
025Exxxx = xxxx * 0.1 °C
025Fxxxx = xxxx °C
6 Meter ID 6 bytes According to M-Bus
EN13757-3
identification field Meter ID
0C78xxxxxxxx
7 Alarm
codes 5 bytes INT16 Error and warning flags
02FD17xxxx
For further information about Alarm
codes
please refer to the meter’s manual
Table 13: Payload, message format Combined heat/cooling
6.7.3 Meter communication error message
The payloads using M-Bus encoded data uses the Function field of the DIF to indicate errors. In this case
it is set to “value during error state” (M-Bus standard EN 13757-3:2013) and the value sent should not be
used. A typical case for this is when the module is unable to communicate with the meter and retrieve
meter values, in which case all the fields in the payload have the DIF indicating “value during error state”.
In case of erroneous data or if the module is unable to communicate with meter, bit 4-5 of the bit of the
DIF code (first byte of each index field) will be set to 11b. For example, a DIF code of 0x02 will be set to
0x32 in case of error. (This applies to all message format except JSON.) For message format JSON, the
actual value will be replaced with “null” in case of error state. If no meter communication is possible at all,
all fields have this error indication set.
6.8 Downlink
CMi4130 supports configuration via downlink, i.e. sending commands to an end-device via the LoRaWAN
network.
Note that this feature should only be used sparingly due to bandwidth consideration.
Communication via downlink is sent on port 2 and can only be made in a short window after an uplink
transmission from module to server. Therefore, time-critical communication should not be performed over
downlink.
Downlink commands are structured according to the following format:
“0x00” "TLV
" " Number of bytes in
configuration" "Configuration". For a complete description of all available downlink commands, see Table
14 .
Field name TLV Number of
bytes in
configuration Configuration Example