BS EN 61158-6-22:2012
$215.11
Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 22 elements
| Published By | Publication Date | Number of Pages |
| BSI | 2012 | 92 |
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 22 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 behavior provided by the different Types of the fieldbus Application Layer in terms of:
-
the abstract syntax defining the application layer protocol data units conveyed between communicating application entities;
-
the transfer syntax defining the application layer protocol data units conveyed between communicating application entities;
-
the application context state machine defining the application service behavior visible between communicating application entities; and
-
the application relationship state machines defining the communication behavior visible between communicating application entities.
The purpose of this standard is to define the protocol provided to:
-
define the wire-representation of the service primitives defined in IEC 61158-5-22:2010; and
-
define the externally visible behavior associated with their transfer.
This standard specifies the protocol 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 syntax and behavior of the application layer protocol that conveys the application layer services defined in IEC 61158-5-22:2010.
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 protocols standardized in subparts of IEC 61158-6.
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 the application layer service definition standard. Instead, conformance is achieved through implementation of this application layer protocol specification.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 6 | CONTENTS |
| 10 | INTRODUCTION |
| 11 | 1 Scope 1.1 General |
| 12 | 1.2 Specifications 1.3 Conformance 2 Normative references |
| 13 | 3 Terms, definitions, abbreviations, symbols and conventions 3.1 Terms and definitions from other ISO/IEC standards 3.2 Fieldbus application-layer specific definitions |
| 17 | 3.3 Abbreviations and symbols |
| 19 | 3.4 Conventions |
| 20 | 4 Application layer protocol specification 4.1 Operating principle Tables Table 1 – PDU element definition Table 2 – Object definition |
| 21 | 4.2 Device reference models |
| 22 | Figures Figure 1 – RTFL device reference model |
| 23 | 4.3 Application layer structure 5 FAL syntax description 5.1 Introduction and coding principles 5.2 Data type encoding Figure 2 – RTFN device reference model |
| 24 | Figure 3 – Encoding of TimeOfDay value Table 3 – Transfer syntax for bit sequences |
| 25 | Figure 4 – Encoding of TimeDifference value |
| 26 | Table 4 – Transfer syntax for Integer data type Table 5 – Transfer syntax for Unsigned data type |
| 27 | 5.3 CeS encoding Table 6 – Object dictionary structure |
| 28 | Figure 5 – Object dictionary addressing schema Table 7 – Object dictionary object type definitions |
| 29 | Table 8 – Basic data type definitions |
| 30 | Table 9 – Complex data type definition |
| 31 | Table 10 – Communication section |
| 33 | Table 11 – Device type Table 12 – Error register encoding Table 13 – Error register |
| 34 | Table 14 – Object definition template Table 15 – Encoding of event log entries |
| 35 | Table 16 – Event log Table 17 – Manufacturer device name |
| 36 | Table 18 – Manufacturer HW version Table 19 – Manufacturer SW version Table 20 – CL configuration |
| 38 | Table 21 – Time sync IRQ configuration encoding Table 22 – Time sync IRQ configuration |
| 39 | Table 23 – Time sync IRQ state |
| 40 | Table 24 – Store parameters read information Table 25 – Store parameters |
| 41 | Table 26 – Restore parameters read information Table 27 – Restore default parameters |
| 43 | Table 28 – Diagnostic information |
| 46 | Table 29 – Diagnostic threshold |
| 47 | Table 30 – IP address EMCY |
| 48 | Table 31 – Inhibit time EMCY Table 32 – Encoding of consumer heartbeat entries |
| 49 | Table 33 – Consumer heartbeat list Table 34 – Producer heartbeat parameter |
| 51 | Table 35 – Identity object |
| 53 | Table 36 – SDO protocol timeout Table 37 – Enable client SDO parameter |
| 54 | Table 38 – Enable EMCY Table 39 – PDO timeout tolerance Table 40 – Store EDS |
| 55 | Table 41 – Storage format Table 42 – OS command |
| 56 | Table 43 – OS command mode |
| 57 | Table 44 – OS debugger interface |
| 58 | Table 45 – OS prompt |
| 59 | Table 46 – Module list Table 47 – Emergency subscriber encoding Table 48 – Emergency subscriber |
| 60 | Table 49 – Client SDO parameter encoding Table 50 – Client SDO parameter |
| 61 | Table 51 – Receive PDO communication parameter |
| 63 | Table 52 – Transmit PDO communication parameter |
| 65 | Table 53 – Mapping format Table 54 – Receive PDO mapping parameter |
| 66 | Table 55 – Transmit PDO mapping parameter |
| 67 | Table 56 – Initiate SDO expedited download request Table 57 – Initiate SDO expedited download response Table 58 – Initiate SDO normal download request |
| 68 | Table 59 – Initiate SDO normal download response Table 60 – SDO download request Table 61 – SDO download response |
| 69 | Table 62 – Initiate SDO expedited upload request Table 63 – Initiate SDO expedited upload response Table 64 – Initiate SDO normal upload response |
| 70 | Table 65 – SDO upload request Table 66 – SDO upload response Table 67 – SDO abort request Table 68 – SDO abort codes |
| 71 | Table 69 – Process data write request via MSC |
| 72 | Table 70 – Process data write request via CDC Table 71 – Emergency request Table 72 – Emergency error codes |
| 73 | Table 73 – Heartbeat request via MSC Table 74 – Heartbeat request via CDC |
| 74 | 5.4 ISO/IEC 8802-3 DLPDU communication inside Type 22 RTFL 5.5 Management encoding 6 FAL protocol state machines Figure 6 – Relationships among protocol machines and adjacent layers Table 75 – Send frame request Table 76 – Application layer management request |
| 75 | 6.1 Overview |
| 76 | 6.2 Fieldbus service protocol machine (FSPM) 6.3 Application relationship protocol machine (ARPM) 6.4 DLL mapping protocol machine Figure 7 – ALSM protocol machine |
| 77 | 7 AP-context state machine 8 FAL service protocol machine (FSPM) 9 Application layer state machine (ALSM) 9.1 Description |
| 78 | Figure 8 – ALSM diagram Table 77 – State transitions and management services |
| 79 | 9.2 States |
| 80 | 9.3 Primitive definitions Table 78 – Primitives issued by ALSM to DLL Table 79 – Primitives issued by DLL to ALSM Table 80 – Primitives issued by FSPM to ALSM Table 81 – Primitives issued by ALSM to FSPM |
| 81 | 9.4 State table 9.5 AL-service forwarding depending on AL-state Table 82 – ALSM state table |
| 82 | 10 DLL mapping protocol machine (DMPM) 10.1 Overview 10.2 Primitives exchanged between ALSM and DMPM Table 83 – Application layer states and communication services Table 84 – Primitives issued by ALSM to DMPM |
| 84 | Table 85 – Primitives issued by DMPM to ALSM |
| 86 | 10.3 Primitives exchanged between DLL and DMPM Table 86 – Primitives issued by DMPM to DLL |
| 87 | Table 87 – Primitives issued by DLL to DMPM |
| 88 | 10.4 ALSM to DLL mapping Table 88 – ALSM to DLL mapping |
| 90 | Bibliography |
