BSI PD CLC IEC/TR 62453-52-90:2019
$189.07
Field device tool (FDT) interface specification – Communication implementation for common language infrastructure. IEC 61784 CPF 9
| Published By | Publication Date | Number of Pages |
| BSI | 2019 | 48 |
This part of the IEC 62453-52-xy series, which is a Technical Report, provides information for integrating the HART®1 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.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 2 | undefined |
| 5 | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications |
| 7 | CONTENTS |
| 10 | FOREWORD |
| 12 | INTRODUCTION Figures Figure 1 – Part 52-90 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 Symbols and abbreviated terms 3.3 Conventions 3.3.1 Datatype names and references to datatypes 3.3.2 Vocabulary for requirements 3.3.3 Use of UML 4 Bus category 5 Access to instance and device data 5.1 General 5.2 IO signals provided by DTM |
| 15 | 5.3 Data interfaces 5.3.1 General 5.3.2 Mapping HART datatypes to FDT datatypes Tables Table 1 – Output signal info within IOSignalInfo / HartIOSignalInfo |
| 16 | 5.3.3 SemanticInfo Table 2 – Mapping of basic datatypes |
| 17 | 5.3.4 Data exposure using IDeviceData and IInstanceData interfaces Table 3 – SemanticInfo attributes description |
| 18 | Table 4 – Basic Variables exported in IDeviceData and IInstanceData interfaces |
| 20 | Table 5 – Basic Variables exported only in IDeviceData interface |
| 21 | Figure 2 – Structural information for device variables |
| 22 | Figure 3 – Structural information for dynamic variables |
| 23 | 6 Protocol specific behaviour 6.1 Support of burst mode Figure 4 – Structural information for extended device status |
| 24 | 6.2 Device addressing 6.3 Support of scanning 6.4 Support of extended command numbers 6.5 Support for handling of communication failures and time-outs Figure 5 – Device-initiated data transfer with burst mode |
| 25 | 6.6 Support for handling of Delayed Responses 6.7 Support for topologies with mixed HART protocols 6.8 Support for nested communication with multiple gateways 6.9 Support for topologies with WirelessHART 6.10 Transparent gateways 6.10.1 General 6.10.2 Scenario 1 – Manual topology creation |
| 26 | 6.10.3 Scenario 2 – Topology scan and add 7 Protocol specific usage of general datatypes 8 Protocol specific common datatypes 8.1 HartDeviceAddress datatype Figure 6 – HartDeviceAddress datatype Table 6 – Protocol specific usage of general datatypes |
| 27 | 8.2 HartDeviceIpAddress datatype Figure 7 – HartDeviceIpAddress datatype Table 7 – HartDeviceAddress datatype |
| 28 | 8.3 HartDeviceWirelessAddress datatype Figure 8 – HartDeviceWirelessAddress datatype Table 8 – HartDeviceIpAddress datatype |
| 29 | 9 Network management datatypes 10 Communication datatypes 10.1 General 10.2 HartConnectRequest datatype Figure 9 – HartNetworkData datatype Table 9 – HartDeviceWirelessAddress datatype Table 10 – HartNetworkData datatype |
| 30 | 10.3 HartConnectResponse datatype Figure 10 – HartConnectRequest datatype Table 11 – HartConnectRequest datatype |
| 31 | 10.4 HartLongAddress datatype 10.5 HartDisconnectRequest datatype Figure 11 – HartConnectResponse datatype Table 12 – HartConnectResponse datatype Table 13 – HartLongAddress datatype |
| 32 | 10.6 HartDisconnectResponse datatype 10.7 HartTransactionRequest datatype Figure 12 – HartDisconnectRequest datatype Figure 13 – HartDisconnectResponse datatype Table 14 – HartDisconnectRequest datatype Table 15 – HartDisconnectResponse datatype |
| 33 | 10.8 HartTransactionResponse datatype Figure 14 – HartTransactionRequest datatype Figure 15 – HartTransactionResponse datatype Table 16 – HartTransactionRequest datatype |
| 34 | 10.9 HartStatus datatype 10.10 HartAbortMessage datatype Figure 16 – HartAbortMessage datatype Table 17 – HartTransactionResponse datatype Table 18 – HartStatus datatype Table 19 – HartAbortMessage datatype |
| 35 | 10.11 HartSubscribeRequest datatype 10.12 HartSubscribeResponse datatype 10.13 HartUnsubscribeRequest datatype Figure 17 – HartSubscribeRequest datatype Figure 18 – HartSubscribeResponse datatype Table 20 – HartSubscribeRequest datatype Table 21 – HartSubscribeResponse datatype |
| 36 | 10.14 HartUnsubscribeResponse datatype 11 Datatypes for process data information 11.1 General Figure 19 – HartUnsubscribeRequest datatype Figure 20 – HartUnsubscribeResponse datatype Table 22 – HartUnsubscribeRequest datatype Table 23 – HartUnsubscribeResponse datatype |
| 37 | 11.2 HartIOSignalInfo datatype Figure 21 – HartIOSignalInfo datatype Table 24 – Usage of IOSignalInfo datatype Table 25 – HartIOSignalInfo datatype |
| 38 | 12 Device identification datatypes 12.1 General 12.2 HartDeviceScanInfo datatype Figure 22 – HartDeviceScanInfo datatype Table 26 – HartDeviceScanInfo datatype |
| 40 | Table 27 – Protocol specific mapping of scan information |
| 42 | 12.3 HartDeviceIdentInfo datatype Figure 23 – HartDeviceIdentInfo datatype Table 28 – HartDeviceIdentInfo datatype |
| 43 | 12.4 Mapping of information source |
| 44 | Table 29 – Protocol specific mapping of identity information |
| 46 | Bibliography |
