CLC IEC/TR 62453-52-32:2019

SLOVENSKI STANDARD
01-junij-2019
Specifikacija vmesnika orodja procesne naprave - 52-32. del: Implementacija
komunikacije za skupno jezikovno infrastrukturo - IEC 61784 CP 3/4, CP 3/5 in CP
3/6 (IEC/TR 62453-52-32:2017)
Field device tool (FDT) interface specification - Part 52-32: Communication
implementation for common language infrastructure - IEC 61784 CP 3/4, CP 3/5 and CP
3/6 (IEC/TR 62453-52-32:2017)
Field Device Tool (FDT)-Schnittstellenspezifikation - Teil 52-32:
Kommunikationsimplementierung mit der allgemeinen Sprachinfrastruktur -
Kommunikationsprofilfamilie (CPF) 3/4, 3/5 und 3/6 nach IEC 61784 (IEC/TR 62453-52-
32:2017)
Spécification des interfaces des outils des dispositifs de terrain (FDT) - Partie 52-32:
Mise en oeuvre d’un profil de communication pour l’infrastructure commune de langage -
CP 3/4, CP 3/5 et CP 3/6 de l’ IEC 61784 (IEC/TR 62453-52-32:2017)
Ta slovenski standard je istoveten z: CLC IEC/TR 62453-52-32:2019
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

TECHNICAL REPORT CLC IEC/TR 62453-52-32

RAPPORT TECHNIQUE
TECHNISCHER BERICHT
February 2019
ICS 25.040.40; 35.100.05; 35.110

English Version
Field device tool (FDT) interface specification - Part 52-32:
Communication implementation for common language
infrastructure - IEC 61784 CP 3/4, CP 3/5 and CP 3/6
(IEC/TR 62453-52-32:2017)
Spécification des interfaces des outils des dispositifs de Field Device Tool (FDT)-Schnittstellenspezifikation - Teil
terrain (FDT) - Partie 52-32: Mise en œuvre d’un profil de 52-32: Kommunikationsimplementierung mit der
communication pour l’infrastructure commune de langage - allgemeinen Sprachinfrastruktur -
CP 3/4, CP 3/5 et CP 3/6 de l’ IEC 61784 Kommunikationsprofilfamilie (CPF) 3/4, 3/5 und 3/6 nach
(IEC/TR 62453-52-32:2017) IEC 61784
(IEC/TR 62453-52-32:2017)
This Technical Report was approved by CENELEC on 2019-01-14.

CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden,
Switzerland, Turkey and the United Kingdom.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2019 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. CLC IEC/TR 62453-52-32:2019 E

European foreword
This document (CLC IEC/TR 62453-52-32:2019) consists of the text of IEC/TR 62453-52-32:2017
prepared by SC 65E "Devices and integration in enterprise systems" of IEC/TC 65 "Industrial-process
measurement, control and automation.

Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC shall not be held responsible for identifying any or all such patent rights.

Endorsement notice
The text of the International Standard IEC/TR 62453-52-32:2017 was approved by CENELEC as a
European Standard without any modification.

Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments)
applies.
NOTE 1  Where an International Publication has been modified by common modifications, indicated by (mod), the relevant
EN/HD applies.
NOTE 2  Up-to-date information on the latest versions of the European Standards listed in this annex is available here:
www.cenelec.eu.
Publication Year Title EN/HD Year
IEC 61131-3 2013 Programmable controllers - Part 3: EN 61131-3 2013
Programming languages
IEC 61158-6-10 -  Industrial communication networks - EN 61158-6-10 -
Fieldbus specifications - Part 6-10:
Application layer protocol specification -
Type 10 elements
IEC 61158 series Industrial communication networks - EN 61158 series
Fieldbus specifications - Part 1: Overview
and guidance for the IEC 61158 and IEC
61784 series
IEC 61784-1 2014 Industrial communication networks - EN 61784-1 2014
Profiles - Part 1: Fieldbus profiles
IEC 62453-1 2016 Field device tool (FDT) interface EN 62453-1 2017
specification - Part 1: Overview and
guidance
IEC 62453-2 2016 Field device tool (FDT) interface EN 62453-2 2017
specification - Part 2: Concepts and
detailed description
IEC TR 62453-42 2016 Field device tool (FDT) interface - -
specification - Part 42: Object model
integration profile - Common language
infrastructure
IEC 62453-303-2 2009 Field device tool (FDT) interface EN 62453-303-2 2009
specification - Part 303-2: Communication
profile integration - IEC 61784 CP 3/4, CP
3/5 and CP 3/6
IEC TR 62453-52-32 ®
Edition 1.0 2017-06
TECHNICAL
REPORT
colour
inside
Field device tool (FDT) interface specification –

Part 52-32: Communication implementation for common language

infrastructure – IEC 61784 CP 3/4, CP 3/5 and CP 3/6

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 25.040.40; 35.100.05; 35.110 ISBN 978-2-8322-4331-2

– 2 – IEC TR 62453-52-32:2017 © IEC 2017
CONTENTS
FOREWORD . 5
INTRODUCTION . 7
1 Scope . 8
2 Normative references . 8
3 Terms, definitions, symbols, abbreviated terms and conventions . 9
3.1 Terms and definitions. 9
3.2 Abbreviations . 9
3.3 Conventions . 9
3.3.1 Datatype names and references to datatypes . 9
3.3.2 Vocabulary for requirements . 9
3.3.3 Use of UML . 9
4 Bus Category . 9
5 Access to instance and device data . 9
5.1 General . 9
5.2 IO signals provided by DTM . 10
5.3 Data interfaces . 10
5.3.1 General . 10
5.3.2 Mapping PROFINET datatypes to FDT datatypes . 10
5.3.3 SemanticInfo . 11
6 Protocol specific behavior . 12
6.1 PROFINET device model . 12
6.2 Configuration and parameterization of PROFINET devices . 13
6.3 PROFINET – related information of a Device DTM . 13
6.4 Remarks on FDT 1.2 / 2 Compatibility . 14
7 Protocol specific usage of general FDT datatypes . 14
8 Protocol specific common datatype: PnDeviceAddress . 14
9 Network management . 15
9.1 General . 15
9.2 Configuration . 16
9.3 Process Data Items . 28
9.4 Parameterization . 28
10 Communication datatypes. 28
10.1 General . 28
10.2 ConnectRequest and ConnectResponse Services . 28
10.2.1 PnConnectRequest Service . 28
10.2.2 PnConnectResponse Service. 29
10.3 DisconnectRequest and DisconnectResponse Services . 30
10.3.1 PnDisconnectRequest Service . 30
10.3.2 PnDisconnectResponse Service . 31
10.4 TransactionRequest and TransactionResponse Services . 32
10.4.1 PnReadRequest Service . 32
10.4.2 PnReadResponse Service . 33
10.4.3 PnWriteRequest Service . 35
10.4.4 PnWriteResponse Service . 36
10.4.5 PnCancelRequest Service . 37
10.4.6 PnCancelResponse Service . 38

IEC TR 62453-52-32:2017 © IEC 2017 – 3 –
10.5 SubscribeRequest and SubscribeResponse Service . 39
10.5.1 PnSubscribeRequest . 39
10.5.2 PnSubscribeResponse . 40
10.6 UnsubscribeRequest and UnsubscribeResponse Service . 41
10.6.1 PnUnsubscribeRequest Service . 41
10.6.2 PnUnsubscribeResponse Service . 41
10.7 AbortMessage Service . 42
10.8 PnResponseError . 42
10.8.1 Communication error . 42
10.8.2 Handling of errors during Connect and Disconnect . 43
11 Datatypes for process data information . 43
11.1 General . 43
11.2 PnIOSignalInfo. 43
11.3 Mapping of PROFINET datatypes to FDT datatypes . 45
12 Device identification . 45
12.1 General . 45
12.2 PnDeviceScanInfo datatype . 45
12.3 PnDeviceIdentInfo datatype . 49
Bibliography . 51

Figure 1 – Part 52-32 of the IEC 62453 series . 7
Figure 2 – PROFINET Device Model . 13
Figure 3 – PROFINET Device Address . 15
Figure 4 – PROFINET Network Data . 16
Figure 5 – PnConnectRequest . 29
Figure 6 – PnConnectResponse . 30
Figure 7 – PnDisconnectRequest . 31
Figure 8 – PnDisconnectResponse . 32
Figure 9 – PnReadRequest . 33
Figure 10 – PnReadResponse . 34
Figure 11 – PnWriteRequest . 36
Figure 12 – PnWriteResponse . 37
Figure 13 – PnCancelRequest . 38
Figure 14 – PnCancelResponse . 39
Figure 15 – PnSubscribeRequest . 40
Figure 16 – PnSubscribeResponse . 40
Figure 17 – PnUnsubscribeRequest . 41
Figure 18 – PnUnsubscribeResponse . 41
Figure 19 – PnAbortMessage . 42
Figure 20 – PnResponseError . 43
Figure 21 – ProtocolIOSignalInfo . 44
Figure 22 – PnDeviceScanInfo datatype . 46
Figure 23 – PnDeviceIdentInfo . 49

Table 1 – Mapping of datatypes . 11

– 4 – IEC TR 62453-52-32:2017 © IEC 2017
Table 2 – Usage of SemanticInfo . 12
Table 3 – Usage of general datatypes . 14
Table 4 – PnDeviceAddress . 15
Table 5 – PROFINET Network Data . 17
Table 6 – PnConnectRequest datatype . 29
Table 7 – PnConnectResponse datatype . 30
Table 8 – PnDisonnectRequest datatype . 31
Table 9 – PnDisconnectResponse datatype . 32
Table 10 – PnReadRequest datatype . 33
Table 11 – PnReadResponse datatype . 35
Table 12 – PnWriteRequest datatype . 36
Table 13 – PnWriteResponse datatype . 37
Table 14 – PnCancelRequest datatype . 38
Table 15 – PnCancelResponse datatype . 39
Table 16 – PnSubscribeRequest datatype . 40
Table 17 – PnSubscribeResponse datatype . 40
Table 18 – PnUnsubscribeRequest datatype . 41
Table 19 – PnUnsubscribeResponse datatype . 42
Table 20 – PnAbortMessage datatype . 42
Table 21 – PnResponseError datatype . 43
Table 22 – PnDatatypeInfo . 44
Table 23 – ProtocollIOSignalInfo datatypes . 45
Table 24 – PnDeviceScanInfo datatype . 46
Table 25 – PnDeviceScanInfo specific mapping . 47
Table 26 – PnDeviceIdentInfo datatypes . 49
Table 27 – PnDeviceIndentInfo specific mapping . 50

IEC TR 62453-52-32:2017 © IEC 2017 – 5 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –

Part 52-32: Communication implementation
for common language infrastructure –
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 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.
The main task of IEC technical committees is to prepare International Standards. However, a
technical committee may propose the publication of a technical report when it has collected
data of a different kind from that which is normally published as an International Standard, for
example "state of the art".
IEC TR 62453-52-32, which is a technical report, 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-52-xy series is intended to be read in conjunction with its
corresponding part in the IEC 62453-3xy series. This document corresponds to
IEC 62453-303-2.
– 6 – IEC TR 62453-52-32:2017 © IEC 2017
The text of this technical report is based on the following documents:
Enquiry draft Report on voting
65E/440/DTR 65E/514/RVC
Full information on the voting for the approval of this technical report can be found in the
report on voting indicated in the above table.
This document has been drafted in accordance with the ISO/IEC Directives, Part 2.
The 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 document will remain unchanged until the
stability date indicated on the IEC website under "http://webstore.iec.ch" in the data related to
the specific document. At this date, the document will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
A bilingual version of this publication may be issued at a later date.

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.
IEC TR 62453-52-32:2017 © IEC 2017 – 7 –
INTRODUCTION
This part of IEC 62453 is an interface specification for developers of Field Device Tool (FDT)
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 fieldbuses 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 Device Type Manager (DTM), 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 kind of fieldbusses and thus meets the requirements for integrating different kinds of
devices into heterogeneous control systems.
Figure 1 shows how this part of the IEC 62453-52-xy series is aligned in the structure of the
IEC 62453 series.
Part 52-32
Communication
implementation
for common
language
infrastructure –
IEC 61784 CP 3/4,
CP 3/5 and CP 3/6
IEC
Figure 1 – Part 52-32 of the IEC 62453 series

– 8 – IEC TR 62453-52-32:2017 © IEC 2017
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –

Part 52-32: Communication implementation
for common language infrastructure –
IEC 61784 CP 3/4, CP 3/5 and CP 3/6

1 Scope
This part of the IEC 62453-52-xy series, which is a Technical Report, provides information for
technology into the CLI-based implementation of FDT interface
integrating the PROFINET®
specification (IEC TR 62453-42).
This part of IEC 62453 specifies implementation of communication and other services based
on IEC 62453-303-2.
This document neither contains the FDT specification nor modifies it.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their
content constitutes requirements of this document. For dated references, only the edition
cited applies. For undated references, the latest edition of the referenced document (including
any amendments) applies.
IEC 61131-3:2013, Programmable controllers – Part 3: Programming languages
IEC 61158-6-10, Industrial communication networks – Fieldbus specifications – Part 6-10:
Application layer protocol specification – Type 10 elements
IEC 61158 (all parts), Industrial communication networks – Fieldbus specifications
IEC 61784-1:2014, Industrial communication networks – Profiles – Part 1: Fieldbus profiles
IEC 62453-1:2016, Field device tool (FDT) interface specification – Part 1: Overview and
guidance
IEC 62453-2:2016, Field device tool (FDT) interface specification – Part 2: Concepts and
detailed description
IEC TR 62453-42: 2016, Field device tool (FDT) interface specification – Part 42: Object
model integration profile – Common language infrastructure
IEC 62453-303-2:2009, Field device tool (FDT) interface specification – Part 303-2:
Communication profile integration – IEC 61784 CP 3/4, CP 3/5 and CP 3/6
IEC 62453-303-2:2009/AMD1:2016
___________
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.

IEC TR 62453-52-32:2017 © IEC 2017 – 9 –
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,
IEC 62453-2, IEC TR 62453-42 and IEC 62453-303-2 apply.
ISO and IEC maintain terminological databases for use in standardization at the following
addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
3.2 Abbreviations
For the purposes of this document, the abbreviations given in IEC 62453-1, IEC 62453-2,
IEC 62453-303-2, IEC TR 62453-42, and the following apply.
I&M Identification and maintenance functions
3.3 Conventions
3.3.1 Datatype names and references to datatypes
The conventions for naming and referencing of datatypes are explained in FDT 2.0
Specification.
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:2016.
4 Bus Category
PROFINET protocols are identified by the unique identifiers in busCategory attributes as
specified in IEC 62453-303-2.
5 Access to instance and device data
5.1 General
Used at interfaces:
– IInstanceData
– IDeviceData
The minimum set of provided data shall be:

– 10 – IEC TR 62453-52-32:2017 © IEC 2017
– Process values shall be modeled as ProcessData including ranges and scaling, where
applicable.
– All network configuration related parameters shall be exposed in NetworkData (see
Clause 9).
– All startup parameters of sub modules shall be exposed in NetworkData (see Clause 9).
– It is recommended to expose startup parameters in the IDeviceData and IInstanceData
interfaces; exposure of additional parameters is at the device vendor’s discretion. Profiles
may define a mandatory set of parameters.
5.2 IO signals provided by DTM
A DTM shall provide IO signal information for the device using the IProcessData interface.
The IO signals describe datatype and address parameters of process data as detailed in
Clause 11.
5.3 Data interfaces
5.3.1 General
Exposure of device parameters is at the vendor’s discretion. Profiles may define the
mandatory exposure of profile specific parameters. It is recommended to expose at least all
startup parameters.
5.3.2 Mapping PROFINET datatypes to FDT datatypes
PROFINET uses datatypes as specified in IEC 61158 for the transmission on the fieldbus.
The FDT interfaces IDeviceData and IInstanceData use .NET datatypes, while PLC
applications use datatypes as defined in IEC 61131-3. This subclause defines the mapping of
parameter datatypes, whereas mapping of process datatypes is defined in Clause 11. The
mapping of parameter datatypes is described in Table 1.

IEC TR 62453-52-32:2017 © IEC 2017 – 11 –
Table 1 – Mapping of datatypes
PROFINET datatype FDT datatype IEC datatype
Bit boolean BOOL
Integer8 int SINT
Integer16 int INT
Integer32 int DINT
Integer64 int LINT
Unsigned8 byte USINT
Unsigned16 unsigned UINT
Unsigned32 unsigned UDINT
Unsigned64 unsigned ULINT
Float32 float REAL
Float64 double LREAL
Date date LWORD
TimeOfDay dateAndTime LWORD
TimeOfDayWithoutDateIndication time TIME_OF_DAY
TimeDifference structured LWORD
TimeOfDayWithoutDateIndication duration DWORD
NetworkTime structured LWORD
NetworkTimeDifference structured LWORD
VisibleString string STRING
OctetString hexString STRING
Unsigned8Unsigned8 - WORD
Float32Unsigned8 - LWORD
Float32Status8 structured LWORD
F_MessageTrailer4Byte structured DWORD
F_MessageTrailer5Byte structured LWORD
additional GSDML datatypes
Bit boolean BOOL
BitArea BinaryBitArray ARRAY OF BYTE

5.3.3 SemanticInfo
The SemanticInfo provides means to uniquely identify parameters. The usage of SemanticInfo
attributes is defined in Table 2.

– 12 – IEC TR 62453-52-32:2017 © IEC 2017
Table 2 – Usage of SemanticInfo
Attribute Description of use for PROFINET
SemanticInfo.ReadAddress The value of ReadAddress and WriteAdress is a string conforming to a
SemanticInfo.WriteAddress pattern as follows:
Api.Slot.Subslot.Index.ByteOffset.BitOffset.BitLength
where
Api = API number
Slot = Slot number
Subslot = Subslot number
Index = Index number
ByteOffset = start byte within the index
BitOffset = start bit within the index
BitLength = length in bits
All values are unsigned integers.
NOTE Profiles may define additional address formats.
SemanticInfo.ApplicationDomain The value of ApplicationDomain is as follows:
FDT PROFINET
FDT PROFIDRIVE
NOTE Profiles may define additional ApplicationDomain values.
SemanticInfo.SemanticId The value of SemanticId is vendor specific. Profiles may define a distinct
set of mandatory SemanticId values.

6 Protocol specific behavior
6.1 PROFINET device model
The PROFINET device model is captured in a hierarchical structure of ProtocolNetworkData
class (see Figure 2). Further details on attributes and methods are provided in Clause 9.

IEC TR 62453-52-32:2017 © IEC 2017 – 13 –

IEC
Figure 2 – PROFINET Device Model
6.2 Configuration and parameterization of PROFINET devices
In order to enable a PROFINET Communication DTM to configure and parameterize a
PROFINET Network, all type data usually included in a vendor specific GSDML file, are
provided in NetworkData (see Clause 9 for further details). The Communication DTM is
responsible for calculating or querying any instance data needed for network configuration.
6.3 PROFINET – related information of a Device DTM
The information used by a PROFINET controller to set up the PROFINET network properly
and allow cyclic communication between control system and PROFINET devices is provided
by a DTM in:
• PROFINET network data
• Process data items.
A DTM of a PROFINET device shall deliver these parts of PROFINET related information to
get integrated into an FDT-based engineering system. Below (see Clauses 8, 9 and 11), a
more detailed description is given on how to generate and how to provide this information.

– 14 – IEC TR 62453-52-32:2017 © IEC 2017
This specification makes no assumptions whether a modular PROFINET device is modeled in
a Device DTM, Composite DTM or Gateway DTM. All types of DTMs have to provide all
mandatory information defined in the following chapters.
6.4 Remarks on FDT 1.2 / 2 Compatibility
A variety of features and capabilities have been included in PROFINET since the release of
the FDT 1.2 Annex for PROFINET. In order to utilize these additional features, a pure FDT 2.0
environment is required. For mixed topologies, Table 5 provides information on which data is
available with FDT 1.2 DTMs and consequently, is available in a mixed topology after
transformation. Conversely, only this subset is available when using FDT 2.0 DTMs (as child
DTMs) below a FDT 1.2 DTM (as parent DTM) in a mixed topology.
7 Protocol specific usage of general FDT datatypes
The FDT2.0 Specification already defines a set of datatypes that can be used to identify a
device and to provide device information. This clause describes how these datatypes are
used with PROFINET.
Table 3 – Usage of general datatypes
Attribute Description for use in PROFINET
ProtocolId See Clause 4
PhysicalLayer See Clause 4
ApplicationDomian/ See 5.3.3
SemanticId
Address See Clause 8
ManufacturerId See ‘IM0.IM_Vendor_ID‘ and ‘DCP.DeviceVendorValue’ given in 12.3
DeviceTypeId See ‘DCP_DeviceIdentNumber’ given in 12.3
HardwareRevision See ‘IM_Hardware_Revision’ given in 12.3
SoftwareRevision See ‘IM_Software_Revision’ given in 12.3
ProtocolIdentificationProfile Identifies the protocol specific profile that was used for device
identification. It contains one of the values "DCP" or "IM".
Tag See ‘DeviceName’ in 12.2
Serialnumber See 12.2
ProtocolSpecificProperties See ‘DCP_ManufacturerSpecificString‘, ‘IM_OrderID’, ‘IM_Profile_ID’,
‘IM_Profile_Specific_Type’ ‘DCP_DeviceRoleDetail’, ‘ConfiguredState’
in 12.3
8 Protocol specific common datatype: PnDeviceAddress
The only protocol-specific common datatype is PnDeviceAddress. The protocol specific device
address relates to network management and communication. See Figure 3 and Table 4.

IEC TR 62453-52-32:2017 © IEC 2017 – 15 –
FdtDatatype
Network::ProtocolDeviceAddress
# ProtocolDeviceAddress()
^ TransformDeviceAddress() :String
PnDeviceAddress
{leaf}
«Property»
+ IPAddress :System.Net.IPAddress
+ IPDefaultGateway :System.Net.IPAddress
+ IPSubnetMask :System.Net.IPAddress
+ MacAddress :byte ([])
+ NameOfStation :string
- CheckMacAddressLength(byte[]) :bool
- CheckStationName(string) :bool
+ PnDeviceAddress()
+ PnDeviceAddress(string, IPAddress, IPAddress, IPAddress, byte[])
# TransformDeviceAddress() :string
+ Verify() :void
IEC
Figure 3 – PROFINET Device Address
Table 4 – PnDeviceAddress
Property Usage Multiplicity Description
IPAddress M [1.1] The attribute contains the IP address that is assigned to the
device. The IP address is a secondary address. The default value
is System.Net.IPAddress(new byte[] { 0, 0, 0, 0 }).
IPDefaultGateway M [1.1] The attribute contains the default gateway address. The default
value is null.
IPSubnetMask M [1.1] The attribute contains the subnet mask. The default value is
System.Net.IPAddress(new byte[] { 255, 255, 255, 255 }).
MacAddress M [1.1] The attribute contains the MAC address of the device. The MAC
address is a secondary address.
The default Value is new byte[6].
NameOfStation M [1.1] The station name is the primary address. The default value is an
empty string.
9 Network management
9.1 General
The data needed for management of the network is exposed by the Device DTM in the
INetworkData interface. See Figure 4.

– 16 – IEC TR 62453-52-32:2017 © IEC 2017
NetworkDataInfo
NetworkDataItems
0.*
1.* NetworkData
Item
NetworkDataItems
NetworkData
NetworkDataGroup
< T > PnDeviceNetworkData
NetworkData < T > PnModuleNetworkData
ProtocolNetworkData
< T > PnGenericSubmoduleNetworkData
PnDeviceNetworkData
ProtocolSpecificNetworkData + NetworkDataGroup PnModules
PnModuleNetworkData
+ NetworkDataGroup PnSubmodules
ProtocolSpecificNetworkData
PnDapNetworkData
ProtocolSpecificNetworkData
PnGenericSubmodule
NetworkData
PnPortSubmodule PnInterfaceSubmoduleNe PnIoSubmodule
NetworkData tworkData NetworkData

IEC
Used in:
INetworkData::GetNetworkDataInfo()
Figure 4 – PROFINET Network Data
The datatype PnDeviceAddress is used for defining the network address of a device.
The protocol specific datatypes are based on definitions given in the IEC 61784 and
IEC 61158 specifications. Furthermore, they contain additional information about the device
that is needed by systems to configure PROFINET links and to establish communication
between the PROFINET Controller and the PROFINET devices.
9.2 Configuration
The configuration of the device itself is done with the aid of the DTM’s GUI. Downloading the
configuration into the PROFINET device is performed via the PROFINET controller. To do that
and in order to set up the bus communication, the PROFINET controller needs information
from the DTM. Table 5 describes the properties of PROFINET specific network data.

IEC TR 62453-52-32:2017 © IEC 2017 – 17 –

Table 5 – PROFINET Network Data
Name Datatype Description FDT FDT
1.2.1 2.0
PnDeviceNetworkData Class
PnModules NetworkDataGroup The related modules of the Device. M
PnRole Enumeration Specifies the role for shared Device. M
ObjectUUID_LocalIndex UInt16 //ISO15745Profile/ProfileBody/ApplicationProcess/DeviceAccessPointList/DeviceAcce M
ssPointItem
DeviceID Uint16 //ISO15745Profile/ProfileBody/DeviceIdentity M
DeviceName string Address information according to the PROFINET specification. M
VendorID UInt16 //ISO15745Profile/ProfileBody/DeviceIdentity M
InfoText string Additional textual information. Shall only be set by DTM. O M
VendorName string //ISO15745Profile/ProfileBody/DeviceIdentity/VendorName M
ArType UInt16 ARType according to the PROFINET specification. Shall only be set by Parent. M M
ArUUID Guid ARUUID according to the PROFINET specification. M M
Shall only be set by Parent.
ArProperties UInt32 ARProperties according to the PROFINET specification. M M
Shall only be set by Parent.
DeviceTypeInformation Document The attribute contains the path to the device description file. O M
For Profinet devices it is mandatory to provide this attribute.
Only a parent developed according to the Profinet Annex can handle GSDML
information.
PnModuleNetworkData
Class
PnSubmodules NetworkDataGroup Contains the elements for addressing a IO Device. M
SlotNumber UInt16 The slot address that is used by the module. M M
Shall be set by DTM during configuration. Can be set by Parent during topology scan.
ModuleIdentNumber UInt32 The ModuleIdentNumber according to the PROFINET specification. M M
Shall be set by DTM during configuration. Can be set by Parent during topology scan.
Name string Name for the enclosing module. M M
Shall only be set by DTM.
– 18 – IEC TR 62453-52-32:2017 © IEC 2017

Name Datatype Description FDT FDT
1.2.1 2.0
Descriptor string Description for the enclosing module. O M
Shall only be set by DTM.
PnDapNetworkData Class
PnDeviceAddress Class Contains the elements for addressing a PROFINET Device. M
MaxInputLength UInt16 //ISO15745Profile/ProfileBody/ApplicationProcess/DeviceAccessPointList/DeviceAcce M
ssPointItem/IOConfigData
MaxOutputLength UInt16 //ISO
...