🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS EN IEC 61158-5-26:2019

BS EN IEC 61158-5-26:2019

$215.11

Industrial communication networks. Fieldbus specifications – Application layer service definition. Type 26 elements

Published By Publication Date Number of Pages
BSI 2019 110
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Categories: ,

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 Overview

The Fieldbus Application Layer (FAL) provides user programs with a means to access the Fieldbus communication environment. In this respect, the FAL can be viewed as a “window between corresponding application programs.”

This part of IEC 61158 provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 26 fieldbus. 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 International Standard defines in an abstract way the externally visible service provided by the different Types of fieldbus Application Layer in terms of

  1. an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service;

  2. the primitive actions and events of the service;

  3. the parameters associated with each primitive action and event, and the form which they take; and

  4. the interrelationship between these actions and events, and their valid sequences.

The purpose of this document is to define the services provided to

  1. the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and

  2. Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model.

This document specifies the structure and services of the IEC Fieldbus Application Layer, in conformance with the OSI Basic Reference Model (see ISO/IEC 7498-1) and the OSI Application Layer Structure (see ISO/IEC 9545).

FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes.

Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this document to provide access to the FAL to control certain aspects of its operation.

1.2 Specifications

The principal objective of this document is to specify the characteristics of conceptual application layer services suitable for time-critical communications, and thus supplement the OSI Basic Reference Model in guiding the development of application layer protocols for timecritical communications.

A secondary objective is to provide migration paths from previously-existing industrial communications protocols. It is this latter objective which gives rise to the diversity of services standardized as the various Types of IEC 61158, and the corresponding protocols standardized in subparts of IEC 61158-6.

This specification may be used as the basis for formal Application 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

  1. the sizes and octet ordering of various multi-octet service parameters, and

  2. the correlation of paired request and confirm, or indication and response, primitives.

1.3 Conformance

This document does not specify individual implementations or products, nor does it constrain the implementations of application layer entities within industrial automation systems.

There is no conformance of equipment to this application layer service definition standard. Instead, conformance is achieved through implementation of conforming application layer protocols that fulfill any given Type of application layer services as defined in this document.

PDF Catalog

PDF Pages PDF Title
2 National foreword
5 Annex ZA(normative)Normative references to international publicationswith their corresponding European publications
7 CONTENTS
10 FOREWORD
12 INTRODUCTION
13 1 Scope
1.1 Overview
14 1.2 Specifications
1.3 Conformance
2 Normative references
15 3 Terms, definitions, symbols, abbreviations and conventions
16 3.1 Terms and definitions from other ISO/IEC standards
3.1.1 Terms and definitions from ISO/IEC 74981
3.1.2 Terms and definitions from ISO/IEC 8822
3.1.3 Terms and definitions from ISO/IEC 9545
3.1.4 Terms and definitions from ISO/IEC 88241
17 3.2 Fieldbus application layer Type 26-specific definitions
23 3.3 Abbreviations and symbols
25 3.4 Conventions
3.4.1 Overview
3.4.2 General conventions
3.4.3 Conventions for class definitions
26 3.4.4 Conventions for service definitions
27 4 Concepts
28 5 Data type ASE
5.1 Overview
5.2 Formal definition of data type objects
5.2.1 Data type class definitions
29 5.2.2 Attributes
30 5.3 FAL defined data types
5.3.1 Fixed length types
34 5.3.2 String types
35 5.4 Data type ASE service specification
6 Communication model specification
6.1 General
6.2 Protocol stack for Type 26 fieldbus
36 6.3 Overview of Type 26 communication model
Figures
Figure 1 – Protocol stack for Type 26 fieldbus
37 6.4 Cyclic data communication service with Common-memory
6.4.1 Overview
6.4.2 Common–memory: allocation to each node
Figure 2 – Unconfirmed Push-Publisher/Subscriber type interaction
Figure 3 – Unconfirmed/Confirmed Client/Server type interaction
38 6.4.3 Data sharing among nodes with the CM
Figure 4 – Common memory allocation
39 Figure 5 – Data sharing with the CM
Figure 6 – Node #01 for reception only
40 6.4.4 CM data type
6.5 ASEs
6.5.1 Overview of Type 26 ASEs
Figure 7 – Node #01 without the CM
41 6.5.2 Type 26 specific conventions for FAL service common parameters
Figure 8 – The structure of ASEs for Type 26 FAL
42 6.5.3 Cyclic-data ASE
44 Tables
Table 1 – Write service parameters
45 Table 2 – Send-CM service parameters
Table 3 – Read service parameters
46 Table 4 – Update memory service parameters
47 6.5.4 Message data ASE
Table 5 – Get- buffer service parameters
50 Figure 9 – Virtual-address-space for Byte block
51 Table 6 – Byte block read service parameters
52 Table 7 – Byte block write service parameters
53 Figure 10 – Virtual-address-space for Word block
Table 8 – Word block read service parameters
54 Table 9 – Word block write service parameters
55 Table 10 – Network parameter read service parameters
56 Table 11 – Network parameter write service parameters
57 Table 12 – Stop command service parameters
58 Table 13 – Operation command service parameters
Table 14 – profile read service parameters
61 Table 15 – Transparent message service parameters
62 Table 16 – Log data read service parameters
Table 17 – Log data items
66 Table 18 – Log data clear service parameters
67 Table 19 – Message return service parameters
68 Table 20 – Vendor specific message service parameters
69 Table 21 – Set remote node configuration parameter service parameters
Table 22 – Data elements and Node configuration parameters
70 Table 23 – Service parameters of Read remote participating node management information parameter service
71 Table 24 – Participating node management information parameters
72 Table 25 – Read remote node management information parameter service parameters
Table 26 – Node management information parameters
73 Table 27 – Read remote node setting information parameter service parameters
74 6.5.5 Communication load measurement ASE
Table 28 –Node setting information parameters
76 Table 29 – Start TK-holding-time measurement service parameters
Table 30 – Terminate TK-holding-time measurement service parameters
77 Table 31 – Token-holding-time measurement result
78 Table 32 – Start GP_Comm sender log service parameters
Table 33 – Terminate GP_Comm sender log service parameters
79 6.5.6 Network management ASE
Table 34 – GP_Comm sender log measurement result
82 Table 35 – Service parameters for Set configuration parameter
83 Table 36 – Configuration parameters
Table 37 – Read node management information parameter service parameters
84 Table 38 – Node management information parameters
85 Table 39 – Service parameters for Read participating node mgt. information parameter
Table 40 – Participating node management information parameters
86 Table 41 – Service parameters for Read network management information parameter
Table 42 – Network management information parameters
87 Table 43 – Service parameters for Read message sequencenumber management information
Table 44 – Read message sequence number management information parameters
88 Table 45 –Read node status service parameters
Table 46 – Read node status parameters
89 Table 47 – Upper layer operating condition matrix
Table 48 –Reset node service parameters
90 Table 49 – Set network address service parameters
Table 50 – Register service parameters
91 Table 51 – Event service parameters
Table 52 – Activate/Deactivate measurement service parameters
92 6.5.7 General purpose command server ASE
Table 53 – Get log data service parameters
95 6.5.8 AR ASE
Table 54 – Send command service parameters
96 Figure 11 – AR ASE internal architecture
98 Table 55 – CT send service parameters
100 Table 56 – MT send service parameters
101 Table 57 – CS send service parameters
102 Table 58 – Notify state change service parameters
Table 59 – Control measurement service parameters
104 Figure 12 – Structure of IP address
Table 60 – DLSAP assignments
105 Table 61 – DLS Primitives and parameters
106 6.5.9 FAL ASE summary
Table 62 – Lower layer T-profile and the required standards
Table 63 – Summary of FAL ASEs
109 Bibliography
BS EN IEC 61158-5-26:2019
$215.11