IEC 61158-6-13:2014

IEC 61158-6-13 ®
Edition 2.0 2014-08
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Industrial communication networks – Fieldbus specifications –
Part 6-13: Application layer protocol specification – Type 13 elements

Réseaux de communication industriels – Spécifications des bus de terrain –
Partie 6-13: Spécification du protocole de la couche application – Éléments
de type 13
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.

Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite
ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie
et les microfilms, sans l'accord écrit de l'IEC ou du Comité national de l'IEC du pays du demandeur. Si vous avez des
questions sur le copyright de l'IEC ou si vous désirez obtenir des droits supplémentaires sur cette publication, utilisez
les coordonnées ci-après ou contactez le Comité national de l'IEC de votre pays de résidence.

IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé Fax: +41 22 919 03 00
CH-1211 Geneva 20 info@iec.ch
Switzerland 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.

IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing more than 30 000 terms and
Technical Specifications, Technical Reports and other definitions in English and French, with equivalent terms in 14
documents. Available for PC, Mac OS, Android Tablets and additional languages. Also known as the International
iPad. Electrotechnical Vocabulary (IEV) online.

IEC publications search - www.iec.ch/searchpub IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a More than 55 000 electrotechnical terminology entries in
variety of criteria (reference number, text, technical English and French extracted from the Terms and Definitions
committee,…). It also gives information on projects, replaced clause of IEC publications issued since 2002. Some entries
and withdrawn publications. have been collected from earlier publications of IEC TC 37,

77, 86 and CISPR.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: csc@iec.ch.
A propos de l'IEC
La Commission Electrotechnique Internationale (IEC) est la première organisation mondiale qui élabore et publie des
Normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.

A propos des publications IEC
Le contenu technique des publications IEC est constamment revu. Veuillez vous assurer que vous possédez l’édition la
plus récente, un corrigendum ou amendement peut avoir été publié.

Catalogue IEC - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
Application autonome pour consulter tous les renseignements
Le premier dictionnaire en ligne de termes électroniques et
bibliographiques sur les Normes internationales,
électriques. Il contient plus de 30 000 termes et définitions en
Spécifications techniques, Rapports techniques et autres
anglais et en français, ainsi que les termes équivalents dans
documents de l'IEC. Disponible pour PC, Mac OS, tablettes
14 langues additionnelles. Egalement appelé Vocabulaire
Android et iPad.
Electrotechnique International (IEV) en ligne.

Recherche de publications IEC - www.iec.ch/searchpub
Glossaire IEC - std.iec.ch/glossary
Plus de 55 000 entrées terminologiques électrotechniques, en
La recherche avancée permet de trouver des publications IEC
en utilisant différents critères (numéro de référence, texte, anglais et en français, extraites des articles Termes et
comité d’études,…). Elle donne aussi des informations sur les Définitions des publications IEC parues depuis 2002. Plus
projets et les publications remplacées ou retirées. certaines entrées antérieures extraites des publications des

CE 37, 77, 86 et CISPR de l'IEC.
IEC Just Published - webstore.iec.ch/justpublished

Service Clients - webstore.iec.ch/csc
Restez informé sur les nouvelles publications IEC. Just
Published détaille les nouvelles publications parues. Si vous désirez nous donner des commentaires sur cette
Disponible en ligne et aussi une fois par mois par email. publication ou si vous avez des questions contactez-nous:
csc@iec.ch.
IEC 61158-6-13 ®
Edition 2.0 2014-08
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Industrial communication networks – Fieldbus specifications –

Part 6-13: Application layer protocol specification – Type 13 elements

Réseaux de communication industriels – Spécifications des bus de terrain –

Partie 6-13: Spécification du protocole de la couche application – Éléments

de type 13
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
CODE PRIX XB
ICS 25.040.40; 35.100.70; 35.110 ISBN 978-2-8322-1763-4

– 2 – IEC 61158-6-13:2014 © IEC 2014
CONTENTS
FOREWORD . 5
INTRODUCTION . 7
1 Scope . 8
1.1 General . 8
1.2 Specifications . 8
1.3 Conformance . 9
2 Normative references . 9
3 Terms, definitions, symbols, abbreviations and conventions . 9
3.1 ISO/IEC 7498-1 terms . 10
3.2 ISO/IEC 8822 terms . 10
3.3 ISO/IEC 9545 terms . 10
3.4 ISO/IEC 8824-1 terms . 10
3.5 Terms and definitions from IEC 61158-5-13 . 11
3.6 Other terms and definitions . 11
3.7 Abbreviations and symbols . 11
4 FAL syntax description . 12
4.1 General . 12
4.2 FAL-AR PDU abstract syntax . 12
4.3 Abstract syntax of Asyn1 pduBody . 15
4.4 Abstract syntax of Asyn2 pduBody . 16
5 Transfer syntax . 23
5.1 Encoding of data types . 23
6 FAL protocol state machines . 27
7 AP context state machine . 28
8 FAL service protocol machine . 28
9 AR protocol machine . 29
9.1 Buffered-network-scheduled bi-directional pre-established connection (BNB-
PEC) ARPM . 29
9.2 Buffered-network-scheduled uni-directional pre-established connection
(BNU-PEC) ARPM . 31
9.3 Queued user-triggered uni-directional (QUU) ARPM . 33
9.4 Queued user-triggered bi-directional connectionless (QUB-CL) ARPM . 36
9.5 Queued user-triggered bi-directional connection-oriented with segmentation
(QUB-COS) ARPM . 40
10 DLL mapping protocol machine . 58
10.1 Primitive definitions . 58
10.2 DMPM state machine . 59
Annex A (normative) Constant value assignments. 61
A.1 Values of abort-code . 61
A.2 NMT-command-ID . 62
A.3 Type 13 specific error-code constants . 62
A.4 Node-list. 64
Bibliography . 65

Figure 1 – Encoding of Time of Day value . 26

Figure 2 – Encoding of Time Difference value . 27
Figure 3 – Primitives exchanged between protocol machines . 28
Figure 4 – State transition diagram of BNB-PEC ARPM . 30
Figure 5 – State transition diagram of BNU-PEC ARPM . 32
Figure 6 – State transition diagram of QUU ARPM . 35
Figure 7 – State transition diagram of QUB-CL ARPM . 38
Figure 8 – State transition diagram of QUB-COS (CmdL) ARPM . 43
Figure 9 – State transition diagram of QUB-COS (SeqL) ARPM . 55
Figure 10 – State transition diagram of DMPM . 59

Table 1 – Use of signaling-flags . 14
Table 2 – Values of error-type. 18
Table 3 – Transfer syntax for bit sequences . 23
Table 4 – Transfer syntax for data type UNSIGNEDn . 24
Table 5 – Transfer syntax for data type INTEGERn . 25
Table 6 – Primitives issued by user to BNB-PEC ARPM . 29
Table 7 – Primitives issued by BNB-PEC ARPM to user . 29
Table 8 – BNB-PEC ARPM state table – sender transactions . 30
Table 9 – BNB-PEC ARPM state table – receiver transactions . 31
Table 10 – Function BuildFAL-PDU . 31
Table 11 – Primitives issued by user to BNU-PEC ARPM . 31
Table 12 – Primitives issued by BNU-PEC ARPM to user . 31
Table 13 – BNU-PEC ARPM state table – sender transactions . 33
Table 14 – BNU-PEC ARPM state table – receiver transactions . 33
Table 15 – Function BuildFAL-PDU . 33
Table 16 – Primitives issued by user to QUU ARPM . 33
Table 17 – Primitives issued by QUU ARPM to user . 34
Table 18 – QUU ARPM state table – sender transactions . 35
Table 19 – QUU ARPM state table – receiver transactions . 35
Table 20 – Function BuildFAL-PDU . 36
Table 21 – Primitives issued by user to QUB-CL ARPM . 36
Table 22 – Primitives issued by QUB-CL ARPM to user . 37
Table 23 – QUB-CL ARPM state table – sender transactions . 39
Table 24 – QUB-CL ARPM state table – receiver transactions . 40
Table 25 – Function BuildFAL-PDU . 40
Table 26 – Primitives issued by user to QUB-COS (CmdL) ARPM . 41
Table 27 – Primitives issued by QUB-COS (CmdL) ARPM to user . 42
Table 28 – QUB-COS (CmdL) ARPM state table – sender transactions . 44
Table 29 – QUB-COS (CmdL) ARPM state table – receiver transactions . 49
Table 30 – Function BuildSegment . 51
Table 31 – Function RoundUp . 51
Table 32 – Function MoreFollows . 51

– 4 – IEC 61158-6-13:2014 © IEC 2014
Table 33 – Function AddSegment . 52
Table 34 – Function GetIntermediatePDU . 52
Table 35 – Primitives issued by QUB-COS (CmdL) to QUB-COS (SeqL) . 52
Table 36 – Primitives issued by QUB-COS (SeqL) to QUB-COS (CmdL) . 53
Table 37 – Parameters used with primitives exchanged between QUB-COS (SeqL)
and QUB-COS (CmdL) . 53
Table 38 – QUB-COS (SeqL) ARPM states . 54
Table 39 – QUB-COS (SeqL) ARPM state table – sender transactions . 55
Table 40 – QUB-COS (SeqL) ARPM state table – receiver transactions . 56
Table 41 – Function BuildFAL-PDU . 58
Table 42 – Function IncrementCounter . 58
Table 43 – Function AddToHistoryBuffer . 58
Table 44 – Primitives issued by ARPM to DMPM . 58
Table 45 – Primitives issued by DMPM to ARPM . 58
Table 46 – Primitives issued by DMPM to data-link layer . 59
Table 47 – Primitives issued by data-link layer to DMPM . 59
Table 48 – DMPM state table – sender transactions . 60
Table 49 – DMPM state table – receiver transactions . 60
Table A.1 – Values of abort-code . 61
Table A.2 – Values of NMTCommandID . 62
Table A.3 – Type 13 specific error-code constants . 63
Table A.4 – Node-list format . 64

INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 6-13: Application layer protocol specification –
Type 13 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.
Attention is drawn to the fact that the use of the associated protocol type is restricted by its
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 layer protocol Type
to be used with other layer protocols of the same Type, or in other Type combinations
explicitly authorized by its intellectual-property-right holders.
NOTE Combinations of protocol Types are specified in IEC 61784-1 and IEC 61784-2.
International Standard IEC 61158-6-13 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:
– 6 – IEC 61158-6-13:2014 © IEC 2014
• addition of synchronization feature,
• corrections and
• editorial improvements.
The text of this standard is based on the following documents:
FDIS Report on voting
65C/764/FDIS 65C/774/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.
The list of all the parts of the IEC 61158 series, 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.
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 61158-1.
The application protocol provides the application service by making use of the services
available from the data-link or other immediately lower layer. The primary aim of this standard
is to provide a set of rules for communication expressed in terms of the procedures to be
carried out by peer application entities (AEs) at the time of communication. These rules for
communication are intended to provide a sound basis for development in order to serve a
variety of purposes:
– as a guide for implementors and designers;
– for use in the testing and procurement of equipment;
– as part of an agreement for the admittance of systems into the open systems environment;
– as a refinement to the understanding of time-critical communications within OSI.
This standard is concerned, in particular, with the communication and interworking of sensors,
effectors and other automation devices. By using this standard together with other standards
positioned within the OSI or fieldbus reference models, otherwise incompatible systems may
work together in any combination.

– 8 – IEC 61158-6-13:2014 © IEC 2014
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 6-13: Application layer protocol specification –
Type 13 elements
1 Scope
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 13 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 specifies interactions between remote applications and defines the externally
visible behavior provided by the Type 13 fieldbus application layer in terms of
a) the formal abstract syntax defining the application layer protocol data units conveyed
between communicating application entities;
b) the transfer syntax defining encoding rules that are applied to the application layer
protocol data units;
c) the application context state machine defining the application service behavior visible
between communicating application entities;
d) 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
1) define the wire-representation of the service primitives defined in IEC 61158-5-13, and
2) define the externally visible behavior associated with their transfer.
This standard specifies the protocol of the Type 13 fieldbus application layer, in conformance
with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI application layer structure
(ISO/IEC 9545).
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-13.
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 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.
Conformance is achieved through implementation of this application layer protocol
specification.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
NOTE All parts of the IEC 61158 series, as well as IEC 61784-1 and IEC 61784-2 are maintained simultaneously.
Cross-references to these documents within the text therefore refer to the editions as dated in this list of normative
references.
IEC 61158-3-13, Industrial communication networks – Fieldbus specifications – Part 3-13:
Data-link layer service definition – Type 13 elements
IEC 61158-4-13, Industrial communication networks – Fieldbus specifications – Part 4-13:
Data-link layer protocol specification – Type 13 elements
IEC 61158-5-13, Industrial communication networks – Fieldbus specifications – Part 5-13:
Application layer service definition – Type 13 elements
ISO/IEC 7498 (all parts), Information technology – Open Systems Interconnection – Basic
Reference Model
ISO/IEC 7498-1, Information technology – Open Systems Interconnection – Basic Reference
Model: The Basic Model
ISO/IEC 8802-3, Information technology – Telecommunications and information exchange
between systems – Local and metropolitan area networks – Specific requirements – Part 3:
Carrier sense multiple access with collision detection (CSMA/CD) access method and
physical layer specifications
ISO/IEC 8822, Information technology – Open Systems Interconnection – Presentation
service definition
ISO/IEC 8824-1, Information technology – Abstract Syntax Notation One (ASN.1):
Specification of basic notation
ISO/IEC 9545, Information technology – Open Systems Interconnection – Application Layer
structure
ISO/IEC 9899, Information technology – Programming languages – C
IEEE 754, IEEE Standard for Floating-Point Arithmetic
3 Terms, definitions, symbols, abbreviations and conventions
For the purposes of this document, the following terms, definitions, symbols, abbreviations
and conventions apply.
– 10 – IEC 61158-6-13:2014 © IEC 2014
3.1 ISO/IEC 7498-1 terms
This standard is partly based on the concepts developed in ISO/IEC 7498-1, and makes use
of the following terms defined therein:
3.1.1 application entity
3.1.2 application process
3.1.3 application protocol data unit
3.1.4 application service element
3.1.5 application entity invocation
3.1.6 application transaction
3.1.7 transfer syntax
3.2 ISO/IEC 8822 terms
For the purposes of this document, the following term as defined in ISO/IEC 8822 applies:
3.2.1 abstract syntax
3.3 ISO/IEC 9545 terms
For the purposes of this document, the following terms as defined in ISO/IEC 9545 apply:
3.3.1 application-context
3.3.2 application-process-type
3.3.3 application-service-element
3.3.4 application control service element

3.4 ISO/IEC 8824-1 terms
For the purposes of this document, the following terms as defined in ISO/IEC 8824-1 apply:
3.4.1 any type
3.4.2 bitstring type
3.4.3 boolean type
3.4.4 choice type
3.4.5 false
3.4.6 integer type
3.4.7 module
3.4.8 null type
3.4.9 object identifier
3.4.10 octetstring type
3.4.11 production
3.4.12 simple type
3.4.13 sequence of type
3.4.14 sequence type
3.4.15 structured type
3.4.16 tag
3.4.17 tagged type
3.4.18 true
3.4.19 type
3.5 Terms and definitions from IEC 61158-5-13
3.5.1 application relationship
3.5.2 client
3.5.3 error class
3.5.4 publisher
3.5.5 server
3.5.6 subscriber
3.6 Other terms and definitions
The following terms and definitions are used in this standard:
3.6.1
receiving
service user that receives a confirmed primitive or an unconfirmed primitive, or a service
provider that receives a confirmed APDU or an unconfirmed APDU
3.6.2
resource
processing or information capability of a subsystem
3.6.3
sending
service user that sends a confirmed primitive or an unconfirmed primitive, or a service
provider that sends a confirmed APDU or an unconfirmed APDU
3.6.4
managing node
node that can manage the SCNM mechanism
3.6.5
controlled node
node without the ability to manage the SCNM mechanism
3.7 Abbreviations and symbols
AE Application entity
AL Application layer
AP Application process
APDU Application protocol data unit
AR Application relationship
AREP Application relationship end point
ARPM Application relationship protocol machine
ASnd Asynchronous Send (Type 13 frame type)
BNB-PEC Buffered network-scheduled bi-directional pre-established connection
BNU-PEC Buffered network-scheduled uni-directional pre-established connection
CmdL Command layer
CN Controlled node
– 12 – IEC 61158-6-13:2014 © IEC 2014
cnf confirmation
DL- (as a prefix) data-link-
DLCEP Data-link connection end point
DLL Data-link layer
DLME Data-link-management entity
DLSAP Data-link service access point
DLSDU DL-service-data-unit
DMPM DLL mapping protocol machine
DNS Domain name service
FAL Fieldbus application layer
ind indication
IP Internet protocol (see RFC 791)
MAC Media access controll
MN Managing node
NMT Network management
OD Object dictionary
PDO Process data object
PDU Process data unit
QUB-CL Queued user-triggered bi-directional connectionless
QUB-COS Queued user-triggered bi-directional connection-oriented with
segmentation
QUU Queued user-triggered uni-directional
req request
rsp response
SDO Service data object
SeqL Sequence layer
UDP User datagram protocol
4 FAL syntax description
4.1 General
This description of the Type 13 abstract syntax uses formalisms similar to ASN.1, although
the encoding rules differ from that standard.
4.2 FAL-AR PDU abstract syntax
4.2.1 Top level definition
APDU ::= CHOICE {
[3] Isoc1
[4] Isoc2
[5] Asyn1
[6] Asyn2
}
4.2.2 Isoc1
Isoc1 ::= SEQUENCE {
message-type
destination
source
reserved
signaling-flags
PDO-version
reserved8
size
PDO-payload
}
4.2.3 Isoc2
Isoc2 ::= SEQUENCE {
message-type
destination
source
NMT-status
signaling-flags
PDO-version
reserved8
size
PDO-payload
}
4.2.4 Asyn1
Asyn1 ::= SEQUENCE {
message-type
destination
source
NMT-status
signaling-flags
requested-service-ID
requested-service-target
fieldbus-version
reserved8
pduBody CHOICE{
[1h…5h] reserved
[6h] Sync-request
[7h.FFh] reserved
}
}
4.2.5 Asyn2
Asyn2 ::= SEQUENCE {
message-type
destination
source
service-ID
pduBody CHOICE {
[1h] ident-response
[2h] status-response
[3h] NMT-request
[4h] NMT-command
[5h] SDO
[6h] Sync-response
[A0h…FEh] manufacturer-specific
[FFh] reserved
}
}
4.2.6 Message-type
message-type ::= Unsigned8  — Contains the context specific APDU tags

– 14 – IEC 61158-6-13:2014 © IEC 2014
4.2.7 Addresses
destination ::= Unsigned8  — Node address (1…255)
source ::= Unsigned8   — Node address (1…250, 253, 254)

4.2.8 Service-ID
service-ID ::= Unsigned8   — Contains the context specific tags for the pduBody

4.2.9 Reserved8
reserved8 ::= Unsigned8
4.2.10 Reserved16
reserved16 ::= Unsigned16
4.2.11 Reserved24
reserved24 ::= Unsigned24
4.2.12 Signaling-flags
signaling-flags ::= BitString {
RD  (0)
ER  (1)
EA  (2)
EC  (3)
EN  (4)
MS  (5)
PS  (6)
MC  (7)
RS_bit1 (8)
RS_bit2 (9)
RS_bit3 (10)
PR_bit1 (11)
PR_bit2 (12)
PR_bit3 (13)
reserved (14)
reserved (15)
}
The different APDU types use the flags as listed in Table 1. In all cases without "x" the flags
are present but not written resp. interpreted.
Table 1 – Use of signaling-flags
Isoc1 Isoc2 Asyn1 IdentResponse StatusResponse SyncResponse
RD x x
ER  x
EA x x
EC   x
EN x  x
MS x x
PS
MC
RS x x x x
PR x x x x
The usage of these flags is specified in IEC 61158-3-13 and IEC 61158-4-13.

4.2.13 PDO-version
PDO-version ::= Unsigned8  — High nibble: main version; low nibble: sub version

4.2.14 Size
size ::= Unsigned8   — Size of PDO payload; max. 1490 octets due to
Ethernet restrictions and protocol overhead

4.2.15 PDO-payload
PDO-payload ::= Any
4.2.16 NMT-status
NMT-status ::= CHOICE {
NMT_GS_OFF   Unsigned8 ::= 0000 0000b
NMT_xS_NOT_ACTIVE Unsigned8 ::= 0001 1100b
NMT_xS_PRE_OPERATIONAL_1 Unsigned8 ::= 0001 1101b
NMT_xS_PRE_OPERATIONAL_2 Unsigned8 ::= 0101 1101b
NMT_xS_READY_TO_OPERATE Unsigned8 ::= 0110 1101b
NMT_xS_OPERATIONAL Unsigned8 ::= 1111 1101b
NMT_xS_STOPPED  Unsigned8 ::= 0100 1101b
NMT_xS_BASIC_ETHERNET Unsigned8 ::= 0001 1110b
}
NOTE If sender = MN: "x" := "M"; if sender = CN: "x" := "C".

4.2.17 Requested-service-ID
requested-service-ID ::= CHOICE {
no-service   [0h] IMPLICIT Unsigned8
ident-request   [1h] IMPLICIT Unsigned8
status-request   [2h] IMPLICIT Unsigned8
NMT-req-inv   [3h] IMPLICIT Unsigned8
manufacturer-specific  [A0h]… [FEh] IMPLICIT Unsigned8
unspecified-invite  [FFh] IMPLICIT Unsigned8
}
4.2.18 Requested-service-target
requested-service-target ::= Unsigned8  — Node address (1…255); not assigned (0)

4.2.19 Fieldbus-version
fieldbus-version ::= Unsigned8  — High nibble: main version; low nibble: sub version

4.3 Abstract syntax of Asyn1 pduBody
4.3.1 Sync-request
4.3.1.1 Overview
Sync-request ::= SEQUENCE {
synchronization-control Bitstring — see 4.3.1.2
PRes-time  Unsigned32 — time delay between end of the reception of the PRes from MN
and start of sending the own time-triggered PRes in ns
reserved  Unsigned32
sync-MN-delay  Unsigned32 — propagation delay between MN and CN in ns
reserved  Unsigned32
fallback-timeout  Unsigned32 — SoC timeout for deactivating the time-triggered sending of PRes
in state NMT_CS_PRE_OPERATIONAL_2 in ns
destination-MAC-address Unsigned32 — destination MAC address of the node the Sync-request is sent to
}
NOTE The above listed elements are sometimes summarized as follows:
"synchronization-control" through "destination-MAC-address" are summarized under the term "sync-control".

– 16 – IEC 61158-6-13:2014 © IEC 2014

4.3.1.2 Synchronization-control
Synchronization-control ::= Bitstring {
PRes-time-valid  (0) — The parameter PRes-time is valid
Reserved bit1  (1)
sync-MN-delay-valid (2) — The parameter sync-MN-delay is valid
reserved bit2  (3)
fallback-timeout-valid (4) — The parameter fallback-timeout is valid
reserved bit3  (5)
MAC-address-valid (4) — The parameter destination-MAC-address is valid
reserved bit4 through bit26 (7)…(29)
PRes-mode-reset  (30) — Deactivate the time-triggered sending of PRes
PRes-mode-set  (31) — Activate the time-triggered sending of PRes. This bit overules
bit30
}
4.4 Abstract syntax of Asyn2 pduBody
4.4.1 Ident-response
4.4.1.1 Overview
Ident-response ::= SEQUENCE {
signaling-flags
NMT-status
reserved8
fieldbus-version
reserved8
feature-flags  BitString  — (see 4.4.1.2)
MTU   Unsigned16 — size of the largest possible IP frame incl. header
poll-in-size  Unsigned16 — actual CN setting for Isoc1 data block size
poll-out-size   Unsigned16 — actual CN setting for Isoc2 data block size
response-time  Unsigned32 — time required by the CN to respond to Isoc1
reserved16
device-type  Unsigned32 — CN’s device type
vendor-ID   Unsigned32 — CN’s vendor ID
product-code   Unsigned32 — CN’s product code
revision-number  Unsigned32 — CN’s revision number
serial-number   Unsigned32 — CN’s serial number
vendor-specific-extension-1 Unsigned64 — for vendor specific purpose, to be filled with zeros if not used
verify-configuration-date Unsigned32 — CN’s configuration date
verify-configuration-time Unsigned32 — CN’s configuration time
application-sw-date  Unsigned32 — CN’s application software date
application-sw-time  Unsigned32 — CN’s application software time
IP-address   Unsigned32 — current IP address value of the CN
subnet-mask   Unsigned32 — current IP subnet mask of the CN
default-gateway  Unsigned32 — current IP default gateway of the CN
host-name   VisibleString32 — current DNS host name of the CN
vendor-specific-extension-2 SEQUENCE SIZE(48) OF Unsigned8
—for vendor specific purpose, to be filled with zeros if not in use
}
NOTE Some of the above listed elements are sometimes summarized as follows:
"poll-in-size" through "response-time" are summarized under the term "cycle-timing",
"device-type" through "serial-number" under "identity",
"verify-configuration-date" and "verify-configuration-time" under "verify-configuration",
"application-sw-date" and "application-sw-time" under "application-software-version",
"vendor-specific-extension-1" and "vendor-specific-extension-2" under "vendor-specific-extensions",
"IP-address" through "default-gateway" under "IP-address".

4.4.1.2 Feature-flags
feature-flags ::= BitString {
Isochronous   (0)  — device may be isochronously accessed via Isoc1
SDO by UDP/IP  (1)  — device supports SDO communication via UDP/IP
SDO by ASnd   (2)  — device supports SDO communication via ASnd
reserved for future use (3)
NMT-info services  (4)  — device supports NMT Info Services
Extended NMT-state-commands (5)  — device supports Extended NMT State Commands
Dynamic PDO mapping (6)  — device supports dynamic PDO Mapping
NMT services by UDP/IP (7)  — device supports NMT Services by UDP/IP
Configuration manager (8)  — device supports Configuration Manager functions
Multiplexed access  (9)  — CN device supports multiplexed isochronous access.
Node-ID setup by SW  (10)  — device supports NodeID setup by software
MN basic ethernet mode (11)  — MN device supports Basic Ethernet Mode
Routing Type 1 support (12)  — device supports Routing Type 1 functions
Routing Type 2 support (13)  — device supports Routing Type 2 functions
WriteMultipleByIndex  (14) — device supports WriteMultipleByIndex SDO service
ReadMultipleByIndex  (15) — device supports ReadMultipleByIndex SDO service
reserved bit1 through bit2 (16)…(17)
Time-triggered PRes  (18) — device supports time-triggered sending of PRes
reserved bit3 through bit16 (19)…(31)
}
4.4.2 Status-response
4.4.2.1 Overview
Status-response ::= SEQUENCE {
signaling-flags
NMT-status
reserved24
static-error-bit-field
List-of-errors
}
4.4.2.2 Static-error-bitfield
static-error
...