BS EN 61499-2-2013 Function blocks Software tool requirements《功能块 软件工具要求》.pdf

1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationFunction blocksPart 2: Software tool requirementsBS EN 61499-2:2013National forewordThis British Standard is the UK implementation of EN 61499-2:2013. It isidentical to IEC 61499

2、-2:2012. It supersedes BS EN 61499-2:2005 which iswithdrawn.The UK participation in its preparation was entrusted to Technical CommitteeGEL/65, Measurement and control.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport t

3、o include all the necessary provisions of acontract. Users are responsible for its correct application. The British Standards Institution 2013Published by BSI Standards Limited 2013ISBN 978 0 580 79809 2ICS 25.040; 35.240.50 Compliance with a British Standard cannot confer immunity fromlegal obligat

4、ions.This British Standard was published under the authority of the StandardsPolicy and Strategy Committee on 30 April 2013.Amendments issued since publicationAmd. No. Date Text affectedBRITISH STANDARDBS EN 61499-2:2013EUROPEAN STANDARD EN 61499-2 NORME EUROPENNE EUROPISCHE NORM February 2013CENELE

5、C European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elektrotechnische Normung Management Centre: Avenue Marnix 17, B - 1000 Brussels 2013 CENELEC - All rights of exploitation in any form and by any means reserved worldwide

6、for CENELEC members. Ref. No. EN 61499-2:2013 E ICS 25.040; 35.240.50 Supersedes EN 61499-2:2005 English version Function blocks - Part 2: Software tool requirements (IEC 61499-2:2012) Blocs fonctionnels - Partie 2: Exigences pour les outils logiciels(CEI 61499-2:2012) Funktionsbausteine fr industri

7、elle Leitsysteme - Teil 2: Anforderungen an Software-Werkzeuge(IEC 61499-2:2012) This European Standard was approved by CENELEC on 2012-12-12. CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of

8、a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CENELEC member. This European Standard exists in three official versions (English, French, Germ

9、an). A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions. CENELEC members are the national electrotechnical committees of Austria, Belgium

10、, Bulgaria, Croatia, Cyprus, the Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, S

11、witzerland, Turkey and the United Kingdom. BS EN 61499-2:2013EN 61499-2:2013 - 2 - Foreword The text of document 65B/846/FDIS, future edition 2 of IEC 61499-2, prepared by IEC/TC 65B “Measurement and control devices“ of IEC/TC 65 “Industrial-process measurement, control and automation“ was submitted

12、 to the IEC-CENELEC parallel vote and approved by CENELEC as EN 61499-2:2013. The following dates are fixed: latest date by which the document has to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2013-09-12 latest date by which the national

13、 standards conflicting with the document have to be withdrawn (dow) 2015-12-12 This document supersedes EN 61499-2:2005. EN 61499-2:2013 includes the following significant technical changes with respect to EN 61499-2:2005: - the contents of Annex A have been updated to conform to the technical chang

14、es of the second edition of EN 61499-1; - CDATA sections are now allowed for the textual contents of algorithms in Tables A.4 and A.5. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CENELEC and/or CEN shall not be held responsibl

15、e for identifying any or all such patent rights. Endorsement notice The text of the International Standard IEC 61499-2:2012 was approved by CENELEC as a European Standard without any modification. In the official version, for Bibliography, the following note has to be added for the standard indicate

16、d : IEC 61499-4 NOTE Harmonised as EN 61499-4. BS EN 61499-2:2013- 3 - EN 61499-2:2013 Annex ZA (normative) Normative references to international publications with their corresponding European publications The following documents, in whole or in part, are normatively referenced in this document and

17、are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. NOTE When an international publication has been modified by common modifications, indicated by (mod),

18、 the relevant EN/HD applies. Publication Year Title EN/HD Year IEC 61131-3 2003 Programmable controllers - Part 3: Programming languages EN 61131-3 2003 IEC 61499-1 2012 Function blocks - Part 1: Architecture EN 61499-1 2013 ISO/IEC 8824 Series Information technology - Abstract Syntax Notation One (

19、ASN.1) - - BS EN 61499-2:2013 2 61499-2 IEC:2012 CONTENTS INTRODUCTION . 5 1 Scope . 6 2 Normative references . 6 3 Terms and definitions . 6 4 Software tool requirements . 7 Information to be provided by the software tool supplier 7 4.1Exchange of library elements 7 4.2Information to be provided by

20、 the supplier of library elements . 7 4.3Display of declarations 7 4.4Modification of declarations . 8 4.5Validation of declarations 8 4.6Implementation of declarations 8 4.7System operation, testing and maintenance 8 4.8Annex A (normative) Document type definitions (DTDs) . 9 Annex B (informative)

21、Graphics model . 26 Annex C (informative) Examples 29 Bibliography 47 Figure B.1 Graphics model . 26 Figure B.2 ECC drawing example 28 Table A.1 Document type definition (DTD) elements 9 Table A.2 DataType DTD (1 of 2) . 10 Table A.3 DataType DTD elements (1 of 2) 12 Table A.4 Library Element DTD (1

22、 of 5) . 15 Table A.5 LibraryElement DTD elements (1 of 5) . 20 BS EN 61499-2:201361499-2 IEC:2012 5 INTRODUCTION IEC 61499 consists of the following parts, under the general title Function blocks: Part 1: Architecture Part 2: Software tool requirements Part 3: Tutorial information (withdrawn) Part

23、4: Rules for compliance profiles BS EN 61499-2:2013 6 61499-2 IEC:2012 FUNCTION BLOCKS Part 2: Software tool requirements 1 Scope This part of IEC 61499 defines requirements for software tools to support the following systems engineering tasks enumerated in IEC 61499-1: the specification of function

24、 block types; the functional specification of resource types and device types; the specification, analysis, and validation of distributed IPMCSs; the configuration, implementation, operation, and maintenance of distributed IPMCSs; the exchange of information among software tools. It is assumed that

25、such software tools may be used in the context of an Engineering Support System (ESS) as described in IEC 61499-1. It is beyond the scope of this standard to specify the entire life cycle of industrial-process measurement and control systems (IPMCSs), or the entire set of tasks and activities requir

26、ed to support an IPCMS over its life cycle. However, other standards which do specify such tasks and activities may extend or modify the requirements specified in this part of IEC 61499. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document

27、and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. IEC 61131-3:2003, Programmable controllers Part 3: Programming languages IEC 61499-1:2012, Functi

28、on blocks Part 1: Architecture ISO/IEC 8824 (all parts), Information technology Abstract Syntax Notation One (ASN.1) 3 Terms and definitions For the purposes of this document, the terms and definitions given in IEC 61499-1, as well as the following apply. 3.1library element collection of declaration

29、s applying to a data type, function block type, adapter type, subapplication type, resource type, device type, segment type, or system configuration BS EN 61499-2:201361499-2 IEC:2012 7 4 Software tool requirements Information to be provided by the software tool supplier 4.1This Clause defines the f

30、unctional requirements of software tools that support the performance of the systems engineering tasks enumerated in Clause 1. The supplier of a software tool shall specify the following information in addition to other information required in this Clause: the type or types of library element to whi

31、ch the software tool applies; the engineering task or tasks supported by the software tool. Task descriptions may be taken from the enumeration of engineering tasks given in Clause 1, or may be defined by the supplier. Exchange of library elements 4.2A software tool shall be capable of exchanging it

32、s library elements with other software tools. This exchange shall take the form of data in the format defined in Annex A, written on physical media or exchanged over communication links or networks. Information to be provided by the supplier of library elements 4.3NOTE The provisions of this subclau

33、se are intended to provide the means by which the provider of a library element may achieve protection of intellectual property while still providing sufficient information to permit the effective use of the library element. The provider of a library element may elect to provide an implementation of

34、 the library element. EXAMPLE 1 The provider of a function block type library element may provide an implementation of the function block type as: one or more instances of the function block type in a resource contained in a device of Class 0 or higher as described in IEC 61499-4; an instantiable im

35、plementation of the function block type in a resource contained in a device of Class 1 or higher as described in IEC 61499-4; a file in an implementation-dependent format suitable for installation in a resource contained in a deviceof Class 2 as described in IEC 61499-4, for instance using the XML s

36、yntax defined in Annex D. When an implementation of a library element is provided, the provider is not required to provide full details of the implementation. However, the provider shall provide sufficient information to enable the user to fully determine the functionality of the provided library el

37、ement. EXAMPLE 2 The requirement of the above paragraph would be met by the provider of an instance of a function block type in a resource through the provision, at a minimum, of the following information: a function block type library element specifying its event interfaces, data interfaces and ser

38、vices as defined in IEC 61499-1; resource type and device type library elements showing the occurrence and connections of the function block instances. Display of declarations 4.4A software tool shall be capable of displaying the declarations of its associated library elements in a form appropriate

39、to the engineering task. This display may utilize the graphical or textual formats defined in IEC 61499-1, or a format defined by the supplier of the software tool. NOTE The declarations of a library element may define its interfaces (event and data inputs and outputs) and internal variables as well

40、 as its algorithms and the control of their execution, for example via an execution control chart (ECC), etc. BS EN 61499-2:2013 8 61499-2 IEC:2012 Software tools may provide additional features, beyond those illustrated in IEC 61499-1, in the graphic display of declarations. EXAMPLE 1 In the displa

41、y of an Execution Control Chart (ECC), the tool may provide, along with the display of each transition, a cardinal number indicating the order (as defined in IEC 61499-1) in which the transition is evaluated. EXAMPLE 2 A software tool may provide means of navigating a mapping from the display of a f

42、unction block instance in an application to its corresponding display in a resource, and vice versa. Modification of declarations 4.5A software tool shall enable its user to modify the declarations of its associated library elements as appropriate to the engineering task. Such modifications may incl

43、ude adding, deleting or changing the contents of declarations, and may be performed either graphically or textually or both. EXAMPLE The software tool may provide convenient means for the user to change the order in which declarations are listed in their textual representation, for instance in a lis

44、t of transitions in an Execution Control Chart (ECC), without the user having to edit the textual representation by manual means such as “cut and paste“. Validation of declarations 4.6If required by the associated engineering task, a software tool shall provide facilities for validation of the decla

45、rations of its associated library elements. Such facilities may include, but are not limited to: Checking the corectness of the syntax of declarations. Checking the semantic corectness of declarations, for instance, checking whether al function block instances in an application and its associated su

46、bapplications are properly allocated to resources, interconnected within resources, and intercommunicating among resources in a system configuration. Simulation and testing of the operation of an instance of a library element type, either by itself or in association with other instances of the same

47、or different types. Implementation of declarations 4.7If required by the associated engineering task, a software tool shall provide facilities for the implementation of the declarations of its associated library elements. Such facilities may include, but are not limited to: the production of an exec

48、utable code (“firmware“) for embedding in instances of resource types and device types; the creation and interconnection (“downloading“) of function block instances in resources and devices, for instance by using the management facilities defined in subclause 6.3 and Annexes F and G of IEC 61499-1.

49、System operation, testing and maintenance 4.8If required by the associated engineering task, a software tool shall provide facilities for the operation, testing and maintenance of an Industrial Process Measurement and Control System (IPMCS) specified by its associated library elements. Such facilities may include, but are not limited to: the facilities described in preceding subclauses of this Clause; the information exchange facilities defined in IEC 61499-1. BS E