BS EN 61158-5-23:2014
$215.11
Industrial communication networks. Fieldbus specifications – Application layer service definition. Type 23 elements
Published By | Publication Date | Number of Pages |
BSI | 2014 | 94 |
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 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-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 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 | English CONTENTS |
8 | INTRODUCTION |
9 | 1 Scope 1.1 General |
10 | 1.2 Specifications 1.3 Conformance 2 Normative references |
11 | 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Referenced terms and definitions |
12 | 3.2 Type 23 specific terms and definitions |
14 | 3.3 Symbols and abbreviated terms |
15 | 3.4 Conventions |
18 | 4 Concept 5 Data type ASE 5.1 Overview 5.2 Fixed length types |
23 | 6 Communication model specification 6.1 Communication model |
24 | Figures Figure 1 – Cyclic model (n:n type distributed shared memory, unconfirmed push model) Figure 2 – Cyclic model (1:n type distributed shared memory, unconfirmed push model) Figure 3 – Transient model (Client server model) |
25 | 6.2 ASE Figure 4 – Transient model (Push model) Figure 5 – Structure of ASE type C of FAL type 23 Figure 6 – Structure of ASE type F of FAL type 23 |
27 | Tables Table 1 – Ld service parameters Table 2 – Set service parameters Table 3 – Reset service parameters |
28 | Table 4 – Read service parameters Table 5 – Write service parameters |
29 | Table 6 – Ld service parameters |
30 | Table 7 – Set service parameters Table 8 – Reset service parameters |
31 | Table 9 – Read service parameters Table 10 – Write service parameters |
33 | Table 11 – Ld service parameters |
34 | Table 12 – Set service parameters Table 13 – Reset service parameters Table 14 – Read service parameters |
35 | Table 15 – Write service parameters |
38 | Table 16 – Get memory access info service parameters |
39 | Table 17 – Run service parameters Table 18 – Stop service parameters |
40 | Table 19 – Read memory service parameters |
41 | Table 20 – Write memory service parameters |
43 | Table 21 – Get memory access info service parameters |
44 | Table 22 – Run service parameters |
45 | Table 23 – Stop service parameters |
46 | Table 24 – Read memory service parameters |
47 | Table 25 – Write memory service parameters |
48 | Table 26 – Vendor command service parameters |
49 | Table 27 – Distribute node info service parameters |
50 | Table 28 – Get statistics service parameters |
51 | Table 29 – Get node info detail service parameters |
54 | Table 30 – AC data service parameters |
55 | Table 31 – AC data ND service parameters |
56 | Table 32 – Get attribute service parameters Table 33 – Set attribute service parameters |
58 | Table 34 – Synchronization trigger service parameters |
59 | Table 35 – Start measurement service parameters |
60 | 6.3 AR type C Figure 7 – Structure of AR type C Table 36 – Get offset service parameters |
64 | Table 37 – Control cyclic service parameters |
66 | Table 38 – CT Update service parameters |
67 | Table 39 – AC Send service parameters |
68 | Table 40 – AC Param send service parameters |
73 | 6.4 AR type F Figure 8 – Structure of AR type F Table 41 – CPD Set service parameters |
80 | Table 42 – Control cyclic service parameters |
82 | Table 43 – CT Update service parameters |
83 | Table 44 – AC Send service parameters |
84 | Table 45 – AC Send ND service parameters |
88 | Table 46 – Synchronous trigger internal service parameters |
89 | Table 47 – Measure send service parameters |
90 | Table 48 – MeasureAck send service parameters Table 49 – Offset send service parameters |
91 | Table 50 – Update send service parameters |
92 | Bibliography |