EN 62769-103-4:2015

SLOVENSKI STANDARD
01-november-2015
1DSUDYHLQ]GUXåHYDQMHYSURL]YRGQHVLVWHPH±9NOMXþLWHYSURFHVQHQDSUDYH)',
3URILOLGHO352),1(7,(&
Devices and integration in enterprise systems; Field Device Integration (FDI) - Profiles -
Part 103-4: PROFINET (IEC 62769-103-4:2015)
Feldgeräteintegration (FDI) - Profile - Teil 103-4: PROFINET (IEC 62769-103-4:2015)
Intégration des appareils de terrain (FDI) - Partie 103-4: Profils - PROFINET (IEC 62769-
103-4:2015)
Ta slovenski standard je istoveten z: EN 62769-103-4:2015
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.

EUROPEAN STANDARD EN 62769-103-4

NORME EUROPÉENNE
EUROPÄISCHE NORM
June 2015
ICS 25.040.40; 35.100
English Version
Field Device Integration (FDI) - Part 103-4: Profiles - PROFINET
(IEC 62769-103-4:2015)
Intégration des appareils de terrain (FDI) - Partie 103-4: Feldgeräteintegration (FDI) - Profile - Teil 103-4:
Profils - PROFINET PROFINET
(IEC 62769-103-4:2015) (IEC 62769-103-4:2015)
This European Standard was approved by CENELEC on 2015-06-16. CENELEC members are bound to comply with the CEN/CENELEC
Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC
Management Centre or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the
same status as the official versions.
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, 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: Avenue Marnix 17, B-1000 Brussels
© 2015 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 62769-103-4:2015 E

European foreword
The text of document 65E/355/CDV, future edition 1 of IEC 62769-103-4, prepared by SC 65E
"Devices and integration in enterprise systems", of IEC/TC 65 "Industrial-process measurement,
control and automation" was submitted to the IEC-CENELEC parallel vote and approved by
CENELEC as EN 62769-103-4:2015.
The following dates are fixed:
• latest date by which the document has to be implemented at (dop) 2016-03-16
national level by publication of an identical national
standard or by endorsement
(dow) 2018-06-16
• latest date by which the national standards conflicting with
the document have to be withdrawn

Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC [and/or CEN] shall not be held responsible for identifying any or all such
patent rights.
Endorsement notice
The text of the International Standard IEC 62769-103-4:2015 was approved by CENELEC as a
European Standard without any modification.
In the official version, for Bibliography, the following note has to be added for the standard indicated :
IEC 61158 NOTE Harmonized in EN 61158 series.
IEC 61784-1 NOTE Harmonized as EN 61784-1.
1)
IEC 61804-4 NOTE Harmonized as EN 61804-4 (not modified).

1) To be published.
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
NOTE 1 When 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 61158-5-10 -  Industrial communication networks - EN 61158-5-10 -
Fieldbus specifications -
Part 5-10: Application layer service
definition - Type 10 elements
IEC 61784-2 -  Industrial communication networks - EN 61784-2 -
Profiles -
Part 2: Additional fieldbus profiles for real-
time networks based on ISO/IEC 8802-3
IEC 61804 series Function blocks (FB) for process control - EN 61804 series
Electronic device description language
(EDDL)
IEC 62541-100 2015 OPC unified architecture - EN 62541-100 2015
Part 100: Device Interface
2)
IEC 62769-2 -  Field Device Integration (FDI) - EN 62769-2 -
Part 2: FDI Client
2)
IEC 62769-4 -  Field Device Integration (FDI) - EN 62769-4 -
Part 4: FDI Packages
2)
IEC 62769-5 -  Field Device Integration (FDI) - EN 62769-5 -
Part 5: FDI Information Model
2)
IEC 62769-6 -  Field Device Integration (FDI) - EN 62769-6 -
Part 6: FDI Technology Mapping
2)
IEC 62769-7 -  Field Device Integration (FDI) - EN 62769-7 -
Part 7: FDI Communication Devices

2) To be published.
IEC 62769-103-4 ®
Edition 1.0 2015-05
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Field device integration (FDI) –

Part 103-4: Profiles – PROFINET

Intégration des appareils de terrain (FDI) –

Partie 103-4: Profils – PROFINET

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040.40; 35.100 ISBN 978-2-8322-2624-7

– 2 – IEC 62769-103-4:2015 © IEC 2015
CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 7
2 Normative references . 7
3 Terms, definitions, abbreviated terms and acronyms . 8
3.1 Terms and definitions . 8
3.2 Abbreviated terms and acronyms . 8
4 Conventions . 8
4.1 EDDL syntax . 8
4.2 XML syntax . 8
4.3 Capitalizations . 8
5 Profile for PROFINET . 9
5.1 General . 9
5.2 Catalog profile . 9
5.2.1 Protocol support file . 9
5.2.2 CommunicationProfile definition . 10
5.2.3 Profile device . 10
5.2.4 Protocol version information . 10
5.3 Associating a Package with a device . 11
5.3.1 Device type identification mapping . 11
5.3.2 Device type revision mapping . 12
5.4 Information Model mapping . 13
5.4.1 ProtocolType definition . 13
5.4.2 DeviceType mapping . 14
5.4.3 FunctionalGroup identification definition . 14
5.5 Topology elements . 14
5.5.1 ConnectionPoint definition . 14
5.5.2 Communication Device definition . 16
5.5.3 Communication service provider definition . 17
5.5.4 Network definition . 17
5.6 Methods . 18
5.6.1 Methods for FDI Communication Servers . 18
5.6.2 Methods for Gateways . 22
Annex A (normative) Topology scan schema . 30
A.1 General . 30
A.2 Network . 30
A.3 ProfinetNetworkT . 30
A.4 ProfinetConnectionPointT . 30
A.5 ProfinetIdentificationT . 31
A.6 MACT . 32
A.7 IPv4T . 32
A.8 IPv6T . 32
A.9 DNSNameT . 32
A.10 Hex4DigitT . 32
Annex B (normative) Transfer service parameters . 33

IEC 62769-103-4:2015 © IEC 2015 – 3 –
B.1 General . 33
B.2 sendData . 33
B.3 receiveData . 33
B.4 TransferSendDataT . 33
B.5 TransferResultDataT . 34
B.6 OperationT . 34
Bibliography . 35

Figure 1 – Version mapping problem . 12

Table 1 – ProtocolSupportFile for FDI Device Packages . 9
Table 2 – ProtocolSupportFile for FDI Communication Packages . 10
Table 3 – Catalog values for profile devices . 10
Table 4 – Version mapping examples . 11
Table 5 – Device identification information mapping . 12
Table 6 – Protocol type Profinet_IO . 13
Table 7 – DeviceType Property mapping . 14
Table 8 – PROFINET identification type definition . 14
Table 9 – ConnectionPoint type for Profinet_IO . 15
Table 10 – Method Connect arguments . 19
Table 11 – Method Disconnect arguments . 19
Table 12 – Method Transfer arguments . 20
Table 13 – Method SetAddress arguments . 21
Table 14 – Method Connect arguments . 23
Table 15 – Method Transfer arguments . 25
Table 16 – Method SetAddress arguments . 27
Table A.1 – Elements of ProfinetNetworkT . 30
Table A.2 – Attributes of ProfinetConnectionPointT . 31
Table A.3 – Elements of ProfinetConnectionPointT . 31
Table A.4 – Attributes of ProfinetIdentificationT . 31
Table B.1 – Attributes of TransferSendDataT . 34
Table B.2 – Attributes of TransferResultDataT . 34

– 4 – IEC 62769-103-4:2015 © IEC 2015
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
FIELD DEVICE INTEGRATION (FDI) –

Part 103-4: Profiles – PROFINET

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.
International Standard IEC 62769-103-4 has been prepared by subcommittee 65E: Devices
and integration in enterprise systems, of IEC technical committee 65: Industrial-process
measurement, control and automation.
The text of this standard is based on the following documents:
CDV Report on voting
65E/355/CDV 65E/418/RVC
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts in the IEC 62769 series, published under the general title Field Device
Integration (FDI), can be found on the IEC website.

IEC 62769-103-4:2015 © IEC 2015 – 5 –
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC website 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 62769-103-4:2015 © IEC 2015
INTRODUCTION
The International Electrotechnical Commission (IEC) draws attention to the fact that it is
claimed that compliance with this document may involve the use of patents concerning
a) method for the supplying and installation of device-specific functionalities, see Patent
Family DE10357276;
b) method and device for accessing a functional module of automation system, see Patent
Family EP2182418;
c) methods and apparatus to reduce memory requirements for process control system
;
software applications, see Patent Family US2013232186
d) extensible device object model, see Patent Family US12/893,680;
IEC takes no position concerning the evidence, validity and scope of this patent right.
The holders of these patent rights have assured the IEC that he/she is willing to negotiate
licences either free of charge or under reasonable and non-discriminatory terms and
conditions with applicants throughout the world. In this respect, the statement of the holder of
this patent right is registered with IEC. Information may be obtained from:
a) ABB Research Ltd
Claes Rytoft
Affolterstrasse 4
Zurich, 8050
Switzerland
b) Phoenix Contact GmbH & Co KG
Intellectual Property, Licenses & Standards
Flachsmarktstrasse 8, 32825 Blomberg
Germany
c) Fisher Controls International LLC
John Dilger, Emerson Process Management LLLP
st
301 S. 1 Avenue, Marshaltown, Iowa 50158
USA
d) Rockwell Automation Technologies, Inc.
1 Allen-Bradley Drive
Mayfield Heights, Ohio 44124
USA
Attention is drawn to the possibility that some of the elements of this document may be the
subject of patent rights other than those identified above. IEC shall not be held responsible for
identifying any or all such patent rights.
ISO (www.iso.org/patents) and IEC (http://patents.iec.ch) maintain on-line data bases of
patents relevant to their standards. Users are encouraged to consult the data bases for the
most up to date information concerning patents.

IEC 62769-103-4:2015 © IEC 2015 – 7 –
FIELD DEVICE INTEGRATION (FDI) –

Part 103-4: Profiles – PROFINET

1 Scope
This part of IEC 62769 specifies an FDI profile of IEC 62769 for IEC 61784-2_CP 3/4,
IEC 61784-2_CP3/5 and IEC 61784-2_CP3/6 (PROFINET ).
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
IEC 61158-5-10, Industrial communication networks – Fieldbus specifications – Part 5-10:
Application layer service definition – 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 61804 (all parts), Function blocks (FB) for process control and Electronic Device
Description Language (EDDL)
IEC 62541-100:2015, OPC Unified Architecture – Part 100: OPC UA for Devices
IEC 62769-2, Field Device Integration (FDI) – Part 2: FDI Client
NOTE 1 IEC 62769-2 is technically identical to FDI-2022.
IEC 62769-4, Field Device Integration (FDI) – Part 4: FDI Packages
NOTE 2 IEC 62769-4 is technically identical to FDI-2024.
IEC 62769-5, Field Device Integration (FDI) – Part 5: FDI Information Model
NOTE 3 IEC 62769-5 is technically identical to FDI-2025.
IEC 62769-6, Field Device Integration (FDI) – Part 6: FDI Technology Mapping
NOTE 4 IEC 62769-6 is technically identical to FDI-2026.
IEC 62769-7, Field Device Integration (FDI) – Part 7: FDI Communication Devices
NOTE 5 IEC 62769-7 is technically identical to FDI-2027.
PI Order No.: 2.122:2008, Specification for PROFIBUS – Device Description and Device
Integration – Volume 1: GSD, V5.1, July 2008: GSD; available at
—————————
PROFINET is the trade name of the non-profit consortium PROFIBUS & PROFINET International. This information is given
for the convenience of users of this technical report and does not constitute an endorsement by IEC of the trademark holder
or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the
trade name holder.
– 8 – IEC 62769-103-4:2015 © IEC 2015
PI Order No.: 2.352:2014, GSDML Specification for PROFINET IO; available at

3 Terms, definitions, abbreviated terms and acronyms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 61158-5-10,
IEC 61784-2, IEC 61804, IEC 62541-100, IEC 62769-2, IEC 62769-4, IEC 62769-5,
IEC 62769-6, IEC 62769-7 and PI Order No.: 2.352:2014 apply.
3.2 Abbreviated terms and acronyms
For the purposes of this document, the following abbreviated terms and acronyms apply:
DCP Discovery and basic configuration protocol (according to IEC 61158-5-10)
DNS Domain name system
EDD Electronic Device Description
EDDL Electronic Device Description Language (see IEC 61804)
GSD General station description (see PI Order No.: 2.122:2008)
GSDML GSD markup language (see PI Order No.: 2.352:2014)
IP Internet protocol (RFC 791)
UIP User Interface plug-in
UUID Universal unique identifier (see ISO/IEC 11578)
XML Extensible markup language (see REC-xml-20081126)
4 Conventions
4.1 EDDL syntax
This part of IEC 62769 specifies content for the EDD component that is part of FDI
Communication Packages. The specification content using EDDL syntax uses the font
Courier New. The EDDL syntax is used for method signature, variable, data structure and
component declarations.
4.2 XML syntax
XML syntax examples use the font Courier New. The XML syntax is used to describe XML
document schema.
EXAMPLE:
4.3 Capitalizations
The IEC 62769 series uses capitalized terms to emphasize that these terms have an FDI
specific meaning.
Some of these terms using an acronym as a prefix for example
• FDI Client, or
• FDI Server.
Some of these terms are compound terms such as:
• Communication Servers, or
IEC 62769-103-4:2015 © IEC 2015 – 9 –
• Profile for Package.
Parameter names or attributes are concatenated to a single term, where the original terms
start in this term with a capital letter such as:
• ProtocolSupportFile, or
• ProtocolType.
Parameter names or attributes can also be constructed by using an underscore character to
concatenate two or more terms such as:
• PROFILE_ID, or
• Profinet_PA_Network.
5 Profile for PROFINET
5.1 General
This profile document to the FDI specification in IEC 62769 specifies the protocol specifics
needed for FDI Packages describing Communication Servers, Gateways and Devices.
For Communication Servers this document defines also protocol specifics as these need to be
considered in the Communication Servers hosted Information Model.
5.2 Catalog profile
5.2.1 Protocol support file
5.2.1.1 FDI Device Package
A GSD file is a mandatory Attachment for FDI Device Packages representing PROFINET IO
devices.
Protocol specific attachments are mentioned in the Package Catalog as defined in
IEC 62769-5. A communication feature list mark-up language (GSDML) file according to PI
Order No.: 2.352:2014 is a mandatory attachment for FDI Device Packages representing
PROFINET devices. Table 1 specifies the parameters of ProtocolSupportFile in the FDI
Device Package.
Table 1 – ProtocolSupportFile for FDI Device Packages
Parameter Description
Content Type text/xml
Root Namespace Empty
Source Relationship http://fdi-cooperation.com/2010/relationship/attachment-protocol
Filename According to PI Order No.: 2.352:2014

5.2.1.2 FDI Communication Package
A GSDML file as specified in ISO 15745-4:2003/AMD1:2006, is an optional attachment for FDI
Communication Packages representing PROFINET IO devices. Table 2 specifies the
parameters of ProtocolSupportFile for FDI Communication Packages.

– 10 – IEC 62769-103-4:2015 © IEC 2015
Table 2 – ProtocolSupportFile for FDI Communication Packages
Parameter Description
Content Type text/xml
Root Namespace Empty
Source Relationship http://fdi-cooperation.com/2010/relationship/attachment-protocol
Filename According to PI Order No.: 2.352:2014

5.2.2 CommunicationProfile definition
IEC 62769-4 defines a CommunicationProfileT enumeration type for the Catalog XML
schema. The PROFINET specific value defined inside this enumeration is "profinet_io".
5.2.3 Profile device
A Profile Package shall provide the catalog values for profile devices, enabling the FDI Server
to leverage a generic device description, if a specific one is not available. The definitions in
Table 3 focus on catalog content that is vendor independent.
Table 3 – Catalog values for profile devices
Element Attribute Content
PackageType – Profile
Manufacturer – Empty
DeviceModel – Allowed profile identifier values (PROFILE_ID) are provided by
PROFIBUS & PROFINET International (PI). PI provides and maintains an
XML file (Profile_ID_Table) containing the assignment of PROFILE_ID to
profiles.
It is available at
The file can be downloaded by any engineering or service tool whenever
it is connected to the Internet.
NOTE More information is provided in PI Order No.: 3.502 (I&M Profile)
and related profile definitions referred therein.
The string format shall be hexadecimal starting with 0x, e.g. ‘0x3D00’.

5.2.4 Protocol version information
IEC 62769-4 defines an element type named InterfaceT for the Catalog XML schema. The
element type InterfaceT contains an element named Version which is supposed to provide
version information about the applied communication protocol profile. The value has to follow
the IEC 62769-4 defined version information schema defined in the element type VersionT.
Table 4 describes how to apply the currently known protocol versions defined by the non-
profit consortium PROFIBUS & PROFINET International. The general rule is to apply the
value “0” for parts of the version information according to IEC 62769-4 that are not used in
currently known protocol versions.

IEC 62769-103-4:2015 © IEC 2015 – 11 –
Table 4 – Version mapping examples
Protocol / Version InterfaceT Version value
PROFINET Version 2.3 2.3.0
NOTE 1 This table is just an example since this document cannot foresee how future protocol versions will be
defined.
NOTE 2 The currently known PROFINET protocol revision information provides major and minor version
information. Leading zeros are not considered in version value evaluation since only the actual decimal values
are relevant.
5.3 Associating a Package with a device
5.3.1 Device type identification mapping
The purpose of a device type identification mapping is to enable FDI host systems to compare
the scan result against the topology representation in the Information Model. FDI host
systems shall also be enabled to determine the FDI Device Package that fits for a device
entry contained in the scan result. This will enable the user of an FDI host system to
synchronize the Information Model with the actual installation.
The communication server implemented scan service (defined in 5.6.1.7) provides a scan
result through an XML document (schema defined in Annex A).
The Gateway implemented scan service (defined in 5.6.2.7) provides a scan result by means
of the Information Model that contains data structures created from EDD content as specified
in 5.6.2.7.
Common for both ways of presenting the scan result is that scan results contain device type
identification and device instance identification.
FDI host systems comparing the actual network topology configuration against the topology
representation in the Information Model shall be enabled to handle the following situations:
a) The physical Device instance identified at a specific device address is not logically
present in the Information model (as Instance): Enable the FDI Host system to find the
appropriate FDI Device package according to the device catalogue information.
b) The physical Device instance identified by the device address is logically present in the
Information Model (as Instance): Enable the FDI Host system to compare the device type
information presented in the scan result (see the identification in Clause A.5 and 5.6.2.7)
and the device type specific information of the Instance present in the Information Model.
The FDI Device package contains device type identification information that can be compared
to the scan result based on the Catalog Schema in IEC 62769-4 which defines the XML
element (simple) type “DeviceModel” and “Manufacturer”. Both types are used in (complex)
element types “Protocol” and “RegDeviceType”.
As a result of the FDI Package deployment the FDI Package information is then present in the
Information Model as specified FunctionalGroup Identification containing VendorID and
DeviceID (see 5.4.3).
The mapping between different device identification data sources is described in Table 5.
Since scan results provided by the Communication Server or Gateway can convey data that is
produced by the device (firmware) the device type identification mapping shall be supported
by providing corresponding data in the FDI Device Package contained Catalog and
Information Model.
– 12 – IEC 62769-103-4:2015 © IEC 2015
Table 5 – Device identification information mapping
FDI Device Package Information Model Communication Server Gateway provided scan
provided scan result result
Catalog specified type FunctionalGroup: Element (path): COLLECTION
Identification ConnectionPoint/Identificat ConnectionPoint.
Manufacturer
Browse Name: ion Identification.VendorID
VendorID Attribute:
VendorID
Catalog specified type FunctionalGroup: Element (path): COLLECTION
Identification ConnectionPoint/Identificat ConnectionPoint.
DeviceModel
Browse Name: ion Identification.DeviceID
DeviceID Attribute:
DeviceID
5.3.2 Device type revision mapping
IEC 62769-4 envisions a concept that allows determining the compatibility between an FDI
Device Package and a Device. IEC 62769-4 specifies a life cycle management process
bearing on a single version information provided for the entire device.
PROFINET IO related specifications, for example PI Order No.: 2.352:2011 (GSDML) and PI
Order No.: 3.502 (I&M), split the device revision into software and hardware related
information. These specifications do not outline any rules whether the GSD, GSDML or I&M
specified HARDWARE_REVISION is independent from SOFTWARE_REVISION.
The goal of 5.3.2 is to describe the translation rules between the PROFINET IO related
specifications describing their way of providing version information and the IEC 62769-4
specified way of containing version information that can be compared against the version read
from the device. The purpose is to determine compatibility between an FDI Device Package
and a Device. (Figure 1 depicts the problem.)
FDI PROFINET
I&M: HARDWARE_REVISION
GSDML: HardwareRelease
FDI
FDI Profile
specified
specifed
Device
translation
revision
I&M: SOFTWARE_REVISION
GSDML: SoftwareRelease
IEC
Figure 1 – Version mapping problem
The firmware of a device implements the data exchange interface which shall be described by
means of the FDI Device Package content (EDD). A device firmware that implements the
GSD, GSDML or I&M profile enables reading the values SOFTWARE_REVISION and
HARDWARE_REVISION. The access to these values shall be described in the FDI Device
Package contained EDD.
Firmware modifications that affect the firmware implemented data exchange interface shall be
reflected in the FDI Device Package. Such firmware and device description modification shall
be visible in the SOFTWARE_REVISION.
Hardware related modifications shall be captured in the HARDWARE_REVISION value.
Hardware related modifications do not necessarily require always a firmware update. Thus

IEC 62769-103-4:2015 © IEC 2015 – 13 –
HARDWARE_REVISION cannot be used to determine compatibility between a device and the
FDI Device Package. But if a hardware modification requires firmware modifications both
HARDWARE_REVISION and SOFTWARE_REVISION shall be changed.
The IEC 62769-4 specifies the Catalog schema and an element DeviceVersion which is used
in the element type declaration ListOfSupportedDeviceVersions. The value of DeviceVersion
shall be compared to the device provided SOFTWARE_REVISION in order to determine the
compatibility between an FDI Device Package and a Device.
The data format for the SOFTWARE_REVISION is a string while the DeviceVersion expects
three numbers for major, minor, and revision. Therefore the following rules apply: If the string
has the format .. references to a simple integer number in the
string such as ‘1’ or ‘12’, not to other representations such as hexadecimal format. If
. is provided, this is transferred to major and minor and ‘0’ is used for
revision. If only an is provided, this is transferred to major and ‘0’ is used for minor
and revision. A leading character or a leading character and whitespace shall be ignored. For
a string in any other format the revision number shall not be considered to select the correct
FDI Package.
5.4 Information Model mapping
5.4.1 ProtocolType definition
This standard refers to IEC 61158 specified protocols as these are relevant to support the
device management related use cases supported through FDI specifications. The scope is
limited to data transport from the Information Model to the device.
For example, the device address management is based on services specified in the
IEC 61158 series. But since the address management service is encapsulated by the IEC
62769-7 specified SetAddress service the details of IEC 61158 specified services do not need
to be known.
The protocol type Profinet_IO shall be used to identify the PROFINET IO communication. The
type Profinet_IO is a sub type of the abstract type ProtocolType (IEC 62541-100). Table 6
specifies the attributes and the values of the Protocol type Profinet_IO.
Table 6 – Protocol type Profinet_IO
Attribute Value
BrowseName Profinet_IO
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Sub type of the ProtocolType defined in IEC 62541-100.

– 14 – IEC 62769-103-4:2015 © IEC 2015
5.4.2 DeviceType mapping
The properties mapping of the DeviceType node is defined in Table 7.
Table 7 – DeviceType Property mapping
Property PROFINET Mapping
SerialNumber SERIAL_NUMBER (see Table 8)
RevisionCounter REV_COUNTER (see Table 8)
Manufacturer VendorID (see Table 8, GSDML “Attributes of element DeviceIdentity”)
Model DeviceID (see Table 8, GSDML “Attributes of element DeviceIdentity”)
DeviceRevision Not supported
DeviceManual Not supported
SoftwareRevision SOFTWARE_REVISION (see Table 8)
HardwareRevision HARDWARE_REVISION (see Table 8)

5.4.3 FunctionalGroup identification definition
As defined in IEC 62541-100:2015, 5.3, each device representation in the FDI Server hosted
Information Model shall contain a protocol specific FunctionalGroup named Identification. The
Parameters of this FunctionalGroup are defined for PROFINET as follows:
Table 8 – PROFINET identification type definition
BrowseName DataType Mandatory/Optional
VendorD UInt16 Mandatory
DeviceID UInt16 Mandatory
ORDER_ID String Mandatory
SERIAL_NUMBER String Mandatory
HARDWARE_REVISION UInt16 Mandatory
SOFTWARE_REVISION String Mandatory
REV_COUNTER UInt16 Mandatory
PROFILE_ID UInt16 Mandatory
PROFILE_SPECIFIC_TYPE UInt16 Mandatory
IM_VERSION ByteString Mandatory
IM_SUPPORTED UInt16 Mandatory
The BaseDataVariable instances shall be created from VARIABLE declarations with identifiers
that correspond to the browse names listed in Table 8 except the attributes VendorID and
DeviceID. The related attribute values shall be taken from the GSD file (5.2.1). The element
names VendorID and DeviceID match with the attribute names defined in the GSDML
specification.
5.5 Topology elements
5.5.1 ConnectionPoint definition
In order to support different network topology engineering needs related to different protocol
layers used for PROFINET IO the ConnectionPoint type definitions follow the IEC 62769-7
given recommendations about how to handle address information for protocol layers
embedded in PROFINET IO.
IEC 62769-103-4:2015 © IEC 2015 – 15 –
The ConnectionPoint type ConnectionPoint_Profinet_IO shall be used to parameterize
PROFINET IO network access points. The ConnectionPoint type Profinet_IO is a sub type of
the abstract type ConnectionPointType (IEC 62769-5). Table 9 specifies the allowed values of
the ConnectionPoint attributes for the protocol type Profinet_IO.
Table 9 – ConnectionPoint type for Profinet_IO
Attribute Value
BrowseName Profinet_IO
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Sub type of the ConnectionPointType defined in IEC 62541-100.
HasProperty Variable MAC Octet[6] PropertyType Mandatory
HasProperty Variable IPv4 Octet[4] PropertyType Mandatory
HasProperty Variable DNSNAME String PropertyType Mandatory
HasProperty Variable VALID Boolean PropertyType Mandatory

The ConnectionPoint type Profinet_IO shall be described by an EDD element contained in a
Communication Device related FDI Package that can drive a PROFINET IO network. Actual
ConnectionPoint properties are declared by VARIABLE constructs grouped together in a
COLLECTION named ConnectionPoint.
Variable MAC is an array of 6 bytes holding the MAC address. The value is a unique identifier
assigned to network interfaces that support IEEE Std 802.3 specified communication. The
value can only be read from the device for example during execution of the scan service.
Variable IPv4 is an array of 4 bytes holding the IP-Address.
NOTE 1 Formatting of an IP-Address results typically in a character string that consists of four “.” separated, 1.3-
digit decimal numbers (example 128.12.1.15). The EDDL specification according to IEC 61804-3 and IEC 61804-4
does not support formatting instructions for the OCTECT type. But since semantics of the VARIABLE definitions
made in this part of IEC 62769 are defined it’s assumed that the system can render VARIABLE values accordingly.
...