IEC 61158-5-2:2010

IEC 61158-5-2
®
Edition 2.0 2010-08
INTERNATIONAL
STANDARD

colour
inside

Industrial communication networks – Fieldbus specifications –
Part 5-2: Application layer service definition – Type 2 elements



IEC 61158-5-2:2010(E)

---------------------- Page: 1 ----------------------
THIS PUBLICATION IS COPYRIGHT PROTECTED
Copyright © 2010 IEC, Geneva, Switzerland

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication,
please contact the address below or your local IEC member National Committee for further information.

IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: inmail@iec.ch
Web: www.iec.ch

About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
ƒ Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
ƒ IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
ƒ Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
ƒ Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00

---------------------- Page: 2 ----------------------
IEC 61158-5-2
®
Edition 2.0 2010-08
INTERNATIONAL
STANDARD

colour
inside

Industrial communication networks – Fieldbus specifications –
Part 5-2: Application layer service definition – Type 2 elements


INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XH
ICS 25.04.40; 35.100.70; 35.110 ISBN 978-2-88912-105-2
® Registered trademark of the International Electrotechnical Commission

---------------------- Page: 3 ----------------------
– 2 – 61158-5-2 © IEC:2010(E)
CONTENTS
FOREWORD.5
INTRODUCTION.7
1 Scope.8
1.1 Overview .8
1.2 Specifications.9
1.3 Conformance.9
2 Normative references .9
3 Terms, definitions, symbols, abbreviations and conventions .10
3.1 ISO/IEC 7498-1 terms .10
3.2 ISO/IEC 8822 terms .11
3.3 ISO/IEC 9545 terms .11
3.4 ISO/IEC 8824 terms .11
3.5 Type 2 fieldbus data-link layer terms .11
3.6 Type 2 fieldbus application-layer specific definitions.11
3.7 Type 2 abbreviations and symbols.18
3.8 Conventions .19
4 Common concepts.22
5 Data type ASE.22
5.1 General .22
5.2 Formal definition of data type objects .22
5.3 FAL defined data types.22
5.4 Data type ASE service specification .32
6 Communication model specification.32
6.1 Concepts.32
6.2 ASEs.40
6.3 ARs .155
6.4 Summary of FAL classes .192
6.5 Permitted FAL services by AR type .193
Bibliography.195

Figure 1 – Overview of ASEs and object classes .34
Figure 2 – Addressing format using MAC, class, instance and attribute IDs .35
Figure 3 – Identity object state transition diagram .52
Figure 4 – Static Assembly state transition diagram .57
Figure 5 – Dynamic Assembly state transition diagram .58
Figure 6 – Typical timing relationships for acknowledged data production.67
Figure 7 – Example of a COS system with two acking devices .67
Figure 8 – Message flow in COS connection – one Connection object, one consumer.67
Figure 9 – Message flow in COS connection – multiple consumers .68
Figure 10 – CPF2 time synchronization offset clock model.80
Figure 11 – CPF2 time synchronization system with offset clock model .80
Figure 12 – CPF2 time synchronization group startup sequence .83
Figure 13 – Parameter object state transition diagram .89

---------------------- Page: 4 ----------------------
61158-5-2 © IEC:2010(E) – 3 –
Figure 14 – Example of Find_Next_Object_Instance service . 114
Figure 15 – Transmission trigger timer.149
Figure 16 – Inactivity watchdog timer.150
Figure 17 – Using tools for configuration.151
Figure 18 – Production inhibit timer .152
Figure 19 – Context of transport services within the connection model. 158
Figure 20 – Application–to–application view of data transfer . 158
Figure 21 – Data flow diagram for a link producer .159
Figure 22 – Data flow diagram for a link consumer.160
Figure 23 – Triggers .161
Figure 24 – Binding transport instances to the producer and consumer of a transport
connection that does not have a reverse data path .162
Figure 25 – Binding transport instances to the producers and consumers of a transport
connection that does have a reverse data path . 162
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 . 163
Figure 27 – Binding transport instances to the producers and consumers of a
multipoint connection when the transport connection does have reverse data paths .163

Table 1 – Valid IANA MIB printer codes for character set selection .31
Table 2 – Common elements .37
Table 3 – ST language elements.38
Table 4 – Type conversion operations.38
Table 5 – Values of implementation-dependent parameters .39
Table 6 – Extensions to IEC 61131-3:2003 .40
Table 7 – Identity object state event matrix .53
Table 8 – Static Assembly state event matrix .57
Table 9 – Dynamic Assembly state event matrix .58
Table 10 – Message Router object Forward_Open parameters .61
Table 11 – Acknowledge Handler object state event matrix.64
Table 12 – Producing I/O application object state event matrix .65
Table 13 – Profile identification.77
Table 14 – Profile default settings and ranges .77
Table 15 – Default PTP clock settings.78
Table 16 – Hand_Set clock quality management .79
Table 17 – Parameter object state event matrix .89
Table 18 – Status codes .92
Table 19 – Get_Attribute_All service parameters .94
Table 20 – Set_Attribute_All service parameters.95
Table 21 – Get_Attribute_List service parameters.97
Table 22 – Set_Attribute_List service parameters .99
Table 23 – Reset service parameters.101
Table 24 – Start service parameters .103
Table 25 – Stop service parameters.105

---------------------- Page: 5 ----------------------
– 4 – 61158-5-2 © IEC:2010(E)
Table 26 – Create service parameters .106
Table 27 – Delete service parameters.108
Table 28 – Get_Attribute_Single service parameters. 109
Table 29 – Set_Attribute_Single service parameters . 111
Table 30 – Find_Next_Object_Instance service parameters . 112
Table 31 – NOP service parameters .115
Table 32 – Apply_Attributes service parameters . 116
Table 33 – Save service parameters .118
Table 34 – Restore service parameters.119
Table 35 – Group_Sync service parameters.121
Table 36 – Add_AckData_Path service parameters.123
Table 37 – Remove_AckData_Path service parameters . 124
Table 38 – Get-Enum_String service parameters .125
Table 39 – CM_Open service parameters .133
Table 40 – CM_Close service parameters.135
Table 41 – CM_ Unconnected_Send service parameters . 137
Table 42 – CM_Get_Connection_Data service parameters . 139
Table 43 – CM_Search_Connection_Data service parameters . 140
Table 44 – CM_Get_Connection_Data service parameters . 141
Table 45 – I/O Connection object attribute access .146
Table 46 – Bridged Connection object attribute access .147
Table 47 – Explicit messaging object attribute access. 148
Table 48 – Connection_Bind service parameters . 153
Table 49 – Service_Name service parameters .154
Table 50 – How production trigger, transport class, and CM_RPI determine when data
is produced.157
Table 51 – Transport classes .168
Table 52 – UCMM_Create service parameters .185
Table 53 – UCMM_Delete service parameters .186
Table 54 – UCMM_Write service parameters .187
Table 55 – UCMM_Abort service parameters .188
Table 56 – TR_Write service parameters .189
Table 57 – TR_Trigger service parameters .190
Table 58 – TR_Packet_arrived service parameters .190
Table 59 – TR_Ack_received service parameters. 191
Table 60 – TR_Verify service parameters .191
Table 61 – TR_Status_updated service parameters .192
Table 62 – FAL class summary .193
Table 63 – FAL services by AR type .194

---------------------- Page: 6 ----------------------
61158-5-2 © IEC:2010(E) – 5 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________

INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –

Part 5-2: Application layer service definition –
Type 2 elements


FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
NOTE 1 Use of some of the associated protocol types is restricted by their intellectual-property-right holders. In
all cases, the commitment to limited release of intellectual-property-rights made by the holders of those rights
permits a particular data-link layer protocol type to be used with physical layer and application layer protocols in
Type combinations as specified explicitly in the IEC 61784 series. Use of the various protocol types in other
combinations may require permission from their respective intellectual-property-right holders.
International Standard IEC 61158-5-2 has been prepared by subcommittee 65C: Industrial
networks, of IEC technical committee 65: Industrial-process measurement, control and
automation.
This second edition cancels and replaces the first edition published in 2007. This edition
constitutes a technical revision.
The main changes with respect to the previous edition are listed below:
• Clause 2 and Bibliography: update of normative and bibliographic references

---------------------- Page: 7 ----------------------
– 6 – 61158-5-2 © IEC:2010(E)
• subclause 6.1.3: update lists with new objects
• subclause 6.2.1.2.6: update of the Time Sync ASE/object (to match new IEC 61558)
• new subclause 6.2.1.2.7: new Parameter ASE/object
• subclause 6.2.1.3: update/add services for Time Sync and Parameter ASEs
• subclause 6.2.2.3: minor updates to the Connection Manager ASE services
• subclause 6.4: add Parameter ASE to the object table
• subclause 6.5: update contents of service table for Time Sync and Parameter ASEs
The text of this standard is based on the following documents:
FDIS Report on voting
65C/606/FDIS 65C/620/RVD

Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with ISO/IEC Directives, Part 2.
A list of all parts of the IEC 61158 series, published under the general title Industrial
communication networks – Fieldbus specifications, can be found on the IEC web site.
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC web site under "http://webstore.iec.ch" in the data
related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
NOTE 2 The revision of this standard will be synchronized with the other parts of the IEC 61158 series.

IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.

---------------------- Page: 8 ----------------------
61158-5-2 © IEC:2010(E) – 7 –
INTRODUCTION
This part of IEC 61158 is one of a series produced to facilitate the interconnection of
automation system components. It is related to other standards in the set as defined by the
“three-layer” fieldbus reference model described in IEC/TR 61158-1.
The application service is provided by the application protocol making use of the services
available from the data-link or other immediately lower layer. This standard defines the
application service characteristics that fieldbus applications and/or system management may
exploit.
Throughout the set of fieldbus standards, the term “service” refers to the abstract capability
provided by one layer of the OSI Basic Reference Model to the layer immediately above.
Thus, the application layer service defined in this standard is a conceptual architectural
service, independent of administrative and implementation divisions.

---------------------- Page: 9 ----------------------
– 8 – 61158-5-2 © IEC:2010(E)
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –

Part 5-2: Application layer service definition –
Type 2 elements



1 Scope
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
a) an abstract model for defining application resources (objects) capable of being
manipulated by users via the use of the FAL service,
b) the primitive actions and events of the service;
c) the parameters associated with each primitive action and event, and the form which they
take; and
d) the interrelationship between these actions and events, and their valid sequences.
The purpose of this standard is to define the services provided to
a) the FAL user at the boundary between the user and the application layer of the fieldbus
reference model, and
b) 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

---------------------- Page: 10 ----------------------
61158-5-2 © IEC:2010(E) – 9 –
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
a) the sizes and octet ordering of various multi-octet service parameters, and
b) 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.
2 Normative references
The following referenced documents are indispensable for the a
...