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(E) which is a Technical Report, provides information for integrating the HART® technology into the CLI-based implementation of FDT interface 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.

General Information

Status
Published
Publication Date
15-Jun-2017
Current Stage
PPUB - Publication issued
Start Date
16-Jun-2017
Completion Date
16-Jun-2017
Ref Project

Buy Standard

Technical report
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
English language
41 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

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
IEC TR 62453-52-90:2017-06(en)
---------------------- Page: 1 ----------------------
THIS PUBLICATION IS COPYRIGHT PROTECTED
Copyright © 2017 IEC, Geneva, Switzerland

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form

or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from

either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC

copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or

your local IEC member National Committee for further information.
IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé Fax: +41 22 919 03 00
CH-1211 Geneva 20 info@iec.ch
Switzerland www.iec.ch
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 corrigenda or an amendment might have been published.
IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org

The stand-alone application for consulting the entire The world's leading online dictionary of electronic and

bibliographical information on IEC International Standards, electrical terms containing 20 000 terms and definitions in

Technical Specifications, Technical Reports and other English and French, with equivalent terms in 16 additional

documents. Available for PC, Mac OS, Android Tablets and languages. Also known as the International Electrotechnical

iPad. Vocabulary (IEV) online.

IEC publications search - www.iec.ch/searchpub IEC Glossary - std.iec.ch/glossary

The advanced search enables to find IEC publications by a 65 000 electrotechnical terminology entries in English and

variety of criteria (reference number, text, technical French extracted from the Terms and Definitions clause of

committee,…). It also gives information on projects, replaced IEC publications issued since 2002. Some entries have been

and withdrawn publications. collected from earlier publications of IEC TC 37, 77, 86 and

CISPR.
IEC Just Published - webstore.iec.ch/justpublished

Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc

details all new publications released. Available online and If you wish to give us your feedback on this publication or

also once a month by email. need further assistance, please contact the Customer Service

Centre: csc@iec.ch.
---------------------- Page: 2 ----------------------
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

Warning! Make sure that you obtained this publication from an authorized distributor.

® Registered trademark of the International Electrotechnical Commission
---------------------- Page: 3 ----------------------
– 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

---------------------- Page: 4 ----------------------
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

---------------------- Page: 5 ----------------------
– 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

---------------------- Page: 6 ----------------------
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.
---------------------- Page: 7 ----------------------
– 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.
---------------------- Page: 8 ----------------------
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
---------------------- Page: 9 ----------------------
– 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.

---------------------- Page: 10 ----------------------
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.
---------------------- Page: 11 ----------------------
– 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
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.