ISO IEC IEEE 21451-1-2010 ISO IEC IEEE Standard for Information technology - Smart transducer interface for sensors and actuators - Part 1 Network Capable Appli.pdf

1、 Reference number ISO/IEC/IEEE 21451-1:2010(E) IEEE 2000INTERNATIONAL STANDARD ISO/IEC/ IEEE 21451-1 First edition 2010-05-15 Information technology Smart transducer interface for sensors and actuators Part 1: Network Capable Application Processor (NCAP) information model Technologies de linformatio

2、n Interface de transducteurs intelligente pour capteurs et actuateurs Partie 1: Modle dinformation de processeur dapplication utilisable en rseau (NCAP) ISO/IEC/IEEE 21451-1:2010(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may

3、 be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat, the

4、IEC Central Office and IEEE do not accept any liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Ever

5、y care has been taken to ensure that the file is suitable for use by ISO member bodies and IEEE members. In the unlikely event that a problem relating to it is found, please inform the ISO Central Secretariat or IEEE at the address given below. COPYRIGHT PROTECTED DOCUMENT IEEE 2000 All rights reser

6、ved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO or IEEE at the respective address below. ISO copyright office Institut

7、e of Electrical and Electronics Engineers, Inc. Case postale 56 CH-1211 Geneva 20 3 Park Avenue, New York NY 10016-5997, USA Tel. + 41 22 749 01 11 E-mail stds.iprieee.org Fax + 41 22 749 09 47 Web www.ieee.org E-mail copyrightiso.org Web www.iso.org ISO version published 2010 Published in Switzerla

8、nd ii IEEE 2000 All rights reservedISO/IEC/IEEE 21451-1:2010(E) IEEE 2000 All rights reserved iiiForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that a

9、re members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other internatio

10、nal organizations, governmental and non- governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. IEEE Standards documents are developed within the IEEE Societies and the St

11、andards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National Standards Institute, which brings together volunteers representing varied viewpoints and interests t

12、o achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the ac

13、curacy of any of the information contained in its standards. The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires ap

14、proval by at least 75 % of the national bodies casting a vote. Attention is called to the possibility that implementation of this standard may require the use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity o

15、f any patent rights in connection therewith. ISO/IEEE is not responsible for identifying essential patents or patent claims for which a license may be required, for conducting inquiries into the legal validity or scope of patents or patent claims or determining whether any licensing terms or conditi

16、ons provided in connection with submission of a Letter of Assurance or a Patent Statement and Licensing Declaration Form, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that determination of the validity of any patent rights,

17、 and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from ISO or the IEEE Standards Association. ISO/IEC/IEEE 21451-1 was prepared by the Technical Committee on Sensor Technology of the IEEE Instrumentation and Measurement Society of

18、 the IEEE (as IEEE Std 1451.1-1999). It was adopted by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 31, Automatic identification and data capture techniques, in parallel with its approval by the ISO/IEC national bodies, under the “fast-track procedure” defined in

19、the Partner Standards Development Organization cooperation agreement between ISO and IEEE. IEEE is responsible for the maintenance of this document with participation and input from ISO/IEC national bodies. ISO/IEC/IEEE 21451-1:2010(E) iv IEEE 2000 All rights reserved(blank page) ISO/IEC/IEEE 21451-

20、1:2010(E) IEEE 2000 All rights reserved vThe Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright 2000 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 18 April 2000. Printed in the United States of

21、 America. Print: ISBN 0-7381-1767-6 SH94767 PDF: ISBN 0-7381-1768-4 SS94767 No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. IEEE Std 1451.1-1999 IEEE Standard for a Smart Transducer Inte

22、rface for Sensors and Actuators Network Capable Application Processor (NCAP) Information Model Sponsor TC-9 Committee on Sensor Technology of the IEEE Instrumentation and Measurement Society Approved 26 June 1999 IEEE-SA Standards Board Abstract: This standard defines an object model with a network-

23、neutral interface for connecting processors to communication networks, sensors, and actuators. The object model containing blocks, services, and components specifies interactions with sensors and actuators and forms the basis for implementing application code executing in the processor. Keywords: ac

24、tuators, communication network, object model, sensors ISO/IEC/IEEE 21451-1:2010(E) vi IEEE 2000 All rights reservedIEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. Members of the co

25、mmittees serve voluntarily and without compensation. They are not necessarily members of the Institute. The standards developed within IEEE represent a consensus of the broad expertise on the subject within the Institute as well as those activities outside of IEEE that have expressed an interest in

26、participating in the development of the standard. Use of an IEEE Standard is wholly voluntary. The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the IEEE Standard. Fur

27、thermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the standard. Every IEEE Standard is subjected to review at least every ve years for revision or reafrma

28、tion. When a document is more than ve years old and has not been reaf rmed, it is reasonable to conclude that its contents, although still of some value, do not wholly reect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE Standard

29、. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership afliation with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Interpretations: Occasionally questio

30、ns may arise regarding the meaning of portions of standards as they relate to specic applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standards represent a consensus of all concerned i

31、nterests, it is important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason, IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant response to interpretation requests except in those

32、 cases where the matter has previously received formal consideration. Comments on standards and requests for interpretations should be addressed to: Secretary, IEEE-SA Standards Board 445 Hoes Lane P.O. Box 1331 Piscataway, NJ 08855-1331 USA IEEE is the sole entity that may authorize the use of cert

33、ication marks, trademarks, or other designations to indicate compliance with the materials set forth herein. Authorization to photocopy portions of any individual standard for internal or personal use is granted by the Institute of Electrical and Electronics Engineers, Inc., provided that the approp

34、riate fee is paid to Copyright Clearance Center. To arrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; (978) 750-8400. Permission to photocopy portions of any individual standard for educational classroom use

35、can also be obtained through the Copyright Clearance Center. Note: Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity o

36、f any patent rights in connection therewith. The IEEE shall not be responsible for identifying patents for which a license may be required by an IEEE standard or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention.ISO/IEC/IEEE 21451-1:2010(E)

37、IEEE 2000 All rights reserved viiIntroduction This introduction is not part of IEEE Std 1451.1-1999, IEEE Standard for a Smart Transducer Interface for Sensors and ActuatorsNetwork Capable Application Processor (NCAP) Information Model. The objective of the IEEE/NIST Working Group on transducer inte

38、rface standards is to utilize existing control networking technology and develop standardized connection methods for Smart Transducers to control networks. Little or no changes would be required to use different methods of analog-to-digital (A/D) conversion, different microprocessors, or different n

39、etwork protocols and transceivers. This objective is achieved through the denition of a common object model for the components of a Networked Smart Transducer, together with interface specications to these components. The Networked Smart Transducer model shows two key views of a smart transducer: Ph

40、ysical view Logical view Physical view The rst view shows the physical components of the system. This view is indicated by components drawn in solid lines in Figure 1. Transducer Firmware Network Network Hardware Network Protocol Network Abstraction Logical Interface Specification Transducer Abstrac

41、tion Logical Interface Specification I/O Interface Hardware Transducer (sensors & actuators) Transducer Hardware Interface Specification (e.g. IEEE1451.2) IEEE1451-000 Application Software: Function Blocks Components Services Logical Interface to NCAP support Transducer Blocks Ports NCAP Block Opera

42、ting System Firmware Server Object Dispatch Microprocessor Hardware NCAP Figure 1Networked Smart Transducer modelISO/IEC/IEEE 21451-1:2010(E) viii IEEE 2000 All rights reservedFigure 1 shows a model composed of sensors and actuators connected to form a transducer. The transducer is connected over an

43、 interface to a microprocessor or controller that is in turn interfaced to the network. The Hardware Interface Specication between the sensor/actuator and the rest of the device hardware, known as the network capable application processor (NCAP), is indicated by the rightmost thick, dashed line in t

44、he gure. A typical speci cation is described in the companion standard IEEE Std 1451.2-1997. The NCAP hardware consists of the microprocessor and its supporting circuitry as well as hardware implementing the physical layer of the attached network and the input/output (I/O) interface to the transduce

45、r, as shown in Figure 1. Logical view The second view is the logical view of the system and is indicated by components shown in dotted lines in Figure 1. The logical components may be grouped into application and support components. The support components are the operating system, the network protoc

46、ol, and transducer rmware components shown. The operating system provides an interface to applications, indicated by the dashed line labeled “Logical Interface to NCAP support.” A second logical interface, labeled “Network Abstraction Logical Interface Specication,” consists of Port and Server Objec

47、t Dispatch components dened in this standard. This interface provides an abstraction to hide communication details specic to a given network within a small set of communication methods. The details of this interface are dened by this standard. The third logical interface, labeled “Transducer Abstrac

48、tion Logical Interface Specication” performs the same abstraction function for the specics of the transducer I/O hardware and rmware. In effect, this inter- face makes all such transducer interfaces look like I/O drivers. The details of this interface are dened by this standard. Applications are mod

49、eled as Function Blocks in combination with Components and Services. The NCAP block provides application organization and support for the other blocks. All of these Blocks, Components, and Services are dened by this standard. These interfaces are optional in the sense that not all must be exposed in an implementation. NOTEIf support for interoperable transducers is not required, it is permissible to not use the IEEE1451.2 Interface Specication, or a similar transducer