Home Cart Quotation About-Us
www.ChineseStandard.net
SEARCH

GB/T 29618.42-2017 English PDF

Standard IDUSDBUY PDFLead-DaysStandard Title (Description)Status
GB/T 29618.42-2017RFQ ASK 3 days Field device tool (FDT) interface specification -- Part 42: Object model integration profile -- Common language infrastructure Valid

Similar standards

GB/T 33008.1   GB/T 33009.1   GB/T 33009.2   GB/T 29618.5110   GB/T 29618.62   GB/T 29618.61   

Basic data

Standard ID: GB/T 29618.42-2017 (GB/T29618.42-2017)
Description (Translated English): Field device tool (FDT) interface specification -- Part 42: Object model integration profile -- Common language infrastructure
Sector / Industry: National Standard (Recommended)
Classification of Chinese Standard: N10
Classification of International Standard: 25.040
Word Count Estimation: 318,369
Date of Issue: 2017-07-31
Date of Implementation: 2018-02-01
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

GB/T 29618.42-2017: Field device tool (FDT) interface specification -- Part 42: Object model integration profile -- Common language infrastructure


---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 42. Object model integration profile - Common language infrastructure ICS 25.040 N10 National Standards of People's Republic of China Field Device Tool (FDT) Interface Specification Part 42 - Object model specification integration Generic language infrastructure Fielddevicetool (FDT) interfacespecification- Part 42.Objectmodelintegrationprofile- (IEC /T R62453-42.2016, IDT) 2017-07-31 Posted 2018-02-01 implementation General Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China China National Standardization Administration released Directory Foreword XIII Introduction XV 1 Scope 1 2 Normative references 1 3 Terms and definitions, abbreviations, conventions 1 3.1 Terms and definitions 1 3.2 Abbreviations 7 3.3 Conventions 8 4 to achieve the concept of 8 4.1 Technology Orientation 8 4.2 abstract FDT object model to achieve 8 4.3 FDT Framework Application (FA) 9 4.4 DTM business logic 10 4.5 DTM function realization 13 4.6 User Management 15 4.7 FDT and system topology implementation 18 4.8 module to achieve 20 4.9 FDT Communication Implementation 20 4.10 logo 23 4.11 DTM Data Persistence and Synchronization Implementation 24 4.12 access device data and input and output information to achieve 28 4.13 DTM Instance Clone 31 4.14 Concept of life cycle 32 4.15 Audit Trail 32

5 Technology Concepts

5.1 Overview 33 Support for .NETCLR Version 35 5.3 Support for 32-bit and 64-bit target platforms 36 5.4 Object Activation and Deactivation 37 5.5 Data Types 39 5.6 Common Objects 45 5.7 threads 56 5.8 Localization Support 58 5.9 DTM user interface to achieve 60 5.10 DTM User Interface Hosting 61 5.11 The realization of static function 63 5.12 Persistence 65 5.13 Comparison of DTM and Device Data 69 5.14 Tracking 69 5.15 Report Generation 69 5.16 Security 71 6 FDT Objects and Interfaces 74 6.1 Overview 74 6.2 Framework Applications 74 6.3 DTM Business Logic 77 6.4 DTM User Interface 90 6.5 Communication Channel 92 6.6 Availability of Interface Methods 93 7 FDT data type 94 7.1 Overview 94 7.2 Data Types --- Foundations 94 7.3 General Data Types 95 7.4 Data Type --- DtmInfo/T ypeInfo 95 7.5 Data Types --- DeviceIdentInfo 97 7.6 Data Types for Installation and Deployment 102 7.7 Data Type - Communication 105 7.8 Data Type -BusCategory 111 7.9 Data Type - Device/Instance Data 112 7.10 Export and Import Data Types 7.11 Description of the data types of the process data 122 7.12 Data Type - Address Information 128 7.13 Data Type -NetworkDataInfo 132 7.14 Data Type-DTM Function 134 7.15 Data Type - DTM Message 136 7.16 DTM UI Dialog Box Operators Data Types 137 7.17 Data Types -CommunicationChannelInfo 137 7.18 Data Types - Hardware Identification and Scanning 139 7.19 Data Type - DTM Report Type 141 7.20 Device Information on Integrated DTMs 142 8 Workflow 144 8.1 Overview 144 8.2 Instantiate, load and release 144 8.3 DTM permanent storage 150 8.4 Multi-user environment, locking and data transactions 153 8.5 Performing DTM Functions 157 8.6 DTM Communication 175 8.7 Nested Communication 181 8.8 Topology Planning 183 8.9 Sub-DTM instantiation, configuration, movement and release 188 Topology Scanning 193 8.11 Configuration of Communication Network 198 8.12 Using IO Information.199 8.13 Address Management 203 8.14 Device Initiated Data Transfer 206 8.15 Read Data and Write Data 207 8.16 Compare Data 210 8.17 Reassign a different DtmDeviceType 211 on a device node 8.18 Partially Duplicated FDT Topology 215 8.19 Audit trail sequence 216 9 Install 219 9.1 Overview 219 9.2 Common Rules 219 9.3 FDT Core Assembly Installation 224 9.4 Communication Protocol Installation 224 9.5 DTM Installation 225 9.6 DTM Installer 229 9.7 DTM Deployment 234 9.8 Path and file information 236 Concept of life cycle 236 10.1 Overview 236 10.2 Technical Concepts 236 10.3 DTM Installation 240 10.4 Life Cycle Scenario 241 Framework Application Structure 11.1 Overview 246 11.2 Stand-alone Application 246 11.3 Remote User Interface 246 11.4 Distributed Multi-User Applications 247 11.5 OPC UA 247 Appendix A (Normative) FDT2 use case model 249 A.1 Use Case Model Overview 249 A.2 Participants 249 A.3 Use Case 250 Appendix B (Normative) FDT interface definitions and data types 263 Appendix C (Normative) Mapping of Service to Interface Methods C.1 Overview 264 C.2 DTM Services 264 C.3 represents the service of the object 268 C.4 Common Channel Services 268 C.5 Process Channel Services 268 C.6 Communication Channel Services 269 C.7 Framework Application Services 270 Appendix D (Normative) FDT Version Interoperability Guide D.1 General 272 D.2 Overview 272 D.3 Component Interoperability 272 Appendix E (Normative) FDT1.2.x/This part of the backward compatibility 274 E.1 General 274 E.2 Parallel FDT Topology 274 E.3 Hybrid FDT Topology 275 E.4 FDT1.2.x/This part of the adapter 277 E.5 FDT1.2.xXML/This section data type converter 278 E.6 Backwards compatible with related sequences 280 Appendix F (Informative) Implementation Tips 282 F.1 General recommendations 282 F.2 IAsyncResult mode 282 F.3 Thread Best Practices 283 Appendix G (informative) Trademark name 284 Appendix H (informative) UML symbol 285 H.1 Overview 285 H.2 class diagram 285 H.3 Statechart 288 H.4 Use Case Figure 289 H.5 Sequence diagram 290 H.6 Object Figure 293 Appendix I (Informative) Physical Layer Example 295 I.1 Overview 295 I.2 INTERBUS 295 I.3 PROFIBUS 295 I.4 PROFINET 295 Appendix J (Informative) Predefined SemanticId 297 J.1 General 297 J.2 Data 297 J.3 Image 297 J.4 Document 297 Ref. 298 Figure 1 GB/T 29618.42 and GB/T 29618 series of standards XV relationship Figure 2 Object Model 9 Figure 3 Framework application 9 Figure 4 DTM business logic 10 Figure 5 DTM, Device Type, and Device Identification Information 11 Figure 6 Process Data Information 12 Figure 7 logical topology and physical topology 18 Figure 8 FDT and Logic Topology 19 Figure 9 DTM and Physical Topology 20 Figure 10 Point-to-point communication 21 Figure 11 Nested Communication 22 Figure 12 Identification of connected devices 24 Figure 13 FDT storage and synchronization mechanism 25 Figure 14 DTMDataSet DTM instance and the relationship between the equipment 25 Figure 15 DTMDataSet structure 26 Figure 16 Data Synchronization 27 Figure 17 routing IO information 30 Figure 18 Multi-Role Device Figure 19 FDT .NET Assembly 34 Figure 20 FDT object implementation 34 Figure 21 FDTCLR Extension Concept 36 Figure 22 example. Assembly.LoadFrom () 37 Figure 23 Example. Assembly Relevance 38 Figure 24 Example. Data Type Definition 40 Figure 25 Example. Data Clone 41 Figure 26 Example. No Data Cloning Method 41 Figure 27 Protocol Specific Data Types 42 Figure 28 Protocol List and Type Information Attributes 43 Figure 29 Example. Properties of the Protocol Assembly 44 Example of Figure 30. Protocol-specific assembly processing in a framework application 44 Figure 31 This section of the FDT object decoupling 45 Figure 32 IAsyncResult Mode. Block Call 47 Figure 33 Example. Asynchronous Interface Blocking 48 Figure 34 IAsyncResult Mode (Simplified). Block Call 48 Figure 35 IAsyncResult Mode. Non-blocking Call 49 Figure 36 Example. Non-blocking Use of Asynchronous Interfaces 50 Figure 37 IAsyncResult Mode (Brief Description). Non-blocking Call 50 Figure 38 IAsyncResult Mode. Cancel Operation 51 Figure 39 IAsyncResult mode. Provides progress events 52 Figure 40 provides the main window 60 of the scrollbar's frame application Figure 41 Controls with Internal Slider 61 Figure 42 Example. Managing DTM WPF Controls 62 in a WPF Framework Application Figure 43 Example. Managing DTM WPF Controls 62 in a WinForms Framework Application Figure 44. Example DTM WinForms control 63 is hosted in the WinForms framework application Figure 45. Example. DTM WinForms Control 63 is hosted in a WPF framework application Figure 46 StaticFunctionDescription and Static Function Relationship 64 Figure 47 DTMDataset structure 65 Figure 48 Example. Initialize DtmDataSubset 66 with DTM data Figure 49 Example. Writing DTM Data 67 in DTMDataSubset Figure 50 Example. Reading DTM Data 67 from DTMDataSubset Figure 51 Example. Create a BulkData.DtmDataSubset 68 with descriptors Figure 52 Example. Search for DtmDataSubsets 68 with a specific descriptor Figure 53 DTM-specific architecture 70 Figure 54 Example .Authenticode check 72 Figure 55 Example. Consistency log file 73 Figure 56 Example. Check consistency record file 74 Figure 57 Framework Application Interface 75 Figure 58 DTM Business Logic Interface (Part 1) Figure 59 DTM Business Logic Interface (Part 2) 78 Figure 60 DTMBL state machine 82 Figure 61 DTM online state machine 84 Figure 62 Data Modification by DTM 88 Figure 63 DTM Modification. State Machine for Instance Data 89 Figure 64 Device Modification. State Machine 90 Related to Device Data Figure 65 DTMUI Interface 91 Figure 66 Communication Channel Interface 92 Figure 67 FdtDatatype and FdtList 94 Figure 68 DtmInfo/T ypeInfo Data Type 96 Figure 69 DeviceIdentInfo data type 98 Figure 70 DeviceIdentInfo - Example for HART 99 Figure 71 Example .DeviceIdentInfo creation 101 Figure 72 Example. Using DeviceIdentInfo 102 Figure 73 for example. DeviceIdentInfoTypeAttribute 102 Figure 74 SetupManifest - Data Type 103 Figure 75 DtmManifest-data type 104 Figure 76 DtmUiManifest-data type 105 Figure 77 Communication Data Type - Connection 106 Figure 78 Communication Data Type - Transaction 106 Figure 79 Communication Data Type - Disconnected 107 Figure 80 Communication Data Type - Subscription 107 Figure 81 Communication Data Type - Scanning 108 Figure 82 Communication Data Type - Address Setting 108 Figure 83 Example .HART Communication - Connection 110 Figure 84 Example Communication - CommunicationType 111 for HART Figure 85 BusCategory data type 111 Figure 86 Device/Instance Data - Data Type 112 Figure 87 provides an example of providing information 114 about a HART device data Figure 88 Example Provides information on the data of a PROFIBUS device module 115 Figure 89 provides an example of providing information about the data 116 Figure 90 provides information about structure data 117 Figure 91 EnumInfo - Data Type 118 Figure 92 Read, Write Request - Data Type 118 Figure 93 ResponseInfo - Data Type 119 Figure 94 TopologyImportExport - Data Type 121 Figure 95 ImportExportDataset-data type 122 Figure 96 ProcessDataInfo-data type 123 Figure 97 IOSignalInfo - Data Type 124 Figure 98 Example. ProcessDataInfo 125 for HART (UML) Figure 99 Example. Creation of ProcessDataInfo for HART Figure 100 Example using ProcessData 127 for HART Figure 101 for example .OSignalInfoType property 127 Figure 102 ProcessImage-data type 128 Figure 103 AddressInfo - Data Type 129 Figure 104 Example. CreateAddressInfo 130 Figure 105 Example. Use AddressInfo 131 Figure 106 Example. Device Address Type Attributes 132 Figure 107 NetworkDataInfo - Data Type 132 Figure 108 Example .NetworkDataInfo creation 133 Figure 109 Example. Example of Using NetworkDataInfo 134 Figure 110 Example .NetworkDataTypeAttribute example 134 Figure 111 DTM Functions - Data Types 135 Figure 112 DTM Message - Data Type 136 Figure 113 ActionItem-data type 137 Figure 114 CommunicationChannelInfo - Data Type 138 Example of Figure 115. Channel Info 139 Figure 116 DeviceScanInfo - Data Type 140 Figure 117 for example .HARTDeviceScanInfo - data type 141 Figure 118 DTM Report - Data Types 142 Figure 119 Device Module Related Information 143 Figure 120 looks for DTMBL object 145 Figure 121 instantiates a new DTMBL 146 Figure 122 User Rights Configuration 147 Figure 123 Load DTMBL 148 Figure 124 Load Expert User Level DTM 149 Figure 125 Releases the DTMBL 150 Figure 126 Save DTM Data 151 Figure 127 Data Submission Failed 152 Figure 128 Export DTM Datasets to File 153 Figure 129 Propagation of Change 155 Figure 130 Synchronizes DTMs 156 in a multi-user environment Figure 131 Finding the DTM User Interface 157 Figure 132 Instantiates a DTM User Interface 158 Figure 133 DTML-Instantiated DTMUI 159 Figure 134 Instantiated modal DTMUI 160 triggered by DTMBL Figure 135 Release DTM User Interface 161 Figure 136 releases DTMUI 162 triggered by DTMBL Figure 137 Self-Triggered Release of DTMUI 162 Figure 138 Release Non-Modal DTMUI 163 Triggered by Standard Operations Figure 139 Progress indication of long DTM operation 164 Figure 140 Launches Application 165 Figure 141 Executing Command Function 166 Figure 142 Executes Command Function 167 with User Interface Figure 143 opens the document 168 Figure 144 DTM UI-triggered interaction 169 Figure 145 Interaction triggered by DTM business logic 170 Figure 146 DTM UI Triggering and Canceling Interactions 171 Figure 147 Retrieve Information on Available Static Functions 172 Figure 148 Example. Information on Available Static Functions 173 Figure 149 Execute Static Function 174 Figure 150 executes a static function 175 with multiple parameters Figure 151 Establishing a Communication Connection 176 Figure 152 DTM cancels the ongoing connection 177 Figure 153 Communicating with Devices 178 Figure 154 Disconnection of Sub DTM 179 Figure 155 Sub DTM terminates the connection 180 Figure 156 17EventOnlineStateChanged () Sub DTM interrupt connection 180 Figure 157 Communication Channel Abort Connection 181 Figure 158 Example. Nested Communication Behavior 182 Figure 159 Example. Nested Communication Data Exchange 183 Figure 160 Add DTM 184 in the topology Figure 161 Remove DTM 185 from the topology Figure 162 Framework application creation topology 186 Figure 163 DTM Generate Subtopology 187 Figure 164 Instance and Configuration of Sub DTMBLs Figure 165 Parent DTM and child DTM interactions 190 Figure 166 DTM interaction via IDtmMessaging 191 Figure 167 Parent DTM moves one child DTM 192 Figure 168 Parent DTM Remove child DTM 193 Figure 169 Network Topology Scanning 194 Figure 170 Cancel Topology Scanning 195 Figure 171 Scan based on DTM assignment 196 Figure 172 Manufacturer Specific Device Identification 197 Fig. 173 Configuration of the fieldbus master 198 Figure 174 Passive Device Integration.199 Figure 175 Process Data Allocation.200 Figure 176 Process Image Creation.201 Fig. 177 Modify Confirmation 202 while PLC is running Figure 178 Modify the variable name 203 via the process image interface Figure 179 Set DTM Address 204 via User Interface Figure 180 does not set the DTM address 205 through the user interface Figure 181 displays or modifies the sub-DTM address 206 via the user interface Figure 182 Device Initiated Data Transfer 207 Figure 183 Read/Write Instance Data 208 Figure 184 Read/Write Device Data 209 Figure 185 compares the device data set with the instance data set 210 Figure 186 compares instance data and persistence data set 210 Figure 187 DTM Triggering ActiveTypeChanged Event 212 Figure 188 looks for matching DtmDeviceTypes 213 after an incompatible device change Figure 189 Reassign DtmDeviceType 214 after incompatible device replacement Figure 190 Clone DTM 215 without sub DTMs Figure 191 Clone the DTM 216 that contains all the child DTMs Figure 192 Audit trail 217 for parameter modifications in the instance data set Figure 193 Audit trail of parameter changes in the device 218 Figure 194 Audit trail of function calls 218 Figure 195 GAC and FDT_Registry 221 Figure 196 Installation Path with DTM Example 222 Figure 197 Example Protocol List 225 Figure 198 Search for an installed DTM 226 Figure.199 Example .DtmManifest 227 Figure.200 Example of DtmUiManifest 228 Figure.201 DTM installation structure Figure 202 Example of DtmSetupManifest 231 Figure 203 DeviceIdentManifest example 233 Figure 204 DTM Deployment 235 Figure 205 DTM Identification Overview 237 Figure 206 ID Properties 240 in DTM Installation Figure 207 Check DTM Installation 243 for Support Type List Figure 208 Scan installed DTM 244 Figure 209 Data Set Migration to Reassigned DtmDeviceType 245 Figure 210 Client/Server Application 246 Figure 211 Distributed Multi-User Application Example 247 Figure 212 OPCUA server 248 based on this section Figure A.1 Main Use Cases Figure 249 Figure A.2 Observation Use Case 251 Figure A.3 Operational Example 253 Figure A.4 Maintenance Use Case 255 Figure A.5 Planning Use Case 259 Figure E.1 This part of the Frame Application 274 is backwards compatible with FDT 1.2.x. Figure E.2 This section of the framework application 275 that contains the FDT1.2.x device DTMs Figure E.3 This section of the Frame Application 276 containing the FDT 1.2.x Communication and Gateway DTM Figure E.4 This section of the Frame Application 276 containing the FDT 1.2.x Gateway DTM Figure E.5 This section-FDT1.2 uses a translator to interact 279 Figure E.6 Data Set Migration from FDT1.xDTM to FDT2.xDTM 280 Figure H.1 Note 285 Figure H.2 Class 285 Figure H.3 Correlation 285 Figure H.4 Navigable association 286 Figure H.5 Combination 286 Figure H.6 Polymerization 286 Figure H.7 depends on 286 Figure H.8 Associated Classes 287 Figure H.9 Abstract Classes, Generalizations and Interfaces Figure H.10 Interface-related symbols 287 Figure H.11 multiplicity 288 Figure H.12 enumerates data types 288 Figure H.13 Element of the UML Statechart 288 Figure H.14 UML Statechart Example 289 Figure H.15 UML use case syntax 289 Figure H.16 UML sequence diagram 290 Figure H.17 Empty frame 290 of a UML sequence diagram Figure H.18 Objects with lifelines and their activation 291 Figure H.19 Method Invocation 291 Figure H.20 Guarded call and multiple invoked models 291 Figure H.21 calls itself 292 Figure H.22 Continuation/StateInvariant 292 Figure H.23 Another fragment 292 Figure H.24 Option fragment 293 Figure H.25 Cyclic combination of fragments 293 Figure H.26 Break symbol 293 Figure H.27 Sequence reference 293 Figure H.28 Object 294 Figure H.29 Object Association 294 Table 1 FDT user level 16 Table 2 DTM Roles Related Access and User Interface 16 Table 3 Attributes Related to Data Access Control 29 Table 4 CLR version 35 support Table 5 Framework Application Interfaces Table 6 DTM Business Logic Interface Table 7 Interface Availability for Different Types of DTMs 80 Table 8 DTMBL state machine definition 83 Table 9 Definition of Online State Machine 85 Table 10 describes the state of the instance data set 89 Table 11 describes the status of the data set online modification 90 Table 12 DTMUI Interfaces 92 Table 13 Communication Channel Interfaces 92 Table 14 Availability of DTMBL Methods in Different States 93 Table 15 FDT Basic Data Types 95 Table 16 FDT General Data Types 95 Table 17 DtmInfo Data Type Descriptions 96 Table 18 DeviceIdentInfo Data Type Description 98 Table 19 DeviceIdentInfo - Example 100 for HART Table 20 SetupManifest Data Type Descriptions 103 Table 21 DtmManifest Data Type Descriptions 104 Table 22 DtmUiManifest data type descriptions Table 23 Communication Data Type Descriptions Table 24 BusCategory Data Type Description 111 Table 25 Data Type Descriptions for Device Data 113 Table 26 reads, writes the data type description 119 Table 27 Read, ......
Image     

Tips & Frequently Asked Questions:

Question 1: How long will the true-PDF of GB/T 29618.42-2017_English be delivered?

Answer: Upon your order, we will start to translate GB/T 29618.42-2017_English as soon as possible, and keep you informed of the progress. The lead time is typically 1 ~ 3 working days. The lengthier the document the longer the lead time.

Question 2: Can I share the purchased PDF of GB/T 29618.42-2017_English with my colleagues?

Answer: Yes. The purchased PDF of GB/T 29618.42-2017_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+ countries

Question 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.