🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS EN IEC 61158-4-28:2023

BS EN IEC 61158-4-28:2023

$198.66

Industrial communication networks. Fieldbus specifications – Data-link layer protocol specification. Type 28 elements

Published By Publication Date Number of Pages
BSI 2023 60
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

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.

PDF Catalog

PDF Pages PDF Title
2 undefined
5 Annex ZA (normative)Normative references to international publicationswith their corresponding European publications
6 Blank Page
7 English
CONTENTS
10 FOREWORD
12 INTRODUCTION
13 1 Scope
1.1 General
1.2 Specifications
1.3 Procedures
1.4 Applicability
1.5 Conformance
14 2 Normative references
3 Terms, definitions, symbols, abbreviated terms and conventions
3.1 Reference model terms and definitions
16 3.2 Service convention terms and definitions
17 3.3 Common terms and definitions
Figures
Figure 1 – Relationships of DLSAPs, DLSAP-addresses and group DL-addresses
18 3.4 Additional Type 28 terms and definitions
20 3.5 Additional Type 28 symbols and abbreviations
Figure 2 – Bitmap data type diagram
21 4 Overview of the DL-protocol
4.1 DLL protocol architecture
Figure 3 – DLL in Type 28 protocol stack architecture
22 Figure 4 – Relationship of the fieldbus DLL to other fieldbus layers and to users of the fieldbus DLS
Figure 5 – Type 28 DLL protocol architecture diagram
23 4.2 DLL working mechanism
4.2.1 Node
4.2.2 Addressing
Tables
Table 1 – NodeID address assignment of Type 28 DLL
Table 2 – NodeID and MAC address mapping table
24 4.2.3 Multicast
4.2.4 Resource mapping and scheduling
Table 3 – Members of multicast group mapping table
25 Figure 6 – Resource mapping between DLL and PhL
26 5 DLPDU structure
5.1 Universal DLPDU structure
Figure 7 – DLL resource mapping message queue scheduling diagram
27 Figure 8 – Universal DLPDU structure
28 5.2 Basic configuration DLPDU
Figure 9 – Basic configuration DLPDU structure
29 Figure 10 – General configuration block structure
30 5.3 Address assignment DLPDU
5.4 Multicast assignment DLPDU
Figure 11 – Address allocation DLPDU structure
31 5.5 Resource allocation DLPDU
Figure 12 – Multicast assignment DLPDU structure
32 Figure 13 – Resource allocation DLPDU structure
33 5.6 Access notification DLPDU
Figure 14 – Access notification DLPDU structure
34 5.7 Resource application DLPDU
Figure 15 – Resource application DLPDU structure
35 5.8 Resource release DLPDU
5.9 Status query DLPDU
Figure 16 – Resource release DLPDU structure
36 5.10 Status response DLPDU
Figure 17 – Status query DLPDU structure
Figure 18 – Status response DLPDU structure
37 5.11 Announcement DLPDU
Figure 19 – Announcement DLPDU structure
38 5.12 Clock synchronization DLPDU
39 5.13 Common DLPDU
Figure 20 – Clock synchronization DLPDU structure
40 6 Working procedure
6.1 Initialization procedure
6.1.1 Basic configuration
6.1.2 Resource mapping configuration
Figure 21 – Common DLPDU structure
41 Figure 22 – Resource mapping configuration diagram
42 6.2 DLL node management procedure
6.2.1 DLL maintenance
Figure 23 – Initial access configuration procedure diagram
43 6.2.2 Node join
Figure 24 – The random access configuration procedure diagram
44 6.2.3 Node query
6.2.4 Node leave
45 6.3 Data transmission procedure
Figure 25 – Node leave procedure diagram
46 Figure 26 – DLS data sending procedure diagram
47 6.4 Clock synchronization procedure
Figure 27 – DLS data receiving procedure diagram
48 Figure 28 – Clock synchronization delay measurement procedure diagram
Figure 29 – Clock register structure diagram
49 7 State machine
7.1 DLDE state machine
Figure 30 – Clock synchronization procedure
50 Figure 31 – DLDE state machine
51 Table 4 – DLDE state transition
52 7.2 DLME state machine
Figure 32 – DLME state machine
53 7.3 DLCE state machine
Figure 33 – DLCE state machine
Table 5 – DLME state machine state transition
54 8 Error handling
8.1 General
8.2 Possible sources and characteristics of errors
Table 6 – DLCE state machine state transition
55 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
56 Annex A (informative)Example for NodeID and MAC address mapping
Table A.1 – Example of NodeID and MAC address mapping table saved on TN
57 Annex B(informative)Example for multicast group working mechanism
Figure B.1 – Multicast working mechanism diagram
58 Bibliography

Related products

BS EN IEC 61158-4-28:2023
$198.66