BSI PD CLC/TR 62453-41:2009:2010 Edition
$215.11
Field device tool (FDT) interface specification – Object model integration profile. Common object model
Published By | Publication Date | Number of Pages |
BSI | 2010 | 330 |
This part of IEC 62453, which is a Technical report, defines how the common FDT principles are implemented based on the MS 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 shall be implemented as specified.
This part specifies FDT version 1.2.1.
PDF Catalog
PDF Pages | PDF Title |
---|---|
6 | CONTENTS |
15 | INTRODUCTION Figures Figure 1 – Part 41 of the IEC 62453 series |
16 | 1 Scope 2 Normative references 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Terms and definitions |
17 | 3.2 Abbreviations 3.3 Conventions 4 Implementation concept 4.1 Technological orientation |
18 | 4.2 Implementation of abstract FDT object model Figure 2 − Frame Application interfaces |
19 | Figure 3 − DTM interfaces |
20 | 4.3 Object interaction Figure 4 − FDT Client/server relationship via XML |
22 | Figure 5 − Data access and storage Figure 6 − Communication |
23 | 4.4 Implementation of DTM data persistence and synchronization Figure 7 − Documentation Figure 8 − Parameter verification in case of failsafe devices |
24 | 4.5 DTM state machine |
25 | Figure 9 − State machine of a DTM Tables Table 1 – Definition of DTM state machine |
27 | 5 General concepts 5.1 General 5.2 Overview of task related FDT interfaces Table 2 − Task related DTM interfaces |
28 | Table 3 − Task related DTM ActiveX® interfaces Table 4 − Task related FDT-Channel interfaces Table 5 − Task related Channel ActiveX( interfaces Table 6 − Task related BTM interfaces |
29 | Table 7 − Task related BTM ActiveX( interfaces Table 8 − Task related Frame Application interfaces |
30 | 5.3 Return values of interface methods 5.4 Dual interfaces 5.5 Unicode 5.6 Asynchronous versus synchronous behavior |
31 | 5.7 ProgIds 5.8 Implementation of DTM, DTM device type and hardware identification information Figure 10 − Device identification |
32 | Figure 11 − Structural overview |
33 | Table 9 − Semantic identification information |
34 | 5.9 Implementation of slave redundancy Table 10 − Regular expressions |
35 | 6 Implementation of FDT services: FDT interfaces 6.1 Overview of the FDT interfaces 6.2 FDT objects |
36 | Figure 12 − Interfaces of FDT objects – DTM and DtmActiveXControl |
37 | Figure 13 − Interfaces of FDT object – Frame Application Figure 14 − FDT objects – FDT-Channel |
38 | Figure 15 − FDT objects – BTM and BtmActiveXControl Table 11 − Availability of DTM methods in different states |
41 | Table 12 − Availability of Frame Application interfaces |
42 | 6.3 Device Type Manager |
83 | 6.4 DTM ActiveXControl |
85 | 6.5 FDT Channel |
105 | 6.6 Channel ActiveXControl |
108 | 6.7 Block Type Manager |
110 | 6.8 BTM ActiveXControl |
111 | 6.9 Frame Application |
147 | 7 FDT sequence charts 7.1 DTM peer to peer communication Figure 16 − Peer to peer connection between DTM and device |
148 | Figure 17 − Asynchronous connect (peer to peer) Figure 18 − Asynchronous disconnect (peer to peer) |
149 | 7.2 Nested communication Figure 19 − Asynchronous transaction (peer to peer) |
150 | Figure 20 − System-topology |
151 | Figure 21 − Generation of system topology by Frame Application |
152 | Figure 22 – Generation of system topology – Participation of DTM |
153 | Figure 23 – System connection (across communication hierarchy) |
154 | Figure 24 − Asynchronous transactions (system connection) |
155 | 7.3 Topology scan Figure 25 − Scan network topology |
156 | Figure 26 − Cancel topology scan |
157 | Figure 27 − Provisional topology scan |
158 | Figure 28 − Scan for communication hardware |
160 | 7.4 Registration of protocol specific FDT schemas Figure 29 − Manufacturer specific device identification |
161 | Figure 30 − Add protocol specific schemas to Frame Applications schema sub path |
162 | 7.5 Configuration of a fieldbus master Figure 31 − Frame Application reads protocol specific device identification information of DTMDeviceTypes |
163 | 7.6 Starting and releasing applications Figure 32 − Bus master configuration |
164 | 7.7 Channel access Figure 33 − Starting and releasing applications |
165 | 7.8 DCS Channel assignment Figure 34 − Channel access |
166 | Figure 35 − DCS channel assignment single DTM |
167 | Figure 36 − Sequence of channel assignement for a single DTM |
168 | Figure 37 − Modular DTM structure |
169 | 7.9 Printing of DTM specific documents Figure 38 − Channel assignment for modular DTMs |
170 | 7.10 Printing of Frame Application specific documents Figure 39 − Printing of DTM specific documents |
171 | Figure 40 − Printing of Frame Application specific documents |
172 | Figure 41 − Report generation (Frame Application style) |
173 | Figure 42 − Report generation (device vendor specific style) |
174 | 7.11 Propagation of changes |
175 | Figure 43 − Propagation of changes |
176 | 7.12 Locking |
177 | Figure 44 − Locking for non-synchronized DTMs |
179 | 7.13 Instantiation and release Figure 45 − Locking for synchronized DTMs Figure 46 − Instantiation of a new DTM |
180 | Figure 47 − Instantiation of an existing DTM Figure 48 − Instantiation of a DTM user interface |
181 | 7.14 Persistent storage of a DTM Figure 49 − Release of a DTM user interface |
182 | Figure 50 − State machine of instance data set Table 13 – Description of instance data set states |
183 | Figure 51 – Persistence states of a data set Table 14 – Description of persistent states |
184 | Figure 52 − Saving instance data of a DTM |
185 | 7.15 Audit trail Figure 53 − Copy and versioning of a DTM instance |
186 | Figure 54 − Audit trail |
187 | 7.16 Comparison of two instance data sets Figure 55 − Comparison without user interface |
188 | 7.17 Failsafe data access Figure 56 − Comparison with user interface |
189 | 7.18 Set or modify device address with user interface Figure 57 − Failsafe data access |
190 | 7.19 Set or modify known device addresses without user interface Figure 58 − Set or modify device address with user interface |
191 | 7.20 Display or modify all child device addresses with user interface Figure 59 − Set or modify known device addresses without user interface |
192 | 7.21 Device initiated data transfer Figure 60 − Display or modify all child device addresses with user interface |
193 | 7.22 Starting and releasing DTM user interface in modal dialog Figure 61 − Device initiated data transfer |
194 | Figure 62 − Modal DTM user interface |
195 | 7.23 Parent component handling redundant slave |
196 | 7.24 Initialization of a Channel ActiveX control Figure 63 − Handling of a redundant slave |
197 | Figure 64 − Init of Channel ActiveX with IFdtChannelActiveXControl2 |
198 | 7.25 DTM upgrade Figure 65 − Init of Channel ActiveX® without IFdtChannelActiveXControl2 |
199 | Figure 66 − Saving data from a DTM to be upgraded |
200 | 7.26 Usage of IDtmSingleDeviceDataAccess::ReadRequest / Write Request Figure 67 − Loading data in the replacement DTM |
201 | 7.27 Instantiation of DTM and BTM Figure 68 − Usage of IDtmSingleDeviceDataAccess |
202 | Figure 69 − General sequence of creation and instantiation of blocks |
203 | 8 Installation issues 8.1 Registry and device information Table 15 – Component categories |
204 | Table 16 – Combinations of categories Table 17 – Example for DTM registration |
206 | 8.2 Paths and file information |
207 | 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 |
208 | Table 20 – Helper objects for documentation |
209 | Annex A (normative) FDT IDL |
225 | Annex B (normative) Mapping of services to interface methods Table B.1 − General services Table B.2 − DTM service related to installation Table B.3 − DTM service related to DTM Information |
226 | Table B.4 − DTM services related to DTM state machine Table B.5 − DTM services related to function |
227 | Table B.6 − DTM services related to documentation Table B.7 − DTM services to access the instance data Table B.8 − DTM services to access diagnosis Table B.9 − DTM services to access to device data |
228 | Table B.10 − DTM services related to network management information Table B.11 − DTM services related to online operation 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 |
229 | Table B.15 − General channel service Table B.16 − Channel services for IO related information Table B.17 − Channel services related to communication |
230 | 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 event |
231 | 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 Table B.25 − FA services related to DTM data synchronization |
232 | Table B.26 − FA related to Presentation Table B.27 − FA services related to audit trail |
233 | Annex C (normative) FDT XML schemas Table C.1 – Description of general XML attributes |
238 | Table C.2 – Description of general XML elements |
240 | Table C.3 – Device classification ID |
241 | Table C.4 – Device classification according to IEC 62390 Annex G |
249 | Table C.5 – Description of applicationId attribute Table C.6 – Description of applicationId elements |
250 | Table C.7 – Description of user information attributes Table C.8 – Description of user information elements |
251 | Table C.9 – Description of DTM information attributes Table C.10 – Description of DTM information elements |
255 | Table C.11 – Description of function call attributes Table C.12 – Description of parameter document attributes |
256 | Table C.13 – Description of parameter document elements |
264 | Table C.14 – Description of documentation attributes Table C.15 – Description of documentation elements |
266 | Table C.16 – Description of protocols element |
267 | Table C.17 – Description of system tag attributes Table C.18 – Description of system tag elements |
268 | Table C.19 – Description of audit trail attributes Table C.20 – Description of audit trail elements |
269 | Table C.21 – Description of device status attribute Table C.22 – Description of device status elements |
271 | Table C.23 – Description of function attributes Table C.24 – Description of function elements |
275 | Table C.25 – Description of channel functions attributes Table C.26 – Description of channel function elements |
277 | Table C.27 – Description of comparison attribute Table C.28 – Description of comparison elements |
278 | Table C.29 – Description of fail safe attributes Table C.30 – Description of fail safe elements |
279 | Table C.31 – Description of topology scan elements |
280 | Table C.32 – Description of operation phase attribute Table C.33 – Description of operation phase element Table C.34 – Description of DTM init element |
281 | Table C.35 – Description of user message attributes Table C.36 – Description of user message elements |
282 | Table C.37 – Description of DTM info list elements |
283 | Table C.38 – Description of topology attributes |
284 | Table C.39 – Description of topology elements |
288 | Table C.40 – Description of device list attributes Table C.41 – Description of device list elements |
290 | Table C.42 – Description of gui label element Table C.43 – Description of DTM state element |
291 | Table C.44 – Description of frame version element Table C.45 – Description of connect response element |
292 | Table C.46 – Description of type request element Table C.47 – Description of scan request attributes |
293 | Table C.48 – Description of scan request elements |
295 | Table C.49 – Description of common identification attributes Table C.50 – Description of common identification element Table C.51 – Description of scan identification attributes |
296 | Table C.52 – Description of scan identification elements |
298 | Table C.53 – Description of device type identification element |
299 | Table C.54 – Description of item list attributes |
301 | Table C.55 – Description of item list elements |
305 | Table C.56 – Description of BTM data type attributes Table C.57 – Description of BTM data type elements |
307 | Table C.58 – Description of BTM information elements |
308 | Table C.59 – Description of BTM parameter elements |
310 | Table C.60 – Description of BTM init element Table C.61 – Description of BTM info list element |
312 | Annex D (informative) FDT XML styles – Documentation |
316 | Annex E (informative) FDT XSL Transformation |
317 | Figure E.1 – XSLT role |
318 | Annex F (normative) Channel schema Table F.1 – Description of basic channel attribute Table F.2 – Description of basic channel elements |
319 | Table F.3 – Description of xxx channel parameter attribute Table F.4 – Description of xxx channel parameter attribute |
320 | Annex G (normative) FDT version interoperability guide |
321 | Table G.1 − Interoperability between components of different versions |
325 | Annex H (informative) Implementation with .Net technology |
327 | Annex I (informative) Trade names |
328 | Bibliography |