MADCAD.com - The Cloud-Based Reference Library

eLibrary > PD IEC TS 62453-43:2024 Field device tool (FDT) interface specification - Object model integration profile. CLI and HTML >

PD IEC TS 62453-43:2024 Field device tool (FDT) interface specification - Object model integration profile. CLI and HTML, 2025

Expand All

TOC Search:

PD IEC TS 62453-43:2024 Field device tool (FDT) interface specification - Object model integration profile. CLI and HTML, 2025

undefined
CONTENTS
FOREWORD
INTRODUCTION
Figures [Go to Page]
Figure 1 – Relation of IEC TS 62453-43 to the IEC 62453 series
1 Scope
2 Normative references
3 Terms, definitions, abbreviated terms and conventions [Go to Page]
3.1 Terms and definitions
3.2 Abbreviated terms
3.3 Conventions
4 Implementation concept [Go to Page]
4.1 General
4.2 Implementation of abstract FDT Object model
4.3 FDT Frame Application (FA) [Go to Page]
4.3.1 General
Figure 2 – IEC TS 62453-43 Object model
Figure 3 – Frame Application [Go to Page]
4.3.2 System communication
4.4 DTM Business Logic [Go to Page]
4.4.1 General
Figure 4 – Frame Application with integrated Communication Channel
Figure 5 – DTM Business Logic [Go to Page]
4.4.2 DTM, DTM Device Type, and Device Ident Info
Figure 6 – DTM, Device Type and Device Ident Info [Go to Page]
4.4.3 Device data info
4.4.4 Process data info
Figure 7 – Process data info [Go to Page]
4.4.5 Diagnostic data info
4.4.6 Network management info
4.4.7 Function info
4.4.8 Report info
4.4.9 Document reference info
4.5 DTM functions [Go to Page]
4.5.1 DTM User Interface
4.5.2 Function access control
4.5.3 User interaction in DTM WebUIs
4.5.4 Command functions
4.5.5 Static Function
4.6 Communication Channel
Figure 8 – Communication Channel
4.7 DTM categories [Go to Page]
4.7.1 General
4.7.2 Device DTM
4.7.3 Communication DTM (CommDTM)
Figure 9 – Device DTM [Go to Page]
4.7.4 Gateway DTM
Figure 10 – Communication DTM
Figure 11 – Gateway DTM [Go to Page]
4.7.5 Composite Device DTM
Figure 12 – Composite Device DTM [Go to Page]
4.7.6 Module DTM
4.7.7 Block Type Manager
Figure 13 – Module DTM
Figure 14 – Block Type Manager
4.8 User management [Go to Page]
4.8.1 General
4.8.2 Multi-user access
4.8.3 User levels
Tables [Go to Page]
Table 1 – FDT user levels
Table 2 – Role-dependent access rights and user interfaces for DTMs
4.9 FDT and system topology [Go to Page]
4.9.1 General
4.9.2 Topology management
Figure 15 – Logical topology and physical topology
Figure 16 – FDT and logical topology
Figure 17 – DTMs and physical topology [Go to Page]
4.9.3 Address management
4.9.4 Configuration of fieldbus master or communication scheduler
Figure 18 – Address setting via DTM WebUI [Go to Page]
4.9.5 Data exchange between Frame Applications
4.10 Modularity
Figure 19 – Fieldbus master configuration tool as part of a DTM
4.11 FDT communication [Go to Page]
4.11.1 General
4.11.2 Point-to-point communication
4.11.3 Nested communication
Figure 20 – Point-to-point communication [Go to Page]
4.11.4 Dynamic changes in network
Figure 21 – Nested communication
4.12 Identification [Go to Page]
4.12.1 DTM instance identification
4.12.2 System GUI label
4.12.3 Hardware identification
4.13 Scanning and DTM assignment [Go to Page]
4.13.1 Scanning introduction
4.13.2 Scanning
Figure 22 – Identification of connected devices [Go to Page]
4.13.3 DTM assignment
4.13.4 Manufacturer-specific device identification
Figure 23 – Fieldbus scanning
4.14 DTM data persistence and synchronization [Go to Page]
4.14.1 Persistence overview
4.14.2 Relations of DTMDataSet
Figure 24 – FDT storage and synchronization mechanism [Go to Page]
4.14.3 DTMDataSet structure
Figure 25 – Relation between DTMDataSet, DTM instance, and device
Figure 26 – DTMDataSet structure [Go to Page]
4.14.4 Types of persistent DTM data
4.14.5 Data synchronization
Figure 27 – Data Synchronization
4.15 Device data and IO information [Go to Page]
4.15.1 Exposing device data and IO information
4.15.2 Data access control
Figure 28 – Example for same organization of FunctionInfo and DataInfo
Table 3 – Description of properties related to data access control [Go to Page]
4.15.3 Routed IO information
Figure 29 – Routed IO information [Go to Page]
4.15.4 Comparison of DTM and device data
4.15.5 PLC tool support
Figure 30 – Process Image
Figure 31 – Transfer of layout information using IProcessImage [Go to Page]
4.15.6 Support for multirole devices
Figure 32 – Multirole device
4.16 Clone of DTM instances [Go to Page]
4.16.1 General
4.16.2 Replicating a part of topology with Parent DTM and a subset of its Child DTMs
4.16.3 Cloning of a DTM without its children
4.16.4 Delayed cloning
4.17 Lifecycle concepts
4.18 Audit trail [Go to Page]
4.18.1 General
4.18.2 Audit trail events
5 Technical concepts [Go to Page]
5.1 General
Figure 33 – FDT .NET Assemblies
5.2 Support of HTML versions
5.3 Support of JavaScript versions
Figure 34 – FDT Object implementation
Table 4 – Supported HTML versions
Table 5 – Supported ECMAScript versions
5.4 Support of .NET Common Language Runtime versions [Go to Page]
5.4.1 General
5.4.2 DTM rules
5.4.3 Frame Application rules
Table 6 – Supported .NET Standard library versions
5.5 Support for 32-bit and 64-bit target platforms
5.6 Object activation and deactivation [Go to Page]
5.6.1 General
5.6.2 Assembly loading and object creation
5.6.3 Assembly dependencies
5.6.4 Shared assemblies
Figure 35 – Example: Assembly dependencies [Go to Page]
5.6.5 Object deactivation and unloading
5.7 Datatypes [Go to Page]
5.7.1 General
5.7.2 Serialization / deserialization
5.7.3 Optional elements
Figure 36 – Example: Datatype definition [Go to Page]
5.7.4 Verify
5.7.5 Clone
Figure 37 – Example: Data cloning [Go to Page]
5.7.6 Equals
5.7.7 Lists
5.7.8 Nullable
5.7.9 Enumeration
5.7.10 Protocol-specific datatypes
Figure 38 – Example: Methods without data cloning
Figure 39 – Protocol-specific datatypes
Figure 40 – Protocol manifest and type info attributes [Go to Page]
5.7.11 Custom datatypes
Figure 41 – Example: Protocol assembly attributes
Figure 42 – Example: Handling of protocol-specific assemblies in Frame Application
5.8 General object interaction [Go to Page]
5.8.1 General
5.8.2 Decoupling of FDT Objects
Figure 43 – Example: Handling of KnownType for custom data types
Figure 44 – Decoupled FDT Objects in IEC TS 62453-43 [Go to Page]
5.8.3 Parameter interchange with .NET datatypes
5.8.4 Interaction patterns
5.8.5 Properties
5.8.6 Synchronous methods
5.8.7 Asynchronous methods
Figure 45 – IAsyncResult pattern: blocking call
Figure 46 – Example: Blocking use of asynchronous interface
Figure 47 – IAsyncResult pattern (simplified): blocking call
Figure 48 – IAsyncResult pattern: non-blocking call
Figure 49 – Example: Non-blocking use of asynchronous interface
Figure 50 – IAsyncResult pattern (simplified depiction): non-blocking call
Figure 51 – IAsyncResult pattern: canceling an operation
Figure 52 – IAsyncResult pattern: providing progress events [Go to Page]
5.8.8 Events pattern
5.8.9 Exception handling
5.9 Threading [Go to Page]
5.9.1 General
5.9.2 Races
5.9.3 Locks
5.9.4 Deadlocks
5.10 Threading rules [Go to Page]
5.10.1 Implementation rules
5.10.2 Avoiding deadlocks
5.10.3 FDT Object interaction rules
5.11 Localization support [Go to Page]
5.11.1 General
5.11.2 Access to localized resources and culture-dependent functions
5.11.3 Handling of cultures
5.11.4 Switching the User Interface language
5.12 DTM User Interface implementation [Go to Page]
5.12.1 General
5.12.2 Private dialogs
5.12.3 Modal DTM WebUI
5.13 DTM User Interface hosting [Go to Page]
5.13.1 General
5.13.2 Hosting DTM WebUI
Figure 53 – General concept for hosting DTM WebUI
Figure 54 – Example: Integration of a DTM WebUI into a Frame WebUI
Figure 55 – Example: Hosting a DTM WebUI in a WPF Frame Application
5.14 Static Function implementation
Figure 56 – Example: Integrating the WebData connector in a DTM WebUI
Figure 57 – Relation of StaticFunctionDescription to Static Function
5.15 Persistence [Go to Page]
5.15.1 Overview
Figure 58 – DTMDataset structure [Go to Page]
5.15.2 Data format
5.15.3 Adding / reading / writing / deleting of data
Figure 60 – Example: Writing of DTM data in DTMDataSubset [Go to Page]
5.15.4 Searching for data
Figure 61 – Example: Reading of DTM data from a DTMDataSubset
5.16 Comparison of DTM and device data [Go to Page]
5.16.1 Comparison of datasets using IDeviceData / IInstanceData
Figure 62 – Example: Creation of a BulkData.DTMDataSubset with descriptor
Figure 63 – Example: Searching for DTMDataSubsets with specific descriptor [Go to Page]
5.16.2 Comparison of datasets using IComparison
5.17 Tracing
5.18 Report generation [Go to Page]
5.18.1 Introduction
5.18.2 Report types
5.18.3 DTM report data format
5.18.4 Report data exchange
5.19 Security [Go to Page]
5.19.1 General
5.19.2 Strong naming of assemblies
Figure 64 – Skeleton of a DTM-specific report fragment [Go to Page]
5.19.3 Identification of origin
5.19.4 Code access security
5.19.5 Validation of FDT compliance certification
Figure 65 – Example: Conformity record file
6 FDT Objects and interfaces [Go to Page]
6.1 General
Figure 66 – Example: checking conformity record file
6.2 Frame Application [Go to Page]
6.2.1 General
6.2.2 Frame Application Business Logic
Figure 67 – Frame Application BL interfaces
Table 7 – Frame Application BL interfaces [Go to Page]
6.2.3 Frame Application WebUI
6.3 DTM Business Logic [Go to Page]
6.3.1 DTM BL interfaces
Figure 68 – Frame Application WebUI
Table 8 – Frame Application WebUI interfaces
Figure 69 – DTM Business Logic interfaces (Part 1)
Figure 70 – DTM Business Logic interfaces (Part 2)
Table 9 – DTM Business Logic interfaces
Table 10 – Availability of interfaces depending of type of DTM [Go to Page]
6.3.2 State machines related to DTM BL
Figure 71 – State machine of DTM BL
Table 11 – Definition of DTM BL state machine
Figure 72 – Online state machine of DTM
Table 12 – Definition of online state machine [Go to Page]
6.3.3 State machine of instance data
Figure 73 – Modifications of data through a DTM
Figure 74 – ModifiedInDtm: State machine of instance data
Table 13 – Description of instance dataset states
Figure 75 – ModifiedInDevice: State machine related to device data
Table 14 – Description of dataset states regarding online modifications
6.4 DTM User Interface [Go to Page]
6.4.1 DTM WebUI
Figure 76 – DTM WebUI interfaces
Figure 77 – Example: Definition of DtmWebUi object
Figure 78 – Example: Access to DtmWebUi by Frame WebUI
Table 15 – DTM WebUI interfaces
6.5 Communication Channel
Figure 79 – Communication Channel interfaces
Table 16 – Communication Channel interfaces
Figure 80 – Connection state machine
Table 17 – Definition of connection state machine
6.6 Availability of interface methods
Table 18 – Availability of DTM BL methods in different states
7 FDT datatypes [Go to Page]
7.1 General
7.2 Datatypes – Base
Figure 81 – FdtDatatype and FdtList
7.3 General datatypes
7.4 Datatypes – DtmInfo / TypeInfo
Table 19 – FDT base datatypes
Table 20 – FDT General datatypes
Figure 82 – DtmInfo / TypeInfo – datatypes
7.5 Datatypes – DeviceIdentInfo
Table 21 – DtmInfo datatype description
Figure 83 – DeviceIdentInfo – datatypes
Table 22 – DeviceIdentInfo datatype description
Figure 84 – DeviceIdentInfo – Example for HART®
Table 23 – DeviceIdentInfo – Example for HART®
Figure 85 – Example: DeviceIdentInfo creation
7.6 Datatypes for installation and deployment [Go to Page]
7.6.1 Datatypes – DtmPackageManifest
Figure 86 – Example: Using DeviceIdentInfo
Figure 87 – Example: DeviceIdentInfoTypeAttribute [Go to Page]
7.6.2 Datatypes – DtmManifest
Figure 88 – DtmPackageManifest – datatypes
Table 24 – DtmPackageManifest datatype description [Go to Page]
7.6.3 Datatypes – DtmWebUiManifest
Figure 89 – DtmManifest – datatypes
Table 25 – DtmManifest datatype description
7.7 Datatypes – Communication
Figure 90 – DtmWebUiManifest – datatypes
Table 26 – DtmWebUiManifest datatype description
Figure 91 – Communication datatypes – Connect
Figure 92 – Communication datatypes – Transaction
Figure 93 – Communication datatypes – Disconnect
Figure 94 – Communication datatypes – Subscribe
Figure 95 – Communication datatypes – Scanning
Figure 96 – Communication datatypes – Address setting
Table 27 – Communication datatype description
Figure 97 – Example: Communication – Connect for HART®
Figure 98 – Example: Communication – CommunicationType for HART
7.8 Datatypes – BusCategory
7.9 Datatypes – Device / instance data [Go to Page]
7.9.1 General
Figure 99 – BusCategory – datatypes
Table 28 – BusCategory datatype description
Figure 100 – Device / instance data – datatypes
Table 29 – DeviceData datatype description
Figure 101 – Example: Providing information on data of a HART® device
Figure 102 – Example: Providing information on module data of a PROFIBUS device
Figure 103 – Example: Providing information on data
Figure 104 – Example: Providing information on structured data [Go to Page]
7.9.2 Datatypes used in reading and writing DeviceData
Figure 105 – EnumInfo – datatype
Figure 106 – Read and Write Request – datatypes
Table 30 – Reading and Writing datatype description
Figure 107 – ResponseInfo – datatype
7.10 Datatypes for export and import [Go to Page]
7.10.1 Datatypes – TopologyImportExport
Table 31 – Reading and Writing datatype description
Figure 108 – TopologyImportExport – datatypes
Table 32 – TopologyImportExport datatype description [Go to Page]
7.10.2 Datatypes – ImportExportDataset
7.11 Datatypes for process data description [Go to Page]
7.11.1 Datatypes – ProcessDataInfo
Figure 109 – ImportExportDataset – datatypes
Table 33 – ImportExportDataset datatype description
Figure 110 – ProcessDataInfo – datatypes
Table 34 – ProcessDataInfo datatype description
Figure 111 – IOSignalInfo – datatypes
Table 35 – IOSignalInfo datatype description
Figure 112 – Example: ProcessDataInfo for HART (UML)
Figure 113 – Example: ProcessDataInfo creation for HART® [Go to Page]
7.11.2 Datatypes – Process Image
Figure 114 – Example: Using ProcessData for HART®
Figure 115 – Example: IOSignalInfoType attribute
Figure 116 – ProcessImage – datatypes
Table 36 – ProcessImage datatype description
7.12 Datatypes – Address information
Figure 117 – AddressInfo – datatypes
Table 37 – AddressInfo datatype description
Figure 118 – Example: AddressInfo creation
Figure 119 – Example: Using AddressInfo
Figure 120 – Example: DeviceAddressTypeAttribute
7.13 Datatypes – NetworkDataInfo
Figure 121 – NetworkDataInfo – datatypes
Figure 122 – Example: NetworkDataInfo creation example
Table 38 – NetworkDataInfo datatype description
7.14 Datatypes – DTM functions
Figure 123 – Example: NetworkDataInfo using example
Figure 124 – Example: NetworkDataTypeAttribute example
Figure 125 – DTM Function – datatypes
7.15 Datatypes – DTM messages
Figure 126 – DTM Messages – datatypes
Table 39 – DTM Function datatype description
7.16 Datatypes – CommunicationChannelInfo
Table 40 – DTM Messages datatype description
Figure 127 – CommunicationChannelInfo – datatypes
Table 41 – CommunicationChannelInfo datatype description
7.17 Datatypes – HardwareIdentification and scanning [Go to Page]
7.17.1 General
7.17.2 Datatypes – DeviceScanInfo
Figure 128 – Example: Channel information [Go to Page]
7.17.3 Example – HardwareIdentification and scanning for HART®
Figure 129 – DeviceScanInfo – datatypes
Table 42 – DeviceScanInfo datatype description
7.18 Datatypes – DTM report types
Figure 130 – Example: HARTDeviceScanInfo – datatype
Table 43 – Example: HARTDeviceScanInfo datatype description
7.19 Information related to device modules in a monolithic DTM
Figure 131 – DTM Report – datatypes
Table 44 – Reporting datatype description
Figure 132 – Information related to device modules
8 Workflows [Go to Page]
8.1 General
8.2 Instantiation, loading and release [Go to Page]
8.2.1 Finding a DTM BL object
Figure 133 – Finding a DTM BL object [Go to Page]
8.2.2 Instantiation of a new DTM BL
Figure 134 – Instantiation of a new DTM BL [Go to Page]
8.2.3 Configuring access rights
8.2.4 Loading a DTM BL
Figure 135 – Configuration of user permissions [Go to Page]
8.2.5 Loading a DTM with Expert user level
Figure 136 – Loading a DTM BL
Figure 137 – Loading a DTM with Expert user level [Go to Page]
8.2.6 Release of a DTM BL
8.3 Persistent storage of a DTM [Go to Page]
8.3.1 Saving instance data of a DTM
Figure 138 – Release of a DTM BL [Go to Page]
8.3.2 Copy and versioning of a DTM instance
Figure 139 – Saving data of a DTM [Go to Page]
8.3.3 Dataset commit failed
8.3.4 Export a DTM dataset to file
Figure 140 – Dataset commit failed
8.4 Locking and DataTransactions in multi-user environments [Go to Page]
8.4.1 General
Figure 141 – Export a DTM dataset to file [Go to Page]
8.4.2 Propagation of changes
8.4.3 Synchronizing DTMs in multi-user environments
Figure 142 – Propagation of changes
Figure 143 – Synchronizing DTMs in multi-user environments
8.5 Execution of DTM Functions [Go to Page]
8.5.1 General
8.5.2 Finding a DTM WebUI
8.5.3 Instantiation of a DTM WebUI
Figure 144 – Finding a DTM WebUI [Go to Page]
8.5.4 Release of a DTM WebUI
Figure 145 – Instantiation of a DTM WebUI [Go to Page]
8.5.5 Execution of command functions
Figure 146 – Release of a DTM WebUI [Go to Page]
8.5.6 Opening of documents
Figure 147 – Execute a command function [Go to Page]
8.5.7 Interaction between DTM WebUI and DTM Business Logic
Figure 148 – Opening a document
Figure 149 – Interaction triggered by the DTM WebUI [Go to Page]
8.5.8 Interaction between DTM Business Logic and DTM WebUI
8.5.9 Interaction between DTM WebUI and DTM Business Logic with Cancel
Figure 150 – Interaction triggered between DTM BL and DTM WebUI [Go to Page]
8.5.10 Retrieving information about available Static Functions
Figure 151 – Interaction triggered and canceled by the DTM WebUI
Figure 152 – Retrieving information about available Static Functions [Go to Page]
8.5.11 Executing a Static Function
Figure 153 – Example: Information about available Static Functions
Figure 154 – Executing a Static Function
8.6 DTM communication [Go to Page]
8.6.1 General
8.6.2 Establishing a communication connection
8.6.3 Cancel establishment of communication connection
Figure 155 – Establishing a communication connection [Go to Page]
8.6.4 Communicating with the device
Figure 156 – DTM cancels ongoing Connect operation [Go to Page]
8.6.5 Frame Application or Child DTM disconnect a device
Figure 157 – Communicating with the device [Go to Page]
8.6.6 Terminating a communication connection
Figure 158 – Child DTM disconnects [Go to Page]
8.6.7 DTM aborts communication connection
Figure 159 – Child DTM terminates a connection [Go to Page]
8.6.8 Communication Channel aborts communication connection
Figure 160 – Child DTM aborts a connection
8.7 Nested communication [Go to Page]
8.7.1 General
Figure 161 – Communication Channel aborts a connection [Go to Page]
8.7.2 Communication request for a nested connection
Figure 162 – Example: Nested communication behavior [Go to Page]
8.7.3 Propagation of errors for a nested connection
Figure 163 – Example: Nested communication data exchange
8.8 Topology planning [Go to Page]
8.8.1 General
8.8.2 Adding a DTM to the topology
8.8.3 Removing a DTM from topology
Figure 164 – Add DTM to topology [Go to Page]
8.8.4 Frame Application creates topology
Figure 165 – Removing a DTM from topology [Go to Page]
8.8.5 DTM generates sub-topology
Figure 166 – Frame Application creates topology
Figure 167 – DTM generates sub-topology [Go to Page]
8.8.6 Physical Layer and DataLinkLayer
8.9 Instantiation, configuration, move and release of Child DTMs [Go to Page]
8.9.1 General
8.9.2 Instantiation and configuration of Child DTM BL
Figure 168 – Instantiation and configuration of Child DTM BL [Go to Page]
8.9.3 Interaction between Parent DTM and Child DTM
Figure 169 – Interaction between Parent DTM and Child DTM [Go to Page]
8.9.4 Interaction between Parent DTM and Child DTM using IDtmMessaging
8.9.5 Parent DTM moves a Child DTM
Figure 170 – Interaction using IDtmMessaging [Go to Page]
8.9.6 Parent DTM removes Child DTM
Figure 171 – Parent DTM moves a Child DTM
8.10 Topology scan [Go to Page]
8.10.1 General
8.10.2 Scan of network topology
Figure 172 – Parent DTM removes Child DTM [Go to Page]
8.10.3 Cancel topology scan
Figure 173 – Scan of network topology [Go to Page]
8.10.4 Scan based DTM assignment
Figure 174 – Cancel topology scan [Go to Page]
8.10.5 Manufacturer-specific device identification
Figure 175 – Scan based DTM assignment
Figure 176 – Manufacturer-specific device identification
8.11 Configuration of communication networks [Go to Page]
8.11.1 Configuration of a fieldbus master
Figure 177 – Configuration of a fieldbus master [Go to Page]
8.11.2 Integration of a passive device
8.12 Using IO information [Go to Page]
8.12.1 Assignment of symbolic name to process data
Figure 178 – Integration of a passive device
Figure 179 – Assignment of process data [Go to Page]
8.12.2 Creation of Process Image
8.12.3 Validation of changes in process image while PLC is running
Figure 180 – Creation of process image [Go to Page]
8.12.4 Changing of variable names using process image interface
Figure 181 – Validation of changes while PLC is running
8.13 Managing addresses [Go to Page]
8.13.1 Set DTM address with user interface
Figure 182 – Changing of variable names using process image interface
Figure 183 – Set DTM address with WebUI [Go to Page]
8.13.2 Set DTM addresses without user interface
Figure 184 – Set DTM addresses without UI [Go to Page]
8.13.3 Display or modify addresses of all Child DTMs with user interface
Figure 185 – Display or modify child addresses with UI
8.14 Device-initiated data transfer
Figure 186 – Device-initiated data transfer
8.15 Reading and writing data [Go to Page]
8.15.1 Read/write instance data
Figure 187 – Read/write instance data [Go to Page]
8.15.2 Read/write device data
Figure 188 – Read/write device data
8.16 Comparing data [Go to Page]
8.16.1 Comparing device dataset and instance dataset
8.16.2 Comparing different instance datasets
Figure 189 – Comparing device dataset and instance dataset
8.17 Reassigning a different DtmDeviceType at a device node [Go to Page]
8.17.1 General
Figure 190 – Compare instance data with persisted dataset [Go to Page]
8.17.2 DTM detects a change in connected device type
Figure 191 – DTM triggers ActiveTypeChanged event [Go to Page]
8.17.3 Search matching DtmDeviceTypes after incompatible device exchange
8.17.4 Reassign DtmDeviceType after incompatible device exchange
Figure 192 – Find matching DtmDeviceTypes after incompatible device exchange
Figure 193 – Reassign a DtmDeviceType after incompatible device exchange
8.18 Copying part of FDT Topology [Go to Page]
8.18.1 Cloning of a single DTM without Children
Figure 194 – Clone DTM without children [Go to Page]
8.18.2 Cloning of a DTM with all its Children
8.19 Sequences for audit trail [Go to Page]
8.19.1 General
8.19.2 Audit trail of parameter modifications in instance dataset
Figure 195 – Clone DTM with all children [Go to Page]
8.19.3 Audit trail of parameter modifications in device dataset
Figure 196 – Audit trail of parameter modifications in instance dataset [Go to Page]
8.19.4 Audit trail of function calls
Figure 197 – Audit trail of parameter modifications in device
Figure 198 – Audit trail of function calls [Go to Page]
8.19.5 Audit trail of general notification
9 Installation [Go to Page]
9.1 General
9.2 Common rules [Go to Page]
9.2.1 Predefined installation paths
Table 45 – Predefined FDT installation paths [Go to Page]
9.2.2 Predefined web-server paths
Figure 199 – Installation paths (with example DTM) [Go to Page]
9.2.3 Manifest files
9.2.4 Paths in manifest files
9.2.5 DTM Installation package format
Table 46 – Predefined web-server paths [Go to Page]
9.2.6 Digital signatures of package components
9.3 Installation of FDT core assemblies
9.4 Installation of communication protocols [Go to Page]
9.4.1 General
9.4.2 Registration
9.4.3 Protocol manifest
Figure 200 – Installed FDT and protocol assemblies [Go to Page]
9.4.4 NuGet package
Figure 201 – Example: Protocol manifest
9.5 Installation of DTMs [Go to Page]
9.5.1 General
Figure 202 – NuGet file structure [Go to Page]
9.5.2 Registration
Figure 203 – Search for installed DTMs [Go to Page]
9.5.3 DTM manifest
Figure 204 – Example: DtmManifest [Go to Page]
9.5.4 DTM WebUI manifest
9.5.5 WebUI container files
Figure 205 – Example: DtmWebUiManifest
9.6 DTM package file [Go to Page]
9.6.1 Naming convention
Figure 206 – Structure of a WebUI container file [Go to Page]
9.6.2 Structure (physical model)
9.6.3 Relationships (logical model)
Figure 207 – DTM package file structure [Go to Page]
9.6.4 Core properties
Figure 208 – DTM package file relationships
Table 47 – Overview of relationships [Go to Page]
9.6.5 License file
9.6.6 Readme file
9.6.7 Icon file
Table 48 – Overview of core properties [Go to Page]
9.6.8 DTM package manifest
Figure 209 – Example: DtmPackageManifest [Go to Page]
9.6.9 DTM device identification manifest
Figure 210 – Example: DeviceIdentManifest [Go to Page]
9.6.10 DTM package file creation rules
9.6.11 Countersignatures
9.6.12 Referenced NuGet packages
9.7 DTM deployment
Figure 211 – DTM deployment
9.8 Paths and file information [Go to Page]
9.8.1 Path information provided by a DTM via IFunction
Figure 212 – Unpacking the DTM package [Go to Page]
9.8.2 Paths and persistence
9.8.3 Multi-user systems
10 Life cycle concept [Go to Page]
10.1 General
10.2 Technical concept [Go to Page]
10.2.1 General
10.2.2 DtmManifest / DtmInfo
Figure 213 – Overview DTM identification [Go to Page]
10.2.3 TypeInfo
Table 49 – DTM identification
Table 50 – TypeInfo – User readable description of supported types [Go to Page]
10.2.4 Supported DataSet formats
10.2.5 DeviceIdentInfo
Table 51 – TypeInfo identification
Table 52 – DtmType – Dataset support identification [Go to Page]
10.2.6 Dataset
10.2.7 DeviceScanInfo
Table 53 – Dataset identification
10.3 DTM installation [Go to Page]
10.3.1 General
Figure 214 – Identification attributes in DTM package
Table 54 – DeviceScanInfo – scanned device identification [Go to Page]
10.3.2 Handling of DTM installations
10.4 Life cycle scenarios [Go to Page]
10.4.1 Overview
Table 55 – Package information
Table 56 – Changing DTM – overview [Go to Page]
10.4.2 Search for device type in DTM packages
10.4.3 Search for installed DTMs
Figure 215 – Search DTM package for list of supported types
Figure 216 – Scan installed DTMs [Go to Page]
10.4.4 Dataset migration for reassigned DTM
Figure 217 – Dataset migration to a reassigned DtmDeviceType
11 Frame Application architectures [Go to Page]
11.1 General
11.2 Standalone application
11.3 Remote User Interface
11.4 Distributed multi-user application
Figure 218 – Client / Server Application
11.5 OPC UA
Figure 219 – Example for distributed multi-user application
11.6 Web services
Figure 220 – OPC UA server based on IEC TS 62453-43
Figure 221 – Web server based on IEC TS 62453-43
Annexes [Go to Page]
Annex A (normative) Use case model [Go to Page]
A.1 Use case model overview
A.2 Actors
Figure A.1 – Main use case diagram [Go to Page]
A.3 Use cases
Table A.1 – Actors
Figure A.2 – Observation use cases
Table A.2 – Observation use cases
Figure A.3 – Operation use cases
Table A.3 – Operation use cases
Figure A.4 – Maintenance use cases
Table A.4 – Maintenance use cases
Figure A.5 – Planning use cases
Table A.5 – Planning use cases
Annex B (normative) FDT interface definition and datatypes
Annex C (normative) Mapping of services to interface methods [Go to Page]
C.1 General
C.2 DTM services
Table C.1 – General services
Table C.2 – DTM service related to installation
Table C.3 – DTM service related to DTM information
Table C.4 – DTM services related to DTM state machine
Table C.5 – DTM services related to function
Table C.6 – DTM services related to documentation
Table C.7 – DTM services to access the instance data
Table C.8 – DTM services to access diagnosis
Table C.9 – DTM services to access to device data
Table C.10 – DTM services related to network management information
Table C.11 – DTM services related to online operation
Table C.12 – DTM services related to FDT-Channel objects [Go to Page]
C.3 Presentation object services
C.4 General channel services
Table C.13 – DTM services related to import and export
Table C.14 – DTM services related to data synchronization
Table C.15 – DTM UI state control
Table C.16 – General channel service [Go to Page]
C.5 Process Channel services
C.6 Communication Channel Services
Table C.17 – Channel services for IO related information
Table C.18 – Channel services related to communication [Go to Page]
C.7 Frame Application Services
Table C.19 – Channel services related sub-topology management
Table C.20 – Channel services related to functions
Table C.21 – Channel services related to scan
Table C.22 – FA services related to general event
Table C.23 – FA services related to topology management
Table C.24 – FA services related to redundancy
Table C.25 – FA services related to storage of DTM data
Table C.26 – FA services related to DTM data synchronization
Table C.27 – FA services related to presentation
Table C.28 – FA services related to audit trail
Table C.29 – FA services related to sandboxing a DTM
Table C.30 – FA services related to sandboxing a Communication Channel
Annex D (normative) FDT version interoperability guide [Go to Page]
D.1 Overview
D.2 General
D.3 Component interoperability
Table D.1 – Interoperability between components of different versions
Annex E (normative) Definition of JavaScript APIs [Go to Page]
E.1 General
E.2 Request / Response datatypes
E.3 Message datatypes [Go to Page]
E.3.1 SendMessages
E.3.2 Request datatype
E.3.3 Response datatype
E.4 API for WebUIs
E.5 API for tracing
Annex F (informative) Implementation hints [Go to Page]
F.1 IAsyncResult pattern [Go to Page]
F.1.1 Overview
F.2 Threading best practices
F.3 Testing DTM messages in regard to JSON serialization/deserialization
Figure F.1 – Example: Test for JSON data
Figure F.2 – Example: Erroneous DTM-specific message example
Figure F.3 – Example: Failing test for erroneous JSON data
Annex G (informative) Comparison of IEC TR 62453-42 and IEC TS 62453-43
Annex H (informative) Physical layer examples [Go to Page]
H.1 General
H.2 Interbus S
H.3 PROFIBUS
H.4 PROFINET
Annex I (informative) Predefined SemanticIds [Go to Page]
I.1 General
I.2 Data
I.3 Images
I.4 Documents
Annex J (informative) Standard StaticFunctions [Go to Page]
J.1 General
J.2 StaticFunction GetDeviceStatus
Table J.1 – StaticFunctionDescription for GetDeviceStatus [Go to Page]
J.3 StaticFunction GetProcessValue
Table J.2 – IStaticFunction2: BeginExecute arguments for GetDeviceStatus
Table J.3 – Exceptions for GetDeviceStatus
Table J.4 – StaticFunctionDescription for GetProcessValue
Table J.5 – IStaticFunction2:BeginExecute arguments for GetDeviceStatus
Table J.6 – Exceptions for GetProcessValue
Bibliography [Go to Page]

Email *
Password *
Confirm *
First Name *
Last Name *
Title
Company Name *
Company Size *
Industry *
Address *
Address 2
City *
State *	Zip *
Country *
Phone *
How did you hear about MADCAD.com? *

Company*
Full name*
Email*
Phone

Full name*
Email*
Phone
Your selection

MADCAD.com Free Trial

Report To Us

Contact us for a custom quote

⨯To continue with accurate pricing,
please select your company type below:

⨯We need your input!

⨯ We need your input!

⨯We need your input!

⨯We need your input!

Cart Warning

PD IEC TS 62453-43:2024 Field device tool (FDT) interface specification - Object model integration profile. CLI and HTML, 2025

Username:
Password:

Company Industry
Number Of Employees
Revenue

MADCAD.com Free Trial

Report To Us

Contact us for a custom quote

⨯To continue with accurate pricing, please select your company type below:

⨯We need your input!

⨯ We need your input!

⨯We need your input!

⨯We need your input!

Cart Warning

PD IEC TS 62453-43:2024 Field device tool (FDT) interface specification - Object model integration profile. CLI and HTML, 2025

⨯To continue with accurate pricing,
please select your company type below: