BS EN 61158-6-12:2012
$215.11
Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 12 elements
Published By | Publication Date | Number of Pages |
BSI | 2012 | 148 |
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 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; and.
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-12, 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-12.
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 |
11 | INTRODUCTION |
12 | 1 Scope 1.1 General |
13 | 1.2 Specifications 1.3 Conformance 2 Normative references |
14 | 3 Terms, definitions, symbols, abbreviations and conventions 3.1 Reference model terms and definitions 3.2 Service convention terms and definitions |
15 | 3.3 Application layer definitions |
20 | 3.4 Common symbols and abbreviations 3.5 Additional symbols and abbreviations |
22 | 3.6 Conventions Figures Figure 1 – Common structure of specific fields |
24 | Figure 2 – Type description example Tables Table 1 – PDU element description example |
25 | Table 2 – Example attribute description Table 3 – State machine description elements |
26 | Table 4 – Description of state machine elements Table 5 – Conventions used in state machines |
27 | 4 Application layer protocol specification 4.1 Operating principle 4.2 Node reference model |
28 | Figure 3 – Slave Node Reference Model |
29 | 5 FAL syntax description 5.1 Coding principles 5.2 Data types and encoding rules Figure 4 – Encoding of Time Of Day value |
30 | Figure 5 – Encoding of Time Difference value Table 6 – Transfer Syntax for bit sequences |
31 | Table 7 – Transfer syntax for data type Unsignedn |
32 | 5.3 AR coding Figure 6 – AL Control Request structure Table 8 – Transfer syntax for data type Integern |
33 | Figure 7 – AL Control Response structure Table 9 – AL Control Description Table 10 – AL Control Response |
34 | Table 11 – AL Status Codes |
35 | Figure 8 – AL State Changed structure Table 12 – AL State Changed |
36 | Figure 9 – PDI Control type description Figure 10 – Sync Configuration type description Table 13 – PDI Control Table 14 – PDI Configuration |
37 | 5.4 SII coding Table 15 – Sync Configuration Table 16 – Slave Information Interface Area |
38 | Table 17 – Slave Information Interface Categories Table 18 – Mailbox Protocols Supported Types |
39 | Table 19 – Categories Types Table 20 – Structure Category String |
40 | Table 21 – Structure Category General |
41 | Table 22 – Structure Category FMMU Table 23 – Structure Category SyncM for each Element |
42 | 5.5 Isochronous PDI coding Table 24 – Structure Category TXPDO and RXPDO for each PDO Table 25 – Structure PDO Entry |
43 | Figure 11 – Distributed Clock sync and latch type description |
44 | Table 26 – Distributed Clock sync parameter |
45 | Table 27 – Distributed Clock latch data |
46 | 5.6 CoE coding Figure 12 – CoE general structure Table 28 – CoE elements |
47 | Figure 13 – SDO Download Expedited Request structure |
48 | Figure 14 – SDO Download Expedited Response structure Table 29 – SDO Download Expedited Request |
49 | Figure 15 – SDO Download Normal Request structure Table 30 – SDO Download Expedited Response |
50 | Table 31 – SDO Download Normal Request |
51 | Figure 16 – Download SDO Segment Request structure Table 32 – Download SDO Segment Request |
52 | Figure 17 – Download SDO Segment Response structure Figure 18 – SDO Upload Expedited Request structure Table 33 – Download SDO Segment Response |
53 | Figure 19 – SDO Upload Expedited Response structure Table 34 – SDO Upload Expedited Request |
54 | Table 35 – SDO Upload Expedited Response |
55 | Figure 20 – SDO Upload Normal Response structure Table 36 – SDO Upload Normal Response |
56 | Figure 21 – Upload SDO Segment Request structure Figure 22 – Upload SDO Segment Response structure Table 37 – Upload SDO Segment Request |
57 | Figure 23 – Abort SDO Transfer Request structure Table 38 – Upload SDO Segment Response |
58 | Table 39 – Abort SDO Transfer Request |
59 | Table 40 – SDO Abort Codes |
60 | Figure 24 – SDO Information Service structure Figure 25 – Get OD List Request structure Table 41 – SDO Information Service |
61 | Figure 26 – Get OD List Response structure Table 42 – Get OD List Request |
62 | Table 43 – Get OD List Response |
63 | Figure 27 – Get Object Description Request structure Figure 28 – Get Object Description Response structure Table 44 – Get Object Description Request |
64 | Figure 29 – Get Entry Description Request structure Table 45 – Get Object Description Response |
65 | Figure 30 – Get Entry Description Response structure Table 46 – Get Entry Description Request |
66 | Table 47 – Get Entry Description Response |
67 | Figure 31 – SDO Info Error Request structure |
68 | Table 48 – SDO Info Error Request |
69 | Table 49 – Emergency Request |
70 | Table 50 – Emergency Error Codes Table 51 – Error Code |
71 | Table 52 – Diagnostic Data Table 53 – Sync Manager Length Error Table 54 – Sync Manager Address Error Table 55 – Sync Manager Settings Error |
72 | Table 56 – RxPDO Transmission via mailbox Table 57 – TxPDO Transmission via mailbox |
73 | Table 58 – RxPDO Remote Transmission Request Table 59 – TxPDO Remote Transmission Request |
74 | Table 60 – Command object structure Table 61 – Object Dictionary Structure Table 62 – Object Code Definitions |
75 | Table 63 – Basic Data Type Area |
76 | Table 64 – Extended Data Type Area |
77 | Table 65 – Enumeration Definition Table 66 – CoE Communication Area |
78 | Table 67 – Device Type |
79 | Table 68 – Error Register Table 69 – Manufacturer Device Name |
80 | Table 70 – Manufacturer Hardware Version Table 71 – Manufacturer Software Version Table 72 – Identity Object |
81 | Table 73 – Receive PDO Mapping Table 74 – Transmit PDO Mapping |
82 | Table 75 – Sync Manager Communication Type |
83 | Table 76 – Sync Manager Channel 0-31 |
84 | 5.7 EoE coding Figure 32 – EoE general structure Table 77 – Sync Manager Synchronization |
85 | Figure 33 – EoE Timestamp structure Table 78 – Initiate EoE Request |
86 | Figure 34 – EoE Fragment Request structure Table 79 – Initiate EoE Response |
87 | Table 80 – EoE Fragment Request |
88 | Figure 35 – Set IP Parameter Request structure Table 81 – EoE Data |
89 | Table 82 – Set IP Parameter Request |
90 | Figure 36 – Set IP Parameter Response structure Table 83 – Set IP Parameter Response |
91 | Figure 37 – Set Address Filter Request structure Table 84 – EoE Result Parameter |
92 | Table 85 – Set Address Filter Request |
93 | 5.8 FoE Coding Figure 38 – Set Address Filter Response structure Table 86 – Set Address Filter Response |
94 | Figure 39 – Read Request structure Figure 40 – Write Request structure Table 87 – Read Request |
95 | Figure 41 – Data Request structure Table 88 – Write Request |
96 | Figure 42 – Ack Request structure Table 89 – Data Request |
97 | Figure 43 – Error Request structure Table 90 – Ack Request |
98 | Table 91 – Error Request Table 92 – Error codes of FoE |
99 | 6 FAL protocol state machines 6.1 Overall structure Figure 44 – Busy Request structure Table 93 – Busy Request |
100 | Figure 45 – Relationship among Protocol Machines |
101 | 6.2 AP-Context state machine 6.3 FAL service protocol machine (FSPM) 6.4 Application Relationship Protocol Machines (ARPMs) Figure 46 – AR Protocol machines |
103 | Figure 47 – ESM Diagramm Table 94 – State transitions and local management services |
104 | Table 95 – Primitives issued by ESM to DL Table 96 – Primitives issued by DL to ESM |
105 | Table 97 – Primitives issued by Application to ESM Table 98 – Primitives issued by ESM to Application Table 99 – ESM Variables |
106 | Table 100 – ESM macros |
107 | Table 101 – ESM functions |
108 | Table 102 – ESM state table |
120 | Table 103 – ESM Functions Table 104 – Primitives issued by Mailbox handler to DL Table 105 – Primitives issued by DL to Mailbox handler |
121 | Table 106 – Primitives issued by Protocol handler to Mailbox handler Table 107 – Primitives issued by Mailbox handler to Protocol handler |
122 | Table 108 – Primitives issued by Application to CoESM |
123 | Table 109 – Primitives issued by CoESM to Application Table 110 – CoESM state table |
133 | Table 111 – Primitives issued by Application to EoESM |
134 | Table 112 – Primitives issued by EoESM to Application |
135 | Table 113 – EoESM state table |
139 | Table 114 – Primitives issued by Application to FoESM |
140 | Table 115 – Primitives issued by FoESM to Application Table 116 – FoESM state table |
144 | 6.5 DLL mapping protocol machine (DMPM) |
145 | Bibliography |