GB/T 29618.2: Evolution and historical versions
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 29618.2-2017 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Field device tool (FDT) interface specification -- Part 2: Concepts and detailed description
| Valid |
GB/T 29618.2-2017
|
| GB/T 29618.2-2013 | English | RFQ |
ASK
|
7 days [Need to translate]
|
Field device tool (FDT) interface specification -- Part 2: Concepts and detailed description
| Obsolete |
GB/T 29618.2-2013
|
PDF similar to GB/T 29618.2-2017
Basic data | Standard ID | GB/T 29618.2-2017 (GB/T29618.2-2017) | | Description (Translated English) | Field device tool (FDT) interface specification -- Part 2: Concepts and detailed description | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | N10 | | Classification of International Standard | 25.040 | | Word Count Estimation | 158,130 | | Date of Issue | 2017-07-31 | | Date of Implementation | 2018-02-01 | | Older Standard (superseded by this standard) | GB/T 29618.2-2013 | | 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.2-2017: Field device tool (FDT) interface specification -- Part 2: Concepts and detailed description
---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 2. Concepts and detailed description
ICS 25.040
N10
National Standards of People's Republic of China
Replacing GB/T 29618.2-2013
Field Device Tool (FDT) Interface Specification
Part 2. Concept and detailed description
Fielddevicetool (FDT) interfacespecification-
Part 2.Conceptsanddetaileddescription
(IEC 62453-2.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 IX
Introduction Ⅺ
1 Scope 1
2 Normative references 1
3 Terms and Definitions, Symbols and Abbreviations, Conventions 1
3.1 Terms and definitions 1
3.2 Symbols and Abbreviations 2
3.3 agreement 2
4 basic principle 2
4.1 Overview 2
4.2 Abstract FDT model 2
4.3 Modularity 14
4.4 bus category 14
4.5 Recognition 15
4.6 System and FDT Topology 16
4.7 FDT Communication 17
4.8 DTM, DTM Device Type and Hardware Identification Information 19
4.9 DTM data permanent storage and synchronization 21
4.10 DTM Device Parameters Access 22
4.11 DTM state machine 22
4.12 basic operation stage 24
4.13 FDT Version Interoperability 25
5 FDT Session Model and Use Case 27
5.1 Session Model Overview 27
5.2 Executive 28
5.3 Use Case 30
General Concepts
6.1 Address Management 44
6.2 Scanning and DTM Assignment 44
6.3 Configuration of the fieldbus master or communication scheduler 46
6.4 PLC Tools Support 46
6.5 Slave redundancy 48
7 FDT Service Specification 50
7.1 Service Specification Overview 50
7.2 DTM service 50
7.3 represents the object service 68
7.4 channel object service 68
7.5 Process Channel Object Services - Services for IO Related Information 69
7.6 Communication Channel Object Service 70
7.7 Framework Application Services 76
8 FDT dynamic behavior 85
8.1 Generate FDT Topology 85
8.2 Address Setting 87
8.3 Communication 89
8.4 Scanning and DTM Assignment 91
8.5 Multi-user environment 92
8.6 Change Notice 96
8.7 DTM Instance Data State Machine 96
8.8 Working with Redundant Slaves's Parent 99
8.9 DTM upgrade 100
Appendix A (Normative) FDT data type definition 103
A.1 Overview 103
A.2 basic data types 103
A.3 General data types 104
A.4 user information data type 122
A.5 DTM information data type 123
A.6 BTM data type 123
A.7 Device and Scan Identification Data Types 125
A.8 Functional Data Types 129
A.9 AuditTrail data type 132
A.10 Document Data Type 133
A.11 DeviceList Data Types 135
A.12 Network Management Data Types 136
A.13 Data Types for Instance 138
A.14 DeviceStatus data types 142
A.15 OnlineCompare data type 143
A.16 UserInterface data type 143
A.17 Fieldbus-specific data types 144
References 146
Figure 1 GB/T 29618 series Part 2 Ⅺ
Figure 2 Abstract FDT model 2
Figure 3 Integrated Communications Channel Framework Application 6
Figure 4 Device Type Manager (DTM) 6
Figure 5 Communication DTM 7
Figure 6 Device DTM 7
Figure 7 Gateway DTM 8
Figure 8 Composite Equipment DTM 9
Figure 9 modular equipment 10
Figure 10 Block Type Manager (BTM) 10
FIG. 11 shows the object 11
Figure 12 Channel object 12
Figure 13 Communication Channel 13
Figure 14 Combination of Process and Communication Channels 14
Figure 15 Identification of connected equipment 15
Figure 16 FDT Topology for a Simple System 16
Figure 17 FDT Topology for Complex System Topologies 17
Figure 18 Peer to Peer Communication 18
Figure 19 Nested Communication 19
Figure 20 DTM, DTM Device Type and Device Identification Information 20
Figure 21 Connected Hardware Identification 21
Figure 22 FDT Storage and Synchronization Mechanism 22
Figure 23 DTM state machine 23
Figure 24 allows sub-states of communication 24
Figure 25 The main use case Figure 28
Figure 26 Observation Example 30
Figure 27 Operational Example 31
Figure 28 Maintenance Cases 35
Figure 29 Planning Use Case 39
Figure 30 OEM Services 42
Figure 31 Manager Use Case 43
Figure 32 Address Setting by DTM Presentation Object 44
Figure 33 Fieldbus Scanning 45
Figure 34 Fieldbus Master Configuration Tool as part of DTM 46
Figure 35 Process Image 47
Figure 36 Layout information transmitted via the process image 47
Figure 37 Redundancy 48
Figure 38 Frame Application Trigger Generation FDT Topology 86
Figure 39 DTM Trigger Generation FDT Topology 86
Figure 40 Setting or Modifying Device Addresses - Using User Interface 87
Figure 41 Setting or Modifying Device Addresses - No User Interface 88
Figure 42 Interface Shows or modifies the addresses of all the sub-devices - using the user interface 88
Figure 43 Peer-to-peer Communication 89
Figure 44 Nested Communication 90
Figure 45 Device Initiated Data Transfer 91
Figure 46 Scan and DTM Assignment 92
Figure 47 Multi-user system 93
Figure 48 Normal Synchronization Mechanism 94
Figure 49 Typical Asynchronous Locking Mechanism 94
Fig. 50 Parameterization in the case of a synchronous locking mechanism 95
Figure 51 Example Data Modification State Machine 96
Figure 52 Permanent state machine for instance data 97
Figure 53 Managing Redundant Topology 100
Figure 54 Correlates the data to dataSetId 101
Figure 55 shows the supported dataSetId load data 102
Table 1 FDT object description 3
Table 2 FDT object description of the relationship between 4
Table 3 DTM Status Transitions 23
Table 4 Sub-state conversions for DTM "communicationAlowed" 24
Table 5 Operating Phase 25
Table 6 Executive 29
Table 7 Operational Cases 31
Table 8 Maintenance Cases 35
Table 9 Planning Use Cases 40
Table 10 Manager Use Cases 43
Table 11 PrivateDialogEnabled service parameters 50
Table 12 SetLanguage Services Parameters
Table 13 SetSystemGuiLabel Service Parameters
Table 14 Parameters for the GetTypeInformation service (for DTM)
Table 15 Parameter 53 of the GetTypeInformation service (for BTM)
Table 16 Parameter for the GetIdentificationInformation service (for DTM)
Table 17 Parameter for the GetIdentificationInformation service (for BTM)
Table 18 HardwareInformation Services (for DTM) Parameters
Table 19 GetActiveTypeInfo Service Parameters
Table 20 Parameter 54 for the GetActiveTypeInfo service (for BTM)
Table 21 Parameters for Initialize Service (for DTM)
Table 22 Parameters for the Initialize Service (for BTM)
Table 23 SetLinkedCommunicationChannel Service Parameters
Table 24 EnableCommunication service parameters 56
Table 25 ReleaseLinkedCommunicationChannel Service Parameters
Table 26 ClearInstanceData Service Parameters
Table 27 Terminate Service Parameters
Table 28 GetFunctions Service Parameters
Table 29 InvokeFunctions Service Parameters
Table 30 GetGuiInformation service parameters 58
Table 31 Parameters of the OpenPresentation service 59
Table 32 ClosePresentation service parameters 59
Table 33 GetChannels Service Parameters 60
Table 34 GetDocumentation Service Parameters 60
Table 35 InstanceDataInformation parameters for service 60
Table 36 InstanceDataRead Service Parameters 61
Table 37 InstanceDataWrite service parameters 61
Table 38 Verify service parameters 62
Table 39 CompareDataValueSets service parameters 62
Table 40 DeviceDataInformation service parameters 62
Table 41 DeviceDataRead Service Parameters
Table 42 DeviceDataWrite Service Parameters
Table 43 Network Management Information Services parameters 64
Table 44 Network Management Information Services parameters 64
Table 45 Parameter 64 for DeviceStatus service (for DTM)
Table 46 Parameter 65 of the CompareDataValueSetWithDeviceData service (for DTM)
Table 47 Parameters for WriteDataToDevice Service (for DTM) 65
Table 48 Parameter 65 of the ReadDataFromDevice service (for DTM)
Table 49 OnLockInstanceData service parameters 66
Table 50 OnUnlockInstanceData service parameters 66
Table 51 OnInstanceDataChanged Service Parameters 67
Table 52 OnInstanceChildDataChanged service parameters 67
Table 53 Export Service Parameters 67
Table 54 Import service parameters 68
Table 55 Parameters for the ReadChannelInformation service 68
Table 56 Parameters for the WriteChannelInformation Service 69
Table 57 Parameters for the ReadChannelData Service 69
Table 58 Parameters for the WriteChannelData Service 69
Table 59 GetSupportedProtocols service parameters 70
Table 60 Connect service parameters 70
Table 61 Disconnect Services Parameters 71
Table 62 AbortRequest Service Parameters 71
Table 63 AbortIndication Service Parameters 71
Table 64 Transaction Service Parameters 72
Table 65 Parameter for the SequenceDefine service 72
Table 66 SequenceStart Service Parameters 73
Table 67 ValidateAddChild service parameters 73
Table 68 ChilaAdded Service Parameters 73
Table 69 Parameter ValidateRemoveChild Service 74
Table 70 ChildRemoved Service Parameters 74
Table 71 SetChildrenAddresses Service Parameters
Table 72 GetChannelFunctions Service Parameters
Table 73 GetGuiInformation Service parameters 75
Table 74 Scan Service Parameters
Table 75 OnErrorMessage service parameters
Table 76 OnProgress service parameters 77
Table 77 OnOnlineStatusChanged Service Parameters
Table 78 Parameters for OnFunctionsChanged Service 77
Table 79 GetDtmInfoList service parameters 78
Table 80 CreatChild (DTM) Service Parameters 78
Table 81 CreatChild (BTM) Service Parameters 78
Table 82 DeleteChild service parameters 79
Table 83 Parameters of the MoveChild Service 79
Table 84 GetParentNodes Service Parameters 79
Table 85 GetChildNodes Service Parameters 80
Table 86 GetDtm service parameters 80
Table 87 ReleaseDtm service parameters 80
Table 88 Parameters for the OnAddedRedundantChild service 81
Table 89 OnRemoveRedundantChild service parameters 81
Table 90 SaveInstanceData service parameters 81
Table 91 LoadInstanceData Service Parameters 82
Table 92 GetPrivateDtmStorageInformation parameters for service 82
Table 93 LockInstanceData Service Parameters 82
Table 94 UnlockInstanceData service parameters 83
Table 95 Parameter 83 for the OnInstanceDataChanged service
Table 96 Parameter ValidateProcessImage Service 83
Table 97 Parameters of the OpenPresentationRequest service 84
Table 98 ClosePresentationRequest service parameters 84
Table 99 UserDialog service parameters 84
Table 100 RecordAuditTrailEvent service parameters 85
Table 101 Example Data Modification State Machine 97
Table 102 Permanent State Machine for Instance Data 97
Table 103 Examples of DTM lifecycles 98
Table A.1 Basic data types 104
Table A.2 Simple General Data Types 104
Table A.3 classificationId enumeration value of the definition of 111
Table A.4 General Structured Data Types 113
Table A.5 Simple User Information Data Types 122
Table A.6 structured user information data type 123
Table A.7 structured DTM information data types 123
Table A.8 Simple BTM Data Types 124
Table A.9 structured BTM data types
Table A.10 Simple Device Identification Data Types 125
Table A.11 Structured Device Identification Data Types 126
Table A.12 Simple Function Data Types 129
Table A.13 structured functional data types 130
Table A.14 Simple auditTrail Data Types 132
Table A.15 structured auditTrail data types
Table A.16 Simple Document Data Types
Table A.17. Structured Document Data Types
Table A.18 Simple devList Data Types
Table A.19 structured devList data types
Table A.20 Simple Network Management Data Types 137
Table A.21 Structured Network Management Data Types
Table A.22 Simple Instance Data Types
Table A.23 structured instance data types
Table A.24 Simple Device Status Data Types 142
Table A.25 structured device status data types
Table A.26 Simple Online Comparison of Data Types 143
Table A.27 Structured online comparison data types 143
Table A.28 Simple user interface data types
Table A.29 structured user interface data types
Table A.30 Fieldbus Data Types 145
Foreword
GB/T 29618 "Field Device Tool (FDT) Interface Specification" is divided into the following sections.
--- Part 1. Overview and guidelines;
--- Part 2. Concept and detailed description;
--- Part 301. Communication profile integrated FF field bus specification;
--- Part 302. Communication rules integrated universal industrial agreement;
--- Part 306. Communication rules integrated INTERBUS fieldbus specification;
--- Part 309. Communication profile integrated addressable remote sensor high-speed channel;
--- Part 315. Communication line regulation integrated MODBUS field bus specification;
--- Part 41. Object model lineage integration common object model;
--- Part 42. Object model rules integrated common language infrastructure;
--- Part 515. Common object model of communication to achieve MODBUS field bus specification
--- Part 51-10. Common Object Model Communication to achieve FF Fieldbus Specification;
--- Part 51-20. Common object model of communication to achieve universal industrial agreement;
Part 51-60. General object model communication to achieve INTERBUS fieldbus specification;
--- Part 51-90. Common object model of communication to achieve IEC 61784CPF9;
--- Part 51-150. Common object model of communication to achieve IEC 61784CPF15;
--- Part 52-10. General language infrastructure to achieve communication FF fieldbus specification;
--- Part 52-20. Common language infrastructure to achieve universal industrial communication protocol;
--- Part 52-31. Communication of the common language infrastructure IEC 61784CP3/1 and CP3/2;
--- Part 52-32. Communication of common language infrastructure IEC 61784CP3/4, CP3/5 and CP3/6;
--- Part 52-90. Common language infrastructure to achieve communication EC61784CPF9;
--- Part 52-150 of the General Language Infrastructure Communication IEC 61784CPF15;
--- Part 61. Generic object model device type manager style guide;
--- Part 62. Field Device Tool (FDT) common language infrastructure style guide.
This section GB/T 29618 Part 2.
This section drafted in accordance with GB/T 1.1-2009 given rules.
This Part replaces GB/T 29618.2-2013 "Field Device Tool (FDT) Interface Specification Part 2. Concept and detailed description",
This section compared with GB/T 29618.2-2013 In addition to editorial changes, the main technical changes are as follows.
--- The range has been adjusted accordingly (see Chapter 1,.2013 Chapter 1);
--- Normative references have been adjusted accordingly (see Chapter 2,.2013 Chapter 2);
--- Added the term "sub DTM" (see 3.1.1);
--- Added the term "parent DTM" (see 3.1.4);
--- Increased agreement "UML use" (see 3.3.1);
--- Removed the BTM item in Table 1, which indicated that the channel item was adjusted accordingly (see Table 1 in Table 1,.2013).
--- Added an overview of the beginning of the framework application (see 4.2.2.1);
--- Increased system communication (see 4.2.2.2);
--- Added DTM Business Logic Overview (see 4.2.3.1);
--- Added DTM category and the beginning of the overview, communication DTM (COMM-DTM), DTM equipment, gateway DTM, composite set
DTM, Module DTM, Block Type Manager (BTM);
--- Added DTM functions, command functions and static functions (see 4.2.3.3);
--- Increased identification and specific content (see 4.5);
--- Increased system and FDT topology (see 4.6);
--- Increased FDT communication (see 4.7);
--- Added Figures 7, 8, 9, 10 (see 4.2.3.2), Figure 12, Figure 13, Figure 14 (see 4.2.4), Figure 20, Figure 21
Figure 22 (see 4.9), Figure 23, Figure 24 (see 4.11), Figure 26, Figure 27, Figure 28, Figure 29, Figure 30 and Figure 31
--- Removed the PLC overview of the beginning of the PLC tool support document chapter, PLC process image changes (see.2013 version
6.4);
--- Removed part of ReadDataFromDevice service (see.2013 version 7.2.12.4);
--- Deleted the process of image authentication related FA services (see.2013 version 7.7.7).
This section uses the translation method identical with IEC 62453-2.2016 "Field Device Tool (FDT) Interface Specification Part 2. Concepts and
Detailed description "(in English).
The documents of our country that are consistent with the corresponding international documents that are normative references in this section are as follows.
--- Part 1 GB/T 15969.1-2007 programmable logic controller General Information (IEC 61131-1.2003, IDT);
--- Part 2. Equipment requirements and testing (IEC 61131-2.2007, IDT); --- GB/T 15969.2-2008;
Programmable logic controller - Part 3. Programming language (IEC 61131-3.2002, IDT);
GB/T 15969.4-2007 Programmable controller Part 4. User guide (IEC 61131-4.2004, IDT);
--- GB/T 15969.5-2002 programmable logic controller Part 5. Communication (idtIEC 61131-5.2000);
--- Part 6. Functional safety (IEC 61131-6.2012, IDT) --- GB/T 15969.6-2015;
--- GB/T 15969.7-2008 Programmable controller Part 7. Fuzzy control programming (IEC 61131-7.2000,
IDT);
--- GB/T 15969.8-2007 Programmable controller Part 8 - Programming language application and implementation guidelines (IEC /TR
61131-8.2003, IDT);
--- GB/T 29618.301-2015 Field Device Tool (FDT) Interface Specification Part 301. Communication Profile Integration FF
Fieldbus specification (IEC 62453-301.2009, IDT);
--- GB/T 29618.302-2013 Field Device Tool (FDT) Interface Specification Part 302. Communication Profile Integration General
Industrial Agreement (IEC 62453-302.2009, IDT);
--- GB/T 29618.306-2017 Field Device Tool (FDT) Interface Specification Part 306. Communication Profile Integration
INTERBUS Fieldbus Specification (IEC 62453-306 Ed. 1.0.2009, IDT);
--- GB/T 29618.309-2013 Field Device Tool (FDT) Interface Specification Part 309.
Remote Sensor High Speed Channel (IEC 62453-309.2009, IDT);
--- GB/T 29618.315-2013 Field Device Tool (FDT) Interface Specification Part 315. Communication Profile Integration
MODBUS Fieldbus Specification (IEC 62453-315.2009, IDT).
This part is proposed by China Machinery Industry Federation.
This part of the National Industrial Process Measurement and Control Standardization Technical Committee (SAC/TC124) centralized.
This part of the drafting unit. Southwest University, Mechanical Industry Instrumentation Technology and Economy Institute, Chongqing Chuan Yi Automation Co., Ltd.
Division, Shanghai Automation Instrumentation Co., Ltd., Rockwell Automation (China) Co., Ltd., Zhejiang University Institute of Intelligent Systems and Control, Suzhou
Software Co., Ltd. of the United States, Heights (Shanghai) Automation System Co., Ltd., Schneider Electric (China) Co., Ltd.
The main drafters of this section. Zhang Yu, Liu Feng, Wang Chunxi, Wang Shuo, Wang Deji, Tian Yingming, Zhang Qingjun, Hua Rong, Feng Dongqin, Lu Yajun, Li Jing,
Wang Yong, Du Jialin, Pan Dongbo.
This part replaces the standards previously issued as.
--- GB/T 29618.2-2013.
Introduction
This section provides interface specifications for developers of FDT (Field Device Tool) components, FDT components for client/server architecture
Functional control and data access. This section is the result of analysis and design in the development of standard interfaces. These standard interfaces are easy to multiple
Manufacturers develop servers and clients that seamlessly interoperate.
Integrating field devices into the control system requires some additional tasks. In addition to the need for fieldbus specific tools and equipment specific
Tools, you need to integrate these tools into higher-level system-wide planning or engineering tools. In particular, in order to be heterogeneous in large scale
Of the control system (typically in the process industry), it is important to clearly define the relevant engineering interfaces that are easy to use.
Device-specific software components created in this section are called device type managers (DTMs). It passes the FDT defined in this section
Service that integrates all device-specific data, features, and business rules into the system.
The FDT/DTM method is open to all types of fieldbus and allows integration of various devices into heterogeneous systems.
Figure 1 shows the GB/T 29618.2 GB/T 29618 series standard structure in the position.
Figure 1 GB/T 29618 series of Part 2
Field Device Tool (FDT) Interface Specification
Part 2. Concept and detailed description
1 Scope
This part of GB/T 29618 explains the general principles of field device tools concepts. The principles of this section apply to a variety of industrial applications
For example, engineering systems, configuration programs, monitoring and diagnostic applications.
This section specifies the common objects, common object behavior and the interaction between common objects, which are the basis of FDT.
2 Normative references
The following documents for the application of this document is essential. For dated references, only the dated version applies to this article
Pieces. For undated references, the latest edition (including all amendments) applies to this document.
GB/T 29618.1-2017 Field Device Tool (FDT) Interface Specifications Part 1. Overview and Guidance (IEC 62453-1.
2016, IDT)
IEC 61131 (all parts) Programmable controllers (Programmablecontrollers)
IEC /T R62390.2005 Common automation equipment-Profileguideline
IEC 62453-3xy (all parts) Field Device Tool (FDT) Interface Specification Part 3xy. Field Communication Profile Integration
DeviceTool (FDT) interfacespecification-Part 3xy.Communicationprofileintegration)
3 Terms and definitions, symbols and abbreviations, conventions
3.1 Terms and definitions
GB/T 29618.1 defined and the following terms and definitions apply to this document.
3.1.1
Sub DTM childDTM
The DTM instance in the FDT project can be categorized by its relationship to the parent DTM.
Note Any DTM that uses FDT communication can be classified as a sub DTM (ie, device DTM, gateway DTM, module DTM, and BTM).
3.1.2
FDT version FDTversion
Relevant technical implementation-specific version of the organization.
Note. The FDT version is specified in IEC /T R62453-41 or IEC /T R62453-42.
3.1.3
Monolithic DTM monlithicDTM
The monolithic DTM represents the entire device that contains all of its modules.
Note. Other concepts that represent device modules are also included in this section, such as module DTM (ModuleDTM) and BTM.
3.1.4
Parent DTM parentDTM
The DTM instance in an FDT project can be categorized by its relationship to a sub DTM.
Note Any DTM that provides FDT communication can be classified as a parent DTM (eg, communication DTM, gateway DTM, composite device DTM).
|