Configuration options
Table 313. All configuration options
|
Field name (Abbr.) |
Description |
Default value |
Locked device & correct PAK or open device |
Locked device & no PAK |
Downlink |
|---|---|---|---|---|---|
|
Meter ID |
Meter identification number of the meter. Not configurable. |
N/A |
Readable |
Readable |
N/A |
|
Power mode |
Used to activate/deactivate the module. |
Passive |
Readable / Writeable |
Readable |
N/A |
|
Message format |
The message format determines the structure and payload of the telegram sent from the module. |
0x1E (Standard) |
Readable / Writeable |
Readable |
Writeable |
|
EcoMode |
When activated, 11+1 years of battery-life is guaranteed by adapting the transmit interval of the module to current signal conditions. |
On |
Readable / Writeable |
Readable |
Writeable |
|
Transmit interval |
Sets the number of minutes between each transmission from the module. |
60 min |
Readable / Writeable |
Readable |
Writeable |
|
Date & Time |
Date and time set for the meter. |
N/A |
Readable |
Readable |
N/A |
|
Set Time Relative |
Adjusts the time of the meter relative to the current time. |
N/A |
N/A |
N/A |
Writeable |
|
Set absolute time |
Sets the time of the meter. When synchronizing the time via the Elvaco OTC App, the date, time and UTC offset settings of the phone will be applied to the meter. |
N/A |
Writeable |
N/A |
N/A |
|
Set UTC offset |
Sets the UTC offset of the meter. |
N/A |
Readable / Writeable |
Readable |
Writeable |
|
Configuration Lock |
Locks the module to prevent unauthorized access. |
Open |
Readable / Writeable |
Readable |
Writeable |
|
LoRaWAN® settings |
|||||
|
Device EUI |
Unique module identification number. Not configurable. |
Device-unique 64-bit number |
Readable |
Readable |
N/A |
|
Activation type |
Sets the way the device joins the LoRaWAN® network. |
OTAA |
Readable / Writeable |
Readable |
N/A |
|
Network join |
Displays whether the module has joined the LoRaWAN® network or not. |
N/A |
Readable |
Readable |
N/A |
|
Join EUI |
Application ID that determines where data ends up. |
0x 94 19 3A 03 03 00 00 01 (internal antenna version) 0x 94 19 3A 03 04 00 00 01 (external antenna version) |
Readable / Writeable |
Readable |
N/A |
|
Device address |
32-bit address used by the module to identify itself on the LoRaWAN® network. |
N/A |
Readable / Writeable |
N/A |
N/A |
|
Current data rate |
The current data rate used for the module. |
N/A |
Readable |
Readable |
N/A |
Table 314. Downlink commands
|
Field name |
TLV |
Number of bytes in configuration |
Configuration |
Example |
|---|---|---|---|---|
|
Configuration lock |
0x05 |
0x01 |
0x00 = Locked 0x01 = Open |
0x00050101 (Opens the configuration lock) |
|
Transmit interval |
0x06 |
0x02 |
0xNumber of minutes between transmission (lsByte -> msByte) |
0x0006021E00 (Sets the Tx interval to 30 minutes) |
|
Message format |
0x07 |
0x01 |
0x1E = Message format Standard 0x1F = Message format Compact 0x20 = Message format JSON 0x21 = Message format Scheduled-daily redundant 0x22 = Message format Scheduled - Extended 0x23 = Message format Combined heat/cooling |
0x0007011F (Sets the message format to compact) |
|
EcoMode |
0x0F |
0x01 |
0x00 = Disable EcoMode 0x01 = Enable EcoMode |
0x000F0100 (Disables EcoMode) |
|
Set Time Relative |
0x13 |
0x04 |
0xNumber of seconds* (lsByte -> msByte) *Negative numbers supported. |
0x0013043C000000 (Adds 60 seconds to the current time) 0x0013043C000080 (Subtracts 60 seconds from the current time) |
|
UTC offset |
0x17 |
0x02 |
0xNumber of minutes* (lsByte -> msByte) *Negative numbers supported. |
0x17023C00 (Sets the UTC offset to +60 minutes) 0x17023C80 (Sets the UTC offset to -60 minutes) |
|
Reboot |
0x22 |
0x02 |
0x759E is used to reboot device (note endianness, LSB first). |
0x0022029E75 (Reboots the device) |
To allow a flexible output from the device, CMi4160 has several message formats. Some of them are scheduled, meaning the meter is read on top of every hour, and a clock message is sent once per day, see Scheduled message formats for details.
Table 315. CMi4160 Message formats
|
Message format name |
Message ID |
Scheduled |
Introduced in FW |
|---|---|---|---|
|
|
No |
1.0.1 |
|
|
|
No |
1.0.1 |
|
|
|
No |
1.0.1 |
|
|
|
Yes |
1.0.1 |
|
|
|
Yes |
1.0.1 |
|
|
|
Yes |
1.0.1 |
|
|
|
Yes |
1.0.5 |
|
|
|
No |
1.0.8 |
Note
Message formats with more than one message ID, such as Scheduled Extended+, have been divided into several telegrams due to size limitations.
Table 316. Payload, message format standard [0x1E]
|
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) 0403xxxxxxxx = xxxxxxxx Wh 0404xxxxxxxx = xxxxxxxx * 10 Wh 0405xxxxxxxx = xxxxxxxx * 100 Wh 0406xxxxxxxx = xxxxxxxx kWh 0407xxxxxxxx = xxxxxxxx * 10 kWh 040Exxxxxxxx = xxxxxxxx MJ 040Fxxxxxxxx = xxxxxxxx * 10 MJ 04FB0Dxxxxxxxx = xxxxxxxx MCal 04FB0Exxxxxxxx = xxxxxxxx * 10 MCal 04FB0Fxxxxxxxx = xxxxxxxx * 100 MCal |
|
2 |
Volume |
6 bytes |
INT32 |
Volume (m3) 0413xxxxxxxx = xxxxxxxx * 0.001 m3 0414xxxxxxxx = xxxxxxxx * 0.01 m3 0415xxxxxxxx = xxxxxxxx * 0.1 m3 |
|
3 |
Power |
4 bytes |
INT16 |
Power (kW) 022Bxxxx = xxxx W 022Cxxxx = xxxx * 10 W 022Dxxxx = xxxx * 100 W 022Exxxx = xxxx kW 022Fxxxx = xxxx * 10 kW |
|
4 |
Flow |
4 bytes |
INT16 |
Flow (m3/h) 023Bxxxx = xxxx * 0.001 m3/h 023Cxxxx = xxxx * 0.01 m3/h 023Dxxxx = xxxx * 0.1 m3/h 023Fxxxx = xxxx * 10 m3/h |
|
5 |
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 |
|
6 |
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 |
|
7 |
Meter address |
10 bytes |
According to M-Bus EN13757-3 identification field |
Meter address Byte 0-1 = DIF/VIF code Byte 2-5 = Meter ID (BCD8, lsByte -> msByte) Byte 6-7 = Meter manufacturer (lsByte -> msByte) Byte 8 = Meter version Byte 9 = Device type |
|
8 |
Error flags |
4 bytes |
INT8 |
Error and warning flags 01FD17xx For further information about Alarm codes please refer to the meter’s manual |
Table 317. Payload, message format Compact [0x1F]
|
DIB |
Field |
Size |
Data type |
Description |
|---|---|---|---|---|
|
0 |
Message format identifier |
1 byte |
- |
0x1F (Compact) |
|
1 |
Energy |
6-7 bytes |
INT32 |
Energy consumption (Wh, J, Cal) 0403xxxxxxxx = xxxxxxxx Wh 0404xxxxxxxx = xxxxxxxx * 10 Wh 0405xxxxxxxx = xxxxxxxx * 100 Wh 0406xxxxxxxx = xxxxxxxx kWh 0407xxxxxxxx = xxxxxxxx * 10 kWh 040Exxxxxxxx = xxxxxxxx MJ 040Fxxxxxxxx = xxxxxxxx * 10 MJ 04FB0Dxxxxxxxx = xxxxxxxx MCal 04FB0Exxxxxxxx = xxxxxxxx * 10 MCal 04FB0Fxxxxxxxx = xxxxxxxx * 100 MCal |
|
2 |
Meter address |
10 bytes |
According to M-Bus EN13757-3 identification field |
Meter address Byte 0-1 = DIF/VIF code Byte 2-5 = Meter ID (BCD8, lsByte -> msByte) Byte 6-7 = Meter manufacturer (lsByte -> msByte) Byte 8 = Meter version Byte 9 = Device type |
|
3 |
Error flags |
4 bytes |
INT8 |
Error and warning flags 01FD17xx For further information about Error flags please refer to the meter’s manual |
For message format JSON, the data is presented in a plain text format.
Table 318. Fields, message format JSON [0x20]
|
Field |
Description |
|---|---|
|
Message format identifier |
20 (Message format JSON) |
|
Energy |
Energy consumption |
|
Unit |
Unit of energy consumption (Wh, kWh, MWh, GWh, J, kJ, MJ, GJ, Cal, kCal, MCal or GCal) |
|
Meter ID |
Identification number of the meter in which the module is mounted. |
Below shows an example of a telegram sent using the JSON message format.
{"E":12345678,"U":"kWh","ID":87654321}
The Maximum flow message format includes the maximum flow from the previous logging period, as well at what date it took place. See the details of the content in the table below.
Table 319. Payload, message format Maximum flow [0x5D]
|
Field |
Size (bytes) |
Data type |
Description |
|---|---|---|---|
|
Message ID |
1 |
UINT8 |
Always 0x5D |
|
Meter ID |
10 |
BCD8 |
Byte 0-1: DIF/VIF code Byte 2-5: Meter ID (BCD8, lsByte -> msByte) Byte 6-7: Meter manufacturer (lsByte -> msByte) Byte 8: Meter version Byte 9: Device type Example: 077974031961A5114004 |
|
Energy |
6-7 |
INT32 |
Instanenous energy Example: |
|
Max. flow rate in the last logging period |
5 |
INT16 |
Maximum flow last entry in the meter’s history log. Example: Storage nr 3 is used (DIF=0x44, DIFE=0x01). Function field of DIF set to |
|
Date of max flow |
5 |
INT32 |
Date of maximum flow taken from the meter’s history log. Using M-Bus Date format (Type G). Example: Storage nr 3 is used (DIF=0xC2, DIFE=0x01) This is the date for the maximum flow, typically different from the due date timestamp. Note 1: This date is not compensated to be sent in UTC since it is only a date. It is the date stored in the meter, which may be local time, not UTC. Note 2: Since M-Bus format G is used only date is sent. If meter’s logger is set to shorter intervals (hours, daily) the minute/hour of the max flow will not be sent. Note 3: Function field of DIF not indicating max value as for the flow above. |
|
Energy at last logging period |
7-8 |
INT32 |
Energy value taken from history log in the meter. Example: 840106xxxxxxxx. Monthly energy value, either heat or cooling. Storage nr 2 is used for historic values. |
|
Rt temp |
4 |
INT16 |
Instantaneous return temperature. Example: |
|
Error flags |
7 |
INT32 |
Instantaneous error flags from meter. Example: |
For scheduled message formats, such as Scheduled Daily Redundant and Pulse Extended, two types of messages will be transmitted from the module - a clock message and a data message. Scheduled message formats will read the meter on top of the hour, making received telegrams more predictable. The difference between a clock message and a data message is described in the following table.
Table 320. Clock message and data message
|
Message |
Time interval |
Description |
|---|---|---|
|
Clock message |
Once per day |
The clock message presents the current time of the meter. It can be used to verify that the clock is correct and has not drifted more than accepted. |
|
Data message |
Determined by Transmit interval parameter |
The actual meter data collected from the meter. |
The following table contains a detailed description of the payload of the clock message.
Table 321. Payload, clock message
|
Field |
Size |
Data type |
Description |
|---|---|---|---|
|
Message format identifier |
1 byte |
- |
0xFA (=Clock message) |
|
Date/Time |
6 bytes |
32 bit binary integer M-Bus type F |
046Dxxxxxx = Valid date/time message 346Dxxxxxx = Invalid date/time message |
The clock message will be transmitted once every day and the data message at least (regulated by transmit interval parameter or EcoMode) once every day. The transmit interval can only be set to the values listed in Table 322, “Transmit interval options ”.
Although the meter readout will occur on top-of-the-hour, the data message will not necessarily be transmitted at that exact time. The LoRaWAN® transmission will occur after a random delay of 0-15 minutes to decrease the risk of collisions. The readout for the clock message occurs at a random hour (00:00-23:00) at a random minute in the 35-45 minute interval and will be transmitted immediately after the readout.
Note
When using scheduled message formats, the transmit interval cannot be set to higher than 1440 (24 hours).
Table 322. Transmit interval options
|
Parameter |
Values |
Unit |
|---|---|---|
|
Transmit interval |
60, 120, 180, 240, 360, 480, 720, 1440 |
Minutes |
The data message of Scheduled - Daily Redundant contains an accumulated daily energy field, which is updated at 24:00 each day. In other words, depending on transmit interval settings and data rate, the field will be included in between 1-24 telegrams per day. This will increase the probability of the value being received. For example, if the transmit interval is set to “2”, the accumulated energy read at 24:00 will be transmitted 12 times during the 24 next coming hours (every 2nd hour).
The following table contains a detailed description of the payload of message format Scheduled - Daily Redundant.
Table 323. Payload, message format Scheduled – Daily redundant [0x21]
|
DIB |
Field |
Size |
Data type |
Description |
|---|---|---|---|---|
|
0 |
Message format identifier |
1 byte |
- |
0x21 (Scheduled-daily redundant) |
|
1 |
Energy |
6-7 bytes |
INT32 |
Energy consumption (Wh, J, Cal) 0403xxxxxxxx = xxxxxxxx Wh 0404xxxxxxxx = xxxxxxxx * 10 Wh 0405xxxxxxxx = xxxxxxxx * 100 Wh 0406xxxxxxxx = xxxxxxxx kWh 0407xxxxxxxx = xxxxxxxx * 10 kWh 040Exxxxxxxx = xxxxxxxx MJ 040Fxxxxxxxx = xxxxxxxx * 10 MJ 04FB0Dxxxxxxxx = xxxxxxxx MCal 04FB0Exxxxxxxx = xxxxxxxx * 10 MCal 04FB0Fxxxxxxxx = xxxxxxxx * 100 MCal |
|
2 |
Volume |
6 bytes |
INT32 |
Volume (m3) 0413xxxxxxxx = xxxxxxxx * 0.001 m3 0414xxxxxxxx = xxxxxxxx * 0.01 m3 0415xxxxxxxx = xxxxxxxx * 0.1 m3 0416xxxxxxxx = xxxxxxxx m3 0417xxxxxxxx = xxxxxxxx * 10 m3 |
|
3 |
Meter address |
10 bytes |
According to M-Bus EN13757-3 identification field |
Meter address Byte 0-1 = DIF/VIF code Byte 2-5 = Meter ID, BCD8 Byte 6-7 = Meter manufacturer Byte 8 = Meter version Byte 9 = Device type |
|
4 |
Error flags |
4 bytes |
INT8 |
Error and warning flags 01FD17xx For further information about Error flags please refer to the meter’s manual |
|
5 |
Meter date/time |
6 bytes |
INT32 |
Meter date and time (YY-MM-DD HH:MM) 046Dxxxxxxxx Bit 31-28 = Year-high* Bit 27-24 = Month Bit 23-21 = Year-low* Bit 20-16 = Day Bit 15 = Summertime flag** 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 |
|
6 |
Accumulated energy at 24:00 |
6-7 bytes |
INT32 |
Energy consumption (Wh, J, Cal) 4403xxxxxxxx = xxxxxxxx Wh 4404xxxxxxxx = xxxxxxxx *10 Wh 4405xxxxxxxx = xxxxxxxx *100 Wh 4406xxxxxxxx = xxxxxxxx kWh 4407xxxxxxxx = xxxxxxxx * 10 kWh 440Exxxxxxxx = xxxxxxxx MJ 440Fxxxxxxxx = xxxxxxxx * 10 MJ 44FB0Dxxxxxxxx = xxxxxxxx MCal 44FB0Exxxxxxxx = xxxxxxxx * 10 MCal 44FB0Fxxxxxxxx = xxxxxxxx * 100 MCal Note: Before a midnight reading has been performed the Function field of the DIF is set to “value during error state” to indicate that the value is not valid. |
The data message of Scheduled - Extended contains all the data fields from message format Standard. In addition to these, it also includes the meter date/time to transmit messages on the full hour. As for all Scheduled message formats, the transmit interval can only be set to the values included in Table 238, “Transmit interval options ”.
The following table contains a detailed description of the payload of message format Scheduled - Extended.
Table 324. Payload, message format Scheduled - Extended [0x22]
|
DIB |
Field |
Size |
Data type |
Description |
|---|---|---|---|---|
|
0 |
Message format identifier |
1 byte |
- |
0x22 (Scheduled-Extended) |
|
1 |
Energy |
6-7 bytes |
INT32 |
Energy consumption (Wh, J, Cal) 0403xxxxxxxx = xxxxxxxx Wh 0404xxxxxxxx = xxxxxxxx * 10 Wh 0405xxxxxxxx = xxxxxxxx * 100 Wh 0406xxxxxxxx = xxxxxxxx kWh 0407xxxxxxxx = xxxxxxxx * 10 kWh 040Exxxxxxxx = xxxxxxxx MJ 040Fxxxxxxxx = xxxxxxxx * 10 MJ 04FB0Dxxxxxxxx = xxxxxxxx MCal 04FB0Exxxxxxxx = xxxxxxxx * 10 MCal 04FB0Fxxxxxxxx = xxxxxxxx * 100 MCal |
|
2 |
Volume |
6 bytes |
INT32 |
Volume (m3) 0413xxxxxxxx = xxxxxxxx * 0.001 m3 0414xxxxxxxx = xxxxxxxx * 0.01 m3 0415xxxxxxxx = xxxxxxxx * 0.1 m3 0416xxxxxxxx = xxxxxxxx m3 0417xxxxxxxx = xxxxxxxx * 10 m3 |
|
3 |
Power / Flow / Fw temp / Rt temp |
12 bytes |
INT64 |
Byte 0-2 = DIF/VIF codes, 0x07FFA0 Byte 3 = Scaling of Power/Flow -Bit 6.4 (n), 10n-3 W, n = 0..7 -Bit 2..0 (m), 10m-6 m3 /h, m = 0..7 Byte 4-5 = Fw temp (lsByte -> msByte), °C, 2 decimals Byte 6-7 = Rt temp (lsByte -> msByte), °C, 2 decimals Byte 8-9 = Flow (lsByte -> msByte), 10m-6 m3/h Byte 10-11 = Power (lsByte -> msByte), 10n-3 W |
|
4 |
Meter ID / Error flags |
13 bytes |
INT72 |
Byte 0-3 = DIF/VIF codes, 0x0DFF21E9 Byte 4 = Error flags Byte 5-8 = Meter ID (BCD8, lsByte -> msByte) Byte 9-10 = Meter manufacturer (lsByte -> msByte) Byte 11 = Meter version Byte 12 = Device type |
|
5 |
Meter date/time |
6 bytes |
INT32 |
Meter date and time (YY-MM-DD HH:MM) 046Dxxxxxxxx Bit 31-28 = Year-high* Bit 27-24 = Month Bit 23-21 = Year-low* Bit 20-16 = Day Bit 15 = Summertime flag** 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 **0 = standard time, 1= daylight-saving time **0 = standard time, 1= daylight-saving time |
Message format Combined heat/cooling is developed to be used in meters that measures both heating and cooling energy.
The following table contains a detailed description of the payload of message format Combined heat/cooling.
Table 325. Payload, message format Combined heat/cooling [0x23]
|
DIB |
Field |
Size |
Data type |
Description |
|---|---|---|---|---|
|
0 |
Message format identifier |
1 byte |
- |
0x23 (Combined heat/cooling) |
|
1 |
Heat energy |
6-7 bytes |
INT32 |
Energy consumption (Wh, J, Cal) 0403xxxxxxxx = xxxxxxxx Wh 0404xxxxxxxx = xxxxxxxx * 10 Wh 0405xxxxxxxx = xxxxxxxx * 100 Wh 0406xxxxxxxx = xxxxxxxx kWh 0407xxxxxxxx = xxxxxxxx * 10 kWh 040Exxxxxxxx = xxxxxxxx MJ 040Fxxxxxxxx = xxxxxxxx * 10 MJ 04FB0Dxxxxxxxx = xxxxxxxx MCal 04FB0Exxxxxxxx = xxxxxxxx * 10 MCal 04FB0Fxxxxxxxx = xxxxxxxx * 100 MCal |
|
2 |
Cooling energy |
8-9 bytes |
INT32 |
Energy consumption (Wh, J, Cal) 0483FF02xxxxxxxx = xxxxxxxx Wh 0484FF02xxxxxxxx = xxxxxxxx * 10 Wh 0485FF02xxxxxxxx = xxxxxxxx * 100 Wh 0486FF02xxxxxxxx = xxxxxxxx kWh 0487FF02xxxxxxxx = xxxxxxxx * 10 kWh 048EFF02xxxxxxxx = xxxxxxxx MJ 048FFF02xxxxxxxx = xxxxxxxx * 10 MJ 04FB8DFF02xxxxxxxx = xxxxxxxx MCal 04FB8EFF02xxxxxxxx = xxxxxxxx * 10 MCal 04FB8FFF02xxxxxxxx = xxxxxxxx * 100 MCal |
|
3 |
Volume |
6 bytes |
INT32 |
Volume (m3) 0413xxxxxxxx = xxxxxxxx * 0.001 m3 0414xxxxxxxx = xxxxxxxx * 0.01 m3 0415xxxxxxxx = xxxxxxxx * 0.1 m3 0416xxxxxxxx = xxxxxxxx m3 0417xxxxxxxx = xxxxxxxx * 10 m3 |
|
4 |
Fw temp |
4 bytes |
INT16 |
Forward temperature (°C) 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) 025Exxxx = °C, 1 decimal |
|
6 |
Meter address |
10 bytes |
According to M-Bus EN13757-3 identification field |
Meter address Byte 0-1 = DIF/VIF code Byte 2-5 = Meter ID, BCD8 Byte 6-7 = Meter manufacturer Byte 8 = Meter version Byte 9 = Device type |
|
7 |
Error flags |
4 bytes |
INT8 |
Error and warning flags 01FD17xx For further information about Error flags please refer to the meter’s manual |
The data message of message format Scheduled mode-extended + contains three tariffs and all the meter data included in the Standard telegram. In addition to these, a timestamp from the meter (meter date/time) is included in each telegram.
The following tables contains a detailed description of the payload of message format Scheduled - Extended+.
Table 326. Payload Scheduled Extended, telegram 1 [0x3D]
|
DIB |
Field |
Size |
Data type |
Description |
|---|---|---|---|---|
|
0 |
Message format identifier |
1 byte |
- |
0x3D (Scheduled Extended+ telegram 1) |
|
1 |
Energy |
7 bytes |
INT32 |
Energy consumption (Wh, J, Cal) 0403xxxxxxxx = xxxxxxxx Wh 0404xxxxxxxx = xxxxxxxx * 10 Wh 0405xxxxxxxx = xxxxxxxx * 100 Wh 0406xxxxxxxx = xxxxxxxx kWh 0407xxxxxxxx = xxxxxxxx * 10 kWh 040Exxxxxxxx = xxxxxxxx MJ 040Fxxxxxxxx = xxxxxxxx * 10 MJ 04FB0Dxxxxxxxx = xxxxxxxx MCal 04FB0Exxxxxxxx = xxxxxxxx * 10 MCal 04FB0Fxxxxxxxx = xxxxxxxx * 100 MCal |
|
2 |
Energy Tariff 1 |
8 bytes |
INT32 |
Energy Tariff 1 Same encoding as heat energy, e.g., 841003xxxxxxxx = xxxxxxxx Wh |
|
3 |
Energy Tariff 2 |
8 bytes |
INT32 |
Energy Tariff 2 Same encoding as heat energy, e.g., 842003xxxxxxxx = xxxxxxxx Wh |
|
4 |
Meter address |
10 bytes |
According to M-Bus EN13757-3 identification field |
Meter address Byte 0-1 = DIF/VIF code Byte 2-5 = Meter ID, BCD8 Byte 6-7 = Meter manufacturer Byte 8 = Meter version Byte 9 = Device type |
|
5 |
Meter date/time |
6 bytes |
INT32 |
Meter date and time (YY-MM-DD HH:MM) 046Dxxxxxxxx Bit 31-28 = Year-high* Bit 27-24 = Month Bit 23-21 = Year-low* Bit 20-16 = Day Bit 15 = Summertime flag** 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 **0 = standard time, 1= daylight-saving time ***0 = timestamp is valid, 1 = timestamp is not valid |
Table 327. Payload Scheduled Extended, telegram 2 [0x3E]
|
DIB |
Field |
Size |
Data type |
Description |
|---|---|---|---|---|
|
0 |
Message format identifier |
1 byte |
- |
0x3E (Scheduled Extended+ telegram 2) |
|
1 |
Volume |
6 bytes |
INT32 |
Volume (m3) 0413xxxxxxxx = xxxxxxxx * 0.001 m3 0414xxxxxxxx = xxxxxxxx * 0.01 m3 0415xxxxxxxx = xxxxxxxx * 0.1 m3 0416xxxxxxxx = xxxxxxxx m3 0417xxxxxxxx = xxxxxxxx * 10 m3 |
|
2 |
Power |
4 bytes |
INT16 |
Power (kW) 022Bxxxx = xxxx W 022Cxxxx = xxxx * 10 W 022Dxxxx = xxxx * 100 W 022Exxxx = xxxx kW 022Fxxxx = xxxx * 10 kW |
|
3 |
Flow |
4 bytes |
INT16 |
Flow (m3/h) 023Bxxxx = xxxx * 0.001 m3/h 023Cxxxx = xxxx * 0.01 m3/h 023Dxxxx = xxxx * 0.1 m3/h 023Exxxx = xxxx m3/h 023Fxxxx = xxxx * 10 m3/h |
|
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 address |
10 bytes |
According to M-Bus EN13757-3 identification field |
Meter address Byte 0-1 = DIF/VIF code Byte 2-5 = Meter ID, BCD8 Byte 6-7 = Meter manufacturer Byte 8 = Meter version Byte 9 = Device type |
|
7 |
Meter date/time |
6 bytes |
INT32 |
Meter date and time (YY-MM-DD HH:MM) 046Dxxxxxxxx Bit 31-28 = Year-high* Bit 27-24 = Month Bit 23-21 = Year-low* Bit 20-16 = Day Bit 15 = Summertime flag** 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 **0 = standard time, 1= daylight-saving time ***0 = timestamp is valid, 1 = timestamp is not valid |
|
8 |
Error flags |
4 bytes |
INT8 |
Error and warning flags 01FD17xx For further information about Error flags please refer to the meter’s manual |
The error codes transported from an MCM is the status byte of the M-Bus header. Bits 71:64 of M-Bus header.
Meaning of Error Codes
The following information is from the documentation received from Diehl Metering. It has only been enhanced by formatting, content is as-is straight from the document. For latest error description please use the latest documentation available from Diehl Metering. Table 328, “Diehl error codes” corresponds to Table 7 of EN 13757-3:2013 for M-Bus.
Table 328. Diehl error codes
|
Bit |
Description |
Usage |
|---|---|---|
|
0 |
Reserved |
- |
|
1 |
Any application error |
- |
|
2 |
Power low |
E-8, E-9 |
|
3 |
Permanent error |
C-1, E-4 |
|
4 |
Temporary error |
E-1, E-3, E-6, E-7, leak error |
|
5 |
Manufacturer specific |
|
|
6 |
manufacturer specific |
|
|
7 |
manufacturer specific |
Table 329, “Error code positioning” explains the position of error codes from the User’s Manual of the meter.
Table 329. Error code positioning
|
Error |
C-1 |
E-8 |
E-4 |
E-1 |
E-7 |
E-9 |
E-3 |
E-6 |
Leak error |
E-5 |
|---|---|---|---|---|---|---|---|---|---|---|
|
M-bus status Byte |
0x08 |
0x04 |
0x28 |
0x50 |
0x70 |
0x84 |
0xB0 |
0xD0 |
0xF0 |
0x10 |
|
Prio |
Highest |
Lowest |
The table below lists existing meter error codes that, if present, are displayed on the meter along with their corresponding explanations
Table 330. Meter error interpretation
|
Error meter display |
Error description |
|---|---|
|
C-1 |
Basic parameter error in flash or RAM |
|
E-8 |
No primary voltage (only if mains unit used) Powered by back-up battery |
|
E-4 |
Hardware error in ultrasonic measurement Short-circuit in ultrasonic transducer Ultrasonic transducer defective |
|
E-1 |
Temperature measurement error Sensor break Sensor short-circuit Temperature range exceeded [-9.9 °C … 190 °C] |
|
E-7 |
No meaningful ultrasonic receive signal Air in the measuring path |
|
E-9 |
Warning: battery nearly exhausted |
|
E-3** |
Temperature sensors reversed in hot and cold lines |
|
E-6** |
Wrong direction of flow Flow sensor incorrectly installed |
|
E-B* |
Leakage: leakage detected in energy meter |
|
E-C* |
Leakage: leakage pulse input 1 |
|
E-D* |
Leakage: leakage pulse input 2 |
|
E-A* |
Leakage: pipe break detected |
|
E-5 |
Reading too frequently M-Bus communication not possible for short time |
* Optional
** application-dependent
Comments (0 comments)