EN 13757-3:2004
(Main)Communication systems for meters and remote reading of meters - Part 3: Dedicated application layer
Communication systems for meters and remote reading of meters - Part 3: Dedicated application layer
This document applies to communication systems for meters and remote reading of meters.
Kommunikationssysteme für Zähler und deren Fernablesung - Teil 3: Spezieller Application Layer
Erarbeitung einer Norm für den M-Bus Application Layer.
Systèmes de communication et de télérelevé de compteurs - Partie 3: Couches d'application spéciale
Préparer une norme pour la couche d'application spéciale M-Bus.
Komunikacijski sistemi za merilnike in daljinsko odčitavanje - 3. del: Posebna aplikacijska plast
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-april-2005
.RPXQLNDFLMVNLVLVWHPL]DPHULOQLNHLQGDOMLQVNRRGþLWDYDQMHGHO 3RVHEQD
DSOLNDFLMVNDSODVW
Communication systems for and remote reading of meters - Part 3: Dedicated application
layer
Kommunikationssysteme für Zähler und deren Fernablesung - Teil 3: Spezieller
Application Layer
Systemes de communication et de télérelevé de compteurs - Partie 3: Couches
d'application spéciale
Ta slovenski standard je istoveten z: EN 13757-3:2004
ICS:
33.200 Daljinsko krmiljenje, daljinske Telecontrol. Telemetering
meritve (telemetrija)
35.100.70 Uporabniški sloj Application layer
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN STANDARD
EN 13757-3
NORME EUROPÉENNE
EUROPÄISCHE NORM
November 2004
ICS 33.200; 35.100.70
English version
Communication systems for and remote reading of meters - Part
3: Dedicated application layer
Systèmes de communication et de télérelevé de compteurs Kommunikationssysteme für Zähler und deren
- Partie 3: Couches d'application spéciale Fernablesung - Teil 3: Spezieller Application Layer
This European Standard was approved by CEN on 23 September 2004.
CEN 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 Central Secretariat or to any CEN 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 CEN member into its own language and notified to the Central Secretariat has the same status as the official
versions.
CEN members are the national standards bodies of Austria, Belgium, Cyprus, Czech Republic, Denmark, Estonia, Finland, France,
Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia,
Slovenia, Spain, Sweden, Switzerland and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre: rue de Stassart, 36 B-1050 Brussels
© 2004 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 13757-3:2004: E
worldwide for CEN national Members.
Contents
page
Foreword.3
Introduction .4
1 Scope .5
2 Normative references .5
3 Terms and definitions .5
4 General principles : Cl-field.6
5 Variable Data Respond (Cl = 72h, Cl = 78h, Cl = 7Ah).9
6 Variable Data Blocks (Records) .14
7 Value Information Block (VIB) .18
8 Application Layer Status and error reporting.25
9 Generalized Object Layer.28
10 Manufacturer Specific unstructured Data Block .28
11 Management of lower layers.29
Annex A (normative) Coding of Data Records .33
Annex B (normative) Interpretation of Hex-Codes Ah - Fh in BCD-data fields .39
Annex C (normative) Non metric units .40
Annex D (informative) Alarm Protocol.41
Annex E (informative) Examples.42
Annex F (informative) Secondary Search .49
Annex G (informative) International reference works.52
Annex H (informative) Meaning of "device type specific" parameters of Mbus for Radio products.53
Bibliography .55
Foreword
This document (EN 13757-3:2004) has been prepared by Technical Committee CEN/TC 294 “Communication
systems for meters and remote reading of meters”, the secretariat of which is held by AFNOR.
This European Standard shall be given the status of a national standard, either by publication of an identical
text or by endorsement, at the latest by May 2005, and conflicting national standards shall be withdrawn at the
latest by May 2005.
This standard consists of the following parts:
EN 13757-1, Communication system for meters and remote reading of meters - Part 1: Data exchange.
EN 13757-2, Communication systems for and remote reading of meters - Part 2: Physical and link layer.
EN 13757-3, Communication systems for and remote reading of meters - Part 3: Dedicated application layer.
prEN 13757-4, Communication systems for meters and remote reading of meters - Part 4: Wireless meter
readout.
According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to implement this European Standard: Austria, Belgium, Cyprus, Czech Republic,
Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, Switzerland
and United Kingdom.
Introduction
This document belongs to a series of parts of EN 13757 which covers communication systems for meters and
remote reading of meters. Part 1 contains generic descriptions and a communication protocol. Part 2 contains
a physical and a link layer for twisted pair base band (M-Bus). Part 4 (currently an enquiry is under
preparation) describes wireless communication.
The bus communication system of EN 1434–3 is commonly called M-Bus. Its application layer describes a
standard especially for meter readout.
It can be used with various physical layers and with link layers and network layers which support the
transmission of variable length binary transparent telegrams. Frequently the physical and link layers of
EN 13757-2 (Twisted pair baseband) and prEN 13757-4 (wireless) or the alternatives described
in EN 13757-1 are used.
An overview of communication systems for meters is given in EN 13757-1, which also contains further
definitions.
This standard is a compatible enhancement of the 6.4 to 6.6 of the original standard EN 1434–3:1997.
Besides some clarifications and implementation hints it contains optional enhancements especially for
complex meters. Due to technical progress some variants (Fixed format and mode 2=high byte first) are no
longer supported in this standard.
It should be noted that this standard contains only directions how data should be coded. It is beyond the task
of an application layer standard to define which data will be transmitted under what conditions by which types
of slaves or which data transmitted to a slave will have which reactions. Therefore adherence to this standard
guarantees the coexistence and common communication and readout capability of slaves via a universal
master software (covering all optional features), but not yet functional or communication interchangeabilty of
meters following this standard. For several meter types and meter classes a group of remote heating users
have provided such application descriptions required for full interchangeability. They are accessible via the
www-server of the m-bus users group http://www.m-bus.com/files/default.html (file name: WG4N99R4.EXE
(this is a self expanding .doc-file)).
1 Scope
This document applies to communication systems for meters and remote reading of meters.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
EN 13757-2:2004, Communication systems for and remote reading of meters - Part 2: Physical and link layer.
NOTE Further information and examples are available in the download area of http://www.m-bus.com.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1 Table of abbreviations
DES Data Encryption Standard
DRH Data Record Header
DIB Data Information Block
DIF Data Information Field
DIFE Data Information Field Extensions
VIB Value Information Block
VIF Value Information Field
VIFE Value Information Field Extensions
RSP_UD Respond User Data
SND_UD Send User Data to slave
REQ-UD Request User Data
MDH Manufacturer Specific Data Block
CI Control Information Field
E Extension Bit
3.2
hexadecimal numbers
hexadecimal numbers are designated by a following "h"
Binary numbers
4 General principles : Cl-field
4.1 Overview
All application layer telegrams have variable length. The length information is part of the link layer. It shall be
known to the application layer in order to properly terminate its decoding of each telegram. Each telegram
starts with a one byte CI (control information) field, which distinguishes between various telegram types and
application functions. It is also used to distinguish between true application layer communication and
management commands for lower layers. The meaning of the remaining bytes of the telegram depends also
on the value of the CI-field.
Table 1 — CI-Field codes used by the master or the slave
Application
00h to 4Fh reserved for DLMS-based applications
50h application reset
51h data send (master to slave)
52h selection of slaves
53h reserved
54h to 58h reserved for DLMS-based applications
55h to 5Bh reserved
5Ch synchronize action
60h to 6Fh reserved
70h slave to master: report of application errors
71h slave to master: report of alarms
72h slave to master: 12 byte header followed by variable format data
73h to 77h reserved
78h slave to master: Variable data format response without header
79h reserved
7Ah slave to master: 4 byte header followed by Variable data format response
7Bh to 80h reserved
81h reserved for a future CEN–TC294– Radio relaying and application Layer
82h reserved for a future CENELEC–TC205 network/application Layer
82h to 8Fh reserved
90h to 97h manufacturer specific (obsolete)
A0h to AFh manufacturer specific
B0 to B7h manufacturer specific
B8h set baud rate to 300 baud
B9h set baud rate to 600 baud
BAh set baud rate to 1 200 baud
BBh set baud rate to 2 400 baud
BCh set baud rate to 4 800 baud
BDh set baud rate to 9 600 baud
BEh set baud rate to 19 200 baud
BFh set baud rate to 38 400 baud
C0h to FFh reserved
Note that the CI-codes 50h, 52h, 5Ch, 70h, 71h, 78h, 7Ah, 80h, 81h, A0h – AFh and B8h – BFh are optional
compatible enhancements of the EN 1434-3:1997 standard. Note also that even if the functions of these
optional CI-codes are not implemented in a slave the link layer protocol requires a proper link layer
acknowledge of SND_UD telegrams containing any of these CI-codes.
The EN 1434–3 defined two possible data sequences in multibyte records. This standard supports only the
mode where the least significant byte of a multibyte record is transmitted first.
4.2 Application reset (Cl = 50h), (optional)
4.2.1 General
With the CI-Code 50h the master can release a reset of the application layer in the slaves. Each slave himself
decides which parameters to change – e.g. which data output is default – after it has received such an
application reset.
4.2.2 Application reset subcode (optional)
It is allowed to use optional parameters after CI = 50h. If more bytes follow, the first byte is the application
reset subcode. Further bytes are ignored. The application reset subcode defines which telegram function and
which subtelegram is requested by the master. The datatype of this parameter is 8 bit binary. The upper 4 bits
define the telegram type or telegram application and the lower 4 bits define the number of the subtelegram
(the meaning of this number is device specific). The lower four bits may be ignored for slaves which provide
only a single telegram for each application. The use of the value zero for the number of the subtelegram
means that all telegrams are requested.
Slaves with only one type of telegram may ignore application reset and the added parameters. The following
codes can
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.