BSI PD CLC/TR IEC 62453-41:2019
$215.11
Field device tool (FDT) interface specification – Object model integration profile. Common object model
Published By | Publication Date | Number of Pages |
BSI | 2019 | 332 |
This part of IEC 62453, which is a technical report, defines how the common FDT principles are implemented based on the Microsoft1 COM technology, including the object behavior and object interaction via COM interfaces.
This part specifies the technology-specific implementation of the protocol-specific functionality and communication services.
This part of IEC 62453 is informative, however when this part is applied its requirements need to be implemented as specified.
This part specifies FDT version 1.2.1.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
7 | CONTENTS |
17 | FOREWORD |
19 | INTRODUCTION Figures Figure 1 – Part 41 of the IEC 62453 series |
20 | 1 Scope 2 Normative references 3 Terms, definitions, abbreviations and conventions 3.1 Terms and definitions |
21 | 3.2 Abbreviations 3.3 Conventions |
22 | 4 Implementation concept 4.1 Technological orientation 4.2 Implementation of abstract FDT object model 4.2.1 General 4.2.2 FDT Frame Application (FA) |
23 | 4.2.3 Device Type Manager (DTM) Figure 2 − Frame Application interfaces Figure 3 − DTM interfaces |
24 | 4.2.4 Presentation object 4.2.5 FDT-Channel object 4.3 Object interaction 4.3.1 Parameter interchange via XML Figure 4 − FDT Client/server relationship via XML |
26 | 4.3.2 Examples of usage Figure 5 − Data access and storage |
27 | Figure 6 − Communication Figure 7 − Documentation |
28 | 4.4 Implementation of DTM data persistence and synchronization 4.4.1 Persistence overview Figure 8 − Parameter verification in case of failsafe devices |
29 | 4.4.2 Persistence interfaces 4.5 DTM state machine Figure 9 − State machine of a DTM |
30 | Tables Table 1 – Definition of DTM state machine |
31 | 5 General concepts 5.1 General 5.2 Overview of task related FDT interfaces Table 2 − Task related DTM interfaces |
32 | Table 3 − Task related DTM ActiveX® interfaces Table 4 − Task related FDT-Channel interfaces Table 5 − Task related Channel ActiveX( interfaces |
33 | Table 6 − Task related BTM interfaces Table 7 − Task related BTM ActiveX( interfaces Table 8 − Task related Frame Application interfaces |
34 | 5.3 Return values of interface methods 5.4 Dual interfaces 5.5 Unicode 5.6 Asynchronous versus synchronous behavior |
35 | 5.7 ProgIds 5.8 Implementation of DTM, DTM device type and hardware identification information 5.8.1 Device identification Figure 10 − Device identification |
37 | Figure 11 − Structural overview |
38 | 5.8.2 Protocol-specific transformation style sheet (xsl) 5.8.3 Semantic identification information 5.8.4 Device assignment Table 9 − Semantic identification information |
39 | 5.8.5 Regular expression specification 5.9 Implementation of slave redundancy 5.9.1 General Table 10 − Regular expressions |
40 | 5.9.2 Topology import/export 6 Implementation of FDT services: FDT interfaces 6.1 Overview of the FDT interfaces 6.2 FDT objects 6.2.1 FDT object model |
41 | Figure 12 − Interfaces of FDT objects – DTM and DtmActiveXControl |
42 | Figure 13 − Interfaces of FDT object – Frame Application Figure 14 − FDT objects – FDT-Channel |
43 | 6.2.2 Avalability of interface methods Figure 15 − FDT objects – BTM and BtmActiveXControl |
44 | Table 11 − Availability of DTM methods in different states |
46 | Table 12 − Availability of Frame Application interfaces |
47 | 6.3 Device Type Manager 6.3.1 Interface IDtm |
56 | 6.3.2 Interface IDtm2 |
57 | 6.3.3 Interface IDtmActiveXInformation |
59 | 6.3.4 Interface IDtmApplication |
61 | 6.3.5 Interface IDtmChannel |
62 | 6.3.6 Interface IDtmDocumentation |
63 | 6.3.7 Interface IDtmDiagnosis |
65 | 6.3.8 Interface IDtmImportExport |
67 | 6.3.9 Interface IDtmInformation |
68 | 6.3.10 Interface IDtmInformation2 |
69 | 6.3.11 Interface IDtmOnlineDiagnosis |
70 | 6.3.12 Interface IDtmOnlineParameter |
73 | 6.3.13 Interface IDtmParameter |
74 | 6.3.14 Interface IFdtCommunicationEvents |
77 | 6.3.15 Interface IFdtCommunicationEvents2 |
78 | 6.3.16 Interface IFdtEvents |
81 | 6.3.17 Interface IDtmHardwareIdentification |
83 | 6.3.18 Interface IDtmSingleDeviceDataAccess |
86 | 6.3.19 Interface IDtmSingleInstanceDataAccess |
88 | 6.4 DTM ActiveXControl 6.4.1 Interface IDtmActiveXControl 6.4.2 Init |
89 | 6.4.3 PrepareToRelease |
90 | 6.5 FDT Channel 6.5.1 Interface IFdtChannel |
93 | 6.5.2 Interface IFdtChannelActiveXInformation |
95 | 6.5.3 Interface IFdtCommunication |
102 | 6.5.4 Interface IFdtChannelSubTopology |
106 | 6.5.5 Interface IFdtChannelSubTopology2 6.5.6 Interface IFdtChannelScan |
108 | 6.5.7 Interface IFdtFunctionBlockData |
110 | 6.6 Channel ActiveXControl 6.6.1 Interface IFdtChannelActiveXControl |
111 | 6.6.2 Interface IFdtChannelActiveXControl2 |
112 | 6.7 Block Type Manager |
113 | 6.7.1 Interface IBtm |
114 | 6.7.2 Interface IBtmInformation 6.7.3 Interface IBtmParameter |
115 | 6.8 BTM ActiveXControl 6.8.1 General 6.8.2 Interface IBtmActiveXControl |
116 | 6.9 Frame Application 6.9.1 Interface IDtmEvents |
125 | 6.9.2 Interface IDtmEvents2 |
126 | 6.9.3 Interface IDtmScanEvents |
128 | 6.9.4 Interface IDtmAuditTrailEvents |
130 | 6.9.5 Interface IFdtActiveX |
131 | 6.9.6 Interface IFdtActiveX2 |
134 | 6.9.7 Interface IFdtBulkData |
136 | 6.9.8 Interface IFdtContainer |
139 | 6.9.9 Interface IFdtDialog |
140 | 6.9.10 Interface IFdtTopology |
146 | 6.9.11 Interface IDtmRedundancyEvents |
147 | 6.9.12 Interface IDtmSingleDeviceDataAccessEvents |
150 | 6.9.13 Interface IDtmSingleInstanceDataAccessEvents |
151 | 6.9.14 Interface IFdtBtmTopology |
152 | 7 FDT sequence charts 7.1 DTM peer to peer communication 7.1.1 General 7.1.2 Establish a peer-to-peer connection between DTM and device 7.1.3 Asynchronous connect for a peer-to-peer connection Figure 16 − Peer to peer connection between DTM and device |
153 | 7.1.4 Asynchronous disconnect for a peer-to-peer connection 7.1.5 Asynchronous transaction for a peer-to-peer connection Figure 17 − Asynchronous connect (peer to peer) Figure 18 − Asynchronous disconnect (peer to peer) |
154 | 7.2 Nested communication 7.2.1 General Figure 19 − Asynchronous transaction (peer to peer) |
155 | 7.2.2 Generate system topology Figure 20 − System-topology |
156 | Figure 21 − Generation of system topology by Frame Application |
157 | 7.2.3 Establish a system connection between DTM and device Figure 22 – Generation of system topology – Participation of DTM |
158 | 7.2.4 Asynchronous transaction for a system connection Figure 23 – System connection (across communication hierarchy) |
159 | 7.3 Topology scan 7.3.1 Scan network Figure 24 − Asynchronous transactions (system connection) |
160 | 7.3.2 Cancel topology scan Figure 25 − Scan network topology |
161 | 7.3.3 Provisional scan result notifications Figure 26 − Cancel topology scan |
162 | 7.3.4 Scan for communication hardware Figure 27 − Provisional topology scan |
163 | 7.3.5 Manufacturer-specific device identification Figure 28 − Scan for communication hardware |
165 | 7.4 Registration of protocol-specific FDT schemas Figure 29 − Manufacturer-specific device identification |
166 | Figure 30 − Add protocol-specific schemas to Frame Applications schema sub path |
167 | 7.5 Configuration of a fieldbus master Figure 31 − Frame Application reads protocol-specificdevice identification information of DTMDeviceTypes |
168 | 7.6 Starting and releasing applications Figure 32 − Bus master configuration |
169 | 7.7 Channel access Figure 33 − Starting and releasing applications |
170 | 7.8 DCS Channel assignment Figure 34 − Channel access |
171 | Figure 35 − DCS channel assignment single DTM |
172 | Figure 36 − Sequence of channel assignement for a single DTM |
173 | Figure 37 − Modular DTM structure |
174 | 7.9 Printing of DTM-specific documents Figure 38 − Channel assignment for modular DTMs |
175 | 7.10 Printing of Frame Application-specific documents 7.10.1 General Figure 39 − Printing of DTM-specific documents |
176 | 7.10.2 Processing a document Figure 40 − Printing of Frame Application-specific documents |
177 | Figure 41 − Report generation (Frame Application style) |
178 | 7.10.3 Rules for use of DTM-specific style sheets Figure 42 − Report generation (device vendor-specific style) |
179 | 7.11 Propagation of changes Figure 43 − Propagation of changes |
180 | 7.12 Locking 7.12.1 Locking for non-synchronized DTMs |
181 | 7.12.2 Locking for synchronized DTMs Figure 44 − Locking for non-synchronized DTMs |
182 | Figure 45 − Locking for synchronized DTMs |
183 | 7.13 Instantiation and release 7.13.1 Instantiation of a new DTM 7.13.2 Instantiation of an existing DTM Figure 46 − Instantiation of a new DTM |
184 | 7.13.3 Instantiation of a DTM ActiveX( user interface 7.13.4 Release of a DTM user interface Figure 47 − Instantiation of an existing DTM Figure 48 − Instantiation of a DTM user interface |
185 | 7.14 Persistent storage of a DTM 7.14.1 State machine of instance data Figure 49 − Release of a DTM user interface |
186 | Figure 50 − State machine of instance data set Table 13 – Description of instance data set states |
187 | 7.14.2 Saving instance data of a DTM Figure 51 – Persistence states of a data set Table 14 – Description of persistent states |
188 | 7.14.3 Reload of a DTM object for another instance 7.14.4 Copy and versioning of a DTM instance Figure 52 − Saving instance data of a DTM |
189 | 7.15 Audit trail Figure 53 − Copy and versioning of a DTM instance |
190 | 7.16 Comparison of two instance data sets 7.16.1 Comparison without user interface Figure 54 − Audit trail |
191 | 7.16.2 Comparison with user interface Figure 55 − Comparison without user interface |
192 | 7.17 Failsafe data access Figure 56 − Comparison with user interface |
193 | 7.18 Set or modify device address with user interface Figure 57 − Failsafe data access |
194 | 7.19 Set or modify known device addresses without user interface Figure 58 − Set or modify device address with user interface |
195 | 7.20 Display or modify all child device addresses with user interface Figure 59 − Set or modify known device addresses without user interface |
196 | 7.21 Device initiated data transfer Figure 60 − Display or modify all child device addresses with user interface |
197 | 7.22 Starting and releasing DTM user interface in modal dialog Figure 61 − Device initiated data transfer |
198 | 7.23 Parent component handling redundant slave Figure 62 − Modal DTM user interface |
199 | Figure 63 − Handling of a redundant slave |
200 | 7.24 Initialization of a Channel ActiveX control 7.24.1 General 7.24.2 Supports IFdtChannelActiveXcontrol2 7.24.3 Does not support IFdtChannelActiveXControl2 Figure 64 − Init of Channel ActiveX with IFdtChannelActiveXControl2 |
201 | 7.25 DTM upgrade 7.25.1 General 7.25.2 Saving data from a DTM to be upgraded Figure 65 − Init of Channel ActiveX® without IFdtChannelActiveXControl2 |
202 | 7.25.3 Loading data in the replacement DTM Figure 66 − Saving data from a DTM to be upgraded |
203 | 7.26 Usage of IDtmSingleDeviceDataAccess::ReadRequest / Write Request Figure 67 − Loading data in the replacement DTM |
204 | 7.27 Instantiation of DTM and BTM Figure 68 − Usage of IDtmSingleDeviceDataAccess |
205 | Figure 69 − General sequence of creation and instantiation of blocks |
206 | 8 Installation issues 8.1 Registry and device information 8.1.1 Visibility of business objects of a DTM 8.1.2 Component categories Table 15 – Component categories |
207 | 8.1.3 Registry entries 8.1.4 Installation issues Table 16 – Combinations of categories Table 17 – Example for DTM registration |
208 | 8.1.5 Microsoft’s standard component categories manager 8.1.6 Building a Frame Application-database of supported devices 8.1.7 DTM registration |
209 | 8.2 Paths and file information 8.2.1 Path information provided by a DTM 8.2.2 Paths and persistency 8.2.3 Multi-user systems |
210 | 9 Description of data types, parameters and structures 9.1 Ids 9.2 Data type definitions Table 18 – FDT-specific Ids Table 19 – Basic data types |
211 | Table 20 – Helper objects for documentation |
212 | Annex A (normative)FDT IDL |
228 | Annex B (normative)Mapping of services to interface methods B.1 General B.2 DTM services Table B.1 − General services Table B.2 − DTM services related to installation |
229 | Table B.3 − DTM services related to DTM information Table B.4 − DTM services related to DTM state machine |
230 | Table B.5 − DTM services related to function Table B.6 − DTM services related to documentation Table B.7 − DTM services to access the instance data |
231 | Table B.8 − DTM services to access diagnosis Table B.9 − DTM services to access the device data Table B.10 − DTM services related to network management information Table B.11 − DTM services related to online operation |
232 | B.3 Presentation object services B.4 General channel services Table B.12 − DTM services related to FDT-Channel objects Table B.13 − DTM services related to import and export Table B.14 − DTM services related to data synchronization |
233 | B.5 Process channel services B.6 Communication Channel Services Table B.15 − General channel services Table B.16 − Channel services for IO related information Table B.17 − Channel services related to communication |
234 | B.7 Frame Application Services Table B.18 − Channel services related sub-topology management Table B.19 − Channel services related to functions Table B.20 − Channel services related to scan Table B.21 − FA services related to general events |
235 | Table B.22 − FA services related to topology management Table B.23 − FA services related to redundancy Table B.24 − FA services related to storage of DTM data |
236 | Table B.25 − FA services related to DTM data synchronization Table B.26 − FA services related to presentation Table B.27 − FA services related to audit trail |
237 | Annex C (normative)FDT XML schemas C.1 General C.2 FDTDataTypesSchema Table C.1 – Description of general XML attributes |
242 | Table C.2 – Description of general XML elements |
244 | Table C.3 – Device classification ID |
245 | Table C.4 – Device classification according to IEC TR 62390:2005, Annex G |
253 | C.3 FDTApplicationIdSchema C.4 FDTUserInformationSchema Table C.5 – Description of applicationId attribute Table C.6 – Description of applicationId elements |
254 | Table C.7 – Description of user information attributes Table C.8 – Description of user information elements |
255 | C.5 DTMInformationSchema Table C.9 – Description of DTM information attributes Table C.10 – Description of DTM information elements |
258 | C.6 DTMFunctionCallSchema |
259 | C.7 DTMParameterSchema Table C.11 – Description of function call attributes Table C.12 – Description of parameter document attributes |
260 | Table C.13 – Description of parameter document elements |
267 | C.8 DTMDocumentationSchema |
268 | Table C.14 – Description of documentation attributes Table C.15 – Description of documentation elements |
269 | C.9 DTMProtocolsSchema |
270 | C.10 DTMSystemTagListSchema Table C.16 – Description of protocols element Table C.17 – Description of system tag attributes Table C.18 – Description of system tag elements |
271 | C.11 DTMAuditTrailSchema |
272 | Table C.19 – Description of audit trail attributes Table C.20 – Description of audit trail elements |
273 | C.12 DTMDeviceStatusSchema Table C.21 – Description of device status attribute Table C.22 – Description of device status elements |
274 | C.13 DTMFunctionsSchema Table C.23 – Description of function attributes |
275 | Table C.24 – Description of function elements |
278 | C.14 DTMChannelFunctionsSchema Table C.25 – Description of channel functions attributes |
279 | Table C.26 – Description of channel function elements |
281 | C.15 DTMOnlineCompareSchema Table C.27 – Description of comparison attribute Table C.28 – Description of comparison elements |
282 | C.16 FDTFailSafeDataSchema C.17 DTMTopologyScanSchema Table C.29 – Description of fail safe attributes Table C.30 – Description of fail safe elements |
283 | C.18 FDTOperationPhaseSchema Table C.31 – Description of topology scan elements Table C.32 – Description of operation phase attribute Table C.33 – Description of operation phase element |
284 | C.19 DTMInitSchema C.20 FDTUserMessageSchema Table C.34 – Description of DTM init element Table C.35 – Description of user message attributes |
285 | Table C.36 – Description of user message elements |
286 | C.21 DTMInfoListSchema Table C.37 – Description of DTM info list elements |
287 | C.22 FDTTopologyImportExportSchema Table C.38 – Description of topology attributes Table C.39 – Description of topology elements |
291 | C.23 DTMDeviceListSchema Table C.40 – Description of device list attributes |
292 | Table C.41 – Description of device list elements |
293 | C.24 DTMSystemGuiLabelSchema C.25 DTMStateSchema Table C.42 – Description of gui label element |
294 | C.26 DTMEnvironmentSchema Table C.43 – Description of DTM state element Table C.44 – Description of frame version element |
295 | C.27 FDTConnectResponseSchema C.28 TypeRequestSchema Table C.45 – Description of connect response element Table C.46 – Description of type request element |
296 | C.29 FDTScanRequestSchema Table C.47 – Description of scan request attributes Table C.48 – Description of scan request elements |
297 | C.30 FDTxxxIdentSchema C.31 FDTxxxDeviceTypeIdentSchema |
298 | C.32 FDTxxxScanIdentSchema C.33 DTMIdentSchema Table C.49 – Description of common identification attributes |
299 | C.34 DTMScanIdentSchema Table C.50 – Description of common identification element Table C.51 – Description of scan identification attributes Table C.52 – Description of scan identification elements |
301 | C.35 DTMDeviceTypeIdentSchema Table C.53 – Description of device type identification element |
303 | C.36 DTMItemListSchema Table C.54 – Description of item list attributes |
304 | Table C.55 – Description of item list elements |
308 | C.37 BtmDataTypesSchema Table C.56 – Description of BTM data type attributes |
309 | Table C.57 – Description of BTM data type elements |
310 | C.38 BtmInformationSchema Table C.58 – Description of BTM information elements |
311 | C.39 BtmParameterSchema Table C.59 – Description of BTM parameter elements |
313 | C.40 BtmInitSchema Table C.60 – Description of BTM init element |
314 | C.41 BtmInfoListSchema Table C.61 – Description of BTM info list element |
315 | Annex D (informative)FDT XML styles – Documentation |
319 | Annex E (informative)FDT XSL Transformation E.1 Identification transformation E.2 Hint |
320 | Figure E.1 – XSLT role |
321 | Annex F (normative)Channel schema F.1 FDTBasicChannelParameterSchema Table F.1 – Description of basic channel attribute Table F.2 – Description of basic channel elements |
322 | F.2 Template for Channel Schema Table F.3 – Description of xxx channel parameter attribute Table F.4 – Description of xxx channel parameter elements |
323 | Annex G (normative)FDT version interoperability guide G.1 Overview G.2 General G.3 Component interoperability |
324 | Table G.1 − Interoperability between components of different versions |
325 | G.4 FDT type library G.5 DTM and device versions G.6 Persistence |
326 | G.7 Nested communication G.7.1 General G.7.2 Data exchange G.7.3 Communication channel upgrade G.7.4 Scenarios |
327 | G.7.5 OnAddChild G.8 Implementation hints G.8.1 Interfaces G.8.2 Persistence |
328 | Annex H (informative)Implementation with Net technology H.1 How FDT supports .NET based development H.2 Microsoft .NET Framework 1.1 and 2.0 compatibility H.3 Side-by-side installation and related problems |
329 | H.4 How to avoid compatibility issues |
330 | Annex I (informative)Trade names |
331 | Bibliography |