BS EN IEC 61158-5-26:2023
$215.11
Industrial communication networks. Fieldbus specifications – Application layer service definition. Type 26 elements
Published By | Publication Date | Number of Pages |
BSI | 2023 | 122 |
1.1 General 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 2 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 Type 2 fieldbus application layer in terms of: a) an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service, b) the primitive actions and events of the service; c) the parameters associated with each primitive action and event, and the form which they take; and d) the interrelationship between these actions and events, and their valid sequences. The purpose of this document is to define the services provided to: a) the FAL user at the boundary between the user and the application layer of the fieldbus reference model, and b) 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 Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (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 318 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 […] 1.3 Conformance […]
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
5 | Annex ZA (normative)Normative references to international publicationswith their corresponding European publications |
7 | CONTENTS |
10 | FOREWORD |
12 | INTRODUCTION |
13 | 1 Scope 1.1 General |
14 | 1.2 Specifications 1.3 Conformance 2 Normative references |
16 | 3 Terms, definitions, symbols, abbreviated terms and conventions 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 |
17 | 3.1.4 Terms and definitions from ISO/IEC 88241 3.2 Fieldbus application layer Type 26-specific definitions |
23 | 3.3 Abbreviated terms and symbols |
25 | 3.4 Conventions 3.4.1 Overview 3.4.2 General conventions |
26 | 3.4.3 Conventions for class definitions |
27 | 3.4.4 Conventions for service definitions |
28 | 4 Concepts 5 Data type ASE 5.1 Overview |
29 | 5.2 Formal definition of data type objects 5.2.1 Data type class definitions |
30 | 5.2.2 Attributes |
31 | 5.3 FAL defined data types 5.3.1 Fixed length types |
37 | 5.3.2 String types |
38 | 5.4 Data type ASE service specification 6 Communication model specification 6.1 General 6.2 Protocol stack for Type 26 fieldbus |
39 | 6.3 Overview of Type 26 communication model Figures Figure 1 – Protocol stack for Type 26 fieldbus |
40 | 6.4 Cyclic data communication service with Common-memory 6.4.1 Overview Figure 2 – Unconfirmed Push-Publisher/Subscriber type interaction Figure 3 – Unconfirmed/Confirmed Client/Server type interaction |
41 | 6.4.2 Common–memory: allocation to each node |
42 | 6.4.3 Data sharing among nodes with the CM Figure 4 – Common memory allocation |
43 | Figure 5 – Data sharing with the CM Figure 6 – Node #01 for reception only |
44 | 6.4.4 CM data type 6.5 ASEs 6.5.1 Overview of Type 26 ASEs Figure 7 – Node #01 without the CM Figure 8 − Data sharing among nodes with and without CM3 |
45 | 6.5.2 Type 26 specific conventions for FAL service common parameters Figure 9 – The structure of ASEs for Type 26 FAL |
46 | 6.5.3 Cyclic-data ASE |
49 | Tables Table 1 – Write service parameters |
50 | Table 2 – Send-CM service parameters Table 3 – Read service parameters |
51 | Table 4 – Update memory service parameters |
52 | 6.5.4 Message data ASE Table 5 – Get- buffer service parameters |
57 | Figure 10 – Virtual-address-space for Byte block Table 6 – Byte block read service parameters |
58 | Table 7 – Byte block write service parameters |
59 | Figure 11 – Virtual-address-space for Word block Table 8 – Word block read service parameters |
60 | Table 9 – Word block write service parameters |
61 | Table 10 – Network parameter read service parameters |
62 | Table 11 – Extended network parameter read service parameters |
63 | Table 12 – Network parameter write service parameters |
64 | Table 13 – Extended network parameter write service parameters |
65 | Table 14 – Stop command service parameters Table 15 – Operation command service parameters |
66 | Table 16 – profile read service parameters |
68 | Table 17 – Transparent message service parameters |
69 | Table 18 – Log data read service parameters Table 19 – Log data items |
74 | Table 20 – Log data clear service parameters |
75 | Table 21 – Message return service parameters |
76 | Table 22 – Vendor specific message service parameters |
77 | Table 23 – Set remote node configuration parameter service parameters Table 24 – Data elements and Node configuration parameters |
78 | Table 25 – Service parameters of Read remote participatingnode management information parameter service |
79 | Table 26 – Participating node management information parameters |
80 | Table 27 – Read remote node management information parameter service parameters |
81 | Table 28 – Node management information parameters |
82 | 6.5.5 Load measurement ASE Table 29 – Read remote node setting information parameter service parameters Table 30 – Node setting information parameters |
84 | Table 31 – Start TK-holding-time measurement service parameters |
85 | Table 32 – Terminate TK-holding-time measurement service parameters |
86 | Table 33 – Token-holding-time measurement result |
87 | Table 34 – Start GP_Comm sender log service parameters Table 35 – Terminate GP_Comm sender log service parameters |
88 | 6.5.6 Network management ASE Table 36 – GP_Comm sender log measurement result |
92 | Table 37 – Service parameters for Set configuration parameter Table 38 – Configuration parameters |
93 | Table 39 – Read node management information parameter service parameters Table 40 – Node management information parameters |
94 | Table 41 – Service parameters for Read participating node mgt. information parameter |
95 | Table 42 – Participating node management information parameters Table 43 – Service parameters for Read network management information parameter |
96 | Table 44 – Network management information parameters Table 45 – Service parameters for Read message sequencenumber management information |
97 | Table 46 – Read message sequence number management information parameters Table 47 – Read node status service parameters |
98 | Table 48 – Read node status parameters Table 49 – Upper layer operating condition matrix |
99 | Table 50 – Reset node service parameters Table 51 – Set network address service parameters |
100 | Table 52 – Register service parameters Table 53 – Event service parameters |
101 | Table 54 – Activate/Deactivate measurement service parameters |
102 | 6.5.7 General purpose command server ASE Table 55 – Get log data service parameters |
105 | 6.5.8 AR ASE Table 56 – Send command service parameters |
106 | Figure 12 – AR ASE internal architecture |
109 | Table 57 – CT send service parameters |
111 | Table 58 – MT send service parameters |
112 | Table 59 – CS send service parameters |
113 | Table 60 – Notify state change service parameters |
114 | Table 61 – Control measurement service parameters |
115 | Table 62 – DLSAP assignments |
116 | Figure 13 – Structure of IP address |
117 | Table 63 – DLS Primitives and parameters |
118 | 6.5.9 FAL ASE summary Table 64 – Lower layer T-profile and the required standards Table 65 – Summary of FAL ASEs |
121 | Bibliography |