BS EN 61158-4-3:2014
$215.11
Industrial communication networks. Fieldbus specifications – Data-link layer protocol specification. Type 3 elements
Published By | Publication Date | Number of Pages |
BSI | 2014 | 174 |
1.1 General
The data-link layer provides basic time-critical messaging communications between devices in an automation environment.
This protocol provides communication opportunities to a pre-selected “master” subset of data-link entities in a cyclic asynchronous manner, sequentially to each of those data-link entities. Other data-link entities communicate only as permitted and delegated by those master data-link entities.
For a given master, its communications with other data-link entities can be cyclic, or acyclic with prioritized access, or a combination of the two.
This protocol provides a means of sharing the available communication resources in a fair manner. There are provisions for time synchronization and for isochronous operation.
1.2 Specifications
This standard specifies
-
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;
-
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.
1.3 Procedures
The procedures are defined in terms of
-
the interactions between peer DL-entities (DLEs) through the exchange of fieldbus DLPDUs;
-
the interactions between a DL-service (DLS) provider and a DLS-user in the same system through the exchange of DLS primitives;
-
the interactions between a DLS-provider and a Ph-service provider in the same system through the exchange of Ph-service primitives.
1.4 Applicability
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.
Profiles provide a simple multi-attribute means of summarizing an implementation’s capabilities, and thus its applicability to various time-critical communications needs.
1.5 Conformance
This standard also specifies conformance requirements for systems implementing these procedures. This standard does not contain tests to demonstrate compliance with such requirements.
PDF Catalog
PDF Pages | PDF Title |
---|---|
6 | English CONTENTS |
10 | INTRODUCTION |
11 | 1 Scope 1.1 General 1.2 Specifications 1.3 Procedures 1.4 Applicability |
12 | 1.5 Conformance 2 Normative references 3 Terms, definitions, symbols and abbreviations 3.1 Reference model terms and definitions |
14 | 3.2 Service convention terms and definitions |
15 | 3.3 Common terms and definitions |
16 | Figures Figure 1 – Relationships of DLSAPs, DLSAP-addresses and group DLaddresses |
17 | 3.4 Additional Type 3 definitions |
19 | 3.5 Common symbols and abbreviations |
20 | 3.6 Type 3 symbols and abbreviations |
24 | 4 Common DLprotocol elements 4.1 Frame check sequence |
25 | Tables Table 1 – FCS length, polynomials and constants by Type 3 synchronous |
27 | 5 Overview of the DLprotocol 5.1 General 5.2 Overview of the medium access control and transmission protocol Table 2 – Characteristic features of the fieldbus data-link protocol |
28 | 5.3 Transmission modes and DLentity |
30 | Figure 2 – Logical token-passing ring |
33 | 5.4 Service assumed from the PhL |
34 | Figure 3 – PhL data service for asynchronous transmission |
37 | 5.5 Operational elements |
39 | Figure 4 – Idle time TID1 |
40 | Figure 5 – Idle time TID2 (SDN, CS) Figure 6 – Idle time TID2 (MSRD) |
41 | Figure 7 – Slot time TSL1 Figure 8 – Slot time TSL2 |
46 | Figure 9 – Slot time TSL1 Figure 10 – Slot time TSL2 |
52 | 5.6 Cycle and system reaction times Figure 11 – Token transfer period |
53 | Figure 12 – Message transfer period |
55 | 6 General structure and encoding of DLPDUs, and related elements of procedure 6.1 DLPDU granularity Figure 13 – UART character |
56 | 6.2 Length octet (LE, LEr) 6.3 Address octet Figure 14 – Octet structure Figure 15 – Length octet coding |
57 | Figure 16 – Address octet coding |
58 | Figure 17 – DAE/SAE octet in the DLPDU Figure 18 – Address extension octet |
59 | 6.4 Control octet (FC) |
60 | Figure 19 – FC octet coding for send/request DLPDUs Figure 20 – FC octet coding for acknowledgement or response DLPDUs |
61 | Table 3 – Transmission function code |
62 | Table 4 – FCB, FCV in responder |
63 | 6.5 DLPDU content error detection 6.6 DATA_UNIT Figure 21 – FCS octet coding |
64 | 6.7 Error control procedures Figure 22 – Data field Figure 23 – Ident user data |
65 | 7 DLPDU-specific structure, encoding and elements of procedure 7.1 DLPDUs of fixed length with no data field |
66 | Figure 24 – DLPDUs of fixed length with no data field |
67 | 7.2 DLPDUs of fixed length with data field Figure 25 – DLPDUs of fixed length with no data field |
68 | Figure 26 – DLPDUs of fixed length with data field Figure 27 – DLPDUs of fixed length with data field |
69 | 7.3 DLPDUs with variable data field length Figure 28 – DLPDUs with variable data field length |
70 | 7.4 Token DLPDU Figure 29 – DLPDUs with variable data field length Figure 30 – Token DLPDU |
71 | 7.5 ASP DLPDU 7.6 SYNCH DLPDU 7.7 Time Event (TE) DLPDU Figure 31 – Token DLPDU |
72 | 7.8 Clock Value (CV) DLPDU 7.9 Transmission procedures Figure 32 – Send/request DLPDU of fixed length with no data |
73 | Figure 33 – Token DLPDU and send/request DLPDU of fixed length with data Figure 34 – Send/request DLPDU with variable data field length |
74 | Figure 35 – Send/request DLPDU of fixed length with no data Figure 36 – Token DLPDU and send/request DLPDU of fixed length with data |
75 | 8 Other DLE elements of procedure 8.1 DLentity initialization Figure 37 – Send/request DLPDU with variable data field length Table 5 – Operating parameters |
76 | 8.2 States of the media access control of the DLentity |
77 | Figure 38 – DLstate-diagram |
82 | 8.3 Clock synchronization protocol |
83 | Figure 39 – Overview of clock synchronization |
84 | Figure 40 – Time master state machine |
85 | Figure 41 – Time receiver state machine |
86 | Figure 42 – Clock synchronization |
87 | Annex A (normative)DL-Protocol state machines A.1 Overall structure |
88 | A.2 Variation of state machines in different devices Figure A.1 – Structuring of the protocol machines |
89 | A.3 DL Data Resource Table A.1 – Assignment of state machines |
90 | Table A.2 – Data resource |
93 | A.4 FLC / DLM A.4.1 Primitive definitions Table A.3 – Primitives issued by DLUser to FLC |
94 | Table A.4 – Primitives issued by FLC to DLUser |
96 | Table A.5 – Primitives issued by DLUser to DLM Table A.6 – Primitives issued by DLM to DLUser |
97 | Table A.7 – Parameters used with primitives exchanged between DLUser and FLC Table A.8 – Parameters used with primitives exchanged between DLUser and DLM |
98 | A.4.2 State machine description Table A.9 – FLC/DLM state table |
110 | Table A.10 – FLC / DLM function table |
117 | A.5 MAC A.5.1 Primitive definitions A.5.2 State machine description Table A.11 – Primitives issued by DLM to MAC Table A.12 – Primitives issued by MAC to DLM Table A.13 – Parameters used with primitives exchanged between DLM and MAC |
118 | Table A.14 – Local MAC variables |
119 | Table A.15 – MAC state table |
139 | Table A.16 – MAC function table |
143 | A.6 SRU A.6.1 Overview |
144 | A.6.2 Character send SM(CTX) Figure A.2 – Structure of the SRU Machine |
145 | A.6.3 Character receive SM (CRX) A.6.4 Timer-SM (TIM) |
146 | A.6.5 Primitive definition of SRC Table A.17 – Primitives issued by DLM to SRC Table A.18 – Primitives issued by SRC to DLM Table A.19 – Primitives issued by MAC to SRC |
147 | A.6.6 State machine description Table A.20 – Primitives issued by SRC to MAC Table A.21 – Parameters used with primitives exchanged between MAC and SRC Table A.22 – FC structure |
148 | Table A.23 – Local variables of SRC |
149 | Table A.24 – SRC state table |
161 | Table A.25 – SRC functions |
162 | Annex B (informative)Type 3 (synchronous): exemplary FCS implementations Figure B.1 – Example of FCS generation for Type 3 (synchronous) Figure B.2 – Example of FCS syndrome checking on reception for Type 3 (synchronous) |
164 | Annex C (informative)Type 3: Exemplary token procedureand message transfer periods C.1 Procedure of token passing |
165 | C.2 Examples for token passing procedure Figure C.1 – Derivation of the token holding time (TTH) |
166 | Figure C.2 – No usage of token holding time (TTH) |
167 | Figure C.3 – Usage of token holding time (TTH) for message transfer (equivalence between TTH of each Master station) |
169 | Figure C.4 – Usage of token holding time (TTH) in different working load situations |
170 | C.3 Examples for message transfer periods – asynchronous transmission |
172 | Bibliography |