Field device tool (DFT) interface specification - Part 309: Communication profile integration - IEC 61784 CPF 9

Communication Profile Family 9 (commonly known as HART®1) defines communication profiles based on IEC 61158-5-20 and IEC 61158-6-20. The basic profile CP 9/1 is defined in IEC 61784-1.
This part of IEC 62453 provides information for integrating the HART® technology into the FDT standard (IEC 62453-2).
This part of the IEC 62453 specifies communication and other services.
This standard neither contains the FDT specification nor modifies it.

Spécification des interfaces des outils des dispositifs de terrain - Partie 309: Intégration des profils de communication - CPF 9 de l'IEC 61784

Specifikacija vmesnika orodja procesne naprave - 309. del: Integracija komunikacijskih profilov - IEC 61784 CPF 9

General Information

Status
Not Published
Public Enquiry End Date
29-Sep-2021
Current Stage
5020 - Formal vote (FV) (Adopted Project)
Start Date
23-Jun-2022
Due Date
11-Aug-2022

RELATIONS

Buy Standard

Draft
oSIST prEN IEC 62453-309:2021 - BARVE na PDF-str 9,19
English language
49 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
oSIST prEN IEC 62453-309:2021
01-september-2021
Specifikacija vmesnika orodja procesne naprave - 309. del: Integracija
komunikacijskih profilov - IEC 61784 CPF 9

Field device tool (DFT) interface specification - Part 309: Communication profile

integration - IEC 61784 CPF 9

Spécification des interfaces des outils des dispositifs de terrain - Partie 309: Intégration

des profils de communication - CPF 9 de l'IEC 61784
Ta slovenski standard je istoveten z: prEN IEC 62453-309:2021
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
oSIST prEN IEC 62453-309:2021 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
oSIST prEN IEC 62453-309:2021
---------------------- Page: 2 ----------------------
oSIST prEN IEC 62453-309:2021
65E/785/CDV
COMMITTEE DRAFT FOR VOTE (CDV)
PROJECT NUMBER:
IEC 62453-309 ED3
DATE OF CIRCULATION: CLOSING DATE FOR VOTING:
2021-07-09 2021-10-01
SUPERSEDES DOCUMENTS:
65E/749/RR
IEC SC 65E : DEVICES AND INTEGRATION IN ENTERPRISE SYSTEMS
SECRETARIAT: SECRETARY:
United States of America Mr Donald (Bob) Lattimer
OF INTEREST TO THE FOLLOWING COMMITTEES: PROPOSED HORIZONTAL STANDARD:
SC 65C
Other TC/SCs are requested to indicate their interest, if
any, in this CDV to the secretary.
FUNCTIONS CONCERNED:
EMC ENVIRONMENT QUALITY ASSURANCE SAFETY

SUBMITTED FOR CENELEC PARALLEL VOTING NOT SUBMITTED FOR CENELEC PARALLEL VOTING

Attention IEC-CENELEC parallel voting
The attention of IEC National Committees, members of
CENELEC, is drawn to the fact that this Committee Draft
for Vote (CDV) is submitted for parallel voting.
The CENELEC members are invited to vote through the
CENELEC online voting system.

This document is still under study and subject to change. It should not be used for reference purposes.

Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of

which they are aware and to provide supporting documentation.
TITLE:

Field device tool (DFT) interface specification - Part 309: Communication profile integration - IEC

61784 CPF 9
PROPOSED STABILITY DATE: 2025
NOTE FROM TC/SC OFFICERS:

Copyright © 2021 International Electrotechnical Commission, IEC. All rights reserved. It is permitted to download this

electronic file, to make a copy and to print out the content for the sole purpose of preparing National Committee positions.

You may not copy or "mirror" the file or printed version of the document, or any part of it, for any other purpose without

permission in writing from IEC.
---------------------- Page: 3 ----------------------
oSIST prEN IEC 62453-309:2021
– 2 – IEC CDV 62453-309  IEC 2021
CONTENTS

CONTENTS ........................................................................................................................2

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 Abbreviated terms ...............................................................................................9

3.3 Conventions ........................................................................................................9

3.3.1 Data type names and references to data types...............................................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 ............................................................................ 11

5.1 General ............................................................................................................ 11

5.2 Process Channel objects provided by DTM ......................................................... 11

5.3 DTM services to access instance and device data ............................................... 12

6 Protocol-specific behavior .......................................................................................... 12

6.1 Overview .......................................................................................................... 12

6.2 Burst mode subscription .................................................................................... 12

6.3 Usage of device addressing information ............................................................. 13

6.4 Extended Command Numbers ............................................................................ 14

6.5 Handling of communication failures and time-outs ............................................... 14

6.6 Handling of Delayed Responses ......................................................................... 14

6.7 Topologies with mixed HART protocols ............................................................... 16

6.7.1 General ..................................................................................................... 16

6.7.2 Behavior of DTMs supporting ‘Extended_HART’ only.................................... 16

6.7.3 Behavior of DTMs supporting ‘Extended_HART’ and ‘HART_Basic’ ............... 16

6.7.4 Behavior of DTMs that require ‘Extended_HART’ or ‘HART_Basic’ ................ 17

6.8 Nested communication with multiple gateways .................................................... 18

6.9 Communication- and network structures in WirelessHART ................................... 18

6.9.1 General ..................................................................................................... 18

6.9.2 Network topology........................................................................................ 19

7 Protocol-specific usage of general data types.............................................................. 21

8 Protocol-specific common data types .......................................................................... 22

9 Network management data types ................................................................................ 22

9.1 General ............................................................................................................ 22

9.2 Addressing modes ............................................................................................. 22

9.3 Address information........................................................................................... 23

9.4 Additional address information for ‘Extended HART’ protocols ............................. 23

10 Communication data types ......................................................................................... 25

10.1 General ............................................................................................................ 25

10.2 Protocol-specific Addressing Information ............................................................ 26

10.3 Datatype definitions ........................................................................................... 26

11 Channel parameter data types .................................................................................... 30

---------------------- Page: 4 ----------------------
oSIST prEN IEC 62453-309:2021
IEC CDV 62453-309  IEC 2021 – 3 –

12 Device identification ................................................................................................... 33

12.1 Protocol-specific handling of data type STRING .................................................. 33

12.2 Address Range for Scan .................................................................................... 33

12.3 Support for Extended Manufacturer and Device Type Code ................................. 33

12.4 Device type identification data types for protocol ‘HART_Basic’ ........................... 33

12.5 Common device type identification data types for ‘Extended_HART’

protocols ........................................................................................................... 37

12.6 Topology scan data types .................................................................................. 42

12.7 Scan identification data types for protocol ‘HART_Basic’ ..................................... 43

12.8 Scan identification data types for ‘Extended_HART’ protocols.............................. 45

12.9 Device type identification data types – provided by DTM ..................................... 47

Bibliography ..................................................................................................................... 49

Figure 1 – Part 309 of the IEC 62453 series .........................................................................7

Figure 2 – Burst mode subscription .................................................................................... 13

Figure 3 – Handling of Delayed Reponses (scenario 1) ....................................................... 15

Figure 4 – Handling of Delayed Reponses (scenario 2) ....................................................... 15

Figure 5 – Behavior of DTMs supporting ‘Extended_HART’ and ‘HART_Basic’ ..................... 17

Figure 6 – Behavior of DTMs requires ‘Extended_HART’ or ‘HART_Basic’ ........................... 18

Figure 7 – Host connected to a WirelessHART gateway device ........................................... 19

Figure 8 – FDT Topology of a WirelessHART network......................................................... 20

Figure 9 – Host connected to HART FSK ........................................................................... 20

Figure 10 – FDT Topology when directly connected to a WirelessHART adapter device ....... 21

Table 1 – Protocol identifiers ...............................................................................................9

Table 2 – Definition of PhysicalLayer ................................................................................. 10

Table 3 – Protocol specific usage of general data types ...................................................... 22

Table 4 – Relation of ProtocolId and supported features ..................................................... 23

Table 5 – Simple address information data types ................................................................ 24

Table 6 – Structured address information data types .......................................................... 25

Table 7 – Simple communication data types ....................................................................... 26

Table 8 – Structured communication data types ................................................................. 27

Table 9 – Simple channel parameter data types ................................................................. 31

Table 10 – Structured channel parameter data types .......................................................... 31

Table 11 – Address range for device identification .............................................................. 33

Table 12 – Identification data types with protocol-specific mapping for protocol

‘HART_Basic’ ................................................................................................................... 34

Table 13 – Identification data types with semantics for protocol ‘HART_Basic’ ..................... 36

Table 14 – Simple identification data types for protocol ‘HART_Basic’ with protocol

independent semantics ..................................................................................................... 37

Table 15 – Structured identification data types for protocol ‘HART_Basic’ with protocol

independent semantics ..................................................................................................... 37

Table 16 – Identification data types for ‘Extended_HART’ protocols with protocol-

specific mapping ............................................................................................................... 38

Table 17 – Identification data types for ‘Extended_HART’ protocols without protocol

independent semantics ..................................................................................................... 41

---------------------- Page: 5 ----------------------
oSIST prEN IEC 62453-309:2021
– 4 – IEC CDV 62453-309  IEC 2021
Table 18 – Simple identification data types for ‘Extended_HART’ protocols with

protocol independent semantics ........................................................................................ 42

Table 19 – Structured identification data types for ‘Extended_HART’ protocols with

protocol independent semantics ........................................................................................ 42

Table 20 – Structured device type identification data types ................................................. 43

Table 21 – Simple scan identification data types for protocol ‘HART_Basic’ ......................... 43

Table 22 – Structured scan identification data types for protocol ‘HART_Basic’ .................... 43

Table 23 – Simple scan identification data types for ‘Extended_HART’ protocols ................. 45

Table 24 – Structured scan identification data types for ‘Extended_HART’ protocols ............ 45

Table 25 – Structured device type identification data types ................................................. 47

---------------------- Page: 6 ----------------------
oSIST prEN IEC 62453-309:2021
IEC CDV 62453-309  IEC 2021 – 5 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –
Part 309: Communication profile integration –
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.

International Standard IEC 62453-309 has been prepared by subcommittee 65E: Devices and

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

measurement, control and automation.

This third edition cancels and replaces the second edition published in 2016, and constitutes

a technical revision. The main changes are clarifications and corrections.

Each part of the IEC 62453-3xy series is intended to be read in conjunction with IEC 62453-2.

---------------------- Page: 7 ----------------------
oSIST prEN IEC 62453-309:2021
– 6 – IEC CDV 62453-309  IEC 2021
The text of this standard is based on the following documents:
CDV Report on voting
- -

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

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 ----------------------
oSIST prEN IEC 62453-309:2021
IEC CDV 62453-309  IEC 2021 – 7 –
INTRODUCTION

This part of IEC 62453 is an interface specification for developers of FDT (Field Device Tool)

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 fieldbusses 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 DTM (Device Type Manager), 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 IEC 62453-309 is aligned in the structure of the IEC 62453 series.

Part 309
Communication
profile integration -
IEC 61784 CPF 9
IEC
Figure 1 – Part 309 of the IEC 62453 series
---------------------- Page: 9 ----------------------
oSIST prEN IEC 62453-309:2021
– 8 – IEC CDV 62453-309  IEC 2021
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –
Part 309: Communication profile integration –
IEC 61784 CPF 9
1 Scope
Communication Profile Family 9 (commonly known as HART® ) defines communication

profiles based on IEC 61158-5-20 and IEC 61158-6-20. The basic profile CP 9/1 is defined in

IEC 61784-1.

This part of IEC 62453 provides information for integrating the HART® technology into the

FDT standard (IEC 62453-2).
This part of the IEC 62453 specifies communication and other services.
This standard neither contains the FDT specification nor modifies it.
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 61158-5-20, Industrial communication networks – Fieldbus specifications – Part 5-20:

Application layer service definition – Type 20 elements

IEC 61158-6-20, Industrial communication networks – Fieldbus specifications – Part 6-20:

Application layer protocol specification – Type 20 elements

IEC 61784-1, Industrial communication networks – Profiles – Part 1: Fieldbus profiles

IEC 62453-1:– , Field device tool (FDT) interface specification – Part 1: Overview and

guidance

IEC 62453-2:– , Field device tool (FDT) interface specification – Part 2: Concepts and

detailed description
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 and

IEC 62453-2, as well as the following apply.
—————————

HART® and WirelessHART® are trade names of products supplied by FieldComm Group. 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.

To be published concurrently with this standard.
---------------------- Page: 10 ----------------------
oSIST prEN IEC 62453-309:2021
IEC CDV 62453-309  IEC 2021 – 9 –
3.1.1
burst mode

mode in which the field device generates response telegrams without request telegram from

the master
3.2 Abbreviated terms

For the purposes of this document, the abbreviations given in IEC 62453-1, IEC 62453-2, as

well as the following apply.
BACK Burst ACKnowledge
C8PSK Coherent 8-way Phase Shift Keying,
HART communication layer as defined in HCF_SPEC-60, Revision 1.0
DR Delayed Response
EDD Electronic Device Description
FSK Frequency Shift Keying,
HART communication layer as defined in HCF_SPEC-54, Revision 8.1
HART Highway Addressable Remote Transducer
3.3 Conventions
3.3.1 Data type names and references to data types

The conventions for naming and referencing of data types are explained in IEC 62453-2:–,

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 Strong recommendation. It may make sense in
“recommended” special exceptional cases to differ from the
described behaviour.
Function or behaviour may be provided,
Usage of “can’ or “optional’
depending on defined conditions.
3.3.3 Use of UML

Figures in this document are using UML notation as defined in IEC 62453-1:–, Annex A.

4 Bus category

IEC 61784 CPF 9 protocol is identified in the protocolId element of structured data type

'fdt:BusCategory' by the following unique identifiers (see Table 1):
Table 1 – Protocol identifiers
Identifier value ProtocolId Display String Description
036D1498-387B-11D4-86E1- HART_Basic ‘HART’ Support of IEC 61784 CPF 9
protocol over FSK communication
00E0987270B9
with basic functionality
(deprecated)
98503B8F-0FFB-4EB7-BB67- HART_FSK ‘HART FSK’ Support of HART protocol over
F4D6BD16DB8D FSK communication with complete
functionality
---------------------- Page: 11 ----------------------
oSIST prEN IEC 62453-309:2021
– 10 – IEC CDV 62453-309  IEC 2021
Identifier value ProtocolId Display String Description

74D29D22-F752-40EF-A747- HART_Wireless ‘HART Wireless’ Support of WirelessHART protocol

ACA72C791155
58001A08-C178-4A59-A76B- HART_RS485 ‘HART RS485’ Support of HART protocol over
9EF9111CB83D RS485 communication

EF708CB7-A2A1-42AF-890C- HART_Infrared ‘HART Infrared’ Support of HART protocol over

15CEB680CC12 Infrared communication
D122D172-F0C7-4B03-965B- HART_IP ‘HART IP’ Support of HART over IP protocol
512CD4C0871E

The ‘HART_Basic’ protocol is maintained for backward compatibility only (e.g. for interaction

with DTMs according to IEC 62453-309 Ed.1.0). The other protocol identifiers provide a better

support for planning of network topologies and for establishment of connections between DTM

and respective device. For DTMs complying with this document support for one of the other

protocols is mandatory.
Within this document the other protocols (HART_FSK, HART_Wireless, HART_RS485,

HART_Infrared, HART_IP) are referenced as ‘Extended_HART’ protocols. (E.g. for definitions

that apply to all protocols except ‘HART_Basic’.)

Table 2 defines which PhysicalLayer can be used together with the BusCategory defined in

Table 1.
Table 2 – Definition of PhysicalLayer
PhysicalLayer Id value PhysicalLayer name value Description
BAB2091A-C0A7-4614-B9DE- HART FSK Physical Layer Support of HART FSK physical
FCC2709DCF5D layer

B9F1A250-AC94-4487-8F25-A8F3F8F89DC5 WirelessHART Physical Support of WirelessHART

Layer physical layer

036D1591-387B-11D4-86E1-00E0987270B9 HART RS-485 Physical Layer Support of HART devices using

RS-485 communication

AE4119EF-B9FD-429c-B244-134DB182296A HART Infrared Physical Support of HART devices using

Layer infrared communication
307dd808-c010-11db-90e7-0002b3ecdcbe 10BASET HART Ethernet based Physical
Layers
307dd809-c010-11db-90e7-0002b3ecdcbe 10BASETXHD
307dd80a-c010-11db-90e7-0002b3ecdcbe 10BASETXFD
307dd80b-c010-11db-90e7-0002b3ecdcbe 10BASEFLHD
307dd80c-c010-11db-90e7-0002b3ecdcbe 10BASEFLFD
307dd80d-c010-11db-90e7-0002b3ecdcbe 10BASEFXHD
307dd80e-c010-11db-90e7-0002b3ecdcbe 10BASEFXFD
307dd80f-c010-11db-90e7-0002b3ecdcbe 100BASETXHD
307dd810-c010-11db-90e7-0002b3ecdcbe 100BASETXFD
307dd811-c010-11db-90e7-0002b3ecdcbe 100BASEFXHD
307dd812-c010-11db-90e7-0002b3ecdcbe 100BASEFXFD
307dd813-c010-11db-90e7-0002b3ecdcbe 100BASELX10
307dd814-c010-11db-90e7-0002b3ecdcbe 100BASEPX10
307dd815-c010-11db-90e7-0002b3ecdcbe 1000BASEXHD
307dd816-c010-11db-90e7-0002b3ecdcbe 1000BASEXFD
307dd817-c010-11db-90e7-0002b3ecdcbe 1000BASELXHD
307dd818-c010-11db-90e7-0002b3ecdcbe 1000BASELXFD
307dd819-c010-11db-90e7-0002b3ecdcbe 1000BASESXHD
---------------------- Page: 12 ----------------------
oSIST prEN IEC 62453-309:2021
IEC CDV 62453-309  IEC 2021 – 11 –
PhysicalLayer Id value PhysicalLayer name value Description
307dd81a-c010-11db-90e7-0002b3ecdcbe 1000BASESXFD
307dd81b-c010-11db-90e7-0002b3ecdcbe 1000BASETHD
307dd81c-c010-11db-90e7-0002b3ecdcbe 1000BASETFD
307dd81d-c010-11db-90e7-0002b3ecdcbe 10GigBASEFX

The significant information for topology planning is the BusCategory. The PhysicalLayer

(which is provided in the BusInformation data type) shall be used only for additional

information.
The DataLinkLayer property is not applicable for HART and shall be set to null.
5 Access to instance and device data
5.1 General

The HART protocol has semantics defined that allow in a wide range the identification of

device variables and device parameters. Most of this semantic information is defined in the

standard EDD import libraries.

Clause 5 describes how the semantic information defined with the HART protocol shall be

used to export device data, instance data and process data.
5.2 Process Channel objects provided by DTM
The minimum set of provided data shall be:

• the first four provided process related values (PV, SV, …) – if available – are modeled as

channel references. The referenced channel shall include ranges and scaling.

A HART device communicates the process data either via its analogue channels or via digital

information (e.g. by request or by burst mode). Analogue channels are always related to a

dynamic variable, as specified in [3] chapter 8 and therefore the description of an analogue

channel has to be accessed using the respective dynamic variable (e.g. the attributes of

dynamic variable PV always describe the first analogue channel).
HART distinguishes between three metho
...

Questions, Comments and Discussion

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