IEC 62769-103-1:2023

IEC 62769-103-1 ®
Edition 3.0 2023-04
REDLINE VERSION
INTERNATIONAL
STANDARD
colour
inside ®
Field Device Integration (FDI) –
Part 103-1: Profiles – PROFIBUS

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

IEC Secretariat Tel.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
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 corrigendum or an amendment might have been published.

IEC publications search - webstore.iec.ch/advsearchform IEC Products & Services Portal - products.iec.ch
The advanced search enables to find IEC publications by a Discover our powerful search engine and read freely all the
variety of criteria (reference number, text, technical publications previews. With a subscription you will always have
committee, …). It also gives information on projects, replaced access to up to date content tailored to your needs.
and withdrawn publications.
Electropedia - www.electropedia.org
IEC Just Published - webstore.iec.ch/justpublished
The world's leading online dictionary on electrotechnology,
Stay up to date on all new IEC publications. Just Published
containing more than 22 300 terminological entries in English
details all new publications released. Available online and once
and French, with equivalent terms in 19 additional languages.
a month by email.
Also known as the International Electrotechnical Vocabulary

(IEV) online.
IEC Customer Service Centre - webstore.iec.ch/csc

If you wish to give us your feedback on this publication or need
further assistance, please contact the Customer Service
Centre: sales@iec.ch.
IEC 62769-103-1 ®
Edition 3.0 2023-04
REDLINE VERSION
INTERNATIONAL
STANDARD
colour
inside ®
Field Device Integration (FDI) –
Part 103-1: Profiles – PROFIBUS
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 25.040.40; 35.100.05 ISBN 978-2-8322-6857-5
– 2 – IEC 62769-103-1:2023 RLV © IEC 2023
CONTENTS
FOREWORD . 4
1 Scope . 6
2 Normative references . 6
3 Terms, definitions, abbreviated terms and conventions acronyms . 7
3.1 Terms and definitions . 7
3.2 Abbreviated terms and acronyms . 7
4 Conventions . 7
4.1 EDDL syntax . 7
4.2 XML syntax . 7
4.3 Capitalizations . 7
5 Profile for PROFIBUS . 8
5.1 General . 8
5.2 Catalog profile . 8
5.2.1 Protocol support file . 8
5.2.2 CommunicationProfile definition . 9
5.2.3 Profile device . 9
5.2.4 Protocol version information . 9
5.3 Associating a Package with a device . 10
5.3.1 Device type identification mapping . 10
5.3.2 Device type revision mapping . 11
5.4 Information Model mapping . 12
5.4.1 ProtocolType definition . 12
5.4.2 DeviceType mapping . 13
5.4.3 FunctionalGroup identification definition . 13
5.4.4 ConnectionPoint definition . 14
5.4.5 Communication Device definition . 16
5.4.6 Communication service provider definition . 17
5.4.7 Network definition . 18
5.5 Methods . 18 ®
5.5.1 Methods for FDI Communication Servers . 18
5.5.2 Methods for Gateways . 21
Annex A (normative) Topology Scan result schema . 28
A.1 General . 28
A.2 Target Namespace . 28
A.3 Network . 28
A.4 ProfibusNetworkT . 28
A.5 ProfibusConnectionPointT . 29
A.6 ProfibusIdentificationT . 29
A.7 ProfibusAddressT . 30
Annex B (normative) Transfer service parameters . 31
B.1 General . 31
B.2 Target Namespace . 31
B.3 sendData . 31
B.4 xsreceiveData receiveData . 31
B.5 xsTransferSendDataT TransferSendDataT . 31
B.6 TransferResultDataT . 32

B.7 OperationT . 32
Annex C (informative) Mapping to PA DIM . 33
C.1 General . 33
C.2 Mapping table . 33
Bibliography . 34

Figure 1 – Version mapping problem . 12
®
Table 1 – ProtocolSupportFile for FDI Device Packages . 8 ®
Table 2 – ProtocolSupportFile for FDI Communication Packages . 9
Table 3 – PROFIBUS CommunicationProfile definition schema . 9
Table 4 – Catalog values for profile devices . 9
Table 5 – Version mapping examples . 10
Table 6 – Device identification information mapping . 11
Table 7 – Protocol type Profibus_DP . 13
Table 8 – Protocol type Profibus_PA . 13
Table 9 – DeviceType property mapping . 13
Table 10 – PROFIBUS Device Types identification attributes . 14
Table 11 – ConnectionPoint type for Profibus_DP . 14
Table 12 – ConnectionPoint type for Profibus_PA . 15
Table 13 – Method Connect arguments . 19
Table 14 – Method Disconnect arguments . 19
Table 15 – Method Transfer arguments . 20
Table 16 – Method SetAddress arguments . 21
Table 17 – Connect service arguments . 22
Table 18 – Method Transfer arguments . 24
Table 19 – Method SetAddress arguments . 26
Table A.1 – Elements of ProfibusNetworkT . 28
Table A.2 – Attributes of ProfibusConnectionPointT . 29
Table A.3 – Elements of ProfibusConnectionPointT . 29
Table A.4 – Attributes of ProfibusIdentificationT . 30
Table B.1 – Attributes of TransferSendDataT . 32
Table B.2 – Attributes of TransferResultDataT . 32
Table C.1 – Mapping from PB standard parameters to PA DIM . 33

– 4 – IEC 62769-103-1:2023 RLV © IEC 2023
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________ ®
FIELD DEVICE INTEGRATION (FDI ) –

Part 103-1: Profiles – PROFIBUS

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.
This redline version of the official IEC Standard allows the user to identify the changes
made to the previous edition IEC 62769-103-1:2020. A vertical bar appears in the margin
wherever a change has been made. Additions are in green text, deletions are in
strikethrough red text.
IEC 62769-103-1 has been prepared by subcommittee 65E: Devices and integration in
enterprise systems, of IEC technical committee 65: Industrial-process measurement, control
and automation. It is an International Standard.
This third edition cancels and replaces the second edition published in 2020. This edition
constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous
edition:
a) added DEVICE_ID to the ProfibusIdentificationType and namespace to Annex A and
Annex B;
b) added mapping from PB standard parameters to PA DIM.
The text of this International Standard is based on the following documents:
Draft Report on voting
65E/862/CDV 65E/919/RVC
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this International Standard is English.
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/standardsdev/publications.
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.
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.
IMPORTANT – The "colour inside" logo on the cover page of this document 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-1:2023 RLV © IEC 2023 ®
FIELD DEVICE INTEGRATION (FDI ) –

Part 103-1: Profiles – PROFIBUS

1 Scope
®1
This part of IEC 62769 specifies an FDI profile of IEC 62769 for IEC 61784-1_CP 3/1
2 1
(PROFIBUS DP) and IEC 61784-1_CP3/2 (PROFIBUS PA) .
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 61784-1, Industrial communication networks – Profiles – Part 1: Fieldbus profiles
IEC 61804 (all parts), Devices and integration in enterprise systems – Function blocks (FB) for
process control and electronic device description language (EDDL)
IEC 62541-100:2015, OPC Unified Architecture – Part 100: Device Interface OPC UA for
Devices
3 ®
IEC 62769-2 , Field device integration (FDI ) – Part 2: FDI Client
4 ® ®
IEC 62769-4 , Field device integration (FDI ) – Part 4: FDI Packages
5 ®
IEC 62769-5 , Field device integration (FDI ) – Part 5: FDI Information Model
6 ®
IEC 62769-7 , Field Device Integration (FDI ) – Part 7: FDI Communication Devices
PI Order No.: 2.122:2008, Specification for PROFIBUS – Device Description and Device
Integration – Volume 1: GSD, V5.1, July 2008: GSD; available at
____________
FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given
for the convenience of users of this document 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.
PROFIBUS 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.
Under preparation. Stage at the time of publication: IEC/RFDIS 62769-2:2020.
Under preparation. Stage at the time of publication: IEC/RFDIS 62769-4:2020.
Under preparation. Stage at the time of publication: IEC/RFDIS 62769-5:2020.
Under preparation. Stage at the time of publication: IEC/RFDIS 62769-7:2020.

3 Terms, definitions, abbreviated terms and conventions acronyms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 61784-1, IEC 61804
(all parts), IEC 62541-100, IEC 62769-4, IEC 62769-5, IEC 62769-7 and PI Order No.:
2.122:2008 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 Abbreviated terms and acronyms
For the purposes of this document, the following abbreviated terms and acronyms apply:
EDD Electronic Device Description
EDDL Electronic Device Description Language (see IEC 61804 (all parts))
GSD General station description (see PI Order No.: 2.122:2008)
I&M Identification and maintenance function
UUID Universally unique identifier (see ISO/IEC 11578 IEC 62769-8)
XML Extensible markup language (see REC-xml-20081126)
4 Conventions
4.1 EDDL syntax ®
This document 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 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 a 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
• Profile Package.
– 8 – IEC 62769-103-1:2023 RLV © IEC 2023
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
• Profibus_PA_Network
5 Profile for PROFIBUS
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.
Annex B defines the XML schema for Direct Access Services. Annex C provides an overview of
mapping PROFIBUS standard parameters to PA DIM.
5.2 Catalog profile
5.2.1 Protocol support file ®
5.2.1.1 FDI Device Package
Protocol specific attachments are mentioned in the Package Catalog as defined in IEC 62769-5.
A communication feature list (GSD) file according to PI Order No.: 2.122:2008 is a mandatory ®
attachment for FDI Device Packages representing PROFIBUS DP and PROFIBUS PA devices. ®
Table 1 specifies the parameters of the ProtocolSupportFile in the FDI Device Package. ®
Table 1 – ProtocolSupportFile for FDI Device Packages
Parameter Description
Content Type text/plain
Root Namespace empty
Source Relationship http://fdi-cooperation.com/2010/relationship/attachment-protocol
Filename According to PI Order No.: 2.122:2008
®
5.2.1.2 FDI Communication Packages ®
A GSD file as specified in PI Order No.: 2.122:2008 is an optional attachment for FDI
Communication Packages representing PROFIBUS DP and PROFIBUS PA devices. Table 2 ®
specifies the parameters of ProtocolSupportFile for FDI Communication Packages.
®
Table 2 – ProtocolSupportFile for FDI Communication Packages
Parameter Description
Content Type: text/plain
Root Namespace: empty
Source Relationship: http://fdi-cooperation.com/2010/relationship/attachment-protocol
Filename: According to PI Order No.: 2.122:2008

5.2.2 CommunicationProfile definition
IEC 62769-4 defines a CommunicationProfileT string for the Catalog XML schema. Table 3
defines the PROFIBUS specific values for this string.
Table 3 – PROFIBUS CommunicationProfile definition schema
Profile Identifier Protocol
"profibus_dp" PROFIBUS DP/V0; PROFIBUS DP/V1; PROFIBUS DP/V2
“profibus_pa” PROFIBUS PA
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 4 focus on catalog content that is vendor independent.
Table 4 – Catalog values for profile devices
Element Attribute Content
PackageType — Profile
Manufacturer — Empty
DeviceModel — The 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 are 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 5 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.
– 10 – IEC 62769-103-1:2023 RLV © IEC 2023
Table 5 – Version mapping examples
Protocol / Version InterfaceT Version value
a
PROFIBUS DP/V0
0.0.0
a
PROFIBUS DP/V1
1.0.0
a
PROFIBUS DP/V2
2.0.0
b
PROFIBUS PA 3.02
3.2.0
b
PROFIBUS PA 4.0
4.0.0
a
The protocols PROFIBUS DP/V0, PROFIBUS DP/V1 and PROFIBUS DP/V2
contain a single number. This number is considered to be the major version. The
minor and built numbers are set to “0”.
b
The currently known PROFIBUS PA profile numbers are considered to provide
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 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.5.1.7) provides the scan
result through an XML document (the schema is defined in Clause A.6).
The Gateway implemented scan service (defined in 5.5.2.7) provides the scan result by means
of the Information Model that contains data structures created from EDD content as specified
in 5.5.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 catalog 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 device type
information presented in scan result (see the identification in Clause A.6) 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 scan result based on the Catalog Schema in IEC 62769-4 defining the XML (simple) element
types “DeviceModel” and “Manufacturer”. Both types are used in the (complex) element types
“Protocol” and “RegDeviceType”.
____________
The given table can be considered to be an example only since this document cannot foresee how future protocol
versions will be defined.
® ®
As a result of the FDI Package deployment the FDI Package information is then present in
the Information Model as the specified FunctionalGroup Identification containing Ident_Number
and Manufacturer_ID (see 5.4.3). The Ident_Number matches with the GSD specified
Ident_Number. Manufacturer_ID is specified through the I&M profile defined VendorID and
DeviceID (see 5.4.3).
If a device is used as a profile device, the Ident_Number returned in the scan result does not
fit to the Ident_Number within the GSD. In this case, DEVICE_ID can be used to identify the ®
FDI Package.
The mapping between different device identification data sources is described in Table 6. 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.
Table 6 – Device identification information mapping
® Information Model Communication Server Gateway provided
FDI Device Package
provided scan result scan result
Catalog specified type FunctionalGroup: Element (path): COLLECTION
Identification ConnectionPoint/Identification ConnectionPoint.
Manufacturer
Browse Name: Attribute: Identification.
Manufacturer_ID Manufacturer_ID Manufacturer_ID
Catalog specified type FunctionalGroup: Element (path): COLLECTION
Identification ConnectionPoint/Identification ConnectionPoint.
DeviceModel
Browse Name: Attribute: Identification.
Ident_Number Ident_Number Ident_Number

5.3.2 Device type revision mapping ®
IEC 62769-4 envisions a concept that allows to determine 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.
NOTE PROFIBUS related specifications, for example PI Order No.: 2.122:2008 (GSD) and PI
Order No.: 3.502:2009 (I&M) splits the device type revision into software and hardware related
information. The GSD specifies the attributes Hardware_Release and Software_Release. The
I&M specifies HARDWARE_REVISION and SOFTWARE_REVISION. Hardware_Release and
HARDWARE_REVISION will shall match always. Software_Release and
SOFTWARE_REVISION will shall match always.
The goal of 5.3.2 is to describe the translation rules between PROFIBUS related specifications,
describing their way of providing the version information, and the IEC 62769-4 specified way of
containing the version information that can be compared against the version read from the ®
device. The purpose is to determine the compatibility between an FDI Device Package and a
Device. Figure 1 depicts the problem.

– 12 – IEC 62769-103-1:2023 RLV © IEC 2023

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
PROFIBUS PA profile enables the reading of the values SOFTWARE_REVISION and
HARDWARE_REVISION. The access to these values shall be described in the EDD contained ®
in the FDI Device Package.
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 and Software_Release.
Hardware related modifications shall be captured in the HARDWARE_REVISION and
Hardware_Release. Hardware related modifications do not necessarily always require a
firmware update. Thus HARDWARE_REVISION and Hardware_Release 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. Hardware_Release and Software_Release shall be
changed accordingly.
The IEC 62769-4 specifies the Catalog schema and an element DeviceVersion which is used
in the element type declaration ListOfSupportedDeviceVersions. The value of the
DeviceVersion shall be compared to the device provided SOFTWARE_REVISION or the GSD ®
Device
provided Software_Release in order to determine the compatibility between an FDI
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 .. this is transferred to major, minor, and revision
(in the same order). references to simple integer number in the string such as ‘1’ or
‘12’, not to other representations such as hexadecimal format (e.g. 0x001A). 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
The concept to derive PROFIBUS DP and PROFIBUS PA specific Network Types applies to the
protocol type definition.
The protocol type Profibus_DP shall be used to identify the PROFIBUS DP communication. The
type Profibus_DP is a subtype of the abstract type ProtocolType in IEC 62541-100. Table 7
specifies the allowed values of the ProtocolType attributes for the protocol type Profibus_DP.
Table 7 – Protocol type Profibus_DP
Attribute Value
BrowseName Profibus_DP
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Subtype of the ProtocolType defined in IEC 62541-100.

The network type Profibus_PA_Network shall be used to build PROFIBUS PA network
topologies. The type Profibus_DP_Network is a subtype of the abstract type NetworkType in
IEC 62541-100. Table 8 specifies the allowed values of the ProtocolType attributes for the
protocol type Profibus_PA.
Table 8 – Protocol type Profibus_PA
Attribute Value
BrowseName Profibus_PA
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Subtype of the ProtocolType defined in IEC 62541-100.

5.4.2 DeviceType mapping
The DeviceType property mapping of the DeviceType node is defined in Table 9.
Table 9 – DeviceType property mapping
Property PROFIBUS Mapping
SerialNumber SERIAL_NUMBER (see Table 10)
RevisionCounter REV_COUNTER (see Table 10)
Manufacturer ®
String taken from FDI package catalog (ManufacturerName
from PackageT)
Model ®
String taken from FDI package catalog (Name of
DeviceTypeT, which is a localized name)
DeviceRevision Not supported
DeviceManual Not supported
SoftwareRevision SOFTWARE_REVISION (see Table 10)
HardwareRevision HARDWARE_REVISION (see Table 10)

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 PROFIBUS devices types as follows:

– 14 – IEC 62769-103-1:2023 RLV © IEC 2023
Table 10 – PROFIBUS Device Types identification attributes
BrowseName DataType Mandatory/Optional
Ident_Number UInt16 Mandatory
MANUFACTURER_ID UInt16 Mandatory
ORDER_ID String Optional
SERIAL_NUMBER String Optional
HARDWARE_REVISION UInt16 Optional
SOFTWARE_REVISION String Optional
REV_COUNTER UInt16 Optional
PROFILE_ID UInt16 Optional
PROFILE_SPECIFIC_TYPE UInt16 Optional
IM_VERSION ByteString Optional
IM_SUPPORTED UInt16 Optional
DEVICE_ID String Optional
The BaseDataVariable instances, except Ident_Number, shall be created from VARIABLE
declarations with identifiers that correspond to the browse names listed in Table 10. The
BaseDataVariable instances Ident_Number shall be created from the GSD file attribute
Ident_Number.Topology elements.
4.5 Topology elements
5.4.4 ConnectionPoint definition
In order to support different network topology engineering needs related to different physical
layers used by PROFIBUS DP and PROFIBUS PA, two different ConnectionPoint types shall
be defined.
The ConnectionPoint type Profibus_DP shall be used to parameterize PROFIBUS DP network
access points. The ConnectionPoint type Profibus_DP is a subtype of the abstract type
ConnectionPointType defined in IEC 62541-100. Table 11 specifies the allowed values of the
ConnectionPoint attributes for the protocol type Profibus_DP.
Table 11 – ConnectionPoint type for Profibus_DP
Attribute Value
BrowseName ConnectionPoint_Profibus_DP
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Subtype of the ConnectionPointType defined in IEC 62541-100.
HasProperty Variable Address Byte PropertyType Mandatory

The ConnectionPoint type Profibus_DP shall be described by an EDD element contained in a ®
Communication Device related FDI Package that can drive a PROFIBUS DP network. Actual
ConnectionPoint properties are declared by VARIABLE constructs grouped together in a
COLLECTION named ConnectionPoint.

COMPONENT ConnectionPoint_Profibus_DP
{
LABEL "PROFIBUS DP Connection Point";
CLASSIFICATION NETWORK_CONNECTION_POINT;
CAN_DELETE FALSE;
PROTOCOL PROFIBUS_DP;
CONNECTION_POINT ConnectionPoint;
}
VARIABLE Address
{
LABEL "Station address";
HELP "Address of the PROFIBUS slave";
TYPE UNSIGNED_INTEGER(1)
{
INITIAL_VALUE 126;
MIN_VALUE 0;
MAX_VALUE 126;
}
HANDLING READ & WRITE;
CLASS LOCAL;
}
COLLECTION ConnectionPoint
{
LABEL "PROFIBUS DP Connection Point data";
MEMBERS
{
CONNECTION_POINT_ADDRESS, Address;
}
}
The ConnectionPoint type Profibus_PA shall be used to parameterize PROFIBUS PA network
access points. The ConnectionPoint type Profibus_PA is a subtype of the abstract type
ConnectionPointType defined in IEC 62541-100. Table 12 specifies the allowed values of the
ConnectionPoint attributes for the protocol type Profibus_PA.
Table 12 – ConnectionPoint type for Profibus_PA
Attribute Value
BrowseName ConnectionPoint_Profibus_PA
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Subtype of the ConnectionPointType defined in IEC 62541-100.
HasProperty Variable Address Byte PropertyType Mandatory

The Property Address allowed values are 0 to 126.
The ConnectionPoint type Profibus_PA shall be described by an EDD element contained in a ®
Communication Device related FDI Package that can drive a PROFIBUS PA network. Actual
ConnectionPoint properties are declared by VARIABLE constructs grouped together in a
COLLECTION named ConnectionPoint.

– 16 – IEC 62769-103-1:2023 RLV © IEC 2023
COMPONENT ConnectionPoint_Profibus_PA
{
LABEL "PROFIBUS PA Connection Point";
CLASSIFICATION NETWORK_CONNECTION_POINT;
CAN_DELETE FALSE;
PROTOCOL PROFIBUS_PA;
}
VARIABLE Address
{
LABEL "Station address";
HELP "Address of the PROFIBUS slave";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER(1)
{
INITIAL_VALUE 126;
MIN_VALUE 0;
MAX_VALUE 126;
}
HANDLING READ & WRITE;
CLASS LOCAL;
}
COLLECTION ConnectionPoint
{
LABEL "PROFIBUS PA Connection Point data";
MEMBERS
{
CONNECTION_POINT_ADDRESS, Address;
}
}
5.4.5 Communication Device definition ®
According to IEC 62769-7, each FDI Communication Package shall contain an EDD element
describing the communication device. The following EDDL source code in is an example
describing a Communication Server.
COMPONENT Profibus_Communication_Server
{
LABEL "PROFIBUS communication server";
PRODUCT_URI "urn:PROFIBUS International:PROFIBUS Communication Server";
CAN_DELETE TRUE;
CLASSIFICATION NETWORK_COMPONENT;
COMPONENT_RELATIONS
{
Profibus_Communication_Device_Setup
}
}
COMPONENT_RELATION Profibus_Communication_Device_Setup
{
LABEL "Relation between Device and communication device";
RELATION_TYPE CHILD_COMPONENT;
COMPONENTS
{
Profibus_Communication_Device{AUTO_CREATE 1;}
}
MINIMUM_NUMBER 1;
MAXIMUM_NUMBER 4;
} ®
According to IEC 62769-7, each FDI Communication Package shall contain at least one EDD
element describing at least one communication device component. The following EDDL source
code in is an example for a PROFIBUS DP communication device:

COMPONENT Profibus_Communication_Device
{
LABEL "PROFIBUS communication device";
CAN_DELETE TRUE;
CLASSIFICATION NETWORK_COMPONENT;
COMPONENT_RELATIONS { Profibus_Service_Provider_Relation }
BYTE_ORDER BIG_ENDIAN;
}
COMPONENT_RELATION Profibus_Service_Provider_Relation
{
LABEL "Relation to communication service provider";
RELATION_TYPE CHILD_COMPONENT;
COMPONENTS
{
Profibus_Service_Provider{AUTO_CREATE 1;}
}
MINIMUM_NUMBER 1;
MAXIMUM_NUMBER 1;
}
In an actual communication device, the value “ConnectionPoint_Profibus_DP” needs to be
adapted according to the supported protocol and the related connection point definitions given
in 5.5. The attribute BYTE_ORDER value is to be set according to the protocol.
5.4.6 Communication service provider definition ®
According to IEC 62769-7, each FDI Communication Package shall contain at least one EDD
element describing at least one communication service provider component. The following
EDDL source code below is an example for a PROFINET IO communication service provider
component.
The component reference (ConnectionPoint_Profibus_DP) corresponds to the related
connection point definition
...