Valid

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

现场设备工具(FDT)接口规范 第42部分:对象模型行规集成 通用语言基础结构

Preview PDF

This is a limited preview

Buy now to download the full PDF (531 pages)

Need quotation for your management?

Get a formal quotation for GB/T 29618.42-2017 in 30 minutes.

Issued by

General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China, Standardization Administration of the People's Republic of China

Level / Type

National · Recommended

Issue date

July 31, 2017

Implementation date

February 1, 2018

Scope

GB/T 29618.42-2017 is the English-translated version of 现场设备工具(FDT)接口规范 第42部分:对象模型行规集成 通用语言基础结构.

GB/T 29618.42-2017 explains how the FDT device-tool object model is implemented on the Common Language Infrastructure, so that device type managers (DTMs) and the tools that host them can be written for.NET and still work together.

It is Part 42 of the GB/T 29618 series and an identical adoption of IEC/TR 62453-42:2016.

It covers framework applications, DTM business logic and user interfaces, user levels, logical and physical topology, nested communication, data persistence and synchronisation, audit trails, CLR version support, 32-bit and 64-bit platforms, threading, the FDT data types, installation and deployment, and backward compatibility with FDT 1.2.x.

Annexes add the FDT2 use case model and the mapping of services to interface methods. Software houses building DTMs or host applications work from it. It was issued on 31 July 2017 and has applied since 1 February 2018.

Found what you need?

Document preview — GB/T 29618.42-2017

National Standard of the People's Republic of China

ICS
25.040
Classification
N 10

Issued by: General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China, Standardization Administration of the People's Republic of China

Contents

  • Foreword
  • Introduction
  • 1 Scope
  • 2 Normative references
  • 3 Terms and definitions, abbreviations, conventions
  • 3.1 Terms and definitions
  • 3.2 Abbreviations
  • 3.3 Conventions
  • 4 to achieve the concept of
  • 4.1 Technology Orientation
  • 4.2 abstract FDT object model to achieve
  • 4.3 FDT Framework Application (FA)
  • 4.4 DTM business logic
  • 4.5 DTM function realization
  • 4.6 User Management
  • 4.7 FDT and system topology implementation
  • 4.8 module to achieve
  • 4.9 FDT Communication Implementation
  • 4.10 logo
  • 4.11 DTM Data Persistence and Synchronization Implementation
  • 4.12 access device data and input and output information to achieve
  • 4.13 DTM Instance Clone
  • 4.14 Concept of life cycle
  • 4.15 Audit Trail
  • 5 Technology Concepts
  • 5.1 Overview
  • 5.3 Support for 32-bit and 64-bit target platforms
  • 5.4 Object Activation and Deactivation
  • 5.5 Data Types
  • 5.6 Common Objects
  • 5.7 threads
  • 5.8 Localization Support
  • 5.9 DTM user interface to achieve
  • 5.10 DTM User Interface Hosting
  • 5.11 The realization of static function
  • 5.12 Persistence
  • 5.13 Comparison of DTM and Device Data
  • 5.14 Tracking
  • 5.15 Report Generation
  • 5.16 Security
  • 6 FDT Objects and Interfaces
  • 6.1 Overview
  • 6.2 Framework Applications
  • 6.3 DTM Business Logic
  • 6.4 DTM User Interface
  • 6.5 Communication Channel
  • 6.6 Availability of Interface Methods
  • 7 FDT data type
  • 7.1 Overview
  • 7.2 Data Types --- Foundations
  • 7.3 General Data Types
  • 7.4 Data Type --- DtmInfo/T ypeInfo
  • 7.5 Data Types --- DeviceIdentInfo
  • 7.6 Data Types for Installation and Deployment
  • 7.7 Data Type - Communication
  • 7.8 Data Type -BusCategory
  • 7.9 Data Type - Device/Instance Data
  • 7.10 Export and Import Data Types
  • 7.11 Description of the data types of the process data
  • 7.12 Data Type - Address Information
  • 7.13 Data Type -NetworkDataInfo
  • 7.14 Data Type-DTM Function
  • 7.15 Data Type - DTM Message
  • 7.16 DTM UI Dialog Box Operators Data Types
  • 7.17 Data Types -CommunicationChannelInfo
  • 7.18 Data Types - Hardware Identification and Scanning
  • 7.19 Data Type - DTM Report Type
  • 7.20 Device Information on Integrated DTMs
  • 8 Workflow
  • 8.1 Overview
  • 8.2 Instantiate, load and release
  • 8.3 DTM permanent storage
  • 8.4 Multi-user environment, locking and data transactions
  • 8.5 Performing DTM Functions
  • 8.6 DTM Communication
  • 8.7 Nested Communication
  • 8.8 Topology Planning
  • 8.9 Sub-DTM instantiation, configuration, movement and release
  • 8.11 Configuration of Communication Network
  • 8.12 Using IO Information.199
  • 8.13 Address Management
  • 8.14 Device Initiated Data Transfer
  • 8.15 Read Data and Write Data
  • 8.16 Compare Data
  • 8.17 Reassign a different DtmDeviceType 211 on a device node
  • 8.18 Partially Duplicated FDT Topology
  • 8.19 Audit trail sequence
  • 9 Install
  • 9.1 Overview
  • 9.2 Common Rules
  • 9.3 FDT Core Assembly Installation
  • 9.4 Communication Protocol Installation
  • 9.5 DTM Installation
  • 9.6 DTM Installer
  • 9.7 DTM Deployment
  • 9.8 Path and file information
  • 10.1 Overview
  • 10.2 Technical Concepts
  • 10.3 DTM Installation
  • 10.4 Life Cycle Scenario
  • 11.1 Overview
  • 11.2 Stand-alone Application
  • 11.3 Remote User Interface
  • 11.4 Distributed Multi-User Applications
  • 11.5 OPC UA
  • Appendix A (Normative) FDT2 use case model
  • A.1 Use Case Model Overview
  • A.2 Participants
  • A.3 Use Case
  • Appendix B (Normative) FDT interface definitions and data types
  • Appendix C (Normative) Mapping of Service to Interface Methods
  • C.1 Overview
  • C.2 DTM Services
  • C.3 represents the service of the object
  • C.4 Common Channel Services
  • C.5 Process Channel Services
  • C.6 Communication Channel Services
  • C.7 Framework Application Services
  • Appendix D (Normative) FDT Version Interoperability Guide
  • D.1 General
  • D.2 Overview
  • D.3 Component Interoperability
  • Appendix E (Normative) FDT1.2.x/This part of the backward compatibility
  • E.1 General
  • E.2 Parallel FDT Topology
  • E.3 Hybrid FDT Topology
  • E.4 FDT1.2.x/This part of the adapter
  • E.5 FDT1.2.xXML/This section data type converter
  • E.6 Backwards compatible with related sequences
  • Appendix F (Informative) Implementation Tips
  • F.1 General recommendations
  • F.2 IAsyncResult mode
  • F.3 Thread Best Practices
  • Appendix G (informative) Trademark name
  • Appendix H (informative) UML symbol
  • H.1 Overview
  • H.2 class diagram
  • H.3 Statechart
  • H.4 Use Case Figure
  • H.5 Sequence diagram
  • H.6 Object Figure
  • Appendix I (Informative) Physical Layer Example
  • I.1 Overview
  • I.2 INTERBUS
  • I.3 PROFIBUS
  • I.4 PROFINET
  • Appendix J (Informative) Predefined SemanticId
  • J.1 General
  • J.2 Data
  • J.3 Image
  • J.4 Document

5 Technology Concepts

5.13 Comparison of DTM and Device Data 69

5.3 Support for 32-bit and 64-bit target platforms 36

5.1 Overview 33

Support for.NETCLR Version 35

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.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.11 Description of the data types of the process data 122

7.6 Data Types for Installation and Deployment 102

7.19 Data Type - DTM Report Type 141

7.18 Data Types - Hardware Identification and Scanning 139

7.16 DTM UI Dialog Box Operators Data Types 137

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

7.7 Data Type - Communication 105

7.8 Data Type

7.9 Data Type - Device/Instance Data 112

7.10 Export and Import Data Types

7.12 Data Type - Address Information 128

7.13 Data Type

7.14 Data Type-DTM Function 134

7.15 Data Type - DTM Message 136

7.17 Data Types

7.20 Device Information on Integrated DTMs 142

8 Workflow 144

8.4 Multi-user environment, locking and data transactions 153

8.1 Overview 144

8.2 Instantiate, load and release 144

8.3 DTM permanent storage 150

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

Framework Application Structure

Appendix E (Normative) FDT1.2.x/This part of the backward compatibility 274

Figure 28 Protocol List and Type Information Attributes 43

Example of Figure 30. Protocol-specific assembly processing in a framework application 44

Figure 44. Example DTM WinForms control 63 is hosted in the WinForms framework application

Figure 176 Process Image Creation.201 Fig. 177 Modify Confirmation 202 while PLC is running

Figure 197 Example Protocol List 225

Figure 207 Check DTM Installation 243 for Support Type List

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.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 […]

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

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

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

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

J.1 General 297

J.2 Data 297

J.3 Image 297

J.4 Document 297

Ref. 298

Figure 45. Example: DTM WinForms Control 63 is hosted in a WPF framework application

DTM 149 Figure 124 Load Expert User Level DTMBL 150 Figure 125 Releases the Figure 126 Save DTM Data 151

DTM 192 Figure 167 Parent DTM moves one child

DTM 193 Figure 168 Parent DTM Remove child

Figure.199 Example.DtmManifest 227 Figure.200 Example of DtmUiManifest 228 Figure.201 DTM installation structure

......
This preview omits tables, figures, formulas and parts of the technical clauses. The complete document — 531 pages — is available in the English PDF.

Referenced standards

How to Download GB/T 29618.42-2017

  1. 1

    Add to cart

    Click "Download PDF" on this page and choose "Buy this standard". You can add more standards before checkout.

  2. 2

    Checkout

    Enter your email and billing details. Payment is processed securely by Stripe (cards or bank transfer). Prefer bank details? Request a quotation (min. order $300).

  3. 3

    Instant delivery (0–9 sec)

    Delivery is automatic: within seconds of payment you'll receive an email with a secure download link. The link stays valid for 72 hours.

  4. 4

    Invoice included

    A tax invoice is attached to the confirmation email. Need a custom invoice? Contact us.

Related Standards

English PDF
531 pages
Instant delivery (0–9 sec)
Invoice included
View Cart

Secure payment via Stripe

Payments accepted

VisaMastercardAmerican ExpressApple PayGoogle PayStripe

GB/T 29618.42-2017

$4,250.00