Shopping Cart

No products in the cart.

BS EN 62453-309:2017:2018 Edition

$198.66

Field device tool (DFT) interface specification – Communication profile integration. IEC 61784 CPF 9

Published By Publication Date Number of Pages
BSI 2018 56
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

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.

PDF Catalog

PDF Pages PDF Title
2 undefined
7 English
CONTENTS
10 FOREWORD
12 INTRODUCTION
Figures
Figure 1 – Part 309 of the IEC 62453 series
13 1 Scope
2 Normative references
3 Terms, definitions, symbols, abbreviated terms and conventions
3.1 Terms and definitions
14 3.2 Abbreviated terms
3.3 Conventions
3.3.1 Data type names and references to data types
3.3.2 Vocabulary for requirements
3.3.3 Use of UML
4 Bus category
Tables
Table 1 – Protocol identifiers
15 Table 2 – Definition of PhysicalLayer
16 5 Access to instance and device data
5.1 General
5.2 Process Channel objects provided by DTM
17 5.3 DTM services to access instance and device data
6 Protocol-specific behavior
6.1 Overview
6.2 Burst mode subscription
18 6.3 Usage of device addressing information
Figure 2 – Burst mode subscription
19 6.4 Extended Command Numbers
6.5 Handling of communication failures and time-outs
6.6 Handling of Delayed Responses
20 Figure 3 – Handling of Delayed Reponses (scenario 1)
Figure 4 – Handling of Delayed Reponses (scenario 2)
21 6.7 Topologies with mixed HART protocols
6.7.1 General
6.7.2 Behavior of DTMs supporting ‘Extended_HART’ only
6.7.3 Behavior of DTMs supporting ‘Extended_HART’ and ‘HART’
22 6.7.4 Behavior of DTMs that requires ‘Extended_HART’ or ‘HART’
Figure 5 – Behavior of DTMs supporting ‘Extended_HART’ and ‘HART’
23 6.8 Nested communication with multiple gateways
6.9 Communication- and network structures in WirelessHART
6.9.1 General
Figure 6 – Behavior of DTMs requires ‘Extended_HART’ or ‘HART’
24 6.9.2 Network topology
Figure 7 – Host connected to a WirelessHART gateway device
25 Figure 8 – FDT Topology of a WirelessHART network
Figure 9 – Host connected to HART FSK
26 7 Protocol-specific usage of general data types
Figure 10 – FDT Topology when directly connected to a WirelessHART adapter device
27 8 Protocol-specific common data types
9 Network management data types
9.1 General
9.2 Addressing modes
Table 3 – Protocol specific usage of general data types
28 9.3 Address information
9.4 Additional address information for ‘Extended HART’ protocols
Table 4 – Relation of ProtocolId and supported features
29 Table 5 – Simple address information data types
30 10 Communication data types
10.1 General
Table 6 – Structured address information data types
31 10.2 Protocol-specific Addressing Information
10.3 Datatype definitions
Table 7 – Simple communication data types
33 Table 8 – Structured communication data types
35 11 Channel parameter data types
36 Table 9 – Simple channel parameter data types
Table 10 – Structured channel parameter data types
38 12 Device identification
12.1 Protocol-specific handling of data type STRING
12.2 Address Range for Scan
12.3 Support for Extended Manufacturer and Device Type Code
12.4 Device type identification data types for protocol ‘HART’
Table 11 – Address range for device identification
39 Table 12 – Identification data types with protocol-specific mapping for protocol ‘HART’
41 Table 13 – Identification data types with semantics for protocol ‘HART’
42 12.5 Common device type identification data types for ‘Extended_HART’ protocols
Table 14 – Simple identification data types for protocol ‘HART’with protocol independent semantics
Table 15 – Structured identification data types for protocol ‘HART’ with protocol independent semantics
43 Table 16 – Identification data types for ‘Extended_HART’ protocols with protocol-specific mapping
46 Table 17 – Identification data types for ‘Extended_HART’ protocols without protocol independent semantics
47 12.6 Topology scan data types
Table 18 – Simple identification data types for ‘Extended_HART’ protocols with protocol independent semantics
Table 19 – Structured identification data types for ‘Extended_HART’ protocols with protocol independent semantics
48 12.7 Scan identification data types for protocol ‘HART’
Table 20 – Structured device type identification data types
Table 21 – Simple scan identification data types for protocol ‘HART’
Table 22 – Structured scan identification data types for protocol ‘HART’
50 12.8 Scan identification data types for ‘Extended_HART’ protocols
Table 23 – Simple scan identification data types for ‘Extended_HART’ protocols
Table 24 – Structured scan identification data types for ‘Extended_HART’ protocols
52 12.9 Device type identification data types – provided by DTM
Table 25 – Structured device type identification data types
54 Bibliography
BS EN 62453-309:2017
$198.66