《BS EN 61158-4-16-2008 工业通讯网络.现场总线规范.数据链路层协议规范.16型元件.pdf》由会员分享，可在线阅读，更多相关《BS EN 61158-4-16-2008 工业通讯网络.现场总线规范.数据链路层协议规范.16型元件.pdf（112页珍藏版）》请在三一文库上搜索。
1、BRITISH STANDARD BS EN 61158-4-16:2008 Industrial communication networks Fieldbus specifications Part 4-16: Data-link layer protocol specification Type 16 elements ICS 25.040.40; 35.100.20 BS EN 61158-4-16:2008 This British Standard was published under the authority of the Standards Policy and Strat
2、egy Committee on 30 May 2008 BSI 2008 ISBN 978 0 580 61584 9 National foreword This British Standard is the 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
3、. Together with BS EN 61158-2, BS EN 61158-3-16, BS EN 61158-5-16 and BS EN 61158-6-16, it partially supersedes 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 prepa
4、ration was entrusted to Technical Committee AMT/7, Industrial communications Process measurement and control, 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 provisio
5、ns of a contract. Users are responsible for its correct application. Compliance with a British Standard cannot confer immunity from legal obligations. Amendments/corrigenda issued since publication DateComments EUROPEAN STANDARD EN 61158-4-16 NORME EUROPENNE EUROPISCHE NORM February 2008 CENELEC Eur
6、opean Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches 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 f
7、or CENELEC members. Ref. No. EN 61158-4-16:2008 E ICS 35.100.20; 25.040.40 Partially supersedes EN 61158-4:2004 and EN 61491:1998 English version Industrial communication networks - Fieldbus specifications - Part 4-16: Data-link layer protocol specification - Type 16 elements (IEC 61158-4-16:2007) R
8、seaux de communication industriels - Spcifications des bus de terrain - Partie 4-16: Spcification des protocoles 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 (Sicherung
9、sschicht) - Typ 16-Elemente (IEC 61158-4-16:2007) This European Standard was approved by CENELEC on 2008-02-01. 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
10、 alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained 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
11、 by translation under the responsibility of a CENELEC member into its own language and notified to the Central 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, Es
12、tonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, 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
13、IEC 61158-4-16, prepared by SC 65C, Industrial networks, of IEC TC 65, Industrial-process measurement, control 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 611
14、58-4:2004. Together with EN 61158-2:2008 and its companion parts for Type 16, it also partially replaces EN 61491: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 placeho
15、lder for a Type 5 fieldbus data-link layer, for lack of market relevance; addition of new fieldbus types; partition 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 nation
16、al standard or by endorsement (dop) 2008-11-01 latest date by which the national standards conflicting with the 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 limit
17、ed release of intellectual-property-rights made by the holders of those rights permits a particular data-link layer 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 o
18、ther combinations may require permission from their respective intellectual-property-right holders. Annex ZA has 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 611
19、58-4-16:2008 2 CONTENTS INTRODUCTION. 1 Scope. 1.1 General . 1.2 Specifications. 1.3 Procedures. 1.4 Applicability. 1.5 Conformance. 2 Normative references .1 3 Terms, definitions, symbols, abbreviations and conventions .1 3.1 Reference model terms and definitions1 3.2 Service convention terms and d
20、efinitions.1 3.3 Other terms and definitions .1 3.4 Abbreviations 1 3.5 Symbols 3.6 DLPDU IDN concept2 4 DL-protocol overview2 5 Basic DLPDU structure.2 5.1 Overview.2 5.2 MST DLPDU2 5.3 MDT DLPDU .2 5.4 AT DLPDU 3 6 Network management methods.3 6.1 Overview.3 6.2 Enable and disable cyclic communica
21、tion3 6.3 File transfer.4 6.4 Status procedures .4 7 Data transmission methods 4 7.1 Overview.4 7.2 SVC 4 7.3 RTC 5 8 DL management .5 8.1 Overview.5 8.2 Access to PhL .5 9 Error handling and monitoring 9.1 Invalid telegrams.6 9.2 Response to MDT and AT telegram failure 6 9.3 Reaction to handshake t
22、imeout .6 9.4 Service channel error messages6 9.5 Reaction to error messages in the service channel6 9.6 Error counters in the master and the slave 6 9.7 Error effects on communication phases .6 9.8 Monitoring in the master6 9.9 Monitoring in the slave Annex A (normative) IDN Identification numbers
23、.7 A.1 IDN specification .7 BS EN 61158-4-16:2008 3 A.2 Identification numbers in numerical orders 7 A.3 Detailed specification of communication-related IDNs . Bibliography10 Figure 1 Relationships of DLSAPs, DLSAP-addresses and group DL-addresses1 Figure 2 Master service INFO field k2 Figure 3 Stru
24、cture of the master data telegram 2 Figure 4 Device service INFO field m.3 Figure 5 Timing of U/D bits in CP5.3 Figure 6 Timing of U/D bits in CP6.3 Figure 7 Switching to CP04 Figure 8 Phase transitions .4 Figure 9 Service channel handling diagram4 Figure 10 Communication step proceeding diagram.4 F
25、igure 11 State machine for procedure command execution 5 Figure 12 Interaction of procedure command control and acknowledgement 5 Figure 13 Procedure command execution without interrupt 5 Figure 14 Procedure command execution with interrupt .5 Figure 15 Procedure command execution with error message
26、5 Figure 16 Access to the transfer medium .5 Figure 17 Timing diagram for CP0 .5 Figure 18 Telegram transmission starting times of CP1 and CP2 .5 Figure 19 Timing diagram for cyclic operation Figure 20 Telegram transmission times in CP5 6 Figure 21 Telegram transmission times in CP6 6 Figure 22 Requ
27、ired time intervals between telegrams 6 Figure A.1 General IDN structure.7 Figure A.2 IDN name structure.7 Figure A.3 IDN data unit structure7 Figure A.4 Structure of IDN operation data with variable length .7 Figure A.5 Example of the structure of an IDN-list7 Figure A.6 SLKN example9 Table 1 Gener
28、al telegram structure2 Table 2 BOF field.2 Table 3 Device address field2 Table 4 FCS field.2 Table 5 Master synchronization telegram structure 2 Table 6 MST INFO field .2 Table 7 Data fields of the master data telegram .2 Table 8 Master real-time data (for each device) .2 - - - - BS EN 61158-4-16:20
29、08 4 Table 11 Structure of MDT in CP5 .2 Table 12 Structure of Data Record in MDT in CP5 .2 Table 13 File block size in CP52 Table 14 U/D control word in CP5 2 Table 15 Structure of MDT in CP6 .2 Table 16 Structure of data record field in MDT in CP6 . Table 17 U/D control word in CP6 Table 18 Data f
30、ield of the acknowledge telegram.3 Table 19 AT real-time data (for each device).3 Table 20 Status word description (DLL) .3 Table 21 Structure of the ID acknowledge telegram in CP13 Table 22 Structure of the operation data of device m in acknowledge telegram3 Table 23 Structure of AT in CP5 3 Table
31、24 Structure of data record in AT in CP53 Table 25 U/D status word in CP5 .3 Table 26 File block index in CP53 Table 27 Structure of AT in CP6 3 Table 28 Structure of data record in AT in CP63 Table 29 File block size in CP63 Table 30 U/D status word in CP6 .3 Table 31 File block index in CP63 Table
32、 32 List of IDNs element and step numbers .4 Table 33 Condition for modifying data block elements4 Table 34 SVC channel evaluation 4 Table 35 IDN for list transfer Table 36 Procedure command control Table 37 Procedure command acknowledgment (data status) 5 Table 38 Allowed jitter .5 Table 39 Jitter
33、in t2 Table 40 Jitter in t16 Table 41 Loss or failure of master synchronization telegram (MST) .6 Table 42 Failure of master data telegrams (MDT) 6 Table 43 Failure of acknowledge telegrams (AT)6 Table 44 Reaction to handshake timeout .6 Table 45 Error messages.6 Table 46 Reaction to error message 6
34、 Table 47 States of error counters 1 in the master for MST and AT failures.6 Table 48 States of error counter 1 in the devices for MST-failures in CP3 and CP4 .6 Table 49 States of error counter 1 in the devices for MDT-failures in CP46 Table 50 States of error counters 2 in the master for AT-failur
35、es6 Table 51 States of error counter 2 in the devices for MST-failures .6 Table 9 Control word description (DLL)2 Table 10 Structure of the ID request telegram in CP1 2 BS EN 61158-4-16:2008 5 Table 54 Slave monitoring .7 Table A.1 Data block structure.7 Table A.2 IDN structure .7 Table A.3 Element
36、3 of IDNs7 Table A.4 Valid combinations of the display formats 7 Table A.5 Data status structure7 Table A.6 Communication related IDN list that are relevant for Type 16.7 Table A.7 Attributes for IDN S-0-00018 Table A.8 Attributes for IDN S-0-00028 Table A.9 Attributes for IDN S-0-00038 Table A.10 A
37、ttributes for IDN S-0-00048 Table A.11 Attributes for IDN S-0-00068 Table A.12 Attributes for IDN S-0-00088 Table A.13 Attributes for IDN S-0-00098 Table A.14 Attributes for IDN S-0-00108 Table A.15 Attributes for IDN S-0-00118 Table A.16 Structure of C1D 8 Table A.17 Attributes for IDN S-0-00148 Ta
38、ble A.18 Structure of interface status .8 Table A.19 Attributes for IDN S-0-00158 Table A.20 Structure of telegram type parameter .8 Table A.21 Attributes for IDN S-0-00168 Table A.22 Attributes for IDN S-0-00188 Table A.23 Attributes for IDN S-0-00198 Table A.24 Attributes for IDN S-0-0021 Table A.
39、25 Attributes for IDN S-0-0022 Table A.26 Attributes for IDN S-0-00249 Table A.27 Attributes for IDN S-0-00289 Table A.28 Attributes for IDN S-0-00299 Table A.29 Attributes for IDN S-0-00879 Table A.30 Attributes for IDN S-0-00889 Table A.31 Attributes for IDN S-0-00899 Table A.32 Attributes for IDN
40、 S-0-00909 Table A.33 Attributes for IDN S-0-00969 Table A.34 Structure of SLKN 9 Table A.35 Attributes for IDN S-0-00979 Table A.36 Structure of Mask C2D.9 Table A.37 Attributes for IDN S-0-00989 Table A.38 Structure of Mask C3D.9 Table A.39 Attributes for IDN S-0-01279 Table A.40 Attributes for ID
41、N S-0-01289 Table 52 States of error counter 2 in the devices for MDT-failures .6 Table 53 Master monitoring BS EN 61158-4-16:2008 6 Table A.43 Attributes for IDN S-0-01439 Table A.44 Structure of Type 16 version 9 Table A.45 Attributes for IDN S-0-0185 Table A.46 Attributes for IDN S-0-0186 Table A
42、.47 Attributes for IDN S-0-018710 Table A.48 Attributes for IDN S-0-018810 Table A.49 Attributes for IDN S-0-030110 Table A.50 Attributes for IDN S-0-030310 Table A.51 Attributes for IDN S-0-030510 Table A.52 Attributes for IDN S-0-030710 Table A.53 Attributes for IDN S-0-039410 Table A.54 Attribute
43、s for IDN S-0-039510 Table A.55 Attributes for IDN S-0-039610 Table A.56 Attributes for IDN S-0-039710 Table A.57 Attributes for IDN S-0-041310 Table A.58 Attributes for IDN S-0-041410 Table A.59 Attributes for IDN S-0-041510 Table A.60 Attributes for IDN S-0-041610 Table A.41 Attributes for IDN S-0
44、-01349 Table A.42 Attributes for IDN S-0-01359 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 mod
45、el described in IEC/TR 61158-1. The 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-l
46、ink entities (DLEs) at the time of 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 agreem
47、ent 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 devices. By using this standard together with other standards positioned within the OSI or fieldbus reference models, otherwise incompatible systems may work together in any combination. BS EN 61158-4-