|
US$2344.00 · In stock
Delivery: <= 11 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 19769.1-2022: Function blocks - Part 1: Architecture
Status: Valid GB/T 19769.1: Evolution and historical versions
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 19769.1-2022 | English | 2344 |
Add to Cart
|
11 days [Need to translate]
|
Function blocks - Part 1: Architecture
| Valid |
GB/T 19769.1-2022
|
| GB/T 19769.1-2015 | English | RFQ |
ASK
|
9 days [Need to translate]
|
Function blocks -- Part 1: Architecture
| Obsolete |
GB/T 19769.1-2015
|
| GB/T 19769.1-2005 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Function block for industrial-process measurement and control system -- Part 1: Architecture
| Obsolete |
GB/T 19769.1-2005
|
PDF similar to GB/T 19769.1-2022
Basic data | Standard ID | GB/T 19769.1-2022 (GB/T19769.1-2022) | | Description (Translated English) | Function blocks - Part 1: Architecture | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | N31 | | Word Count Estimation | 130,169 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 19769.1-2022: Function blocks - Part 1: Architecture---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.
Function blocks -- Part 1.Architecture
ICS 25.040.40
CCSN10
National Standards of People's Republic of China
Replacing GB/T 19769.1-2015
Function Blocks Part 1.Structure
(IEC 61499-1.2012, IDT)
Published on 2022-04-15
2022-11-01 Implementation
State Administration for Market Regulation
Released by the National Standardization Administration
directory
Foreword V
Introduction VIII
1 Scope 1
2 Normative references 1
3 Terms and Definitions 2
4 Reference model 10
4.1 System Model 10
4.2 Device Model 11
4.3 Resource Model 12
4.4 Application Model 13
4.5 Function Block Model 14
4.5.1 Characteristics of function block instances 14
4.5.2 Function block type specification 15
4.5.3 Execution model of basic function blocks 15
4.6 Distributed Model 17
4.7 Management Model 17
4.8 Operating State Model 19
5 Function block, sub-application and adapter interface type specification 19
5.1 Overview 19
5.2 Basic function blocks 20
5.2.1 Type declarations 20
5.2.2 Instance behavior 22
5.3 Compound function blocks 25
5.3.1 Type Specification 25
5.3.2 Instance behavior 27
5.4 Subapplications 28
5.4.1 Type Specification 28
5.4.2 Instance behavior 29
5.5 Adapter interface 30
5.5.1 General 30
5.5.2 Type Specification 30
5.5.3 Usage 31
5.6 Exception and fault handling 33
6 Service interface function block 33
6.1 General 33
6.1.1 Overview 33
6.1.2 Type Specifications 33
6.1.3 Instance behavior 35
6.2 Communication function block 37
6.2.1 Type Specifications 37
6.2.2 Instance behavior 38
6.3 Management function block 38
6.3.1 Requirements 38
6.3.2 Type Specifications 39
6.3.3 Behavior modules for managed function blocks 42
7 Configuration of functional units and systems 44
7.1 Configuration principles 44
7.2 Functional Specifications for Resource, Device and Segment Types 44
7.2.1 Functional Specification of Resource Types 44
7.2.2 Functional specification of equipment types 44
7.2.3 Functional Specification of Segment Types 45
7.3 Configuration Requirements 45
7.3.1 System configuration 45
7.3.2 Application Specification 45
7.3.3 Configuration of equipment and resources 45
7.3.4 Configuration of network segments and links 46
Appendix A (Normative) Event Function Block 47
Appendix B (Normative) Text Grammar 54
Appendix C (Informative) Object Model 68
Appendix D (informative) Relationship to IEC 61131-3 76
Appendix E (Informative) Information Exchange 87
Appendix F (Normative) Text Specification 96
Appendix G (Informative) Attribute 118
References 121
Figure 1 System Model 11
Figure 2 Device Model 12
Figure 3 Resource Model 13
Figure 4 Application Model 14
Figure 5 Features of function blocks 15
Figure 6 Execution Model 16
Figure 7 Execution sequence 17
Figure 8 Distributed Model and Management Model 18
Figure 9 Function block and sub-application type 20
Figure 10 Basic function block type declaration 21
Figure 11 ECC example 22
Figure 12 ECC Operation State Machine 23
Figure 13 Example 26 of PI_REAL for a composite function block
Figure 14 Example 27 of the PID_CALC basic function block
Figure 15 Example PI_REAL_APPL for sub-application 29
Figure 16 Adapter Interface Concept Model 30
Figure 17 Adapter type declaration graphic example 31
Figure 18 Diagram of provider and receiver function block type declarations 32
Figure 19 Illustration of adapter connection 32
Figure 20 Example of Service Interface Function Block 35
Figure 21 Example of timing diagram 36
Figure 22 General Management Function Block Type 39
Figure 23 Sequence of service primitives for failed services 39
Figure 24 Managed function block operation state machine 43
Figure A.1 Event Splitting and Merging 53
Figure C.1 ESS overview 68
Figure C.2 Library Elements 69
Figure C.3 Statement 70
Figure C.4 Function Block Network Declaration 72
Figure C.5 Function Block Type Declaration 73
Figure C.6 Summary of IPMCS 74
Figure C.7 Function Block Types and Instances 75
Figure D.1 Example of a "simple" function block type 76
Figure D.2 READ function block type 79
Figure D.3 UREAD function block type 81
Figure D.4 WRITE function block type 82
Figure D.5 TASK function block type 84
Figure E.1 Type Specification for One-Way Transactions 88
Figure E.2 Establishment of a one-way transactional connection 88
Figure E.3 Normal one-way data transfer 88
Figure E.4 Connection release for unidirectional data transfer 89
Figure E.5 Bidirectional Transaction Type Specification 89
Figure E.6 Establishment of a bidirectional transactional connection 90
Figure E.7 Bidirectional data transfer 90
Figure E.8 Connection release for bidirectional data transfer 90
Table 1 States and transitions of the ECC operating state machine 23
Table 2 Standard Inputs and Outputs of the Service Interface Function Block 34
Table 3 Service Primitive Semantics 36
Table 4 Variable Semantics of Communication Function Blocks 37
Table 5 Semantics of service primitives for communication function blocks 38
Table 6 CMD input values and semantics 39
Table 7 STATUS output values and semantics 40
Table 8 Command syntax 41
Table 9 Action semantics 43 in Figure 24
Table A.1 Event function block 47
Table C.1 ESS class description 69
Table C.2 Syntax Generation for Library Elements 69
Table C.3 Statement Syntax Generation 71
Table C.4 IPMCS class 74
Table D.1 Semantics of STATUS values 77
Table D.2 Source code for READ function block types 79
Table D.3 Source code for UREAD function block types 81
Table D.4 Source code for WRITE function block types 83
Table D.5 Source code for TASK function block types 84
Table D.6 IEC 61499-4 Interaction Characteristics 86
Table E.1 COMPACT encoding for fixed-length data types 94
Table G.1 Definition of attribute elements 118
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 of Standardization Documents"
drafted.
This document is part 1 of GB/T 19769.GB/T 19769 has released the following parts.
---GB/T 19769.1 Function Block Part 1.Structure;
---GB/T 19769.2 Function Block Part 2.Requirements for Software Tools;
--- GB/T 19769.3 Industrial Process Measurement and Control Systems - Part 3.Guidance Information;
---GB/T 19769.4 Function Block Part 4.Rules for Conformance Profiles.
This document replaces GB/T 19769.1-2015 "Function Block Part 1.Structure". Compared with GB/T 19769.1-2015, except for the structure
In addition to structural adjustments and editorial changes, the main technical changes are as follows.
--- Change Note 1 to text "This document does not limit or specify the functions of IPMCS or their system elements, unless a function requires
Use the elements defined in this document to represent. IEC 61499-4 states that elements defined in this document may be subject to conformance systems.
extent of functional limitations of systems, subsystems and equipment. " (see Chapter 1, Chapter 1 of the.2015 edition);
--- Deleted the terms "Access Path", "Configuration (Programmable Control System)"; added "Cross Settlement", "Service Sequence Diagram" and "Temporary Change".
"quantity" and other terms (see Chapter 3, Chapter 3 of the.2015 edition);
--- Change Note 3 to the text "The communication link can be directly connected to the device, or it can be connected to a specific resource type ("communication resource")
Instances are connected. Depending on the type of resource, some distributed applications on it can be mapped, while others cannot. "
(see 4.2, 4.2 of the.2015 edition);
--- Deleted "methods to obtain traditional scheduling functions, such as periodic execution of function block networks, described in Chapter 3 of GB/T 19769.3
described. "(see 4.3 of the.2015 edition);
--- Added "Through the additional functions of related resources, the internal variables and status information of function block instances can be accessed." (see 4.5.1);
--- Change Note 1 to the text "other function block instances or the event output of the same function block instance as the event input event.
These event outputs are generated by the execution control described above, or by the "communication map" "process map" "scheduling" and resource
other functional abilities. "; will "standardization of the function block execution control specification under normal circumstances (including the above)
Seek is defined in Chapter 5 of this document. " is changed to " The specific requirements for the graphic representation of function block types are shown in 5.2.1.1.";deleted
"Users of this document should be aware that if these requirements are not met, the results of algorithm execution are unpredictable."
(see 4.5.3, 4.5.3 of the.2015 edition);
--- "EI variable" is changed to "event input", "EO variable" is changed to "event output" (see Figure 9, Figure 9 of the.2015 edition);
--- Deleted 5.2.1.3 and 5.2.1.4 of the.2015 edition, and added 5.2.2.3 and 5.2.2.4 (see 5.2, 5.2 of the.2015 edition);
--- Changed the content of EC conversion in 5.2.2.4 and the interpretation of symbols in Figure 11 (see 5.2.2.4,.2015 edition of
5.2.2.4);
---Moved Figure 12 and Table 1 from 5.2.2.2 to 5.2.2.4, and changed the ECC state machine state transitions t1, t2 in Table 1,
Condition for t3; change "The transition function is activated by the generation of the previous event on the event input." in footnote a of Table 1 to "The source should be
Make sure that no more than one input event is fired at any given moment. "; added "(or equivalent) after footnote b in Table 1
function)"; the footnote c of Table 1 has been changed and supplemented (see 5.2.2.4, 5.2.2.2 of the.2015 edition);
--- Added "or provided by software tools to eliminate redundant sampling during the implementation phase" [see 5.3.1e)];
--- In the case of "services represented by two or more service interface function blocks, the ISO /IEC 10731 Figures 4 and 5 shall be used.
Notation, as described in E.2." to "" where the service is represented by two or more service interface function blocks, you can
Use the symbols shown in E.2.2 and E.2.3."[see 6.1.3c),.2015 edition of 6.1.3c)];
--- Added the RESET command with the semantics of "reset the specified object" (see Table 6);
--- Delete the corresponding items of access-related create, delete and query command syntax; add the reset command syntax item; delete the corresponding items
Description of access related commands (see Table 8, Table 8 of the.2015 edition);
--- Added the conditions for running state transitions (see Figure 24);
--- Removed "Maximum number of data connections and event connections that can exist in a resource type instance" and "In each resource type instance
Any access path that always exists in the example. ", and will "any data connections and events that always exist in each resource type instance
file connections" to "Any data connections, adapter connections, and event connections that always exist in each instance of a resource type"
(see 7.2.1, 7.2.1 of the.2015 edition);
--- Added functional specification of segment type (see 7.2.3);
--- Changed the content after "Resource configuration follows the following rules" (see 7.3.3, 7.3.3 of the.2015 edition);
---Added "or the declared value of the network segment parameter is inconsistent with the declaration of the network segment type defined in 7.2.3 (if any)"
(see 7.3.4);
--- Changed the pictures at "ECC/Algorithm/Service Sequence" in the entries numbered 3, 4, 5, 6, 11, 12, 18 in Table A.1 (see
Table A.1, Table A.1 of the.2015 edition);
--- Change the EI event to the START event at the text description numbered 11 in Table A.1 (see Table A.1,.2015 edition of
Table A.1);
--- Change the EI event to the START event and EO2 to EO1 at the text description numbered 12 in Table A.1 (see
Table A.1, Table A.1 of the.2015 edition);
--- Changed the location of the character set (see B.1, B.1 of the.2015 edition);
--- Changed the content of the grammar parts of B.2.1, B.2.2, B.3, B.5, B.7 (see Appendix B, Appendix B of the.2015 edition);
--- Added "The syntax defined below should be used to assign labels defined in ISO /IEC 8824-1.2008 to this appendix and appendix E
Derived data types defined in. As defined in ISO /IEC 8824-1.2008, class label applications and special procedures shall be used.
order, except for types that are used only for context-specific tags. "(see B.6);
Items of 4 categories such as Declaration (see Table C.3);
--- Figure C.5 is divided into Figure C.5a) composition and Figure C.5b) class inheritance, and the "Component" part adds PlugDeclaration,
--- Added two semantics of "invalid subscript value" and "array size error" (see Table D.1);
--- Added "The prefix F_ instead of FB_ can optionally be used for simple function block types that are IEC 61131-3 function conversions
results" (see D.2);
--- Increased the interaction process with the programmable controller (see D.6);
--- Added "The rules defined in ISO /IEC 8825-1 are used" (see E.3.1);
--- Changed the content of ASN.1MODULE (see E.3.2, E.3.2 of the.2015 edition);
--- Added coding provisions for array elements [see E.3.3.2f)];
--- Changed the specification syntax (see Appendix F, Appendix F of the.2015 edition).
This document is equivalent to IEC 61499-1.2012 "Function Block Part 1.Structure".
The following editorial changes have been made to this document.
--- Normative references have deleted IEC 61131-1 that was not normatively cited, and placed it in the reference.
Please note that some content of this document may be patented. The issuing agency of this document assumes no responsibility for identifying patents.
This document is proposed by China Machinery Industry Federation.
This document is under the jurisdiction of the National Technical Committee for Standardization of Industrial Process Measurement and Control (SAC/TC124).
This document is drafted by. Southwest University, Xiamen Anton Electronics Co., Ltd., Chongqing Institute of Industrial Automation Instrumentation, Shanghai Jiaotong University,
Schneider Electric (China) Co., Ltd. Shanghai Branch, Beijing Jinlishi Instrument Technology Co., Ltd., Shenzhen Biaoli Technology Development Co., Ltd.
Company, Shenzhen Ertai Technology Co., Ltd., Zibo Vocational College, Jiangsu Jack Instrument Co., Ltd., Shanghai Lige Instrument Co., Ltd., Anhui Tian
Kang (Group) Co., Ltd., Shenyang Zhongke Bo Micro Technology Co., Ltd., Beijing Machinery Industry Automation Research Institute Co., Ltd., Anhui
Automation Instrument Co., Ltd., Chongqing Technology Testing Center, Qingdao Automation Instrument Co., Ltd., EVOC Intelligent Technology Co., Ltd., China
Silian Instrument Group Co., Ltd., Nanjing Keda New Control Instrument Co., Ltd., Chongqing Wei'an Tester Manufacturing Co., Ltd., Xi'an Youyi
Control Technology Development Co., Ltd., Shaanxi Chuangwei Technology Co., Ltd., Maanshan Knight Instrument Technology Co., Ltd., Shanghai Enbang Automation
Instrument Co., Ltd., Sichuan Huikeda Instrument Manufacturing Co., Ltd., Hangzhou Zhenhua Instrument Co., Ltd., Xi'an Shaangu Power Co., Ltd.
Company, Hanwei Technology Group Co., Ltd., Chongqing Naide Automation Technology Co., Ltd., Rockwell Automation (China) Co., Ltd.
The main drafters of this document. Yang Yang, Liu Feng, Zhang Ying, Zheng Chuanlin, Zhang Xinguo, Xiao Guozhuan, Liu Qin, Dai Wenbin, Yan Xinhua, Zhu Hailiang,
Ren Junmin, Zheng Yanzhe, Li Xueyan, Sun Shunyuan, Chen Wenxian, Mao Wenwen, Lin Yue, Han Lixin, Ke Youxi, Zhou Aihua, Yang Weishan, Chen Zhilie,
Liu Jin, Liu Yanshan, Ou Wenhui, Hu Ming, Wu Hongwei, Shu Gaoxiang, Zhang Peng, Lan Ruoling, Xing Weiji, Zhong Rui, Jin Guixin, Li Hongbiao, Gao Jingmei, Sun Jie,
Wang Sha.
The previous versions of the documents replaced by this document are as follows.
---GB/T 19769.1-2005, GB/T 19769.1-2015.
Introduction
GB/T 19769 consists of the following parts.
---GB/T 19769.1, including the following.
● general requirements, including scope, normative references, definitions and reference models;
● Rules for declaring function block types and rules for the behavior of instances of that type;
● Rules for the use of function blocks in configuring a distributed industrial process measurement and control system (IPMCS);
● Rules for the use of function blocks in meeting the communication requirements of distributed IPMCS;
● In the distributed IPMCS, when managing applications, resources and equipment, the rules for the use of function blocks.
---GB/T 19769.2, defines the software tool requirements to support the following system engineering tasks.
● Specification of function block types;
● Functional specification of resource types and device types;
● Specification, analysis and verification of distributed IPMCS;
● Configuration, implementation, operation and maintenance of distributed IPMCS;
● Information exchange between software tools.
--- GB/T 19769.3, the purpose is to promote understanding and acceptance, promote the general and domain-specific applicability of IPMCS structure, promote
Advanced software tools meet the needs of other parts by providing.
● FAQs about GB/T 19769 (all parts);
● An example of using GB/T 19769.1 to solve problems commonly encountered in control and automation engineering.
The IEC standard adopted in this part has been withdrawn, but subsequent IEC editions may be updated in the future, so this part will follow the IEC edition
Revised in this update.
--- GB/T 19769.4, specifies the characteristics of GB/T 19769.1 and GB/T 19769.2 to be implemented in order to promote
The following attributes of systems, equipment and software tools of GB/T 19769.
● Interoperability of equipment from multiple vendors;
● portability between software tools provided by multiple vendors;
● Configurability of multiple vendor software for equipment from different manufacturers.
Function Blocks Part 1.Structure
1 Scope
System, IPMCS) general structure, and gives the function block usage guide. According to the achievable reference model, text grammar and diagram
The notation shown to give this structure. These models, notations and syntaxes apply to.
● Specification and standardization of function block types;
● functional specification and standardization of system elements;
● Specification, analysis and verification of implementation-independent distributed IPMCS;
● Configuration, implementation, operation and maintenance of distributed IPMCS;
● Information exchange between software tools that implement the above functions.
This document does not limit or specify the functions of IPMCS or their system elements, unless a function uses the elements defined in this document
always expressed. IEC 61499-4 states that the elements defined in this document may be subject to functional limitations of conforming systems, subsystems and equipment.
degree.
One of the purposes of this document is to provide a reference model for the use of function blocks in other standards that support the system life cycle. system life cycle
The period includes system planning, design, implementation, verification, operation and maintenance. The models presented in this document are generic, industry-independent, and
Extensions to function block definitions and usage in other standards, specific applications or application areas. Its purpose is to formulate, in accordance with the rules given in this document,
Produce concise, achievable, unambiguous, and consistent specifications.
Note 1.The rules provided by this document alone are not sufficient to ensure interoperability between equipment from different equipment manufacturers. Compliance with other standards in this document may be specified
Additional terms to ensure this interoperability.
Note 2.Compliance with other standards in this document may provide additional clauses to improve the performance of system, device, resource and application management functions.
2 Normative references
The contents of the following documents constitute essential provisions of this document through normative references in the text. Among them, dated citations
documents, only the version corresponding to that date applies to this document; for undated references, the latest edition (including all amendments) applies to
this document.
GB/T 9387.1-1998 Information Technology Open System Interconnection Basic Reference Model Part 1.Basic Model (idtISO /
IEC 7498-1.1994)
GB/T 13000-2010 Universal multi-octet coded character set (UCS) for information technology (ISO /IEC 10646.2003, IDT)
ISO /IEC 8824-1.2008 Information Technology Abstract Syntax Notation (ASN.1). Basic Notation Specification [Information
Note. GB/T 16262.1-2006 Information Technology Abstract Syntax Notation One (ASN.1) Part 1.Basic Notation Specification (ISO /IEC 8824-1.
2002, IDT)
Note. GB/T 15969.3-2017 Programmable Controllers Part 3.Programming Languages (IEC 61131-3.2013, IDT)
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 19769.1-2022_English be delivered?Answer: Upon your order, we will start to translate GB/T 19769.1-2022_English as soon as possible, and keep you informed of the progress. The lead time is typically 7 ~ 11 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of GB/T 19769.1-2022_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 19769.1-2022_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. Question 5: Should I purchase the latest version GB/T 19769.1-2022?Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version GB/T 19769.1-2022 even if the enforcement date is in future. Complying with the latest version means that, by default, it also complies with all the earlier versions, technically.
|