IEC 62453-303-2:2009

IEC 62453-303-2 ®
Edition 1.0 2009-06
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
FIeld device tool (FDT) interface specification –
Part 303-2: Communication profile integration – IEC 61784 CP 3/4, CP 3/5
and CP 3/6
Spécification des interfaces des outils des dispositifs de terrain (FDT) –
Partie 303-2: Intégration des profils de communication – CP 3/4, CP 3/5 et
CP 3/6 de la CEI 61784
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 la CEI ou du Comité national de la CEI du pays du demandeur.
Si vous avez des questions sur le copyright de la CEI 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 la CEI 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.

Useful links:
IEC publications search - www.iec.ch/searchpub Electropedia - www.electropedia.org
The advanced search enables you to find IEC publications The world's leading online dictionary of electronic and
by a variety of criteria (reference number, text, technical electrical terms containing more than 30 000 terms and
committee,…). definitions in English and French, with equivalent terms in
It also gives information on projects, replaced and additional languages. Also known as the International
withdrawn publications. Electrotechnical Vocabulary (IEV) on-line.

IEC Just Published - webstore.iec.ch/justpublished Customer Service Centre - webstore.iec.ch/csc
Stay up to date on all new IEC publications. Just Published If you wish to give us your feedback on this publication
details all new publications released. Available on-line and or need further assistance, please contact the
also once a month by email. Customer Service Centre: csc@iec.ch.

A propos de la CEI
La Commission Electrotechnique Internationale (CEI) 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 CEI
Le contenu technique des publications de la CEI est constamment revu. Veuillez vous assurer que vous possédez
l’édition la plus récente, un corrigendum ou amendement peut avoir été publié.

Liens utiles:
Recherche de publications CEI - www.iec.ch/searchpub Electropedia - www.electropedia.org
La recherche avancée vous permet de trouver des Le premier dictionnaire en ligne au monde de termes
publications CEI en utilisant différents critères (numéro de électroniques et électriques. Il contient plus de 30 000
référence, texte, comité d’études,…). termes et définitions en anglais et en français, ainsi que
Elle donne aussi des informations sur les projets et les les termes équivalents dans les langues additionnelles.
publications remplacées ou retirées. Egalement appelé Vocabulaire Electrotechnique
International (VEI) en ligne.
Just Published CEI - webstore.iec.ch/justpublished
Service Clients - webstore.iec.ch/csc
Restez informé sur les nouvelles publications de la CEI.
Just Published détaille les nouvelles publications parues. Si vous désirez nous donner des commentaires sur
Disponible en ligne et aussi une fois par mois par email. cette publication ou si vous avez des questions
contactez-nous: csc@iec.ch.
IEC 62453-303-2 ®
Edition 1.0 2009-06
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
FIeld device tool (FDT) interface specification –

Part 303-2: Communication profile integration – IEC 61784 CP 3/4, CP 3/5

and CP 3/6
Spécification des interfaces des outils des dispositifs de terrain (FDT) –

Partie 303-2: Intégration des profils de communication – CP 3/4, CP 3/5 et

CP 3/6 de la CEI 61784
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
CODE PRIX V
ICS 25.040.40; 35.100.05; 35.110 ISBN 978-2-8322-0995-0

– 2 – 62453-303-2  IEC:2009
CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 7
2 Normative references . 7
3 Terms, definitions, symbols, abbreviated terms and conventions . 7
3.1 Terms and definitions . 7
3.2 Abbreviated terms . 8
3.3 Conventions . 8
3.3.1 Data type names and references to data types . 8
3.3.2 Vocabulary for requirements . 8
3.3.3 Use of UML . 8
4 Bus category . 8
5 Access instance and device data . 9
5.1 Process Channel objects provided by DTM . 9
5.2 DTM services to access instance and device data . 9
6 Protocol specific behavior . 9
7 Protocol specific usage of general data types . 9
8 Protocol specific common data types . 11
9 Network management data types . 11
9.1 General . 11
9.2 Parameter access data types . 11
10 Communication data types . 17
11 Channel parameter data types . 20
12 Device identification . 23
12.1 Protocol specific handling of data type STRING . 23
12.2 Device type identification data types . 23
12.3 Topology scan data types . 26
12.4 Scan identification data types . 27
12.5 Device type identification data types . 29
Bibliography . 32

Figure 1 – Part 303-2 of the IEC 62453 series . 6

Table 1 – Protocol identifier . 8
Table 2 – Physical layer identifier . 8
Table 3 – Protocol specific usage of general data types . 9
Table 4 – Simple parameter access data types . 11
Table 5 – Structured parameter access data types. 14
Table 6 – Simple communication data types . 17
Table 7 – Structured communication data types . 18
Table 8 – Simple channel parameter data types . 21
Table 9 – Structured channel parameter data types . 22
Table 10 – Identification data types for PROFINET with pure DCP . 24

62453-303-2  IEC:2009 – 3 –
Table 11 – Identification data types for PROFINET with I&M . 25
Table 12 – Simple identification data types with protocol independent semantics . 26
Table 13 – Structured identification data types with protocol independent semantics . 26
Table 14 – Simple device type identification data types . 26
Table 15 – Structured device type identification data type . 27
Table 16 – Simple scan identification data types . 27
Table 17 – Structured scan identification data types . 28
Table 18 – Structured device type identification data types . 29

– 4 – 62453-303-2  IEC:2009
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –

Part 303-2: Communication profile integration –
IEC 61784 CP 3/4, CP 3/5 and CP 3/6

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 provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
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.
International Standard IEC 62453-303-2 has been prepared by subcommittee 65E: Devices
and integration in enterprise systems, of IEC technical committee 65: Industrial-process
measurement, control and automation.
This part, in conjunction with the other parts of the first edition of the IEC 62453 series
cancels and replaces IEC/PAS 62453-1, IEC/PAS 62453-2, IEC/PAS 62453-3, IEC/PAS
62453-4 and IEC/PAS 62453-5 published in 2006, and constitutes a technical revision.
Each part of the IEC 62453-3xy series is intended to be read in conjunction with IEC 62453-2.
This bilingual version (2013-07) corresponds to the monolingual English version, published in
2009-06.
62453-303-2  IEC:2009 – 5 –
The text of this standard is based on the following documents:
FDIS Report on voting
65E/128/FDIS 65E/141/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.
The French version of this standard has not been voted upon.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts of the IEC 62453 series, under the general title Field Device Tool (FDT)
interface specification, can be found on the IEC website.
The committee has decided that the contents of this publication will remain unchanged until
the maintenance result 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.
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.
– 6 – 62453-303-2  IEC:2009
INTRODUCTION
This part of IEC 62453 is an interface specification for developers of FDT (Field Device Tool)
components for function control and data access within a client/server architecture. The
specification is a result of an analysis and design process to develop standard interfaces to
facilitate the development of servers and clients by multiple vendors that need to interoperate
seamlessly.
With the integration of fieldbusses into control systems, there are a few other tasks which
need to be performed. In addition to fieldbus- and device-specific tools, there is a need to
integrate these tools into higher-level system-wide planning- or engineering tools. In
particular, for use in extensive and heterogeneous control systems, typically in the area of the
process industry, the unambiguous definition of engineering interfaces that are easy to use for
all those involved is of great importance.
A device-specific software component, called DTM (Device Type Manager), is supplied by the
field device manufacturer with its device. The DTM is integrated into engineering tools via the
FDT interfaces defined in this specification. The approach to integration is in general open for
all kinds of fieldbusses and thus meets the requirements for integrating different kinds of
devices into heterogeneous control systems.
Figure 1 shows how IEC 62453-303-2 is aligned in the structure of the IEC 62453 series.
Part 303-2
Communication
profile integration –
IEC 61784 CP 3/4,
CP 3/5 and CP 3/6
IEC  1132/09
Figure 1 – Part 303-2 of the IEC 62453 series

62453-303-2  IEC:2009 – 7 –
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –

Part 303-2: Communication profile integration –
IEC 61784 CP 3/4, CP 3/5 and CP 3/6

1 Scope
Communication Profile 3/4, Communication Profile 3/5 and Communication Profile 3/6
(commonly known as PROFINET® IO) define communication profiles based on
IEC 61158-5-10 and IEC 61158-6-10. The basic profiles CP 3/4, CP 3/5, and CP 3/6 are
defined in IEC 61784-2.
This part of IEC 62453 provides information for integrating the PROFINET® technology into
the FDT interface (IEC 62453-2).
This part of the IEC 62453 specifies communication and other services.
This specification neither contains the FDT specification nor modifies it.
2 Normative references
The following referenced documents are indispensable for the application of this specification.
For dated references, only the edition cited applies. For undated references, the latest edition
of the referenced document (including any amendments) applies
IEC 61158-5-10, Industrial communication networks – Fieldbus specifications – Part 5-10:
Application layer service definition – Type 10 elements
IEC 61158-6-10, Industrial communication networks – Fieldbus specifications – Part 6-10:
Application layer protocol specification – Type 10 elements
IEC 61784-2 Industrial communication networks - Profiles - Part 2: Additional fieldbus profiles
for real-time networks based on ISO/IEC 8802-3
IEC 62453-1:2009, Field Device Tool (FDT) interface specification – Part 1: Overview and
guidance
IEC 62453-2:2009, Field Device Tool (FDT) interface specification – Part 2: Concepts and
detailed description
3 Terms, definitions, symbols, abbreviated terms and conventions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62453-1 and
IEC 62453-2 apply.
—————————
PROFINET ® is the trademark of PROFIBUS Nutzerorganisation e.V. (PNO). PNO is a non-profit trade
organization to support the fieldbus PROFIBUS. This information is given for the convenience of users of this
International Standard and does not constitute an endorsement by IEC of the trademark holder or any of its
products. Compliance to this profile does not require use of the registered trademark. Use of the trademark
PROFIBUS and PROFINET requires permission of the trade name holder.

– 8 – 62453-303-2  IEC:2009
3.2 Abbreviated terms
For the purposes of this document, the abbreviations given in IEC 62453-1 and IEC 62453-2
and the following apply.
AR Application Relation
DCP Discovery and basic Configuration Protocol
GSDML Generic Station Description Markup Language
IOCS IO Consumer Status
IOPS IO Provider Status
UML Unified Modeling Language
3.3 Conventions
3.3.1 Data type names and references to data types
The conventions for naming and referencing of data types are explained in IEC 62453-2,
Clause A.1
3.3.2 Vocabulary for requirements
The following expressions are used when specifying requirements.
Usage of “shall” or “mandatory” No exceptions allowed.
Usage of “should” or “recommended” Strong recommendation. It may make sense in special
exceptional cases to differ from the described behaviour.
Usage of “can’ or “optional’ Function or behaviour may be provided, depending on
defined conditions.
3.3.3 Use of UML
Figures in this document are using UML notation as defined in Annex A of IEC 62453-1.
4 Bus category
IEC 61784 CP 3/4, CP 3/5 and CP 3/6 protocols are identified in the protocolId element of the
structured data type 'fdt:BusCategory' by the following unique identifier as defined in Table 1:
Table 1 – Protocol identifier
Identifier value ProtocolId name Description
DFC98364-DAB8-493B-BB92-23B3F92FEBCD ‘Profinet IO’ Support of IEC 61784 CP 3/4,
CP 3/5 and CP 3/6 protocols
IEC 61784 CP 3/4, CP 3/5 and CP 3/6 use the following unique identifier for its physical
layers.
Table 2 – Physical layer identifier
PhysicalLayer element Description
99C36176-E59A-11DA-9023-0002B3ECDCBE 10BASET
99C36177-E59A-11DA-9023-0002B3ECDCBE 10BASETXHD
99C36178-E59A-11DA-9023-0002B3ECDCBE 10BASETXFD
99C36179-E59A-11DA-9023-0002B3ECDCBE 100BASETXHD
99C3617A-E59A-11DA-9023-0002B3ECDCBE 100BASETXFD

62453-303-2  IEC:2009 – 9 –
PhysicalLayer element Description
99C3617B-E59A-11DA-9023-0002B3ECDCBE 10BASEFXHD
99C3617C-E59A-11DA-9023-0002B3ECDCBE 10BASEFXFD
99C3617D-E59A-11DA-9023-0002B3ECDCBE 1000BASEXHD
99C3617E-E59A-11DA-9023-0002B3ECDCBE 1000BASEXFD
99C3617F-E59A-11DA-9023-0002B3ECDCBE 1000BASELXHD
99C36180-E59A-11DA-9023-0002B3ECDCBE 1000BASELXFD
99C36181-E59A-11DA-9023-0002B3ECDCBE 1000BASESXHD
99C36182-E59A-11DA-9023-0002B3ECDCBE 1000BASESXFD
99C36183-E59A-11DA-9023-0002B3ECDCBE 1000BASETHD
99C36184-E59A-11DA-9023-0002B3ECDCBE 1000BASETFD
99C36185-E59A-11DA-9023-0002B3ECDCBE 10GigBASEFX

5 Access instance and device data
5.1 Process Channel objects provided by DTM
The minimum set of provided data should be:
• process values modeled as channel objects including the ranges and scaling.
5.2 DTM services to access instance and device data
The services InstanceItemList and DeviceItemList shall provide access to at least all
mandatory parameters of CP 3/4, CP 3/5 and CP 3/6 devices.
6 Protocol specific behavior
Not applicable.
7 Protocol specific usage of general data types
The following table (Table 3) shows how general data types, defined in IEC 62453-2 within
the namespace ‘fdt’, are used with CP 3/4, CP 3/5 and CP 3/6 devices.
Table 3 – Protocol specific usage of general data types
Attribute Description for use in IEC 61784 CP 3/4, CP 3/5 and CP 3/6
fdt:address For CP 3/4, CP 3/5 and CP 3/6 the address attribute is mandatory for the
exposed parameters in the DTMs. The address string shall be constructed
according to the rules of the FDT semanticId. That means the attribute
‘semanticId’ is always the same as the attribute ‘address’
fdt:protocolId See Clause 4
fdt:physicalLayer See Clause 4
fdt:deviceTypeId The attribute “fdt:DtmDeviceType/@deviceTypeId” must contain the DeviceID
according to the CP 3/4, CP 3/5 and CP 3/6 specification. The DeviceID shall
be entered in decimal format, however, the value should be displayed as hex
to the user.
GSDML XPath Expression:
“/ISO15745Profile/ProfileBody/DeviceIdentity/@DeviceID”
fdt:subDeviceType Enter manufacturer specific value here

– 10 – 62453-303-2  IEC:2009
Attribute Description for use in IEC 61784 CP 3/4, CP 3/5 and CP 3/6
fdt:vendor The attribute fdt:DtmDeviceType/VersionInformation/@vendor shall contain
the VendorName according to CP 3/4, CP 3/5 and CP 3/6 specification.
GSDML XPath Expression:
“/ISO15745Profile/ProfileBody/DeviceIdentity/@VendorName”
fdt:manufacturerId The attribute fdt:DtmDeviceType/VersionInformation/@vendor shall contain
the VendorName according to the CP 3/4, CP 3/5 and CP 3/6 specification.
GSDML XPath Expression:
“/ISO15745Profile/ProfileBody/DeviceIdentity/@VendorName”
fdt:deviceTypeInformation Path to the GSDML file. The attribute contains the full path including the file
name.
For IEC 61784 CP 3/4, CP 3/5 and CP 3/6 devices, it is mandatory to provide
this attribute.
Only a parent developed according to IEC 61784 CP 3/4, CP 3/5 and CP 3/6
Annex can handle GSDML information. Thus, it is not necessary to fill this
attribute with the GSDML itself, if the parent is FDT 1.2 conformant.
The deviceTypeInformation attribute is of type string and shall be used with
format shown in the example:
Example: file://c:/myDtm/myGsdFile.xml
fdt:deviceTypeInformationPath Shall not be used.
The GSDML path information is already mandatory in the
deviceTypeInformation attribute
fdt:semanticId The SemanticIDs follow the different device models that are defined for
IEC 61784 CP 3/4, CP 3/5 and CP 3/6 devices. FDT currently supports
fdt:applicationDomain
following models:
• Profinet IO
• PROFIdrive
PROFINET IO
The applicationDomain is: FDT_PROFINET_IO
The semanticId follows the access information of a communication request:
The semanticId is: Api.Slot.Subslot.Index.ByteOffset.BitOffset.BitLength
Api – Api number
Slot – Slot number
Subslot – Subslot number
Index – Index number
ByteOffset – Start byte within the Index
BitOffset – Start bit within the Index (range 0-7)
BitLength –Length of values in bit
These values are numbers based on decimal format without leading ‘0’.
PROFIdrive
The applicationDomain is: FDT_PROFINET_PROFIDRIVE
According to the PROFIdrive profile, a device (drive unit) may be composed
by a number (1-many) of drive objects (DOs). The DOs may have different
types. Each DO is uniquely identifiable and manages its own parameters.
Each parameter can be uniquely identified by its number (PNU). Each DO
has its own number space.
A parameter may contain simple data or composed data (e.g. arrays).
The data of the device are accessible via a parameter channel (normally Api
0x3A00, Subslot 1, Index 0xB02E and a slot number which is the DO
number).
The semanticId is: DOdo-id.PNUpnu
do-id Drive Object ID
pnu ParameterNumber
62453-303-2  IEC:2009 – 11 –
Attribute Description for use in IEC 61784 CP 3/4, CP 3/5 and CP 3/6
do-id, pnu are based on decimal format without leading ‘0’

8 Protocol specific common data types
Not applicable.
9 Network management data types
9.1 General
The data types specified in this subclause are used in the following services:
• NetworkManagementInfoRead service;
• NetworkManagementInfoWrite service.
9.2 Parameter access data types
The data types describe the parameter information of an IEC 61784 CP 3/4, CP 3/5 and
CP 3/6 device (see Table 4 and Table 5)
Table 4 – Simple parameter access data types
Data type Definition Description
arType UINT ARType according to the PROFINET specification
Shall only be set by Parent
arProperties UDINT ARProperties according to the PROFINET specification
Shall only be set by Parent
arUUID UUID ARUUID according to the PROFINET specification
Shall only be set by Parent
alarmCRType UINT AlarmCRType according to the PROFINET specification
Shall only be set by Parent
alarmCRProperties UDINT AlarmCRProperties according to the PROFINET specification
Shall only be set by Parent
rtaTimeoutFactor UINT RTATimeoutFactor according to the PROFINET specification
Shall only be set by Parent
rtaRetries UINT RTARetries according to the PROFINET specification
Shall only be set by Parent
localAlarmReference UINT LocalAlarmReference according to the PROFINET specification
Shall only be set by Parent
maxAlarmDataLength UINT MaxAlarmDataLength according to the PROFINET specification
Shall only be set by Parent
infoText STRING Additional textual information
Shall only be set by DTM
localIndex UINT The attribute used within Device/Identification to address the
device instance.
Shall only be set by DTM
– 12 – 62453-303-2  IEC:2009
Data type Definition Description
nameOfStation STRING The station name is the primary address. The default value is the
DNS_CompatibleName of the GSDML. The Parent shall configure
the station name according to the rules defined by the
DNS_CompatibleName.
Shall only be set by Parent apart of the default value, which shall
be set by DTM (during InitNew)
dynIpAddress BOOL The attribute indicates whether the IP address is dynamically
assigned to the device.
Shall only be set by Parent
extAddrSupported BOOL Extended address assignment (e.g. by DHCP, BootP) is supported
by the Profinet IO Device.
Shall only be set by DTM
ipAddress STRING The attribute contains the IP address that is assigned to the
device. The IP address is a secondary address. The default value
is “0.0.0.0”.
Shall only be set by Parent
ipSubnetMask STRING The attribute contains the subnet mask. The default value is
“255.255.255.255”.
Shall only be set by Parent
ipDefaultGateway STRING The attribute contains the default gateway address. The default
value is an empty string.
Shall only be set by Parent
macAddress STRING The attribute contains the MAC address of the device. The MAC
address is a secondary address.
The macAddress attribute is of type string and shall be used with
format shown in the example:
Example: 00:A0:45:01:02:03
Shall only be set by Parent
slotNumber UINT The slot address that is used by the module
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
moduleIdentNumber UDINT The ModuleIdentNumber according to the PROFINET specification
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
moduleProperties UINT This attribute is reserved for future use according to the
PROFINET specification
subSlotNumber UINT The subslot address that is used by the submodule.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
subModuleIdentNumber UDINT The SubmoduleIdentNumber according to the PROFINET
specification.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
ioType enumeration (Input Allowed values are: Input, Output, InputAndOutput.
| Output |
Values and meaning according to the PROFINET specification -
InputAndOutput )
SubmoduleProperties.Type.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
sharedInput enumeration Allowed values are: IOController, IOControllerShare.
(IOController |
Values and meaning according to the PROFINET specification -
IOControllerShare )
SubmoduleProperties.SharedInput.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
62453-303-2  IEC:2009 – 13 –
Data type Definition Description
reduceInputSubmodule enumeration Allowed values are: Expected, Zero.
DataLength (Expected | Zero )
Values and meaning according to the PROFINET specification -
SubmoduleProperties.ReduceInputSubmoduleDataLength.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
reduceOutputSubmodule enumeration Allowed values are: Expected, Zero.
DataLength (Expected | Zero )
Values and meaning according PROFINET specification -
SubmoduleProperties.ReduceOutputSubmoduleDataLength.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
discardIOXS enumeration Allowed values are: Expected, Zero.
(Expected | Zero )
Values and meaning according PROFINET specification -
SubmoduleProperties.DiscardIOXS.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
api UDINT The API according to the PROFINET specification.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
index UINT The address of the desired record data object.
Shall only be set by DTM
recordData ARRAY OF USINT The binary data that will be written to the submodule during startup
or connect. The record data implicitly contain the record data
length.
Shall only be set by DTM
consistency enumeration The consistency of the input data.
(itemConsistency |
Shall only be set by DTM during configuration
allItemsConsistency
)
sendClockFactor UINT SendClockFactor according to the PROFINET specification.
Shall only be set by Parent, if the attribute belongs to the element
SubModule.
Shall only be set by DTM, if the attribute belongs to the element
SendClockFactor
reductionRatio UINT ReductionRatio according to the PROFINET specification.
Shall only be set by Parent, if the attribute belongs to the element
SubModule.
Shall only be set by DTM, if the attribute belongs to the element
ReductionRatio
watchdogFactor UINT WatchdogFactor according to the PROFINET specification.
Shall only be set by Parent
dataHoldFactor UINT DataHoldFactor according to the PROFINET specification.
Shall only be set by Parent
– 14 – 62453-303-2  IEC:2009
Table 5 – Structured parameter access data types
Data type Definition Description
Elementary data types U Multiplicity
s
a
g
e
RecordParamData STRUCT  Record data that will be written to the
submodule during startup or connect
index M [1.1]
recordData M [1.1]
fdt:name O [0.1]
RecordParamDataList STRUCT  List of records that will be written to the
submodule during startup or connect
collection of M [1.1]
RecordParamData [1.*]
OutputDataList STRUCT  List of output data provided by a submodule.
The list refers to the corresponding FDT-
Channel objects
consistency O [0.1]
fdt:ChannelReferences M [1.1]
InputDataList STRUCT  List of input data provided by a submodule.
The list refers to the corresponding FDT-
Channel objects
consistency O [0.1]
fdt:ChannelReferences M [1.1]
SubModule STRUCT  The identification and configuration of a
submodule
subSlotNumber M [1.1]
fdt:name M [1.1]
fdt:descriptor O [0.1]
subModuleIdentNumber M [1.1]
api M [1.1]
sendClockFactor M [1.1]
reductionRatio M [1.1]
watchdogFactor M [1.1]
dataHoldFactor M [1.1]
InputDataList O [0.1]
OutputDataList O [0.1]
RecordParamDataList O [0.1]
SubModuleProperties O [0.1]
62453-303-2  IEC:2009 – 15 –
Data type Definition Description
Elementary data types U Multiplicity
s
a
g
e
SubModuleList STRUCT  List of expected submodules within a
module
collection of M [1.1]
SubModule [1.*]
SubModuleProperties STRUCT  The data type defines the type of
submodule: NO_IO, INPUT, OUTPUT, IO
according to the PROFINET specification.
Shall be set by DTM during configuration.
Can be set by Parent during topology scan
ioType M [1.1]
sharedInput M [1.1]
reduceInput- M [1.1]
SubmoduleDataLength
reduceOutput- M [1.1]
SubmoduleDataLength
discardIOXS M [1.1]
Module STRUCT  The identification and configuration of a
module
slotNumber M [1.1]
moduleIdentNumber M [1.1]
moduleProperties M [1.1]
fdt:name M [1.1]
fdt:descriptor M [1.1]
SubModuleList M [1.1]
ModuleList STRUCT  List of expected modules within an
application relationship
collection of M [1.1]
Module [1.*]
AlarmCR STRUCT  The Alarm CR is managed by the
Communication DTM, but the information is
stored at the Device DTM
alarmCRType M [1.1]
alarmCRProperties M [1.1]
rtaTimeoutFactor M [1.1]
rtaRetries M [1.1]
localAlarmReference M [1.1]
maxAlarmDataLength M [1.1]
AR STRUCT  The application relationship (AR) is
managed by the Communication DTM, but
the information is stored at the Device DTM
arType M [1.1]
arProperties M [1.1]
arUUID M [1.1]
AlarmCR M [1.1]
ModuleList O [0.1]
– 16 – 62453-303-2  IEC:2009
Data type Definition Description
Elementary data types U Multiplicity
s
a
g
e
TimingProperties STRUCT  TimingProperties content matches the
GSDML element TimingProperties. The data
type provides device type related timing
constraints to be considered by the IO
Controller.
TimingProperties and its data types shall be
set by the DTM only. The Device DTM
ignores element during execution of function
IDtmParameter::SetParameters
collection of M [1.1]
SendClockFactor M [1.*]
collection of M [1.1]
ReductionRatio M [1.*]
ReductionRatio STRUCT  ReductionRatio is required to map all device
supported reduction ratio values described
by GSDML attribute ReductionRatio. The
GSDML attribute contains a value list to be
mapped on several ReductionRatio
elements of the schema described here.
This data type represents device type data
that shall be set by the DTM only. This
information is used for communication
schedule planning by the parent
reductionRatio M [1.1]
SendClockFactor STRUCT  SendClockFactor is required to map all
device supported send clock factor values
described by GSDML attribute
SendClockFactor. The GSDML attribute
contains a value list to be mapped on
several SendClockFactor elements of the
schema described here.
This data type represents device type data
that shall be set by the DTM only. This
information is used for communication
schedule planning by the parent
sendClockFactor M [1.1]
Identification STRUCT  The identification of a device or device
instance
localIndex M [1.1]
fdt:deviceTypeId M [1.1]
fdt:manufacturerId M [1.1]
infoText O [0.1]
fdt:VersionInformation O [0.1]
Device STRUCT  The parameters of a device or device
instance
Identification M [1.1]
collection of M [1.1]
AR M [1.*]
TimingProperties O [0.1]
Network STRUCT  The address information of the PROFINET
device
62453-303-2  IEC:2009 – 17 –
Data type Definition Description
Elementary data types U Multiplicity
s
a
g
e
nameOfStation M [1.1]
dynIpAddress M [1.1]
ipAddress M [1.1]
ipSubnetMask M [1.1]
ipDefaultGateway M [1.1]
extAddrSupported M [1.1]
macAddress O [0.1]
DeviceList STRUCT  The list contains the parameters for one
device. If the DTM is responsible for a
device hosting multiple device instances,
the list contains the parameters for each
device instance
Network M [1.1]
collection of M [1.1]
Device M [1.*]
10 Communication data types
The data types described in this clause are used at following services:
• connect service;
• disconnect service;
• transaction service;
• abort service;
• SequenceBegin;
• SequenceEnd;
• SequenceStart.
The service arguments contain the address information and the communication data
(explained in Table 6 and Table 7).
The data types described in this clause are defined for the following namespace.
Namespace: fdtprofinet
Table 6 – Simple communication data types
Data type Definition Description
api UDINT Address information according to the PROFINET specification
nameOfStation STRING Address information according to the PROFINET specification
localIndex UINT Address information according to the PROFINET specification
errorDecode USINT Status information according to the PROFINET specification
errorCode1 UINT Status information according to the PROFINET specification
errorCode2 USINT Status information according to the PROFINET specification
index UINT Address information according to the PROFINET specification

– 18 – 62453-303-2  IEC:2009
Data type Definition Description
communicationReference UUID Mandatory identifier for a communication link to a device. This
identifier is allocated by the communication component during the
Connect. The address information has to be used for all following
communication calls
slot UINT Address information according to the PROFINET specification
subSlot UINT Address information according to the PROFINET specification
addData1 UINT Address information according to the PROFINET specification
addData2 UINT Address information according to the PROFINET specification
length UDINT Maximum length of communication data in read request
readOnly BOOL Only read support required on this connection.
The CommunicationChannel can use this information for optimized
connection management, e.g. use implicit AR
sequenceTime UDINT Allowed duration in [ms] for the whole sequence.
Can be set by the DTM at sequence begin
delayTime UDINT Minimum delay time in [ms] between two communication calls
systemTag STRING System Tag of a DTM

Table 7 – Structured communication data types
Data type Definition Description
Elementary data types U Multiplicity
s
a
g
e
Abort STRUCT  Describes the abort
communicationReference M [1.1]
CancelTransaction STRUCT  Describes the specific transaction to
cancel a pending transaction.
The function TransactionRequest is
called with the same “invokeId”
argument as the pending transaction
request.
If the CancelTransaction request is
accepted by the Communication
Channel the function
TransactionRequest returns TRUE.
If no transaction with the given
invokeId was sent, then the function
TransactionRequest returns FALSE.
No OnTransactionResponse can be
expected for the previous pending
request and for CancelTransaction
request with specified invokeId.
If a regular OnTransactionResponse
for the given invokeId was sent
already, then the function
TransactionRequest returns FALSE
communicationReference M [1.1]
ConnectRequest STRUCT  Describes the communication request
to establish a connection
nameOfStation M [1.1]
fdt:manufacturerId M [1.1]
fdt:deviceTypeId M [1.1]
62453-303-2  IEC:2009 – 19 –
Data type Definition Description
Elementary data types U Multiplicity
s
a
g
e
localIndex M [1.1]
systemTag M [1.1]
readOnly O [0.1]
ConnectResponse STRUCT  Describes the communication response
for a connect request
communicationReference M [1.1]
addData1 O [0.1]
addData2 O [0.1]
DisconnectRequest STRUCT  Describes the communication request
to release a connection
communicationReference M [1.1]
DisconnectResponse STRUCT  Describes the communication response
for a disconnect request
communicationReference M [1.1]
addData1 O [0.1]
addData2 O [0.1]
ReadRequest ST
...

IEC 62453-303-2 ®
Edition 1.1 2016-06
CONSOLIDATED VERSION
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
FIeld device tool (FDT) interface specification –
Part 303-2: Communication profile integration – IEC 61784 CP 3/4, CP 3/5
and CP 3/6
Spécification des interfaces des outils des dispositifs de terrain (FDT) –
Partie 303-2: Intégration des profils de communication – CP 3/4, CP 3/5 et
CP 3/6 de l’IEC 61784
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 20 000 terms and definitions in
Technical Specifications, Technical Reports and other English and French, with equivalent terms in 15 additional
documents. Available for PC, Mac OS, Android Tablets and languages. Also known as the International Electrotechnical
iPad. 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 65 000 electrotechnical terminology entries in English and
variety of criteria (reference number, text, technical French extracted from the Terms and Definitions clause of
committee,…). It also gives information on projects, replaced IEC publications issued since 2002. Some entries have been
and withdrawn publications. 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 20 000 termes et définitions en anglais
Spécifications techniques, Rapports techniques et autres
et en français, ainsi que les termes équivalents dans 15
documents de l'IEC. Disponible pour PC, Mac OS, tablettes
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
La recherche avancée permet de trouver des publications IEC
65 000 entrées terminologiques électrotechniques, en anglais
en utilisant différents critères (numéro de référence, texte,
et en français, extraites des articles Termes et Définitions des
comité d’études,…). Elle donne aussi des informations sur les
publications IEC parues depuis 2002. Plus certaines entrées
projets et les publications remplacées ou retirées.
antérieures extraites des publications des CE 37, 77, 86 et

CISPR de l'IEC.
IEC Just Published - webstore.iec.ch/justpublished

Restez informé sur les nouvelles publications IEC. Just Service Clients - webstore.iec.ch/csc
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 62453-303-2 ®
Edition 1.1 2016-06
CONSOLIDATED VERSION
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
FIeld device tool (FDT) interface specification –

Part 303-2: Communication profile integration – IEC 61784 CP 3/4, CP 3/5

and CP 3/6
Spécification des interfaces des outils des dispositifs de terrain (FDT) –

Partie 303-2: Intégration des profils de communication – CP 3/4, CP 3/5 et

CP 3/6 de l’IEC 61784
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040.40; 35.100.05; 35.110 ISBN 978-2-8322-3490-7

IEC 62453-303-2 ®
Edition 1.1 2016-06
CONSOLIDATED VERSION
REDLINE VERSION
VERSION REDLINE
colour
inside
FIeld device tool (FDT) interface specification –
Part 303-2: Communication profile integration – IEC 61784 CP 3/4, CP 3/5
and CP 3/6
Spécification des interfaces des outils des dispositifs de terrain (FDT) –
Partie 303-2: Intégration des profils de communication – CP 3/4, CP 3/5 et
CP 3/6 de l’IEC 61784
– 2 – IEC 62453-303-2:2009+AMD1:2016 CSV
 IEC 2016
CONTENTS
FOREWORD. 4
INTRODUCTION . 6
1 Scope . 7
2 Normative references . 7
3 Terms, definitions, symbols, abbreviated terms and conventions . 7
3.1 Terms and definitions . 7
3.2 Abbreviated terms . 8
3.3 Conventions . 8
3.3.1 Data type names and references to data types . 8
3.3.2 Vocabulary for requirements . 8
3.3.3 Use of UML . 8
4 Bus category . 8
5 Access instance and device data . 11
5.1 Process Channel objects provided by DTM . 11
5.2 DTM services to access instance and device data . 11
6 Protocol specific behavior . 11
7 Protocol specific usage of general data types . 11
8 Protocol specific common data types . 13
9 Network management data types . 13
9.1 General . 13
9.2 Parameter access data types . 13
10 Communication data types . 19
11 Channel parameter data types . 22
12 Device identification . 25
12.1 Protocol specific handling of data type STRING . 25
12.2 Device type identification data types . 25
12.3 Topology scan data types . 28
12.4 Scan identification data types . 29
12.5 Device type identification data types . 31
Bibliography . 34

Figure 1 – Part 303-2 of the IEC 62453 series . 6

Table 1 – Protocol identifier . 8
Table 2 – Physical layer identifier . 9
Table 3 – Protocol specific usage of general data types . 11
Table 4 – Simple parameter access data types . 13
Table 5 – Structured parameter access data types . 16
Table 6 – Simple communication data types . 19
Table 7 – Structured communication data types . 20
Table 8 – Simple channel parameter data types . 23
Table 9 – Structured channel parameter data types . 24
Table 10 – Identification data types for PROFINET with pure DCP . 26

 IEC 2016
Table 11 – Identification data types for PROFINET with I&M . 27
Table 12 – Simple identification data types with protocol independent semantics . 28
Table 13 – Structured identification data types with protocol independent semantics . 28
Table 14 – Simple device type identification data types . 28
Table 15 – Structured device type identification data type . 29
Table 16 – Simple scan identification data types . 29
Table 17 – Structured scan identification data types . 30
Table 18 – Structured device type identification data types . 31
Table 19 – DataLink Layer Identifiers . 11

– 4 – IEC 62453-303-2:2009+AMD1:2016 CSV
 IEC 2016
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –
Part 303-2: Communication profile integration –
IEC 61784 CP 3/4, CP 3/5 and CP 3/6
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 provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
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.
This consolidated version of the official IEC Standard and its amendment has been prepared
for user convenience.
IEC 62453-303-2 edition 1.1 contains the first edition (2009-06) [documents 65E/128/FDIS and
65E/141/RVD] and its amendment 1 (2016-06) [documents 65E/336/CDV and 65E/395A/RVC].
In this Redline version, a vertical line in the margin shows where the technical content is
modified by amendment 1. Additions are in green text, deletions are in strikethrough red text.
A separate Final version with all changes accepted is available in this publication.

 IEC 2016
International Standard IEC 62453-303-2 has been prepared by subcommittee 65E: Devices
and integration in enterprise systems, of IEC technical committee 65: Industrial-process
measurement, control and automation.
Each part of the IEC 62453-3xy series is intended to be read in conjunction with IEC 62453-2.
The French version of this standard has not been voted upon.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts of the IEC 62453 series, under the general title Field Device Tool (FDT)
interface specification, can be found on the IEC website.
The committee has decided that the contents of the base publication and its amendment 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.
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.
– 6 – IEC 62453-303-2:2009+AMD1:2016 CSV
 IEC 2016
INTRODUCTION
This part of IEC 62453 is an interface specification for developers of FDT (Field Device Tool)
components for function control and data access within a client/server architecture. The
specification is a result of an analysis and design process to develop standard interfaces to
facilitate the development of servers and clients by multiple vendors that need to interoperate
seamlessly.
With the integration of fieldbusses into control systems, there are a few other tasks which
need to be performed. In addition to fieldbus- and device-specific tools, there is a need to
integrate these tools into higher-level system-wide planning- or engineering tools. In
particular, for use in extensive and heterogeneous control systems, typically in the area of the
process industry, the unambiguous definition of engineering interfaces that are easy to use for
all those involved is of great importance.
A device-specific software component, called DTM (Device Type Manager), is supplied by the
field device manufacturer with its device. The DTM is integrated into engineering tools via the
FDT interfaces defined in this specification. The approach to integration is in general open for
all kinds of fieldbusses and thus meets the requirements for integrating different kinds of
devices into heterogeneous control systems.
Figure 1 shows how IEC 62453-303-2 is aligned in the structure of the IEC 62453 series.
IEC  1132/09
Figure 1 – Part 303-2 of the IEC 62453 series

 IEC 2016
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –

Part 303-2: Communication profile integration –
IEC 61784 CP 3/4, CP 3/5 and CP 3/6

1 Scope
Communication Profile 3/4, Communication Profile 3/5 and Communication Profile 3/6
(commonly known as PROFINET® IO) define communication profiles based on
IEC 61158-5-10 and IEC 61158-6-10. The basic profiles CP 3/4, CP 3/5, and CP 3/6 are
defined in IEC 61784-2.
This part of IEC 62453 provides information for integrating the PROFINET® technology into
the FDT interface (IEC 62453-2).
This part of the IEC 62453 specifies communication and other services.
This specification neither contains the FDT specification nor modifies it.
2 Normative references
The following referenced documents are indispensable for the application of this specification.
For dated references, only the edition cited applies. For undated references, the latest edition
of the referenced document (including any amendments) applies
IEC 61158-5-10, Industrial communication networks – Fieldbus specifications – Part 5-10:
Application layer service definition – Type 10 elements
IEC 61158-6-10, Industrial communication networks – Fieldbus specifications – Part 6-10:
Application layer protocol specification – Type 10 elements
IEC 61784-2 Industrial communication networks - Profiles - Part 2: Additional fieldbus profiles
for real-time networks based on ISO/IEC 8802-3
IEC 62453-1:2009, Field Device Tool (FDT) interface specification – Part 1: Overview and
guidance
IEC 62453-2:2009, Field Device Tool (FDT) interface specification – Part 2: Concepts and
detailed description
3 Terms, definitions, symbols, abbreviated terms and conventions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62453-1, and
IEC 62453-2 as well as the following apply.
—————————
PROFINET ® is the trademark of PROFIBUS Nutzerorganisation e.V. (PNO). PNO is a non-profit trade
organization to support the fieldbus PROFIBUS. This information is given for the convenience of users of this
International Standard and does not constitute an endorsement by IEC of the trademark holder or any of its
products. Compliance to this profile does not require use of the registered trademark. Use of the trademark
PROFIBUS and PROFINET requires permission of the trade name holder.

– 8 – IEC 62453-303-2:2009+AMD1:2016 CSV
 IEC 2016
3.1.1
IO Controller
controlling device that acts as client for several IO devices (field devices)
3.1.2
IO Device
field device that acts as server for IO operation
3.1.3
IO Supervisor
engineering device that manages commissioning and diagnosis of an IO system
3.2 Abbreviated terms
For the purposes of this document, the abbreviations given in IEC 62453-1 and IEC 62453-2
and the following apply.
AR Application Relation
DCP Discovery and basic Configuration Protocol
GSDML Generic Station Description Markup Language
IOCS IO Consumer Status
IOPS IO Provider Status
UML Unified Modeling Language
3.3 Conventions
3.3.1 Data type names and references to data types
The conventions for naming and referencing of data types are explained in IEC 62453-2,
Clause A.1
3.3.2 Vocabulary for requirements
The following expressions are used when specifying requirements.
Usage of “shall” or “mandatory” No exceptions allowed.
Usage of “should” or “recommended” Strong recommendation. It may make sense in special
exceptional cases to differ from the described behaviour.
Usage of “can’ or “optional’ Function or behaviour may be provided, depending on
defined conditions.
3.3.3 Use of UML
Figures in this document are using UML notation as defined in Annex A of IEC 62453-1.
4 Bus category
IEC 61784 CP 3/4, CP 3/5 and CP 3/6 protocols are identified in the protocolId element of the
structured data type 'fdt:BusCategory' by the following unique identifier as defined in Table 1:
Table 1 – Protocol identifier
Identifier value ProtocolId name Description
DFC98364-DAB8-493B-BB92-23B3F92FEBCD ‘Profinet IO’ Support of IEC 61784 CP 3/4,
CP 3/5 and CP 3/6 protocols
 IEC 2016
IEC 61784 CP 3/4, CP 3/5 and CP 3/6 use the following unique identifier for its physical
layers.
Table 2 – Physical layer identifier
PhysicalLayer element Description
99C36176-E59A-11DA-9023-0002B3ECDCBE 10BASET
99C36177-E59A-11DA-9023-0002B3ECDCBE 10BASETXHD
99C36178-E59A-11DA-9023-0002B3ECDCBE 10BASETXFD
99C36179-E59A-11DA-9023-0002B3ECDCBE 100BASETXHD
99C3617A-E59A-11DA-9023-0002B3ECDCBE 100BASETXFD
99C3617B-E59A-11DA-9023-0002B3ECDCBE 10BASEFXHD
99C3617C-E59A-11DA-9023-0002B3ECDCBE 10BASEFXFD
99C3617D-E59A-11DA-9023-0002B3ECDCBE 1000BASEXHD
99C3617E-E59A-11DA-9023-0002B3ECDCBE 1000BASEXFD
99C3617F-E59A-11DA-9023-0002B3ECDCBE 1000BASELXHD
99C36180-E59A-11DA-9023-0002B3ECDCBE 1000BASELXFD
99C36181-E59A-11DA-9023-0002B3ECDCBE 1000BASESXHD
99C36182-E59A-11DA-9023-0002B3ECDCBE 1000BASESXFD
99C36183-E59A-11DA-9023-0002B3ECDCBE 1000BASETHD
99C36184-E59A-11DA-9023-0002B3ECDCBE 1000BASETFD
99C36185-E59A-11DA-9023-0002B3ECDCBE 10GigBASEFX

Identifier value Description
307DD808-C010-11DB-90E7-0002B3ECDCBE 10BASET (Depreciated)
307DD809-C010-11DB-90E7-0002B3ECDCBE 10BASETXHD (Depreciated)
307DD80A-C010-11DB-90E7-0002B3ECDCBE 10BASETXFD (Depreciated)
307DD80B-C010-11DB-90E7-0002B3ECDCBE 10BASEFLHD (Depreciated)
307DD80C-C010-11DB-90E7-0002B3ECDCBE 10BASEFLFD (Depreciated)
307DD80D-C010-11DB-90E7-0002B3ECDCBE 10BASEFXHD (Depreciated)
307DD80E-C010-11DB-90E7-0002B3ECDCBE 10BASEFXFD (Depreciated)
307DD80F-C010-11DB-90E7-0002B3ECDCBE 100BASETXHD (Depreciated)
307DD810-C010-11DB-90E7-0002B3ECDCBE 100BaseTXFD (Default for Media Type Copper)
307DD811-C010-11DB-90E7-0002B3ECDCBE 100BASEFXHD (Depreciated)
307DD812-C010-11DB-90E7-0002B3ECDCBE 100BaseFXFD (Default for Media Type Fiber Optic)
307DD813-C010-11DB-90E7-0002B3ECDCBE 100BaseLX10
307DD814-C010-11DB-90E7-0002B3ECDCBE 100BASEPX10 (Depreciated)
307DD815-C010-11DB-90E7-0002B3ECDCBE 1000BASEXHD (Depreciated)
307DD816-C010-11DB-90E7-0002B3ECDCBE 1000BaseXFD
307DD817-C010-11DB-90E7-0002B3ECDCBE 1000BASELXHD (Depreciated)
307DD818-C010-11DB-90E7-0002B3ECDCBE 1000BaseLXFD
307DD819-C010-11DB-90E7-0002B3ECDCBE 1000BASESXHD (Depreciated)
307DD81A-C010-11DB-90E7-0002B3ECDCBE 1000BaseSXFD
307DD81B-C010-11DB-90E7-0002B3ECDCBE 1000BASETHD (Depreciated)
307DD81C-C010-11DB-90E7-0002B3ECDCBE 1000BaseTFD
307DD81D-C010-11DB-90E7-0002B3ECDCBE 10GbaseFX

– 10 – IEC 62453-303-2:2009+AMD1:2016 CSV
 IEC 2016
Identifier value Description
307DD81E-C010-11DB-90E7-0002B3ECDCBE 10GbaseLX4
307DD81F-C010-11DB-90E7-0002B3ECDCBE 10GBaseR
307DD820-C010-11DB-90E7-0002B3ECDCBE 10GbaseER
307DD821-C010-11DB-90E7-0002B3ECDCBE 10GbaseLR
307DD822-C010-11DB-90E7-0002B3ECDCBE 10GbaseSR
307DD823-C010-11DB-90E7-0002B3ECDCBE 10GbaseW
307DD824-C010-11DB-90E7-0002B3ECDCBE 10GbaseEW
307DD824-C010-11DB-90E7-0002B3ECDCBE 10GbaseLW
307DD825-C010-11DB-90E7-0002B3ECDCBE 10GbaseSW
307DD826-C010-11DB-90E7-0002B3ECDCBE 10GbaseCX4
307DD827-C010-11DB-90E7-0002B3ECDCBE 2BaseTL
307DD828-C010-11DB-90E7-0002B3ECDCBE 10PassTS
307DD829-C010-11DB-90E7-0002B3ECDCBE 100BaseBX10D
307DD82A-C010-11DB-90E7-0002B3ECDCBE 100BaseBX10U
307DD82B-C010-11DB-90E7-0002B3ECDCBE 100BaseLX10
307DD82C-C010-11DB-90E7-0002B3ECDCBE 1000BaseBX10D
307DD82D-C010-11DB-90E7-0002B3ECDCBE 1000BaseBX10U
307DD82F-C010-11DB-90E7-0002B3ECDCBE 1000BaseLX10
307DD830-C010-11DB-90E7-0002B3ECDCBE 1000BasePX10D
307DD831-C010-11DB-90E7-0002B3ECDCBE 1000BasePX10U
307DD832-C010-11DB-90E7-0002B3ECDCBE 1000BasePX20D
307DD833-C010-11DB-90E7-0002B3ECDCBE 1000BasePX20U
307DD834-C010-11DB-90E7-0002B3ECDCBE 10GBaseT or 100BasePXFD
307DD835-C010-11DB-90E7-0002B3ECDCBE 10GBaseLRM
307DD836-C010-11DB-90E7-0002B3ECDCBE 1000BaseKX
307DD837-C010-11DB-90E7-0002B3ECDCBE 1000BaseKX4
307DD838-C010-11DB-90E7-0002B3ECDCBE 1000BaseKR
307DD839-C010-11DB-90E7-0002B3ECDCBE 10G1GBasePRXD1
307DD83A-C010-11DB-90E7-0002B3ECDCBE 10G1GBasePXRD2
307DD83B-C010-11DB-90E7-0002B3ECDCBE 10G1GBasePXRD3
307DD83C-C010-11DB-90E7-0002B3ECDCBE 10G1GBasePRXU1
307DD83D-C010-11DB-90E7-0002B3ECDCBE 10G1GBasePXRU2
307DD83E-C010-11DB-90E7-0002B3ECDCBE 10G1GBasePXRU3
307DD83F-C010-11DB-90E7-0002B3ECDCBE 10GBasePRD1
307DD840-C010-11DB-90E7-0002B3ECDCBE 10GBasePRD2
307DD841-C010-11DB-90E7-0002B3ECDCBE 10GBasePRD3
307DD842-C010-11DB-90E7-0002B3ECDCBE 10GBasePRU1
307DD843-C010-11DB-90E7-0002B3ECDCBE 10GBasePRU3
307DD844-C010-11DB-90E7-0002B3ECDCBE 40GbaseKR4
307DD845-C010-11DB-90E7-0002B3ECDCBE 40GbaseCR4
307DD845-C010-11DB-90E7-0002B3ECDCBE 40GbaseSR4
307DD846-C010-11DB-90E7-0002B3ECDCBE 40GbaseFR
307DD847-C010-11DB-90E7-0002B3ECDCBE 40GbaseLR4
307DD848-C010-11DB-90E7-0002B3ECDCBE 100GbaseCR10

 IEC 2016
Identifier value Description
307DD849-C010-11DB-90E7-0002B3ECDCBE 100GbaseSR10
307DD84A-C010-11DB-90E7-0002B3ECDCBE 100GbaseLR4
307DD84B-C010-11DB-90E7-0002B3ECDCBE 100GbaseER4
307DD84C-C010-11DB-90E7-0002B3ECDCBE 100BasePXFD
307DD84D-C010-11DB-90E7-0002B3ECDCBE Radio Communication
307DD84E-C010-11DB-90E7-0002B3ECDCBE Speed of 100 Mbit/s (and more) and full duplexity

Table 19 defines which DataLinkLayer shall be used in combination with the BusCategory
values defined in Table 1.
Table 19 – DataLink Layer Identifiers
Identifier value Description
ABE21B4A-3AD4-F274-6F3A-B542CF2DDB58 IEEE 802.3
ABE21B4B-3AD4-F274-6F3A-B542CF2DDB58 IEEE 802.11
ABE21B4C-3AD4-F274-6F3A-B542CF2DDB58 IEEE 802.15.1

5 Access instance and device data
5.1 Process Channel objects provided by DTM
The minimum set of provided data should be:
• process values modeled as channel objects including the ranges and scaling.
5.2 DTM services to access instance and device data
The services InstanceItemList and DeviceItemList shall provide access to at least all
mandatory parameters of CP 3/4, CP 3/5 and CP 3/6 devices.
6 Protocol specific behavior
Not applicable.
7 Protocol specific usage of general data types
The following table (Table 3) shows how general data types, defined in IEC 62453-2 within
the namespace ‘fdt’, are used with CP 3/4, CP 3/5 and CP 3/6 devices.
Table 3 – Protocol specific usage of general data types
Attribute Description for use in IEC 61784 CP 3/4, CP 3/5 and CP 3/6
fdt:address For CP 3/4, CP 3/5 and CP 3/6 the address attribute is mandatory for the
exposed parameters in the DTMs. The address string shall be constructed
according to the rules of the FDT semanticId. That means the attribute
‘semanticId’ is always the same as the attribute ‘address’
fdt:protocolId See Clause 4
fdt:physicalLayer See Clause 4

– 12 – IEC 62453-303-2:2009+AMD1:2016 CSV
 IEC 2016
Attribute Description for use in IEC 61784 CP 3/4, CP 3/5 and CP 3/6
fdt:deviceTypeId The attribute “fdt:DtmDeviceType/@deviceTypeId” must contain the DeviceID
according to the CP 3/4, CP 3/5 and CP 3/6 specification. The DeviceID shall
be entered in decimal format, however, the value should be displayed as hex
to the user.
GSDML XPath Expression:
“/ISO15745Profile/ProfileBody/DeviceIdentity/@DeviceID”
fdt:subDeviceType Enter manufacturer specific value here
fdt:vendor The attribute fdt:DtmDeviceType/VersionInformation/@vendor shall contain
the VendorName according to CP 3/4, CP 3/5 and CP 3/6 specification.
GSDML XPath Expression:
“/ISO15745Profile/ProfileBody/DeviceIdentity/@VendorName”
fdt:manufacturerId The attribute fdt:DtmDeviceType/VersionInformation/@vendor shall contain
the VendorName according to the CP 3/4, CP 3/5 and CP 3/6 specification.
GSDML XPath Expression:
“/ISO15745Profile/ProfileBody/DeviceIdentity/@VendorName”
fdt:deviceTypeInformation Path to the GSDML file. The attribute contains the full path including the file
name.
For IEC 61784 CP 3/4, CP 3/5 and CP 3/6 devices, it is mandatory to provide
this attribute.
Only a parent developed according to IEC 61784 CP 3/4, CP 3/5 and CP 3/6
Annex can handle GSDML information. Thus, it is not necessary to fill this
attribute with the GSDML itself, if the parent is FDT 1.2 conformant.
The deviceTypeInformation attribute is of type string and shall be used with
format shown in the example:
Example: file://c:/myDtm/myGsdFile.xml
fdt:deviceTypeInformationPath Shall not be used.
The GSDML path information is already mandatory in the
deviceTypeInformation attribute
fdt:semanticId The SemanticIDs follow the different device models that are defined for
IEC 61784 CP 3/4, CP 3/5 and CP 3/6 devices. FDT currently supports
fdt:applicationDomain
following models:
• Profinet IO
• PROFIdrive
PROFINET IO
The applicationDomain is: FDT_PROFINET_IO
The semanticId follows the access information of a communication request:
The semanticId is: Api.Slot.Subslot.Index.ByteOffset.BitOffset.BitLength
Api – Api number
Slot – Slot number
Subslot – Subslot number
Index – Index number
ByteOffset – Start byte within the Index
BitOffset – Start bit within the Index (range 0-7)
BitLength –Length of values in bit
These values are numbers based on decimal format without leading ‘0’.
PROFIdrive
The applicationDomain is: FDT_PROFINET_PROFIDRIVE
According to the PROFIdrive profile, a device (drive unit) may be composed
by a number (1-many) of drive objects (DOs). The DOs may have different
types. Each DO is uniquely identifiable and manages its own parameters.
Each parameter can be uniquely identified by its number (PNU). Each DO
has its own number space.
 IEC 2016
Attribute Description for use in IEC 61784 CP 3/4, CP 3/5 and CP 3/6
A parameter may contain simple data or composed data (e.g. arrays).
The data of the device are accessible via a parameter channel (normally Api
0x3A00, Subslot 1, Index 0xB02E and a slot number which is the DO
number).
The semanticId is: DOdo-id.PNUpnu
do-id Drive Object ID
pnu ParameterNumber
do-id, pnu are based on decimal format without leading ‘0’

8 Protocol specific common data types
Not applicable.
9 Network management data types
9.1 General
The data types specified in this subclause are used in the following services:
• NetworkManagementInfoRead service;
• NetworkManagementInfoWrite service.
9.2 Parameter access data types
The data types describe the parameter information of an IEC 61784 CP 3/4, CP 3/5 and
CP 3/6 device (see Table 4 and Table 5)
Table 4 – Simple parameter access data types
Data type Definition Description
arType UINT ARType according to the PROFINET specification
Shall only be set by Parent
arProperties UDINT ARProperties according to the PROFINET specification
Shall only be set by Parent
arUUID UUID ARUUID according to the PROFINET specification
Shall only be set by Parent
alarmCRType UINT AlarmCRType according to the PROFINET specification
Shall only be set by Parent
alarmCRProperties UDINT AlarmCRProperties according to the PROFINET specification
Shall only be set by Parent
rtaTimeoutFactor UINT RTATimeoutFactor according to the PROFINET specification
Shall only be set by Parent
rtaRetries UINT RTARetries according to the PROFINET specification
Shall only be set by Parent
localAlarmReference UINT LocalAlarmReference according to the PROFINET specification
Shall only be set by Parent
maxAlarmDataLength UINT MaxAlarmDataLength according to the PROFINET specification
Shall only be set by Parent
– 14 – IEC 62453-303-2:2009+AMD1:2016 CSV
 IEC 2016
Data type Definition Description
infoText STRING Additional textual information
Shall only be set by DTM
localIndex UINT The attribute used within Device/Identification to address the
device instance.
Shall only be set by DTM
nameOfStation STRING The station name is the primary address. The default value is the
DNS_CompatibleName of the GSDML. The Parent shall configure
the station name according to the rules defined by the
DNS_CompatibleName.
Shall only be set by Parent apart of the default value, which shall
be set by DTM (during InitNew)
dynIpAddress BOOL The attribute indicates whether the IP address is dynamically
assigned to the device.
Shall only be set by Parent
extAddrSupported BOOL Extended address assignment (e.g. by DHCP, BootP) is supported
by the Profinet IO Device.
Shall only be set by DTM
ipAddress STRING The attribute contains the IP address that is assigned to the
device. The IP address is a secondary address. The default value
is “0.0.0.0”.
Shall only be set by Parent
ipSubnetMask STRING The attribute contains the subnet mask. The default value is
“255.255.255.255”.
Shall only be set by Parent
ipDefaultGateway STRING The attribute contains the default gateway address. The default
value is an empty string.
Shall only be set by Parent
macAddress STRING The attribute contains the MAC address of the device. The MAC
address is a secondary address.
The macAddress attribute is of type string and shall be used with
format shown in the example:
Example: 00:A0:45:01:02:03
Shall only be set by Parent
slotNumber UINT The slot address that is used by the module
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
moduleIdentNumber UDINT The ModuleIdentNumber according to the PROFINET specification
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
moduleProperties UINT This attribute is reserved for future use according to the
PROFINET specification
subSlotNumber UINT The subslot address that is used by the submodule.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
subModuleIdentNumber UDINT The SubmoduleIdentNumber according to the PROFINET
specification.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
ioType enumeration (Input Allowed values are: Input, Output, InputAndOutput.
| Output |
Values and meaning according to the PROFINET specification -
InputAndOutput )
SubmoduleProperties.Type.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
 IEC 2016
Data type Definition Description
sharedInput enumeration Allowed values are: IOController, IOControllerShare.
(IOController |
Values and meaning according to the PROFINET specification -
IOControllerShare )
SubmoduleProperties.SharedInput.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
reduceInputSubmodule enumeration Allowed values are: Expected, Zero.
DataLength (Expected | Zero )
Values and meaning according to the PROFINET specification -
SubmoduleProperties.ReduceInputSubmoduleDataLength.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
reduceOutputSubmodule enumeration Allowed values are: Expected, Zero.
DataLength (Expected | Zero )
Values and meaning according PROFINET specification -
SubmoduleProperties.ReduceOutputSubmoduleDataLength.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
discardIOXS enumeration Allowed values are: Expected, Zero.
(Expected | Zero )
Values and meaning according PROFINET specification -
SubmoduleProperties.DiscardIOXS.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
api UDINT The API according to the PROFINET specification.
Shall be set by DTM during configuration. Can be set by Parent
during topology scan
index UINT The address of the desired record data object.
Shall only be set by DTM
recordData ARRAY OF USINT The binary data that will be written to the submodule during startup
or connect. The record data implicitly contain the record data
length.
Shall only be set by DTM
consistency enumeration The consistency of the input data.
(itemConsistency |
Shall only be set by DTM during configuration
allItemsConsistency
)
sendClockFactor UINT SendClockFactor according to the PROFINET specification.
Shall only be set by Parent, if the attribute belongs to the element
SubModule.
Shall only be set by DTM, if the attribute belongs to the element
SendClockFactor
reductionRatio UINT ReductionRatio according to the PROFINET specification.
Shall only be set by Parent, if the attribute belongs to the element
SubModule.
Shall only be set by DTM, if the attribute belongs to the element
ReductionRatio
watchdogFactor UINT WatchdogFactor according to the PROFINET specification.
Shall only be set by Parent
dataHoldFactor UINT DataHoldFactor according to the PROFINET specification.
Shall only be set by Parent
– 16 – IEC 62453-303-2:2009+AMD1:2016 CSV
 IEC 2016
Table 5 – Structured parameter access data types
Data type Definition Description
Elementary data types U Multiplicity
s
a
g
e
RecordParamData STRUCT  Record data that will be written to the
submodule during startup or connect
index M [1.1]
recordData M [1.1]
fdt:name O [0.1]
RecordParamDataList STRUCT  List of records that will be written to the
submodule during startup or connect
collection of M [1.1]
RecordParamData [1.*]
OutputDataList STRUCT  List of output data provided by a submodule.
The list refers to the corresponding FDT-
Channel objects
consistency O [0.1]
fdt:ChannelReferences M [1.1]
InputDataList STRUCT  List of input data provided by a submodule.
The list refers to the corresponding FDT-
Channel objects
consistency O [0.1]
fdt:ChannelReferences M [1.1]
SubModule STRUCT  The identification and configuration of a
submodule
subSlotNumber M [1.1]
fdt:name M [1.1]
fdt:descriptor O [0.1]
subModuleIdentNumber M [1.1]
api M [1.1]
sendClockFactor M [1.1]
reductionRatio M [1.1]
watchdogFactor M [1.1]
dataHoldFactor M [1.1]
InputDataList O [0.1]
OutputDataList O [0.1]
RecordParamDataList O [0.1]
SubModuleProperties O [0.1]
 IEC 2016
Data type Definition Description
Elementary data types U Multiplicity
s
a
g
e
SubModuleList STRUCT  List of expected submodules within a
module
collection of M [1.1]
SubModule [1.*]
SubModuleProperties STRUCT  The data type defines the type of
submodule: NO_IO, INPUT, OUTPUT, IO
according to the PROFINET specification.
Shall be set by DTM during configuration.
Can be set by Parent during topology scan
ioType M [1.1]
sharedInput M [1.1]
reduceInput- M [1.1]
SubmoduleDataLength
reduceOutput- M [1.1]
SubmoduleDataLength
discardIOXS M [1.1]
Module STRUCT  The identification and configuration of a
module
slotNumber M [1.1]
moduleIdentNumber M [1.1]
moduleProperties M [1.1]
fdt:name M [1.1]
fdt:descriptor M [1.1]
SubModuleList M [1.1]
ModuleList STRUCT  List of expected modules within an
application relationship
collection of M [1.1]
Module [1.*]
AlarmCR STRUCT  The Alarm CR is managed by the
Communication DTM, but the information is
stored at the Device DTM
alarmCRType M [1.1]
alarmCRProperties M [1.1]
rtaTimeoutFactor M [1.1]
rtaRetries M [1.1]
localAlarmReference M [1.1]
maxAlarmDataLength M [1.1]
AR STRUCT  The application relationship (AR) is
managed by the Communication DTM, but
the information is stored at the Device DTM
arType M [1.1]
arProperties M [1.1]
arUUID M [1.1]
AlarmCR M [1.1]
ModuleList O [0.1]
-
...