Jun,05

IEC 61499-1-2005 pdf – Function blocks – Part 1: Architecture

IEC 61499-1-2005 pdf – Function blocks – Part 1: Architecture

IEC 61499-1-2005 pdf – Function blocks – Part 1: Architecture.
1 Scope This part of IEC 61499 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. These models, representations and syntax can be used for: • the specification and standardization of function block types; • the functional specification and standardization of system elements; • the implementation independent specification, analysis, and validation of distributed IPMCSs; • the configuration, implementation, operation, and maintenance of distributed IPMCSs; • the exchange of information among software tools for the performance of the above functions. NOTE 1 This part of IEC 61499 does not restrict or specify the functional capabilities of IPMCSs or their system elements, except as such capabilities are represented using the elements defined herein. IEC 61499-4 addresses the extent to which the elements defined in this part of IEC 61499 may be restricted by the functional capabilities of compliant systems, subsystems, and devices. Part of the purpose of this part of IEC 61499 is to provide reference models for the use of function blocks in other standards dealing with the support of the system life cycle, including system planning, design, implementation, validation, operation and maintenance. The models given in this part of IEC 61499 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 part of IEC 61499 be concise, implementable, complete, unambiguous, and consistent.
3 Terms and definitions For the purposes of this document, the terms and definitions given in the ISO/AFNOR Dictionary of computer science, as well as the following apply. NOTE Terms defined in this clause are italicized where they appear in the bodies of definitions. 3.1 acceptor function block instance which provides a socket adapter of a defined adapter interface type 3.2 access path association of a symbolic name with a variable for the purpose of open communication 3.3 adapter connection connection from a plug adapter to a socket adapter of the same adapter interface type, which carries the flows of data and events defined by the adapter interface type 3.4 adapter interface type type which consists of the definition of a set of event inputs, event outputs, data inputs, and data outputs, and whose instances are plug adapters and socket adapters 3.5 algorithm finite set of well-defined rules for the solution of a problem in a finite number of operations 3.6 application software functional unit that is specific to the solution of a problem in industrial-process measurement and control NOTE An application may be distributed among resources, and may communicate with other applications. 3.7 attribute property or characteristic of an entity, for instance, the version identifier of a function block type specification 3.8 basic function block type function block type that cannot be decomposed into other function blocks and that utilizes an execution control chart (ECC) to control the execution of its algorithms
3.20 configuration parameter parameter related to the configuration of a system, device or resource 3.21 confirm primitive service primitive which represents an interaction in which a resource indicates completion of some algorithm previously invoked by an interaction represented by a request primitive 3.22 connection association established between functional units for conveying information [ISO/AFNOR: 1989] 3.23 critical region operation or sequence of operations which is executed under the exclusive control of a locking object which is associated with the data on which the operations are performed 3.24 data reinterpretable representation of information in a formalized manner suitable for communication, interpretation or processing [ISO 2382-01.01.02] 3.25 data connection association between two function blocks for the conveyance of data 3.26 data input interface of a function block which receives data from a data connection 3.27 data output interface of a function block which supplies data to a data connection 3.28 data type set of values together with a set of permitted operations [ISO 2382-15.04.01] 3.29 declaration mechanism for establishing the definition of an entity NOTE A declaration may involve attaching an identifier to the entity, and allocating attributes such as data types and algorithms to it. 3.30 device independent physical entity capable of performing one or more specified functions in a particular context and delimited by its interfaces NOTE A programmable controller system as defined in IEC 61131-1 is a device.

Download
The previous

IEC 60974-1-2005 pdf - Arc welding equipment – Part 1: Welding power sources

The next

IEC 62013-2-2005 pdf - Caplights for use in mines susceptible to firedamp – Part 2: Performance and other safety- related matters

Related Standards