Elvaco CMi4110, User Manual

Page: 21 / 27

CMi4110 User’s Manual English v1.3
CMi4110 User’s Manual English v1.3
page | 21 (27) [2018-06]
V1.3
7 Meter ID 6 bytes
(including
DIF/VIF) According to M-
Bus EN13757-3
identification field
Meter ID
0C78xxxxxxxx = Meter ID
8 Meter
date/time 6 bytes
(including
DIF/VIF M-Bus Type F
Meter date and time (YY-MM-DD HH:MM)
Mapped to OBIS 9.36
046Dxxxxxxxx
Bit 31-28 = Year-high*
Bit 27-24 = Month
Bit 23-21 = Year-low*
Bit 20-16 = Day
Bit 15 = Summer time flag**
Bit 14-13 = Century
Bit 12-8 = Hour
Bit 7 = Error flag
Bit 6 = Reserved for future use***
Bit 5-0 = Minute
*The year is read by combining the year-high
and year-low field. For example, year-high =
0010 and year-low = 010 => year = 0010010
**0 = standard time, 1= daylight-saving time
***0 = timestamp is valid, 1 = timestamp is
not
valid
9 Error flags 5 bytes
(including
DIF/VIF)
Uint16
M-Bus Type C Error and warning flags
02FD17xxxx
Meter communication error message
When CMi4110 is unable to communicate with UH50/UC50, an error message will be transmitted on the
LoRaWAN network. Table 12 describes that error message for each message type.
Message type Error message
Standard 0E00
Compact 0E00
JSON { }
Scheduled-daily redundant 0E00
Table 12: Meter communication error message
6.7 Downlink
CMi4110 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 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.
Some appropriate use of downlink commands is:
•
Adjusting the meter clock when message type scheduled is used.
•
Adjusting the MaxDTx parameter in order to optimize the performance of CMi4110 on the