GB/T 21099.4: Evolution and historical versions
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 21099.4-2024 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Devices and integration in enterprise systems - Function blocks(FB) for process control and electronic device description language(EDDL) - Part 4: EDD interpretation
| Valid |
GB/T 21099.4-2024
|
| GB/T 21099.4-2010 | English | 1334 |
Add to Cart
|
7 days [Need to translate]
|
Function blocks (FB) for process control -- Part 4: EDD interoperability guideline
| Valid |
GB/T 21099.4-2010
|
PDF similar to GB/T 21099.4-2024
Basic data | Standard ID | GB/T 21099.4-2024 (GB/T21099.4-2024) | | Description (Translated English) | Devices and integration in enterprise systems - Function blocks(FB) for process control and electronic device description language(EDDL) - Part 4: EDD interpretation | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | N10 | | Classification of International Standard | 25.040.40; 35.240.50 | | Word Count Estimation | 130,121 | | Date of Issue | 2024-11-28 | | Date of Implementation | 2025-06-01 | | Older Standard (superseded by this standard) | GB/T 21099.4-2010 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 21099.4-2024: Devices and integration in enterprise systems - Function blocks(FB) for process control and electronic device description language(EDDL) - Part 4: EDD interpretation
---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.
ICS 25.040.40;35.240.50
CCSN10
National Standard of the People's Republic of China
Replaces GB/T 21099.4-2010
Equipment and integrated process control in enterprise systems
Using function blocks (FB) and electronic device description language
(EDDL) Part 4.EDD Interoperability
Part 4.EDD interpretation
Published on 2024-11-28 Implemented on 2025-06-01
State Administration for Market Regulation
The National Standardization Administration issued
Table of Contents
Preface IX
Introduction Ⅺ
1 Scope 1
2 Normative references 1
3 Terms and Definitions, Acronyms and Abbreviations and Conventions 2
3.1 General Terms and Definitions 2
3.2 Terms and definitions related to modular equipment 2
3.3 Abbreviations and abbreviations 3
3.4 Convention 3
4 EDDL User Interface Description 3
4.1 Overview 3
4.2 Menu conventions for handheld device applications 4
4.3 Menu conventions based on PC applications 4
4.3.1 Overview 4
4.3.2 Online Root Menu 5
4.3.3 Offline Root Menu 5
4.3.4 EDD menu structure example 6
4.3.5 User Interface 10
4.4 Label association for indirect variable references 13
4.4.1 Overview 13
4.4.2 Simple variable reference 14
4.4.3 Complex variable references 14
4.5 Help in connecting 16
4.5.1 Overview 16
4.5.2 Simple variable reference 16
4.5.3 Complex variable references 17
4.6 Containers and container items 18
4.6.1 Overview 18
4.6.2 Allowed and default styles 18
4.6.3 Container 20
4.6.4 Container Item 21
4.7 Layout Rules 27
4.7.1 Overview 27
4.7.2 Controlling layout with the LAYOUT_TYPE attribute 28
4.7.3 Layout of WIDTH and HEIGHT 31
4.7.4 COLUMNBREAK and ROWBREAK layout rules 34
4.7.5 Layout Example 40
4.7.6 Traditional User Interface 54
4.8 Graphic elements 60
5 EDDL Data Description 63
5.1 Device Data Stored by EDDL Applications 63
5.1.1 Overview 63
5.1.2 FILE 63
5.1.3 LIST 65
5.2 Exposing Data Items Outside of an EDD Application 72
5.3 Initializing the EDD Instance 72
5.3.1 Overview 72
5.3.2 Initialization support 72
5.3.3 TEMPLATE 72
5.4 Device Model Mapping 73
5.4.1 BLOCK_A 73
5.4.2 BLOCK_B 73
6 EDDLMETHOD Programming and Use of Built-in Functions 74
6.1 Method environment 74
6.1.1 Overview 74
6.1.2 Security 74
6.1.3 Equipment data 74
6.1.4 Method Type and Parameters 74
6.1.5 Termination Processing 75
6.2 Implementation requirements 75
6.3 BuiltinMenuDisplay 76
6.4 Division by Zero and Indeterminate Floating-Point Values 78
6.4.1 Integer and Unsigned Integer Values 78
6.4.2 Floating-point values 78
7 Modular Equipment 79
7.1 Overview 79
7.2 EDD Identification 79
7.3 Instance Object Model 79
7.4 Offline Configuration 80
7.5 Online Configuration 80
7.6 Simple Modular Device Example 80
7.6.1 Overview 80
7.6.2 Example of a separate EDD file with direct EDD references 81
7.6.3 Example of a separate EDD file for classified EDD references and interfaces 82
7.6.4 An Example of an EDD File 84
7.6.5 Combination of single and separate modular equipment examples 86
7.7 Uploading and downloading modular devices 86
7.8 Diagnosis 86
7.9 Reading Modular Device Topology 87
7.9.1 SCAN 87
7.9.2 Detection module type 88
7.10 Configuration Check 89
8 Session Management 90
8.1 Overview 90
8.2 Data Management 90
8.2.1 Overview 90
8.2.2 Online Session Cache 91
8.2.3 Offline Session Cache 91
8.2.4 Dialog Box and Window Cache 92
8.2.5 Cache METHODs 93
8.3 UI Aspects of Editing Sessions 95
8.4 User Roles 96
9 Offline and Online Configuration 96
9.1 Overview 96
9.2 Offline Datasets 97
9.3 Offline Configuration 97
9.4 Online Datasets 97
9.5 Online Configuration 97
9.6 Upload and Download 97
9.6.1 Overview 97
9.6.2 Error Recovery 98
9.6.3 Upload Process 99
9.6.4 Download Program 100
10 EDDL Communication Description 102
10.1 General requirements 102
10.2 Parsing data received from the device 102
10.3 Parsing Complex Data Items 103
10.4 FoundationFieldbus 103
10.5 ISA100_Wireless Communication Model 106
Appendix A (Normative) Device Simulation 109
Appendix B (Informative) Predefined Identifiers 110
Appendix C (Informative) Description of EDDL Profile 114
Appendix D (Normative) Upload/Download Cache Model 115
References 117
Figure 1 EDD example of root menu 6
Figure 2 Example of EDD application for diagnosis11
Figure 3 EDD application example of process variables11
Figure 4 EDD application example of primary variable 12
Figure 5 Example of EDD application of process-related equipment characteristics 12
Figure 6 EDD application example of device characteristics 13
Figure 7 Example of EDD application for maintenance characteristics 13
Figure 8 Usage of COLLECTIONMEMBERS in STYLEGROUPMENU 21
Figure 9 shows a single bit 23 of BIT_ENUMERATED
Figure 10 shows multiple bits of BIT_ENUMERATED 23
Figure 11 EDD application example 24 of a variable of type BIT_ENUMERATED
Figure 12 EDD example of a "write only" variable (HANDLINGWRITE) 24
Figure 13 Basic layout elements 27
Figure 14 Example of a layout with equal column widths 28
Figure 15 Layout example of optimized column width 29
Figure 16 Optimizing the cell body layout with column width (label on the left) 29
Figure 17 Optimizing the cell body layout with column width (label at the top) 30
Figure 18 EDD source code for VARIABLEs laid out across columns 33
Figure 19 Variables layout across multiple columns 33
Figure 20 Example of EDD source code highlighting element layout 34
Figure 21 Layout of highlighted elements 35
Figure 22 EDD source code example of partially filled row layout 35
Figure 23 Layout of partially filled rows 36
Figure 24 EDD source code example of partially filled row layout 36
Figure 25 Layout of partially filled rows 37
Figure 26 EDD source code example of very large element layout 37
Figure 27 Extra large elements in equal column width layout 37
Figure 28.Oversized elements in optimized column width layout 38
Figure 29 EDD source code example for column layout in stacked groups 38
Figure 30 Layout of columns in a stacked group 39
Figure 31 EDD source code with GRAPHs column layout for the stacked group example 39
Figure 32 Column layout of GRAPHs stacking group 40
Figure 33 EDD example of overview menu 40
Figure 34 Overview window EDD application example 41
Figure 35 EDD source code for menu items spanning a column layout 41
Figure 36 Layout example of menu items spanning one column 42
Figure 37 EDD example using COLUMNBREAK42
Figure 38 Overview window EDD application example 43
Figure 39 Overview window EDD application example 43
Figure 40 Overview window EDD application example 44
Figure 41 EDD source code for small size embedded image layout 44
Figure 42 Example of layout of small embedded images 45
Figure 43 EDD source code for GROUP multi-column layout 45
Figure 44 Example of GROUP multi-column layout 46
Figure 45.Example of an embedded graph and chart EDD 47
Figure 46 Embedded Graphics EDD Application Example 47
Figure 47 Full-width graph and chart EDD application example 48
Figure 48 Example of EDD application of full-width images in equal column width layout
Figure 49 Example of EDD application of full-width images in optimized column width layout 49
Figure 50 EDD example of nested containers 50
Figure 51 EDD application example of nested containers 50
Figure 52 EDD example 51 of EDIT_DISPLAYS
Figure 53 EDD application example 52 of EDIT_DISPLAYS
Figure 54 Image EDD example 52
Figure 55 Image EDD application example 53
Figure 56 EDD example of a large embedded image 53
Figure 57 Example of layout of large embedded images 54
Figure 58 Example of EDD of VALIDITY in online session 55
Figure 59 Example of EDD application for restricted area measurement 60
Figure 60 EDD example for restricted area measurement 61
Figure 61 Example of file declaration 64
Figure 62 Example of valve characteristics comparison 65
Figure 63 A more complex file declaration example 66
Figure 64 Example of reviewing stored radar signals 67
Figure 65 EDD example of inserting, replacing or comparing radar signals 69
Figure 66 BLOCK_A Example 73
Figure 67 Wizard Example 77
Figure 68 Different relationships between modules 80
Figure 69 Components and possible configurations of modular equipment 80
Figure 70 Example of a separate EDD file referenced directly by EDD 81
Figure 71 EDD example for module 182
Figure 72 EDD example for module 282
Figure 73 EDD example for modular equipment 83
Figure 74 EDD example for module 184
Figure 75 EDD example for module 2 84
Figure 76 EDD example for module 2 85
Figure 77 Upload/download sequence for modular devices 86
Figure 78 SCANMETHOD example 88
Figure 79 DETECTMETHOD Example 89
Figure 80 CHECK_CONFIGURATIONMETHOD example 89
Figure 81 Data cache of online session 91
Figure 82 Data cache for offline sessions 92
Figure 83 Using a shared edit buffer sub-dialog box or window 92
Figure 84 Using a separate edit buffer sub-dialog or window 93
Figure 85 Data caching of nested methods 93
Figure 86 Data caching for calling METHOD in a dialog box or window 94
Figure 87 Data cache of METHOD using the edit cache call dialog box 94
Figure 88 Data cache of the METHOD that calls the dialog box 94
Figure 89 Data flow downloaded to the device 98
Figure 90 Data flow uploaded from the device 98
Figure 91 Example of a device with two unique BLOCK_A definitions 104
Figure 92 Device example EDD 104 with two unique BLOCK_A definitions
Figure 93 BLOCK_A example of PARAMETER_LISTS 105
Figure 94 EDD example of BLOCK_A of PARAMETER_LISTS 105
Figure 95 ISA100_Wireless device object representation example 106
Figure 96 ISA100_Wireless device EDD example with two unique BLOCK_A definitions 107
Figure 97 BLOCK_A example with PARAMETER_LISTS 107
Figure 98 EDD example of BLOCK_A of PARAMETER_LISTS 108
Figure D.1 Upload Cache Model 115
Figure D.2 Download Cache Model 116
Table 1 List of defined root menu identifiers for handheld devices 4
Table 2 Identifiers for PC-based devices Root menu identifier list 4
Table 3 Alternative options for online root menu 5
Table 4 Fallback alternatives for offline root menu 6
Table 5 Summary of Label rules for simple variable references 14
Table 6 Summary of Label rules for simple variable references 14
Table 7 Summary of Prefix rules for complex variable references 15
Table 8 Summary of Prefix rules for complex variable references 15
Table 9 Summary of Body rules for complex variable references 15
Table 10 Summary of Body rules for complex variable references 16
Table 11 Summary of Suffix rules for complex variable references 16
Table 12 Summary of Suffix rules for complex variable references 16
Table 13 Summary of help rules for simple variable references 17
Table 14 Summary of help rules for simple variable references 17
Table 15 Summary of help prefix rules for complex variable references 17
Table 16 Summary of help prefix rules for complex variable references 17
Table 17 Summary of help suffix rules for complex variable references 18
Table 18 Summary of help suffix rules for complex variable references 18
Table 19 Allowed container items and default STYLEs 19
Table 20 Uninitialized state of VARIABLEs on the user interface 22
Table 21 Operation steps for "write-only" variables in online session 25
Table 22 Layout content description 27
Table 23 Minimum and maximum widths of input fields that span a column 30
Table 24 Width and height range and applicability 31
Table 25 VALIDITY example 1 in online session 56
Table 26 VALIDITY Example 2 in Online Session 57
Table 27 VALIDITY Example 3 in Online Session 58
Table 28 VALIDITY example 4 in online session 59
Table 29 Floating point result example 78
Table 30 COMPONENT_PATH usage 79
Table 31 Diagnostic categories 87
Table 32 Session Management Terms 90
Table 33 Terminology used in data management 90
Table 34 Method Cache Control Builtins 95
Table 35 Defined upload menu identifier list 99
Table 36 Defined Download Menu Identifier List 100
Table B.1 ARRAY predefined identifiers 110
Table B.2 COLLECTION predefined identifiers 110
Table B.3 COMMAND predefined identifiers 110
Table B.4 IMAGE predefined identifiers 111
Table B.5 MENU predefined identifiers 111
Table B.6 METHOD predefined identifiers 112
Table B.7 VARIABLE predefined identifiers 112
Foreword
This document is in accordance with the provisions of GB/T 1.1-2020 "Guidelines for standardization work Part 1.Structure and drafting rules for standardization documents"
Drafting.
This document is Part 4 of GB/T (Z) 21099.GB/T (Z) 21099 has published the following parts.
--- Function blocks for process control Part 1.General aspects of the system;
--- Function Block (FB) and Electronic Device Description Language (EDDL) for equipment and integrated process control in enterprise systems Part 2
Points. FB concept specification;
--- Function Block (FB) and Electronic Device Description Language (EDDL) for equipment and integrated process control in enterprise systems Part 3
Points. EDDL syntax and semantics;
--- Function Block (FB) and Electronic Device Description Language (EDDL) for equipment and integrated process control in enterprise systems Part 4
Points. EDD interoperability;
--- Function Block (FB) and Electronic Device Description Language (EDDL) for equipment and integrated process control in enterprise systems Part 5
Points. EDDL built-in library;
--- Function blocks (FB) and electronic device description language (EDDL) for process control Part 6.Meeting the requirements of field device engineering tools
The need to integrate fieldbus devices.
This document replaces GB/T 21099.4-2010 "Function blocks (FB) for process control Part 4.EDD interoperability guide" and
Compared with GB/T 21099.4-2010, in addition to structural adjustments and editorial changes, the main technical changes are as follows.
--- Added the terms "container", "container item", "device developer", "handheld device", "channel", "component", "interface", "modal window", "module
Chemical equipment” (see 3.1, 3.2);
--- Deleted the terms "EDD application" and "end user" (see 3.1 of the.2010 edition);
--- Added abbreviations and abbreviations "CS", "FDI", "GPE", "HART", "ISA100", "PB", "PI", "PIPROFILEPA", "PN"
(see 3.3);
--- Deleted the abbreviations and abbreviations "HCF", "OPC" and "PNO" (see 3.2 of the.2010 edition);
--- Added Table 1 "List of defined root menu identifiers for handheld devices" (see 4.2);
--- 4.3 has been significantly revised, including re-arrangement, modification, deletion or addition of content, addition of tables, etc. (see 4.3,.2010 edition
4.3);
---4.4 "Conventions for all menus" was changed to 4.4 "Label associations for indirect variable references" (see 4.4, 4.4 of the.2010 edition);
--- Added 4.5 "Help Association" (see 4.5);
---4.5 "User Interface Extensions" was changed to 4.6 "Containers and Contained Items", and the clauses under it were significantly modified, including rewriting
Arrange, modify, delete or add content, add tables, etc. (see 4.6, 4.5 of the.2010 edition);
---4.6 "Layout Rules" was changed to 4.7 "Layout Rules", and the clauses under it were significantly modified, including re-arrangement, modification and deletion.
Reduce or increase content, add tables and figures, etc. (see 4.7, 4.6 of the.2010 edition);
--- Deleted 4.7 "Default Menu Style" (see 4.7 of the.2010 edition);
--- 5.1 “Overview” was changed to 4.8 “Graphical Elements”, and the content was modified (see 4.8, 5.1 of the.2010 edition);
--- Deleted 5.2 "Graphs and Charts", 5.3 "MAGE" and 5.4 "GRID" and related content (see 5.2, 5.3,.2010 edition
5.4);
--- Chapter 6 "EDDL Data Description" was changed to Chapter 5 "Description of EDDL Data", 6.1 was deleted, and 5.2~5.4 were added (see
Chapter 5, Chapter 6 in the.2010 edition);
--- Added Chapter 6 "EDDLMETHOD Programming and Use of Built-in Functions" (see Chapter 6);
--- Chapter 7 "EDDL built-in functions" was changed to "modular devices" (see Chapter 7, Chapter 7 of the.2010 edition);
---Added "Session Management" (see Chapter 8);
--- Added "Offline and Online Configuration" (see Chapter 9);
--- Added "EDDL Communication Description" (see Chapter 10);
--- Changed Appendix A (see Appendix A, Appendix A of the.2010 edition);
--- Added Appendix D (see Appendix D).
This document is equivalent to IEC 61804-4.2020 "Function blocks (FBs) and electronic devices for equipment and integrated process control in enterprise systems"
Device Description Language (EDDL) Part 4.EDD Interoperability.
Please note that some of the contents of this document may involve patents. The issuing organization of this document does not assume the responsibility for identifying patents.
This document was proposed by the China Machinery Industry Federation.
This document is under the jurisdiction of the National Industrial Process Measurement, Control and Automation Standardization Technical Committee (SAC/TC124).
This document was drafted by. Hangzhou Youwen Automation System Co., Ltd., Xiamen Anton Electronics Co., Ltd., Yangzhou Vocational University, Zhejiang Zheng
Taizhong Automatic Control Engineering Co., Ltd., Dandong Tongbo Electric (Group) Co., Ltd., Jiangsu Jack Instrument Co., Ltd., Hangzhou Zhenhua Instrument Co., Ltd.
Company, Xi'an Dingzheng Measurement and Control Technology Co., Ltd., Chongqing Chuanyi Software Co., Ltd., Guoneng Zhishen Control Technology Co., Ltd., Jiangsu Huaxia Instrument
Co., Ltd., Shanghai Mingkong Sensing Technology Co., Ltd., Jiangsu Shuangmu Measurement and Control Technology Co., Ltd., Jiangyuan (Tianchang) Technology Co., Ltd., Chongqing
Qingchuan Instrument Automation Co., Ltd. Flow Instrument Branch, Beijing Jingyi Group Co., Ltd., Nanjing U-Best Electrical Technology Co., Ltd.
Co., Ltd., Anhui Tiankang (Group) Co., Ltd., Chongqing Wei'an Instrument Manufacturing Co., Ltd., Endress+Hauser (China) Automation Co., Ltd.
Company, Chongqing Shulong Information Technology Co., Ltd., Yunnan Normal University, Shaanxi Institute of Metrology, Chongqing Chuanyi Automation Co., Ltd.
Co., Ltd., China Academy of Railway Sciences Group Co., Ltd. Electronic Computing Technology Research Institute, Shanghai Lodinson Industrial Automation Equipment Co., Ltd.
Company, Zhejiang Zhongkong Automation Instrument Co., Ltd., Henan Baoshian Electronic Technology Co., Ltd., Qingdao Automation Instrument Co., Ltd., Anhui
Automation Instrument Co., Ltd., Xi'an Dongfeng Electromechanical Co., Ltd., Taicang Boiler Automation Instrument Factory Co., Ltd., Hangzhou Electronic Science and Technology University
University of Science and Technology, Shenzhen Jinkaibo Automation Testing Co., Ltd., Southwest University, and Chongqing Zhongzhilian Instrument Co., Ltd.
The main drafters of this document are. Wang Wenhai, Xiao Guozhuan, Chen Jiusong, Zhang Chuangxun, Zhang Yiding, Bao Qiao, Zhang Bailin, Qu Kebing, Tian Yingming, Feng Jian,
Xu Bin, Gao Fan, Huang Dong, Yang Shaohua, Chen Qingrong, Yuan Ming, Wang Jianchao, Zou Mingwei, Wang Li, Wang Lin, Mao Wenzhang, Tang Tian, Zhu Siwei, Guo Wei,
Gan Jianhou, Ding Ling, Xu Jian, Wang Fang, Du Chengxin, Li Junyi, Xie Yifei, Wei Jiabao, Qin Zeguang, Ke Youxi, Zhan Hang, Li Wei, Kong Yaguang, Luo Yixing,
Zhang Geng, Yang Yang, Liu Feng, Zhang Xinguo, Zhou Xuelian, Zhang Yu, He Qiang, Wu Hongwei, Bu Yan, Zhou Xiang, Che Lei, Gao Jingmei, Song Boyu, Hu Wenxiu,
Gan Haoting, Gu Penny, Su Zelin, Liang Chen.
The previous versions of this document and the documents it replaces are as follows.
---First published in.2010 as GB/T 21099.4-2010;
---This is the first revision.
Introduction
GB/T (Z) 21099 consists of the following 6 parts.
--- Part 1.General introduction to system aspects. The purpose is to provide suppliers with general guidelines and specifications to ensure that users can select compatible equipment.
compatibility, interoperability, interoperability and interchangeability.
--- Part 2.FB concept specification. The purpose is to provide conceptual function block specifications, including. device model of device components;
conceptual specification of the FB for measurement, execution, and processing, including general rules for supporting essential features of control to avoid impeding innovation
New details and specialized details for different industrial fields; Electronic Device Description (EDD) technology, using engineering life cycle tools
Tools to integrate real product details.
--- Part 3.EDDL syntax and semantics. The purpose is to specify the Electronic Device Description Language (EDDL) technology, which allows the use of industrial
The integration of actual product details is accomplished through tools in the process life cycle.
--- Part 4.EDD interoperability. The purpose is to ensure that field device developers use the EDDL structure consistently. It supplements
EDDL specification to promote interoperability and portability between EDDL applications
Plant nature.
--- Part 5.EDDL built-in library. The purpose is to define the EDDL built-in library and provide various fieldbus specifications.
--- Part 6.Meeting the needs of field device engineering tools for integrated fieldbus devices. The purpose is to provide equipment and system manufacturers with
It provides guidance for manufacturers to use EDDL technology to meet user needs, and also provides guidance for system integrators and instrument maintenance personnel.
Provides guidance to help end users integrate systems and incorporate device management into their workflow using EDDL technology.
This document contains.
---Overview of using EDDL;
--- Provide EDDL examples and demonstrate how to use them;
---Describe how to implement the use case;
---Explain the correct application of EDD for each example.
This document is not a guide to EDDL, nor is it intended to replace the EDDL specification.
This document provides instructions for EDD applications. These instructions describe how to perform operations when the technology used in the host implementation is not specified.
For example, the FILE structure describes the data stored by the proxy EDD application on behalf of the EDD. The FILE construct does not specify data.
The EDD application can use a database, a plain file, or any other format of its choice.
EDDL functions are subject to the profile of each communication technology. The descriptions in this document refer to these functions in a general sense and are not intended to be exhaustive.
All communication technologies will support all the functions described. In order to understand the features supported by each communication technology, reference is made to GB/T 21099.3
The line definition in.
Equipment and integrated process control in enterprise systems
Using function blocks (FB) and electronic device description language
(EDDL) Part 4.EDD Interoperability
1 Scope
This document specifies the EDD application and EDD interpretation of EDD documents to support EDD interoperability.
The EDDL specification is supplemented to facilitate
Improve interoperability and portability between EDDL applications.
2 Normative references
The contents of the following documents constitute the essential clauses of this document through normative references in this document.
For referenced documents without a date, only the version corresponding to that date applies to this document; for referenced documents without a date, the latest version (including all amendments) applies to
This document.
IEC 61784-1 Industrial networks-Profiles-Part 1.Fieldbus profiles
IEC 61784-2 Industrial Network Profile Part 2.Additional Real-time Fieldbus Profile Based on ISO /IEC /IEEE8802-3
8802-3)
Note. GB/T 33537.3-2017 Industrial Communication Network Fieldbus Specification Type 23.CC-Link IE Specification Part 3.CC-Link IE Communication
Industry regulations (IEC 61784-2.2014, MOD)
IEC 61804-3 Function blocks (FB) and electronic device description language (EDDL) for equipment and integrated process control in enterprise systems
tics]
Note. GB/T 21099.3-2024 Function blocks (FB) and electronic device description language (EDDL) for equipment and integrated process control in enterprise systems Part 3
Part. EDDL syntax and semantics (IEC 61804-3.2020, IDT)
IEC 61804-5 Function Block (FB) and Electronic Device Description Language (EDDL) for equipment and integrated process control in enterprise systems Part
Note. GB/T 21099.5-2024 Function blocks (FB) and electronic device description language (EDDL) for equipment and integrated process control in enterprise systems
Part 5.EDDL built-in library (IEC 61804-5.2020, IDT)
FDIPackage]
Note. GB/T 41771.4-2022 Field device integration Part 4.Package (IEC 62769-4.2021, IDT)
Note. GB/T 41771.7-2023 Field device integration Part 7.Communication equipment (IEC 62769-7.2023, IDT)
|