BS EN 61158-5-2:2012
$215.11
Industrial communication networks. Fieldbus specifications – Application layer service definition. Type 2 elements
| Published By | Publication Date | Number of Pages |
| BSI | 2012 | 200 |
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 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 standard defines in an abstract way the externally visible service provided by the Type 2 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 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 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 the Type 2 application layer services as defined in this standard.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 7 | CONTENTS |
| 10 | INTRODUCTION |
| 11 | 1 Scope 1.1 Overview |
| 12 | 1.2 Specifications 1.3 Conformance 2 Normative references |
| 13 | 3 Terms, definitions, symbols, abbreviations and conventions 3.1 ISO/IEC 7498 1 terms |
| 14 | 3.2 ISO/IEC 8822 terms 3.3 ISO/IEC 9545 terms 3.4 ISO/IEC 8824 terms 3.5 Type 2 fieldbus data-link layer terms 3.6 Type 2 fieldbus application-layer specific definitions |
| 21 | 3.7 Type 2 abbreviations and symbols |
| 22 | 3.8 Conventions |
| 25 | 4 Common concepts 5 Data type ASE 5.1 General 5.2 Formal definition of data type objects 5.3 FAL defined data types |
| 34 | Tables Table 1 – Valid IANA MIB printer codes for character set selection |
| 35 | 5.4 Data type ASE service specification 6 Communication model specification 6.1 Concepts |
| 37 | Figures Figure 1 – Overview of ASEs and object classes |
| 38 | Figure 2 – Addressing format using MAC, class, instance and attribute IDs |
| 40 | Table 2 – Common elements |
| 41 | Table 3 – ST language elements Table 4 – Type conversion operations |
| 42 | Table 5 – Values of implementation-dependent parameters |
| 43 | 6.2 ASEs Table 6 – Extensions to IEC 61131 3:2003 |
| 55 | Figure 3 – Identity object state transition diagram |
| 56 | Table 7 – Identity object state event matrix |
| 60 | Figure 4 – Static Assembly state transition diagram Table 8 – Static Assembly state event matrix |
| 61 | Figure 5 – Dynamic Assembly state transition diagram Table 9 – Dynamic Assembly state event matrix |
| 64 | Table 10 – Message Router object Forward_Open parameters |
| 67 | Table 11 – Acknowledge Handler object state event matrix |
| 68 | Table 12 – Producing I/O application object state event matrix |
| 70 | Figure 6 – Typical timing relationships for acknowledged data production Figure 7 – Example of a COS system with two acking devices Figure 8 – Message flow in COS connection – one Connection object, one consumer |
| 71 | Figure 9 – Message flow in COS connection – multiple consumers |
| 80 | Table 13 – Profile identification Table 14 – Profile default settings and ranges |
| 81 | Table 15 – Default PTP clock settings |
| 82 | Table 16 – Hand_Set clock quality management |
| 83 | Figure 10 – CPF2 time synchronization offset clock model Figure 11 – CPF2 time synchronization system with offset clock model |
| 86 | Figure 12 – CPF2 time synchronization group startup sequence |
| 92 | Figure 13 – Parameter object state transition diagram Table 17 – Parameter object state event matrix |
| 95 | Table 18 – Status codes |
| 97 | Table 19 – Get_Attribute_All service parameters |
| 98 | Table 20 – Set_Attribute_All service parameters |
| 100 | Table 21 – Get_Attribute_List service parameters |
| 102 | Table 22 – Set_Attribute_List service parameters |
| 104 | Table 23 – Reset service parameters |
| 106 | Table 24 – Start service parameters |
| 108 | Table 25 – Stop service parameters |
| 109 | Table 26 – Create service parameters |
| 111 | Table 27 – Delete service parameters |
| 112 | Table 28 – Get_Attribute_Single service parameters |
| 114 | Table 29 – Set_Attribute_Single service parameters |
| 115 | Table 30 – Find_Next_Object_Instance service parameters |
| 117 | Figure 14 – Example of Find_Next_Object_Instance service |
| 118 | Table 31 – NOP service parameters |
| 119 | Table 32 – Apply_Attributes service parameters |
| 121 | Table 33 – Save service parameters |
| 122 | Table 34 – Restore service parameters |
| 124 | Table 35 – Group_Sync service parameters |
| 126 | Table 36 – Add_AckData_Path service parameters |
| 127 | Table 37 – Remove_AckData_Path service parameters |
| 128 | Table 38 – Get-Enum_String service parameters |
| 136 | Table 39 – CM_Open service parameters |
| 138 | Table 40 – CM_Close service parameters |
| 140 | Table 41 – CM_ Unconnected_Send service parameters |
| 142 | Table 42 – CM_Get_Connection_Data service parameters |
| 143 | Table 43 – CM_Search_Connection_Data service parameters |
| 144 | Table 44 – CM_Get_Connection_Data service parameters |
| 149 | Table 45 – I/O Connection object attribute access |
| 150 | Table 46 – Bridged Connection object attribute access |
| 151 | Table 47 – Explicit messaging object attribute access |
| 152 | Figure 15 – Transmission trigger timer |
| 153 | Figure 16 – Inactivity watchdog timer |
| 154 | Figure 17 – Using tools for configuration |
| 155 | Figure 18 – Production inhibit timer |
| 156 | Table 48 – Connection_Bind service parameters |
| 157 | Table 49 – Service_Name service parameters |
| 158 | 6.3 ARs |
| 160 | Table 50 – How production trigger, transport class, and CM_RPI determine when data is produced |
| 161 | Figure 19 – Context of transport services within the connection model Figure 20 – Application–to–application view of data transfer |
| 162 | Figure 21 – Data flow diagram for a link producer |
| 163 | Figure 22 – Data flow diagram for a link consumer |
| 164 | Figure 23 – Triggers |
| 165 | Figure 24 – Binding transport instances to the producer and consumer of a transport connection that does not have a reverse data path Figure 25 – Binding transport instances to the producers and consumers of a transport connection that does have a reverse data path |
| 166 | Figure 26 – Binding transport instances to the producer and consumers of a multipoint connection when the transport connection does not have a reverse data path Figure 27 – Binding transport instances to the producers and consumers of a multipoint connection when the transport connection does have reverse data paths |
| 171 | Table 51 – Transport classes |
| 188 | Table 52 – UCMM_Create service parameters |
| 189 | Table 53 – UCMM_Delete service parameters |
| 190 | Table 54 – UCMM_Write service parameters |
| 191 | Table 55 – UCMM_Abort service parameters |
| 192 | Table 56 – TR_Write service parameters |
| 193 | Table 57 – TR_Trigger service parameters Table 58 – TR_Packet_arrived service parameters |
| 194 | Table 59 – TR_Ack_received service parameters Table 60 – TR_Verify service parameters |
| 195 | 6.4 Summary of FAL classes Table 61 – TR_Status_updated service parameters |
| 196 | 6.5 Permitted FAL services by AR type Table 62 – FAL class summary |
| 197 | Table 63 – FAL services by AR type |
| 198 | Bibliography |
