GB/T 29618.41-2013 English PDFUS$7114.00 · In stock
Delivery: <= 10 days. True-PDF full-copy in English will be manually translated and delivered via email. GB/T 29618.41-2013: Field device tool (FDT) interface specification -- Part 41: Object model integration profile -- Common object model Status: Valid
Similar standardsGB/T 33008.1 GB/T 33009.1 GB/T 33009.2 GB/T 29618.5110 GB/T 29618.5120 GB/T 29618.42Basic dataStandard ID: GB/T 29618.41-2013 (GB/T29618.41-2013)Description (Translated English): Field device tool (FDT) interface specification -- Part 41: Object model integration profile -- Common object model Sector / Industry: National Standard (Recommended) Classification of Chinese Standard: N10 Classification of International Standard: 25.040 Word Count Estimation: 356,371 Quoted Standard: GB/T 29618.1-2013; GB/T 29618.2-2013; ISO/IEC 19501-2005 Adopted Standard: IEC 62453-41-2009, IDT Regulation (derived from): National Standards Bulletin 2013 No. 10 Issuing agency(ies): General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China, Standardization Administration of the People's Republic of China Summary: This standard specifies: how to achieve universal FDT technology based MSCOM principle, including through COM interfaces object behavior and object interactions. This standard specifies the protocol-specific functions and communication services specific t GB/T 29618.41-2013: Field device tool (FDT) interface specification -- Part 41: Object model integration profile -- Common object model---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order. Field device tool (FDT) interface specification.Part 41. Objcect model integration profile.Common object model ICS 25.040 N10 National Standards of People's Republic of China Field device tool (FDT) interface specification Part 41. Object model integration profiles Common Object Model Fielddevicetool (FDT) interfacespecification- Part 41. Objectmodelintegrationprofile- (IEC 62453-41.2009, IDT) Issued on. 2013-07-19 2013-12-15 implementation Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China Standardization Administration of China released Table of ContentsPreface ⅩⅢ Introduction ⅩⅣ 1 Scope 1 2 Normative references 1 3 Terms and definitions, symbols and abbreviations, conventions 1 3.1 Terms and definitions 3.1.1 ActiveX 1 3.1.2 asynchronous function (asynchronousfunction) 1 3.1.3 CLSID 1 3.1.4 ProgID 1 3.1.5 Synchronization (synchronousfunction) 2 3.2 Abbreviations 2 3.3 Conventions 2 4 implements the concept of 2 4.1 Technical positioning 2 Abstract FDT 4.2 Object Model 3 4.2.1 Overview 3 4.2.2 FDT frame application (FA) 3 4.2.3 Device Type Manager (DTM) 3 4.2.4 objects that represent 4 4.2.5 FDT channel object 4 4.3 object interaction 4 4.3.1 exchange of parameters through XML 4 4.3.2 Usage Example 6 Permanent and synchronization of data 8 4.4 DTM Overview 8 4.4.1 Permanent 4.4.2 permanent interface 9 4.5 DTM state machine 9 5 General Concepts 11 5.1 Overview 11 5.2 task-related FDT Interface Overview 11 Return Value 5.3 interface method 14 5.4 pairs of interface 14 Unicode 5.5 (Unicode) Standard 15 5.6 synchronous vs. asynchronous behavior behavior 15 5.7 ProgID 15 5.8 DTM achieve, DTM device type and hardware identification information 15 15 5.8.1 Device Identification 5.8.2 protocol-specific transformation stylesheet (xsl) 18 5.8.3 semantic identification information 18 5.8.4 Device Allocation 18 5.8.5 Regular Expressions specifications 19 5.9 Slave redundancy to achieve 19 5.9.1 Overview 19 5.9.2 Topology Import/Export 19 6 FDT specification to achieve service. FDT interface 20 6.1 FDT Interface Overview 20 6.2 FDT object 20 6.2.1 FDT object model 20 Availability Interface 6.2.2 Method 24 28 6.3 Device Type Manager 6.3.1 IDtm interface 28 6.3.2 IDtm2 interface 36 6.3.3 IDtmActiveXInformation interface 37 6.3.4 IDtmApplication interface 38 6.3.5 IDtmChannel interface 40 6.3.6 IDtmDocumentation interface 41 6.3.7 IDtmdiagnosis interface 41 6.3.8 IDtmImportExport interface 43 6.3.9 IDtmInformation interface 45 6.3.10 IDtmInformation2 interface 46 6.3.11 IDtmOnlineDiagnosis interface 46 6.3.12 IDtmOnlineParameter interface 47 6.3.13 IDtmParameter interface 49 6.3.14 IFdtCommunicationEvents interface 51 6.3.15 IFdtCommunicationEvents2 interface 53 6.3.16 IFdtEvents interface 54 6.3.17 IDtmHardwareIdentification interface 56 6.3.18 IDtmSingleDeviceDataAccess interface 57 6.3.19 IDtmSingleInstanceDataAccess interface 60 6.4 DTM ActiveXControl 61 6.4.1 IDtmActiveXControl interface 61 6.4.2 Init 62 6.4.3 PrepareToRelease 62 6.5 FDT channel 63 6.5.1 IFdtChannel Interface 63 6.5.2 IFdtChannelActiveXInformation Interface 65 6.5.3 IFdtCommunication Interface 67 6.5.4 IFdtChannelSubTopology interface 73 6.5.5 IFdtChannelSubTopology2 Interface 76 6.5.6 IFdtChannelScan Interface 76 6.5.7 IFdtFunctionBlockData interface 78 6.6 ActiveXControl channel 79 6.6.1 IFdtChannelActiveXControl Interface 79 6.6.2 IFdtChannelActiveXControl2 Interface 81 6.7 Type Manager 81 6.7.1 IBtm interface 82 6.7.2 IBtmInformation Interface 83 6.7.3 IBtmParameter Interface 83 6.8 BTM ActiveXControl 84 6.8.1 Overview 84 6.8.2 IBtmActiveXControl interface 84 85 6.9 Framework application 6.9.1 IDtmEvents Interface 85 6.9.2 IDtmEvents2 interface 92 6.9.3 IDtmScanEvents Interface 93 6.9.4 IDtmAuditTrailEvents interface 94 6.9.5 IFdtActiveX Interface 95 6.9.6 IFdtActiveX2 Interface 97 6.9.7 IFdtBulkData Interface 99 6.9.8 IFdtContainer interface 101 6.9.9 IFdtDialog interface 103 6.9.10 IFdtTopology interface 104 6.9.11 IDtmRedundancyEvents interface 108 6.9.12 IDtmSingleDeviceDataAccessEvents interface 110 6.9.13 IDtmSingleInstanceDataAccessEvents interface 112 6.9.14 IFdtBtmTopology interface 112 7 FDT program charts 113 7.1 DTM peer to peer communications 113 7.1.1 Overview 113 7.1.2 DTM and establish connections between devices, etc. 113 7.1.3 Peer asynchronous connection connection 114 7.1.4 IFdtCommunicationEvents2∷OnConnectResponse2 () asynchronous peer disconnecting 114 7.1.5 peer connection asynchronous transactions 115 7.2 Nested Communication 116 7.2.1 Overview 116 7.2.2 generation system topology 116 7.2.3 establish DTM and devices connected to the system 118 7.2.4 System Connection asynchronous transactions 119 120 7.3 Topology scan 7.3.1 Network Scanning 120 7.3.2 cancel topology scan 121 7.3.3 Provisional results of the scan notifications 122 7.3.4 scan communication hardware 123 7.3.5 manufacturer-specific device identification 124 7.4 protocol specific FDT architecture register 126 7.5 fieldbus master configuration 128 7.6 application and release 129 7.7 Channel Access 130 7.8 DCS channel assignment 131 7.9 DTM particular document to print 135 7.10 Application-specific framework document printing 136 136 7.10.1 Overview 7.10.2 Issue 137 7.10.3 DTM-specific style sheets usage rules 139 7.11 Change transfer 140 Lock 141 7.12 7.12.1 locking sync DTM 142 7.12.2 lock synchronization DTM 144 7.13 instantiated and released 145 7.13.1 instantiate new DTM 145 146 7.13.2 Examples of the existing DTM 7.13.3 DTM ActiveX user interface instantiation 146 7.13.4 DTM user interface release 147 7.14 DTM persistent storage 148 7.14.1 Examples of data sets state machine 148 7.14.2 DTM instance data storage 150 7.14.3 Overload DTM objects used in other instances 151 Copy of version 7.14.4 DTM instances 151 7.15 Audit Trail 151 Comparative 152 7.16 two instances of data sets 7.16.1 no user interface 152 Comparison 7.16.2 a relatively user interface 153 7.17 Fail-safe data access 154 7.18 through the user interface to set or modify the device address 155 7.19 through the user interface does not set or modify a known device address 156 7.20 through the user interface to display or modify all sub-device address 157 7.21 device-initiated data transmission 158 7.22 and release modal dialog within the DTM user interface 159 7.23 parent component redundancy from processing device 160 7.24 ActiveX control initialization channel 161 7.24.1 Overview 161 7.24.2 support IFdtChannelActiveXcontrol2 162 7.24.3 does not support IFdtChannelActiveXcontrol2 162 7.25 DTM upgrade 163 7.25.1 Overview 163 7.25.2 DTM will be upgraded to save data 163 7.25.3 Replace load data 164 in the DTM 7.26 IDtmSingleDeviceDataAccess∷ReadRequest/WriteRequest usage 165 7.27 DTM and BTM instantiation 166 8 Installation Notes 168 8.1 registration and device information 168 Visibility 8.1.1 DTM business object 168 8.1.2 Component Categories 168 8.1.3 registry entry 169 8.1.4 Installation Notes 169 8.1.5 Microsoft Component Category Manager Standard 169 8.1.6 supports the establishment of equipment framework application database 169 8.1.7 DTM registered 170 8.2 path and file information 170 8.2.1 DTM route information provided by 170 8.2.2 and permanent path 171 8.2.3 Multi-User Systems 171 9 data types, parameters and structure description 171 9.1 identifier 171 9.2 data type definition 172 Appendix A (normative appendix) FDTIDL 173 Appendix B (normative) service interface method 199 maps B.1 Overview 199 B.2 DTM Services 199 B.3 indicates Object Services 203 B.4 General channel service 203 B.5 process 203 channel service B.6 service communication channel 203 B.7 Framework application services 205 Appendix C (Normative Appendix) FDTXML architecture 207 C.1 Overview 207 C.2 FDTDataTypeSchema 207 C.3 FDTApplicationSchema 228 C.4 FDTUserInformationSchema 229 C.5 DTMInformationSchema 231 C.6 DTMFunctionCalSchema 238 C.7 DTMParameterSchema 239 C.8 DTMDocumentationSchema 252 C.9 DTMProtocolsSchema 255 C.10 DTMSystemTagListSchema 256 C.11 DTMAuditTrailSchema 258 C.12 DTMDeviceStatusSchema 260 C.13 DTMFunctionsSchema 261 C.14 DTMChannelFunctionsSchema 268 C.15 DTMOnlineCompareSchema 272 C.16 FDTFailSafeDataSchema 273 C.17 DTMTopologyScanSchema 275 C.18 FDTOperationPhaseSchema 275 C.19 DTMInitSchema 276 C.20 FDTUserMessageSchema 277 C.21 DTMInfoListSchema 279 C.22 FDTTopologyImportExportSchema 281 C.23 DTMDeviceListSchema 287 C.24 DTMSystemGuiLabelSchema 290 C.25 DTMStateSchema 291 C.26 DTMEnvironmentSchema 292 C.27 FDTConnectResponseSchema 293 C.28 TypeRequestSchema 293 C.29 FDTScanRequestSchema 294 C.30 FDT ××× IdentSchema 296 C.31 FDT ××× DeviceTypeIdentSchema 296 C.32 FDT ××× ScanIdentSchema 296 C.33 DTMIdentSchema 296 C.34 DTMScanIdentSchema 297 C.35 DTMDeviceTypeIdentSchema 300 C.36 DTMItemListSchema 303 C.37 BtmDataTypesSchema 312 C.38 BtmInformationSchema 314 C.39 BtmParameterSchema 316 C.40 \u003c/FDT\u003e BtmInitSchema 319 C.41 BtmInfoListSchema 320 Appendix D (Informative Appendix) FDTXML style - 321 files Appendix E (Informative Appendix) FDTXSL converter 328 E.1 identity transformation 328 E.2 Tip 328 Annex F (normative) Channel Architecture 330 F.1 FDTBasicChannelParameterSchema 330 F.2 channel architecture template 331 Annex G (normative appendix) FDT version Interoperability Guide 333 G.1 Overview 333 G.2 Overview 333 G.3 Interoperability components 333 G.4 FDT Type Library 334 G.5 DTM and device version 335 G.6 permanent 335 G.7 Nested Communication 335 G.7.1 Overview 335 G.7.2 Data Exchange 335 G.7.3 communication channel 336 upgrade G.7.4 Scenario 336 G.7.5 OnAddChild 336 G.8 achieve prompt 336 G.8.1 Interface 336 Appendix H (informative) implemented using .NET technology 338 H.1 FDT how to support the development of .NET-based 338 H.2 Microsoft .NET Framework 1.1 and 2.0 compatibility 338 H.3 parallel installation and related issues 338 H.4 How to avoid compatibility problems 339 Annex I (informative) trademark 340 References 341 FIG. 1 GB/T 29618 Series Part 41 ⅩⅢ Figure 2 Framework Application Programming Interface 3 Figure 3 DTM Interface 3 FIG. 4 by the FDT XML client/server relationship 4 5 data access and storage 6 6 Communications 7 7 7 Archive Parameter 8 8 check the fail-safe device Fig 9 DTM state machine 9 Figure 10 device identification 16 11 Chart 17 Overview Figure 12 FDT and DTM objects DtmActiveXControl interface 21 Figure 13 FDT frame application interface objects 22 Figure 14 FDT objects FDTChannel 23 Figure 15 FDT objects -BTM and BtmActiveXControl 24 Peer DTM and the device 16 is connected 114 17 asynchronous connection (peer) 114 18 asynchronous disconnected (Peer to Peer) 115 19 asynchronous processing (Peer to Peer) 115 Figure 20 System Topology 116 21 topology generated by the application framework 117 FIG. 22 generates a system topology -DTM participation 118 Figure 23 system is connected (through the communication layer) 119 24 asynchronous processing (system connection) 120 Figure 25 Scan Network Topology 121 26 Cancel topology scan 122 27 123 temporary scan results 28 scan communication hardware 124 29 manufacturer-specific device identification 125 Figure 30 to add a specific protocol architecture application architecture framework sub-path 127 Figure 31 device identification information read DTMDeviceType Framework application specific protocol 128 32 Bus Master Configuration 129 33 and release the application 130 Figure 34 Channel Access 131 Figure 35 DCS channel allocation unit DTM 132 36 single DTM channel allocation order 133 The modular structure of Fig. 37 DTM 134 38 modular DTM channel assignment 135 Figure 39 DTM particular document to print 136 Figure 40 frame application-specific document printing 137 41 report generation (Framework application style) 138 42 Report Generation (equipment manufacturer specific style) 139 43 changes passed 141 FIG. 44 is not synchronized DTM lock 143 45 lock synchronization DTM 144 46 145 new DTM instantiated 47 Examples of existing DTM 146 Figure 48 DTM user interface instantiation 147 49 release DTM user interface 148 Figure 50 Examples of data sets state machine 149 Permanent state of FIG. 51 data sets 150 52 Save DTM instance data 150 Figure 53 DTM copy and the example of 151 Figure 54 Audit Trail 152 Figure 55 Comparison 153 without a user interface Figure 56 Comparison with the user interface 154 57 fail-safe data access 155 Figure 58 without a user interface to set or modify a known device address 156 Figure 59 without a user interface to set or modify a known device address 157 Figure 60 to modify all the sub-device address with the user interface display 158 Figure 61 device-initiated data transmission 159 62 Modal DTM user interface 160 63 redundant processing device 161 FIG. 64 is initialized with IFdtChannelActiveXControl2 channel ActiveX 162 Figure 65 Initialization ActiveX controls without IFdtChannelActiveXControl2 interface 163 66 saved data will be upgraded DTM 164 Figure 67 Loading data replacement within 165 DTM Figure 68 IDtmSingleDeviceDataAccess usage 166 FIG. 69 is created and instantiated general flow 167 Figure E.1 XSTL role 329 Table 1 DTM state machine defines 10 Table 2 tasks related to DTM interface 11 Table 3 Tasks related DTM-ActiveX interface 12 Table 4 tasks associated channel interface 12 Table 5 tasks related to Channel-ActiveX interface 13 Table 6 tasks related BTM interface 13 Table 7 task-related BTM-ActiveX interface 13 Table 8 task-related application program interface framework 14 Table 9 semantic identification information 18 Table 10 Regular Expressions 19 Table 11 states the availability of different methods of DTM 25 Table 12 Framework application availability 27 interface Table 13. Examples of data sets state description 149 Table 14 Permanent Status Description 150 Table 15 component categories 168 Table 16 clusters 168 Table 17 DTM 169 registered examples Table 18 FDT-specific ID 171 Table 19 Basic data types 172 Table 20 of the document helper objects 172 Table B.1 General Services 199 Table B.2 services related to the installation of DTM 199 Table B.3 DTM DTM service related information 199 Table B.4 DTM DTM state machine related services 200 Table B.5 function related services 200 DTM Table B.6 documents related service DTM 201 Table B.7 DTM instance data access service 201 Table B.8 access service diagnostics DTM 201 Table B.9 DTM device data access service 201 Table B.10 network management information services related to the DTM 202 Table B.11 online services related to the operation of DTM 202 Table B.12 channel object associated DTM Services 202 Table B.13 import and export related services 202 DTM Table B.14 related DTM data synchronization service 202 Table B.15 Common Channel Services 203 Table B.16 related information service channel 203 Table B.17 communication-related service channel 203 Table B.18 Topology management services related to channel 204 Table B.19 channel function related services 204 Table B.20 relevant channel scan service 204 Table B.21 FA generic event-related services 205 Table B.22 topology management services related to FA 205 Table B.23 FA redundancy related services 205 Table B.24 DTM data storage-related services 206 FA Table B.25 FA relevant data synchronization service 206 Table B.26 indicates that the associated service 206 FA Table B.27 audit trail related services 206 FA Table C.1 generic XML Property Description 207 Table C.2 generic XML element Description 211 Table C.3 Device Class ID 214 Table C.4 in Appendix G in accordance with IEC 62390 device class 215 Table C.5 ApplicationID Property Description 228 Table C.6 ApplicationID element Description 229 Table C.7 user information Property Description 230 Table C.8 user information element Description 230 Table C.9 DTM information Property Description 231 Table C.10 DTM information element Description 232 Table C.11 function calls Property Description 238 Table C.12 Parameter Description document property 239 Table C.13 Parameter Description document element 240 Table C.14 Document Properties Description 252 Table C.15 document element Description 252 Table C.16 protocol elements description 255 Table C.17 System tab Property Description 256 Table C.18 system label elements Description 256 Table C.19 audit trail Property Description 258 Table C.20 audit trail element Description 258 Table C.21 Device Status Property Description 260 Table C.22 Device Status element Description 260 Table C.23 functional properties Description 261 Table C.24 functional elements described 262 Table C.25 Channel Function Property Description 268 Table C.26 Channel Function element Description 269 Comparison Table C.27 Property Description 272 Comparison Table C.28 element Description 272 Table C.29 failsafe Property Description 274 Table C.30 describes the fail-safe metal element 274 Table C.31 topology scan element Description 275 Table C.32 operating phases Property Description 276 Table C.33 operational phase element Description 276 Table C.34 DTMInit element Description 276 Table C.35 custom message attributes Description 277 Table C.36 user message element Description 277 Table C.37 DTM list element Description 279 Table C.38 topological properties Description 281 Table C.39 describes topology element 281 Table C.40 device list Property Description 288 Table C.41 device list element Description 288 Table C.42 GUI label element Description 290 Table C.43 DTM state element Description 291 Table C.44 version of the framework element Description 292 Table C.45 Connection Response elements Description 293 Table C.46 Type Description request element 293 Table C.47 scan request Property Description 294 Table C.48 scan request element Description 294 Table C.49 public identity property description 297 Table C.50 public identification element Description 297 Table C.51 scan identity property description 298 Table C.52 scanning identification element Description 298 Table C.53 Device type identification element Description 300 Table C.54 lists the properties described in Item 303 Table C.55 item list element Description 304 Table C.56 BTM 312 Data Type Attribute Description Table C.57 BTM data type element Description 313 Table C.58 BTM information element Description 314 Table C.59 BTM parameter element Description 316 Table C.60 BTMInit element Description 319 Table C.61 BTM list element Description 320 Table F.1 basic channel attribute description 330 Table F.2 basic channel element Description 330 Table F.3 ××× channel Item Description 331 Table F.4 ××× channel parameter element Description 331 Table G.1 different version of the component interoperability between 334ForewordGB/T 29618 "Field device tool (FDT) interface specification" temporarily divided into the following sections. --- Part 1. Overview and guidance; --- Part 2. Concepts and detailed description; --- Part 301. Integrated communication profile Fieldbus Specification FF; --- Part 302. Integrated communication profile Common Industrial Protocol; Part --- Article 303-1. communication pro......Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 29618.41-2013_English be delivered?Answer: Upon your order, we will start to translate GB/T 29618.41-2013_English as soon as possible, and keep you informed of the progress. The lead time is typically 6 ~ 10 working days. The lengthier the document the longer the lead time.Question 2: Can I share the purchased PDF of GB/T 29618.41-2013_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 29618.41-2013_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to Sales@ChineseStandard.net. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay. |