Shopping Cart

No products in the cart.

BS EN IEC 61158-4-4:2019

$198.66

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

Published By Publication Date Number of Pages
BSI 2019 52
Guaranteed Safe Checkout
Category:

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

The data-link layer provides basic time-critical messaging communications between devices in an automation environment.

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

1.2 Specifications

This document specifies

  1. 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 datalink service provider;

  2. the structure of the fieldbus DLPDUs used for the transfer of data and control information by the protocol of this document, and their representation as physical interface data units.

1.3 Procedures

The procedures are defined in terms of

  1. the interactions between peer DL-entities (DLEs) through the exchange of fieldbus DLPDUs;

  2. the interactions between a DL-service (DLS) provider and a DLS-user in the same system through the exchange of DLS primitives;

  3. 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 document also specifies conformance requirements for systems implementing these procedures. This document does not contain tests to demonstrate compliance with such requirements.

PDF Catalog

PDF Pages PDF Title
2 National foreword
5 Annex ZA(normative)Normative references to international publicationswith their corresponding European publications
7 CONTENTS
9 FOREWORD
11 INTRODUCTION
12 1 Scope
1.1 General
1.2 Specifications
1.3 Procedures
1.4 Applicability
1.5 Conformance
13 2 Normative references
3 Terms, definitions, symbols and abbreviations
3.1 Reference model terms and definitions
15 3.2 Service convention terms and definitions
16 3.3 Terms and definitions
19 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
20 4.1.1 Functional classes
4.1.2 Functions of the DLL
Figures
Figure 1 – Relationship of PhE, DLE and DLS-user
22 Figure 2 – DLE state diagram for confirmed and unconfirmed, unacknowledged DLPDUs
23 Figure 3 – DLE state diagram for confirmed acknowledged DLPDUs
24 Figure 4 – DLE state diagram for unconfirmed acknowledged DLPDUs
25 Figure 5 – Full duplex DLE receive state diagram
Figure 6 – Full duplex DLE transmit state diagram
28 Figure 7 – Link access example
29 4.1.3 Service assumed from the PhL
31 4.2 General structure and encoding of PhIDUs and DLPDUs, and related elements of procedure
4.2.1 PhIDU structure and encoding
32 4.2.2 Frame check sequence
33 4.2.3 Common DLPDU structure, encoding and elements of procedure
34 Figure 8 – Simple Type 4-route format
Figure 9 – Extended Type 4-route format
35 Figure 10 – Complex Type 4-route format
Figure 11 – Immediate Type 4-route format
36 Figure 12 – IP Type 4-route format
37 Figure 13 – Control-status format
Figure 14 – Data-field-format
38 4.3 DLPDU-specific structure, encoding and elements of procedure
4.3.1 Confirmed DLPDU
Tables
Table 1 – Summary structure of DLPDUs
39 4.3.2 Unconfirmed DLPDU
Table 2 – Structure of confirmed DLPDUs
40 Table 3 – Structure of unconfirmed DLPDUs
41 4.3.3 Acknowledge DLPDU
4.3.4 Immediate-reply DLPDU
Table 4 – Structure of acknowledge DLPDU
Table 5 – Structure of immediate-reply DLPDU
42 4.4 DLservice elements of procedure
4.4.1 Receipt of a DLUnitdata request primitive
43 4.4.2 Receipt of a DLUnitdata response primitive
44 4.4.3 Autonomous DLE acknowledge
4.4.4 Generation of a DLUnitdata indication primitive
45 4.5 Route mechanism
4.5.1 Request Type 4-route generation
46 Figure 15 – Source / destination designator
Figure 16 – Simple Type 4-route generation
Figure 17 – Extended Type 4-route generation
47 4.5.2 DLroute generation
Figure 18 – Complex and IP Type 4-route generation
Figure 19 – Simple DLroute generation
48 4.6 Link-access system
Figure 20 – Extended DLroute generation
Figure 21 – Complex and IP DLroute generation
49 4.7 Local variables, counters and queues
4.7.1 V(ACPDU) – acknowledge confirmed PDU
4.7.2 V(AUPDU) – acknowledge unconfirmed PDU
4.7.3 V(NA) – node-address
4.7.4 V(NDLE) – number of DLEs
4.7.5 V(PNR) – permitted number of retries
4.7.6 V(DC) – device class (simple or normal)
4.7.7 V(BR) – bit rate
4.7.8 V(MID) – max indication delay
50 4.7.9 V(DMRT) – default max retry time
4.7.10 Q(UR) – user request queue
4.7.11 C(LAC) – link access counter
4.7.12 C(LIC) – link idle counter
51 Bibliography
BS EN IEC 61158-4-4:2019
$198.66