1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationField device tool (FDT) interfacespecification Part 41: Object model integration profile Common object modelPD CLC/TR 62453-41:2009National forewordThis Published Document is the
2、 UK implementation of CLC/TR 62453-41:2009.The UK participation in its preparation was entrusted to Technical CommitteeAMT/7, Industrial communications: process measurement and control, including fieldbus.A list of organizations represented on this committee can be obtained onrequest to its secretar
3、y.This publication does not purport to include all the necessary provisions of acontract. Users are responsible for its correct application. BSI 2010ISBN 978 0 580 62567 1ICS 25.040.40; 35.100.05; 35.110Compliance with a British Standard cannot confer immunity fromlegal obligations.This Published Do
4、cument was published under the authority of theStandards Policy and Strategy Committee on 31 January 2010Amendments issued since publicationAmd. No. Date Text affectedBRITISH STANDARDPD CLC/TR 62453-41:2009TECHNICAL REPORT CLC/TR 62453-41 RAPPORT TECHNIQUE TECHNISCHER BERICHT November 2009 CENELEC E
5、uropean Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elektrotechnische Normung Central Secretariat: Avenue Marnix 17, B - 1000 Brussels 2009 CENELEC - All rights of exploitation in any form and by any means reserved worldwide f
6、or CENELEC members. Ref. No. CLC/TR 62453-41:2009 E ICS 25.040.40; 35.100.05; 35.110 English version Field device tool (FDT) interface specification - Part 41: Object model integration profile - Common object model (IEC/TR 62453-41:2009) Spcification des interfaces des outils des dispositifs de terr
7、ain (FDT) - Partie 41: Profil dintgration des modles objet - Modle objet commun (CEI/TR 62453-41:2009) Field Device Tool (FDT)-Schnittstellenspezifikation - Teil 41: Profil zur Integration des Objektmodells - Allgemeines Objektmodell (COM) (IEC/TR 62453-41:2009) This Technical Report was approved by
8、 CENELEC on 2009-10-01. CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland,
9、 Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. PD CLC/TR 62453-41:2009CLC/TR 62453-41:2009 - 2 - Foreword The text of document 65E/64/CDV, future edition 1 of IEC/TR 62453-41, prepared by Devices and integration in enterprise systems, of IEC TC 65, Industr
10、ial-process measurement, control and automation, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as CLC/TR 62453-41 on 2009-10-01. Annex ZA has been added by CENELEC. _ Endorsement notice The text of the Technical Report IEC/TR 62453-41:2009 was approved by CENELEC as a Te
11、chnical Report without any modification. _ PD CLC/TR 62453-41:2009- 3 - CLC/TR 62453-41:2009 Annex ZA (normative) Normative references to international publications with their corresponding European publications The following referenced documents are indispensable for the application of this documen
12、t. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. NOTE When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD applies. Publica
13、tion Year Title EN/HD Year IEC 61784 series Industrial communication networks - Profiles EN 61784 series IEC 62453-1 2009 Field device tool (FDT) interface specification - Part 1: Overview and guidance EN 62453-1 2009 IEC 62453-2 2009 Field device tool (FDT) interface specification - Part 2: Concept
14、s and detailed description EN 62453-2 2009 _ PD CLC/TR 62453-41:2009 2 TR 62453-41 IEC:2009(E) CONTENTS INTRODUCTION.13 1 Scope.14 2 Normative references .14 3 Terms, definitions, symbols, abbreviated terms and conventions 14 3.1 Terms and definitions 14 3.2 Abbreviations 15 3.3 Conventions 15 4 Imp
15、lementation concept15 4.1 Technological orientation 15 4.2 Implementation of abstract FDT object model16 4.2.1 General .16 4.2.2 FDT Frame Application (FA) 16 4.2.3 Device Type Manager (DTM) .17 4.2.4 Presentation object17 4.2.5 FDT-Channel object.17 4.3 Object interaction 18 4.3.1 Parameter interch
16、ange via XML.18 4.3.2 Examples of usage 19 4.4 Implementation of DTM data persistence and synchronization.21 4.4.1 Persistence overview.21 4.4.2 Persistence interfaces .22 4.5 DTM state machine .22 5 General concepts .25 5.1 General .25 5.2 Overview of task related FDT interfaces 25 5.3 Return value
17、s of interface methods .28 5.4 Dual interfaces 28 5.5 Unicode.28 5.6 Asynchronous versus synchronous behavior .28 5.7 ProgIds .29 5.8 Implementation of DTM, DTM device type and hardware identification information 29 5.8.1 Device identification 29 5.8.2 Protocol specific transformation style sheet (x
18、sl) .31 5.8.3 Semantic identification information 31 5.8.4 Device assignment 31 5.8.5 Regular expression specification .32 5.9 Implementation of slave redundancy .32 5.9.1 General .32 5.9.2 Topology import/export32 6 Implementation of FDT services: FDT interfaces.33 6.1 Overview of the FDT interface
19、s .33 6.2 FDT objects.33 6.2.1 FDT object model 33 6.2.2 Avalability of interface methods .36 PD CLC/TR 62453-41:2009TR 62453-41 IEC:2009(E) 3 6.3 Device Type Manager40 6.3.1 Interface IDtm40 6.3.2 Interface IDtm249 6.3.3 Interface IDtmActiveXInformation 51 6.3.4 Interface IDtmApplication.52 6.3.5 I
20、nterface IDtmChannel.54 6.3.6 Interface IDtmDocumentation 55 6.3.7 Interface IDtmDiagnosis 56 6.3.8 Interface IDtmImportExport58 6.3.9 Interface IDtmInformation 60 6.3.10 Interface IDtmInformation2 61 6.3.11 Interface IDtmOnlineDiagnosis 62 6.3.12 Interface IDtmOnlineParameter .63 6.3.13 Interface I
21、DtmParameter .66 6.3.14 Interface IFdtCommunicationEvents 67 6.3.15 Interface IFdtCommunicationEvents2 70 6.3.16 Interface IFdtEvents 71 6.3.17 Interface IDtmHardwareIdentification.74 6.3.18 Interface IDtmSingleDeviceDataAccess .76 6.3.19 Interface IDtmSingleInstanceDataAccess 79 6.4 DTM ActiveXCont
22、rol 81 6.4.1 Interface IDtmActiveXControl.81 6.4.2 Init.81 6.4.3 PrepareToRelease.82 6.5 FDT Channel.83 6.5.1 Interface IFdtChannel 83 6.5.2 Interface IFdtChannelActiveXInformation.85 6.5.3 Interface IFdtCommunication.88 6.5.4 Interface IFdtChannelSubTopology95 6.5.5 Interface IFdtChannelSubTopology
23、299 6.5.6 Interface IFdtChannelScan 99 6.5.7 Interface IFdtFunctionBlockData101 6.6 Channel ActiveXControl 103 6.6.1 Interface IFdtChannelActiveXControl .103 6.6.2 Interface IFdtChannelActiveXControl2 .105 6.7 Block Type Manager106 6.7.1 Interface IBtm106 6.7.2 Interface IBtmInformation 107 6.7.3 In
24、terface IBtmParameter107 6.8 BTM ActiveXControl 108 6.8.1 General .108 6.8.2 Interface IBtmActiveXControl.108 6.9 Frame Application .109 6.9.1 Interface IDtmEvents .109 6.9.2 Interface IDtmEvents2 .118 6.9.3 Interface IDtmScanEvents .119 6.9.4 Interface IDtmAuditTrailEvents 121 6.9.5 Interface IFdtA
25、ctiveX .123 6.9.6 Interface IFdtActiveX2 .124 PD CLC/TR 62453-41:2009 4 TR 62453-41 IEC:2009(E) 6.9.7 Interface IFdtBulkData.127 6.9.8 Interface IFdtContainer129 6.9.9 Interface IFdtDialog .132 6.9.10 Interface IFdtTopology.133 6.9.11 Interface IDtmRedundancyEvents139 6.9.12 Interface IDtmSingleDevi
26、ceDataAccessEvents 140 6.9.13 Interface IDtmSingleInstanceDataAccessEvents143 6.9.14 Interface IFdtBtmTopology.144 7 FDT sequence charts .145 7.1 DTM peer to peer communication145 7.1.1 General .145 7.1.2 Establish a peer-to-peer connection between DTM and device 145 7.1.3 Asynchronous connect for a
27、 peer-to-peer connection 145 7.1.4 Asynchronous disconnect for a peer-to-peer connection 146 7.1.5 Asynchronous transaction for a peer-to-peer connection146 7.2 Nested communication 147 7.2.1 General .147 7.2.2 Generate system topology .148 7.2.3 Establish a system connection between DTM and device.
28、150 7.2.4 Asynchronous transaction for a system connection151 7.3 Topology scan.153 7.3.1 Scan network.153 7.3.2 Cancel topology scan 153 7.3.3 Provisional scan result notifications.154 7.3.4 Scan for communication hardware.155 7.3.5 Manufacturer specific device identification.156 7.4 Registration o
29、f protocol specific FDT schemas 158 7.5 Configuration of a fieldbus master .160 7.6 Starting and releasing applications161 7.7 Channel access.162 7.8 DCS Channel assignment163 7.9 Printing of DTM specific documents.167 7.10 Printing of Frame Application specific documents168 7.10.1 General .168 7.10
30、.2 Processing a document .169 7.10.3 Rules for use of DTM specific style sheets 171 7.11 Propagation of changes.172 7.12 Locking .174 7.12.1 Locking for non-synchronized DTMs 174 7.12.2 Locking for synchronized DTMs.175 7.13 Instantiation and release .177 7.13.1 Instantiation of a new DTM 177 7.13.2
31、 Instantiation of an existing DTM.177 7.13.3 Instantiation of a DTM ActiveX user interface178 7.13.4 Release of a DTM user interface .179 7.14 Persistent storage of a DTM179 7.14.1 State machine of instance data179 7.14.2 Saving instance data of a DTM 181 7.14.3 Reload of a DTM object for another in
32、stance .182 PD CLC/TR 62453-41:2009TR 62453-41 IEC:2009(E) 5 7.14.4 Copy and versioning of a DTM instance.182 7.15 Audit trail.183 7.16 Comparison of two instance data sets .185 7.16.1 Comparison without user interface.185 7.16.2 Comparison with user interface .185 7.17 Failsafe data access186 7.18
33、Set or modify device address with user interface .187 7.19 Set or modify known device addresses without user interface188 7.20 Display or modify all child device addresses with user interface 189 7.21 Device initiated data transfer.190 7.22 Starting and releasing DTM user interface in modal dialog 1
34、91 7.23 Parent component handling redundant slave .193 7.24 Initialization of a Channel ActiveX control194 7.24.1 General .194 7.24.2 Supports IFdtChannelActiveXcontrol2195 7.24.3 Does not support IFdtChannelActiveXControl2 195 7.25 DTM upgrade 196 7.25.1 General .196 7.25.2 Saving data from a DTM t
35、o be upgraded196 7.25.3 Loading data in the replacement DTM .197 7.26 Usage of IDtmSingleDeviceDataAccess:ReadRequest / Write Request 198 7.27 Instantiation of DTM and BTM .199 8 Installation issues.201 8.1 Registry and device information 201 8.1.1 Visibility of business objects of a DTM.201 8.1.2 C
36、omponent categories.201 8.1.3 Registry entries .202 8.1.4 Installation issues202 8.1.5 Microsofts standard component categories manager.203 8.1.6 Building a Frame Application-database of supported devices.203 8.1.7 DTM registration203 8.2 Paths and file information204 8.2.1 Path information provided
37、 by a DTM204 8.2.2 Paths and persistency .204 8.2.3 Multi-user systems 205 9 Description of data types, parameters and structures .205 9.1 Ids.205 9.2 Data type definitions205 Annex A (normative) FDT IDL 207 Annex B (normative) Mapping of services to interface methods223 Annex C (normative) FDT XML
38、schemas231 Annex D (informative) FDT XML styles Documentation .310 Annex E (informative) FDT XSL Transformation.314 Annex F (normative) Channel schema .316 Annex G (normative) FDT version interoperability guide 318 Annex H (informative) Implementation with .Net technology.323 Annex I (informative) T
39、rade names 325 PD CLC/TR 62453-41:2009 6 TR 62453-41 IEC:2009(E) Bibliography326 Figure 1 Part 41 of the IEC 62453 series .13 Figure 2 Frame Application interfaces16 Figure 3 DTM interfaces 17 Figure 4 FDT Client/server relationship via XML 18 Figure 5 Data access and storage20 Figure 6 Communicatio
40、n 20 Figure 7 Documentation.21 Figure 8 Parameter verification in case of failsafe devices .21 Figure 9 State machine of a DTM.23 Figure 10 Device identification.29 Figure 11 Structural overview 30 Figure 12 Interfaces of FDT objects DTM and DtmActiveXControl.34 Figure 13 Interfaces of FDT object Fr
41、ame Application.35 Figure 14 FDT objects FDT-Channel.35 Figure 15 FDT objects BTM and BtmActiveXControl .36 Figure 16 Peer to peer connection between DTM and device.145 Figure 17 Asynchronous connect (peer to peer).146 Figure 18 Asynchronous disconnect (peer to peer) 146 Figure 19 Asynchronous trans
42、action (peer to peer)147 Figure 20 System-topology 148 Figure 21 Generation of system topology by Frame Application .149 Figure 22 Generation of system topology Participation of DTM .150 Figure 23 System connection (across communication hierarchy)151 Figure 24 Asynchronous transactions (system conne
43、ction) 152 Figure 25 Scan network topology.153 Figure 26 Cancel topology scan.154 Figure 27 Provisional topology scan.155 Figure 28 Scan for communication hardware .156 Figure 29 Manufacturer specific device identification .158 Figure 30 Add protocol specific schemas to Frame Applications schema sub
44、 path .159 Figure 31 Frame Application reads protocol specific device identification information of DTMDeviceTypes160 Figure 32 Bus master configuration161 Figure 33 Starting and releasing applications.162 Figure 34 Channel access .163 Figure 35 DCS channel assignment single DTM.164 Figure 36 Sequen
45、ce of channel assignement for a single DTM 165 Figure 37 Modular DTM structure.166 Figure 38 Channel assignment for modular DTMs167 Figure 39 Printing of DTM specific documents .168 Figure 40 Printing of Frame Application specific documents.169 PD CLC/TR 62453-41:2009TR 62453-41 IEC:2009(E) 7 Figure
46、 41 Report generation (Frame Application style).170 Figure 42 Report generation (device vendor specific style) 171 Figure 43 Propagation of changes .173 Figure 44 Locking for non-synchronized DTMs.175 Figure 45 Locking for synchronized DTMs .177 Figure 46 Instantiation of a new DTM.177 Figure 47 Ins
47、tantiation of an existing DTM .178 Figure 48 Instantiation of a DTM user interface178 Figure 49 Release of a DTM user interface 179 Figure 50 State machine of instance data set.180 Figure 51 Persistence states of a data set .181 Figure 52 Saving instance data of a DTM.182 Figure 53 Copy and versioni
48、ng of a DTM instance .183 Figure 54 Audit trail .184 Figure 55 Comparison without user interface .185 Figure 56 Comparison with user interface 186 Figure 57 Failsafe data access 187 Figure 58 Set or modify device address with user interface188 Figure 59 Set or modify known device addresses without u
49、ser interface 189 Figure 60 Display or modify all child device addresses with user interface .190 Figure 61 Device initiated data transfer191 Figure 62 Modal DTM user interface 192 Figure 63 Handling of a redundant slave194 Figure 64 Init of Channel ActiveX with IFdtChannelActiveXControl2.195 Figure 65 Init of Channel ActiveX without IFdtChannelActiveXContro
