Configuration options
Table 271. 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 |
|
EcoMode |
When activated, a minimum battery-life of 6+1 or 10+1 years depending on the configuration) can be achieved by the module. |
10 years |
Readable / Writeable |
Readable |
Writeable |
|
Message format |
The message format determines the meter data included in the telegram from the module. |
0x24 (Standard) |
Readable / Writeable |
Readable |
Writeable |
|
Transmit interval |
Sets the number of minutes between each transmission from the module. |
60 minutes |
Readable / Writeable |
Readable |
Writeable |
|
Date & Time |
Date and time of the meter. |
N/A |
Readable / Writeable |
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 |
Writeable |
N/A |
N/A |
N/A |
|
Configuration Lock |
Locks the module to prevent unauthorized access. |
Open |
Readable / Writeable |
Readable |
Writeable |
|
Pulse input selection |
Select which of the three pulse inputs to include when using the Engelmann message format. One or more can be selected. |
0x00 (None) |
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 |
Writeable |
|
Network join |
Used to display whether the module has joined the LoRaWAN® network |
N/A |
Readable |
Readable |
N/A |
|
Join EUI |
Application identifier that determines where data ends up. |
94193A030C000001 |
Readable / Writeable |
Readable |
Writeable |
|
Device address |
32-bit address used by the device to identify itself on the LoRaWAN® network. |
N/A |
Readable / Writeable |
Readable |
Writeable |
|
Current data rate |
The current data rate used for the module. |
N/A |
Readable |
Readable |
N/A |
Table 272. Downlink commands
|
Field name |
TLV |
Number of bytes in configuration |
Configuration |
Example |
|---|---|---|---|---|
|
Configuration lock |
0x05 |
0x01 |
0x00 = Locked 0x01 = Open |
0x00050101 (Enables 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 |
0x24 = Standard 0x25 = Compact 0x26 = JSON 0x27 = Scheduled-daily redundant 0x28 = Scheduled - Extended 0x29 = Combined heat/cooling 0x2C = Engelmann |
0x0007010XX (Sets the message format to compact) |
|
EcoMode |
0x0F |
0x01 |
0x00 = Disable EcoMode 0x01 = Enable EcoMode, 10 years 0x02 = Enable EcoMode, 6 years |
0x000F0100 (Disables EcoMode) |
|
Set Time Relative |
0x13 |
0x02 |
0xNumber of minutes* (lsByte -> msByte) *Negative numbers supported. |
0x0013020F00 (Adds 15 minutes to the current time) 0x0013020F80 (Subtracts 15 minutes from the current time) |
|
UTC offset |
0x17 |
0x02 |
0xNumber of minutes* (lsByte -> msByte) *Negative numbers supported. |
0x0017023C00 (Sets the UTC offset to +60 minutes) 0x0017023C80 (Sets the UTC offset to -60 minutes) |
|
Reboot |
0x22 |
0x02 |
0x9E75 is used to reboot device |
0x0022029E75 (Reboots the device) |
|
Pulse input selection |
0x1D |
0x01 |
Bit flags for selecting which pulse inputs are to be included in the Engelmann message format. 0 = disabled, 1 = enabled Bit 0: Input 1 Bit 1: Input 2 Bit 2: Input 3 Bits 3-7 are reserved and shall be set to 0. |
0x001D0101 (Only input 1) 0x001D0107 (Input 1, 2 & 3) |
CMi4170 has several different message formats.
Table 273. CMi4170 Message formats
|
Field |
Size |
Description |
|---|---|---|
|
Message format |
1 byte |
0x24 = Standard 0x25 = Compact 0x26 = JSON 0x27 = Scheduled – daily redundant 0x28 = Scheduled - Extended 0x29 = Combined heat/cooling 0x2C = Engelmann telegram 1 0x2D = Engelmann telegram 2* |
*Engelmann telegram 2 cannot be selected as a telegram type. It is the ID of the second telegram when using message format Engelmann.
Table 274. Payload, message format Standard [0x24]
|
DIB |
Field |
Size |
Data type |
Description |
|---|---|---|---|---|
|
0 |
Message format |
1 byte |
- |
0x24 (= Standard) |
|
1 |
Energy |
6-7 bytes |
INT32 |
Energy consumption (Wh, J, Cal) 0400xxxxxxxx = xxxxxxxx,xxx Wh 0401xxxxxxxx = xxxxxxxx,xx Wh 0402xxxxxxxx = xxxxxxxx,x Wh 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 ( m³ ) 0411xxxxxxxx = xxxxxxxx * 0.00001 m³ 0412xxxxxxxx = xxxxxxxx * 0.0001 m³ 0413xxxxxxxx = xxxxxxxx * 0.001 m³ 0414xxxxxxxx = xxxxxxxx * 0.01 m³ 0415xxxxxxxx = xxxxxxxx * 0.1 m³ 0416xxxxxxxx = xxxxxxxx m³ 0417xxxxxxxx = xxxxxxxx * 10 m³ |
|
3 |
Power |
4 bytes |
INT16 |
Power (W) 022Bxxxx = xxxx W 022Cxxxx = xxxx * 10 W 022Dxxxx = xxxx * 100 W 022Exxxx = xxxx kW 022Fxxxx = xxxx * 10 kW |
|
4 |
Flow |
4 bytes |
INT16 |
Flow ( m³/h) 023Bxxxx = xxxx * 0.001 m³/h 023Cxxxx = xxxx * 0.01 m³/h 023Dxxxx = xxxx * 0.1 m³/h 023Exxxx = xxxx m³/h 023Fxxxx = xxxx * 10 m³/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 ID |
6 bytes |
According to M-Bus EN13757-3 identification field |
Meter ID 0C78xxxxxxxx |
|
8 |
Error flags |
4 bytes |
INT8 |
Error and warning flags 01FD17xx |
Table 275. Payload, message format Compact [0x25]
|
DIB |
Field |
Size |
Data type |
Description |
|---|---|---|---|---|
|
0 |
Message format |
1 byte |
- |
0x25 (= Compact) |
|
1 |
Energy |
6-7 bytes |
INT32 |
Energy consumption (Wh, J, Cal) 0400xxxxxxxx = xxxxxxxx,xxx Wh 0401xxxxxxxx = xxxxxxxx,xx Wh 0402xxxxxxxx = xxxxxxxx,x Wh 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 ID |
6 bytes |
According to M-Bus EN13757-3 identification field |
Meter ID 0C78xxxxxxxx |
|
3 |
Error flags |
4 bytes |
INT8 |
Error and warning flags 01FD17xx |
In message format JSON, data is presented on a plain text format.
The following table contains a description of all field included in the telegram.
Table 276. Payload, message format JSON [0x26]
|
Field |
Description |
|---|---|
|
Energy |
Energy consumption (Wh, J, Cal) |
|
Unit |
Unit of energy consumption |
|
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":12345.678,"U":"MWh","ID":87654321}
For message scheduled formats, such as Scheduled Daily Redundant 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, allowing a predictability of the received telegrams. The difference between a clock message and a data message is described in the following table.
Table 277. 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 278. Payload, clock message
|
Field |
Size |
Data type |
Description |
|---|---|---|---|
|
Message format identifier |
1 byte |
- |
0xFA (=Clock message) |
|
Data/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 the values listed in Table 279, “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 interval and will be transmitted immediately after the readout.
Note
When using scheduled message formats, the transmit interval cannot not be set to higher than 1440 (24 hours).
Table 279. Transmit interval options
|
Parameter |
Values |
Unit |
|---|---|---|
|
Transmit interval |
60, 120, 180, 240, 360, 480, 720, 1440 |
Minutes |
The data message of Scheduled mode-daily redundant contains an accumulated daily energy field, which is updated at 24:00 each day. Depending on transmit interval settings and data rate, the field will be included in between 1-24 data messages per day. This will increase the probability of the value being received. For example, if the transmit interval is set to “120”, the accumulated energy read at 24:00 will be transmitted 12 times during the 24 next coming hours.
Table 280. Payload, message format Scheduled – Daily redundant [0x27]
|
DIB |
Field |
Size |
Data type |
Description |
|---|---|---|---|---|
|
0 |
Message format |
1 byte |
- |
0x27 (= Scheduled – daily redundant) |
|
1 |
Heat energy E1 / Cooling Energy E3 |
6-7 bytes |
INT32 |
Energy consumption (Wh, J, Cal) 0400xxxxxxxx = xxxxxxxx,xxx Wh 0401xxxxxxxx = xxxxxxxx,xx Wh 0402xxxxxxxx = xxxxxxxx,x Wh 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 ( m³ ) 0411xxxxxxxx = xxxxxxxx * 0.00001 m³ 0412xxxxxxxx = xxxxxxxx * 0.0001 m³ 0413xxxxxxxx = xxxxxxxx * 0.001 m³ 0414xxxxxxxx = xxxxxxxx * 0.01 m³ 0415xxxxxxxx = xxxxxxxx * 0.1 m³ 0416xxxxxxxx = xxxxxxxx m³ 0417xxxxxxxx = xxxxxxxx * 10 m³ |
|
3 |
Meter ID |
6 bytes |
According to M-Bus EN13757-3 identification field |
Meter ID 0C78xxxxxxxx |
|
4 |
Error flags |
4 bytes |
INT8 |
Error and warning flags 01FD17xx |
|
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 = 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 yearlow 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) 4406xxxxxxxx = MWh, 3 decimals = kWh 440Exxxxxxxx = GJ, 3 decimals 44FB0Dxxxxxxxx = Gcal, 3 decimals 44863Dxxxxxxxx = MMBTU, 3 decimals 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. Example: The following table contains a detailed description of the payload of message format Scheduled - Daily redundant |
The data message of Scheduled mode-Extended contains all the data fields from message format Scheduled mode-Extended with an additional meter timestamp. Like all Scheduled message formats, the meter is read at full hour.
Table 281. Payload, message format Scheduled - Extended [0x28]
|
DIB |
Field |
Size |
Data type |
Description |
|---|---|---|---|---|
|
0 |
Message format identifier |
1 byte |
- |
0x28 (Scheduled-Extended) |
|
1 |
Heat energy E1 / Cooling Energy E3 |
6-7 bytes |
INT32 |
Energy consumption (Wh, J, Cal) 0400xxxxxxxx = xxxxxxxx,xxx Wh 0401xxxxxxxx = xxxxxxxx,xx Wh 0402xxxxxxxx = xxxxxxxx,x Wh 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 ( m³ ) 0411xxxxxxxx = xxxxxxxx * 0.00001 m³ 0412xxxxxxxx = xxxxxxxx * 0.0001 m³ 0413xxxxxxxx = xxxxxxxx * 0.001 m³ 0414xxxxxxxx = xxxxxxxx * 0.01 m³ 0415xxxxxxxx = xxxxxxxx * 0.1 m³ 0416xxxxxxxx = xxxxxxxx m³ 0417xxxxxxxx = xxxxxxxx * 10 m³ |
|
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-3 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 / Info bits |
9 bytes |
INT48 |
06FF21xxxxyyyyyyyy xxxx = Info bits (lsByte -> msByte) yyyyyyyy = Meter ID (lsByte -> msByte)* *Sent in binary format |
|
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 yearlow 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 |
Table 282. Payload, message format, Combined heat/cooling [0x29]
|
DIB |
Field |
Size |
Data type |
Description |
|---|---|---|---|---|
|
0 |
Message format |
1 byte |
- |
0x29 (Combined heat/cooling) |
|
1 |
Heat Energy E1 |
6-7 bytes |
INT32 |
Energy consumption (Wh, J, Cal) 0400xxxxxxxx = xxxxxxxx,xxx Wh 0401xxxxxxxx = xxxxxxxx,xx Wh 0402xxxxxxxx = xxxxxxxx,x Wh 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 E3 |
7-8 bytes |
INT32 |
Energy consumption (Wh, J, Cal, MBTU) 841006xxxxxxxx = MWh, 3 decimals = kWh 84100Exxxxxxxx = GJ, 3 decimals 8410FB0Dxxxxxxxx = Gcal, 3 decimals 8410863Dxxxxxxxx = MMBTu, 3 decimals |
|
3 |
Volume |
6 bytes |
INT32 |
Volume ( m³ ) 0411xxxxxxxx = xxxxxxxx * 0.00001 m³ 0412xxxxxxxx = xxxxxxxx * 0.0001 m³ 0413xxxxxxxx = xxxxxxxx * 0.001 m³ 0414xxxxxxxx = xxxxxxxx * 0.01 m³ 0415xxxxxxxx = xxxxxxxx * 0.1 m³ 0416xxxxxxxx = xxxxxxxx m³ 0417xxxxxxxx = xxxxxxxx * 10 m³ |
|
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 |
Error flags |
4 bytes |
INT8 |
Error and warning flags 01FD17xx |
In message format Engelmann, two types of telegrams are transmitted from the module; the first contain information collected from the Sensostar meter and the second information collected from meters connected via the module’s pulse inputs. Note that telegram 2 is only transmitted from the module if the pulse inputs are used.
When using the Engelmann message format the transmit interval (see section 6.5) is doubled to compensate for the additional telegrams transmitted in this message format, even if pulse inputs are not used and telegram 2 is not transmitted.
The module configuration parameter “Pulse input configuration” specifies which of the three pulse inputs are connected and whose data shall be read and transmitted by the module. Only the values configured to be included are sent. If no inputs are selected, telegram 2 is not sent.
Note: in case of errors in reading the data from the meter the function field in the DIF is set to indicate “value during error state” (M-Bus standard EN 13757-3:2013). In such cases the VIF and data part should be ignored. Since the unit of the input can be unknown in such cases it is set to dimensionless in the VIF, e.g., B440FD3A00000000 = pulse counter 1, no unit, with “value during error state”
Table 283. Payload, message format Engelmann, heat meter telegram [0x2C]
|
DIB |
Field |
Size |
Data type |
Description |
|---|---|---|---|---|
|
0 |
Message format |
1 byte |
- |
0x2C (Engelmann, telegram 1) |
|
1 |
Heat energy E1 / Cooling Energy E3 |
6-7 bytes |
INT32 |
Energy consumption (Wh, J, Cal) 0400xxxxxxxx = xxxxxxxx,xxx Wh 0401xxxxxxxx = xxxxxxxx,xx Wh 0402xxxxxxxx = xxxxxxxx,x Wh 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 E3* |
7-8 bytes |
INT32 |
Energy consumption (Wh, J, Cal, MBTU) 841006xxxxxxxx = MWh, 3 decimals = kWh 84100Exxxxxxxx = GJ, 3 decimals 8410FB0Dxxxxxxxx = Gcal, 3 decimals 8410863Dxxxxxxxx = MMBTu, 3 decimals |
|
3 |
Volume |
6 bytes |
INT32 |
Volume ( m³ ) 0411xxxxxxxx = xxxxxxxx * 0.00001 m³ 0412xxxxxxxx = xxxxxxxx * 0.0001 m³ 0413xxxxxxxx = xxxxxxxx * 0.001 m³ 0414xxxxxxxx = xxxxxxxx * 0.01 m³ 0415xxxxxxxx = xxxxxxxx * 0.1 m³ 0416xxxxxxxx = xxxxxxxx m³ 0417xxxxxxxx = xxxxxxxx * 10 m³ |
|
4 |
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 = 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 yearlow 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 |
|
5 |
Meter ID |
6 bytes |
According to M-Bus EN13757-3 identification field |
Meter ID 0C78xxxxxxxx |
|
6 |
Error flags |
4 bytes |
INT8 |
Error and warning flags 01FD17xx |
*Cooling Energy E3 field is only valid in a combined heat/cooling meter for message format Engelmann. Else the function field of the DIF is set to “value during error state” to indicate that the value is not valid.
Table 284. Payload, message format Engelmann, pulse input telegram
|
DIB |
Field |
Size |
Data type |
Description |
|---|---|---|---|---|
|
0 |
Message format |
1 byte |
- |
0x2D (Engelmann, telegram 2) |
|
1 |
Pulse input 1 |
7-8 bytes |
INT32 |
844013xxxxxxxx = m3, 3 decimals 844014xxxxxxxx = m3, 2 decimals 844015xxxxxxxx = m3, 1 decimal 844006xxxxxxxx = MWh, 3 decimals 844007xxxxxxxx = MWh, 2 decimals 8440FD3Axxxxxxxx = No unit |
|
2 |
Pulse input 2 |
8-9 bytes |
INT32 |
84804013xxxxxxxx = m3, 3 decimals 84804014xxxxxxxx = m3, 2 decimals 84804015xxxxxxxx = m3, 1 decimal 84804006xxxxxxxx = MWh, 3 decimals 84804007xxxxxxxx = MWh, 2 decimals 848040FD3Axxxxxxxx = No unit |
|
3 |
Pulse input 3 |
8-9 bytes |
INT32 |
84C04013xxxxxxxx = m3, 3 decimals 84C04014xxxxxxxx = m3, 2 decimals 84C04015xxxxxxxx = m3, 1 decimal 84C04006xxxxxxxx = MWh, 3 decimals 84C04007xxxxxxxx = MWh, 2 decimals 84C040FD3Axxxxxxxx = No unit |
|
4 |
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 = 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 yearlow 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 |
|
5 |
Meter ID |
6 bytes |
According to M-Bus EN13757-3 identification field |
Meter ID 0C78xxxxxxxx |
Comments (0 comments)