SIST EN 50491-11:2015

SLOVENSKI STANDARD
01-september-2015
Splošne zahteve za stanovanjske in stavbne elektronske sisteme (HBES) in
sisteme za avtomatizacijo in krmiljenje stavb (BACS) - 11. del: Inteligentno
merjenje - Aplikacijske specifikacije - Preprost zunanji prikazovalnik za uporabnika
General requirements for Home and Building Electronic Systems (HBES) and Building
Automation and Control Systems (BACS) - Part 11: Smart Metering - Application
Specifications - Simple External Consumer Display
Allgemeine Anforderungen an die Elektrische Systemtechnik für Heim und Gebäude
(ESHG) und an Systeme der Gebäudeautomation (GA) -- Teil 11: Smart Metering -
Applikationsbeschreibung - Einfache externe Verbrauchsanzeige
Exigences générales pour systèmes électroniques pour les foyers domestiques et les
bâtiments (HBES) et pour systèmes de gestion technique du bâtiment (SGTB) -- Partie
11: Comptage intelligent - Spécifications d’application - Affichage simple et externe du
client
Ta slovenski standard je istoveten z: EN 50491-11:2015
ICS:
35.240.99 8SRUDEQLãNHUHãLWYH,7QD IT applications in other fields
GUXJLKSRGURþMLK
97.120 Avtomatske krmilne naprave Automatic controls for
za dom household use
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN 50491-11

NORME EUROPÉENNE
EUROPÄISCHE NORM
June 2015
ICS 97.120
English Version
General requirements for Home and Building Electronic Systems
(HBES) and Building Automation and Control Systems (BACS) -
Part 11: Smart Metering - Application Specifications - Simple
External Consumer Display
Exigences générales pour systèmes électroniques pour les Allgemeine Anforderungen an die Elektrische
foyers domestiques et les bâtiments (HBES) et pour Systemtechnik für Heim und Gebäude (ESHG) und an
systèmes de gestion technique du bâtiment (SGTB) - Partie Systeme der Gebäudeautomation (GA) - Teil 11: Smart
11: Comptage intelligent - Spécifications d'application - Metering - Applikationsbeschreibung - Einfache externe
Affichage simple et externe du client Verbrauchsanzeige
This European Standard was approved by CENELEC on 2015-05-04. CENELEC members are bound to comply with the CEN/CENELEC
Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC
Management Centre or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the
same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2015 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 50491-11:2015 E
Contents
Foreword . 4
Introduction . 5
1 Scope . 6
2 Normative References. 6
3 Terms, definitions and abbreviations . 6
3.1 Terms and definitions . 6
3.2 Abbreviations . 7
4 General reference model . 8
5 Requirements for the Data interface . 10
5.1 General . 10
5.2 Minimization of data transmission . 11
5.3 Data consistency . 11
5.4 Filtering of message types and data points . 11
6 Conformity and Testing . 12
7 Metering Functional Blocks of MDC . 12
7.1 MDC Heat Meter (M_HEATM) . 12
7.1.1 Aims and objectives . 12
7.1.2 Functional specification . 12
7.1.3 Constraints . 12
7.1.4 Data Point Overview . 13
7.2 MDC Heat Cost Allocator (M_HCA) . 15
7.2.1 Aims and objectives . 15
7.2.2 Functional specification . 15
7.2.3 Constraints . 15
7.2.4 Data Point Overview . 16
7.3 MDC Water Meter (M_WATERM) . 17
7.3.1 Aims and objectives . 17
7.3.2 Functional specification . 17
7.3.3 Constraints . 17
7.3.4 Data Point Overview . 18
7.4 MDC Generic Meter (M_GENERICM) . 19
7.4.1 Aims and objectives . 19
7.4.2 Functional specification . 19
7.4.3 Constraints . 20
7.4.4 Data Point Overview . 20
7.5 MDC Gas Meter (M_GASM) . 21
7.5.1 Aims and objectives . 21
7.5.2 Functional specification . 21
7.5.3 Constraints . 22
7.5.4 Data Point Overview . 22
7.6 MDC Electricity Meter (M_ELECM) . 23
7.6.1 Aims and objectives . 23
7.6.2 Functional specification . 23
7.6.3 Constraints . 24
7.6.4 Data Point Overview . 24
7.7 MDC Breaker (M_BREAKERM) . 26
7.7.1 Aims and objectives . 26
7.7.2 Functional Specification . 26
7.7.3 Constraints . 26
7.7.4 Datapoint description. 26
7.8 MDC Valve (M_VALVEM). 27
7.8.1 Aims and objectives . 27
7.8.2 Functional Specification . 27
7.8.3 Constraints . 28
7.8.4 Datapoint description. 28
8 Metering Data model . 29
8.1 Introduction . 29
8.2 Boolean Value . 29
8.3 1-octet unsigned counter value . 30
8.4 Datapoint Types 2-Octet Float Value” . 30
8.5 2-octet unsigned counter value . 31
8.6 4-Octet Signed unsigned counter Value . 31
8.7 4 Octet signed time period . 31
8.8 Datapoint Type “MeteringValue” . 32
8.8.1 General . 32
8.8.2 Coding General . 32
8.8.3 Coding VallnfField . 33
8.8.4 Coding Status . 34
8.8.5 Recommended display format for metering data . 34
8.9 DPT Active Energy . 35
8.10 DPT for tariff information . 36
8.11 DPT_Currency . 36
8.12 DPTs for Price Information . 37
8.13 Format of DPT_DateTime . 37
8.13.1 Coding . 37
8.13.2 Remarks to the coding of DPT_DateTime . 38
8.14 Datapoint Type DPT_Metering_DeviceType . 41
8.15 Datapoint Type Character Set . 42
8.16 Datapoint Type DPT_VarString_8859_1 . 43
8.17 DPT_Gas_Measurement_Condition . 43
8.18 Datapoint Type DPT_Meter_BreakerValve_State . 44
8.19 Datapoint Type DPT_Meter_Mode . 44
8.20 Datapoint Type DPT_Power_Threshold_Status . 45
8.21 Datapoint Type DPT_Battery_Status . 45
Bibliography . 46

Foreword
This document (EN 50491-11:2015) has been prepared by CLC/TC 205 "Home and Building Electronic
Systems (HBES)".
The following dates are fixed:
(dop) 2016-05-04
• latest date by which this document has to be
implemented at national level by publication of
an identical national standard or by
endorsement
(dow) 2018-05-04
• latest date by which the national standards
conflicting with this document have to
be withdrawn
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC [and/or CEN] shall not be held responsible for identifying any or all such patent
rights.
This document has been prepared under a mandate given to CENELEC by the European Commission
and the European Free Trade Association.
EN 50491-11 is part of the EN 50491 series, General requirements for Home and Building Electronic
Systems (HBES) and Building Automation and Control Systems (BACS), which comprises the following
parts:
− Part 1: General;
− Part 2: Environmental conditions;
− Part 3: Electrical safety requirements;
− Part 4-1: General functional safety requirements for products intended to be integrated in Building
Electronic Systems (HBES) and Building Automation and Control Systems (BACS);
− Part 5-1: EMC requirements, conditions and test setup;
− Part 5-2: EMC requirements for HBES/BACS used in residential, commercial and light industry
environment;
− Part 5-3: EMC requirements for HBES/BACS used in industry environment;
− Part 6-1: HBES installations — Installation and planning;
− Part 6-3: HBES installations — Assessment and definition of levels [Technical Report
CLC/TR 50491-6-3];
− Part 11: Smart Metering — Application Specification — Simple External Consumer Display (the
present document);
− Part 12: Smart grid — Application specification — Interface and framework for customer (currently at
Enquiry stage).
Introduction
In March 2009, the European Commission issued a mandate M/441 for the standardization of smart
metering functionalities and communication for usage in Europe for electricity, gas, heat and water
applications to ensure interoperability of technologies and applications within a harmonized European
market.
As a result, a Technical Report, CEN/CLC/ETSI TR 50572, Functional Reference Architecture for
Communications in Smart Metering Systems, was published in December 2011.
As a consequence of this work and in line with the CEN/CLC/ETSI TR 50572 functional reference
architecture, CLC/TC 205, responsible for Home and Building Electronic Systems, was entrusted with the
task to formulate standards for the communication from the smart metering system towards the home.
1 Scope
This European Standard specifies a data model to abstract the metering world towards a simple external
consumer display. The data model, as described by means of functional blocks contained in this
European Standard, lays down the format of metering data accessible by a simple external consumer
display. This data interface would be typically part of the meter communication functions and be accessed
by a simple external consumer display via the H1 interface of the CEN/CLC/ETSI TR 50572 between the
display and the meter communication functions.
The data interface specified in this document may also be accessed by the LNAP or NNAP through the C
or M interface, after which the data could be accessed by HBES devices through the H2 and H3 interface.
In other words, in this way the same data model can be used both on the H1 as well as the H2 and H3
interface.
The document specifies neither the communication mechanisms used on the data interface, nor the
applied data privacy and security mechanisms nor the ergonomics of the simple external consumer
displays, where national regulations may apply.
The document does also not specify the communication protocol used between the meters and the meter
communication functions. However, it takes into account the existing European standards like the
EN 13757 series (in particular EN 13757-3:2013 and its Annex O) and the EN 62056 series for the
definition of the data model.
2 Normative References
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
EN 13757 (all parts), Communication system for meters
prEN 50491-12, General requirements for Home and Building Electronic Systems (HBES) and Building
Automation and Control Systems (BACS) — Part 12: Smart grid — Application specification — Interface
and framework for customer
CEN/CLC/ETSI TR 50572, Functional Reference Architecture for Communications in Smart Metering
Systems
EN 62056 (all parts), Electricity metering data exchange — The DLMS/COSEM suite (IEC 62056, all
parts)
ISO 4217, Codes for the representation of currencies and funds
ISO/IEC 8859-1, Information technology — 8-bit single-byte coded graphic character sets — Part 1: Latin
alphabet No. 1
3 Terms, definitions and abbreviations
3.1 Terms and definitions
3.1.1
meter
instrument for measuring, memorizing and displaying data related to the consumption of a commodity
3.1.2
data point
container element, in which information is located related to a function of a product (in e.g. memory or a
register)
3.2 Abbreviations
C C interface – for the term and definition, see CEN/CLC/ETSI TR 50572
Cs Company Specific
FB Functional Block
H1 H1 interface – for the term and definition, see CEN/CLC/ETSI TR 50572
H2 H2 interface – for the term and definition, see CEN/CLC/ETSI TR 50572
H3 H3 interface – for the term and definition, see CEN/CLC/ETSI TR 50572
LNAP Local Network Access Point - for the term and definition, see CEN/CLC/ETSI TR 50572
M M interface – for the term and definition, see CEN/CLC/ETSI TR 50572
NA Not Allowed / Not Applicable
MCF Meter Communication Function – for the term and definition, see CEN/CLC/ETSI TR 50572
NNAP Neighbourhood Network Access Point – for the term and definition,
see CEN/CLC/ETSI TR 50572
HVAC Heating Ventilation Air Conditioning
4 General reference model
Figure 1 — Metering system topology from CEN/CLC/ETSI/TR 50572
Reference is made to the Reference architecture diagram for smart metering communications as given in
CEN/CLC/ETSI/TR 50572.
In this European Standard, a functional block is specified for each typical metering function, grouping a
number of in- and output data points, as depicted in Figure 1.
Figure 1 depicts logical entities and not physical devices.
NOTE 1 This standard does not define requirements for devices acting as data sources for the simple external
consumer display (devices sending input on the I interface shown in Figure 1) and are covered by other European
standards.
In line with the M/441 architecture, the information flow on the H1 is predominantly from the meter
communication function in one or more meters to one or more simple external consumer displays (or
optionally one common display), whereby the latter acts as sink of the information obtained through the
H1 interface from the meter communication functions. Where necessary, the consumer display may poll
data from the meter communication functions, e.g. historical values. In no case shall it be able to alter
metering data through the consumer display. Hence, most functional blocks of the data interface specified
in this European Standard contain data that are intended as output data to a connected display.
The data structures used on the H1 interface are part of this European Standard. All other underneath
described interfaces are informative.
NOTE 2 The wired Meter communication according to EN 13757-2 / EN 13757-6 is only applicable if it is used
exclusively for the H1 interface.
The functional blocks specified in this document may also be accessed by the LNAP or NNAP through
the C or M interface, after which the data could be accessed bi-directionally with HBES devices through
the H2 and H3 interface.
The communication on the H2 and H3 interface is part of prEN 50491-12.
For each connected metering function (Tx Meter in Figure 1), the corresponding metering communication
function shall hold an entity of the corresponding functional block. The input for each connected metering
function is supplied by meters complying with the EN 62056 and EN 13757 series and is not part of this
standard.
1)
The input to the LNAP and NNAP is due to be part of the IEC 62746 .
The measurable quantities shown in Table 1 can be represented in the data interface through the listed
functional blocks (FB):
Table 1 – Measurable quantities
Physical Media FB
Other M_GENERICM
Oil M_GENERICM
Electricity M_ELECM
Gas M_GASM b)
Heat (outlet) M_HEATM
Steam M_GENERICM
Warm Water (30°C to 90°C) M_WATERM
Water M_WATERM
Heat cost allocator M_HCA
Cooling Load meter (outlet) M_HEATM
Cooling Load meter (inlet) M_HEATM
Heat (inlet) M_HEATM
Heat and Cool M_HEATM
Breaker M_BREAKERM
Valve M_VALVEM
Waste water meter M_WATERM
1) Under development.
5 Requirements for the Data interface
5.1 General
Each metering function shall be represented by a corresponding functional block, typically part of the
metering communication function and accessed by a simple user display.
Some meters may also provide metering data history values (e.g. monthly data). It is highly
recommended that for each meter a limited set of history values is available, e.g. covering the previous
week, previous month or previous year.
Depending on national regulations, it may be necessary that some of the data survive power down
situations.
In case of one common display unit supporting multiple meter devices, during installation and teach-in
procedures of metering devices, a meter device directory shall be created to assign linked meters.
The format and management of the metering device directory is company and/or protocol specific and not
part of this specification. Appropriate procedures shall be provided to:
• add a new metering device, and
• replace a metering device by another device (with different identification number and e.g. different
unit/resolution of the metering data), and
• delete a metering device.
The above workflow shall be supported by appropriate means (e.g. device localization via display, text
information…).
Two data points ‘MeterReplacement’ and ‘MeterReplacementCounter’ are defined for each metering
Functional Block to detect and manage replacement of metering devices. Further company specific
mechanisms can be implemented to simplify the meter replacement workflow.
For each meter a ‘UserText’ may be configured to simplify identification and localization of the meter. This
‘UserText’ can be useful in case of:
• service, maintenance;
• binding of metering data to displays;
• billing information for the end user;
• etc.
In case of removal or deletion of a metering device from the device directory, it is highly recommended to
keep the corresponding instance of the functional block alive and set all data in the Functional Block to
void values (see below). It is not recommended to re-assign functional block Indices of the remaining
functional blocks because data processing by the data display could be corrupted.
After commissioning or power up, metering data can be void or outdated for hours until a new message
from a metering device is received by the metering communication function.
On customer move out, certain data may need to be made unavailable for the next customer.
On supplier change, certain data needs to be made unavailable for the next supplier.
The ‘OutOfService’ Status attribute in metering Data Points shall indicate void data. This status attribute
may be set in the following cases:
• No metering device is connected to the metering Functional Block (ex-factory default data).
• A previously connected metering device is removed or deleted from the device directory. Handling of
the metering device directory is manufacturer specific.
In case of meter replacement, all metering data in the corresponding Functional Block shall be set to void
as upon removal of the previous meter until the first valid metering data message from the new device is
received. This may take several hours.
NOTE This specification does not foresee specific mechanisms to supervise the presence/function of connected
metering devices using life-check mechanisms etc. Because of very manufacturer specific cyclic update periods for
metering messages, a life-check ‘timeout’ cannot be standardized. Therefore this specification does not put
requirements to set metering data automatically ‘OutOfService’ in case of missing/outdated data from the connected
metering device.
The simply user display can access metering data by:
• polling of Functional Blocks and Data Points or
• regularly by data being pushed to the display or
• notifications or messages (e.g. sent by an external actor or generated by the meter). Data structures
for this type of messages are not specified in this standard.
5.2 Minimization of data transmission
Meter data comprises data that change infrequently and some that change frequently. The data
transmission rate shall reflect the frequency with which the data is expected to change. In the case the
data is polled, the user display shall not access a next Data Point value before the meter communication
function has responded to the previous Data Point access, unless the meter communication function did
not respond to the user display’s request within a time that can be set manufacturer specific.
5.3 Data consistency
During polling of metering data, new metering data may be received and read-out data may be
inconsistent. For data consistency checking each metering Functional Block shall provide a Data Point
‘RxSequenceCounter’ that shall be incremented each time new metering data is received from the
corresponding metering device.
The user display reading out metering data shall check the ‘RxSequenceCounter’ counter before and
after read out of the complete set of metering data. If the sequence counter value has changed, metering
data may be inconsistent. The user display shall then retry the procedure.
5.4 Filtering of message types and data points
EN 13757-3 provides several message types declared by the C-field. For a display only a few Message
types are relevant. The special Request/Respond messages used for the Gateway to request special
data are not relevant for a simple external consumer display. For the presentation of the data the
spontaneous meter messages with C=44h are recommended. Also C=46h or 06h could be taken into
account, as they constitute special messages for installation purposes.
All other message types should be ignored. If a message is ignored the reception time stamp
“RxReceptionTime” shall not be changed.
It is recommended to limit the number of supported VIF/VIFE of EN 13757-3 for a consumer display.
The following data points may be excluded from the interpretation:
• Plain text VIF 7Ch/FCh , as used for very uncommon units;
• Manufacturer specific VIFs 7Fh/FFh;
• Extension Table FDh.
The manufacturer shall consider to also limit the number of supported units from the extension table FBh.
6 Conformity and Testing
The requirements for the data interface between the meter communication function and a simple user
display are given in Clause 5 of this standard.
The measurable quantity or quantities determine the need to implement the functional blocks as given in
Table 1. If a certain function of the functional blocks as described in the relevant section of Clause 7 is
implemented, then the data structures shall comply with the format as given in Clause 8. If a certain
function is added that is not described in functional blocks as given in Clause 7, the data structures used
may be manufacturer or country specific.
Testing of compliance consist in the checking of the correct implementation of the (different parts) of the
data structures. As this standard does not describe the communication protocols used to transport the
specified data structures, testing of compliance of the implemented data structures may have to be
performed with testing tools that are specific to the used communication protocol.
7 Metering Functional Blocks of MDC
7.1 MDC Heat Meter (M_HEATM)
7.1.1 Aims and objectives
The Functional Block ‘MDC Heat Meter’ shall contain heat meter data (Device Type = 4, 10 to 13 –
see 8.14).
NOTE The same Functional Block also covers measurement of cooling energy.
7.1.2 Functional specification
The data points of the functional block representing heat meter data can be accessed by the display.
7.1.3 Constraints
Only a subset of metering data may be accessible by the display. The effective number of data that is
provided by meters is company specific.
7.1.4 Data Point Overview
Table 2 — Data Point Overview M_HEATM
Datapoint Description Datapoint Type
CurrentEnergyConsumption Accumulated energy value DPT_MeteringValue
TempFlowWater Current flow temperature DPT_Value_Temp
TempReturnWater Current Return temperature DPT_Value_Temp
TempDiffWater Current Temperature difference DPT_Value_Tempd
ReliabilityOfMeteringData Indicates whether metering data are up-to-date or DPT_Bool
outdated.
CurrentPower Current measured power DPT_MeteringValue
CurrentVolumeFlow Current measured volume flow DPT_MeteringValue
CurrentEnergyConsumption_T1 Current energy consumption Tarif 1 DPT_MeteringValue
HistoryStorageNumbers Array of storage numbers for history values DPT_Value_1_Ucount[n]
HistoryDate Array of date/time information for history values DPT_DateTime[n]
HistoryEnergyConsumption Array of energy consumption history values DPT_MeteringValue[n]
HistoryEnergyConsumption_T1 Array of energy consumption tarif 1 history values DPT_MeteringValue[n]
HistoryVolumeMaxFlow Array of Max Volume Flow history values DPT_MeteringValue[n]
HistoryVolumeMinFlow Array of Min Volume Flow history values DPT_MeteringValue[n]
HistoryMaxPower Array of Max. Power history values DPT_MeteringValue[n]
HistoryMinPower Array of Min. Power history values DPT_MeteringValue[n]
RxSequenceCounter Sequence counter generated locally by the receiver DPT_Value_1_Ucount
and incremented each time a metering message is
received. This data point shall be used for consistency
checking.
RxReceptionTime Time stamp generated locally by the receiver each DPT_DateTime
time a metering message is received
Manufacturer manufacturer code of the connected meter DPT_Value_2_Ucount
IdentificationNumber Mapping 8 Digit BCD to unsigned long integer DPT_Value_4_Ucount
VersionNumber Version of the device, structure is manufacturer DPT_Value_1_Ucount
specific
Datapoint Description Datapoint Type
Metering DeviceType Metering Device Type. Supported values in M_HEATM DPT_Metering_DeviceType
are:
4 : Heat meter
10 : Cooling Load energy meter
(outlet)
11 : Cooling Load energy meter (inlet)
12 : Heat energy (inlet)
13 : Heat and Cool energy
255 : void Medium
FabricationNumber Mapping 8 Digit BCD to unsigned long integer DPT_Value_4_Ucount
AccessNumber Consecutive message number that is generated by the DPT_Value_1_Ucount
metering device
DeviceStatus Combined Status/Error-code (bitset) DPT_Value_1_Ucount
OperatingTime Duration of meter accumulation DPT_LongDeltaTimeSec
OnTime Duration of Meter power up DPT_LongDeltaTimeSec
CurrentDate Date and time of the meter DPT_DateTime
MaxPowerDate Date and time of Maximum Power DPT_DateTime
MaxPower Measured maximum power value, DPT_MeteringValue
reset after change of storage nr
MinPowerDate Date and time of Minimum Power DPT_DateTime
MinPower Measured minimum power value DPT_MeteringValue
ErrorDate Date and time of Error event DPT_DateTime
ErrorConsumption value of energy consumption at the moment when an DPT_MeteringValue
error occurred
AveragingDuration Measuring time for current min/max value generation DPT_LongDeltaTimeSec
(integration time)
MeteringRawData raw data of metering telegram DPT_Value_1_Ucount [n]
UserText Additional text information to the metering device, DPT_VarString_8859_1
which can be entered by the installer during
commissioning
MeterReplacement Indicates that the connected heat meter is replaced. DPT_Bool
This data point shall be set automatically by the Data
interface and shall be reset manually by the
installer/service technician.
Datapoint Description Datapoint Type
MeterReplacementCounter Indicates the number of meter replacements. The DPT_Value_1_Ucount
counter shall be incremented automatically each time a
meter is replaced. The Datapoint is (normally) read
only.
Currency Indicates the currency applicable for the costs and DPT_Currency
credit communicated by the server to the client (e.g.
data interface to the display)
Accumulated Cost Indicates the accumulated costs of the energy DPT_Cost
consumption (negative values would allow encoding
profit)
Current Credit Indicates the current credit level (negative values DPT_Credit
would allow encoding debit)
Mode Indicates the current mode of the meter DPT_Meter_Mode
Battery Status Indicates the current status of the battery in the meter DPT_Battery_State

7.2 MDC Heat Cost Allocator (M_HCA)
7.2.1 Aims and objectives
The Functional Block MDC ‘Heat Cost Allocator’ shall contain heat cost allocator data (Device Type = 8).
A heat cost allocator provides the measured relative cumulated heat consumption of e.g. a radiator.
7.2.2 Functional specification
The data points of the functional block representing the heat cost allocator can be accessed by the
display.
7.2.3 Constraints
Only a subset of metering data can be accessed by the display. The effective number of data that is
provided by meters is very company specific.
7.2.4 Data Point Overview
Table 3 — Data Point Overview M_HCA
Datapoint Description Datapoint Type
CurrentEnergyConsumption Accumulated HCA units DPT_MeteringValue
TempFlowWater Flow temperature (radiator temperature) DPT_Value_Temp
TempExternal External temperature (room temperature) DPT_Value_Temp
ReliabilityOfMeteringData Indicates whether metering data are up-to-date or DPT_Bool
outdated.
HistoryStorageNumbers Array of storage numbers for history values. DPT_Value_1_Ucount[n]
HistoryDate Array of date/time information for history values. DPT_DateTime[n]
HistoryEnergyConsumption Array of energy consumption history values. DPT_MeteringValue[n]
RxSequenceCounter Sequence counter generated locally by the receiver and DPT_Value_1_Ucount
incremented each time a metering message is received.
This data point shall be used for consistency checking.
RxReceptionTime Time stamp generated locally by the receiver each time DPT_DateTime
a metering message is received
MeteringDeviceType Metering Device Type. Supported values in M_HCA are: DPT_Metering_DeviceType
8: Heat cost allocator
255: void Medium
AccessNumber Consecutive message number that is generated by the DPT_Value_1_Ucount
metering device
DeviceStatus Combined Status/Error-code (bitset) DPT_Value_1_Ucount
OperatingTime Duration of meter accumulation DPT_LongDeltaTimeSec
OnTime Duration of Meter power up DPT_LongDeltaTimeSec
CurrentDate Date and time of the meter DPT_DateTime
ErrorDate Date and time of Error event DPT_DateTime
ErrorConsumption value of energy consumption HCA units at the moment DPT_MeteringValue
when an error occurred
ReliabilityOfMeteringData Indicates whether metering data are up-to-date or DPT_Bool
outdated.
AveragingDuration Measuring time for min/max values DPT_LongDeltaTimeSec
MeteringRawData raw data of Metering telegram DPT_Value_1_Ucount [n]
UserText Additional text information to the metering device, which DPT_VarString_8859_1
can be entered by the installer during commissioning.
Datapoint Description Datapoint Type
MeterReplacement Indicates that the connected Metering heat meter is DPT_Bool
replaced. This data point shall be set automatically by
the Data interface and shall be reset manually by the
installer/service technician.
MeterReplacementCounter Indicates the number of meter replacements. The DPT_Value_1_Ucount
counter shall be incremented automatically each time a
meter is replaced. The Datapoint is (normally) read-only.
Currency Indicates the currency applicable for the costs and credit DPT_Currency
communicated by the server to the client (e.g. data
interface to the display)
Accumulated Cost Indicates the accumulated costs of the energy DPT_Cost
consumption (negative values would allow encoding
profit)
Current Credit Indicates the current credit level (negative values would DPT_Credit
allow encoding debit)
Mode Indicates the current mode of the meter DPT_Meter_Mode
Battery Status Indicates the current status of the battery in the meter DPT_Battery_State

7.3 MDC Water Meter (M_WATERM)
7.3.1 Aims and objectives
The Functional Block MDC ‘Water Meter’ shall contain water meter data (Metering Type = 6, 7 and 40).
The Functional Block covers measurement of cold and warm water volume.
7.3.2 Functional specification
The data points of the functional block representing the water meter can be accessed by the display.
7.3.3 Constraints
Only a subset of metering data can be accessed by the display. The effective number of data that is
provided by meters is very company specific.
7.3.4 Data Point Overview
Table 4 — Data Point Overview M_WATERM
Datapoint Description Datapoint Type
CurrentVolumeConsumption Accumulated water volume. DPT_MeteringValue
CurrentVolumeFlow Current measured volume flow DPT_Value_Volume_Flow
TempFlowWater Current flow temperature DPT_Value_Temp
ReliabilityOfMeteringData Indicates whether metering data are up-to-date or DPT_Bool
outdated.
HistoryStorageNumbers Array of storage numbers for history values DPT_Value_1_Ucount[n]
HistoryDate Array of date/time information for history values DPT_DateTime[n]
HistoryVolumeConsumption Array of volume consumption history values DPT_MeteringValue[n]
HistoryVolumeMaxFlow Array of Max Volume Flow history values DPT_MeteringValue[n]
HistoryVolumeMinFlow Array of Min Volume Flow history values DPT_MeteringValue[n]
RxSequenceCounter Sequence counter generated locally by the receiver and DPT_Value_1_Ucount
incremented each time a metering message is received.
This data point is used for consistency checking
RxReceptionTime Time stamp generated locally by the receiver each time DPT_DateTime
a metering message is received
Manufacturer manufacturer code of the connected meter DPT_Value_2_Ucount
IdentificationNumber Mapping 8 Digit BCD -> unsigned long integer DPT_Valu
...