|
Metering Data can be generated by multiple meters and metering sensors in the home or building. KNX provides the means to collect this rich information and make it available in a systematic way. For this purpose, KNX has specified a KNX Metering M-Bus Data Collector, as documented in Volume 10 of the KNX Specifications. The device allows the collection of metering data compliant with EN13757-3 and EN13757-4 (S Mode). The specification describes the standardised mapping of a substantial set of M-BUS DIF, DIFE, VIF and VIFE encodings. Though covering the majority of the implementations on the market, thanks to the common approach, additional mappings can easily be added. The most common M-Bus media can be mapped including heat, water and warm water, heat cost allocation, cooling load (inlet and outlet), heat (inlet) and heat and cool. Recently mapping of gas and electricity meter data has been added.
Operation of KNX M-Bus Data Collector.
One KNX M-Bus Data Collector can receive, filter and interpret M-Bus Data of up to eight meters, each represented by a KNX Interface Object. That KNX interface object holds static data of the meter, such as manufacturer, identification number, version, medium... as well as variable data, like operating time, dates and values for minimal and maximal metering data, information on errors and other. The Interface Object even allows storing the raw M-Bus telegram data. For each storage number, the history date, the energy consumption and the minimal and maximal flow and power are stored. The KNX M-Bus Data Collector acts as a server, holding the data of these 8 meters available for any client to read from remote. In all of this, great care is taken to maintain data integrity. Since this model, originally designed to represent M-Bus meters on KNX, is very complete, it can be used as the basic model for all possible other generic meters or metering interfaces (pulse counters, S0-interface...). More info: http://hiddenwires.co.uk/resourcesarticles2011/articles20110104-11.html |




