IEC 61158-4-4:2019 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 and 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. This third edition cancels and replaces the second edition published in 2014 and constitutes a technical revision. The main changes include the following significant technical changes with respect to the previous edition: lt;br \/gt;a) additional user parameters to services; lt;br \/gt;b) additional services to support distributed objects;c) additional secure services<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 52<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 55<\/td>\n | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
| 59<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
| 61<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
| 62<\/td>\n | 1 Scope 1.1 General 1.2 Specifications 1.3 Procedures 1.4 Applicability 1.5 Conformance <\/td>\n<\/tr>\n | ||||||
| 63<\/td>\n | 2 Normative references 3 Terms, definitions, symbols and abbreviations 3.1 Reference model terms and definitions <\/td>\n<\/tr>\n | ||||||
| 65<\/td>\n | 3.2 Service convention terms and definitions <\/td>\n<\/tr>\n | ||||||
| 66<\/td>\n | 3.3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 69<\/td>\n | 3.4 Symbols and abbreviations 3.4.1 Constants, variables, counters and queues 3.4.2 Miscellaneous 4 Data Link Protocol Definition 4.1 Overview of the DLprotocol <\/td>\n<\/tr>\n | ||||||
| 70<\/td>\n | 4.1.1 Functional classes 4.1.2 Functions of the DLL Figures Figure 1 \u2013 Relationship of PhE, DLE and DLS-user <\/td>\n<\/tr>\n | ||||||
| 72<\/td>\n | Figure 2 \u2013 DLE state diagram for confirmed and unconfirmed, unacknowledged DLPDUs <\/td>\n<\/tr>\n | ||||||
| 73<\/td>\n | Figure 3 \u2013 DLE state diagram for confirmed acknowledged DLPDUs <\/td>\n<\/tr>\n | ||||||
| 74<\/td>\n | Figure 4 \u2013 DLE state diagram for unconfirmed acknowledged DLPDUs <\/td>\n<\/tr>\n | ||||||
| 75<\/td>\n | Figure 5 \u2013 Full duplex DLE receive state diagram Figure 6 \u2013 Full duplex DLE transmit state diagram <\/td>\n<\/tr>\n | ||||||
| 78<\/td>\n | Figure 7 \u2013 Link access example <\/td>\n<\/tr>\n | ||||||
| 79<\/td>\n | 4.1.3 Service assumed from the PhL <\/td>\n<\/tr>\n | ||||||
| 81<\/td>\n | 4.2 General structure and encoding of PhIDUs and DLPDUs, and related elements of procedure 4.2.1 PhIDU structure and encoding <\/td>\n<\/tr>\n | ||||||
| 82<\/td>\n | 4.2.2 Frame check sequence <\/td>\n<\/tr>\n | ||||||
| 83<\/td>\n | 4.2.3 Common DLPDU structure, encoding and elements of procedure <\/td>\n<\/tr>\n | ||||||
| 84<\/td>\n | Figure 8 \u2013 Simple Type 4-route format Figure 9 \u2013 Extended Type 4-route format <\/td>\n<\/tr>\n | ||||||
| 85<\/td>\n | Figure 10 \u2013 Complex Type 4-route format Figure 11 \u2013 Immediate Type 4-route format <\/td>\n<\/tr>\n | ||||||
| 86<\/td>\n | Figure 12 \u2013 IP Type 4-route format <\/td>\n<\/tr>\n | ||||||
| 87<\/td>\n | Figure 13 \u2013 Control-status format Figure 14 \u2013 Data-field-format <\/td>\n<\/tr>\n | ||||||
| 88<\/td>\n | 4.3 DLPDU-specific structure, encoding and elements of procedure 4.3.1 Confirmed DLPDU Tables Table 1 \u2013 Summary structure of DLPDUs <\/td>\n<\/tr>\n | ||||||
| 89<\/td>\n | 4.3.2 Unconfirmed DLPDU Table 2 \u2013 Structure of confirmed DLPDUs <\/td>\n<\/tr>\n | ||||||
| 90<\/td>\n | Table 3 \u2013 Structure of unconfirmed DLPDUs <\/td>\n<\/tr>\n | ||||||
| 91<\/td>\n | 4.3.3 Acknowledge DLPDU 4.3.4 Immediate-reply DLPDU Table 4 \u2013 Structure of acknowledge DLPDU Table 5 \u2013 Structure of immediate-reply DLPDU <\/td>\n<\/tr>\n | ||||||
| 92<\/td>\n | 4.4 DLservice elements of procedure 4.4.1 Receipt of a DLUnitdata request primitive <\/td>\n<\/tr>\n | ||||||
| 93<\/td>\n | 4.4.2 Receipt of a DLUnitdata response primitive <\/td>\n<\/tr>\n | ||||||
| 94<\/td>\n | 4.4.3 Autonomous DLE acknowledge 4.4.4 Generation of a DLUnitdata indication primitive <\/td>\n<\/tr>\n | ||||||
| 95<\/td>\n | 4.5 Route mechanism 4.5.1 Request Type 4-route generation <\/td>\n<\/tr>\n | ||||||
| 96<\/td>\n | Figure 15 \u2013 Source \/ destination designator Figure 16 \u2013 Simple Type 4-route generation Figure 17 \u2013 Extended Type 4-route generation <\/td>\n<\/tr>\n | ||||||
| 97<\/td>\n | 4.5.2 DLroute generation Figure 18 \u2013 Complex and IP Type 4-route generation Figure 19 \u2013 Simple DLroute generation <\/td>\n<\/tr>\n | ||||||
| 98<\/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 | ||||||
| 99<\/td>\n | 4.7 Local variables, counters and queues 4.7.1 V(ACPDU) \u2013 acknowledge confirmed PDU 4.7.2 V(AUPDU) \u2013 acknowledge unconfirmed PDU 4.7.3 V(NA) \u2013 node-address 4.7.4 V(NDLE) \u2013 number of DLEs 4.7.5 V(PNR) \u2013 permitted number of retries 4.7.6 V(DC) \u2013 device class (simple or normal) 4.7.7 V(BR) \u2013 bit rate 4.7.8 V(MID) \u2013 max indication delay <\/td>\n<\/tr>\n | ||||||
| 100<\/td>\n | 4.7.9 V(DMRT) \u2013 default max retry time 4.7.10 Q(UR) \u2013 user request queue 4.7.11 C(LAC) \u2013 link access counter 4.7.12 C(LIC) \u2013 link idle counter <\/td>\n<\/tr>\n | ||||||
| 101<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Tracked Changes. Industrial communication networks. Fieldbus specifications – Data-link layer protocol specification. Type 4 elements<\/b><\/p>\n |