CLC IEC/TR 62453-52-90:2019

SLOVENSKI STANDARD
01-maj-2019
Specifikacija vmesnika orodja procesne naprave - 52-90. del: Implementacija
komunikacije za skupno jezikovno infrastrukturo - IEC 61784 CPF 9 (IEC/TR 62453-
52-90:2017)
Field device tool (FDT) interface specification - Part 52-90: Communication
implementation for common language infrastructure - IEC 61784 CPF 9 (IEC/TR 62453-
52-90:2017)
Field Device Tool (FDT)-Schnittstellenspezifikation - Teil 52-90:
Kommunikationsimplementierung mit der allgemeinen Sprachinfrastruktur -
Kommunikationsprofilfamilie (CPF) 9 nach IEC 61784 (IEC/TR 62453-52-90:2017)
Spécification des interfaces des outils des dispositifs de terrain (FDT) – Partie 52-90:
Mise en oeuvre d’un profil de communication pour l’infrastructure commune de langage –
CPF 9 de l’IEC 61784 (IEC/TR 62453-52-90:2017)
Ta slovenski standard je istoveten z: CLC IEC/TR 62453-52-90:2019
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.

TECHNICAL REPORT CLC IEC/TR 62453-52-90

RAPPORT TECHNIQUE
TECHNISCHER BERICHT
February 2019
ICS 25.040.40; 35.100.05; 35.110

English Version
Field device tool (FDT) interface specification - Part 52-90:
Communication implementation for common language
infrastructure - IEC 61784 CPF 9
(IEC/TR 62453-52-90:2017)
Spécification des interfaces des outils des dispositifs de Field Device Tool (FDT)-Schnittstellenspezifikation - Teil
terrain (FDT) – Partie 52-90: Mise en œuvre d’un profil de 52-90: Kommunikationsimplementierung mit der
communication pour l’infrastructure commune de langage – allgemeinen Sprachinfrastruktur -
CPF 9 de l’IEC 61784 Kommunikationsprofilfamilie (CPF) 9 nach IEC 61784
(IEC/TR 62453-52-90:2017) (IEC/TR 62453-52-90:2017)

This Technical Report was approved by CENELEC on 2019-01-14.

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, Serbia, 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: Rue de la Science 23, B-1040 Brussels
© 2019 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. CLC IEC/TR 62453-52-90:2019 E

European foreword
This document (CLC IEC/TR 62453-52-90:2019) consists of the text of IEC/TR 62453-52-90:2017
prepared by SC 65E "Devices and integration in enterprise systems" of IEC/TC 65 "Industrial-process
measurement, control and automation".
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC shall not be held responsible for identifying any or all such patent rights.

Endorsement notice
The text of the International Standard IEC/TR 62453-52-90:2017 was approved by CENELEC as a
European Standard without any modification.

Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
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.
NOTE 1  Where 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 61784-1 2014 Industrial communication networks - EN 61784-1 2014
Profiles - Part 1: Fieldbus profiles
IEC 62453-1 2016 Field device tool (FDT) interface EN 62453-1 2017
specification - Part 1: Overview and
guidance
IEC 62453-2 2016 Field device tool (FDT) interface EN 62453-2 2017
specification - Part 2: Concepts and
detailed description
IEC TR 62453-42 2016 Field device tool (FDT) interface - -
specification - Part 42: Object model
integration profile - Common language
infrastructure
IEC 62453-309 2016 Field device tool (FDT) interface EN 62453-309 2017
specification – Part 309: Communication
profile integration – IEC 61784 CPF 9

IEC TR 62453-52-90 ®
Edition 1.0 2017-06
TECHNICAL
REPORT
colour
inside
Field device tool (FDT) interface specification –

Part 52-90: Communication implementation for common language

infrastructure – IEC 61784 CPF 9

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 25.040.40; 35.100.05; 35.110 ISBN 978-2-8322-4333-6

– 2 – IEC TR 62453-52-90:2017 © IEC 2017
CONTENTS
FOREWORD . 5
INTRODUCTION . 7
1 Scope . 8
2 Normative references . 8
3 Terms, definitions, symbols, abbreviated terms and conventions . 8
3.1 Terms and definitions . 8
3.2 Symbols and abbreviated terms . 9
3.3 Conventions . 9
3.3.1 Datatype names and references to datatypes . 9
3.3.2 Vocabulary for requirements . 9
3.3.3 Use of UML . 9
4 Bus category . 9
5 Access to instance and device data . 9
5.1 General . 9
5.2 IO signals provided by DTM . 9
5.3 Data interfaces . 10
5.3.1 General . 10
5.3.2 Mapping HART datatypes to FDT datatypes . 10
5.3.3 SemanticInfo . 11
5.3.4 Data exposure using IDeviceData and IInstanceData interfaces . 12
6 Protocol specific behaviour . 18
6.1 Support of burst mode . 18
6.2 Device addressing . 19
6.3 Support of scanning . 19
6.4 Support of extended command numbers . 19
6.5 Support for handling of communication failures and time-outs . 19
6.6 Support for handling of Delayed Responses . 20
6.7 Support for topologies with mixed HART protocols . 20
6.8 Support for nested communication with multiple gateways . 20
6.9 Support for topologies with WirelessHART . 20
6.10 Transparent gateways . 20
6.10.1 General . 20
6.10.2 Scenario 1 – Manual topology creation . 20
6.10.3 Scenario 2 – Topology scan and add . 21
7 Protocol specific usage of general datatypes . 21
8 Protocol specific common datatypes . 21
8.1 HartDeviceAddress datatype . 21
8.2 HartDeviceIpAddress datatype . 22
8.3 HartDeviceWirelessAddress datatype . 23
9 Network management datatypes . 24
10 Communication datatypes . 24
10.1 General . 24
10.2 HartConnectRequest datatype . 24
10.3 HartConnectResponse datatype . 25
10.4 HartLongAddress datatype . 26
10.5 HartDisconnectRequest datatype . 26

IEC TR 62453-52-90:2017 © IEC 2017 – 3 –
10.6 HartDisconnectResponse datatype . 27
10.7 HartTransactionRequest datatype . 27
10.8 HartTransactionResponse datatype . 28
10.9 HartStatus datatype . 29
10.10 HartAbortMessage datatype . 29
10.11 HartSubscribeRequest datatype . 30
10.12 HartSubscribeResponse datatype . 30
10.13 HartUnsubscribeRequest datatype . 30
10.14 HartUnsubscribeResponse datatype . 31
11 Datatypes for process data information . 31
11.1 General . 31
11.2 HartIOSignalInfo datatype . 32
12 Device identification datatypes . 33
12.1 General . 33
12.2 HartDeviceScanInfo datatype . 33
12.3 HartDeviceIdentInfo datatype . 37
12.4 Mapping of information source . 38
Bibliography . 41

Figure 1 – Part 52-90 of the IEC 62453 series . 7
Figure 2 – Structural information for device variables . 16
Figure 3 – Structural information for dynamic variables . 17
Figure 4 – Structural information for extended device status . 18
Figure 5 – Device-initiated data transfer with burst mode . 19
Figure 6 – HartDeviceAddress datatype . 21
Figure 7 – HartDeviceIpAddress datatype . 22
Figure 8 – HartDeviceWirelessAddress datatype . 23
Figure 9 – HartNetworkData datatype . 24
Figure 10 – HartConnectRequest datatype . 25
Figure 11 – HartConnectResponse datatype . 26
Figure 12 – HartDisconnectRequest datatype . 27
Figure 13 – HartDisconnectResponse datatype . 27
Figure 14 – HartTransactionRequest datatype . 28
Figure 15 – HartTransactionResponse datatype . 28
Figure 16 – HartAbortMessage datatype . 29
Figure 17 – HartSubscribeRequest datatype . 30
Figure 18 – HartSubscribeResponse datatype . 30
Figure 19 – HartUnsubscribeRequest datatype . 31
Figure 20 – HartUnsubscribeResponse datatype . 31
Figure 21 – HartIOSignalInfo datatype . 32
Figure 22 – HartDeviceScanInfo datatype . 33
Figure 23 – HartDeviceIdentInfo datatype . 37

Table 1 – Output signal info within IOSignalInfo / HartIOSignalInfo . 10
Table 2 – Mapping of basic datatypes . 11

– 4 – IEC TR 62453-52-90:2017 © IEC 2017
Table 3 – SemanticInfo attributes description . 12
Table 4 – Basic Variables exported in IDeviceData and IInstanceData interfaces . 13
Table 5 – Basic Variables exported only in IDeviceData interface . 15
Table 6 – Protocol specific usage of general datatypes . 21
Table 7 – HartDeviceAddress datatype . 22
Table 8 – HartDeviceIpAddress datatype . 23
Table 9 – HartDeviceWirelessAddress datatype . 24
Table 10 – HartNetworkData datatype. 24
Table 11 – HartConnectRequest datatype . 25
Table 12 – HartConnectResponse datatype . 26
Table 13 – HartLongAddress datatype . 26
Table 14 – HartDisconnectRequest datatype . 27
Table 15 – HartDisconnectResponse datatype . 27
Table 16 – HartTransactionRequest datatype . 28
Table 17 – HartTransactionResponse datatype . 29
Table 18 – HartStatus datatype . 29
Table 19 – HartAbortMessage datatype . 29
Table 20 – HartSubscribeRequest datatype . 30
Table 21 – HartSubscribeResponse datatype . 30
Table 22 – HartUnsubscribeRequest datatype . 31
Table 23 – HartUnsubscribeResponse datatype . 31
Table 24 – Usage of IOSignalInfo datatype . 32
Table 25 – HartIOSignalInfo datatype . 32
Table 26 – HartDeviceScanInfo datatype . 33
Table 27 – Protocol specific mapping of scan information . 35
Table 28 – HartDeviceIdentInfo datatype . 37
Table 29 – Protocol specific mapping of identity information . 39

IEC TR 62453-52-90:2017 © IEC 2017 – 5 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –

Part 52-90: Communication implementation
for common language infrastructure –
IEC 61784 CPF 9
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.
The main task of IEC technical committees is to prepare International Standards. However, a
technical committee may propose the publication of a technical report when it has collected
data of a different kind from that which is normally published as an International Standard, for
example "state of the art".
IEC TR 62453-52-90, which is a technical report, has been prepared by subcommittee 65E:
Devices and integration in enterprise systems, of IEC technical committee 65: Industrial-
process measurement, control and automation.
Each part of the IEC 62453-52-xy series is intended to be read in conjunction with its
corresponding part in the IEC 62453-3xy series. This document corresponds to
IEC 62453-309.
– 6 – IEC TR 62453-52-90:2017 © IEC 2017
The text of this technical report is based on the following documents:
Enquiry draft Report on voting
65E/440/DTR 65E/514/RVC
Full information on the voting for the approval of this technical report 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.
The list of all parts of the IEC 62453 series, under the general title Field device tool (FDT)
interface specification, 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.
A bilingual version of this publication may be issued at a later date.

IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
IEC TR 62453-52-90:2017 © IEC 2017 – 7 –
INTRODUCTION
This part of IEC 62453 is an interface specification for developers of Field Device Tool (FDT)
components for function control and data access within a client/server architecture. The
specification is a result of an analysis and design process to develop standard interfaces to
facilitate the development of servers and clients by multiple vendors that need to interoperate
seamlessly.
With the integration of fieldbuses into control systems, there are a few other tasks which need
to be performed. In addition to fieldbus- and device-specific tools, there is a need to integrate
these tools into higher-level system-wide planning or engineering tools. In particular, for use
in extensive and heterogeneous control systems, typically in the area of the process industry,
the unambiguous definition of engineering interfaces that are easy to use for all those
involved is of great importance.
A device-specific software component, called Device Type Manager (DTM), is supplied by the
field device manufacturer with its device. The DTM is integrated into engineering tools via the
FDT interfaces defined in this specification. The approach to integration is in general open for
all kind of fieldbusses and thus meets the requirements for integrating different kinds of
devices into heterogeneous control systems.
Figure 1 shows how this part of the IEC TR 62453-52-xy series is aligned in the structure of
the IEC 62453 series.
Part 62453-52-90
implementation
for common
language
infrastructure –
IEC 61784 CPF 9
IEC
Figure 1 – Part 52-90 of the IEC 62453 series

– 8 – IEC TR 62453-52-90:2017 © IEC 2017
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –

Part 52-90: Communication implementation
for common language infrastructure –
IEC 61784 CPF 9
1 Scope
This part of the IEC 62453-52-xy series, which is a Technical Report, provides information for
technology into the CLI-based implementation of FDT interface
integrating the HART®
specification (IEC TR 62453-42).
This part of IEC 62453 specifies implementation of communication and other services based
on IEC 62453-309.
This document neither contains the FDT specification nor modifies it.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their
content constitutes requirements of this document. For dated references, only the edition
cited applies. For undated references, the latest edition of the referenced document (including
any amendments) applies.
IEC 61784-1:2014, Industrial communication networks – Profiles – Part 1: Fieldbus profiles
IEC 62453-1:2016, Field device tool (FDT) interface specification – Part 1: Overview and
guidance
IEC 62453-2:2016, Field device tool (FDT) interface specification – Part 2: Concepts and
detailed description
IEC TR 62453-42:2016, Field device tool (FDT) interface specification – Part 42: Object model
integration profile – Common language infrastructure
IEC 62453-309:2016, Field device tool (FDT) interface specification – Part 309:
Communication profile integration – IEC 61784 CPF 9
3 Terms, definitions, symbols, abbreviated terms and conventions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62453-1,
IEC 62453-2, IEC TR 62453-42 and IEC 62453-309 apply.
___________
HART ® is the trade name of a product supplied by HART Communication Foundation. This information is given
for 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.

IEC TR 62453-52-90:2017 © IEC 2017 – 9 –
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 Symbols and abbreviated terms
For the purposes of this document, the symbols and abbreviations given in IEC 62453-1,
IEC 62453-2, IEC 62453-309, and IEC TR 62453-42 apply.
3.3 Conventions
3.3.1 Datatype names and references to datatypes
The conventions for naming and referencing of datatypes are explained in IEC 62453-2:2016,
Clause A.1.
3.3.2 Vocabulary for requirements
The following expressions are used when specifying requirements.
Usage of “shall” or “mandatory” No exceptions allowed.
Usage of “should” or “recommended” Strong recommendation. It may make sense
in special exceptional cases to differ from
the described behaviour.
Usage of “can” or “optional” Function or behaviour may be provided,
depending on defined conditions.
3.3.3 Use of UML
Figures in this document are using UML notation as defined in Annex A of IEC 62453-1:2016.
4 Bus category
IEC 61784 CPF 9 protocol is identified in the attribute busCategory of the BusCategory
element by the identifiers, as specified in IEC 62453-309.
5 Access to instance and device data
5.1 General
Used at interfaces:
• IInstanceData
• IDeviceData
These interfaces shall provide access to at least all parameters defined in IEC 62453-309.
5.2 IO signals provided by DTM
A DTM shall provide IO signal information of the device using the IProcessData interface.
To provide all information required to access the output signal information the DTM shall
provide the information shown in Table 1 within its HartIOSignalInfo.

– 10 – IEC TR 62453-52-90:2017 © IEC 2017
Table 1 – Output signal info within IOSignalInfo / HartIOSignalInfo
Attribute Description
Name Name of the IO signal
Range Reference to the variables providing range information
Unit Reference to an enumeration variable describing the
unit information
DeviceVariableAssignment Constant enumeration value that can take following
values
– unassigned: The IO signal is not assigned to
dynamic variable and can only be accessed using
the indexed approach (reading device variables).
– PV: IO signal assigned to the PV dynamic variable
– SV: IO signal assigned to the SV dynamic variable
– TV: IO signal assigned to the TV dynamic variable
– QV: IO signal assigned to the QV dynamic variable
DeviceVariableCode Constant that specifies the device specific variable
code (see [7] Table 34). Because of compatibility
reasons to other FDT versions (e.g.
IEC TR 62453-41), this variable could be set to the
value 252 that stands for “unknown”.

5.3 Data interfaces
5.3.1 General
Within HART, several command sets are defined. As part of the command set definition,
HART provides a precise naming convention that is documented within the sources of the
standard EDD libraries. The data provided by the access data interfaces should be named
according to the HART naming convention. For backward compatibility, the semantic IDs as
defined in previous versions of FDT should also be provided by the DTM.
A DTM shall provide all device data that is related to the set of Universal Commands and
should provide all device data related to Common Practice CommandsIf the device supports
additional command sets, like device family profiles, those data should also be exported using
the naming convention as defined in the HART EDD libraries and as shown in Figure 2 and
Figure 3.
5.3.2 Mapping HART datatypes to FDT datatypes
For a better usability of data provided by the data access interfaces IDeviceData and
IInstanceData, all data from the device shall be converted into datatypes that are common to
FDT. The mapping of basic datatypes is defined in Table 2.
___________
Figures in square brackets refer to the Bibliography.

IEC TR 62453-52-90:2017 © IEC 2017 – 11 –
Table 2 – Mapping of basic datatypes
HART Datatypes FDT datatype IEC datatype
Packed ASCII (see [10] 5.1.1) String STRING
ISO Latin-1 (see [10] 5.1.2) String STRING
Dates (see [10] 5.2) DateTime DATE_AND_TIME
Time (see [10] 5.3) ULong (1/32 ms since ULINT (1/32 ms since
midnight) midnight)
Single Precision Floating Point (see [10] 5.4) float REAL
Double Precision Floating Point (see [10] 5.4) double LREAL
1-4 Byte Unsigned Integer (see [10] 5.5) UInt UDINT
5-8 Byte Unsigned Integer (see [10] 5.5) ULong ULINT
1-4 Byte Unsigned Integer (see [10] 5.5) UInt UDINT
5-8 Byte Unsigned Integer (see [10] 5.5) ULong ULINT
1-4 Byte Enumerated (see [10] 5.7.1) UInt UDINT
5-8 Byte Enumerated (see [10] 5. 7.1) ULong ULINT
1-4 Byte Bit Fields (see [10] 5.7.2) UInt UDINT
5-8 Byte Bit Fields (see [10] 5.7.2) ULong ULINT

HCF standardized the access to device specific data using structures with the standard EDD
import libraries for HART. The structure uses ARRAY and COLLECTION constructs that shall
be reused when exposing data within FDT in IDeviceData and IInstanceData interfaces with
elements of type StructDataGroup.
When converting a COLLECTION into a StructDataGroup, the DataItems shall be identical to
the COLLECTION members with:
DataItem Name = COLLECTION member identifier
DataItem Label = COLLECTION member label
When converting an ARRAY into a StructDataGroup, the DataItem shall be identical to the
ARRAY element with:
DataItem Name = ARRAY element index as string
DataItem Label = ARRAY element label
An example for such a structure is presented in Figure 2 and Figure 3.
5.3.3 SemanticInfo
The SemanticInfo for HART protocol related parameters is directly related to the protocol
specification. The definition of the HART commands is the base for the parameter address
information which shall be used in the properties ParameterReadAddress,
ParameterWriteAddress and SemanticId of the SemanticInfo datatype.
The syntax of the parameter address information is as follows:
CMD[Q()]BBL
The [Q()] portion only is required to define request data.
For description of the attributes, please view Table 3.

– 12 – IEC TR 62453-52-90:2017 © IEC 2017
Table 3 – SemanticInfo attributes description
Attribute Datatype Description
decimal integer command number in the range of 0 to 255
hex-string request data bytes
decimal integer index of the start byte in the response data section (start index = 0)
decimal integer index of the start bit in the byte referenced by
decimal integer length of the value in bits

According to 6.4, commands with extended command number shall be described using
“CMD31Q…” wherein the first two byte of the request data section shall contain the
extended command number.
The property SemanticInfo.ApplicationDomain shall contain ‘FDT_HART’ for all parameters in
Table 4 and Table 5.
5.3.4 Data exposure using IDeviceData and IInstanceData interfaces
5.3.4.1 Export of basic device parameters
Using the HART datatype mapping rules introduced in the preceding sections basic device
parameters defined within the Universal and Common Practice Command sets can be
exported.
Basic parameters that are not accessed using index information in the request part should for
compatibility reasons provide additionally the SemanticInfo information specified in previous
versions of FDT. Variables are identified by their standard identifier in HART. In Table 4, all
variables are listed that shall be exported in the related data interfaces when supported by the
device. HART identifier shall be assigned to the property Data.Id.
Variables with identifiers starting with “PV.”, ”SV.”, ”TV.” and ”QV.” shall be seen as short cuts
to variables that shall be available too, using the structured exposure of device variables as
defined in 5.3.4.2.1.
IEC TR 62453-52-90:2017 © IEC 2017 – 13 –
Table 4 – Basic Variables exported in IDeviceData and IInstanceData interfaces
Identifier SemanticInfo Description
device_type CMD0B1B0L16 Expanded Device Type (see [7], subsection 5.1 and [5],
section 6).
NOTE The information from CMD0 is also available
via IHardwareIdentification interface.
request_preambles CMD0B3B0L8 Minimum number of Preambles required for the request
message from the Master to the Slave. This number
includes the two preambles used in asynchronous
Physical Layers (along with the Delimiter) to detect the
start of message.
universal_revision CMD0B4B0L8 HART Protocol Major Revision Number implemented by
this device. For HART Revision 7, this value shall be
the number 7.
transmitter_revision CMD0B5B0L8 Device Revision Level (refer to the HCF Command
Summary Specification)
software_revision CMD0B6B0L8 Software Revision Level of this device. Levels 254 and
255 are reserved.
hardware_revision CMD0B7B3L5 (Most Significant 5 Bits) Hardware Revision Level of
the electronics in this particular device. Does Not
Necessarily Trace Individual Component Changes.
Level 31 is Reserved.
physical_signaling_code CMD0B7B0L3 (Least Significant 3 Bits) Physical Signaling Code (see
[7], subsection 5.10)
device_flags CMD0B8B0L8 Flags (see [7], subsection 5.11)
device_id CMD0B9B0L24 Device ID. This number shall be different for every
device manufactured with a given Device Type.
response_preambles CMD0B12B0L8 Minimum number of preambles to be sent with the
response message from the slave to the master.
max_num_device_variables CMD0B13B0L8 Maximum Number of Device Variables. This indicates
the last Device Variable code that a host application
should expect to be found in the field device (e.g.,
when identifying the Device Variables using Command
54).
config_change_counter CMD0B14B0L16 Configuration Change Counter
extended_fld_device_status CMD0B16B0L8 Extended Field Device Status (see [7], subsection
5.17)
manufacturer_id CMD0B17B0L16 Manufacturer Identification Code (see [7], subsection
5.8)
private_label_distributor CMD0B19B0L16 Private Label Distributor Code (see [7], subsection 5.8)
device_profile CMD0B21B0L8 Device Profile (see [7], subsection 5.57)
polling_address CMD7B0B0L8 Polling Address of Device (refer to [13], subsection
5.3.4)
loop_current_mode CMD7B1B0L8 Loop Current Mode (see [7], subsection 5.16)
message CMD12B0B0L192 Message
tag CMD13B0B0L48 Tag
descriptor CMD13B6B0L96 Descriptor
date CMD13B18B0L24 Date Code
PV.SENSOR_SERIAL_NUMBER CMD14B0B0L24 Transducer Serial Number
PV.DIGITAL_UNITS CMD14B3B0L8 Transducer Limits and Minimum Span Units Code
(refer to [7], subsection 5.2)
PV.UPPER_SENSOR_LIMIT CMD14B4B0L32 Upper Transducer Limit
PV.LOWER_SENSOR_LIMIT CMD14B8B0L32 Lower Transducer Limit
PV.MINIMUM_SPAN CMD14B12B0L32 Minimum Span

– 14 – IEC TR 62453-52-90:2017 © IEC 2017
Identifier SemanticInfo Description
PV.ALARM_CODE CMD15B0B0L8 PV Alarm Selection Code (see [7], subsection 5.6). The
Alarm Selection Code indicates the action taken by the
device under error conditions. For transmitters, the
code indicates the action taken by the Loop Current.
For Actuators, the action taken by the positioner is
indicated.
PV.TRANSFER_FUNCTION CMD15B1B0L8 PV Transfer Function Code (see [7], subsection 5.3).
The Transfer Function Code shall return "0", Linear, if
transfer functions are not supported by the device.
PV.RANGE_UNITS CMD15B2B0L8 PV Upper and Lower Range Values Units Code (refer
to [7], subsection 5.2)
PV.UPPER_RANGE_VALUE CMD15B3B0L32 PV Upper Range Value
PV.LOWER_RANGE_VALUE CMD15B7B0L32 PV Lower Range Value
PV.DAMPING_VALUE CMD15B11B0L32 PV Damping Value (units of seconds)
write_protect CMD15B15B0L8 Write Protect Code (see [7], subsection 5.7). The Write
Protect Code shall return "251", None, when write
protect is not implemented by a device.
PV.ANALOG_CHANNEL_FLAGS CMD15B17B0L8 PV Analog Channel Flags (see [7], subsection 5.26)
final_assembly_number CMD16B0B0L24 Final Assembly Number
longTag CMD20B0B0L256 Long Tag
PV.DIGITAL_UNITS CMD1B0B0L8 Primary Variable Units (refer to [7], subsection 5.2)
SV.DIGITAL_UNITS CMD3B9B0L8 Secondary Variable Units Code (refer to [7], subsection
5.2)
TV.DIGITAL_UNITS CMD3B14B0L8 Tertiary Variable Units Code (refer to [7], subsection
5.2)
QV.DIGITAL_UNITS CMD3B19B0L8 Quaternary Variable Units Code (refer to [7],
subsection 5.2)
PV.CLASSIFICATION CMD8B0B0L8 Primary Variable Classification (refer to [7], subsection
5.21)
SV.CLASSIFICATION CMD8B1B0L8 Secondary Variable Classification (refer to [7],
subsection 5.21)
TV.CLASSIFICATION CMD8B2B0L8 Tertiary Variable Classification (refer to [7], subsection
5.21)
QV.CLASSIFICATION CMD8B3B0L8 Quaternary Variable Classification (refer to [7],
subsection 5.21)
lock_device_status_code CMD76B0B0L8 Lock Status (see HCF Common Table 25, Lock Device
Status)
last_clock_date, CMD90B8B0L24 Date clock last set
last_clock_time CMD90B11B0L32 Time clock last set
real_time_clock_flag CMD90B15B0L8 RTC Flags (refer to [7], subsection 5.42)

Table 4 contains data that can also be read via other interfaces. In this case, the DTM shall
take care about the consistency of the data. E.g. the variables which are related to CMD0
shall be identical to the HartDeviceScanInfo data, which can be read via the IHardwareScan
interface.
Table 5 lists all basic device variables that shall be exported only within IDeviceData interface
if supported by the device.
IEC TR 62453-52-90:2017 © IEC 2017 – 15 –
Table 5 – Basic Variables exported only in IDeviceData interface
Identifier Semantic Info Description
device_status -/- Device status information transferred with each reply. Due to the
(empty) fact that device_status is accessible by standard means in each
transaction, the semantic info is empty
PV.DIGITAL_VALUE CMD1B1B0L32 Primary Variable
PV.ANALOG_VALUE CMD2B0B0L32 Primary Variable Loop Current (units of milli amperes)
PV.PERCENT_RANGE CMD2B4B0L32 Primary Variable Percent of Range (units of percent)
PV.DIGITAL_VALUE CMD3B5B0L32 Primary Variable
SV.DIGITAL_VALUE CMD3B10B0L32 Secondary Variable
TV.DIGITAL_VALUE CMD3B15B0L32 Tertiary Variable
QV.DIGITAL_VALUE CMD3B20B0L32 Quaternary Variable
current_date
...