BS EN 61499-1:2013
$215.11
Function blocks – Architecture
| Published By | Publication Date | Number of Pages |
| BSI | 2013 | 122 |
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.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 7 | English CONTENTS |
| 10 | INTRODUCTION |
| 11 | 1 Scope 2 Normative references |
| 12 | 3 Terms and definitions |
| 21 | 4 Reference models 4.1 System model Figures Figure 1 โ System model |
| 22 | 4.2 Device model 4.3 Resource model Figure 2 โ Device model |
| 23 | Figure 3 โ Resource model |
| 24 | 4.4 Application model 4.5 Function block model 4.5.1 Characteristics of function block instances Figure 4 โ Application model |
| 25 | Figure 5 โ Characteristics of function blocks |
| 26 | 4.5.2 Function block type specifications 4.5.3 Execution model for basic function blocks |
| 27 | Figure 6 โ Execution model Figure 7 โ Execution timing |
| 28 | 4.6 Distribution model 4.7 Management model |
| 29 | Figure 8 โ Distribution and management models |
| 30 | 4.8 Operational state models 5 Specification of function block, subapplication and adapter interface types 5.1 Overview |
| 31 | 5.2 Basic function blocks 5.2.1 Type declaration Figure 9 โ Function block and subapplication types |
| 32 | Figure 10 โ Basic function block type declaration |
| 33 | 5.2.2 Behavior of instances Figure 11 โ ECC example |
| 35 | Figure 12 โ ECC operation state machine Tables Table 1 โ States and transitions of ECC operation state machine |
| 36 | 5.3 Composite function blocks 5.3.1 Type specification |
| 37 | Figure 13 โ Composite function block PI_REAL example |
| 38 | 5.3.2 Behavior of instances Figure 14 โ Basic function block PID_CALC example |
| 39 | 5.4 Subapplications 5.4.1 Type specification |
| 40 | 5.4.2 Behavior of instances Figure 15 โ Subapplication PI_REAL_APPL example |
| 41 | 5.5 Adapter interfaces 5.5.1 General principles 5.5.2 Type specification Figure 16 โ Adapter interfaces โ Conceptual model |
| 42 | 5.5.3 Usage Figure 17 โ Adapter type declaration โ graphical example |
| 43 | Figure 18 โ Illustration of provider and acceptor function block type declarations |
| 44 | 5.6 Exception and fault handling 6 Service interface function blocks 6.1 General principles 6.1.1 General Figure 19 โ Illustration of adapter connections |
| 45 | 6.1.2 Type specification Table 2 โ Standard inputs and outputs for service interface function blocks (1 of 2) |
| 46 | 6.1.3 Behavior of instances Figure 20 โ Example service interface function blocks |
| 47 | Figure 21 โ Example service sequence diagrams |
| 48 | 6.2 Communication function blocks 6.2.1 Type specification Table 3 โ Service primitive semantics |
| 49 | 6.2.2 Behavior of instances Table 4 โ Variable semantics for communication function blocks Table 5 โ Service primitive semantics for communication function blocks |
| 50 | 6.3 Management function blocks 6.3.1 Requirements 6.3.2 Type specification Figure 22 โ Generic management function block type |
| 51 | Figure 23 โ Service primitive sequences for unsuccessful service Table 6 โ CMD input values and semantics Table 7 โ STATUS output values and semantics |
| 52 | Table 8 โ Command syntax |
| 53 | 6.3.3 Behavior of managed function blocks |
| 54 | Figure 24 โ Operational state machine of a managed function block |
| 55 | 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 โ Semantics of actions in Figure 24 |
| 56 | 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 |
| 57 | 7.3.2 Specification of applications 7.3.3 Configuration of devices and resources |
| 58 | 7.3.4 Configuration of network segments and links |
| 59 | Annex A (normative) Event function blocks |
| 60 | Table A.1 โ Event function blocks (1 of 6) |
| 65 | Figure A.1 โ Event split and merge |
| 66 | Annex B (normative) Textual syntax |
| 77 | Annex C (informative) Object models Figure C.1 โ ESS overview |
| 78 | Figure C.2 โ Library elements Table C.1 โ ESS class descriptions Table C.2 โ Syntactic productions for library elements |
| 79 | Figure C.3 โ Declarations |
| 80 | Figure C.4 โ Function block network declarations Table C.3 โ Syntactic productions for declarations |
| 82 | Figure C.5 โ Function block type declarations Figure C.6 โ IPMCS overview |
| 83 | Table C.4 โ IPMCS classes |
| 84 | Figure C.7 โ Function block types and instances |
| 85 | Annex D (informative) Relationship to IEC 61131-3 Figure D.1 โ Example of a โsimpleโ function block type |
| 86 | Table D.1 โ Semantics of STATUS values |
| 88 | Figure D.2 โ Function block type READ |
| 89 | Table D.2 โ Source code of function block type READ |
| 90 | Figure D.3 โ Function block type UREAD Table D.3 โ Source code of function block type UREAD |
| 91 | Figure D.4 โ Function block type WRITE |
| 92 | Table D.4 โ Source code of function block type WRITE |
| 93 | Figure D.5 โ Function block type TASK Table D.5 โ Source code of function block type TASK |
| 94 | Table D.6 โ IECย 61499 interoperability features |
| 95 | Annex E (informative) Information exchange |
| 96 | Figure E.1 โ Type specifications for unidirectional transactions Figure E.2 โ Connection establishment for unidirectional transactions Figure E.3 โ Normal unidirectional data transfer |
| 97 | Figure E.4 โ Connection release in unidirectional data transfer Figure E.5 โ Type specifications for bidirectional transactions |
| 98 | Figure E.6 โ Connection establishment for bidirectional transaction Figure E.7 โ Bidirectional data transfer Figure E.8 โ Connection release in bidirectional data transfer |
| 102 | Table E.1 โ COMPACT encoding of fixed length data types |
| 103 | Annex F (normative) Textual specifications |
| 116 | Annex G (informative) Attributes |
| 117 | Table G.1 โ Elements of attribute definitions |
| 120 | Bibliography |
Related products
-
BS EN 61499-4:2013
Function blocks – Rules for compliance profiles Published By Publication Date Number of Pages BSIโฆ
