IEC 62769-109-1:2023

IEC 62769-109-1 ®
Edition 3.0 2023-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 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-109-1 ®
Edition 3.0 2023-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-6888-9
– 2 – IEC 62769-109-1:2023 RLV © IEC 2023
CONTENTS
FOREWORD . 4
1 Scope . 6
2 Normative references . 6
3 Terms, definitions, abbreviated terms and conventions acronyms . 6
3.1 Terms and definitions . 6
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 CP 9/1 (HART ) or CP 9/2 (WirelessHART ) . 8
5.1 General . 8
5.2 Catalog profile . 8
5.2.1 Protocol support file . 8
5.2.2 CommunicationProfile definition . 8
5.2.3 Profile device . 9
5.2.4 Protocol version information . 9
5.3 Associating a Package with a CP 9/1 device . 10
5.3.1 Device type identification mapping . 10
5.3.2 Device type revision mapping . 10
5.4 Information Model mapping . 10
5.4.1 ProtocolType definition . 10
5.4.2 DeviceType mapping . 10
5.4.3 FunctionalGroup Identification definition . 11
5.5 Topology elements . 11
5.5.1 ConnectionPoint definition . 11
5.5.2 Communication Device definition . 17
5.5.3 Communication service provider definition . 18
5.5.4 Network definition . 19
5.6 Methods . 20 ®
5.6.1 Methods for FDI Communication Servers . 20
5.6.2 Methods for Gateways . 24
Annex A (normative) Topology scan schema . 33
A.1 General . 33
A.2 IdentificationType . 33
A.3 AddressTypeTP . 36
A.4 AddressTypeIP . 37
A.5 AddressTypeTDMA . 37
A.6 AddressType . 38
A.7 ConnectionPointType . 39
A.8 NetworkType . 39
A.9 Network . 40
Annex B (normative) Transfer service parameters . 41
B.1 General . 41
B.2 receiveData . 41
B.3 sendData . 41

B.4 TransferResultDataT . 41
B.5 TransferSendDataT . 42
Annex C (informative) Mapping to PA DIM . 43
C.1 General . 43
C.2 Mapping Table . 43
Bibliography . 44

Table 1 – Device Information Files . 8
Table 2 – CommunicationProfile definition . 9
Table 3 – Catalog values for profile devices . 9
Table 4 – Protocol Version Information . 9
Table 5 – Device type catalog mapping . 10
Table 6 – ProtocolType HART definition . 10
Table 7 – Inherited DeviceType Property mapping . 11
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 . 17
Table 12 – Method Connect arguments . 21
Table 13 – Method Disconnect arguments . 21
Table 14 – Method Transfer arguments . 22
Table 15 – Method GetPublishedData arguments. 23
Table 16 – Method SetAddress arguments . 24
Table 17 – Method Connect arguments . 25
Table 18 – Method Disconnect arguments . 26
Table 19 – Method Transfer arguments . 27
Table 20 – Method GetPublishedData arguments. 29
Table 21 – Method SetAddress arguments . 30
Table A.1 – Attributes of IdentificationT . 35
Table A.2 – Elements of AddressTypeTP . 36
Table A.3 – Elements of AddressTypeIP . 37
Table A.4 – Elements of AddressTypeTDMA . 38
Table A.5 – Elements of AddressT . 38
Table A.6 – Elements of ConnectionPointT . 39
Table A.7 – Elements of NetworkT . 39
Table B.1 – Attributes of TransferResultDataT . 41
Table B.2 – Attributes of TransferSendDataT . 42
Table C.1 – Mapping from HART standard parameters to PA DIM . 43

– 4 – IEC 62769-109-1:2023 RLV © IEC 2023
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 IEC 62769-109-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-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. 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 content type for DeviceInfo files;
b) added mapping from HART standard parameters to PA DIM;
The text of this International Standard is based on the following documents:
Draft Report on voting
65E/864/CDV 65E/921/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/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 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-109-1:2023 RLV © IEC 2023 ®
FIELD DEVICE INTEGRATION (FDI ) –

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

1 Scope
®1
This part of IEC 62769 specifies an FDI profile of IEC 62769 for IEC 61784-1_CP 9/1
® 2 ® 3
(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: OPC Device Interface
4 ® ®
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 acronyms
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
___________
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.
HART® and wirelessHART® are is the registered trademark trade name of the non-profit consortium FieldComm
Group. This information is given for the convenience of users of this technical report and does not constitute an
endorsement by IEC of the product named trademark holder or any of its products. Equivalent products may be
used if they can be shown to lead to the same results. Compliance does not require use of the trade name. Use
of the trade name requires permission of the trade name holder.
WirelessHART is the trade name of the non-profit consortium FieldComm Group. 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-4:2020.

3.2 Abbreviated terms and acronyms
For the purposes of this document, the following abbreviated terms and acronyms 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 the IEC 61804 series)
EDDL Electronic device description language (see the IEC 61804 series) ®
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 Extended markup language
4 Conventions
4.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.
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 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
– 8 – IEC 62769-109-1:2023 RLV © IEC 2023
• 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
® ®
5 Profile for CP 9/1 (HART ) or CP 9/2 (WirelessHART )
5.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.
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
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 application/vnd.hart.json
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.
5.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)
CP 9/1 device type that supports a PSK physical layer (Phase-Shift-Keying on a pair
hart_psk
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.

5.2.3 Profile device ®
A Profile Package shall provide the catalog values for profile devices, enabling the FDI Server
to leverage a generic device description, if a specific one is not available. The definitions in
Table 3 focus on catalog content that is vendor independent.
Table 3 – Catalog values for profile devices
Element Attribute Content
PackageType — Profile
DeviceModel — Empty
Manufacturer — Empty
5.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
5.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.
– 10 – IEC 62769-109-1:2023 RLV © IEC 2023
5.3 Associating a Package with a CP 9/1 device
5.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.1)
Manufacturer element of InterfaceT (IEC 62769-4:2023, Manufacturer
Clause E.11)
String format “0xdddd” where dddd is the
MANUFACTURER_ID in hexadecimal format.
DeviceModel element of InterfaceT (IEC 62769-4:2023, Model
Clause E.11)
String format “0xdddd” where dddd is the
DEVICE_TYPE in hexadecimal format.
DeviceRevision element DeviceRevision
ListOfSupportedDeviceRevisionsT (IEC 62769-4:2023, String format “x.0.0” where x is the
Clause E.20) DEVICE_REVISION in decimal format (no leading
zeros).
5.3.2 Device type revision mapping
Each device type is identified as per 5.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.
5.4 Information Model mapping
5.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

5.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)
DeviceManual a
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.

5.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

5.5 Topology elements
5.5.1 ConnectionPoint definition
5.5.1.1 General
CP 9/1 devices can support up to five different ConnectionPoint types that are used for network
communications.
5.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

– 12 – IEC 62769-109-1:2023 RLV © IEC 2023
qualification information for some of the properties (described below). The Protocol Version
(UNIVERSAL_REVISION) described in 5.2.3 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
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;
}
– 14 – IEC 62769-109-1:2023 RLV © IEC 2023
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";
}
}
5.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;
– 16 – IEC 62769-109-1:2023 RLV © IEC 2023
}
VARIABLE IPPort
{
LABEL "IP Port";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER (2);
DEFAULT_VALUE 5 0945094;
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";
}
}
5.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.
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;
}
VARIABLE Network
{
LABEL "Network ID";
CLASS DEVICE;
TYPE UNSIGNED_INTEGER (2);
HANDLING READ & WRITE;
}
COLLECTION ConnectionPoint_TDMA
{
LABEL "Connection Point";
MEMBERS
{
NETWORK, Network, "Network ID";
ADDRESS, DevAddr, "Device Address";
MFG,
...