ANSI ISA TR61804-4-2007 Function Blocks (FB) for Process Control - Part 4 EDD Interoperability Guideline (104.00.02).pdf

1、 TECHNICAL REPORT ANSI/ISA-TR61804-4 (104.00.02)-2007 A Technical Report prepared by ISA and registered with ANSI Function Blocks (FB) for Process Control Part 4: EDD Interoperability Guideline Approved 30 September 2007 ANSI/ISA-TR61804-4 (104.00.02)-2007 Function Blocks (FB) for Process Control Pa

2、rt 4: EDD Interoperability Guideline ISBN: 978-1-934394-38-0 Copyright 2007 by IEC and ISA. All rights reserved. Not for resale. Printed in the United States of America. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means (electron

3、ic, mechanical, photocopying, recording, or otherwise), without the prior written permission of the Publisher. ISA 67 Alexander Drive P. O. Box 12277 Research Triangle Park, North Carolina 27709 USA 3 ANSI/ISA-TR61804-4 (104.00.02)-2007 Copyright 2007 ISA. All rights reserved. Preface This preface,

4、as well as all footnotes and annexes, is included for information purposes and is not part of ANSI/ISA-TR61804-4 (104.00.02)2007. The standards referenced within this document may contain provisions which, through reference in this text, constitute requirements of this document. At the time of publi

5、cation, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this document are encouraged to investigate the possibility of applying the most recent editions of the standards indicated within this document. Members of IEC and ISO maintain regis

6、ters of currently valid International Standards. ANSI maintains registers of currently valid U.S. National Standards. This document has been prepared as part of the service of ISA, toward a goal of uniformity in the field of instrumentation. To be of real value, this document should not be static bu

7、t should be subject to periodic review. Toward this end, the Society welcomes all comments and criticisms and asks that they be addressed to the Secretary, Standards and Practices Board; ISA; 67 Alexander Drive; P. O. Box 12277; Research Triangle Park, NC 27709; Telephone (919) 549-8411; Fax (919) 5

8、49-8288; E-mail: standardsisa.org. The ISA Standards and Practices Department is aware of the growing need for attention to the metric system of units in general, and the International System of Units (SI) in particular, in the preparation of instrumentation standards. The Department is further awar

9、e of the benefits to USA users of ISA standards of incorporating suitable references to the SI (and the metric system) in their business and professional dealings with other countries. Toward this end, this Department will endeavor to introduce SI-acceptable metric units in all new and revised stand

10、ards, recommended practices, and technical reports to the greatest extent possible. Standard for Use of the International System of Units (SI): The Modern Metric System, published by the American Society for Testing any IEC National Committee interested in the subject dealt with may participate in t

11、his preparatory work. International, governmental and non-governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for Standardization (ISO) in accordance with conditions determined by agreement between the tw

12、o organizations. 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international consensus of opinion on the relevant subjects since each technical committee has representation from all interested IEC National Committees. 3) IEC Publications have th

13、e form of recommendations for international use and are accepted by IEC National Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any misinter

14、pretation by any end user. 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications transparently to the maximum extent possible in their national and regional publications. Any divergence between any IEC Publication and the corresponding national

15、or regional publication shall be clearly indicated in the latter. 5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any equipment declared to be in conformity with an IEC Publication. 6) All users should ensure that they have the latest edition of t

16、his publication. 7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and members of its technical committees and IEC National Committees for any personal injury, property damage or other damage of any nature whatsoever, whether direct or i

17、ndirect, or for costs (including legal fees) and expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC Publications. 8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is indispensable for

18、 the correct application of this publication. 9) Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights other than those identified above. IEC shall not be held responsible for identifying any or all such patent rights. The main task of I

19、EC technical committees is to prepare International Standards. However, a technical committee may propose the publication of a technical report when it has collected data of a different kind from that which is normally published as an International Standard, for example, “state of the art”. Technica

20、l reports do not necessarily have to be reviewed until the data they provide are considered to be no longer valid or useful by the maintenance team. IEC 61804-4, which is a Technical Report, has been prepared by subcommittee 65C: Digital communications, of IEC technical committee 65: Industrial-proc

21、ess measurement and control. The text of this Technical Report is based on the following documents: Enquiry draft Report on voting 65C/410/DTR 65C/417/RVC ANSI/ISA-TR61804-4 (104.00.02)-2007 8 Copyright 2007 ISA. All rights reserved. Full information on the voting for the approval of this Technical

22、Report can be found in the report on voting indicated in the above table. This publication has been drafted in accordance with the ISO/IEC Directives, Part 2. The list of all the parts of the IEC 61804 series, under the general title Function blocks (FB) for process control, can be found on the IEC

23、website. The committee has decided that the contents of this publication will remain unchanged until the maintenance result date indicated on the IEC web site under “http:/webstore.iec.ch“ in the data related to the specific publication. At this date, the publication will be reconfirmed, withdrawn,

24、replaced by a revised edition, or amended. A bilingual version of this publication may be issued at a later date. 9 ANSI/ISA-TR61804-4 (104.00.02)-2007 Copyright 2007 ISA. All rights reserved. INTRODUCTION This Technical Report contains an overview of the use of EDDL; provides examples demonstrating

25、 the use of the EDDL constructs; shows how the use cases are fulfilled; and shows the proper EDD application interpretation for each example. This Technical Report is not an EDDL tutorial and is not intended to replace the EDDL specification. Instructions are provided for the EDD application, which

26、describe what is to be performed without prescribing the technology used in the host implementation. For example, the FILE construct describes data that is to be stored by the EDD application on behalf of the EDD. The FILE construct does not specify how the data is to be stored. The EDD application

27、can use a database, a flat file, or any other implementation it chooses. This page intentionally left blank. 11 ANSI/ISA-TR61804-4 (104.00.02)-2007 Copyright 2007 ISA. All rights reserved. ISA FOREWORD Publication of this Technical Report that has been registered with ANSI has been approved by ISA,

28、67 Alexander Drive, P. O. Box 12277; Research Triangle Park, NC 27709. This document is registered as a Technical Report according to the Procedures for the Registration of Technical Reports with ANSI. This document is not an American National Standard and the material contained herein is not normat

29、ive in nature. Comments on the content of this document should be sent to ISA, 67 Alexander Drive, P. O. Box 12277; Research Triangle Park, NC 27709. This page intentionally left blank. 13 ANSI/ISA-TR61804-4 (104.00.02)-2007 Copyright 2007 ISA. All rights reserved. FUNCTION BLOCKS (FB) FOR PROCESS C

30、ONTROL Part 4: EDD interoperability guideline 1 Scope This part of IEC 61804 is a guideline to support EDD interoperability.This Technical Report is intended to ensure that field device developers use the EDDL constructs consistently and that the EDD applications have the same interpretations of the

31、 EDD. It supplements the EDDL specification to promote EDDL application interoperability and improve EDD portability between EDDL applications. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cit

32、ed applies. For undated references, the latest edition of the referenced document (including any amendments) applies. IEC 60050-351, International Electrotechnical Vocabulary (IEV) Part 351: Automatic control IEC 61804-2:2006, Function blocks (FB) for process control Part 2: Specification of FB conc

33、ept IEC 61804-3:2006 Function blocks (FB) for process control Part 3: Electronic Device Description Language (EDDL) ISO/IEC 15948:2004, Information technology Computer graphics and image processing Portable Network Graphics (PNG) Functional specification 3 Terms, definitions, abbreviated terms and a

34、cronyms 3.1 Terms and definitions For the purposes of this document, some of the terms and definitions in IEC 60050-351, as well as the following, some of which have been compiled from the referenced documents, apply. 3.1.1 EDD developer individual or team that develops an EDD 3.1.2 EDD application

35、software or programmes utilizing the EDD to guide the operation of the application NOTE These applications include configuration tools, calibrators, instrument management packages, and instrument simulators 3.1.3 end user individual using the field device and/or the EDDL application ANSI/ISA-TR61804

36、-4 (104.00.02)-2007 14 Copyright 2007 ISA. All rights reserved. 3.2 Abbreviated terms and acronyms CP Communication Profile CPF Communication Profile Family EDD Electronic Device Description. A platform and application-independent model or description of a field device written using EDDL. An EDD des

37、cribes the properties, standard procedures and status associated with a device. EDDL Electronic Device Description Language FF Fieldbus Foundation; see www.fieldbus.org HCF HARTCommunication Foundation; see www.hartcomm.org OPC Open connectivity; OPC Foundation; see www.opcfoundation.org PC Personal

38、 computer PNO PROFIBUS Nutzerorganisation e.V.; see 4 User interface support 4.1 Overview Most EDD applications can be characterized as either a PC application or a hand-held application. Due to the relatively small screen of a hand-held device, hand-held applications can only display a small amoun

39、t of information at any given time. On the other hand, PC applications can provide a much more beneficial user interface, largely due to their larger screen size. To support the capabilities of PC applications, the MENU construct has been extended in IEC 61804-3 compared to IEC 61804-2. Due to the d

40、ifferences in the user interfaces of PC applications and hand-held applications, it is expected that many devices will define two MENU hierarchies one for hand-held applications and the other for PC applications. Some MENUs may be used in both hierarchies. Therefore, the entire hierarchy need not be

41、 specified twice. Different menu structures for different classes of applications are possible. This guideline may be used to create menu structures in an EDD that are interpreted by applications in an unambiguous way. To promote interoperability across applications, it is highly recommended that al

42、l EDD applications follow this guideline. 4.2 Menu conventions for applications There are existing solutions for hand-held application menus and these solutions can be used. This technical report does not provide specific conventions for hand-held applications. 4.3 Menu conventions for PC-based appl

43、ications 4.3.1 Overview EDD applications use special menus in the EDDs to show the user interface of the device. Such menus are defined for diagnostic, process variables, device features, and offline configuration. Defined identifiers are defined for the different root menus. Other submenus can be u

44、nderneath these root menus. 4.3.2 Diagnostic The diagnostic menu includes views that show the device state, detailed diagnostic information and may include graphical views that show, for example, a valve signature. 15 ANSI/ISA-TR61804-4 (104.00.02)-2007 Copyright 2007 ISA. All rights reserved. 4.3.3

45、 Process variables The process variable menu includes views that show process measurements and set points with their quality and important information for process operators, for example, ranges. 4.3.4 Device features The device feature menu includes features for device support. These features can be

46、 split into process-related and device-specific features. This structure is not required if the number of features is too small for splitting. Submenus that represent any structuring are allowed on the device feature menu. In case of such submenus, the menus that are underneath can be split into pro

47、cess-related and device-specific features. 4.3.5 Offline configuring This menu hierarchy includes parameters, variables, and methods for offline configuration. It contains, in particular, all of the application-specific parameters of the device and may also contain important read-only and writeable

48、variables. For more information about application-specific parameters, see 4.4. The menu can have offline methods, for example, configuration assistants. 4.3.6 Overview defined identifiers Table 1 lists defined menu identifiers. Table 1 List of defined menu identifiers Menu Identifier Short descript

49、ion diagnostic_root_menu Diagnostic view process_variables_root_menu Process variable views device_root_menu Device feature views offline_root_menu Menu hierarchy for offline configuration 4.3.7 Example of EDD menu structure This is an example of additional menus that can be added to an EDD for PC applications. These menus are additional to the existing menus for the applications. This example is HART-specific. Examples for Foundation Fieldbus1and PROFIBUS2would be very similar. MENU diagnostic_root_menu