BS EN 13757-3:2013
$215.11
Communication systems for and remote reading of meters – Dedicated application layer
| Published By | Publication Date | Number of Pages |
| BSI | 2013 | 156 |
This European Standard applies to communication systems for meters and remote reading of meters.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 11 | Introduction |
| 12 | 1 Scope 2 Normative references NOTE Further information and examples are available in the download area of http://www.m-bus.com. 3 Terms and definitions, abbreviated terms and numbers 3.1 Terms and definitions 3.2 List of abbreviated terms |
| 14 | 3.3 Hexadecimal and binary numbers Binary numbers are designated by a following “b” Decimal numbers have no suffix! 4 General principles: Cl-field 4.1 Overview |
| 17 | Every data header for wireless M-Bus (EN 13757-4) shall contain at least: 4.2 Application reset and application select (Cl = 50h, 53h) (optional) 4.2.1 Application reset 4.2.2 Application select with subcode (optional) |
| 18 | 4.3 Slave select (52h) (optional) 4.4 Synchronise action (Cl = 5Ch) (optional) 4.5 Clock synchronisation (CI = 6Ch, 6Dh) (optional) For wireless communication (but not limited to this one), the clock synchronisation is executed by a special protocol for clock synchronisation. For this protocol CI-fields 6Ch and 6Dh are used. Annex H.3 specifies the transmission of clock synchronis… Alternatively, the clock may set by an M-Bus-command. The communication partner may send date and time in all command messages to ensure that the meter can detect a replay of an old command. The meter shall not use this time stamp for synchronisation … 4.6 Report of application errors (slave to master) (Cl = 6Eh, 6Fh and 70h) (optional) 4.7 Report of alarm status (slave to master) (Cl = 71h, 74h and 75h) (optional) 4.8 Variable Data Send (master to slave) (CI = 51h, 5Ah, 5Bh, 60h, 61h, 64h, 65h) |
| 19 | 4.9 Variable Data Respond (slave to master) (Cl = 69h to 6Bh, 72h, 73h, 78h to 7Fh) 4.10 Baud rate switch commands B8h – BFh (optional) 5 Variable Data Send and Variable Data Respond 5.1 Introduction 5.2 Structure of none data header |
| 20 | 5.3 Structure of short data header 5.4 Structure of long data header 5.5 Identification number 5.6 Manufacturer identification |
| 21 | 5.7 Version identification 5.8 Device type identification |
| 22 | 5.9 Access number 5.9.1 Overview |
| 23 | 5.9.2 Generation of access number for meter initiated datagrams 5.9.3 Generation of access number for partner generated datagrams |
| 24 | 5.10 Status byte in meter messages The status bits shall be used in this meaning: Power low Warning – The bit “power low” is set only to signal interruption of external power supply or the end of battery life. Permanent error Failure – The bit “permanent error” is set only if the meter signals a fatal device error (which requires a service action). Error can be reset only by a service action. Temporary error Warning – The bit “temporary error” is set only if the meter signals a slight error condition (which not immediately requires a service action). This error condition may later disappear. Any application error Shall be used to communicate a failure during the interpretation or the execution of a received command, e.g. if a not decrypt able message was received. Abnormal conditions Shall be used if a correct working application detects an abnormal behaviour like a permanent flow of water by a water meter. |
| 25 | 5.11 Status byte in partner messages Table 9 — Meaning of status byte for partner messages 5.12 Configuration field (previously: signature field) 5.12.1 General |
| 26 | 5.12.2 Functions data privacy for consumption meter values; detecting simulated meter transmission; preventing later replay of old meter values; preventing the detection of zero consumption by comparing messages. 5.12.3 Structure of encrypted messages Table 11 — Definition of the mode bits (encryption method) 5.12.4 Partial encryption |
| 27 | 5.12.5 Encryption methods DES (modes 2 and 3) |
| 28 | 5.12.6 Encryption methods AES-128 (mode 5) 5.12.6.1 General 5.12.6.2 Encryption mode 5 Table 14 — Initialisation vector mode 5 for the CBC-AES-128 |
| 29 | 5.12.6.3 Additional functionality of configuration field Table 15 — Contents of meter message |
| 30 | Bit 13 (S) is used to declare a synchronised transmission. If the transmission timing (predictable transmission time) fulfils the requirements of a synchronous transmission as defined in EN 13757-4, it shall mark this transmission with a set bit 13. O… The configuration field bits 14 (A) and 15 (B) (Accessibility and Bidirectional communication) are used as defined in Table 17 for access control to the meter. 5.12.6.4 Decryption verification 5.12.7 Examples Annex P shows examples with both unencrypted and encrypted data. 5.13 Address structure if used together with the wireless link layer according to EN 13757-4 |
| 31 | 6 Variable data blocks (records) 6.1 General Table 19 — Structure of a data record (transmitted from left to right) Each data record consists of a Data Record Header (DRH) and the value (data). The DRH in turn consists of the Data Information Block (DIB) to describe the length, type and coding of the data and the Value Information Block (VIB) to give the value of t… 6.2 Data Information Block (DIB) 6.3 Data Information Field (DIF) |
| 32 | Table 20 — Coding of the Data Information Field (DIF) 6.4 Data field Table 21 — Coding of the data field |
| 33 | Table 22 — DIF-coding for special functions 6.5 Function field Table 23 — Function field 6.6 Storage number |
| 34 | 6.7 Extension bit (E) 6.8 Data Information Field Extension (DIFE) Table 24 — Coding of the Data Information Field Extension (DIFE) 6.9 Tariff information 6.10 Subunit information |
| 35 | 7 Value Information Block (VIB) 7.1 General Table 25 — Coding of the Value Information Field (VIF) 7.2 Primary VIFs (main table) |
| 36 | Table 26 — Primary VIF-codes |
| 37 | 7.3 VIF-codes for special purposes 7.4 Main VIFE-code extension table (following VIF = FDh for primary VIF) Table 28 — Main VIFE-code extension table |
| 40 | 7.5 Alternate VIFE-code extension table (following VIF = FBh for primary VIF) Table 29 — Alternate extended VIF-code table |
| 41 | 7.6 Combinable (orthogonal) VIFE-Code extension table Table 30 — Combinable (orthogonal) VIFE-table |
| 44 | 8 Application layer status and error reporting 8.1 General 8.2 Status field 8.3 General application layer errors |
| 46 | 8.4 Record errors data field = 0000b: no data; data field = 0000b: no data and idle filler (DIF = 02Fh): fill record up to the normal length; other data field: dummy data of correct length; other data field: unsafe or estimated data. |
| 47 | 9 Generalised object layer Table 37 — Action codes for the generalised object layer (master to slave) 10 Manufacturer specific unstructured data block |
| 48 | 11 Management of lower layers 11.1 General Table 38 — Management layer of the M-Bus link layer according EN 13757-2 11.2 Switching baud rate for M-Bus link layer according to EN 13757-2 Table 39 — CI-field codes for baud rate switching |
| 49 | 11.3 Selection and secondary addressing Table 40 —Structure of a datagram for selecting a slave |
| 50 | 11.4 Generalised selection procedure Enhanced selection with fabrication number Table 41 — Application layer structure of a datagram for enhanced selection (mode 1) |
| 51 | 11.5 Searching for installed slaves 11.5.1 Primary addresses 11.5.2 Secondary addresses 11.5.3 Wildcard searching procedure |
| 52 | Annex A (normative) Coding of data records Type A: Unsigned integer BCD := XUI4 [1 to 4] Type B: Binary integer := I[1..X] (-2X-1 +1) to +(2X-1-1) Type C: Unsigned integer:= UI[1..X] 0 to 2X-2 |
| 53 | Type F: Compound CP32: Date and time Type G: Compound CP16: Date |
| 54 | Type H: Floating point according to IEEE-standard “Short floating point number IEEE STD 754” = R32IEEESTD754 |
| 55 | Type I: Year down to second |
| 56 | Type J: Time of day |
| 59 | Annex B (normative) Interpretation of hex-codes Ah – Fh in BCD-data fields B.1 General description standard reference B.1.1 Purpose B.2 Definition B.2.1 Hex code meanings B.2.2 LCD-decoding table |
| 60 | Annex C (normative) VIF coding for special units C.1 Non-metric units C.2 Plain text units |
| 61 | C.3 Remote enablement/disablement of valve/breaker Table C.3 — Values for the remote control of the valve |
| 62 | Annex D (informative) Alarm protocol D.1 M-Bus according EN13757-2 D.2 Wireless M-Bus according to EN 13757-4 |
| 63 | Annex E (informative) Examples E.1 General E.2 Example for a RSP_UD with variable data structure answer: E.3 Example baud rate switch: |
| 64 | E.4 Example application select with subcode: E.5 Writing data to a slave |
| 66 | E.6 Configuring data output E.6.1 General E.6.2 Selection without specified data field |
| 67 | E.6.3 Selection with specified data field E.6.4 Deselection of data records |
| 68 | E.7 FCB and selection E.7.1 FCB-implementation slave E.7.2 FCB-implementation master |
| 69 | E.8 Special slave features E.8.1 General E.8.2 Use of the fabrication number |
| 71 | Annex F (informative) Secondary search F.1 General Key |
| 72 | F.2 Instructions for implementation of wildcard search |
| 74 | Annex G (informative) International reference works |
| 75 | Annex H (informative) Special sequences for wireless M-Bus devices H.1 VIF/VIFE/VIFE = FDh 97h 1Dh (error flag) If the data point VIF/VIFE/VIFE = FDh 97h 1Dh is used, then the two least significant bytes of error flag have the following meaning: |
| 76 | H.2 VIF/VIFE/VIFE = FDh 9Fh 1Dh for passing remote control on a node If the data point VIF/VIFE/VIFE = FDh 9Fh 1Dh for a wireless M-Bus device is used the least significant byte of remote control has the following meaning: Table H.7 — Remote control (RC1): power save mode Table H.8 — Remote control (RC1): reserved |
| 77 | H.3 Clock synchronisation Table H.9 — Structure of TC-field Table H.10 — Application frame “time setting” with CI=6Ch (Set date and time) Table H.11 — Application frame “time adjustment” with CI=6Dh (Add/Subtract Time Offset) |
| 79 | Annex I (normative) Transmission of profiles I.1 The standard load profile |
| 80 | I.2 The M-Bus compact profile I.2.1 General I.2.2 The base value and base parameter I.2.3 The base time I.2.4 Structure of the compact profile |
| 82 | I.2.5 Types of Compact profile I.2.6 Compact profile with registers (orthogonal VIFE=1Eh) |
| 83 | I.2.7 Compact profile without registers (orthogonal VIFE=1Fh) |
| 84 | Annex J (informative) The structure of higher protocol layers |
| 86 | Annex K (normative) Compact M-Bus frame K.1 General K.2 CI-fields of the Full and the Compact M-Bus frame |
| 87 | K.2.1 Full M-Bus frame K.2.2 M-Bus- Compact frame |
| 88 | K.2.3 M-Bus-Format frame K.3 Calculation of the Full-Frame-CRC K.4 Calculation of the Format Signature |
| 89 | K.5 Frame examples K.5.1 General K.5.2 Example without data header K.5.3 Example with short data header, no encryption |
| 90 | K.5.4 Example with short data header, encryption mode 5 |
| 91 | Annex L (informative) Use of standards for smart metering applications L.1 General L.2 Data integrity All data integrity is based on the European Standards of EN 60870-5-1. L.3 Privacy L.4 Signature |
| 92 | L.5 Authentication L.6 Billing L.7 Consumer feedback L.7.1 Introduction L.7.2 Required values and their resolution and accuracy L.7.2.2 Required resolution if an extra data point for flow/power) is transmitted. The required value resolutions for meter with additional data points for flow/power are: |
| 93 | Table L.1 — Required value resolution for meter with power/flow data It is recommended that the averaging duration for power/flow values is similar to the average update interval (mean time between two transmissions of messages with updated consumption data). A shorter averaging period might produce strongly variant sn… L.7.3 Required resolution if no extra data point for flow (respectively power) is transmitted. L.7.3.1 General |
| 94 | L.7.3.2 Required time information L.7.3.3 Correlated transmission L.7.3.4 Uncorrelated transmission L.7.4 Transmission on request L.8 Advanced tariffing and prepayment L.8.1 General |
| 95 | L.8.2 Prepayment |
| 96 | Annex M (informative) Installation and registration M.1 General |
| 97 | M.2 Registration with meter support M.2.1 Introduction M.2.2 RF-Link feedback M.2.3 Registration feedback M.3 Registration without meter support To reduce the meter requirements and the service actions of the installer, the support of installation messages may not be provided by all meters. Meters for such a remote based registration start transmitting directly after the mechanical installatio… |
| 98 | This method may also be applied for meters which actually support installation messages, e.g. when the communication partner was replaced or updated. |
| 99 | Annex N (informative) M-Bus data container N.1 Explanation N.2 Definition |
| 100 | N.3 Example |
| 101 | Annex O (normative) Translating M-Bus type record descriptors to OBIS-type record descriptors |
| 102 | O.1 Translation of predefined data record types This list describes how a communication partner can “translate” received M-Bus record into OBIS type records. |
| 107 | Table O.5 — M-Bus-OBIS-Translation: cooling meter |
| 109 | Table O.6 — M-Bus-OBIS-Translation: combined heat and cooling meter |
| 110 | This table consists of the cooling meter counts of combined heat/cooling meters (Device Type = 0Dh). Refer to heat meter for heat meter counts. |
| 111 | Table O.7 — M-Bus-OBIS-Translation: heat meter |
| 113 | Table O.8 — M-Bus-OBIS-Translation: gas meter |
| 115 | Table O.9 — M-Bus-OBIS-Translation: water meter (cold) |
| 116 | Table O.10 — M-Bus-OBIS-Translation: water meter (hot, warm) |
| 117 | O.2 Online addition of an entry for the M-Bus to OBIS conversion table The relevant OBIS-declaration 8-0:2.5.0*255 will be transmitted either binary or with BCD-numbers. BCD-coding: The relevant OBIS-Declaration will be transmitted as 12 digits BCD by: 1Eh DIF; maximum value; 12 digits BCD BBh VIF; Flow rate with unit 10-3 m3/h; VIFE follows 3Fh VIFE “OBIS-declaration” AAh 00h 05h 02h 00h 08h Value; OBIS-code 8-0:2.5.0*255 Binary coding: Alternatively, the relevant OBIS-declaration will be transmitted, e.g. as 48-bit binary by: |
| 118 | Annex P (informative) Datagram examples for the M-Bus and the wM-Bus P.1 Gas meter Table P.1 — SND-NR – Gas meter (wM-Bus) |
| 121 | Table P.2 — RSP-UD – Gas meter (M-Bus) |
| 123 | P.2 Water meter Table P.3 — SND-NR – Water meter (wM-Bus) |
| 126 | Table P.4 — RSP-UD – Water meter (M-Bus) |
| 128 | P.3 Heat meter Table P.5 — SND-NR – Heat meter (wM-Bus) |
| 131 | Table P.6 — RSP-UD – Heat meter (M-Bus) |
| 133 | P.4 Heat cost allocator Table P.7 — SND-NR – H.C.A. (wM-Bus) |
| 136 | Table P.8 — RSP-UD – H.C.A. (M-Bus) |
| 138 | P.5 Installation procedure with a special installation message Table P.9 — SND-IR (wM-Bus) |
| 142 | Table P.10 — CNF-IR (wM-Bus) |
| 143 | P.6 Send a command with an acknowledge Table P.11 — SND-UD (wM-Bus) |
| 145 | Table P.12 — ACK long (wM-Bus) |
| 146 | P.7 Request of the selected data |
| 147 | Table P.13 — REQ-UD2 (wM-Bus) |
| 148 | Table P.14 — RSP-UD (wM-Bus data) |
| 151 | P.8 Reset of the link by a SND-NKE Table P.16 — SND-NKE (wM-Bus) |
| 153 | Bibliography |
Related products
-
BS EN 50491-11:2015
General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems…
