IEC 62769-109-1:2020

Field device integration (FDI) - Part 109-1: Profiles - HART® and WirelessHART®

IEC 62769-109-1:2020 specifies an FDI profile of IEC 62769 for IEC 61784 1_CP 9/1 (HART®) and IEC 61784 1_CP 9/2 (WirelessHART®). This second edition cancels and replaces the first edition published in 2015. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition:
a) support for generic protocol extension for faster adoption of other technologies;
b) support for Package Developers to build EDDs targeted for today’s EDD bases system under a single development tool.

Intégration des appareils de terrain (FDI) - Partie 109-1: Profils - HART® et WirelessHART®

IEC 62769-109-1 spécifie un profil FDI de l'IEC 62769 pour l'IEC 61784 1_CP 9/1 (HART®) et l'IEC 61784 1_CP 9/2 (WirelessHART®). Cette deuxième édition annule et remplace la première édition parue en 2015. Cette édition constitue une révision technique. Cette édition inclut les modifications techniques majeures suivantes par rapport à l'édition précédente:
a) prise en charge d'extensions de protocoles génériques, pour une adoption plus rapide d'autres technologies;
b) capacité offerte aux Développeurs de Paquetages d'élaborer des EDD ciblant les systèmes actuels de bases EDD, en exploitant un seul outil de développement.

General Information

• Status: Published
• Publication Date: 27-Apr-2020
• ICS: 25.040.40 - Industrial process measurement and control
• ICS: 35.100.05 - Multilayer applications
• Technical Committee: SC 65E - Devices and integration in enterprise systems
• Drafting Committee: WG 7 - TC 65/SC 65E/WG 7
• Current Stage: DELPUB - Deleted Publication
• Start Date: 18-Apr-2023
• Completion Date: 28-Jan-2022

Relations

• Revises: IEC 62769-109-1:2015 - Field Devices Integration (FDI) - Part 109-1: Profiles - HART® and WirelessHART®
• Effective Date: 05-Sep-2023
• Revised: IEC 62769-109-1:2023 - Field device integration (FDI)® - Part 109-1: Profiles - HART® and WirelessHART®
• Effective Date: 05-Sep-2023

Overview

IEC 62769-109-1:2020 is the IEC Field Device Integration (FDI) profile for HART® (IEC 61784‑1 CP 9/1) and WirelessHART® (IEC 61784‑1 CP 9/2). Edition 2.0 (2020) is a technical revision that cancels and replaces the 2015 edition. The standard defines how HART and WirelessHART devices are represented, discovered and managed within FDI packages and tools, enabling consistent device integration, configuration and diagnostics across control and asset-management systems.

Key Topics and Technical Requirements

• FDI profile for HART / WirelessHART: Standardizes the catalog, communication profile and device profile representations for CP 9/1 and CP 9/2 devices.
• Information model mapping: Defines ProtocolType, DeviceType and FunctionalGroup mappings so tools can interpret device functionality consistently.
• Topology elements: Specifies ConnectionPoint types (TP, IP, TDMA), Communication Device, Communication Service Provider and Network representations used for device discovery and addressing.
• Methods and services: Includes method definitions for Communication Servers and Gateways such as Connect, Disconnect, Transfer, GetPublishedData and SetAddress - enabling standardized runtime interactions.
• Annexes for implementers:
  • Topology scan schema (Annex A) for structured device/network discovery.
  • Transfer service parameters (Annex B) for data exchange semantics.
• Practical developer support: Adds support for a generic protocol extension to speed adoption of new technologies and enables Package Developers to create EDD-targeted packages under a unified toolchain.
• Edition and IP notes: The document is a redline Edition 2.0 (2020) and includes patent declarations for certain methods; implementers should review licensing statements in the standard.

Applications and Who Uses It

• Device manufacturers: Create FDI packages and EDDs that expose HART/WirelessHART device parameters and diagnostics to host systems.
• System integrators & control engineers: Integrate smart field devices into DCS/SCADA and asset-management systems with standardized discovery and configuration workflows.
• Software/tool vendors: Build FDI-compliant engineering tools, EDD authoring environments, communication servers and gateways that support HART/WirelessHART profiles.
• Plant owners & asset managers: Streamline device lifecycle management, commissioning and diagnostics across heterogeneous field networks.

Related Standards

• IEC 61784-1 (CP 9/1 and CP 9/2) - HART and WirelessHART communication profiles.
• IEC 62769 series (FDI) - other FDI parts covering package & integration framework.
• Refer to the IEC webstore for the latest editions and normative references.

Keywords: IEC 62769-109-1, FDI profile, HART, WirelessHART, field device integration, EDD, topology, communication profile, device integration.

Standards Content (Sample)

IEC 62769-109-1 ®
Edition 2.0 2020-04
REDLINE VERSION
INTERNATIONAL
STANDARD
colour
inside
Field device integration (FDI) –
Part 109-1: Profiles – HART® and WirelessHART®

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 Central Office Tel.: [phone]
3, rue de Varembé [e-mail]
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 Electropedia - www.electropedia.org
The advanced search enables to find IEC publications by a The world's leading online dictionary on electrotechnology,
variety of criteria (reference number, text, technical containing more than 22 000 terminological entries in English
committee,…). It also gives information on projects, replaced and French, with equivalent terms in 16 additional languages.
and withdrawn publications. Also known as the International Electrotechnical Vocabulary

(IEV) online.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Glossary - std.iec.ch/glossary
details all new publications released. Available online and 67 000 electrotechnical terminology entries in English and
once a month by email. French extracted from the Terms and Definitions clause of
IEC publications issued since 2002. Some entries have been
IEC Customer Service Centre - webstore.iec.ch/csc collected from earlier publications of IEC TC 37, 77, 86 and
If you wish to give us your feedback on this publication or CISPR.

need further assistance, please contact the Customer Service

Centre: [e-mail].
IEC 62769-109-1 ®
Edition 2.0 2020-04
REDLINE VERSION
INTERNATIONAL
STANDARD
colour
inside
Field device integration (FDI) –

Part 109-1: Profiles – HART® and WirelessHART®

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 25.040.40; 35.100.05 ISBN 978-2-8322-8291-5

– 2 – IEC 62769-109-1:2020 RLV © IEC 2020

CONTENTS
FOREWORD . 4

INTRODUCTION .

1 Scope . 7

2 Normative references . 7

3 Terms, definitions, abbreviated terms and acronyms conventions . 7

3.1 Terms and definitions . 7

3.2 Abbreviated terms and acronyms . 8
3.3 Conventions . 8
3.3.1 EDDL syntax. 8
3.3.2 XML syntax . 8
3.3.3 Capitalizations . 8
® ®
4 Profile for CP 9/1 (HART ) or CP 9/2 (WirelessHART ) . 9
4.1 General . 9
4.2 Catalog profile . 9
4.2.1 Protocol support file . 9
4.2.2 CommunicationProfile definition . 9
4.2.3 Profile device . 10
4.2.4 Protocol version information . 10
4.3 Associating a Package with a CP 9/1 device . 10
4.3.1 Device type identification mapping . 10
4.3.2 Device type revision mapping . 11
4.4 Information Model mapping . 11
4.4.1 ProtocolType definition . 11
4.4.2 DeviceType mapping . 11
4.4.3 FunctionalGroup Identification definition . 12
4.5 Topology elements . 13
4.5.1 ConnectionPoint definition . 13
4.5.2 Communication Device definition . 19
4.5.3 Communication service provider definition . 20
4.5.4 Network definition . 20
4.6 Methods . 21
4.6.1 Methods for FDI Communication Servers . 21

4.6.2 Methods for Gateways . 25
Annex A (normative) Topology scan schema . 33
A.1 General . 33
A.2 IdentificationType . 33
A.3 AddressTypeTP . 35
A.4 AddressTypeIP . 35
A.5 AddressTypeTDMA . 36
A.6 AddressType . 36
A.7 ConnectionPointType . 37
A.8 NetworkType . 38
A.9 Network . 38
Annex B (normative) Transfer service parameters . 39
B.1 General . 39
B.2 receiveData . 39

B.3 sendData . 39

B.4 TransferResultDataT . 39

B.5 TransferSendDataT . 40

Bibliography . 41

Table 1 – Device Information Files . 9

Table 2 – CommunicationProfile definition . 9

Table 3 – Catalog values for profile devices . 10

Table 4 – Protocol Version Information . 10

Table 5 – Device type catalog mapping . 11
Table 6 – ProtocolType HART definition . 11
Table 7 – Inherited DeviceType Property mapping . 12
Table 8 – Identification parameters . 12
Table 9 – ConnectionPointType HART_TP definition . 14
Table 10 – ConnectionPointType HART_IP Definition . 16
Table 11 – ConnectionPointType HART_TDMA Definition . 18
Table 12 – Method Connect arguments . 22
Table 13 – Method Disconnect arguments . 22
Table 14 – Method Transfer arguments . 23
Table 15 – Method GetPublishedData arguments. 24
Table 16 – Method SetAddress arguments . 25
Table 17 – Method Connect arguments . 26
Table 18 – Method Disconnect arguments . 27
Table 19 – Method Transfer arguments . 28
Table 20 – Method GetPublishedData arguments. 29
Table 21 – Method SetAddress arguments . 30
Table A.1 – Attributes of IdentificationT . 34
Table A.2 – Elements of AddressTypeTP . 35
Table A.3 – Elements of AddressTypeIP . 36
Table A.4 – Elements of AddressTypeTDMA . 36
Table A.5 – Elements of AddressT . 37

Table A.6 – Elements of ConnectionPointT . 37
Table A.7 – Elements of NetworkT . 38
Table B.1 – Attributes of TransferResultDataT . 39
Table B.2 – Attributes of TransferSendDataT . 40

– 4 – IEC 62769-109-1:2020 RLV © IEC 2020

INTERNATIONAL ELECTROTECHNICAL COMMISSION

____________
FIELD DEVICE INTEGRATION (FDI) –

Part 109-1: Profiles – HART® and WirelessHART®

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. A vertical bar appears in the margin wherever a change
has been made. Additions are in green text, deletions are in strikethrough red text.

International Standard IEC 62769-109-1 has been prepared by subcommittee 65E: Devices

and integration in enterprise systems, of IEC technical committee 65: Industrial-process

measurement, control and automation.

This second edition cancels and replaces the first edition published in 2015. This edition

constitutes a technical revision.

This edition includes the following significant technical changes with respect to the previous

edition:
a) support for generic protocol extension for faster adoption of other technologies;

b) support for Package Developers to build EDDs targeted for today’s EDD bases system
under a single development tool.
The text of this International Standard is based on the following documents:
CDV Report on voting
65E/624/CDV 65E/687A/RVC
Full information on the voting for the approval of this International Standard 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.
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.
– 6 – IEC 62769-109-1:2020 RLV © IEC 2020

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.

FIELD DEVICE INTEGRATION (FDI) –

Part 109-1: Profiles – HART® and WirelessHART®

1 Scope
This part of IEC 62769 specifies an FDI profile of IEC 62769 for IEC 61784-1_CP 9/1
® ® 1
(HART ) and IEC 61784-1_CP 9/2 (WirelessHART ) .
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 62541-100:2015, OPC Unified Architecture Specification – Part 100: Device Interface
IEC 62769-4:2015– , Field device integration (FDI) – Part 4: FDI Packages
NOTE IEC 62769-4 is technically identical to FDI-2024.
IEC 62769-5, Field device integration (FDI) – Part 5: FDI Information Model
NOTE IEC 62769-5 is technically identical to FDI-2025.
IEC 62769-7, Field device integration (FDI) – Part 7: FDI Communication Devices
NOTE IEC 62769-7 is technically identical to FDI-2027.
3 Terms, definitions, abbreviated terms and acronyms conventions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62541-100,
IEC 62769-4, IEC 62769-5 and IEC 62769-7 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
______________
HART® and wirelessHART® are the trade names of the non-profit consortium HART Communication Foundation,
Austin,Texas, USA the registered trademark of FieldComm Group. 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 the product named. Compliance does not require use of the trade names. Use of the trade names requires
permission of the trade name holder. Equivalent products may be used if they can be shown to lead to the same
results.
Under preparation. Stage at the time of publication: IEC/RFDIS 62769-4:2020.

– 8 – IEC 62769-109-1:2020 RLV © IEC 2020

3.2 Abbreviated terms and acronyms

For the purposes of this document, the following abbreviations apply:

CP Communication profile (see IEC 61784-1 or IEC 61784-2)

CPF Communication profile family (see IEC 61784-1 or IEC 61784-2)

EDD Electronic device description (see IEC 61804)

EDDL Electronic device description language (see IEC 61804)

FDI Field device integration
FSK Frequency-Shift-Keying
HCF HART Communication Foundation
ID Identification
IM Information Model
IP Internet protocol
PDU Protocol data unit
PSK Phase-Shift-Keying
TCP Transmission Control Protocol (see IETF RFC 793)
UDP User Datagram Protocol (see IETF RFC 768)
XML Extended Extensible markup language
3.3 Conventions
3.3.1 EDDL syntax
This document specifies content for the EDD component that is part of FDI Communication
Packages. EDDL syntax uses the font Courier New. EDDL syntax is used for method
signature, variable, data structure and component declarations.
3.3.2 XML syntax
XML syntax examples use font Courier New. The XML syntax is used to describe XML
document schema.
EXAMPLE
3.3.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:
• FDI Communication Servers or
• Profile 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 like:

• PROFILE_ID or
• HART_Network.
® ®
4 Profile for CP 9/1 (HART ) or CP 9/2 (WirelessHART )

4.1 General
This profile document to the FDI specification in IEC 62769 specifies selects the protocol
specifics needed for FDI Packages describing FDI Communication Servers, gateways and
devices.
4.2 Catalog profile
4.2.1 Protocol support file
No additional file is required for CP 9/1 or CP 9/2 FDI Device Packages.
Device information files provide metadata for the dynamic runtime data that is supplied by the
device. This metadata is a subset of information that is contained in the EDD. The device
information files may be extracted from the package by light-weight gateway or server
implementations to exchange runtime device information with minimal implementation
overhead. Device information files do not replace the need for the EDD part because device
information files only contain a subset of the information from the EDD, and do not provide
any user-interface elements.
The formats of the Device Information Files are described in Table 1.
Table 1 – Device Information Files
Part Content
Content Type Not specified here
Root Namespace Not specified here
Source http://fdi-cooperation.com/2010/relationships/attachment-protocol
Relationship
Filename Not specified here
The Device Information Files are specified in FCG AG21073.
4.2.2 CommunicationProfile definition
IEC 62769-4 defines a CommunicationProfileT enumeration string type for the Catalog XML
schema. Table 2 defines the CP 9/1 specific values for this enumeration.
Table 2 – CommunicationProfile definition
CommunicationProfile Description
hart_fsk CP 9/1 device type that supports an FSK physical layer (Frequency-Shift-Keying on
a pair of wires)
hart_psk CP 9/1 device type that supports a PSK physical layer (Phase-Shift-Keying on a pair
of wires). Devices supporting PSK are required to also inherently support FSK, and
therefore PSK will always be used only in combination with at least FSK.

– 10 – IEC 62769-109-1:2020 RLV © IEC 2020

CommunicationProfile Description

hart_wirelesshart CP 9/2 device type that supports a wireless physical layer (communication between
device and gateway).
hart_ip CP 9/1 device type that supports Internet Protocol (these devices support both TCP

and UDP).
hart_rs485 CP 9/1 device type that supports EIA-485 digital communication.

hart_ir CP 9/1 device type that supports an Infrared physical layer (designed to be
transparent to FSK masters – included only as information to indicate that the device

supports IR connection).
NOTE It is possible for a single CP 9/1 device to support more than one CP.

4.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
DeviceModel — Empty
Manufacturer — Empty
4.2.4 Protocol version information
IEC 62769-4 defines an element type named InterfaceT for the Catalog XML Schema.
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 element type VersionT.
Subclause 4.2.4 describes how to apply the currently known protocol versions for CP 9/1 or
CP 9/2 entries in the device catalog. The general rule is to use the Universal Revision of the
protocol for the major version part of VersionT, and the value "0" for the minor version and
build parts. Table 4 shows the Protocol Version Information.
Table 4 – Protocol Version Information
Protocol Version InterfaceT Version value

HART Universal Revision 5 5.0.0
HART Universal Revision 6 6.0.0
HART Universal Revision 7 7.0.0
The Protocol Version defined in a package is provided for informational purposes only and shall not be used to
determine the compatibility or applicability of a package to a device.

4.3 Associating a Package with a CP 9/1 device
4.3.1 Device type identification mapping
CP 9/1 device types are uniquely identified by parameters Manufacturer, Model and
DeviceRevision. These parameters are used to associate a given device instance to an FDI
Device Package. These parameters are mapped to the FDI Device Package Catalog
according to Table 5.
Table 5 – Device type catalog mapping

Catalog element CP mapping (see 5.4.2)

Manufacturer element of InterfaceT (IEC 62769-4:2015, Manufacturer

Clause E.11)
String format “0xdddd” where dddd is the

Manufacturer number in hexadecimal format.

DeviceModel element of InterfaceT (IEC 62769-4:2015, Model

Clause E.11)
String format “0xdddd” where dddd is the
Model number in hexadecimal format.

DeviceRevision element DeviceRevision

ListOfSupportedDeviceRevisionsT (IEC 62769-4:2015, String format “x.0.0” where x is the
DeviceRevision in decimal format (no leading
Clause E.21)
zeros).
Catalog element CP mapping (SeeTable A.)
Manufacturer element of InterfaceT Manufacturer
(IEC 62769-4:–, Clause E.10)
String format "0xdddd" where dddd is the
MANUFACTURER_ID in hexadecimal format.
DeviceModel element of InterfaceT Model
(IEC 62769-4:–, Clause E.10)
String format "0xdddd" where dddd is the
DEVICE_TYPE in hexadecimal format.
DeviceRevision element DeviceRevision
ListOfSupportedDeviceRevisionsT String format "x.0.0" where x is the
DEVICE_REVISION in decimal format (no
(IEC 62769-4:–, Clause E.20)
leading zeros).
4.3.2 Device type revision mapping
Each device type is identified as per 4.3.1. If a package with matching DeviceRevision is not
available, any CP 9/1 FDI package for a corresponding manufacturer and model shall always
be compatible with a field device as long as the device revision of the field device is equal to
or greater than the device revision specified in the FDI package.
4.4 Information Model mapping
4.4.1 ProtocolType definition
Table 6 defines the ProtocolType used to identify CP 9/1 network communications.

Table 6 – ProtocolType HART definition
Attribute Value
BrowseName HART
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Inherits the properties of ProtocolType defined in IEC 62541-100.

4.4.2 DeviceType mapping
Each device type inherits the properties of DeviceType. The mapping of the inherited
properties from DeviceType is defined in Table 7.

– 12 – IEC 62769-109-1:2020 RLV © IEC 2020

Table 7 – Inherited DeviceType Property mapping

Property Foundation mapping
SerialNumber 3-byte unique ID of a device, returned in bytes 9 to 11 of Command 0 or

Command 11 or Command 21
RevisionCounter 2-byte configuration change counter, returned in bytes 14 and 15 of

Command 0 or Command 11 or Command 21.

-1 (not defined) for HART revision 5 devices

Manufacturer For HART revision 7 or higher devices:

2-byte manufacturer code of a device, returned in bytes 17 and 18 of
Command 0 or Command 11 or Command 21.

For HART revision 6 or lower devices:
Most significant byte shall be fixed to 0, and the least significant byte is
returned in byte 1 of Command 0 or Command 11 or Command 21
2-byte extended device type of a device, returned in bytes 1 and 2 of
Model
Command 0 or Command 11 or Command 21
DeviceManual a
Entry text string (not supported)
DeviceRevision 1-byte device revision level of a device, returned in byte 5 of Command 0 or
Command 11 or Command 21
SoftwareRevision 1-byte software revision level of a device, returned in byte 6 of Command 0 or
Command 11 or Command 21
HardwareRevision 1-byte hardware revision level of a device, returned in byte 7 (only 5 most
significant bits) of Command 0 or Command 11 or Command 21
a
Device manuals are exposed as attachments of the FDI Device Package.

Property Foundation mapping
SerialNumber Unique ID of a device, mapped to SERIAL_NUMBER of IdentificationT.
RevisionCounter Configuration change counter, mapped to REV_COUNTER of
IdentificationT
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)
a
DeviceManual
Entry text string (not supported)
DeviceRevision Device revision level of a device, mapped to DEVICE_REVISION of
IdentificationT
SoftwareRevision Software revision level of a device, mapped to SOFTWARE_REVISION of
IdentificationT
HardwareRevision Hardware revision level of a device, mapped to HARDWARE_REVISION of
IdentificationT
a
Device manuals are exposed as attachments of the FDI Device Package.

4.4.3 FunctionalGroup Identification definition
As defined in IEC 62541-100, each device representation in the FDI Server hosted
Information Model shall contain a protocol specific FunctionalGroup called Identification. This
FunctionalGroup organizes variables found in the device type instance. The FunctionalGroup
Identification for CP 9/1 is defined in Table 8.
Table 8 – Identification parameters
BrowseName DataType Optional/Mandatory
MANUFACTURER_ID UInt16 Mandatory

DEVICE_TYPE UInt16 Mandatory
DEVICE_REVISION UInt8 Mandatory

UNIVERSAL_REVISION UInt8 Optional

SERIAL_NUMBER UInt24 Optional
HARDWARE_REVISION UInt8 Optional

SOFTWARE_REVISION UInt8 Optional

REVISION_COUNTER UInt16 Optional

4.5 Topology elements
4.5.1 ConnectionPoint definition
4.5.1.1 General
CP 9/1 devices can support up to five different ConnectionPoint types that are used for
network communications.
4.5.1.2 HART_TP5, HART_TP6, HART_TP7
The ConnectionPoint types HART_TP5, HART_TP6, and HART_TP7 shall be used to identify
CP 9/1 token passing network communication and are defined in Table 9. HART_TP5,
HART_TP6, and HART_TP7 all contain the same properties, but each provides different
qualification information for some of the properties (described below). The Protocol Version
(UNIVERSAL_REVISION) described in 4.2.4 can be used as an aid to determine which of the
three token passing Connection Point types is the most appropriate. CP 9/1 token passing
communications can be used on a variety of physical layers. FSK, PSK, RS485, and Infrared
physical layer connections shall all use the HART_TP connection type. The ConnectionPoint
types HART_TP5, HART_TP6, and HART_TP7 are subtypes of abstract type
ConnectionPointType defined in IEC 62769-5.
The DevAddr property shall be the long address (5 bytes) for the device and is the only
parameter necessary to communicate with the field device.
The DevMfg property shall be the 2-byte Manufacturer ID and can be used to help automate
the process of assigning live devices in the scan list to offline placeholders.
The DevType property shall be the 2-byte extended device type and can be used to help
automate the process of assigning live devices in the scan list to offline placeholders.

The DevRev property shall be the device revision and can be used to help automate the
process of assigning live devices in the scan list to offline placeholders. ®
protocol version 6 or 7 devices. The
The DevTag property shall be the long tag for HART
DevTag property shall be the tag for protocol version 5 devices. The DevTag property can be
used to help automate the process of assigning live devices in the scan list to offline
placeholders. HART_TP5 Connection Points shall limit the DevTag to 8 characters in length.
HART_TP6 and HART_TP7 Connection Points shall limit the DevTag to 32 characters in
length.
The DevPollAddr property shall be the poll address and can be used to identify which device
is located at a specific poll address. HART_TP5 Connection Points shall be limited to values
between 0 and 15 for the DevPollAddr property. HART_TP6 Connection Points shall be
limited to values between 0 and 31 for the DevPollAddr property. HART_TP7 Connection
Points shall be limited to values between 0 and 63 for the DevPollAddr property.

– 14 – IEC 62769-109-1:2020 RLV © IEC 2020

For forward compatibility, a lower revision HART_TP Connection Point is compatible and can

be used for a higher universal revision device connection. For example, if a future HART

universal revision 8 device is encountered, and no HART_TP8 is available in the FDI server,

HART_TP7 will be compatible and shall be used to connect to the device. If the Protocol

Version (i.e. the Universal Revision) is unknown for any reason, the HART_TP5 Connection

Point can be used, and will be forward compatible to later universal revisions.

Table 9 – ConnectionPointType HART_TP definition

Attribute Value
BrowseName ConnnectionPoint_HART_TP5 or ConnnectionPoint_HART_TP6 or

ConnnectionPoint_HART_TP7
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Inherits the properties of ConnectionPointType defined in IEC 62769-5
HasProperty Variable DevAddr UInt40 PropertyType Mandatory
HasProperty Variable DevMfg UInt16 PropertyType Optional
HasProperty Variable DevType UInt16 PropertyType Optional
HasProperty Variable DevRev UInt16 PropertyType Optional
HasProperty Variable DevTag String PropertyType Optional
HasProperty Variable DevPollAddr UInt8 PropertyType Optional

The ConnectionPoint type HART_TP5, HART_TP6, and HART_TP7 shall be described by an
EDD element contained in a Communication Device related FDI Package that can drive a
CP 9/1 network. Actual ConnectionPoint properties are declared by VARIABLE constructs
grouped together in a COLLECTION named ConnectionPoint_HART_TP5,
ConnectionPoint_HART_TP6, or ConnectionPoint_HART_TP7. The following EDDL source
code is an example describing a TP5 Connection Point.
COMPONENT ConnectionPoint_HART_TP5
{
LABEL "HART TP Connection Point";
CLASSIFICATION NETWORK_CONNECTION_POINT;
CAN_DELETE FALSE;
PROTOCOL HART;
CONNECTION_POINT ConnectionPoint_TP5;
}
VARIABLE DevAddr
{
LABEL "Address";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER(5);
HANDLING READ & WRITE;
}
VARIABLE DevMfg
{
LABEL "Manufacturer";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER(2);
HANDLING READ & WRITE;
}
VARIABLE DevType
{
LABEL "Device Type";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER(2);
HANDLING READ & WRITE;
}
VARIABLE DevRev
{
LABEL "Device Revision";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER;
HANDLING READ & WRITE;
}
VARIABLE DevTag
{
LABEL "Tag";
CLASS DEVICE;
TYPE ASCII(32);
HANDLING READ & WRITE;
}
VARIABLE DevPollAddr
{
LABEL "Poll Address";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER
{
MAX_VALUE 15; //Define appropriate max value for various revisions
}
HANDLING READ & WRITE;
}
COLLECTION ConnectionPoint_TP5
{
LABEL "Connection Point";
MEMBERS
{
ADDRESS,  DevAddr,   "Device Address";
MFG,    DevMfg,   "Manufacturer";
DEV_TYPE, DevType,   "Device Type";
DEV_REV,  DevRev,   "Device Revision";
TAG,    DevTag,   "Device Tag";

POLL_ADDR, DevPollAddr, "Poll Address";
}
}
4.5.1.3 HART_IP
The ConnectionPoint type HART_IP shall be used to identify CP 9/1 IP network
communication and is defined in Table 10. HART_IP communications can be used on a
variety of physical layers. Ethernet connections shall all use the HART_IP connection type.
Additional physical layers developed in the future may also use the HART_IP connection type.
The ConnectionPoint type HART_IP is a subtype of abstract type ConnectionPointType
defined in IEC 62769-5.
The IPAddress property shall indicate the IP Address (up to 16 bytes) used for the
connection.
– 16 – IEC 62769-109-1:2020 RLV © IEC 2020

The IPVersion property shall indicate the version of IP used for the connection (either 4 or 6).

The IPPort property shall be the IP port number for the connection. The default port number

used for HART IP is 5 094.
The DevAddr property shall be the long address (5 bytes) for the device.

The DevMfg property shall be the 2-byte Manufacturer ID and can be used to help automate

the process of assigning live devices in the scan list to offline placeholders.

The DevType property shall be the 2-byte extended device type and can be used to help

automate the process of assigning live devices in the scan list to offline placeholders.
The DevRev property shall be the device revision and can be used to help automate the
process of assigning live devices in the scan list to offline placeholders.
The DevTag property shall be the long tag (with maximum 32 characters) and can be used to
help automate the process of assigning live devices in the scan list to offline placeholders.
Table 10 – ConnectionPointType HART_IP Definition
Attribute Value
BrowseName ConnnectionPoint_HART_IP
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Inherits the properties of ConnectionPointType defined in IEC 62769-5
HasProperty Variable IPAddress ByteString PropertyType Mandatory
HasProperty Variable IPVersion UInt8 PropertyType Mandatory
HasProperty Variable IPPort UInt16 PropertyType Mandatory
HasProperty Variable DevAddr UInt40 PropertyType Mandatory
HasProperty Variable DevMfg UInt16 PropertyType Optional
HasProperty Variable DevType UInt16 PropertyType Optional
HasProperty Variable DevRev UInt16 PropertyType Optional
HasProperty Variable DevTag String PropertyType Optional

The ConnectionPoint type HART_IP shall be described by an EDD element contained in a

Communication Device related FDI Package that can drive a CP 9/1 network. Actual
ConnectionPoint properties are declared by VARIABLE constructs grouped together in a
COLLECTION named ConnectionPoint_HART_IP. The following EDDL source code is an
example describing an IP Connection Point.
COMPONENT ConnectionPoint_HART_IP
{
LABEL "HART IP Connection Point";
CLASSIFICATION NETWORK_CONNECTION_POINT;
CAN_DELETE FALSE;
PROTOCOL HART;
CONNECTION_POINT ConnectionPoint_IP;
}
ARRAY IPAddress
{
LABEL "IP Address";
CLASS DEVICE;
TYPE OCTET(16);
HANDLING READ & WRITE;
}
VARIABLE IPVersion
{
LABEL "IP Version";
CLASS DEVICE;
TYPE ENUMERATED
{
{ 4, "IPv4" },
{ 6, "IPv6" }
}
HANDLING READ & WRITE;
}
VARIABLE IPPort
{
LABEL "IP Port";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER (2);
DEFAULT_VALUE 5 094;
HANDLING READ & WRITE;
}
COLLECTION ConnectionPoint_IP
{
LABEL "Connection Point";
MEMBERS
{
IPADDRESS, IPAddress, "IP Address";
IPVERSION, IPVersion, "IP Version";
IPPORT,  IPPort,  "IP Port";
ADDRESS,  DevAddr,  "Device Address";
MFG,    DevMfg,  "Manufacturer";
DEV_TYPE, DevType
...

IEC 62769-109-1 ®
Edition 2.0 2020-04
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Field device integration (FDI) –
Part 109-1: Profiles – HART® and WirelessHART®

Intégration des appareils de terrain (FDI) –
Partie 109-1: Profils – HART® et WirelessHART®

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

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

IEC Central Office Tel.: [phone]
3, rue de Varembé [e-mail]
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 Electropedia - www.electropedia.org
The advanced search enables to find IEC publications by a The world's leading online dictionary on electrotechnology,
variety of criteria (reference number, text, technical containing more than 22 000 terminological entries in English
committee,…). It also gives information on projects, replaced and French, with equivalent terms in 16 additional languages.
and withdrawn publications. Also known as the International Electrotechnical Vocabulary

(IEV) online.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Glossary - std.iec.ch/glossary
details all new publications released. Available online and 67 000 electrotechnical terminology entries in English and
once a month by email. French extracted from the Terms and Definitions clause of
IEC publications issued since 2002. Some entries have been
IEC Customer Service Centre - webstore.iec.ch/csc collected from earlier publications of IEC TC 37, 77, 86 and
If you wish to give us your feedback on this publication or CISPR.

need further assistance, please contact the Customer Service

Centre: [e-mail].
A propos de l'IEC
La Commission Electrotechnique Internationale (IEC) est la première organisation mondiale qui élabore et publie des
Normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.

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

Recherche de publications IEC - Electropedia - www.electropedia.org
webstore.iec.ch/advsearchform Le premier dictionnaire d'électrotechnologie en ligne au
La recherche avancée permet de trouver des publications IEC monde, avec plus de 22 000 articles terminologiques en
en utilisant différents critères (numéro de référence, texte, anglais et en français, ainsi que les termes équivalents dans
comité d’études,…). Elle donne aussi des informations sur les 16 langues additionnelles. Egalement appelé Vocabulaire
projets et les publications remplacées ou retirées. Electrotechnique International (IEV) en ligne.

IEC Just Published - webstore.iec.ch/justpublished Glossaire IEC - std.iec.ch/glossary
Restez informé sur les nouvelles publications IEC. Just 67 000 entrées terminologiques électrotechniques, en anglais
Published détaille les nouvelles publications parues. et en français, extraites des articles Termes et Définitions des
Disponible en ligne et une fois par mois par email. publications IEC parues depuis 2002. Plus certaines entrées
antérieures extraites des publications des CE 37, 77, 86 et
Service Clients - webstore.iec.ch/csc CISPR de l'IEC.

Si vous désirez nous donner des commentaires sur cette
publication ou si vous avez des questions contactez-nous:
[e-mail].
IEC 62769-109-1 ®
Edition 2.0 2020-04
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Field device integration (FDI) –

Part 109-1: Profiles – HART® and WirelessHART®

Intégration des appareils de terrain (FDI) –

Partie 109-1: Profils – HART® et WirelessHART®

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040.40; 35.100.05 ISBN 978-2-8322-8140-6

– 2 – IEC 62769-109-1:2020 © IEC 2020
CONTENTS
FOREWORD . 4
1 Scope . 6
2 Normative references . 6
3 Terms, definitions, abbreviated terms and conventions . 6
3.1 Terms and definitions . 6
3.2 Abbreviated terms and acronyms . 6
3.3 Conventions . 7
3.3.1 EDDL syntax. 7
3.3.2 XML syntax . 7
3.3.3 Capitalizations . 7
® ®
4 Profile for CP 9/1 (HART ) or CP 9/2 (WirelessHART ) . 8
4.1 General . 8
4.2 Catalog profile . 8
4.2.1 Protocol support file . 8
4.2.2 CommunicationProfile definition . 8
4.2.3 Profile device . 9
4.2.4 Protocol version information . 9
4.3 Associating a Package with a CP 9/1 device . 9
4.3.1 Device type identification mapping . 9
4.3.2 Device type revision mapping . 10
4.4 Information Model mapping . 10
4.4.1 ProtocolType definition . 10
4.4.2 DeviceType mapping . 10
4.4.3 FunctionalGroup Identification definition . 11
4.5 Topology elements . 11
4.5.1 ConnectionPoint definition . 11
4.5.2 Communication Device definition . 17
4.5.3 Communication service provider definition . 18
4.5.4 Network definition . 18
4.6 Methods . 19
4.6.1 Methods for FDI Communication Servers . 19
4.6.2 Methods for Gateways . 23
Annex A (normative) Topology scan schema . 31
A.1 General . 31
A.2 IdentificationType . 31
A.3 AddressTypeTP . 33
A.4 AddressTypeIP . 33
A.5 AddressTypeTDMA . 34
A.6 AddressType . 34
A.7 ConnectionPointType . 35
A.8 NetworkType . 36
A.9 Network . 36
Annex B (normative) Transfer service parameters . 37
B.1 General . 37
B.2 receiveData . 37
B.3 sendData . 37

B.4 TransferResultDataT . 37
B.5 TransferSendDataT . 38
Bibliography . 39

Table 1 – Device Information Files . 8
Table 2 – CommunicationProfile definition . 8
Table 3 – Catalog values for profile devices . 9
Table 4 – Protocol Version Information . 9
Table 5 – Device type catalog mapping . 9
Table 6 – ProtocolType HART definition . 10
Table 7 – Inherited DeviceType Property mapping . 10
Table 8 – Identification parameters . 11
Table 9 – ConnectionPointType HART_TP definition . 12
Table 10 – ConnectionPointType HART_IP Definition . 14
Table 11 – ConnectionPointType HART_TDMA Definition . 16
Table 12 – Method Connect arguments . 20
Table 13 – Method Disconnect arguments . 20
Table 14 – Method Transfer arguments . 21
Table 15 – Method GetPublishedData arguments. 22
Table 16 – Method SetAddress arguments . 23
Table 17 – Method Connect arguments . 24
Table 18 – Method Disconnect arguments . 25
Table 19 – Method Transfer arguments . 26
Table 20 – Method GetPublishedData arguments. 27
Table 21 – Method SetAddress arguments . 28
Table A.1 – Attributes of IdentificationT . 32
Table A.2 – Elements of AddressTypeTP . 33
Table A.3 – Elements of AddressTypeIP . 34
Table A.4 – Elements of AddressTypeTDMA . 34
Table A.5 – Elements of AddressT . 35
Table A.6 – Elements of ConnectionPointT . 35
Table A.7 – Elements of NetworkT . 36
Table B.1 – Attributes of TransferResultDataT . 37
Table B.2 – Attributes of TransferSendDataT . 38

– 4 – IEC 62769-109-1:2020 © IEC 2020
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
FIELD DEVICE INTEGRATION (FDI) –

Part 109-1: Profiles – HART® and WirelessHART®

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.
International Standard IEC 62769-109-1 has been prepared by subcommittee 65E: Devices
and integration in enterprise systems, of IEC technical committee 65: Industrial-process
measurement, control and automation.
This second edition cancels and replaces the first edition published in 2015. This edition
constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous
edition:
a) support for generic protocol extension for faster adoption of other technologies;
b) support for Package Developers to build EDDs targeted for today’s EDD bases system
under a single development tool.

The text of this International Standard is based on the following documents:
CDV Report on voting
65E/624/CDV 65E/687A/RVC
Full information on the voting for the approval of this International Standard 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.
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.
– 6 – IEC 62769-109-1:2020 © IEC 2020
FIELD DEVICE INTEGRATION (FDI) –

Part 109-1: Profiles – HART® and WirelessHART®

1 Scope
This part of IEC 62769 specifies an FDI profile of IEC 62769 for IEC 61784-1_CP 9/1
® ® 1
(HART ) and IEC 61784-1_CP 9/2 (WirelessHART ) .
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 62541-100:2015, OPC Unified Architecture Specification – Part 100: Device Interface
IEC 62769-4:– , Field device integration (FDI) – Part 4: FDI Packages
IEC 62769-5, Field device integration (FDI) – Part 5: FDI Information Model
IEC 62769-7, Field device integration (FDI) – Part 7: FDI Communication Devices
3 Terms, definitions, abbreviated terms and conventions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62541-100,
IEC 62769-4, IEC 62769-5 and IEC 62769-7 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 abbreviations apply:
CP Communication profile (see IEC 61784-1 or IEC 61784-2)
CPF Communication profile family (see IEC 61784-1 or IEC 61784-2)
EDD Electronic device description (see IEC 61804)
EDDL Electronic device description language (see IEC 61804)
______________
HART® and wirelessHART® are the registered trademark of FieldComm Group. This information is given for
the convenience of users of this document and does not constitute an endorsement by IEC of the product
named. Equivalent products may be used if they can be shown to lead to the same results.
Under preparation. Stage at the time of publication: IEC/RFDIS 62769-4:2020.

FDI Field device integration
FSK Frequency-Shift-Keying
HCF HART Communication Foundation
ID Identification
IM Information Model
IP Internet protocol
PDU Protocol data unit
PSK Phase-Shift-Keying
TCP Transmission Control Protocol (see IETF RFC 793)
UDP User Datagram Protocol (see IETF RFC 768)
XML Extensible markup language
3.3 Conventions
3.3.1 EDDL syntax
This document specifies content for the EDD component that is part of FDI Communication
Packages. EDDL syntax uses the font Courier New. EDDL syntax is used for method
signature, variable, data structure and component declarations.
3.3.2 XML syntax
XML syntax examples use font Courier New. The XML syntax is used to describe XML
document schema.
EXAMPLE
3.3.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:
• FDI Communication Servers or
• Profile 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 like:
• PROFILE_ID or
• HART_Network.
– 8 – IEC 62769-109-1:2020 © IEC 2020
® ®
4 Profile for CP 9/1 (HART ) or CP 9/2 (WirelessHART )
4.1 General
This profile document to the FDI specification in IEC 62769 selects the protocol specifics
needed for FDI Packages describing FDI Communication Servers, gateways and devices.
4.2 Catalog profile
4.2.1 Protocol support file
Device information files provide metadata for the dynamic runtime data that is supplied by the
device. This metadata is a subset of information that is contained in the EDD. The device
information files may be extracted from the package by light-weight gateway or server
implementations to exchange runtime device information with minimal implementation
overhead. Device information files do not replace the need for the EDD part because device
information files only contain a subset of the information from the EDD, and do not provide
any user-interface elements.
The formats of the Device Information Files are described in Table 1.
Table 1 – Device Information Files
Part Content
Content Type Not specified here
Root Namespace Not specified here
Source http://fdi-cooperation.com/2010/relationships/attachment-protocol
Relationship
Filename Not specified here
The Device Information Files are specified in FCG AG21073.
4.2.2 CommunicationProfile definition
IEC 62769-4 defines a CommunicationProfileT string type for the Catalog XML schema.
Table 2 defines the CP 9/1 specific values for this enumeration.
Table 2 – CommunicationProfile definition
CommunicationProfile Description
hart_fsk CP 9/1 device type that supports an FSK physical layer (Frequency-Shift-Keying on
a pair of wires)
hart_psk CP 9/1 device type that supports a PSK physical layer (Phase-Shift-Keying on a pair
of wires). Devices supporting PSK are required to also inherently support FSK, and
therefore PSK will always be used only in combination with at least FSK.
hart_wirelesshart CP 9/2 device type that supports a wireless physical layer (communication between
device and gateway).
hart_ip CP 9/1 device type that supports Internet Protocol (these devices support both TCP
and UDP).
hart_rs485 CP 9/1 device type that supports EIA-485 digital communication.
hart_ir CP 9/1 device type that supports an Infrared physical layer (designed to be
transparent to FSK masters – included only as information to indicate that the device
supports IR connection).
NOTE It is possible for a single CP 9/1 device to support more than one CP.

4.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
DeviceModel — Empty
Manufacturer — Empty
4.2.4 Protocol version information
IEC 62769-4 defines an element type named InterfaceT for the Catalog XML Schema.
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 element type VersionT.
Subclause 4.2.4 describes how to apply the currently known protocol versions for CP 9/1 or
CP 9/2 entries in the device catalog. The general rule is to use the Universal Revision of the
protocol for the major version part of VersionT, and the value "0" for the minor version and
build parts. Table 4 shows the Protocol Version Information.
Table 4 – Protocol Version Information
Protocol Version InterfaceT Version value
HART Universal Revision 5 5.0.0
HART Universal Revision 6 6.0.0
HART Universal Revision 7 7.0.0
The Protocol Version defined in a package is provided for informational purposes only and shall not be used to
determine the compatibility or applicability of a package to a device.

4.3 Associating a Package with a CP 9/1 device
4.3.1 Device type identification mapping
CP 9/1 device types are uniquely identified by parameters Manufacturer, Model and
DeviceRevision. These parameters are used to associate a given device instance to an FDI
Device Package. These parameters are mapped to the FDI Device Package Catalog
according to Table 5.
Table 5 – Device type catalog mapping
Catalog element CP mapping (SeeTable A.)
Manufacturer element of InterfaceT Manufacturer
(IEC 62769-4:–, Clause E.10)
String format "0xdddd" where dddd is the
MANUFACTURER_ID in hexadecimal format.
DeviceModel element of InterfaceT Model
(IEC 62769-4:–, Clause E.10)
String format "0xdddd" where dddd is the
DEVICE_TYPE in hexadecimal format.

– 10 – IEC 62769-109-1:2020 © IEC 2020
Catalog element CP mapping (SeeTable A.)
DeviceRevision element DeviceRevision
ListOfSupportedDeviceRevisionsT String format "x.0.0" where x is the
(IEC 62769-4:–, Clause E.20) DEVICE_REVISION in decimal format (no
leading zeros).
4.3.2 Device type revision mapping
Each device type is identified as per 4.3.1. If a package with matching DeviceRevision is not
available, any CP 9/1 FDI package for a corresponding manufacturer and model shall always
be compatible with a field device as long as the device revision of the field device is equal to
or greater than the device revision specified in the FDI package.
4.4 Information Model mapping
4.4.1 ProtocolType definition
Table 6 defines the ProtocolType used to identify CP 9/1 network communications.
Table 6 – ProtocolType HART definition
Attribute Value
BrowseName HART
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Inherits the properties of ProtocolType defined in IEC 62541-100.

4.4.2 DeviceType mapping
Each device type inherits the properties of DeviceType. The mapping of the inherited
properties from DeviceType is defined in Table 7.
Table 7 – Inherited DeviceType Property mapping
Property Foundation mapping
SerialNumber Unique ID of a device, mapped to SERIAL_NUMBER of IdentificationT.
RevisionCounter Configuration change counter, mapped to REV_COUNTER of
IdentificationT
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)
a
DeviceManual
Entry text string (not supported)
DeviceRevision Device revision level of a device, mapped to DEVICE_REVISION of
IdentificationT
SoftwareRevision Software revision level of a device, mapped to SOFTWARE_REVISION of
IdentificationT
Hardware revision level of a device, mapped to HARDWARE_REVISION of
HardwareRevision
IdentificationT
a
Device manuals are exposed as attachments of the FDI Device Package.

4.4.3 FunctionalGroup Identification definition
As defined in IEC 62541-100, each device representation in the FDI Server hosted
Information Model shall contain a protocol specific FunctionalGroup called Identification. This
FunctionalGroup organizes variables found in the device type instance. The FunctionalGroup
Identification for CP 9/1 is defined in Table 8.
Table 8 – Identification parameters
BrowseName DataType Optional/Mandatory
MANUFACTURER_ID UInt16 Mandatory
DEVICE_TYPE UInt16 Mandatory
DEVICE_REVISION UInt8 Mandatory
UNIVERSAL_REVISION UInt8 Optional
SERIAL_NUMBER UInt24 Optional
HARDWARE_REVISION UInt8 Optional
SOFTWARE_REVISION UInt8 Optional
REVISION_COUNTER UInt16 Optional

4.5 Topology elements
4.5.1 ConnectionPoint definition
4.5.1.1 General
CP 9/1 devices can support up to five different ConnectionPoint types that are used for
network communications.
4.5.1.2 HART_TP5, HART_TP6, HART_TP7
The ConnectionPoint types HART_TP5, HART_TP6, and HART_TP7 shall be used to identify
CP 9/1 token passing network communication and are defined in Table 9. HART_TP5,
HART_TP6, and HART_TP7 all contain the same properties, but each provides different
qualification information for some of the properties (described below). The Protocol Version
(UNIVERSAL_REVISION) described in 4.2.4 can be used as an aid to determine which of the
three token passing Connection Point types is the most appropriate. CP 9/1 token passing
communications can be used on a variety of physical layers. FSK, PSK, RS485, and Infrared
physical layer connections shall all use the HART_TP connection type. The ConnectionPoint
types HART_TP5, HART_TP6, and HART_TP7 are subtypes of abstract type
ConnectionPointType defined in IEC 62769-5.
The DevAddr property shall be the long address (5 bytes) for the device and is the only
parameter necessary to communicate with the field device.
The DevMfg property shall be the 2-byte Manufacturer ID and can be used to help automate
the process of assigning live devices in the scan list to offline placeholders.
The DevType property shall be the 2-byte extended device type and can be used to help
automate the process of assigning live devices in the scan list to offline placeholders.
The DevRev property shall be the device revision and can be used to help automate the
process of assigning live devices in the scan list to offline placeholders. ®
The DevTag property shall be the long tag for HART protocol version 6 or 7 devices. The
DevTag property shall be the tag for protocol version 5 devices. The DevTag property can be
used to help automate the process of assigning live devices in the scan list to offline

– 12 – IEC 62769-109-1:2020 © IEC 2020
placeholders. HART_TP5 Connection Points shall limit the DevTag to 8 characters in length.
HART_TP6 and HART_TP7 Connection Points shall limit the DevTag to 32 characters in
length.
The DevPollAddr property shall be the poll address and can be used to identify which device
is located at a specific poll address. HART_TP5 Connection Points shall be limited to values
between 0 and 15 for the DevPollAddr property. HART_TP6 Connection Points shall be
limited to values between 0 and 31 for the DevPollAddr property. HART_TP7 Connection
Points shall be limited to values between 0 and 63 for the DevPollAddr property.
For forward compatibility, a lower revision HART_TP Connection Point is compatible and can
be used for a higher universal revision device connection. For example, if a future HART
universal revision 8 device is encountered, and no HART_TP8 is available in the FDI server,
HART_TP7 will be compatible and shall be used to connect to the device. If the Protocol
Version (i.e. the Universal Revision) is unknown for any reason, the HART_TP5 Connection
Point can be used, and will be forward compatible to later universal revisions.
Table 9 – ConnectionPointType HART_TP definition
Attribute Value
BrowseName ConnnectionPoint_HART_TP5 or ConnnectionPoint_HART_TP6 or
ConnnectionPoint_HART_TP7
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Inherits the properties of ConnectionPointType defined in IEC 62769-5
HasProperty Variable DevAddr UInt40 PropertyType Mandatory
HasProperty Variable DevMfg UInt16 PropertyType Optional
HasProperty Variable DevType UInt16 PropertyType Optional
HasProperty Variable DevRev UInt16 PropertyType Optional
HasProperty Variable DevTag String PropertyType Optional
HasProperty Variable DevPollAddr UInt8 PropertyType Optional

The ConnectionPoint type HART_TP5, HART_TP6, and HART_TP7 shall be described by an
EDD element contained in a Communication Device related FDI Package that can drive a
CP 9/1 network. Actual ConnectionPoint properties are declared by VARIABLE constructs
grouped together in a COLLECTION named ConnectionPoint_HART_TP5,
ConnectionPoint_HART_TP6, or ConnectionPoint_HART_TP7. The following EDDL source
code is an example describing a TP5 Connection Point.
COMPONENT ConnectionPoint_HART_TP5
{
LABEL "HART TP Connection Point";
CLASSIFICATION NETWORK_CONNECTION_POINT;
CAN_DELETE FALSE;
PROTOCOL HART;
CONNECTION_POINT ConnectionPoint_TP5;
}
VARIABLE DevAddr
{
LABEL "Address";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER(5);
HANDLING READ & WRITE;
}
VARIABLE DevMfg
{
LABEL "Manufacturer";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER(2);
HANDLING READ & WRITE;
}
VARIABLE DevType
{
LABEL "Device Type";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER(2);
HANDLING READ & WRITE;
}
VARIABLE DevRev
{
LABEL "Device Revision";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER;
HANDLING READ & WRITE;
}
VARIABLE DevTag
{
LABEL "Tag";
CLASS DEVICE;
TYPE ASCII(32);
HANDLING READ & WRITE;
}
VARIABLE DevPollAddr
{
LABEL "Poll Address";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER
{
MAX_VALUE 15; //Define appropriate max value for various revisions
}
HANDLING READ & WRITE;
}
COLLECTION ConnectionPoint_TP5
{
LABEL "Connection Point";
MEMBERS
{
ADDRESS,  DevAddr,   "Device Address";
MFG,    DevMfg,   "Manufacturer";
DEV_TYPE, DevType,   "Device Type";
DEV_REV,  DevRev,   "Device Revision";
TAG,    DevTag,   "Device Tag";
POLL_ADDR, DevPollAddr, "Poll Address";
}
}
– 14 – IEC 62769-109-1:2020 © IEC 2020
4.5.1.3 HART_IP
The ConnectionPoint type HART_IP shall be used to identify CP 9/1 IP network
communication and is defined in Table 10. HART_IP communications can be used on a
variety of physical layers. Ethernet connections shall all use the HART_IP connection type.
Additional physical layers developed in the future may also use the HART_IP connection type.
The ConnectionPoint type HART_IP is a subtype of abstract type ConnectionPointType
defined in IEC 62769-5.
The IPAddress property shall indicate the IP Address (up to 16 bytes) used for the
connection.
The IPVersion property shall indicate the version of IP used for the connection (either 4 or 6).
The IPPort property shall be the IP port number for the connection. The default port number
used for HART IP is 5 094.
The DevAddr property shall be the long address (5 bytes) for the device.
The DevMfg property shall be the 2-byte Manufacturer ID and can be used to help automate
the process of assigning live devices in the scan list to offline placeholders.
The DevType property shall be the 2-byte extended device type and can be used to help
automate the process of assigning live devices in the scan list to offline placeholders.
The DevRev property shall be the device revision and can be used to help automate the
process of assigning live devices in the scan list to offline placeholders.
The DevTag property shall be the long tag (with maximum 32 characters) and can be used to
help automate the process of assigning live devices in the scan list to offline placeholders.
Table 10 – ConnectionPointType HART_IP Definition
Attribute Value
BrowseName ConnnectionPoint_HART_IP
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Inherits the properties of ConnectionPointType defined in IEC 62769-5
HasProperty Variable IPAddress ByteString PropertyType Mandatory
HasProperty Variable IPVersion UInt8 PropertyType Mandatory
HasProperty Variable IPPort UInt16 PropertyType Mandatory
HasProperty Variable DevAddr UInt40 PropertyType Mandatory
HasProperty Variable DevMfg UInt16 PropertyType Optional
HasProperty Variable DevType UInt16 PropertyType Optional
HasProperty Variable DevRev UInt16 PropertyType Optional
HasProperty Variable DevTag String PropertyType Optional

The ConnectionPoint type HART_IP shall be described by an EDD element contained in a
Communication Device related FDI Package that can drive a CP 9/1 network. Actual
ConnectionPoint properties are declared by VARIABLE constructs grouped together in a
COLLECTION named ConnectionPoint_HART_IP. The following EDDL source code is an
example describing an IP Connection Point.

COMPONENT ConnectionPoint_HART_IP
{
LABEL "HART IP Connection Point";
CLASSIFICATION NETWORK_CONNECTION_POINT;
CAN_DELETE FALSE;
PROTOCOL HART;
CONNECTION_POINT ConnectionPoint_IP;
}
ARRAY IPAddress
{
LABEL "IP Address";
CLASS DEVICE;
TYPE OCTET(16);
HANDLING READ & WRITE;
}
VARIABLE IPVersion
{
LABEL "IP Version";
CLASS DEVICE;
TYPE ENUMERATED
{
{ 4, "IPv4" },
{ 6, "IPv6" }
}
HANDLING READ & WRITE;
}
VARIABLE IPPort
{
LABEL "IP Port";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER (2);
DEFAULT_VALUE 5 094;
HANDLING READ & WRITE;
}
COLLECTION ConnectionPoint_IP
{
LABEL "Connection Point";
MEMBERS
{
IPADDRESS, IPAddress, "IP Address";
IPVERSION, IPVersion, "IP Version";
IPPORT,  IPPort,  "IP Port";
ADDRESS,  DevAddr,  "Device Address";
MFG,    DevMfg,  "Manufacturer";
DEV_TYPE, DevType,  "Device Type";
DEV_REV,  DevRev,  "Device Revision";
TAG,    DevTag,  "Device Tag";
}
}
4.5.1.4 HART_TDMA
The ConnectionPoint type HART_TDMA shall be used to identify CP 9/2 time division media
access network communication and is defined in Table 11. HART_TDMA communications
can be used on a variety of physical layers. The ConnectionPoint type HART_TDMA is a
subtype of abstract type ConnectionPointType defined in IEC 62769-5. WirelessHART
connections shall all use the HART_TDMA connection type. Additional physical layers
developed in the future may also use the HART_TDMA connection type.

– 16 – IEC 62769-109-1:2020 © IEC 2020
The Network property shall be the network ID for the network.
The DevAddr property shall be the long address (5 bytes) for the device.
The DevMfg property shall be the 2 byte Manufacturer ID, and can be used to help automate
the process of assigning live devices in the scan list to offline placeholders.
The DevType property shall be the 2 byte extended device type, and can be used to help
automate the process of assigning live devices in the scan list to offline placeholders.
The DevRev property shall be the device revision and can be used to help automate the
process of assigning live devices in the scan list to offline placeholders.
The DevTag property shall be the long tag (with maximum 32 characters) and can be used to
help automate the process of assigning live devices in the scan list to offline placeholders.
Table 11 – ConnectionPointType HART_TDMA Definition
Attribute Value
BrowseName ConnnectionPoint_HART_TDMA
IsAbstract False
References NodeClass BrowseName DataType TypeDefinition ModellingRule
Inherits the properties of ConnectionPointType defined in IEC 62769-5
HasProperty Variable Network UInt16 PropertyType Mandatory
HasProperty Variable DevAddr UInt40 PropertyType Mandatory
HasProperty Variable DevMfg UInt16 PropertyType Optional
HasProperty Variable DevType UInt16 PropertyType Optional
HasProperty Variable DevRev UInt16 PropertyType Optional
HasProperty Variable DevTag String PropertyType Optional

The ConnectionPoint type HART_TDMA shall be described by an EDD element contained in a
Communication Device related FDI Package that can drive a CP 9/2 network. Actual
ConnectionPoint properties are declared by VARIABLE constructs grouped together in a
COLLECTION named ConnectionPoint_HART_TDMA. The following EDDL source code is an
example describing a TDMA Connection Point.
COMPONENT ConnectionPoint_HART_TDMA
{
LABEL "HART TDMA Connection Point";
CLASSIFICATION NETWORK_CONNECTION_POINT;
CAN_DELETE FALSE;
PROTOCOL HART;
CONNECTION_POINT ConnectionPoint_TDMA;
}
VAR
...