HOME   Cart(2)   Quotation   About-Us Policy PDFs Standard-List
www.ChineseStandard.net Database: 189759 (19 Oct 2025)

GB/T 29618.315-2013 English PDF

US$974.00 · In stock
Delivery: <= 3 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 29618.315-2013: Field device tool (FDT) interface specification -- Part 315: Communication profile integration -- MODBUS
Status: Valid
Standard IDContents [version]USDSTEP2[PDF] delivered inStandard Title (Description)StatusPDF
GB/T 29618.315-2013English974 Add to Cart 3 days [Need to translate] Field device tool (FDT) interface specification -- Part 315: Communication profile integration -- MODBUS Valid GB/T 29618.315-2013

PDF similar to GB/T 29618.315-2013


Standard similar to GB/T 29618.315-2013

GB/T 33008.1   GB/T 33009.1   GB/T 33009.2   GB/T 29618.306   GB/T 29618.301   GB/T 29618.302   

Basic data

Standard ID GB/T 29618.315-2013 (GB/T29618.315-2013)
Description (Translated English) Field device tool (FDT) interface specification -- Part 315: Communication profile integration -- MODBUS
Sector / Industry National Standard (Recommended)
Classification of Chinese Standard N10
Classification of International Standard 25.040
Word Count Estimation 49,456
Quoted Standard GB/T 15969.3; GB/T 29618.1; GB/T 29618.2; IEC 61158-5-15; IEC 61158-6-15; IEC 61784-1; IEC 61784-2; RFC 791
Adopted Standard IEC 62453-315-2009, IDT
Regulation (derived from) National Standards Bulletin 2013 No. 10
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
Summary This standard specifies: the Modbus TCP and Modbus Serial Line protocol is integrated in the system based on FDT information. Family communication line regulation 15 (commonly referred to as Modbus) based on IEC 61158-5-15 and IEC 61158-6-15 defines the c

GB/T 29618.315-2013: Field device tool (FDT) interface specification -- Part 315: Communication profile integration -- MODBUS


---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 315.. Communication profile integration-MODBUS ICS 25.040 N10 National Standards of People's Republic of China Field device tool (FDT) interface specification Part 315. Integrated communication profile MODBUS Fieldbus specifications Fielddevicetool (FDT) interfacespecification- Part 315. Communicationprofileintegration-MODBUS (IEC 62453-315.2009, IDT) Issued on. 2013-07-19 2013-12-15 implementation Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China Standardization Administration of China released

Table of Contents

Introduction Ⅴ Introduction Ⅵ 1 Scope 1 2 Normative references 1 3 Terms, definitions, symbols, abbreviations and conventions 1 3.1 Terms and definitions 3.2 Abbreviations 2 3.3 Conventions 2 4 bus Category 2 5 Examples of data access and equipment 2 Process Object 5.1 DTM channel provides 2 5.2 DTM provides access to data services and devices Examples 2 6 3 protocol-specific behavior 6.1 Overview 3 6.2 Radio 3 6.3 Modbus request without confirmation private 5 7 common type of protocol-specific data usage of 6 8 protocol-specific generic data type 7 8.1 Overview 7 Addressing 7 8.2 9 8 types of network management data 10 communication data type 8 10.1 Overview 8 Connection Management 10.2 Data Types 9 10.3 Transaction Service specific data type 9 11-channel parameter data type 32 12 device identification 34 12.1 General Equipment type identification data type 34 12.2 topology scan data types 35 12.3 Scan type identification data 37 Device type identifies the type of data provided 12.4 DTM 39 12.5 protocol-specific device identification object to the FDT data type mapping 40 References 41 FIG. 1 GB/T 29618 series Part 315 Ⅵ Figure 2 ModbusSerialLine communication DTM broadcast sequence 4 Figure 3 ModbusTCP communication DTM broadcast sequence 4 4 no Modbus communication DTM broadcast sequence 5 Figure 5 ModbusSerialLine without confirmation request to the communication DTM 5 Figure 6 ModbusTCP without confirmation request to the communication DTM 6 Figure 7 without confirmation request no Modbus communication DTM 6 8 items addressed 10 Table 1 protocol identifier 2 Table 2 broadcast mode of addressing information 3 Table 3 3 Broadcasting request Table 4 General FDT protocol-specific data type usage 7 Table 5 simple data types addressing information 7 Table 6 structured data type address information 7 Table 7 Structure of network management data types 8 Table 8 Simple common communication data type 9 Table 9 Structure of the connection management data type 9 Table 10 ReadCoilsReq simple data types 10 Table 11 ReadCoilsReq structured data types 10 Table 12 ReadCoilsRsp simple data types 11 Table 13 ReadCoilsRsp structured data types 11 Table 14 ReadDiscreteInputsReq simple data types 11 Table 15 ReadDiscreteInputsReq structured data types 12 Table 16 ReadDiscreteInputsRsp simple data types 12 Table 17 ReadDiscreteInputsRsp structured data types 12 Table 18 ReadHoldingRegistersReq simple data types 12 Table 19 ReadHoldingRegistersReq structured data types 13 Table 20 ReadHoldingRegistersRsp simple data types 13 Table 21 ReadHoldingRegistersRsp structured data types 13 Table 22 ReadInputRegistersReq simple data types 13 Table 23 ReadInputRegistersReq structured data types 13 Table 24 ReadInputRegistersRsp simple data types 14 Table 25 ReadInputRegistersRsp structured data types 14 Table 26 WriteSingleCoilReq simple data types 14 Table 27 WriteSingleCoilReq structured data types 14 Table 28 WriteSingleCoilRsp structured data types 15 Table 29 WriteSingleRegisterReq simple data types 15 Table 30 WriteSingleRegisterReq structured data types 15 Table 31 WriteSingleRegisterRsp structured data types 15 Table 32 ReadExceptionStatusReq structured data types 16 Table 33 ReadExceptionStatusRsp simple data types 16 Table 34 ReadExceptionStatusRsp structured data types 16 Table 35 simple diagnostic data types 16 Table 36 DiagnosticsReq structured data types 17 Table 37 DiagnosticsRsp structured data types 17 Table 38 GetCommEventCounterReq structured data types 17 Table 39 GetCommEventCounterRsp simple data types 18 Table 40 GetCommEventCounterRsp structured data types 18 Table 41 GetCommEventLogReq structured data types 18 Table 42 GetCommEventLogRsp simple data types 18 Table 43 GetCommEventLogRsp structured data types 19 Table 44 WriteMultipleCoilsReq simple data types 19 Table 45 WriteMultipleCoilsReq structured data types 20 Table 46 WriteMultipleCoilsRsp structured data types 20 Table 47 WriteMultipleRegistersReq simple data types 20 Table 48 WriteMultipleCoilsReq structured data types 20 Table 49 WriteMultipleCoilsRsp structured data types 21 Table 50 ReportSlaveIDReq structured data types 21 Table 51 ReportSlaveIDRsp simple data types 21 Table 52 ReportSlaveIDRsp structured data types 21 Table 53 ReadFileSubRequest simple data types 22 Table 54 ReadFileSubRequest structured data types 22 Table 55 ReadFileRecordReq structured data types 22 Table 56 ReadFileSubResponse simple data types 22 Table 57 ReadFileSubResponse structured data types 23 Table 58 ReadFileRecordRsp structured data types 23 Table 59 WriteFileSubRequest simple data types 23 Table 60 WriteFileSubRequest structured data types 23 Table 61 WriteFileRecordReq structured data types 24 Table 62 ReadFileRecordRsp structured data types 24 Table 63 MaskWriteRegisterReq simple data types 24 Table 64 MaskWriteRegisterReq structured data types 24 Table 65 MaskWriteRegisterRsp structured data types 25 Table 66 ReadWriteRegistersReq simple data types 25 Table 67 ReadWriteRegistersReq structured data types 25 Table 68 ReadWriteRegistersRsp simple data types 25 Table 69 ReadWriteRegistersRsp structured data types 26 Table 70 ReadFifoQueueReq simple data types 26 Table 71 ReadFifoQueueReq structured data types 26 Table 72 ReadFifoQueueRsp simple data types 26 Table 73 ReadFifoQueueRsp structured data types 26 Table 74 EncapsulatedInterfaceTransportReq simple data types 27 Table 75 EncapsulatedInterfaceTransportReq structured data types 27 Table 76 EncapsulatedInterfaceTransportRsp simple data types 27 Table 77 EncapsulatedInterfaceTransportRsp structured data types 27 Table 78 ReadDeviceIdentificationReq simple data types 28 Table 79 ReadDeviceIdentificationReq structured data types 28 Table 80 IdentificationObject simple data types 28 Table 81 IdentificationObject structured data types 28 Table 82 Simple reading device identification response data type 29 Table 83 ReadDeviceIdentificationRsp structured data types 29 Table 84 PrivateModbusReq simple data types 30 Table 85 PrivateModbusReq structured data types 30 Table 86 PrivateModbusRsp simple data types 30 Table 87 PrivateModbusRsp structured data types 30 Table 88 UnconfirmedPrivateModbusReq simple data types 30 Table 89 UnconfirmedPrivateModbusReq structured data types 31 Table 90 UnconfirmedPrivateModbusRsp structured data types 31 Table 91 ModbusExceptionRsp simple data types 31 Table 92 ModbusExceptionRsp structured data types 32 Table 93 Simple channel parameter data type 32 Control functions and data access. This section is the result of the development of standard interfaces in the process of analysis and design. These multiple standard interfaces easy Manufacturers develop seamless server and client interoperability. Field devices integrated into the control system, you need to perform some other tasks. In addition to the specific fieldbus-specific tools and equipment Tools, the need to integrate these tools into a higher level of system-wide planning or engineering tool. In particular, for the large-scale heterogeneous Control system (typically in the process industry) using well-defined and easy to use interface to the relevant project is very important. Device-specific software components created in accordance with this section called Device Type Manager (DTM). FDT it through this part of the definition of Service, all device-specific data, functions and business rules are integrated into the system. FDT/DTM method for all types of fieldbus is open, allowing all kinds of devices into heterogeneous systems. Figure 1 shows the GB/T 29618.315 position in GB/T 29618 series of standards structure. FIG. 1 GB/T 29618 series - Part 315 Field device tool (FDT) interface specification Part 315. Integrated communication profile MODBUS Fieldbus specifications

1 Scope

Communication profile family 15 (commonly referred to as Modbus) based on IEC 61158-5-15 and IEC 61158-6-15 defines the communication profile. base The line regulation CP15/1 (ModbusTCP) are defined in IEC 61784-1. Additional communication profiles (ModbusSerialLine) defined In the literature [2]. This section GB/T 29618 provides the ModbusTCP and ModbusSerialLine protocol integrated in FDT-based systems Information. Note. This section only defines FDT data types mapped to Modbus parameters. For the protocol-related parameters used in FDT data type definition Restrictions, such as allowing the value and limitations of the array, refer to IEC 61158-5-15 and Modbus application protocol specification.

2 Normative references

The following documents for the application of this document is essential. For dated references, only the dated version suitable for use herein Member. For undated references, the latest edition (including any amendments) applies to this document. GB/T 15969.3 Programmable controllers - Part 3. Programming languages \u200b\u200b(GB/T 15969.3-2005, IEC 61131-3.2002, IDT) GB/T 29618.1 Field device tool (FDT) interface specification - Part 1. Overview and guidance (GB/T 29618.1-2013, IEC 62453-1.2009, IDT) GB/T 29618.2 Field device tool (FDT) interface specification - Part 2. Concepts and detailed description (GB/T 29618.2- 2013, IEC 62453-2.2009, IDT) IEC 61158-5-15 Industrial communication networks - Fieldbus specifications - Part 5-15. Application layer service definition - Type 15 yuan Su (Industrialcommunicationnetworks-Fieldbusspecifications-Part 5-15. Applicationlayerservice definition-Type15elements) IEC 61158-6-15 Industrial communication networks - Fieldbus specifications - Part 6-20. Application layer protocol describes the type of 15 yuan Su (Industrialcommunicationnetworks-Fieldbusspecifications-Part 6-15. Applicationlayerprotocol specification-Type15elements) IEC 61784-1 Industrial communication networks profiles - Part 1. Fieldbus profile (Industrialcommunicationnet- works-Profiles-Part 1. Fieldbusprofiles) IEC 61784-2 Industrial communication networks profiles - Part 2. Based on ISO /IEC 8802-3 real-time network additional fieldbus Line profiles (Industrialcommunicationnetworks-Profiles-Part 2. Additionalfieldbusprofilesforreal- timenetworksbasedonISO /IEC 8802-3) 3 Terms, definitions, symbols, abbreviations and conventions 3.1 Terms and Definitions Terms and definitions GB/T 29618.1 and GB/T 29618.2 defined apply to this document.

Tips & Frequently Asked Questions:

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

Answer: Upon your order, we will start to translate GB/T 29618.315-2013_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.315-2013_English with my colleagues?

Answer: Yes. The purchased PDF of GB/T 29618.315-2013_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 [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.