BS EN 61158-3-22:2012
$167.15
Industrial communication networks. Fieldbus specifications – Data-link layer service definition. Type 22 elements
Published By | Publication Date | Number of Pages |
BSI | 2012 | 38 |
1.1 Overview
This part of IEC 61158 provides common elements for basic time-critical messaging communications between devices in an automation environment. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life.
This standard defines in an abstract way the externally visible service provided by the Type 22 fieldbus data-link layer in terms of:
-
the primitive actions and events of the service;
-
the parameters associated with each primitive action and event, and the form which they take; and
-
the interrelationship between these actions and events, and their valid sequences.
The purpose of this standard is to define the services provided to:
-
the Type 22 fieldbus application layer at the boundary between the application and data-link layers of the fieldbus reference model; and
-
systems management at the boundary between the data-link layer and systems management of the fieldbus reference model.
1.2 Specifications
The principal objective of this standard 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-critical 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:
-
the sizes and octet ordering of various multi-octet service parameters; and
-
the correlation of paired request and confirm, or indication and response, primitives.
1.3 Conformance
This standard does not specify individual implementations or products, nor do they 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 fulfils the Type 22 data-link layer services defined in this standard.
PDF Catalog
PDF Pages | PDF Title |
---|---|
6 | CONTENTS |
8 | INTRODUCTION |
9 | 1 Scope 1.1 Overview 1.2 Specifications 1.3 Conformance |
10 | 2 Normative References 3 Terms, definitions, symbols, abbreviations and conventions 3.1 Reference model terms and definitions |
12 | 3.2 Service convention terms and definitions |
13 | 3.3 Data-link service terms and definitions |
15 | 3.4 Symbols and abbreviations |
17 | 3.5 Common conventions |
18 | 4 Data-link layer services and concepts 4.1 Operating principle 4.2 Communication models |
19 | Figures Figure 1 – RTFL device reference model |
20 | 4.3 Topology Figure 2 – RTFN device reference model Figure 3 – Logical double line in a physical tree topology |
21 | 4.4 Addressing Figure 4 – Logical double line in a physical line topology Figure 5 – Addressing modes |
22 | 4.5 Gateway 4.6 Interaction models 4.7 Synchronization concept |
23 | 5 Communication services 5.1 Overview Figure 6 – Time sequence diagram for time SYNC_START service Figure 7 – Synchronized timing signals without offset Figure 8 – Synchronized timing signals with offset |
24 | Tables Table 1 – Summary of DL-services and primitives |
25 | 5.2 Communication management services Table 2 – DL-Network verification service (NV) Table 3 – DL-RTFN scan network read service (RTFNSNR) |
26 | Table 4 – DL-RTFN connection establishment DLL service (RTFNCE) Table 5 – DL-RTFN connection release service (RTFNCR) |
27 | Table 6 – DL-RTFL control service (RTFLCTL) Table 7 – DL-RTFL configuration service (RTFLCFG) |
28 | 5.3 Cyclic data channel service (CDC) Table 8 – DL-Read configuration data service (RDCD) |
29 | Table 9 – CDC send service (CDCS) |
30 | 5.4 Message channel services (MSC) Table 10 – MSC send service (MSCS) |
31 | 5.5 Time synchronization Table 11 – MSC send broadcast service (MSCSB) Table 12 – MSC read service (MSCR) Table 13 – DL-DelayMeasurement start service (DMS) |
32 | Table 14 – DL-DelayMeasurement read service (DMR) Table 15 – DL-PCS configuration service (PCSC) |
33 | Table 16 – DL-Sync master configuration service (SYNC_MC) Table 17 – DL-Sync start service (SYNC_START) |
34 | 5.6 Media independent interface (MII) management services Table 18 – DL-Sync stop service (SYNC_STOP) Table 19 – DL-MII read service (MIIR) |
35 | Table 20 – DL-MII write service (MIIW) |
36 | Bibliography |