1.1 General This document of IEC 61158 describes basic packet communication services and models in an automation control industrial field environment. The Type 28 data-link layer provides time critical and non-time-critical communication services. Time-critical refers to the requirement to complete specified functions between devices in a defined time window in an industrial field environment. Failure to complete specified functions within the time window may lead to failure or harm in industrial production. This document defines in an abstract way the externally visible service provided by the Type 28 fieldbus data-link layer in terms of a) function description; b) primitive actions and events with primitive sequence diagram; c) the form of externally service interface and related parameters. The purpose of this document is to define the services provided to: – the Type 28 fieldbus application layer at the boundary between the application and data link layers of the fieldbus reference model; – systems management at the boundary between the data-link layer and systems management of the fieldbus reference model. Type 28 DL-service provides both a connected and a connectionless subset of those services provided by OSI data-link protocols as specified in ISO\/IEC 8886. 1.2 Specifications The principal objective of this document is to specify the characteristics of conceptual data-link layer services suitable for time-critical communications and thus supplement the OSI Basic Reference Model in guiding the development of data-link protocols for time-sensitive communications. A secondary objective is to provide migration paths from previously-existing industrial communications protocols. This specification may be used as the basis for formal DL-Programming-Interfaces. Nevertheless, it is not a formal programming interface, and any such interface will need to address implementation issues not covered by this specification, including: a) the sizes and octet ordering of various multi-octet service parameters; and b) the correlation of paired request and confirm, or indication and response primitives. 1.3 Conformance This document does not specify individual implementations or products, nor does it constrain the implementations of data-link entities within industrial automation systems. There is no conformance of equipment to this data-link layer service definition standard. Instead, conformance is achieved through implementation of the corresponding data-link protocol that fulfills the Type 28 data-link layer services defined in this document.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 5<\/td>\n | Annex ZA (normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n | ||||||
| 6<\/td>\n | Blank Page <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 1 Scope 1.1 General 1.2 Specifications 1.3 Procedures 1.4 Applicability 1.5 Conformance <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 2 Normative references 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Reference model terms and definitions <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 3.2 Service convention terms and definitions <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 3.3 Common terms and definitions Figures Figure 1 \u2013 Relationships of DLSAPs, DLSAP-addresses and group DL-addresses <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 3.4 Additional Type 28 terms and definitions <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 3.5 Additional Type 28 symbols and abbreviations Figure 2 \u2013 Bitmap data type diagram <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 4 Overview of the DL-protocol 4.1 DLL protocol architecture Figure 3 \u2013 DLL in Type 28 protocol stack architecture <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | Figure 4 \u2013 Relationship of the fieldbus DLL to other fieldbus layers and to users of the fieldbus DLS Figure 5 \u2013 Type 28 DLL protocol architecture diagram <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 4.2 DLL working mechanism 4.2.1 Node 4.2.2 Addressing Tables Table 1 \u2013 NodeID address assignment of Type 28 DLL Table 2 \u2013 NodeID and MAC address mapping table <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 4.2.3 Multicast 4.2.4 Resource mapping and scheduling Table 3 \u2013 Members of multicast group mapping table <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | Figure 6 \u2013 Resource mapping between DLL and PhL <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 5 DLPDU structure 5.1 Universal DLPDU structure Figure 7 \u2013 DLL resource mapping message queue scheduling diagram <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | Figure 8 \u2013 Universal DLPDU structure <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 5.2 Basic configuration DLPDU Figure 9 \u2013 Basic configuration DLPDU structure <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | Figure 10 \u2013 General configuration block structure <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 5.3 Address assignment DLPDU 5.4 Multicast assignment DLPDU Figure 11 \u2013 Address allocation DLPDU structure <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 5.5 Resource allocation DLPDU Figure 12 \u2013 Multicast assignment DLPDU structure <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | Figure 13 \u2013 Resource allocation DLPDU structure <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 5.6 Access notification DLPDU Figure 14 \u2013 Access notification DLPDU structure <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | 5.7 Resource application DLPDU Figure 15 \u2013 Resource application DLPDU structure <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | 5.8 Resource release DLPDU 5.9 Status query DLPDU Figure 16 \u2013 Resource release DLPDU structure <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 5.10 Status response DLPDU Figure 17 \u2013 Status query DLPDU structure Figure 18 \u2013 Status response DLPDU structure <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | 5.11 Announcement DLPDU Figure 19 \u2013 Announcement DLPDU structure <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 5.12 Clock synchronization DLPDU <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | 5.13 Common DLPDU Figure 20 \u2013 Clock synchronization DLPDU structure <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | 6 Working procedure 6.1 Initialization procedure 6.1.1 Basic configuration 6.1.2 Resource mapping configuration Figure 21 \u2013 Common DLPDU structure <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | Figure 22 \u2013 Resource mapping configuration diagram <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | 6.2 DLL node management procedure 6.2.1 DLL maintenance Figure 23 \u2013 Initial access configuration procedure diagram <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | 6.2.2 Node join Figure 24 \u2013 The random access configuration procedure diagram <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | 6.2.3 Node query 6.2.4 Node leave <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | 6.3 Data transmission procedure Figure 25 \u2013 Node leave procedure diagram <\/td>\n<\/tr>\n | ||||||
| 46<\/td>\n | Figure 26 \u2013 DLS data sending procedure diagram <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | 6.4 Clock synchronization procedure Figure 27 \u2013 DLS data receiving procedure diagram <\/td>\n<\/tr>\n | ||||||
| 48<\/td>\n | Figure 28 \u2013 Clock synchronization delay measurement procedure diagram Figure 29 \u2013 Clock register structure diagram <\/td>\n<\/tr>\n | ||||||
| 49<\/td>\n | 7 State machine 7.1 DLDE state machine Figure 30 \u2013 Clock synchronization procedure <\/td>\n<\/tr>\n | ||||||
| 50<\/td>\n | Figure 31 \u2013 DLDE state machine <\/td>\n<\/tr>\n | ||||||
| 51<\/td>\n | Table 4 \u2013 DLDE state transition <\/td>\n<\/tr>\n | ||||||
| 52<\/td>\n | 7.2 DLME state machine Figure 32 \u2013 DLME state machine <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | 7.3 DLCE state machine Figure 33 \u2013 DLCE state machine Table 5 \u2013 DLME state machine state transition <\/td>\n<\/tr>\n | ||||||
| 54<\/td>\n | 8 Error handling 8.1 General 8.2 Possible sources and characteristics of errors Table 6 \u2013 DLCE state machine state transition <\/td>\n<\/tr>\n | ||||||
| 55<\/td>\n | 8.3 Error handling of MN \/ TN 8.4 PhL error source 8.4.1 General 8.4.2 Lost connection 8.4.3 CRC error 8.4.4 Buffer overflow 8.4.5 Symbol resource conflict 8.4.6 Symbol resource insufficient <\/td>\n<\/tr>\n | ||||||
| 56<\/td>\n | Annex A (informative)Example for NodeID and MAC address mapping Table A.1 \u2013 Example of NodeID and MAC address mapping table saved on TN <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | Annex B(informative)Example for multicast group working mechanism Figure B.1 \u2013 Multicast working mechanism diagram <\/td>\n<\/tr>\n | ||||||
| 58<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Fieldbus specifications – Data-link layer protocol specification. Type 28 elements<\/b><\/p>\n |