{"id":244227,"date":"2024-10-19T16:02:29","date_gmt":"2024-10-19T16:02:29","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61499-12013\/"},"modified":"2024-10-25T11:01:21","modified_gmt":"2024-10-25T11:01:21","slug":"bs-en-61499-12013","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61499-12013\/","title":{"rendered":"BS EN 61499-1:2013"},"content":{"rendered":"
IEC 61499-1:2012 defines a generic architecture and presents guidelines for the use of function blocks in distributed industrial-process measurement and control systems (IPMCSs). This architecture is presented in terms of implementable reference models, textual syntax and graphical representations. The models given in this standard are intended to be generic, domain independent and extensible to the definition and use of function blocks in other standards or for particular applications or application domains. It is intended that specifications written according to the rules given in this standard be concise, implementable, complete, unambiguous, and consistent. This second edition cancels and replaces the first edition published in 2005 an constitutes a technical revision. It includes the significant technical changes with respect to the previous edition related to: Execution control, Temporary variables, Service sequences, the syntax for mapping of FB instances, the Syntax for definition of segment types, the Function block types for interoperation with programmable controllers and the READ\/WRITE management commands.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
7<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 4 Reference models 4.1 System model Figures Figure 1 \u2013 System model <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 4.2 Device model 4.3 Resource model Figure 2 \u2013 Device model <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | Figure 3 \u2013 Resource model <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 4.4 Application model 4.5 Function block model 4.5.1 Characteristics of function block instances Figure 4 \u2013 Application model <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | Figure 5 \u2013 Characteristics of function blocks <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 4.5.2 Function block type specifications 4.5.3 Execution model for basic function blocks <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | Figure 6 \u2013 Execution model Figure 7 \u2013 Execution timing <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 4.6 Distribution model 4.7 Management model <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | Figure 8 \u2013 Distribution and management models <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 4.8 Operational state models 5 Specification of function block, subapplication and adapter interface types 5.1 Overview <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 5.2 Basic function blocks 5.2.1 Type declaration Figure 9 \u2013 Function block and subapplication types <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | Figure 10 \u2013 Basic function block type declaration <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 5.2.2 Behavior of instances Figure 11 \u2013 ECC example <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | Figure 12 \u2013 ECC operation state machine Tables Table 1 \u2013 States and transitions of ECC operation state machine <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 5.3 Composite function blocks 5.3.1 Type specification <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Figure 13 \u2013 Composite function block PI_REAL example <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 5.3.2 Behavior of instances Figure 14 \u2013 Basic function block PID_CALC example <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 5.4 Subapplications 5.4.1 Type specification <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 5.4.2 Behavior of instances Figure 15 \u2013 Subapplication PI_REAL_APPL example <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 5.5 Adapter interfaces 5.5.1 General principles 5.5.2 Type specification Figure 16 \u2013 Adapter interfaces \u2013 Conceptual model <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 5.5.3 Usage Figure 17 \u2013 Adapter type declaration \u2013 graphical example <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure 18 \u2013 Illustration of provider and acceptor function block type declarations <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 5.6 Exception and fault handling 6 Service interface function blocks 6.1 General principles 6.1.1 General Figure 19 \u2013 Illustration of adapter connections <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 6.1.2 Type specification Table 2 \u2013 Standard inputs and outputs for service interface function blocks (1 of 2) <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | 6.1.3 Behavior of instances Figure 20 \u2013 Example service interface function blocks <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Figure 21 \u2013 Example service sequence diagrams <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 6.2 Communication function blocks 6.2.1 Type specification Table 3 \u2013 Service primitive semantics <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | 6.2.2 Behavior of instances Table 4 \u2013 Variable semantics for communication function blocks Table 5 \u2013 Service primitive semantics for communication function blocks <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 6.3 Management function blocks 6.3.1 Requirements 6.3.2 Type specification Figure 22 \u2013 Generic management function block type <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | Figure 23 \u2013 Service primitive sequences for unsuccessful service Table 6 \u2013 CMD input values and semantics Table 7 \u2013 STATUS output values and semantics <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | Table 8 \u2013 Command syntax <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 6.3.3 Behavior of managed function blocks <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Figure 24 \u2013 Operational state machine of a managed function block <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 7 Configuration of functional units and systems 7.1 Principles of configuration 7.2 Functional specification of resource, device and segment types 7.2.1 Functional specification of resource types Table 9 \u2013 Semantics of actions in Figure 24 <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 7.2.2 Functional specification of device types 7.2.3 Functional specification of segment types 7.3 Configuration requirements 7.3.1 Configuration of systems <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 7.3.2 Specification of applications 7.3.3 Configuration of devices and resources <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 7.3.4 Configuration of network segments and links <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Annex A (normative) Event function blocks <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Table A.1 \u2013 Event function blocks (1 of 6) <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Figure A.1 \u2013 Event split and merge <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Annex B (normative) Textual syntax <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Annex C (informative) Object models Figure C.1 \u2013 ESS overview <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Figure C.2 \u2013 Library elements Table C.1 \u2013 ESS class descriptions Table C.2 \u2013 Syntactic productions for library elements <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Figure C.3 \u2013 Declarations <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Figure C.4 \u2013 Function block network declarations Table C.3 \u2013 Syntactic productions for declarations <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Figure C.5 \u2013 Function block type declarations Figure C.6 \u2013 IPMCS overview <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Table C.4 \u2013 IPMCS classes <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Figure C.7 \u2013 Function block types and instances <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Annex D (informative) Relationship to IEC 61131-3 Figure D.1 \u2013 Example of a \u201csimple\u201d function block type <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Table D.1 \u2013 Semantics of STATUS values <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | Figure D.2 \u2013 Function block type READ <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | Table D.2 \u2013 Source code of function block type READ <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Figure D.3 \u2013 Function block type UREAD Table D.3 \u2013 Source code of function block type UREAD <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | Figure D.4 \u2013 Function block type WRITE <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Table D.4 \u2013 Source code of function block type WRITE <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Figure D.5 \u2013 Function block type TASK Table D.5 \u2013 Source code of function block type TASK <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Table D.6 \u2013 IEC\u00a061499 interoperability features <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Annex E (informative) Information exchange <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Figure E.1 \u2013 Type specifications for unidirectional transactions Figure E.2 \u2013 Connection establishment for unidirectional transactions Figure E.3 \u2013 Normal unidirectional data transfer <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Figure E.4 \u2013 Connection release in unidirectional data transfer Figure E.5 \u2013 Type specifications for bidirectional transactions <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Figure E.6 \u2013 Connection establishment for bidirectional transaction Figure E.7 \u2013 Bidirectional data transfer Figure E.8 \u2013 Connection release in bidirectional data transfer <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Table E.1 \u2013 COMPACT encoding of fixed length data types <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Annex F (normative) Textual specifications <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | Annex G (informative) Attributes <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | Table G.1 \u2013 Elements of attribute definitions <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Function blocks – Architecture<\/b><\/p>\n |