BS EN 61158-5-12:2012
$215.11
Industrial communication networks. Fieldbus specifications – Application layer service definition. Type 12 elements
| Published By | Publication Date | Number of Pages |
| BSI | 2012 | 122 |
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 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 “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 different Types of the fieldbus Application Layer in terms of
-
an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service,
-
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 FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and
-
Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model.
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).
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 standard to provide access to the FAL to control certain aspects of its operation.
1.2 Specifications
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.
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
-
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 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 standard.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 6 | CONTENTS |
| 9 | INTRODUCTION |
| 10 | 1 Scope 1.1 Overview |
| 11 | 1.2 Specifications 1.3 Conformance 2 Normative references |
| 12 | 3 Terms, definitions, symbols, abbreviations and conventions 3.1 Reference model terms and definitions 3.2 Service convention terms and definitions |
| 13 | 3.3 Application layer and data-link service terms and definitions |
| 17 | 3.4 Common symbols and abbreviations |
| 18 | 3.5 Conventions |
| 19 | 4 Concepts 4.1 Common concepts 4.2 Type specific concepts |
| 21 | Figures Figure 1 – Producer consumer model Figure 2 – Client server model Figure 3 – Server triggered invocation |
| 22 | Figure 4 – Slave reference model |
| 23 | Figure 5 – Simple slave device |
| 24 | Figure 6 – Complex slave device |
| 25 | Figure 7 – Master functional overview |
| 27 | 5 Data type ASE 5.1 General 5.2 Formal definition of data type objects 5.3 FAL defined data types |
| 35 | 5.4 Data type ASE service specification 6 Communication model specification 6.1 ASEs |
| 36 | Figure 8 – Process output data sequence |
| 37 | Figure 9 – Process input data sequence |
| 39 | Tables Table 1 – Process output data |
| 40 | Table 2 – Process input data |
| 41 | Table 3 – Update process input data |
| 49 | Table 4 – SII read |
| 50 | Table 5 – SII write |
| 51 | Table 6 – SII reload |
| 54 | Figure 10 – CoE server model |
| 55 | Table 7 – Allocation of SDO areas |
| 59 | Figure 11 – Successful single SDO-Download sequence |
| 60 | Figure 12 – Unsuccessful single SDO-Download sequence Figure 13 – Successful segmented SDO-Download sequence |
| 61 | Figure 14 – Successful single SDO-Upload sequence |
| 62 | Figure 15 – Unsuccessful single SDO-Upload sequence Figure 16 – Successful segmented SDO-Upload sequence |
| 63 | Figure 17 – SDO information sequence |
| 64 | Figure 18 – Emergency service |
| 65 | Figure 19 – Command sequence |
| 66 | Figure 20 – PDO mapping |
| 67 | Figure 21 – Sync manager PDO assigment |
| 68 | Figure 22 – RxPDO service |
| 69 | Figure 23 – TxPDO service |
| 70 | Figure 24 – RxPDO remote transmission sequence Figure 25 – TxPDO remote transmission sequence |
| 74 | Table 8 – SDO download expedited |
| 75 | Table 9 – SDO download normal |
| 76 | Table 10 – Download SDO segment |
| 77 | Table 11 – SDO upload expedited |
| 78 | Table 12 – SDO upload normal |
| 79 | Table 13 – Upload SDO segment Table 14 – Abort SDO transfer |
| 80 | Table 15 – Get OD list |
| 81 | Table 16 – OD list segment |
| 82 | Table 17 – Get object description |
| 83 | Table 18 – Get entry description |
| 85 | Table 19 – Object entry segment |
| 86 | Table 20 – Emergency |
| 87 | Table 21 – RxPDO Table 22 – TxPDO |
| 88 | Table 23 – RxPDO remote transmission Table 24 – TxPDO remote transmission |
| 90 | Figure 26 – EoE sequence |
| 93 | Table 25 – Initiate EoE |
| 94 | Table 26 – EoE fragment |
| 95 | Table 27 – Set IP parameter |
| 96 | Table 28 – Set address filter |
| 97 | Figure 27 – FoE read sequence with success |
| 98 | Figure 28 – FoE read sequence with error Figure 29 – FoE write sequence with success |
| 99 | Figure 30 – FoE write sequence with error Figure 31 – FoE write sequence with busy |
| 101 | Table 29 – FoE read Table 30 – FoE write |
| 102 | Table 31 – FoE data Table 32 – FoE ack |
| 103 | Table 33 – FoE busy Table 34 – FoE error |
| 105 | Table 35 – MBX read |
| 106 | Table 36 – MBX write |
| 107 | Table 37 – MBX read upd |
| 108 | 6.2 AR Table 38 – AL management and ESM service primitives |
| 109 | Figure 32 – Successful AL control sequence |
| 110 | Figure 33 – Unsuccessful AL control sequence |
| 111 | Figure 34 – AL state changed sequence |
| 117 | Table 39 – AL control |
| 118 | Table 40 – AL state change |
| 119 | Bibliography |
