|
US$794.00 ยท In stock
Delivery: <= 4 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 29618.529-2018: Field device tool (FDT) interface specification -- Part 529: Communication implementation for common language infrastructure -- IEC 61784 CPF 9
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 29618.529-2018 | English | 794 |
Add to Cart
|
4 days [Need to translate]
|
Field device tool (FDT) interface specification -- Part 529: Communication implementation for common language infrastructure -- IEC 61784 CPF 9
| Valid |
GB/T 29618.529-2018
|
PDF similar to GB/T 29618.529-2018
Basic data | Standard ID | GB/T 29618.529-2018 (GB/T29618.529-2018) | | Description (Translated English) | Field device tool (FDT) interface specification -- Part 529: Communication implementation for common language infrastructure -- IEC 61784 CPF 9 | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | N10 | | Classification of International Standard | 25.040 | | Word Count Estimation | 42,474 | | Date of Issue | 2018-09-17 | | Date of Implementation | 2019-04-01 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 29618.529-2018: Field device tool (FDT) interface specification -- Part 529: Communication implementation for common language infrastructure -- IEC 61784 CPF 9
---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 529. Communication implementation of common language infrastructure IEC 61784 CPF 9)
ICS 25.040
N10
National Standards of People's Republic of China
Field Device Tool (FDT) Interface Specification
Part 529. Communication implementation of a common language infrastructure
IEC 61784CPF9
Part 529.Communicationimplementationforcommonlanguageinfrastructure-
IEC 61784CPF9
[IEC /T R62453-52-90.2017, Fielddevicetool(FDT) interfacespecification-
Part 52-90. Communicationimplementationforcommonlanguageinfrastructure-
IEC 61784CPF9, IDT]
2018-09-17 released.2019-04-01 implementation
State market supervision and administration
China National Standardization Administration issued
Content
Foreword V
Introduction VI
1 Scope 1
2 Normative references 1
3 Terms, definitions, symbols, abbreviations and conventions 1
3.1 Terms and Definitions 1
3.2 Symbols and abbreviations 1
3.3 Convention 1
3.3.1 Data Type Name and Data Type Reference 1
3.3.2 Vocabulary 2 describing the degree of demand
3.3.3 Use of UML 2
4 bus category 2
5 Accessing instance and device data 2
5.1 Overview 2
5.2 IO signal provided by DTM 2
5.3 Data Interface 3
5.3.1 Overview 3
5.3.2 Mapping HART Data Types to FDT Data Types 3
5.3.3 SemanticInfo 4
5.3.4 Display data using IDeviceData and IInstanceData interface 4
6 Protocol Specific Behavior 10
6.1 Support burst mode 10
6.2 Device Addressing 11
6.3 Support for scanning 11
6.4 Support extended command number 11
6.5 Support for communication failure or timeout processing 11
6.6 Support for delayed response processing 11
6.7 Support for topology mixed with HART protocol 11
6.8 Support for multiple gateway nested communications 12
6.9 Support for Wireless HART Topology 12
6.10 Transparent Gateway 12
6.10.1 Overview 12
6.10.2 Scenario 1. Creating Topology Manually 12
6.10.3 Scenario 2. Scanning and Adding Topology 12
7 Protocol-specific usage of generic data types 12
8 Protocol-specific public data types 13
8.1 HartDeviceAddress data type 13
8.2 HartDeviceIpAddress data type 14
8.3 HartDeviceWirelessAddress Data Type 15
9 Network Management Data Type 16
10 Communication data type 16
10.1 Overview 16
10.2 HartConnectRequest data type 17
10.3 HartConnectResponse data type 17
10.4 HartLongAddress data type 18
10.5 HartDisconnectRequest data type 18
10.6 HartDisconnectResponse data type 19
10.7 HartTransactionRequest data type 20
10.8 HartTransactionResponse data type 20
10.9 Hart Status Data Type 21
10.10 HartAbortMessage data type 21
10.11 HartSubscribeRequest data type 22
10.12 HartSubscribeResponse data type 22
10.13 HartUnsubscribeRequest data type 23
10.14 HartUnsubscribeResponse data type 23
11 Data type of process data information 24
11.1 Overview 24
11.2 HartIOSignalInfo data type 24
12 Device Identification Data Type 25
12.1 Overview 25
12.2 HartDeviceScanInfo data type 25
12.3 HartDeviceIdentInfo data type 30
12.4 Mapping of Information Sources 30
Reference 33
Figure 1 This part of VI in GB/T 29618
Figure 2 Structured information for device variables 8
Figure 3 Structured information of dynamic variables 9
Figure 4 Structured information for extended device status 10
Figure 5 Device-initiated data transmission using burst mode 11
Figure 6 HartDeviceAddress data type 13
Figure 7 HartDeviceIpAddress data type 14
Figure 8 HartDeviceWirelessAddress data type 15
Figure 9 HartNetworkData data type 16
Figure 10 HartConnectRequest data type 17
Figure 11 HartConnectResponse data type 18
Figure 12 HartDisconnectRequest data type 19
Figure 13 HartDisconnectResponse data type 19
Figure 14 HartTransactionRequest data type 20
Figure 15 HartTransactionResponse data type 20
Figure 16 HartAbortMessage data type 21
Figure 17 HartSubscribeRequest data type 22
Figure 18 HartSubscribeResponse data type 22
Figure 19 HartUnsubscribeRequest data type 23
Figure 20 HartUnsubscribeResponse data type 23
Figure 21 HartIOSignalInfo data type 24
Figure 22 HartDeviceScanInfo data type 25
Figure 23 HartDeviceIdentInfo data type 30
Table 1 Output signal information in IOSignaInfo/HartIOSignaInfo 2
Table 2 Basic data type mapping 3
Table 3 SemanticInfo attribute description 4
Table 4 Basic variables exported by IDeviceData and IInstanceData interface 4
Table 5 Basic variables only output from the IDeviceData interface 6
Table 6 Protocol-specific usage of generic data types 13
Table 7 HartDeviceAddress data type 14
Table 8 HartDeviceIpAddress data type 15
Table 9 HartDeviceWirelessAddress Data Type 16
Table 10 HartNetworkData data type 16
Table 11 HartConnectRequest data type 17
Table 12 HartConnectResponse data type 18
Table 13 HartLongAddress data type 18
Table 14 HartDisconnectRequest data type 19
Table 15 HartDisconnectResponse data type 19
Table 16 HartTransactionRequest data type 20
Table 17 HartTransactionResponse data type 21
Table 18 Hart Status Data Type 21
Table 19 HartAbortMessage data type 22
Table 20 HartSubscribeRequest data type 22
Table 21 HartSubscribeResponse data type 23
Table 22 HartUnsubscribeRequest data type 23
Table 23 HartUnsubscribeResponse data type 24
Table 24 Usage of the HartIOSignalInfo data type 24
Table 25 HartIOSignalInfo data type 25
Table 26 HartDeviceScanInfo data type 26
Table 27 Protocol-Specific Mapping of Scan Information 27
Table 28 HartDeviceIdentInfo data type 30
Table 29 Protocol Specific Mappings for Identification Information 31
Foreword
GB/T 29618 "Field Device Tool (FDT) Interface Specification" is temporarily divided into the following parts.
--- Part 1. Overview and guidelines;
--- Part 2. Concepts and detailed descriptions;
--- Part 301. Communication profile integration FF fieldbus specification;
--- Part 302. Communication Profile Integration General Industrial Agreement;
--- Part 306. Communication profile integration INTERBUS fieldbus specification;
--- Part 309. Communication profile integration of addressable remote sensor high-speed channel;
--- Part 315. Communication profile integration MODBUS fieldbus specification;
--- Part 41. Object model profile integration common object model;
--- Part 42. Object model profile integration common language infrastructure;
--- Part 515. General object model communication implementation MODBUS fieldbus specification;
--- Part 511. Communication of the general object model to implement the FF fieldbus specification;
--- Part 512. Common object model communication implementation of general industrial protocols;
--- Part 516. Communication of the universal object model to implement the INTERBUS fieldbus specification;
--- Part 519. Communication implementation of the generic object model IEC 61784CPF9;
--- Part 5115. Communication implementation of the general object model IEC 61784CPF15;
--- Part 521. Communication of the common language infrastructure to implement the FF fieldbus specification;
--- Part 522. Common language infrastructure communication implementation of general industrial protocols;
--- Part 5231. Communication implementation of common language infrastructure IEC 61784CP3/1 and CP3/2;
--- Part 5232. Communication implementation of common language infrastructure IEC 61784CP3/4, CP3/5 and CP3/6;
--- Part 529. Communication implementation of the common language infrastructure IEC 61784CPF9;
--- Part 5215. Communication implementation of the common language infrastructure IEC 61784CPF15;
--- Part 61. Device Type Manager Style Guide for the Common Object Model;
--- Part 62. Field Device Tool (FDT) Style Guide.
This part is part 529 of GB/T 29618.
This part is drafted in accordance with the rules given in GB/T 1.1-2009.
This section uses the translation method equivalent to IEC /T R62453-52-90..2017 "Field Device Tool (FDT) Interface Specification No. 52-90
Part. Communication of the common language infrastructure implements IEC 61784CPF9.
The documents of our country that have a consistent correspondence with the international documents referenced in this part are as follows.
--- GB/T 29618.309-2013 Field Device Tool (FDT) Interface Specification Part 309. Communication Profile Integration Addressable
Remote sensor high speed channel (IEC 62453-309..2009, IDT).
This section has made the following editorial changes.
--- Modified the standard name.
This part was proposed by the China Machinery Industry Federation.
This part is under the jurisdiction of the National Industrial Process Measurement Control and Automation Standardization Technical Committee (SAC/TC124).
This section drafted by. Southwest University, Mechanical Industry Instrumentation Institute of Integrated Technology and Economics, He Youxin (Shanghai) Automation System Trade
Yi Co., Ltd., Suzhou Meiming Software Co., Ltd., Rockwell Automation (China) Co., Ltd., Shanghai Automation Instrument Co., Ltd., Zhejiang
University, Schneider Electric (China) Co., Ltd., Chongqing Sichuan Instrument Automation Co., Ltd.
The main drafters of this section. Zhang Wei, Zhou Xuelian, Lv Jing, Wang Chunxi, Wang Shuo, Li Jing, Lu Yajun, Hua Wei, Zhang Qingjun, Feng Dongqin, Wang Yong,
Tian Yingming, Du Jialin, Wang Deji.
Introduction
This section is an interface specification for FDT for functional control and data access in a client/server architecture (currently
Field device tool) component developer. This section is intended to develop the results of standard interfaces, analysis and design processes that are used to facilitate
Seamless interoperability between components developed by a manufacturer.
Integrating the fieldbus into the control system requires some additional tasks. In addition to specific fieldbus or specific device tools
In addition, it is necessary to integrate these tools into higher-level system planning or engineering tools. In particular, for extended and heterogeneous control systems
The use of the medium, usually in the field of the process industry, the clear definition of the engineering interface that is easy for all participants to use is very heavy
need.
DTM (Device Type Manager, DeviceTypeManager) is a software component of a specific device, which will be
The DTM software is provided to the user along with the device. The DTM is integrated into the engineering tool via the FDT interface defined in the specification. The episode
The method is open to all fieldbuses, thus meeting the requirements for integrating different types of devices in heterogeneous control systems.
Figure 1 shows the location of this part in the structure of GB/T 29618.
Figure 1 This part of GB/T 29618
Field Device Tool (FDT) Interface Specification
Part 529. Communication implementation of a common language infrastructure
IEC 61784CPF9
1 Scope
This part of GB/T 29618 provides the integration of HART technology into the FDT interface specification (GB/T 29618.42) based on the CLI
Realized information.
This section specifies the implementation of communications and other services based on IEC 62453-309.
This section does not contain the FDT specification or the FDT specification.
2 Normative references
The following documents are indispensable for the application of this document. For dated references, only dated versions apply 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 Specification Part 1. Overview and Guidelines (IEC 62453-1.
2016, IDT)
GB/T 29618.2-2017 Field device tool (FDT) interface specification Part 2. Concepts and detailed description (IEC 62453-2.
2016, IDT)
GB/T 29618.42-2017 Field Device Tool (FDT) Interface Specification Part 42. Object Model Profiles
Basic structure (IEC /T R62453-42.2016, IDT)
IEC 61784-1.2014 Industrial Communication Network Profiles Part 1. Fieldbus Profiles (Industrialcommunication
networks-Profiles-Part 1. Fieldbusprofiles)
IEC 62453-309.2016 Field Device Tool (FDT) Interface Specification Part 309. Communication Profile Integration IEC 61784
CPF9[Fielddevicetool(DFT)interfacespecification-Part 309.Communicationprofileintegration-
IEC 61784CPF9]
3 Terms, definitions, symbols, abbreviations and conventions
3.1 Terms and definitions
Terms defined in GB/T 29618.1-2017, GB/T 29618.2-2017, GB/T 29618.42-2017 and IEC 62453-309
And definitions apply to this document.
3.2 Symbols and abbreviations
Symbols defined by GB/T 29618.1-2017, GB/T 29618.2-2017, GB/T 29618.42-2017 and IEC 62453-309
And abbreviations apply to this document.
3.3 Convention
3.3.1 Data Type Names and Data Type References
The naming and reference conventions for data types are explained in A.1 of GB/T 29618.2-2017.
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 29618.529-2018_English be delivered?Answer: Upon your order, we will start to translate GB/T 29618.529-2018_English as soon as possible, and keep you informed of the progress. The lead time is typically 2 ~ 4 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of GB/T 29618.529-2018_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 29618.529-2018_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 [email protected]. 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.
|