1、BRITISH STANDARDBS EN 61158-4-16:2008Industrial communication networks Fieldbus specifications Part 4-16: Data-link layer protocol specification Type 16 elementsICS 25.040.40; 35.100.20g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55
2、g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58BS EN 61158-4-16:2008This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 May 2008 BSI 2008ISBN 978 0 580 61584 9National forewordThis British Standard is the
3、UK implementation of EN 61158-4-16:2008. It is identical with IEC 61158-4-16:2007. Together with all of the other sections of BS EN 61158-4, it supersedes BS EN 61158-4:2004 which is withdrawn. Together with BS EN 61158-2, BS EN 61158-3-16, BS EN 61158-5-16 and BS EN 61158-6-16, it partially superse
4、des BS EN 61491:1999, which will be withdrawn upon publication of a revised edition currently in progress and which will be implemented as a Technical Report. The UK participation in its preparation was entrusted to Technical Committee AMT/7, Industrial communications Process measurement and control
5、, including Fieldbus.A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. Compliance with a British Standard canno
6、t confer immunity from legal obligations. Amendments/corrigenda issued since publicationDate CommentsEUROPEAN STANDARD EN 61158-4-16 NORME EUROPENNE EUROPISCHE NORM February 2008 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisch
7、es Komitee fr Elektrotechnische Normung Central Secretariat: rue de Stassart 35, B - 1050 Brussels 2008 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members. Ref. No. EN 61158-4-16:2008 E ICS 35.100.20; 25.040.40 Partially supersedes EN 61158-4:200
8、4 and EN 61491:1998English version Industrial communication networks - Fieldbus specifications - Part 4-16: Data-link layer protocol specification - Type 16 elements (IEC 61158-4-16:2007) Rseaux de communication industriels - Spcifications des bus de terrain - Partie 4-16: Spcification des protocole
9、s des couches de liaison de donnes - Elments de type 16 (CEI 61158-4-16:2007) Industrielle Kommunikationsnetze - Feldbusse - Teil 4-16: Protokollspezifikation des Data Link Layer (Sicherungsschicht) - Typ 16-Elemente (IEC 61158-4-16:2007) This European Standard was approved by CENELEC on 2008-02-01.
10、 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
11、 on application to the Central Secretariat 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 Central
12、Secretariat has the same status as the official versions. CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta
13、, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. Foreword The text of document 65C/474/FDIS, future edition 1 of IEC 61158-4-16, prepared by SC 65C, Industrial networks, of IEC TC 65, Industrial-process measurement, control
14、and automation, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 61158-4-16 on 2008-02-01. This and the other parts of the EN 61158-4 series supersede EN 61158-4:2004. Together with EN 61158-2:2008 and its companion parts for Type 16, it also partially replaces EN 614
15、91:1998 which is at present being revised (to be issued as a Technical Report). With respect to EN 61158-4:2004 the following changes were made: deletion of Type 6 fieldbus, and the placeholder for a Type 5 fieldbus data-link layer, for lack of market relevance; addition of new fieldbus types; parti
16、tion into multiple parts numbered 4-1, 4-2, , 4-19. The following dates were fixed: latest date by which the EN has to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2008-11-01 latest date by which the national standards conflicting with the
17、 EN have to be withdrawn (dow) 2011-02-01 NOTE Use of some of the associated protocol types is restricted by their intellectual-property-right holders. In all cases, the commitment to limited release of intellectual-property-rights made by the holders of those rights permits a particular data-link l
18、ayer protocol type to be used with physical layer and application layer protocols in type combinations as specified explicitly in the EN 61784 series. Use of the various protocol types in other combinations may require permission from their respective intellectual-property-right holders. Annex ZA ha
19、s been added by CENELEC. _ Endorsement notice The text of the International Standard IEC 61158-4-16:2007 was approved by CENELEC as a European Standard without any modification. _ BS EN 61158-4-16:2008 2 CONTENTS INTRODUCTION.8 1 Scope.9 1.1 General .9 1.2 Specifications9 1.3 Procedures9 1.4 Applica
20、bility.91.5 Conformance.9 2 Normative references .10 3 Terms, definitions, symbols, abbreviations and conventions .10 3.1 Reference model terms and definitions10 3.2 Service convention terms and definitions.12 3.3 Other terms and definitions .13 3.4 Abbreviations 17 3.5 Symbols 19 3.6 DLPDU IDN conc
21、ept20 4 DL-protocol overview20 5 Basic DLPDU structure.21 5.1 Overview .21 5.2 MST DLPDU22 5.3 MDT DLPDU .23 5.4 AT DLPDU 30 6 Network management methods.37 6.1 Overview .37 6.2 Enable and disable cyclic communication37 6.3 File transfer.42 6.4 Status procedures .43 7 Data transmission methods 43 7.
22、1 Overview .43 7.2 SVC 43 7.3 RTC 55 8 DL management .56 8.1 Overview .56 8.2 Access to PhL .56 9 Error handling and monitoring 61 9.1 Invalid telegrams.61 9.2 Response to MDT and AT telegram failure 62 9.3 Reaction to handshake timeout .63 9.4 Service channel error messages64 9.5 Reaction to error
23、messages in the service channel66 9.6 Error counters in the master and the slave 66 9.7 Error effects on communication phases .68 9.8 Monitoring in the master68 9.9 Monitoring in the slave 69 Annex A (normative) IDN Identification numbers .71 A.1 IDN specification .71 BS EN 61158-4-16:2008 3 A.2 Ide
24、ntification numbers in numerical orders 78 A.3 Detailed specification of communication-related IDNs .79 Bibliography107 Figure 1 Relationships of DLSAPs, DLSAP-addresses and group DL-addresses15 Figure 2 Master service INFO field k 25 Figure 3 Structure of the master data telegram 26 Figure 4 Device
25、 service INFO field m.31 Figure 5 Timing of U/D bits in CP5.35 Figure 6 Timing of U/D bits in CP6.37 Figure 7 Switching to CP042 Figure 8 Phase transitions .42 Figure 9 Service channel handling diagram45 Figure 10 Communication step proceeding diagram .47 Figure 11 State machine for procedure comman
26、d execution 52 Figure 12 Interaction of procedure command control and acknowledgement 53 Figure 13 Procedure command execution without interrupt 54 Figure 14 Procedure command execution with interrupt .54 Figure 15 Procedure command execution with error message55 Figure 16 Access to the transfer med
27、ium .57 Figure 17 Timing diagram for CP0 .58 Figure 18 Telegram transmission starting times of CP1 and CP2 .58 Figure 19 Timing diagram for cyclic operation 59 Figure 20 Telegram transmission times in CP5 60 Figure 21 Telegram transmission times in CP6 60 Figure 22 Required time intervals between te
28、legrams 61 Figure A.1 General IDN structure.72 Figure A.2 IDN name structure.72 Figure A.3 IDN data unit structure75 Figure A.4 Structure of IDN operation data with variable length .76 Figure A.5 Example of the structure of an IDN-list77 Figure A.6 SLKN example94 Table 1 General telegram structure21
29、 Table 2 BOF field.21 Table 3 Device address field22 Table 4 FCS field.22 Table 5 Master synchronization telegram structure 22 Table 6 MST INFO field .23 Table 7 Data fields of the master data telegram .23 Table 8 Master real-time data (for each device) .24 Annex ZA (normative) Normative references
30、to international publications with their corresponding European publications 108 BS EN 61158-4-16:2008 4 Table 11 Structure of MDT in CP5 .26 Table 12 Structure of Data Record in MDT in CP5 .27 Table 13 File block size in CP527 Table 14 U/D control word in CP5 27 Table 15 Structure of MDT in CP6 .28
31、 Table 16 Structure of data record field in MDT in CP6 .29 Table 17 U/D control word in CP6 29 Table 18 Data field of the acknowledge telegram .30 Table 19 AT real-time data (for each device).30 Table 20 Status word description (DLL) .31 Table 21 Structure of the ID acknowledge telegram in CP132 Tab
32、le 22 Structure of the operation data of device m in acknowledge telegram32 Table 23 Structure of AT in CP5 33 Table 24 Structure of data record in AT in CP5 33 Table 25 U/D status word in CP5 .33 Table 26 File block index in CP534 Table 27 Structure of AT in CP6 35 Table 28 Structure of data record
33、 in AT in CP6 35 Table 29 File block size in CP635 Table 30 U/D status word in CP6 .36 Table 31 File block index in CP637 Table 32 List of IDNs element and step numbers .46 Table 33 Condition for modifying data block elements46 Table 34 SVC channel evaluation 48 Table 35 IDN for list transfer 49 Tab
34、le 36 Procedure command control49 Table 37 Procedure command acknowledgment (data status) 50 Table 38 Allowed jitter .57 Table 39 Jitter in t259 Table 40 Jitter in t160 Table 41 Loss or failure of master synchronization telegram (MST) .62 Table 42 Failure of master data telegrams (MDT) 63 Table 43 F
35、ailure of acknowledge telegrams (AT)63 Table 44 Reaction to handshake timeout .63 Table 45 Error messages.64 Table 46 Reaction to error message 66 Table 47 States of error counters 1 in the master for MST and AT failures.66 Table 48 States of error counter 1 in the devices for MST-failures in CP3 an
36、d CP4 .66 Table 49 States of error counter 1 in the devices for MDT-failures in CP466 Table 50 States of error counters 2 in the master for AT-failures67 Table 51 States of error counter 2 in the devices for MST-failures .67 Table 9 Control word description (DLL)24 Table 10 Structure of the ID reque
37、st telegram in CP1 25 BS EN 61158-4-16:2008 5 Table 54 Slave monitoring .70 Table A.1 Data block structure.71 Table A.2 IDN structure .72 Table A.3 Element 3 of IDNs73 Table A.4 Valid combinations of the display formats 74 Table A.5 Data status structure78 Table A.6 Communication related IDN list th
38、at are relevant for Type 16 .78 Table A.7 Attributes for IDN S-0-000180 Table A.8 Attributes for IDN S-0-000280 Table A.9 Attributes for IDN S-0-000381 Table A.10 Attributes for IDN S-0-0004 81 Table A.11 Attributes for IDN S-0-0006 82 Table A.12 Attributes for IDN S-0-0008 82 Table A.13 Attributes
39、for IDN S-0-0009 83 Table A.14 Attributes for IDN S-0-0010 83 Table A.15 Attributes for IDN S-0-0011 84 Table A.16 Structure of C1D 84 Table A.17 Attributes for IDN S-0-0014 85 Table A.18 Structure of interface status .85 Table A.19 Attributes for IDN S-0-0015 86 Table A.20 Structure of telegram typ
40、e parameter .87 Table A.21 Attributes for IDN S-0-0016 87 Table A.22 Attributes for IDN S-0-0018 88 Table A.23 Attributes for IDN S-0-0019 88 Table A.24 Attributes for IDN S-0-0021 89 Table A.25 Attributes for IDN S-0-0022 89 Table A.26 Attributes for IDN S-0-0024 90 Table A.27 Attributes for IDN S-
41、0-0028 90 Table A.28 Attributes for IDN S-0-0029 91 Table A.29 Attributes for IDN S-0-0087 91 Table A.30 Attributes for IDN S-0-0088 92 Table A.31 Attributes for IDN S-0-0089 92 Table A.32 Attributes for IDN S-0-0090 93 Table A.33 Attributes for IDN S-0-0096 93 Table A.34 Structure of SLKN 94 Table
42、A.35 Attributes for IDN S-0-0097 94 Table A.36 Structure of Mask C2D .95 Table A.37 Attributes for IDN S-0-0098 95 Table A.38 Structure of Mask C3D .95 Table A.39 Attributes for IDN S-0-0127 96 Table A.40 Attributes for IDN S-0-0128 96 Table 52 States of error counter 2 in the devices for MDT-failur
43、es .68 Table 53 Master monitoring69 BS EN 61158-4-16:2008 6 Table A.43 Attributes for IDN S-0-0143 98 Table A.44 Structure of Type 16 version 98 Table A.45 Attributes for IDN S-0-0185 99Table A.46 Attributes for IDN S-0-0186 99 Table A.47 Attributes for IDN S-0-0187 100 Table A.48 Attributes for IDN
44、 S-0-0188 100 Table A.49 Attributes for IDN S-0-0301 101 Table A.50 Attributes for IDN S-0-0303 101 Table A.51 Attributes for IDN S-0-0305 102 Table A.52 Attributes for IDN S-0-0307 102 Table A.53 Attributes for IDN S-0-0394 103 Table A.54 Attributes for IDN S-0-0395 103 Table A.55 Attributes for ID
45、N S-0-0396 104 Table A.56 Attributes for IDN S-0-0397 104 Table A.57 Attributes for IDN S-0-0413 105 Table A.58 Attributes for IDN S-0-0414 105 Table A.59 Attributes for IDN S-0-0415 106 Table A.60 Attributes for IDN S-0-0416 106 Table A.41 Attributes for IDN S-0-0134 97 Table A.42 Attributes for ID
46、N S-0-0135 97 BS EN 61158-4-16:2008 7 INTRODUCTION This part of IEC 61158 is one of a series produced to facilitate the interconnection of automation system components. It is related to other standards in the set as defined by the “three-layer” fieldbus reference model described in IEC/TR 61158-1. T
47、he data-link protocol provides the data-link service by making use of the services available from the physical layer. The primary aim of this standard is to provide a set of rules for communication expressed in terms of the procedures to be carried out by peer data-link entities (DLEs) at the time o
48、f communication. These rules for communication are intended to provide a sound basis for development in order to serve a variety of purposes: a) as a guide for implementors and designers; b) for use in the testing and procurement of equipment; c) as part of an agreement for the admittance of systems into the open systems environment; d) as a refinement to the understanding of time-critical communications within OSI. This standard is concerned, in particular, with the communication and interworking of sensors, effectors and other automation devi
