{"id":430837,"date":"2024-10-20T07:24:59","date_gmt":"2024-10-20T07:24:59","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-61158-5-262023\/"},"modified":"2024-10-26T14:05:33","modified_gmt":"2024-10-26T14:05:33","slug":"bs-en-iec-61158-5-262023","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-61158-5-262023\/","title":{"rendered":"BS EN IEC 61158-5-26:2023"},"content":{"rendered":"
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 […]<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
5<\/td>\n | Annex ZA (normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 1 Scope 1.1 General <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 1.2 Specifications 1.3 Conformance 2 Normative references <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 3.1.4 Terms and definitions from ISO\/IEC 88241 3.2 Fieldbus application layer Type 26-specific definitions <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 3.3 Abbreviated terms and symbols <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 3.4 Conventions 3.4.1 Overview 3.4.2 General conventions <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 3.4.3 Conventions for class definitions <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 3.4.4 Conventions for service definitions <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 4 Concepts 5 Data type ASE 5.1 Overview <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 5.2 Formal definition of data type objects 5.2.1 Data type class definitions <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 5.2.2 Attributes <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 5.3 FAL defined data types 5.3.1 Fixed length types <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 5.3.2 String types <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 5.4 Data type ASE service specification 6 Communication model specification 6.1 General 6.2 Protocol stack for Type 26 fieldbus <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 6.3 Overview of Type 26 communication model Figures Figure 1 \u2013 Protocol stack for Type 26 fieldbus <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 6.4 Cyclic data communication service with Common-memory 6.4.1 Overview Figure 2 \u2013 Unconfirmed Push-Publisher\/Subscriber type interaction Figure 3 \u2013 Unconfirmed\/Confirmed Client\/Server type interaction <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 6.4.2 Common\u2013memory: allocation to each node <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 6.4.3 Data sharing among nodes with the CM Figure 4 \u2013 Common memory allocation <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure 5 \u2013 Data sharing with the CM Figure 6 \u2013 Node #01 for reception only <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 6.4.4 CM data type 6.5 ASEs 6.5.1 Overview of Type 26 ASEs Figure 7 \u2013 Node #01 without the CM Figure 8 \u2212 Data sharing among nodes with and without CM3 <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 6.5.2 Type 26 specific conventions for FAL service common parameters Figure 9 \u2013 The structure of ASEs for Type 26 FAL <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | 6.5.3 Cyclic-data ASE <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Tables Table 1 \u2013 Write service parameters <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | Table 2 \u2013 Send-CM service parameters Table 3 \u2013 Read service parameters <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | Table 4 \u2013 Update memory service parameters <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 6.5.4 Message data ASE Table 5 \u2013 Get- buffer service parameters <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | Figure 10 \u2013 Virtual-address-space for Byte block Table 6 \u2013 Byte block read service parameters <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Table 7 \u2013 Byte block write service parameters <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Figure 11 \u2013 Virtual-address-space for Word block Table 8 \u2013 Word block read service parameters <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Table 9 \u2013 Word block write service parameters <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Table 10 \u2013 Network parameter read service parameters <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Table 11 \u2013 Extended network parameter read service parameters <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Table 12 \u2013 Network parameter write service parameters <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | Table 13 \u2013 Extended network parameter write service parameters <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Table 14 \u2013 Stop command service parameters Table 15 \u2013 Operation command service parameters <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Table 16 \u2013 profile read service parameters <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | Table 17 \u2013 Transparent message service parameters <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Table 18 \u2013 Log data read service parameters Table 19 \u2013 Log data items <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Table 20 \u2013 Log data clear service parameters <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | Table 21 \u2013 Message return service parameters <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | Table 22 \u2013 Vendor specific message service parameters <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Table 23 \u2013 Set remote node configuration parameter service parameters Table 24 \u2013 Data elements and Node configuration parameters <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Table 25 \u2013 Service parameters of Read remote participatingnode management information parameter service <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Table 26 \u2013 Participating node management information parameters <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Table 27 \u2013 Read remote node management information parameter service parameters <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Table 28 \u2013 Node management information parameters <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | 6.5.5 Load measurement ASE Table 29 \u2013 Read remote node setting information parameter service parameters Table 30 \u2013 Node setting information parameters <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Table 31 \u2013 Start TK-holding-time measurement service parameters <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Table 32 \u2013 Terminate TK-holding-time measurement service parameters <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Table 33 \u2013 Token-holding-time measurement result <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Table 34 \u2013 Start GP_Comm sender log service parameters Table 35 \u2013 Terminate GP_Comm sender log service parameters <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | 6.5.6 Network management ASE Table 36 \u2013 GP_Comm sender log measurement result <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Table 37 \u2013 Service parameters for Set configuration parameter Table 38 \u2013 Configuration parameters <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Table 39 \u2013 Read node management information parameter service parameters Table 40 \u2013 Node management information parameters <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Table 41 \u2013 Service parameters for Read participating node mgt. information parameter <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Table 42 \u2013 Participating node management information parameters Table 43 \u2013 Service parameters for Read network management information parameter <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Table 44 \u2013 Network management information parameters Table 45 \u2013 Service parameters for Read message sequencenumber management information <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Table 46 \u2013 Read message sequence number management information parameters Table 47 \u2013 Read node status service parameters <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Table 48 \u2013 Read node status parameters Table 49 \u2013 Upper layer operating condition matrix <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Table 50 \u2013 Reset node service parameters Table 51 \u2013 Set network address service parameters <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Table 52 \u2013 Register service parameters Table 53 \u2013 Event service parameters <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | Table 54 \u2013 Activate\/Deactivate measurement service parameters <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | 6.5.7 General purpose command server ASE Table 55 \u2013 Get log data service parameters <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | 6.5.8 AR ASE Table 56 \u2013 Send command service parameters <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | Figure 12 \u2013 AR ASE internal architecture <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | Table 57 \u2013 CT send service parameters <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | Table 58 \u2013 MT send service parameters <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | Table 59 \u2013 CS send service parameters <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | Table 60 \u2013 Notify state change service parameters <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | Table 61 \u2013 Control measurement service parameters <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | Table 62 \u2013 DLSAP assignments <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | Figure 13 \u2013 Structure of IP address <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | Table 63 \u2013 DLS Primitives and parameters <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | 6.5.9 FAL ASE summary Table 64 \u2013 Lower layer T-profile and the required standards Table 65 \u2013 Summary of FAL ASEs <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Fieldbus specifications – Application layer service definition. Type 26 elements<\/b><\/p>\n |