{"id":244312,"date":"2024-10-19T16:02:56","date_gmt":"2024-10-19T16:02:56","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61158-4-42014\/"},"modified":"2024-10-25T11:01:52","modified_gmt":"2024-10-25T11:01:52","slug":"bs-en-61158-4-42014","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61158-4-42014\/","title":{"rendered":"BS EN 61158-4-4:2014"},"content":{"rendered":"
The data-link layer provides basic time-critical messaging communications between devices in an automation environment.<\/p>\n
This protocol provides a means of connecting devices through a partial mesh network, such that most failures of an interconnection between two devices can be circumvented. In common practice the devices are interconnected in a non-redundant hierarchical manner reflecting application needs<\/p>\n
This standard specifies<\/p>\n
procedures for the timely transfer of data and control information from one data-link user entity to a peer user entity, and among the data-link entities forming the distributed data-link service provider;<\/p>\n<\/li>\n
the structure of the fieldbus DLPDUs used for the transfer of data and control information by the protocol of this standard, and their representation as physical interface data units.<\/p>\n<\/li>\n<\/ol>\n
The procedures are defined in terms of<\/p>\n
the interactions between peer DL-entities (DLEs) through the exchange of fieldbus DLPDUs;<\/p>\n<\/li>\n
the interactions between a DL-service (DLS) provider and a DLS-user in the same system through the exchange of DLS primitives;<\/p>\n<\/li>\n
the interactions between a DLS-provider and a Ph-service provider in the same system through the exchange of Ph-service primitives.<\/p>\n<\/li>\n<\/ol>\n
These procedures are applicable to instances of communication between systems which support time-critical communications services within the data-link layer of the OSI or fieldbus reference models, and which require the ability to interconnect in an open systems interconnection environment.<\/p>\n
Profiles provide a simple multi-attribute means of summarizing an implementation\u2019s capabilities, and thus its applicability to various time-critical communications needs.<\/p>\n
This standard also specifies conformance requirements for systems implementing these procedures. This standard does not contain tests to demonstrate compliance with such requirements.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
6<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
8<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | 1 Scope 1.1 General 1.2 Specifications 1.3 Procedures 1.4 Applicability 1.5 Conformance <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 2 Normative references 3 Terms, definitions, symbols and abbreviations 3.1 Reference model terms and definitions <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 3.2 Service convention terms and definitions <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 3.3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 3.4 Symbols and abbreviations 4 Data Link Protocol Definition 4.1 Overview of the DLprotocol <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | Figures Figure 1 \u2013 Relationship of PhE, DLE and DLS-user <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | Figure 2 \u2013 DLE state diagram for confirmed and unconfirmed, unacknowledged DLPDUs <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | Figure 3 \u2013 DLE state diagram for confirmed acknowledged DLPDUs <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | Figure 4 \u2013 DLE state diagram for unconfirmed acknowledged DLPDUs <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | Figure 5 \u2013 Full duplex DLE receive state diagram Figure 6 \u2013 Full duplex DLE transmit state diagram <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | Figure 7 \u2013 Link access example <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 4.2 General structure and encoding of PhIDUs and DLPDUs, and related elements of procedure <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | Figure 8 \u2013 Simple Type\u00a04-route format Figure 9 \u2013 Extended Type\u00a04-route format <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | Figure 10 \u2013 Complex Type\u00a04-route format Figure 11 \u2013 Immediate Type\u00a04-route format <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | Figure 12 \u2013 IP Type\u00a04-route format <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Figure 13 \u2013 Control-status format Figure 14 \u2013 Data-field-format <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 4.3 DLPDU-specific structure, encoding and elements of procedure Tables Table 1 \u2013 Summary structure of DLPDUs <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Table 2 \u2013 Structure of confirmed DLPDUs <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Table 3 \u2013 Structure of unconfirmed DLPDUs <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | Table 4 \u2013 Structure of acknowledge DLPDU Table 5 \u2013 Structure of immediate-reply DLPDU <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 4.4 DLservice elements of procedure <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 4.5 Route mechanism <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure 15 \u2013 Source \/ destination designator Figure 16 \u2013 Simple Type\u00a04-route generation Figure 17 \u2013 Extended Type\u00a04-route generation <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Figure 18 \u2013 Complex and IP Type\u00a04-route generation Figure 19 \u2013 Simple DLroute generation <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 4.6 Link-access system Figure 20 \u2013 Extended DLroute generation Figure 21 \u2013 Complex and IP DLroute generation <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | 4.7 Local variables, counters and queues <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Fieldbus specifications – Data-link layer protocol specification. Type 4 elements<\/b><\/p>\n |