{"id":245321,"date":"2024-10-19T16:08:03","date_gmt":"2024-10-19T16:08:03","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-pd-clc-tr-iec-62453-422019\/"},"modified":"2024-10-25T11:07:58","modified_gmt":"2024-10-25T11:07:58","slug":"bsi-pd-clc-tr-iec-62453-422019","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-pd-clc-tr-iec-62453-422019\/","title":{"rendered":"BSI PD CLC\/TR IEC 62453-42:2019"},"content":{"rendered":"
This part of IEC 62453, which is a technical report, defines how the common FDT principles are implemented based on the .NET technology, including the object behaviour and object interaction via .NET interfaces. This document specifies FDT version 2.0.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | INTRODUCTION Figures Figure 1 \u2013 Relation of IEC 62453-42 to the IEC 62453 series <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 1 Scope 2 Normative references 3 Terms, definitions, abbreviations and conventions 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 3.2 Abbreviations 3.3 Conventions <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 4 Implementation concept 4.1 Technological orientation 4.2 Implementation of abstract FDT object model <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 4.3 FDT Frame Application (FA) Figure 2 \u2013 IEC 62453-42 Object Model Figure 3 \u2013 Frame Application <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 4.4 DTM Business Logic 4.4.1 General <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 4.4.2 Implementation of DTM, DTM Device Type, and Device Ident Info Figure 4 \u2013 DTM Business Logic <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 4.4.7 Function Info 4.4.8 Report Info 4.4.9 Document Reference Info 4.5 Implementation of DTM Functions 4.5.1 DTM User Interface <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 4.5.2 Function access control 4.5.3 Handling of standard UI elements in modeless DTM UI interfaces <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 4.5.4 Command functions 4.6 User management 4.6.1 General 4.6.2 Multi-user access 4.6.3 User levels <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Table 1 \u2013 FDT User levels <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Table 2 \u2013 Role dependent Access Rights and User Interfaces for DTMs <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 4.7 Implementation of FDT and system topology 4.7.1 General <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 4.7.2 Topology management Figure 7 \u2013 Logical topology and physical topology Figure 8 \u2013 FDT and logical topology <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Figure 9 \u2013 DTMs and physical topology <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 4.7.3 Data exchange between Frame Applications 4.8 Implementation of Modularity 4.9 Implementation of FDT communication 4.9.1 Handling of communication requests <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 4.9.2 Handling of communication errors 4.9.3 Handling of loss of connection 4.9.4 Point\u2013to-point communication Figure 10 \u2013 Point\u2013to-point communication <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 4.9.5 Nested communication 4.9.6 Dynamic changes in network Figure 11 \u2013 Nested communication <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 4.10 Identification 4.10.1 DTM instance identification 4.10.2 Hardware identification <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 4.11 Implementation of DTM data persistence and synchronization 4.11.1 Persistence overview Figure 12 \u2013 Identification of connected devices <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 4.11.2 Relations of DTMDataSet Figure 13 \u2013 FDT storage and synchronization mechanism Figure 14 \u2013 Relation between DTMDataSet, DTM instance, and device <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 4.11.3 DTMDataSet structure Figure 15 \u2013 DTMDataSet structure <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 4.11.4 Types of persistent DTM data 4.11.5 Data synchronization <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 4.12 Implementation of access to device data and IO information 4.12.1 Exposing device data and IO information Figure 16 \u2013 Data Synchronization <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 4.12.2 Data access control <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Table 3 \u2013 Description of properties related to data access control <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | 4.12.3 Routed IO information 4.12.4 Comparison of DTM and device data Figure 17 \u2013 Routed IO information <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | 4.12.5 Support for multirole devices Figure 18 \u2013 Multirole Device <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 4.13 Clone of DTM instances 4.13.1 General 4.13.2 Replicating a part of topology with Parent DTM and a subset of its Child DTMs 4.13.3 Cloning of a DTM without its children 4.13.4 Delayed cloning <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 4.14 Lifecycle concepts 4.15 Audit trail 4.15.1 General 4.15.2 Audit trail events <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | 5 Technical concepts 5.1 General Figure 19 \u2013 FDT .NET Assemblies <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Figure 20 \u2013 FDT Object implementation <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 5.2 Support of .NET Common Language Runtime versions 5.2.1 General 5.2.2 Rules for FDT .NET assemblies 5.2.3 DTM rules 5.2.4 Frame Application rules Table 4 \u2013 Supported CLR versions <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 5.2.5 FDT CLR extension concept 5.3 Support for 32-bit and 64-bit target platforms Figure 21 \u2013 FDT CLR extension concept <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | 5.4 Object activation and deactivation 5.4.1 General 5.4.2 Assembly loading and object creation Figure 22 \u2013 Example: Assembly.LoadFrom() <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | 5.4.3 Assembly dependencies 5.4.4 Shared assemblies Figure 23 \u2013 Example: Assembly dependencies <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | 5.4.5 Object deactivation and unloading <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | 5.5 Datatypes 5.5.1 General 5.5.2 Serialization \/ deserialization Figure 24 \u2013 Example: Datatype definition <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | 5.5.3 Support of XML 5.5.4 Optional elements 5.5.5 Verify 5.5.6 Clone <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | 5.5.7 Equals 5.5.8 Lists Figure 25 \u2013 Example: Data cloning Figure 26 \u2013 Example: Methods without data cloning <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | 5.5.9 Nullable 5.5.10 Enumeration 5.5.11 Protocol-specific datatypes Figure 27 \u2013 Protocol-specific datatypes <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | Figure 28 \u2013 Protocol manifest and type info attributes <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | 5.5.12 Custom datatypes Figure 29 \u2013 Example: Protocol assembly attributes Figure 30 \u2013 Example: Handling of protocol-specific assemblies in Frame Application <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | 5.6 General object interaction 5.6.1 General 5.6.2 Decoupling of FDT Objects Figure 31 \u2013 Decoupled FDT Objects in IEC 62453-42 <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | 5.6.3 Parameter interchange with .NET datatypes 5.6.4 Interaction patterns 5.6.5 Properties 5.6.6 Synchronous methods <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | 5.6.7 Asynchronous methods <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Figure 32 \u2013 IAsyncResult pattern: blocking call Figure 33 \u2013 Example: Blocking use of asynchronous interface <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Figure 34 \u2013 IAsyncResult pattern (simplified): blocking call Figure 35 \u2013 IAsyncResult pattern: non-blocking call <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Figure 36 \u2013 Example: Non-blocking use of asynchronous interface Figure 37 \u2013 IAsyncResult pattern (simplified depiction): non-blocking call <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Figure 38 \u2013 IAsyncResult pattern: canceling an operation <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | 5.6.8 Events pattern Figure 39 \u2013 IAsyncResult pattern: providing progress events <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | 5.6.9 Exception handling <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | 5.7 Threading 5.7.1 Introduction <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | 5.7.2 Threading rules <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | 5.8 Localization support 5.8.1 General <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | 5.8.2 Access to localized resources and culture-dependent functions 5.8.3 Handling of cultures <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | 5.8.4 Switching the User Interface language 5.9 DTM User Interface implementation 5.9.1 General 5.9.2 Resizing <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Figure 40 \u2013 Frame Application’s host window providing scroll bars Figure 41 \u2013 Control using internal scrollbars <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | 5.9.3 Private dialogs 5.10 DTM User Interface hosting 5.10.1 General 5.10.2 Hosting DTM WPF controls <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | 5.10.3 Hosting DTM WinForms controls Figure 42 \u2013 Example: Hosting a DTM WPF control in a WPF Frame Application Figure 43 \u2013 Example: Hosting a DTM WPF control in a WinForms Frame Application <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | 5.11 Static Function implementation Figure 44 \u2013 Example: Hosting DTM WinForms controls in a WinForms Frame Application Figure 45 \u2013 Example: Hosting a DTM WinForms control in a WPF Frame Application <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Figure 46 \u2013 Relation of StaticFunctionDescription to Static Function <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | 5.12 Persistence 5.12.1 Overview Figure 47 \u2013 DTMDataset structure <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | 5.12.2 Data format 5.12.3 Adding \/ reading \/ writing \/ deleting of data <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Figure 48 \u2013 Example: Initialization of DTMDataSubset with DTM data Figure 49 \u2013 Example: Writing of DTM data in DTMDataSubset <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | 5.12.4 Searching for data Figure 50 \u2013 Example: Reading of DTM data from a DTMDataSubset <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | 5.13 Comparison of DTM and device data 5.13.1 Comparison of datasets using IDeviceData \/ IInstanceData Figure 51 \u2013 Example: Creation of a BulkData.DTMDataSubset with descriptor Figure 52 \u2013 Example: Searching for DTMDataSubsets with specific descriptor <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | 5.13.2 Comparison of datasets using IComparison 5.14 Tracing 5.15 Report generation 5.15.1 General <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | 5.15.2 Report types 5.15.3 DTM report data format <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | 5.15.4 Report data exchange 5.16 Security 5.16.1 General 5.16.2 Strong naming of assemblies Figure 53 \u2013 Skeleton of a DTM-specific report fragment <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | 5.16.3 Identification of origin 5.16.4 Code access security 5.16.5 Validation of FDT compliance certification Figure 54 \u2013 Example: Authenticode check <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | Figure 55 \u2013 Example: Conformity record file <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | 6 FDT Objects and interfaces 6.1 General Figure 56 \u2013 Example: checking conformity record file <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | 6.2 Frame Application Figure 57 \u2013 Frame Application interfaces <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | Table 5 \u2013 Frame Application interfaces <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | 6.3 DTM Business Logic 6.3.1 DTM BL interfaces <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | Figure 58 \u2013 DTM Business Logic interfaces (Part 1) <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | Figure 59 \u2013 DTM Business Logic interfaces (Part 2) <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | Table 6 \u2013 DTM Business Logic interfaces <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | Table 7 \u2013 Availability of interfaces depending of type of DTM <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | 6.3.2 State machines related to DTM BL <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | Figure 60 \u2013 State machine of DTM BL <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | Table 8 \u2013 Definition of DTM BL state machine <\/td>\n<\/tr>\n | ||||||
122<\/td>\n | Figure 61 \u2013 Online state machine of DTM <\/td>\n<\/tr>\n | ||||||
123<\/td>\n | Table 9 \u2013 Definition of online state machine <\/td>\n<\/tr>\n | ||||||
125<\/td>\n | 6.3.3 State machine of instance data Figure 62 \u2013 Modifications of data through a DTM <\/td>\n<\/tr>\n | ||||||
126<\/td>\n | Figure 63 \u2013 ModifiedInDtm: State machine of instance data Table 10 \u2013 Description of instance dataset states <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | Figure 64 \u2013 ModifiedInDevice: State machine related to device data Table 11 \u2013 Description of dataset states regarding online modifications <\/td>\n<\/tr>\n | ||||||
128<\/td>\n | 6.4 DTM User Interface Figure 65 \u2013 DTM UI interfaces Tables <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | 6.5 Communication Channel Figure 66 \u2013 Communication Channel interfaces Table 12 \u2013 DTM UI interfaces <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | 6.6 Availability of interface methods Table 13 \u2013 Communication Channel interfaces Table 14 \u2013 Availability of DTM BL methods in different states <\/td>\n<\/tr>\n | ||||||
131<\/td>\n | 7 FDT datatypes 7.1 General <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | 7.2 Datatypes \u2013 Base 7.3 General datatypes Figure 67 \u2013 FdtDatatype and FdtList Table 15 \u2013 FDT base datatypes <\/td>\n<\/tr>\n | ||||||
133<\/td>\n | 7.4 Datatypes \u2013 DtmInfo \/ TypeInfo Table 16 \u2013 FDT General datatypes <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | Figure 68 \u2013 DtmInfo \/ TypeInfo \u2013 datatypes Table 17 \u2013 DtmInfo datatype description <\/td>\n<\/tr>\n | ||||||
135<\/td>\n | 7.5 Datatypes \u2013 DeviceIdentInfo <\/td>\n<\/tr>\n | ||||||
136<\/td>\n | Figure 69 \u2013 DeviceIdentInfo \u2013 datatypes Table 18 \u2013 DeviceIdentInfo datatype description <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | Figure 70 \u2013 DeviceIdentInfo \u2013 Example for HART <\/td>\n<\/tr>\n | ||||||
138<\/td>\n | Table 19 \u2013 DeviceIdentInfo \u2013 Example for HART <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | Figure 71 \u2013 Example: DeviceIdentInfo creation <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | 7.6 Datatypes for installation and deployment 7.6.1 Datatypes \u2013 SetupManifest Figure 72 \u2013 Example: Using DeviceIdentInfo Figure 73 \u2013 Example: DeviceIdentInfoTypeAttribute Figure 74 \u2013 SetupManifest \u2013 datatypes <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | 7.6.2 Datatypes \u2013 DtmManifest Figure 75 \u2013 DtmManifest \u2013 datatypes Table 20 \u2013 SetupManifest datatype description Table 21 \u2013 DtmManifest datatype description <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | 7.6.3 Datatypes \u2013 DtmUiManifest 7.7 Datatypes \u2013 Communication Figure 76 \u2013 DtmUiManifest \u2013 datatypes Table 22 \u2013 DtmUiManifest datatype description <\/td>\n<\/tr>\n | ||||||
143<\/td>\n | Figure 77 \u2013 Communication datatypes \u2013 Connect Figure 78 \u2013 Communication datatypes \u2013 Transaction <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | Figure 79 \u2013 Communication datatypes \u2013 Disconnect Figure 80 \u2013 Communication datatypes \u2013 Subscribe <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | Figure 81 \u2013 Communication datatypes \u2013 Scanning Figure 82 \u2013 Communication datatypes \u2013 Address setting <\/td>\n<\/tr>\n | ||||||
146<\/td>\n | Table 23 \u2013 Communication datatype description <\/td>\n<\/tr>\n | ||||||
147<\/td>\n | Figure 83 \u2013 Example: Communication \u2013 Connect for HART <\/td>\n<\/tr>\n | ||||||
148<\/td>\n | 7.8 Datatypes \u2013 BusCategory 7.9 Datatypes \u2013 Device \/ Instance Data 7.9.1 General Figure 84 \u2013 Example: Communication \u2013 CommunicationType for HART Figure 85 \u2013 BusCategory \u2013 datatypes Table 24 \u2013 BusCategory datatype description <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | Figure 86 \u2013 Device \/ Instance data \u2013 datatypes <\/td>\n<\/tr>\n | ||||||
150<\/td>\n | Table 25 \u2013 DeviceData datatype description <\/td>\n<\/tr>\n | ||||||
151<\/td>\n | Figure 87 \u2013 Example: Providing information on data of a HART device <\/td>\n<\/tr>\n | ||||||
152<\/td>\n | Figure 88 \u2013 Example: Providing information on module data of a PROFIBUS device <\/td>\n<\/tr>\n | ||||||
153<\/td>\n | Figure 89 \u2013 Example: Providing information on data <\/td>\n<\/tr>\n | ||||||
154<\/td>\n | Figure 90 \u2013 Example: Providing information on structured data <\/td>\n<\/tr>\n | ||||||
155<\/td>\n | 7.9.2 Datatypes used in reading and writing DeviceData Figure 91 \u2013 EnumInfo \u2013 datatype Figure 92 \u2013 Read and Write Request \u2013 datatypes Table 26 \u2013 Reading and Writing datatype description <\/td>\n<\/tr>\n | ||||||
156<\/td>\n | Figure 93 \u2013 ResponseInfo \u2013 datatype Table 27 \u2013 Reading and Writing datatype description <\/td>\n<\/tr>\n | ||||||
157<\/td>\n | 7.10 Datatypes for export and import 7.10.1 Datatypes \u2013 TopologyImportExport Figure 94 \u2013 TopologyImportExport \u2013 datatypes <\/td>\n<\/tr>\n | ||||||
158<\/td>\n | 7.10.2 Datatypes \u2013 ImportExportDataset Figure 95 \u2013 ImportExportDataset \u2013 datatypes Table 28 \u2013 TopologyImportExport datatype description Table 29 \u2013 ImportExportDataset datatype description <\/td>\n<\/tr>\n | ||||||
159<\/td>\n | 7.11 Datatypes for process data description 7.11.1 Datatypes \u2013 ProcessDataInfo Figure 96 \u2013 ProcessDataInfo \u2013 datatypes <\/td>\n<\/tr>\n | ||||||
160<\/td>\n | Figure 97 \u2013 IOSignalInfo \u2013 datatypes Table 30 \u2013 ProcessDataInfo datatype description <\/td>\n<\/tr>\n | ||||||
161<\/td>\n | Table 31 \u2013 IOSignalInfo datatype description <\/td>\n<\/tr>\n | ||||||
162<\/td>\n | Figure 98 \u2013 Example: ProcessDataInfo for HART (UML) <\/td>\n<\/tr>\n | ||||||
163<\/td>\n | Figure 99 \u2013 Example: ProcessDataInfo creation for HART <\/td>\n<\/tr>\n | ||||||
164<\/td>\n | 7.11.2 Datatypes \u2013 Process Image Figure 100 \u2013 Example: Using ProcessData for HART Figure 101 \u2013 Example: IOSignalInfoType attribute <\/td>\n<\/tr>\n | ||||||
165<\/td>\n | 7.12 Datatypes \u2013 Address information Figure 102 \u2013 ProcessImage \u2013 datatypes Table 32 \u2013 ProcessImage datatype description <\/td>\n<\/tr>\n | ||||||
166<\/td>\n | Figure 103 \u2013 AddressInfo \u2013 datatypes Table 33 \u2013 AddressInfo datatype description <\/td>\n<\/tr>\n | ||||||
167<\/td>\n | Figure 104 \u2013 Example: AddressInfo creation <\/td>\n<\/tr>\n | ||||||
168<\/td>\n | Figure 105 \u2013 Example: Using AddressInfo Figure 106 \u2013 Example: DeviceAddressTypeAttribute <\/td>\n<\/tr>\n | ||||||
169<\/td>\n | 7.13 Datatypes \u2013 NetworkDataInfo Figure 107 \u2013 NetworkDataInfo \u2013 datatypes <\/td>\n<\/tr>\n | ||||||
170<\/td>\n | Figure 108 \u2013 Example: NetworkDataInfo creation example Table 34 \u2013 NetworkDataInfo datatype description <\/td>\n<\/tr>\n | ||||||
171<\/td>\n | 7.14 Datatypes \u2013 DTM functions Figure 109 \u2013 Example: NetworkDataInfo using example Figure 110 \u2013 Example: NetworkDataTypeAttribute example <\/td>\n<\/tr>\n | ||||||
172<\/td>\n | Figure 111 \u2013 DTM Function \u2013 datatypes <\/td>\n<\/tr>\n | ||||||
173<\/td>\n | 7.15 Datatypes \u2013 DTM messages Table 35 \u2013 DTM Function datatype description <\/td>\n<\/tr>\n | ||||||
174<\/td>\n | Figure 112 \u2013 DTM Messages \u2013 datatypes Table 36 \u2013 DTM Messages datatype description <\/td>\n<\/tr>\n | ||||||
175<\/td>\n | 7.16 Datatypes for delegation of DTM UI dialog actions 7.17 Datatypes \u2013 CommunicationChannelInfo Figure 113 \u2013 ActionItem \u2013 datatypes Figure 114 \u2013 CommunicationChannelInfo \u2013 datatypes Table 37 \u2013 ActionItem datatype description <\/td>\n<\/tr>\n | ||||||
176<\/td>\n | Figure 115 \u2013 Example: Channel information Table 38 \u2013 CommunicationChannelInfo datatype description <\/td>\n<\/tr>\n | ||||||
177<\/td>\n | 7.18 Datatypes \u2013 HardwareIdentification and scanning 7.18.1 General 7.18.2 Datatypes \u2013 DeviceScanInfo Figure 116 \u2013 DeviceScanInfo \u2013 datatypes Table 39 \u2013 DeviceScanInfo datatype description <\/td>\n<\/tr>\n | ||||||
178<\/td>\n | 7.18.3 Example \u2013 HardwareIdentification and scanning for HART Figure 117 \u2013 Example: HARTDeviceScanInfo \u2013 datatype Table 40 \u2013 Example: HARTDeviceScanInfo datatype description <\/td>\n<\/tr>\n | ||||||
179<\/td>\n | 7.19 Datatypes \u2013 DTM report types 7.20 Information related to device modules in a monolithic DTM Figure 118 \u2013 DTM Report \u2013 datatypes Table 41 \u2013 Reporting datatype description <\/td>\n<\/tr>\n | ||||||
180<\/td>\n | Figure 119 \u2013 Information related to device modules <\/td>\n<\/tr>\n | ||||||
181<\/td>\n | 8 Workflows 8.1 General 8.2 Instantiation, loading and release 8.2.1 Finding a DTM BL object <\/td>\n<\/tr>\n | ||||||
182<\/td>\n | Figure 120 \u2013 Finding a DTM BL object <\/td>\n<\/tr>\n | ||||||
183<\/td>\n | 8.2.2 Instantiation of a new DTM BL <\/td>\n<\/tr>\n | ||||||
184<\/td>\n | Figure 121 \u2013 Instantiation of a new DTM BL <\/td>\n<\/tr>\n | ||||||
185<\/td>\n | 8.2.3 Configuring access rights <\/td>\n<\/tr>\n | ||||||
186<\/td>\n | 8.2.4 Loading a DTM BL Figure 122 \u2013 Configuration of user permissions <\/td>\n<\/tr>\n | ||||||
187<\/td>\n | 8.2.5 Loading a DTM with Expert user level Figure 123 \u2013 Loading a DTM BL <\/td>\n<\/tr>\n | ||||||
188<\/td>\n | 8.2.6 Release of a DTM BL Figure 124 \u2013 Loading a DTM with Expert user level <\/td>\n<\/tr>\n | ||||||
189<\/td>\n | 8.3 Persistent storage of a DTM 8.3.1 Saving instance data of a DTM Figure 125 \u2013 Release of a DTM BL <\/td>\n<\/tr>\n | ||||||
190<\/td>\n | 8.3.2 Copy and versioning of a DTM instance Figure 126 \u2013 Saving data of a DTM <\/td>\n<\/tr>\n | ||||||
191<\/td>\n | 8.3.3 Dataset commit failed 8.3.4 Export a DTM dataset to file Figure 127 \u2013 Dataset commit failed <\/td>\n<\/tr>\n | ||||||
192<\/td>\n | 8.4 Locking and DataTransactions in multi-user environments 8.4.1 General Figure 128 \u2013 Export a DTM dataset to file <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | 8.4.2 Propagation of changes <\/td>\n<\/tr>\n | ||||||
194<\/td>\n | Figure 129 \u2013 Propagation of changes <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | 8.4.3 Synchronizing DTMs in multi-user environments Figure 130 \u2013 Synchronizing DTMs in multi-user environments <\/td>\n<\/tr>\n | ||||||
196<\/td>\n | 8.5 Execution of DTM Functions 8.5.1 General 8.5.2 Finding a DTM User Interface object <\/td>\n<\/tr>\n | ||||||
197<\/td>\n | 8.5.3 Instantiation of an integrated DTM graphical user interface Figure 131 \u2013 Finding a DTM User Interface <\/td>\n<\/tr>\n | ||||||
198<\/td>\n | 8.5.4 Instantiation of a DTM UI triggered by the DTM BL Figure 132 \u2013 Instantiation of a DTM User Interface <\/td>\n<\/tr>\n | ||||||
199<\/td>\n | 8.5.5 Instantiation of a modal DTM UI triggered by DTM BL Figure 133 \u2013 Instantiation of a DTM UI triggered by DTM BL <\/td>\n<\/tr>\n | ||||||
200<\/td>\n | 8.5.6 Release of a DTM User Interface Figure 134 \u2013 Instantiation of a modal DTM UI triggered by DTM BL <\/td>\n<\/tr>\n | ||||||
201<\/td>\n | 8.5.7 Release of a DTM UI triggered by the DTM BL Figure 135 \u2013 Release of a DTM User Interface <\/td>\n<\/tr>\n | ||||||
202<\/td>\n | 8.5.8 Release of a DTM User Interface triggered by itself Figure 136 \u2013 Release of a DTM UI triggered by the DTM BL <\/td>\n<\/tr>\n | ||||||
203<\/td>\n | 8.5.9 Release of a non-modal DTM User Interface triggered by a standard action Figure 137 \u2013 Release of a DTM User Interface triggered by itself Figure 138 \u2013 Release of a non-modal DTM UI triggered by a standard action <\/td>\n<\/tr>\n | ||||||
204<\/td>\n | 8.5.10 Progress indication for prolonged DTM actions Figure 139 \u2013 Progress indication for prolonged DTM actions <\/td>\n<\/tr>\n | ||||||
205<\/td>\n | 8.5.11 Starting an application Figure 140 \u2013 Starting an application <\/td>\n<\/tr>\n | ||||||
206<\/td>\n | 8.5.12 Terminating applications 8.5.13 Execution of command functions 8.5.14 Execution of a command function with user interface Figure 141 \u2013 Execute a command function <\/td>\n<\/tr>\n | ||||||
207<\/td>\n | 8.5.15 Opening of documents Figure 142 \u2013 Execute a command function with user interface <\/td>\n<\/tr>\n | ||||||
208<\/td>\n | 8.5.16 Interaction between DTM User Interface and DTM Business Logic Figure 143 \u2013 Opening a document <\/td>\n<\/tr>\n | ||||||
209<\/td>\n | Figure 144 \u2013 Interaction triggered by the DTM User Interface <\/td>\n<\/tr>\n | ||||||
210<\/td>\n | 8.5.17 Interaction between DTM Business Logic and DTM User Interface Figure 145 \u2013 Interaction triggered by the DTM Business Logic <\/td>\n<\/tr>\n | ||||||
211<\/td>\n | 8.5.18 Interaction between DTM User Interface and DTM Business Logic with Cancel Figure 146 \u2013 Interaction triggered and canceled by the DTM User Interface <\/td>\n<\/tr>\n | ||||||
212<\/td>\n | 8.5.19 Retrieving information about available Static Functions Figure 147 \u2013 Retrieving information about available Static Functions <\/td>\n<\/tr>\n | ||||||
213<\/td>\n | 8.5.20 Executing a Static Function Figure 148 \u2013 Example: Information about available Static Functions <\/td>\n<\/tr>\n | ||||||
214<\/td>\n | 8.5.21 Executing a Static Function with multiple arguments Figure 149 \u2013 Executing a Static Function <\/td>\n<\/tr>\n | ||||||
215<\/td>\n | 8.6 DTM communication 8.6.1 General Figure 150 \u2013 Executing a Static Function with multiple Arguments <\/td>\n<\/tr>\n | ||||||
216<\/td>\n | 8.6.2 Establishing a communication connection Figure 151 \u2013 Establishing a communication connection <\/td>\n<\/tr>\n | ||||||
217<\/td>\n | 8.6.3 Cancel establishment of communication connection 8.6.4 Communicating with the device Figure 152 \u2013 DTM cancels ongoing Connect operation <\/td>\n<\/tr>\n | ||||||
218<\/td>\n | 8.6.5 Frame Application or Child DTM disconnect a device Figure 153 \u2013 Communicating with the device <\/td>\n<\/tr>\n | ||||||
219<\/td>\n | 8.6.6 Terminating a communication connection Figure 154 \u2013 Child DTM disconnects <\/td>\n<\/tr>\n | ||||||
220<\/td>\n | 8.6.7 DTM aborts communication connection Figure 155 \u2013 Child DTM terminates a connection Figure 156 \u2013 Child DTM aborts a connection <\/td>\n<\/tr>\n | ||||||
221<\/td>\n | 8.6.8 Communication Channel aborts communication connection 8.7 Nested communication 8.7.1 General Figure 157 \u2013 Communication Channel aborts a connection <\/td>\n<\/tr>\n | ||||||
222<\/td>\n | 8.7.2 Communication request for a nested connection Figure 158 \u2013 Example: Nested communication behavior <\/td>\n<\/tr>\n | ||||||
223<\/td>\n | 8.7.3 Propagation of errors for a nested connection Figure 159 \u2013 Example: Nested communication data exchange <\/td>\n<\/tr>\n | ||||||
224<\/td>\n | 8.8 Topology planning 8.8.1 General 8.8.2 Adding a DTM to the topology <\/td>\n<\/tr>\n | ||||||
225<\/td>\n | 8.8.3 Removing a DTM from topology Figure 160 \u2013 Add DTM to topology <\/td>\n<\/tr>\n | ||||||
226<\/td>\n | 8.8.4 Frame Application creates topology Figure 161 \u2013 Removing a DTM from topology <\/td>\n<\/tr>\n | ||||||
227<\/td>\n | 8.8.5 DTM generates sub-topology Figure 162 \u2013 Frame Application creates topology <\/td>\n<\/tr>\n | ||||||
228<\/td>\n | Figure 163 \u2013 DTM generates sub-topology <\/td>\n<\/tr>\n | ||||||
229<\/td>\n | 8.8.6 Physical Layer and DataLinkLayer 8.9 Instantiation, configuration, move and release of Child DTMs 8.9.1 General 8.9.2 Instantiation and configuration of Child DTM BL <\/td>\n<\/tr>\n | ||||||
230<\/td>\n | 8.9.3 Interaction between Parent DTM and Child DTM Figure 164 \u2013 Instantiation and configuration of Child DTM BL <\/td>\n<\/tr>\n | ||||||
231<\/td>\n | Figure 165 \u2013 Interaction between Parent DTM and Child DTM <\/td>\n<\/tr>\n | ||||||
232<\/td>\n | 8.9.4 Interaction between Parent DTM and Child DTM using IDtmMessaging 8.9.5 Parent DTM moves a Child DTM Figure 166 \u2013 Interaction using IDtmMessaging <\/td>\n<\/tr>\n | ||||||
233<\/td>\n | 8.9.6 Parent DTM removes Child DTM Figure 167 \u2013 Parent DTM moves a Child DTM <\/td>\n<\/tr>\n | ||||||
234<\/td>\n | 8.10 Topology scan 8.10.1 General 8.10.2 Scan of network topology Figure 168 \u2013 Parent DTM removes Child DTM <\/td>\n<\/tr>\n | ||||||
235<\/td>\n | 8.10.3 Cancel topology scan Figure 169 \u2013 Scan of network topology <\/td>\n<\/tr>\n | ||||||
236<\/td>\n | 8.10.4 Scan based DTM assignment Figure 170 \u2013 Cancel topology scan <\/td>\n<\/tr>\n | ||||||
237<\/td>\n | 8.10.5 Manufacturer-specific device identification Figure 171 \u2013 Scan based DTM assignment <\/td>\n<\/tr>\n | ||||||
238<\/td>\n | Figure 172 \u2013 Manufacturer-specific device identification <\/td>\n<\/tr>\n | ||||||
239<\/td>\n | 8.11 Configuration of communication networks 8.11.1 Configuration of a fieldbus master Figure 173 \u2013 Configuration of a fieldbus master <\/td>\n<\/tr>\n | ||||||
240<\/td>\n | 8.11.2 Integration of a passive device 8.12 Using IO information 8.12.1 Assignment of symbolic name to process data Figure 174 \u2013 Integration of a passive device <\/td>\n<\/tr>\n | ||||||
241<\/td>\n | Figure 175 \u2013 Assignment of process data <\/td>\n<\/tr>\n | ||||||
242<\/td>\n | 8.12.2 Creation of Process Image <\/td>\n<\/tr>\n | ||||||
243<\/td>\n | 8.12.3 Validation of changes in process image while PLC is running Figure 176 \u2013 Creation of process image <\/td>\n<\/tr>\n | ||||||
244<\/td>\n | 8.12.4 Changing of variable names using process image interface Figure 177 \u2013 Validation of changes while PLC is running <\/td>\n<\/tr>\n | ||||||
245<\/td>\n | 8.13 Managing addresses 8.13.1 Set DTM address with user interface Figure 178 \u2013 Changing of variable names using process image interface <\/td>\n<\/tr>\n | ||||||
246<\/td>\n | 8.13.2 Set DTM addresses without user interface Figure 179 \u2013 Set DTM address with UI <\/td>\n<\/tr>\n | ||||||
247<\/td>\n | 8.13.3 Display or modify addresses of all Child DTMs with user interface Figure 180 \u2013 Set DTM addresses without UI <\/td>\n<\/tr>\n | ||||||
248<\/td>\n | 8.14 Device-initiated data transfer Figure 181 \u2013 Display or modify child addresses with UI <\/td>\n<\/tr>\n | ||||||
249<\/td>\n | 8.15 Reading and writing data 8.15.1 Read\/write instance data Figure 182 \u2013 Device-initiated data transfer <\/td>\n<\/tr>\n | ||||||
250<\/td>\n | Figure 183 \u2013 Read\/write instance data <\/td>\n<\/tr>\n | ||||||
251<\/td>\n | 8.15.2 Read\/write device data <\/td>\n<\/tr>\n | ||||||
252<\/td>\n | Figure 184 \u2013 Read\/write device data <\/td>\n<\/tr>\n | ||||||
253<\/td>\n | 8.16 Comparing data 8.16.1 Comparing device dataset and instance dataset 8.16.2 Comparing different instance datasets Figure 185 \u2013 Comparing device dataset and instance dataset <\/td>\n<\/tr>\n | ||||||
254<\/td>\n | 8.17 Reassigning a different DtmDeviceType at a device node 8.17.1 General Figure 186 \u2013 Compare instance data with persisted dataset <\/td>\n<\/tr>\n | ||||||
255<\/td>\n | 8.17.2 DTM detects a change in connected device type <\/td>\n<\/tr>\n | ||||||
256<\/td>\n | Figure 187 \u2013 DTM triggers ActiveTypeChanged event <\/td>\n<\/tr>\n | ||||||
257<\/td>\n | 8.17.3 Search matching DtmDeviceTypes after incompatible device exchange <\/td>\n<\/tr>\n | ||||||
258<\/td>\n | 8.17.4 Reassign DtmDeviceType after incompatible device exchange Figure 188 \u2013 Find matching DtmDeviceTypes after incompatible device exchange <\/td>\n<\/tr>\n | ||||||
259<\/td>\n | Figure 189 \u2013 Reassign a DtmDeviceType after incompatible device exchange <\/td>\n<\/tr>\n | ||||||
260<\/td>\n | 8.18 Copying part of FDT Topology 8.18.1 Cloning of a single DTM without Children Figure 190 \u2013 Clone DTM without children <\/td>\n<\/tr>\n | ||||||
261<\/td>\n | 8.18.2 Cloning of a DTM with all its Children 8.19 Sequences for audit trail 8.19.1 General 8.19.2 Audit trail of parameter modifications in instance dataset Figure 191 \u2013 Clone DTM with all children <\/td>\n<\/tr>\n | ||||||
262<\/td>\n | 8.19.3 Audit trail of parameter modifications in device dataset Figure 192 \u2013 Audit trail of parameter modifications in instance dataset <\/td>\n<\/tr>\n | ||||||
263<\/td>\n | 8.19.4 Audit trail of function calls Figure 193 \u2013 Audit trail of parameter modifications in device Figure 194 \u2013 Audit trail of function calls <\/td>\n<\/tr>\n | ||||||
264<\/td>\n | 8.19.5 Audit trail of general notification 9 Installation 9.1 General 9.2 Common rules 9.2.1 Predefined installation paths Table 42 \u2013 Predefined FDT installation paths <\/td>\n<\/tr>\n | ||||||
266<\/td>\n | Figure 195 \u2013 GAC and FDT_Registry <\/td>\n<\/tr>\n | ||||||
267<\/td>\n | 9.2.2 Manifest files Figure 196 \u2013 Installation paths (with example DTM) <\/td>\n<\/tr>\n | ||||||
268<\/td>\n | 9.2.3 Paths in manifest files 9.2.4 Common command line arguments Table 43 \u2013 Predefined setup properties Table 44 \u2013 Setup command line parameters <\/td>\n<\/tr>\n | ||||||
269<\/td>\n | 9.2.5 Digital signatures of setup components 9.3 Installation of FDT core assemblies 9.4 Installation of communication protocols 9.4.1 General 9.4.2 Registration 9.4.3 Protocol manifest <\/td>\n<\/tr>\n | ||||||
270<\/td>\n | 9.5 Installation of DTMs 9.5.1 General Figure 197 \u2013 Example: Protocol manifest <\/td>\n<\/tr>\n | ||||||
271<\/td>\n | 9.5.2 Registration Figure 198 \u2013 Search for installed DTMs <\/td>\n<\/tr>\n | ||||||
272<\/td>\n | 9.5.3 DTM manifest <\/td>\n<\/tr>\n | ||||||
273<\/td>\n | 9.5.4 DTM User Interface manifest Figure 199 \u2013 Example: DtmManifest <\/td>\n<\/tr>\n | ||||||
274<\/td>\n | 9.6 DTM setup 9.6.1 Structure Figure 200 \u2013 Example: DtmUiManifest <\/td>\n<\/tr>\n | ||||||
275<\/td>\n | 9.6.2 DTM setup manifest Figure 201 \u2013 DTM setup structure <\/td>\n<\/tr>\n | ||||||
276<\/td>\n | 9.6.3 DTM device identification manifest Figure 202 \u2013 Example: DtmSetupManifest <\/td>\n<\/tr>\n | ||||||
278<\/td>\n | 9.6.4 Setup creation rules Figure 203 \u2013 Example: DeviceIdentManifest <\/td>\n<\/tr>\n | ||||||
279<\/td>\n | 9.7 DTM deployment <\/td>\n<\/tr>\n | ||||||
280<\/td>\n | Figure 204 \u2013 DTM deployment <\/td>\n<\/tr>\n | ||||||
281<\/td>\n | 9.8 Paths and file information 9.8.1 Path information provided by a DTM 9.8.2 Paths and persistence 9.8.3 Multi-user systems 10 Life cycle concept 10.1 General <\/td>\n<\/tr>\n | ||||||
282<\/td>\n | 10.2 Technical concept 10.2.1 General Figure 205 \u2013 Overview DTM identification <\/td>\n<\/tr>\n | ||||||
283<\/td>\n | 10.2.2 DtmManifest \/ DtmInfo 10.2.3 TypeInfo Table 45 \u2013 DTM identification Table 46 \u2013 DtmType \u2013 user readable description of supported types <\/td>\n<\/tr>\n | ||||||
284<\/td>\n | 10.2.4 Supported DataSet formats 10.2.5 DeviceIdentInfo Table 47 \u2013 TypeInfo identification Table 48 \u2013 DtmType \u2013 Dataset support identification <\/td>\n<\/tr>\n | ||||||
285<\/td>\n | 10.2.6 Dataset 10.2.7 DeviceScanInfo 10.3 DTM setup Table 49 \u2013 Dataset identification Table 50 \u2013 DeviceScanInfo \u2013 scanned device identification <\/td>\n<\/tr>\n | ||||||
286<\/td>\n | 10.4 Life Cycle Scenarios 10.4.1 Overview Figure 206 \u2013 Identification attributes in DTM setup Table 51 \u2013 Setup information <\/td>\n<\/tr>\n | ||||||
287<\/td>\n | 10.4.2 Search for device type in DTM setups Table 52 \u2013 Changing DTM\u2013- overview <\/td>\n<\/tr>\n | ||||||
288<\/td>\n | 10.4.3 Search for installed DTMs Figure 207 \u2013 Check DTM Setup for list of supported types <\/td>\n<\/tr>\n | ||||||
289<\/td>\n | Figure 208 \u2013 Scan installed DTMs <\/td>\n<\/tr>\n | ||||||
290<\/td>\n | 10.4.4 Dataset migration for reassigned DTM Figure 209 \u2013 Dataset migration to a reassigned DtmDeviceType <\/td>\n<\/tr>\n | ||||||
291<\/td>\n | 11 Frame Application architectures 11.1 General 11.2 Standalone application 11.3 Remoted user Interface Figure 210 \u2013 Client \/ Server Application <\/td>\n<\/tr>\n | ||||||
292<\/td>\n | 11.4 Distributed multi-user application 11.5 OPC UA Figure 211 \u2013 Example for distributed multi-user application <\/td>\n<\/tr>\n | ||||||
293<\/td>\n | Figure 212 \u2013 OPC UA server based on IEC TR 62453-42 <\/td>\n<\/tr>\n | ||||||
294<\/td>\n | Annex A (normative)FDT2 Use case model A.1 Use case model overview A.2 Actors Figure A.1 \u2013 Main use case diagram <\/td>\n<\/tr>\n | ||||||
295<\/td>\n | A.3 Use cases A.3.1 Use case overview Table A.1 \u2013 Actors <\/td>\n<\/tr>\n | ||||||
296<\/td>\n | A.3.2 Observation use cases Figure A.2 \u2013 Observation use cases Table A.2 \u2013 Observation use cases <\/td>\n<\/tr>\n | ||||||
297<\/td>\n | A.3.3 Operation use cases <\/td>\n<\/tr>\n | ||||||
298<\/td>\n | Figure A.3 \u2013 Operation use cases Table A.3 \u2013 Operation use cases <\/td>\n<\/tr>\n | ||||||
299<\/td>\n | A.3.4 Maintenance use cases <\/td>\n<\/tr>\n | ||||||
300<\/td>\n | Figure A.4 \u2013 Maintenance use cases <\/td>\n<\/tr>\n | ||||||
301<\/td>\n | Table A.4 \u2013 Maintenance use cases <\/td>\n<\/tr>\n | ||||||
304<\/td>\n | A.3.5 Planning use cases Figure A.5 \u2013 Planning use cases Table A.5 \u2013 Planning use cases <\/td>\n<\/tr>\n | ||||||
306<\/td>\n | A.3.6 Main Operation <\/td>\n<\/tr>\n | ||||||
307<\/td>\n | A.3.7 OEM Service A.3.8 Administration <\/td>\n<\/tr>\n | ||||||
308<\/td>\n | Annex B (normative)FDT interface definition and datatypes <\/td>\n<\/tr>\n | ||||||
309<\/td>\n | Annex C (normative)Mapping of services to interface methods C.1 General C.2 DTM services Table C.1 \u2013 General services Table C.2 \u2013 DTM services related to installation Table C.3 \u2013 DTM service related to DTM Information <\/td>\n<\/tr>\n | ||||||
310<\/td>\n | Table C.4 \u2013 DTM services related to DTM state machine Table C.5 \u2013 DTM services related to function <\/td>\n<\/tr>\n | ||||||
311<\/td>\n | Table C.6 \u2013 DTM services related to documentation Table C.7 \u2013 DTM services to access the instance data Table C.8 \u2013 DTM services to access diagnosis Table C.9 \u2013 DTM services to access to device data <\/td>\n<\/tr>\n | ||||||
312<\/td>\n | Table C.10 \u2013 DTM services related to network management information Table C.11 \u2013 DTM services related to online operation Table C.12 \u2013 DTM services related to FDT-Channel objects <\/td>\n<\/tr>\n | ||||||
313<\/td>\n | C.3 Presentation object services C.4 General channel services C.5 Process channel services Table C.13 \u2013 DTM services related to import and export Table C.14 \u2013 DTM services related to data synchronization Table C.15 \u2013 DTM UI state control Table C.16 \u2013 General channel service <\/td>\n<\/tr>\n | ||||||
314<\/td>\n | C.6 Communication Channel Services Table C.17 \u2013 Channel services for IO related information Table C.18 \u2013 Channel services related to communication Table C.19 \u2013 Channel services related sub-topology management <\/td>\n<\/tr>\n | ||||||
315<\/td>\n | C.7 Frame Application Services Table C.20 \u2013 Channel services related to functions Table C.21 \u2013 Channel services related to scan Table C.22 \u2013 FA services related to general events <\/td>\n<\/tr>\n | ||||||
316<\/td>\n | Table C.23 \u2013 FA services related to topology management Table C.24 \u2013 FA services related to redundancy Table C.25 \u2013 FA services related to storage of DTM data Table C.26 \u2013 FA services related to DTM data synchronization <\/td>\n<\/tr>\n | ||||||
317<\/td>\n | Table C.27 \u2013 FA related to presentation Table C.28 \u2013 FA services related to audit trail <\/td>\n<\/tr>\n | ||||||
318<\/td>\n | Annex D (normative)FDT version interoperability guide D.1 Overview D.2 General <\/td>\n<\/tr>\n | ||||||
319<\/td>\n | D.3 Component interoperability Table D.1 \u2013 Interoperability between components of different versions <\/td>\n<\/tr>\n | ||||||
320<\/td>\n | Annex E (normative)FDT1.2.x \/ IEC 62453-42 Backward-Compatibility E.1 Overview E.2 Parallel FDT topologies Figure E.1 \u2013 Example: IEC TR 62453-42 Frame Applicationwith FDT1.2.x backward-compatibility support <\/td>\n<\/tr>\n | ||||||
321<\/td>\n | E.3 Mixed FDT topologies Figure E.2 \u2013 IEC TR 62453-42 Frame Application with FDT1.2.x Device DTM <\/td>\n<\/tr>\n | ||||||
322<\/td>\n | Figure E.3 \u2013 IEC TR 62453-42 Frame Application with FDT1.2.x Comm. and Gateway DTM Figure E.4 \u2013 IEC TR 62453-42 Frame Application with FDT1.2.x Gateway DTM <\/td>\n<\/tr>\n | ||||||
323<\/td>\n | E.4 FDT1.2.x \/ IEC 62453-42 Adapters <\/td>\n<\/tr>\n | ||||||
324<\/td>\n | E.5 FDT1.2.x XML \/ IEC TR 62453-42 Datatype Transformers E.5.1 General Table E.1 \u2013 Adapter interface mappings <\/td>\n<\/tr>\n | ||||||
325<\/td>\n | E.5.2 Installation and Registration of Protocol-specific Transformers <\/td>\n<\/tr>\n | ||||||
326<\/td>\n | E.5.3 Interaction between FDT2 and FDT1.2 components using Transformers <\/td>\n<\/tr>\n | ||||||
327<\/td>\n | E.6 Sequences related to backward compatibility E.6.1 General E.6.2 Dataset migration from FDT1.x DTM to FDT2.x DTM Figure E.5 \u2013 IEC TR 62453-42 \u2013 FDT1.2 interaction using transformer <\/td>\n<\/tr>\n | ||||||
328<\/td>\n | Figure E.6 \u2013 Dataset migration from FDT1.x DTM to FDT2.x DTM <\/td>\n<\/tr>\n | ||||||
329<\/td>\n | Annex F (informative)Implementation Hints F.1 IAsyncResult pattern <\/td>\n<\/tr>\n | ||||||
330<\/td>\n | F.2 Threading Best Practices <\/td>\n<\/tr>\n | ||||||
331<\/td>\n | Annex G (informative)Trade names <\/td>\n<\/tr>\n | ||||||
332<\/td>\n | Annex H (informative)UML Notation H.1 General H.2 Class diagram Figure H.1 \u2013 Note Figure H.2 \u2013 Class Figure H.3 \u2013 Association <\/td>\n<\/tr>\n | ||||||
333<\/td>\n | Figure H.4 \u2013 Navigable Association Figure H.5 \u2013 Composition Figure H.6 \u2013 Aggregation Figure H.7 \u2013 Dependency <\/td>\n<\/tr>\n | ||||||
334<\/td>\n | Figure H.9 \u2013 Abstract class, Generalization and Interface Figure H.10 \u2013 Interface related notations <\/td>\n<\/tr>\n | ||||||
335<\/td>\n | H.3 Statechart diagram Figure H.11 \u2013 Multiplicity Figure H.12 \u2013 Enumeration datatype Figure H.13 \u2013 Elements of UML statechart diagrams <\/td>\n<\/tr>\n | ||||||
336<\/td>\n | H.4 Use case diagram Figure H.14 \u2013 Example of UML state chart diagram Figure H.15 \u2013 UML use case syntax <\/td>\n<\/tr>\n | ||||||
337<\/td>\n | H.5 Sequence diagram Figure H.16 \u2013 UML sequence diagram Figure H.17 \u2013 Empty UML sequence diagram frame <\/td>\n<\/tr>\n | ||||||
338<\/td>\n | Figure H.18 \u2013 Object with life line and activation Figure H.19 \u2013 Method calls Figure H.20 \u2013 Modeling guarded call and multiple calls <\/td>\n<\/tr>\n | ||||||
339<\/td>\n | Figure H.21 \u2013 Call to itself Figure H.22 \u2013 Continuation \/ StateInvariant <\/td>\n<\/tr>\n | ||||||
340<\/td>\n | Figure H.23 \u2013 Alternative fragment Figure H.24 \u2013 Option fragment Figure H.25 \u2013 Loop combination fragment Figure H.26 \u2013 Break notation <\/td>\n<\/tr>\n | ||||||
341<\/td>\n | H.6 Object diagram Figure H.27 \u2013 Sequence reference Figure H.28 \u2013 Objects Figure H.29 \u2013 Object association <\/td>\n<\/tr>\n | ||||||
342<\/td>\n | Annex I (informative)Physical Layer Examples I.1 General I.2 Interbus S I.3 PROFIBUS I.4 PROFINET <\/td>\n<\/tr>\n | ||||||
344<\/td>\n | Annex J (informative)Predefined SemanticIds J.1 General J.2 Data J.3 Images J.4 Documents <\/td>\n<\/tr>\n | ||||||
346<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Field device tool (FDT) interface specification – Object model integration profile. Common Language Infrastructure<\/b><\/p>\n |