|
US$1104.00 ยท In stock
Delivery: <= 4 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 29618.5215-2018: Field device tool (FDT) interface specification -- Part 5215: Communication implementation for common language infrastructure -- IEC 61784 CPF 15
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 29618.5215-2018 | English | 1104 |
Add to Cart
|
4 days [Need to translate]
|
Field device tool (FDT) interface specification -- Part 5215: Communication implementation for common language infrastructure -- IEC 61784 CPF 15
| Valid |
GB/T 29618.5215-2018
|
PDF similar to GB/T 29618.5215-2018
Basic data | Standard ID | GB/T 29618.5215-2018 (GB/T29618.5215-2018) | | Description (Translated English) | Field device tool (FDT) interface specification -- Part 5215: Communication implementation for common language infrastructure -- IEC 61784 CPF 15 | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | N10 | | Classification of International Standard | 25.40 | | Word Count Estimation | 58,585 | | 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.5215-2018: Field device tool (FDT) interface specification -- Part 5215: Communication implementation for common language infrastructure -- IEC 61784 CPF 15
---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 5115. Communication Implementation of Common Language Infrastructure IEC 61784 CPF 15)
ICS 25.40
N10
National Standards of People's Republic of China
Field Device Tool (FDT) Interface Specification
Part 5115. Common Language Infrastructure
Communication implementation of IEC 61784CPF15
Part 5215. Communicationimplementationforcommonlanguage
infrastructure-IEC 61784CPF15
[IEC /T R62453-52-150.2017, Fielddevicetool(FDT)interface
specification-Part 52-150. Communicationimplementationfor
commonlanguageinfrastructure-IEC 61784CPF15, IDT]
2018-09-17 released.2019-04-01 implementation
State market supervision and administration
China National Standardization Administration issued
Content
Preface VII
Introduction VIII
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 2
3.3 Convention 2
3.3.1 References to data type names and data types 2
3.3.2 Vocabulary requirements 2
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 2
5.3.1 Public Data Set 2
5.3.2 Mapping of Modbus data types to FDT data types 3
5.3.3 SemanticInfo 3
6 Specific behavior of the agreement 3
6.1 Modbus data and addressing model 3
6.2 Modbus related information of device DTM 4
6.3 Broadcast 4
6.4 Unconfirmed Private Modbus Request 5
7 Protocol-specific usage of generic data types 5
8 Protocol-specific public data types. ModbusDeviceAddress 6
9 Network Management Data Type 7
9.1 Overview 7
9.2 Configuration 8
9.3 Process Data Item 8
9.4 Parameterization 8
10 communication data type 8
10.1 Overview 8
10.2 ModbusConnectRequest 8
10.3 ModbusConnectResponse 9
10.4 ModbusDisconnectRequest 9
10.5 ModbusDisconnectResponse 10
10.6 ModbusAbortMessage 10
10.7 ModbusReadCoilsRequest 11
10.8 ModbusReadCoilsResponse 11
10.9 ModbusReadDiscreteInputsRequest 12
10.10 ModbusReadDiscreteInputsResponse 13
10.11 ModbusReadHoldingRegistersRequest 13
10.12 ModbusReadHoldingRegistersResponse 14
10.13 ModbusReadInputRegistersRequest 15
10.14 ModbusReadInputRegistersResponse 15
10.15 ModbusWriteSingleCoilRequest 16
10.16 ModbusWriteSingleCoilResponse 17
10.17 ModbusWriteSingleRegisterRequest 17
10.18 ModbusWriteSingleRegisterResponse 18
10.19 ModbusReadExceptionStatusRequest 19
10.20 ModbusReadExceptionStatusResponse 19
10.21 ModbusDiagnosticsRequest 20
10.22 ModbusDiagnosticsResponse 21
10.23 ModbusGetCommEventCounterRequest 22
10.24 ModbusGetCommEventCounterResponse 22
10.25 ModbusGetCommEventLogRequest 23
10.26 ModbusGetCommEventLogResponse 23
10.27 ModbusWriteMultipleCoilsRequest 24
10.28 ModbusWriteMultipleCoilsResponse 25
10.29 ModbusWriteMultipleRegistersRequest 26
10.30 ModbusWriteMultipleRegistersResponse 26
10.31 ModbusReportSlaveIDRequest 27
10.32 ModbusReportSlaveIDResponse 28
10.33 ModbusReadFileRecordRequest 28
10.34 ModbusReadFileSubRequest 29
10.35 ModbusReadFileRecordResponse 30
10.36 ModbusReadFileSubResponse 31
10.37 ModbusWriteFileRecordRequest 31
10.38 ModbusWriteFileSubRequest 32
10.39 ModbusWriteFileRecordResponse 32
10.40 ModbusMaskWriteRegisterRequest 33
10.41 ModbusMaskWriteRegisterResponse 33
10.42 ModbusReadWriteRegistersRequest 34
10.43 ModbusReadWriteRegistersResponse 35
10.44 ModbusReadFiFoQueueRequest 35
10.45 ModbusReadFiFoQueueResponse 36
10.46 ModbusEncapsulatedInterfaceTransportRequest 37
10.47 ModbusEncapsulatedInterfaceTransportResponse 37
10.48 ModbusReadDeviceIdentificationRequest 38
10.49 ModbusReadDeviceIdentificationResponse 39
10.50 ModbusPrivateRequest 41
10.51 ModbusPrivateResponse 41
10.52 ModbusUnconfirmedPrivateRequest 42
10.53 ModbusUnconfirmedPrivateResponse 43
10.54 ModbusExceptionResponse 43
11 Data type 44 for process data information
11.1 Overview 44
11.2 ModbusIOSignalInfo 44
11.3 Mapping of Modbus data types to FDT data types 46
12 device identification 46
12.1 Overview 46
12.2 ModbusDeviceScanInfo Data Type 46
12.3 ModbusDeviceIdentInfo data type 47
12.4 Information Source Mapping 48
Reference 50
Figure 1 This part of GB/T 29618 VIII
Figure 2 Modbus data and addressing model 4
Figure 3 ModbusDeviceAddress 6
Figure 4 ModbusNetworkData 7
Figure 5 ModbusConnectRequest 8
Figure 6 ModbusConnectResponse 9
Figure 7 ModbusDisconnectRequest 9
Figure 8 ModbusDisconnectResponse 10
Figure 9 ModbusAbortMessage 10
Figure 10 ModbusReadCoilsRequest 11
Figure 11 ModbusReadCoilsResponse 12
Figure 12 ModbusReadDiscreteInputsRequest 12
Figure 13 ModbusReadDiscreteInputsResponse 13
Figure 14 ModbusReadHoldingRegistersRequest 14
Figure 15 ModbusReadHoldingRegistersResponse 14
Figure 16 ModbusReadInputRegistersRequest 15
Figure 17 ModbusReadInputRegistersResponse 16
Figure 18 ModbusWriteSingleCoilRequest 16
Figure 19 ModbusWriteSingleCoilResponse 17
Figure 20 ModbusWriteSingleRegisterRequest 18
Figure 21 ModbusWriteSingleRegisterResponse 18
Figure 22 ModbusReadExceptionStatusRequest 19
Figure 23 ModbusReadExceptionStatusResponse 20
Figure 24 ModbusDiagnosticsRequest 20
Figure 25 ModbusDiagnosticsResponse 21
Figure 26 ModbusGetCommEventCounterRequest 22
Figure 27 ModbusGetCommEventCounterResponse 22
Figure 28 ModbusGetCommEventLogRequest 23
Figure 29 ModbusGetCommEventLogResponse 24
Figure 30 ModbusWriteMultipleCoilsRequest 25
Figure 31 ModbusWriteMultipleCoilsResponse 25
Figure 32 ModbusWriteMultipleRegistersRequest 26
Figure 33 ModbusWriteMultipleRegistersResponse 27
Figure 34 ModbusReportSlaveIDRequest 27
Figure 35 ModbusReportSlaveIDResponse 28
Figure 36 ModbusReadFileRecordRequest 29
Figure 37 ModbusReadFileSubRequest 29
Figure 38 ModbusReadFileRecordResponse 30
Figure 39 ModbusReadFileSubResponse 31
Figure 40 ModbusWriteFileRecordRequest 31
Figure 41 ModbusWriteFileSubRequest 32
Figure 42 ModbusWriteFileRecordResponse 32
Figure 43 ModbusMaskWriteRegisterRequest 33
Figure 44 ModbusMaskWriteRegisterResponse 34
Figure 45 ModbusReadWriteRegistersRequest 34
Figure 46 ModbusReadWriteRegistersResponse 35
Figure 47 ModbusReadFiFoQueueRequest 36
Figure 48 ModbusReadFiFoQueueResponse 36
Figure 49 ModbusEncapsulatedInterfaceTransportRequest 37
Figure 50 ModbusEncapsulatedInterfaceTransportResponse 38
Figure 51 ModbusReadDeviceIdentificationRequest 38
Figure 52 ModbusReadDeviceIdentificationResponse 39
Figure 53 ModbusIdentificationObject 39
Figure 54 ModbusPrivateRequest 41
Figure 55 ModbusPrivateResponse 42
Figure 56 ModbusUnconfirmedPrivateRequest 42
Figure 57 ModbusUnconfirmedPrivateResponse 43
Figure 58 ModbusExceptionResponse 44
Figure 59 ModbusIOSignalInfo 45
Figure 60 ModbusDeviceScanInfo 46
Figure 61 ModbusDeviceIdentInfo 47
Table 1 Mapping of data types 3
Table 2 Usage of Generic Data Types 3
Table 3 Usage of Broadcast in Transaction Requests 5
Table 4 Protocol-specific usage of generic data types 5
Table 5 ModbusDeviceAddress 6
Table 6 ModbusDeviceSerialAddress 7
Table 7 ModbusDeviceTcpAddress 7
Table 8 ModbusNetworkData 8
Table 9 ModbusConnectRequest data type 9
Table 10 ModbusConnectResponse data type 9
Table 11 ModbusDisconnectRequest data type 10
Table 12 ModbusDisconnectResponse data type 10
Table 13 ModbusAbortMessage data type 11
Table 14 ModbusReadCoilsRequest data type 11
Table 15 ModbusReadCoilsResponse data type 12
Table 16 ModbusReadDiscreteInputsRequest data type 13
Table 17 ModbusReadDiscreteInputsResponse data type 13
Table 18 ModbusReadHoldingRegistersRequest data type 14
Table 19 ModbusReadHoldingRegistersResponse data type 15
Table 20 ModbusReadInputRegistersRequest data type 15
Table 21 ModbusReadInputRegistersResponse data type 16
Table 22 ModbusWriteSingleCoilRequest data type 17
Table 23 ModbusWriteSingleCoilResponse data type 17
Table 24 ModbusWriteSingleRegisterRequest data type 18
Table 25 ModbusWriteSingleRegisterResponse data type 19
Table 26 ModbusReadExceptionStatusRequest data type 19
Table 27 ModbusReadExceptionStatusResponse data type 20
Table 28 ModbusDiagnosticsRequest data type 21
Table 29 ModbusDiagnosticsResponse data type 21
Table 30 ModbusGetCommEventCounterRequest data type 22
Table 31 ModbusGetCommEventCounterResponse data type 23
Table 32 ModbusGetCommEventLogRequest data type 23
Table 33 ModbusGetCommEventLogResponse data type 24
Table 34 ModbusWriteMultipleCoilsRequest data type 25
Table 35 ModbusWriteMultipleCoilsResponse data type 26
Table 36 ModbusWriteMultipleRegistersRequest data type 26
Table 37 ModbusWriteMultipleRegistersResponse 27
Table 38 ModbusReportSlaveIDRequest data type 28
Table 39 ModbusReportSlaveIDResponse 28
Table 40 ModbusReadFileRecordRequest data type 29
Table 41 ModbusReadFileSubRequest data type 30
Table 42 ModbusReadFileRecordResponse 30
Table 43 ModbusReadFileSubResponse 31
Table 44 ModbusWriteFileRecordRequest data type 31
Table 45 ModbusWriteFileSubRequest data type 32
Table 46 ModbusWriteFileRecordResponse 33
Table 47 ModbusMaskWriteRegisterRequest data type 33
Table 48 ModbusMaskWriteRegisterResponse 34
Table 49 ModbusReadWriteRegistersRequest data type 35
Table 50 ModbusReadWriteRegistersResponse 35
Table 51 ModbusReadFiFoQueueRequest data type 36
Table 52 ModbusReadFiFoQueueResponse 37
Table 53 ModbusEncapsulatedInterfaceTransportRequest data type 37
Table 54 ModbusEncapsulatedInterfaceTransportResponse 38
Table 55 ModbusReadDeviceIdentificationRequest data type 39
Table 56 ModbusReadDeviceIdentificationResponse 40
Table 57 ModbusIdentificationObject 41
Table 58 ModbusPrivateRequest data type 41
Table 59 ModbusPrivateResponse 42
Table 60 ModbusUnconfirmedPrivateRequest data type 43
Table 61 ModbusUnconfirmedPrivateResponse 43
Table 62 ModbusExceptionResponse 44
Table 63 ModbusIOSignalInfo Data Type 45
Table 64 ModbusDeviceScanInfo Data Type 46
Table 65 ModbusDeviceIdentInfo data type 47
Table 66 Protocol-Specific Mappings for Scanning Information 48
Table 67 Profile-specific mappings for identification information 49
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 5215 of GB/T 29618.
This part is drafted in accordance with the rules given in GB/T 1.1-2009.
This part uses the translation method equivalent to IEC /T R62453-52-150..2017 "Field Device Tool (FDT) Interface Specification No. 52-
Part 150. Communication Implementation of the Common Language Infrastructure IEC 61784CPF15.
The documents of our country that have a consistent correspondence with the international documents referenced in this part are as follows.
--- 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 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 Economy, Schneider Electric (China) Co., Ltd.,
Shanghai Automation Instrument Co., Ltd., Heyouxin (Shanghai) Automation System Trading Co., Ltd., Suzhou Meiming Software Co., Ltd., Rockwell
Automation (China) Co., Ltd., Chongqing Sichuan Instrument Automation Co., Ltd., Zhejiang University.
The main drafters of this section. Liu Feng, Zhang Wei, Lv Jing, Pan Dongbo, Wang Chunxi, Wang Shuo, Wang Yong, Du Jialin, Zhang Qingjun, Li Jing, Lu Yajun,
Hua Wei, Tian Yingming, Feng Dongqin, Wang Deji.
Introduction
This section is an interface specification that specifies the functionality in the client/server architecture for developers of FDT (Field Device Tools) components.
Control and data access. This section is for the development of servers and the need for seamless interoperability between multi-vendor clients, while developing standards
Interface analysis and design process.
Some other tasks that need to be performed to integrate the fieldbus into the control system. In addition to fieldbus or device specific tools, there must be
Integrate these tools into higher-level system-wide planning or engineering tools. In particular, for a wide range of heterogeneous control systems
The use in the process, typically in the process industry, is very important for the well-defined definition of all the easy-to-use engineering interfaces involved.
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 this section. The episode
The method is open to all types of fieldbus, so it can be used to integrate different kinds of devices into heterogeneous control systems.
Claim.
The position of this part in the structure of GB/T 29618 is shown in Figure 1.
Figure 1 This part of GB/T 29618
Field Device Tool (FDT) Interface Specification
Part 5115. Common Language Infrastructure
Communication implementation of IEC 61784CPF15
1 Scope
This part of GB/T 29618 provides integration of Modbus1) into a CLI-based implementation of the FDT interface specification.
Information in (GB/T 29618.42).
This section specifies the implementation of communications and other services based on IEC 62453-315.
This section does not contain the FDT specification and does not modify it.
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 15969.3-2017 Programmable controllers Part 3. Programming languages (IEC 61131-3.2013, IDT)
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 61158-5-15.2010 Industrial Communication Network Fieldbus Specification Part 5-15. Application Layer Service Definition Type 15
Elements (Industrialcommunication networks-Fieldbusspecifications-Part 5-15. Applicationlayer
servicedefinition-Type15elements)
IEC 61784-1.2014 Industrial Communication Network Profiles Part 1. Fieldbus Profiles (Industrialcommunication
networks-Profiles-Part 1. Fieldbusprofiles)
IEC 62453-315.2009 Field Device Tool (FDT) Interface Specification Part 315. Communication Protocol Integration IEC 61784
CPF15[Fielddevicetool(FDT)interfacespecification-Part 315.Communicationprofileintegration-
IEC 61784CPF15]
IEC 62453-315..2009/AMD1..2016
1) Modbus is a registered trademark of Schneider Automation in the United States. This information is for the convenience of users of this section and is not a trademark of IEC .
The name holder or any of its products constitutes an endorsement. Compliance with this section does not require the use of the Modbus trademark. Use the Modbus trademark to get the resistance
License from De Automation.
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-315
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 29618.5215-2018_English be delivered?Answer: Upon your order, we will start to translate GB/T 29618.5215-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.5215-2018_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 29618.5215-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.
|