{"id":244029,"date":"2024-10-19T16:01:27","date_gmt":"2024-10-19T16:01:27","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61158-5-122012\/"},"modified":"2024-10-25T10:59:39","modified_gmt":"2024-10-25T10:59:39","slug":"bs-en-61158-5-122012","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61158-5-122012\/","title":{"rendered":"BS EN 61158-5-12:2012"},"content":{"rendered":"
1.1<\/b> Overview<\/p>\n
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 \u201cwindow between corresponding application programs.\u201d<\/p>\n
This standard 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 12 fieldbus. The term \u201ctime-critical\u201d 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.<\/p>\n
This standard defines in an abstract way the externally visible service provided by the different Types of the fieldbus Application Layer in terms of<\/p>\n
an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service,<\/p>\n<\/li>\n
the primitive actions and events of the service;<\/p>\n<\/li>\n
the parameters associated with each primitive action and event, and the form which they take; and<\/p>\n<\/li>\n
the interrelationship between these actions and events, and their valid sequences.<\/p>\n<\/li>\n<\/ol>\n
The purpose of this standard is to define the services provided to<\/p>\n
the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and<\/p>\n<\/li>\n
Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model.<\/p>\n<\/li>\n<\/ol>\n
This standard specifies the structure and services of the IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO\/IEC 7498) and the OSI Application Layer Structure (ISO\/IEC 9545).<\/p>\n
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.<\/p>\n
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 standard to provide access to the FAL to control certain aspects of its operation.<\/p>\n
1.2<\/b> Specifications<\/p>\n
The principal objective of this standard 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 time- critical communications.<\/p>\n
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.<\/p>\n
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<\/p>\n
the sizes and octet ordering of various multi-octet service parameters, and<\/p>\n<\/li>\n
the correlation of paired request and confirm, or indication and response, primitives.<\/p>\n<\/li>\n<\/ol>\n
1.3<\/b> Conformance<\/p>\n
This standard does not specify individual implementations or products, nor does it constrain the implementations of application layer entities within industrial automation systems.<\/p>\n
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 standard.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
6<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 1 Scope 1.1 Overview <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 1.2 Specifications 1.3 Conformance 2 Normative references <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 3 Terms, definitions, symbols, abbreviations and conventions 3.1 Reference model terms and definitions 3.2 Service convention terms and definitions <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 3.3 Application layer and data-link service terms and definitions <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 3.4 Common symbols and abbreviations <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 3.5 Conventions <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 4 Concepts 4.1 Common concepts 4.2 Type specific concepts <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | Figures Figure 1 \u2013 Producer consumer model Figure 2 \u2013 Client server model Figure 3 \u2013 Server triggered invocation <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | Figure 4 \u2013 Slave reference model <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | Figure 5 \u2013 Simple slave device <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | Figure 6 \u2013 Complex slave device <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | Figure 7 \u2013 Master functional overview <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 5 Data type ASE 5.1 General 5.2 Formal definition of data type objects 5.3 FAL defined data types <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 5.4 Data type ASE service specification 6 Communication model specification 6.1 ASEs <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Figure 8 \u2013 Process output data sequence <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Figure 9 \u2013 Process input data sequence <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Tables Table 1 \u2013 Process output data <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Table 2 \u2013 Process input data <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Table 3 \u2013 Update process input data <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Table 4 \u2013 SII read <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | Table 5 \u2013 SII write <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | Table 6 \u2013 SII reload <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Figure 10 \u2013 CoE server model <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Table 7 \u2013 Allocation of SDO areas <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Figure 11 \u2013 Successful single SDO-Download sequence <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Figure 12 \u2013 Unsuccessful single SDO-Download sequence Figure 13 \u2013 Successful segmented SDO-Download sequence <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Figure 14 \u2013 Successful single SDO-Upload sequence <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Figure 15 \u2013 Unsuccessful single SDO-Upload sequence Figure 16 \u2013 Successful segmented SDO-Upload sequence <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Figure 17 \u2013 SDO information sequence <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | Figure 18 \u2013 Emergency service <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Figure 19 \u2013 Command sequence <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Figure 20 \u2013 PDO mapping <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | Figure 21 \u2013 Sync manager PDO assigment <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | Figure 22 \u2013 RxPDO service <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Figure 23 \u2013 TxPDO service <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Figure 24 \u2013 RxPDO remote transmission sequence Figure 25 \u2013 TxPDO remote transmission sequence <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Table 8 \u2013 SDO download expedited <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | Table 9 \u2013 SDO download normal <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | Table 10 \u2013 Download SDO segment <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Table 11 \u2013 SDO upload expedited <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Table 12 \u2013 SDO upload normal <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Table\u00a013 \u2013 Upload SDO segment Table 14 \u2013 Abort SDO transfer <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Table 15 \u2013 Get OD list <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Table 16 \u2013 OD list segment <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Table 17 \u2013 Get object description <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Table 18 \u2013 Get entry description <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Table 19 \u2013 Object entry segment <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Table 20 \u2013 Emergency <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Table 21 \u2013 RxPDO Table 22 \u2013 TxPDO <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | Table\u00a023 \u2013 RxPDO remote transmission Table 24 \u2013 TxPDO remote transmission <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Figure 26 \u2013 EoE sequence <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Table 25 \u2013 Initiate EoE <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Table 26 \u2013 EoE fragment <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Table 27 \u2013 Set IP parameter <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Table 28 \u2013 Set address filter <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Figure 27 \u2013 FoE read sequence with success <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Figure 28 \u2013 FoE read sequence with error Figure 29 \u2013 FoE write sequence with success <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Figure 30 \u2013 FoE write sequence with error Figure 31 \u2013 FoE write sequence with busy <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | Table 29 \u2013 FoE read Table 30 \u2013 FoE write <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Table 31 \u2013 FoE data Table 32 \u2013 FoE ack <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Table 33 \u2013 FoE busy Table 34 \u2013 FoE error <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | Table 35 \u2013 MBX read <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | Table 36 \u2013 MBX write <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | Table 37 \u2013 MBX read upd <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | 6.2 AR Table 38 \u2013 AL management and ESM service primitives <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | Figure 32 \u2013 Successful AL control sequence <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | Figure 33 \u2013 Unsuccessful AL control sequence <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | Figure 34 \u2013 AL state changed sequence <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | Table 39 \u2013 AL control <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | Table 40 \u2013 AL state change <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Fieldbus specifications – Application layer service definition. Type 12 elements<\/b><\/p>\n |