EN 62769-109-1:2015

SLOVENSKI STANDARD
01-november-2015
9NOMXþLWHYSURFHVQHQDSUDYH)',GHO3URILOL+$57ŠLQEUH]åLþQL+$57Š
,(&
Field Device Integration (FDI) - Part 109-1: Profiles - HART(r) and WirelessHART(r) (IEC
62769-109-1:2015)
Feldgeräteintegration (FDI) - Profile - Teil 109-1: HART(r) und WirelessHART(r) (IEC
62769-109-1:2015)
Intégration des appareils de terrain (FDI) - Partie 109-1: Profils - HART(r) et
WirelessHART(r) (IEC 62769-109-1:2015)
Ta slovenski standard je istoveten z: EN 62769-109-1:2015
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN 62769-109-1

NORME EUROPÉENNE
EUROPÄISCHE NORM
July 2015
ICS 25.040.40; 35.100
English Version
Field Device Integration (FDI) - Part 109-1: Profiles - HART(r)
and WirelessHART(r)
(IEC 62769-109-1:2015)
Intégration des appareils de terrain (FDI) - Partie 109-1: Feldgeräteintegration (FDI) - Profile - Teil 109-1: HART(r)
Profils - HART(r) et WirelessHART(r) und WirelessHART(r)
(IEC 62769-109-1:2015) (IEC 62769-109-1:2015)
This European Standard was approved by CENELEC on 2015-06-23. CENELEC members are bound to comply with the CEN/CENELEC
Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC
Management Centre or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the
same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2015 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.

Ref. No. EN 62769-109-1:2015 E

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

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

1) To be published.
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
NOTE 1 When an International Publication has been modified by common modifications, indicated by (mod), the relevant
EN/HD applies.
NOTE 2 Up-to-date information on the latest versions of the European Standards listed in this annex is available here:
www.cenelec.eu.
Publication Year Title EN/HD Year

IEC 62541-100 -  OPC unified architecture - Part 100: Device EN 62541-100 -
Interface
IEC 62769-4 2015 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
IEC 62769-109-1 ®
Edition 1.0 2015-05
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 ISBN 978-2-8322-2638-4

– 2 – IEC 62769-109-1:2015  IEC 2015
CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 7
2 Normative references . 7
3 Terms, definitions, abbreviated terms and acronyms . 7
3.1 Terms and definitions . 7
3.2 Abbreviated terms and acronyms . 7
4 Conventions . 8
4.1 EDDL syntax . 8
4.2 XML syntax . 8
4.3 Capitalizations . 8
® ®
5 Profile for CP 9/1 (HART ) or CP 9/2 (WirelessHART ) . 9
5.1 General . 9
5.2 Catalog profile . 9
5.2.1 Protocol support file . 9
5.2.2 CommunicationProfile definition . 9
5.2.3 Profile device . 9
5.2.4 Protocol version information . 9
5.3 Associating a Package with a 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 . 11
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 . 19
5.6.1 Methods for FDI Communication Servers . 19
5.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 . 34
A.5 AddressTypeTDMA . 34
A.6 AddressType . 35
A.7 ConnectionPointType . 36
A.8 NetworkType . 36
A.9 Network . 37
Annex B (normative) Transfer service parameters . 38
B.1 General . 38

IEC 62769-109-1:2015  IEC 2015 – 3 –
B.2 receiveData . 38
B.3 sendData . 38
B.4 TransferResultDataT . 38
B.5 TransferSendDataT . 39
Bibliography . 40

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

– 4 – IEC 62769-109-1:2015  IEC 2015
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.
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.
The text of this standard is based on the following documents:
CDV Report on voting
65E/356/CDV 65E/419/RVC
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts in the IEC 62769 series, published under the general title Field Device
Integration (FDI), can be found on the IEC website.

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

IEC 62769-109-1:2015  IEC 2015 – 7 –
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 1
(HART ) and IEC 61784-1_CP 9/2 (WirelessHART ) .
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
IEC 62541-100, OPC unified architecture – 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: Communication Devices
NOTE IEC 62769-7 is technically identical to FDI-2027.
3 Terms, definitions, abbreviated terms and acronyms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62541-100,
IEC 62769-4, IEC 62769-5 and IEC 62769-7 apply.
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
—————————
HART and WirelessHART are the trade names of the non-profit consortium HART Communication Foundation,
Austin,Texas, USA. 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 names.
Use of the trade names requires permission of the trade name holder.

– 8 – IEC 62769-109-1:2015  IEC 2015
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 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
• ProtocolType.
Parameter names or attributes can also be constructed by using an underscore character to
concatenate two or more terms such as:
• PROFILE_ID, or
• HART_Network.
IEC 62769-109-1:2015  IEC 2015 – 9 –
® ®
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 specifies the protocol specifics
needed for FDI Packages describing FDI Communication Servers, gateways and devices.
5.2 Catalog profile
5.2.1 Protocol support file
No additional file is required for CP 9/1 or CP 9/2 FDI Device Packages.
5.2.2 CommunicationProfile definition
IEC 62769-4 defines a CommunicationProfileT enumeration type for the Catalog XML
schema. Table 1 defines the CP 9/1 specific values for this enumeration.
Table 1 – 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.

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 2 focus on catalog content that is vendor independent.
Table 2 – 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. The
element type InterfaceT contains an element named Version which is supposed to provide
version information about the applied communication protocol profile. The value has to follow
the IEC 62769-4 defined version information schema defined in 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

– 10 – IEC 62769-109-1:2015  IEC 2015
protocol for the major version part of VersionT, and the value “0” for the minor version and
build parts. Table 3 shows the Protocol Version Information.
Table 3 – 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.
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 4.
Table 4 – 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
Clause E.21) DeviceRevision 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 5 defines the ProtocolType used to identify CP 9/1 network communications.
Table 5 – 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.

IEC 62769-109-1:2015  IEC 2015 – 11 –
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 6.
Table 6 – 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
Model 2-byte extended device type of a device, returned in bytes 1 and 2 of
Command 0 or Command 11 or Command 21
a
DeviceManual 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.

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 7.
Table 7 – 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.
– 12 – IEC 62769-109-1:2015  IEC 2015
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 8. 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 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 8 – 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

IEC 62769-109-1:2015  IEC 2015 – 13 –
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:2015  IEC 2015
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 9. 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.

IEC 62769-109-1:2015  IEC 2015 – 15 –
Table 9 – 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;
}
– 16 – IEC 62769-109-1:2015  IEC 2015
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 10. 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
d
...