1、 IEEE Std 1451.2-1997IEEE Std 1451.2-1997IEEE Standard for a Smart Transducer Interface for Sensors and ActuatorsTransducer to Microprocessor Communication Protocols and Transducer Electronic Data Sheet (TEDS) FormatsIEEE Instrumentation and Measurement SocietySponsored by TC-9, Committee on Sensor
2、Technology25 Sept. 1998 SH94566To order IEEE standardsCall 1. 800. 678. IEEE (4333) in the US and Canada. Outside of the US and Canada:1. 732. 981. 0600To order by fax:1. 732. 981. 9667IEEE business hours: 8 a.m.4:30 p.m. (EST)For on-line access to IEEE standards informationVia the World Wide Web:ht
3、tp:/standards.ieee.org/Via ftp:stdsbbs.ieee.orgISBN 1-55937-963-4The Institute of Electrical and Electronics Engineers, Inc.345 East 47th Street, New York, NY 10017-2394, USACopyright 1998 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 1998. Printed in t
4、he United States of America.ISBN 1-55937-963-4No 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.2-1997IEEE Standard for a Smart Transducer Interface for Sensors and ActuatorsT
5、ransducer to Microprocessor Communication Protocols and Transducer Electronic Data Sheet (TEDS) FormatsSponsor TC-9, Committee on Sensor Technologyof the IEEE Instrumentation and Measurement SocietyApproved 16 September 1997IEEE Standards BoardAbstract:A digital interface for connecting transducers
6、to microprocessors is dened. A TEDS andits data formats are described. An electrical interface, read and write logic functions to access theTEDS and a wide variety of transducers are dened. This standard does not specify signal condi-tioning, signal conversion, or how the TEDS data is used in applic
7、ations.Keywords:communication protocol, digital interface, microprocessor, NCAP, sensor interface,smart actuator, smart sensor, smart sensor interface, smart transducer, smart transducer interface,STIM, TEDS, 1451IEEE Standardsdocuments are developed within the IEEE Societies and the Standards Coord
8、inat-ing Committees of the IEEE Standards Board. Members of the committees serve voluntarily andwithout compensation. They are not necessarily members of the Institute. The standards developedwithin IEEE represent a consensus of the broad expertise on the subject within the Institute as wellas those
9、 activities outside of IEEE that have expressed an interest in participating in the develop-ment of the standard.Use of an IEEE Standard is wholly voluntary. The existence of an IEEE Standard does not implythat there are no other ways to produce, test, measure, purchase, market, or provide other goo
10、ds andservices related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at thetime a standard is approved and issued is subject to change brought about through developments inthe state of the art and comments received from users of the standard. Every IEEE Standard is sub-ject
11、ed to review at least every ve years for revision or reafrmation. When a document is morethan ve years old and has not been reafrmed, 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 tocheck to determin
12、e that they have the latest edition of any IEEE Standard.Comments for revision of IEEE Standards are welcome from any interested party, regardless ofmembership afliation with IEEE. Suggestions for changes in documents should be in the form of aproposed change of text, together with appropriate suppo
13、rting comments.Interpretations: Occasionally questions may arise regarding the meaning of portions of standards asthey relate to specic applications. When the need for interpretations is brought to the attention ofIEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE
14、Standards rep-resent a consensus of all concerned interests, it is important to ensure that any interpretation hasalso received the concurrence of a balance of interests. For this reason, IEEE and the members of itssocieties and Standards Coordinating Committees are not able to provide an instant re
15、sponse tointerpretation requests except in those cases where the matter has previously received formalconsideration. Comments on standards and requests for interpretations should be addressed to:Secretary, IEEE Standards Board445 Hoes LaneP.O. Box 1331Piscataway, NJ 08855-1331USAAuthorization to pho
16、tocopy portions of any individual standard for internal or personal use isgranted by the Institute of Electrical and Electronics Engineers, Inc., provided that the appropriatefee is paid to Copyright Clearance Center. To arrange for payment of licensing fee, please contactCopyright Clearance Center,
17、 Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA;(978) 750-8400. Permission to photocopy portions of any individual standard for educational class-room use can also be obtained through the Copyright Clearance Center.Note: Attention is called to the possibility that implementation of this
18、 standard mayrequire use of subject matter covered by patent rights. By publication of this standard,no position is taken with respect to the existence or validity of any patent rights inconnection therewith. The IEEE shall not be responsible for identifying patents forwhich a license may be require
19、d by an IEEE standard or for conducting inquiries intothe legal validity or scope of those patents that are brought to its attention.Copyright 1998 IEEE. All rights reserved.iiiIntroductionThis introduction is not part of IEEE Std 1451.2-1997, IEEE Standard for a Smart Transducer Interface for Senso
20、rs andActuatorsTransducer to Microprocessor Communications Protocols and Transducer Electronic Data Sheet (TEDS)Formats.The main objectives of this standard are to: Enable plug and play at the transducer (sensor or actuator) level by providing a common communica-tion interface for transducers. Enabl
21、e and simplify the creation of networked smart transducers. Facilitate the support of multiple networks.The existing fragmented sensor market is seeking ways to build low-cost, networked smart sensors. Manysensor network or eldbus implementations are currently available, each with its own strengths
22、and weak-nesses for a specic application class. Interfacing transducers to all these control networks and supportingthe wide variety of protocols represents a signicant and costly effort to transducer manufacturers. A univer-sally-accepted transducer interface standard would not only allow for the d
23、evelopment of smart sensors andactuators, it could also lead to lower development costs. Therefore, the objective of this project is not to pro-pose another control network, but to develop a smart transducer interface standard that will isolate the choiceof transducers from the choice of networks. T
24、his would relieve the burden from the manufacturer of support-ing a cross product of sensors versus networks, and would help to preserve the users investment if itbecomes necessary to migrate to a different network standard.There is currently no dened common digital communication interface standard
25、between transducers andnetwork capable application processors (NCAPs). Each transducer manufacturer builds its own interface.Consequently, transducer manufacturers cannot afford to support all of the control networks for which theirproducts may be suited. It was concluded at a series of ve transduce
26、r interface workshops held between1994 and 1995 that a common transducer communication interface standard be proposed. This commoninterface would allow the transducer manufacturers to more easily support multiple control networks.This standard will simplify the development of networked transducers b
27、y dening hardware and softwareblocks that do not depend on specic control networks. This project has developed a standard hardwareinterface to connect a smart transducer interface module (STIM) to an NCAP. While the project does notinclude specications for signal conditioning or data conversion, it
28、does provide a mechanism for specifyingthe combination of transducer, signal conditioning, and signal conversion to the rest of the system. Thismechanism is the transducer electronic data sheet (TEDS). The working group has dened a TEDS whichsupports a wide variety of transducers as well as a digita
29、l interface to access the TEDS, read sensors, and setactuators. This allows transducer manufacturers competitive differentiation in areas of quality, feature setand cost, and at the same time affords the opportunity to design to a common interface which can be used ina wide variety of applications.T
30、he TEDS, which provides for self-identifying transducers, is at the core of this effort. The TEDS containselds that fully describe the type, operation, and attributes of one or more transducers. By requiring that theTEDS be physically associated with the transducer, the resulting hardware partition
31、encapsulates the mea-surement aspects in a STIM on one side of the digital interface, and the application related aspects on theNCAP on the other side. In addition to control networks, STIMs can be used with microprocessors in a vari-ety of applications such as portable instruments and data acquisit
32、ion cards.Data output by the STIM may be in integer, single precision real, or double precision real formats. The datais passed to the NCAP and from the NCAP to the rest of the system. Further processing of this data may takeplace both in the NCAP and in other processors in the larger system. Throug
33、hout this standard it is assumed,but not required, that all processing will be performed on data in a single- or double-precision real format.ivCopyright 1998 IEEE. All rights reserved.All elds in the TEDS are specied based on the assumption that, unless specically stated to the contrary,all data wi
34、ll be converted to single- or double-precision real before any processing is performed.This standard provides areas that are open to industry. It should be noted that any use of these areas com-promises the plug and play potential of NCAPs and STIMs.The IEEE 1451.2 transducer to microprocessor inter
35、face is compatible with the P1451.11information modelstandard. The two parts form a standard interface for networked smart sensors and actuators.At the time this standard was approved, the Transducer to Microprocessor Communication working grouphad the following membership:Stan P. Woods,ChairLarry M
36、alchodi,Vice ChairEdwin Vivian El-Kareh,Secretary and EditorOther individuals who contributed to this standard are:The following persons were on the balloting committee:1Numbers preceded by P are IEEE authorized standards projects that were not approved by the IEEE Standards Board at the time thispu
37、blication went to press. For information about obtaining drafts, contact the IEEE.Wayne CatlinAlec Dara-AbramsLee EcclesFernando Gen-KuongRob A. HamiltonRobert JohnsonJohn LawsonKang LeeTremont MiaoDavid MoberlyJames O. MooreDavid E. RasmussenBob StricklinLee BarfordJanusz Bryzek Steven ChenMilton C
38、ramJeff CranmerJohn C. EidsonRobert GavinMike Geipel Ronald S. GyurcsikBruce HamiltonJohn Houldsworth Kenn JennycLyle D. JohnsenNorm LeComteMichael MattesPradip MadanJohn ReidyRod SinksHans SitteDale SoggeDavid R. SmithWilliam J. AlexanderJohn BakerThomas J. BatkoDan CarnahanL. Wayne CatlinMichael G
39、. ClarkJohn C. ColeRodney CummingsWalter CzarnockiRichard T. DAquanniCyrilla Jane DalstraRichard DeMarsMario D. DianoraRobert DolinJoe DrakeJoseph E. DryerDavid P. EckelDavid FergusonJoe FieldDavid M. FoyeRandy FrankCarl B. FreidhoffMike GeipelPatrick S. GoniaRoss S. GottliebMaris GraubeAlfonso C. G
40、uativaTimothy J. GundrumRonald GyurcsikJames A. HammervoldDavid HowarthMutsuya IiDaniel LaBonteKang LeeJohn S. LeferNadim MalufVinod MaudgalMurray NicolsonYukio NishikawaJ. Mark NoworolskiAdam PawlikiewiczThomas L. PhinneyJosep SamitierDale ShoupRajiv K. SinghGrant SmithSamuel M. SmithBob StricklinJ
41、oseph J. SuterArie van RhijnGertjan Van SprakelaarDaniel R. WeberThomas E. WheatleyKeith WitneyStan WoodsJames XuCopyright 1998 IEEE. All rights reserved.vWhen the IEEE Standards Board approved this standard on 16 September 1997, it had the followingmembership:Donald C. Loughry,ChairRichard J. Holle
42、man,Vice ChairAndrew G. Salem,Secretary*Member EmeritusAlso included are the following nonvoting IEEE Standards Board liaisons:Satish K. AggarwalAlan H. CooksonNoelle D. HumenickIEEE Standards Project EditorClyde R. CampStephen L. DiamondHarold E. EpsteinDonald C. FleckensteinJay Forster*Thomas F. G
43、arrityDonald N. HeirmanJim IsaakBen C. JohnsonLowell JohnsonRobert KennellyE. G. Al KienerJoseph L. Koepnger*Stephen R. LambertLawrence V. McCallL. Bruce McClungMarco W. MigliaroLouis-Franois PauGerald H. PetersonJohn W. PopeJose R. RamosRonald H. ReimerIngo RschJohn S. RyanChee Kiow TanHoward L. Wo
44、lfmanviCopyright 1998 IEEE. All rights reserved.Contents1. Overview 11.1 Scope 21.2 Purpose. 21.3 Conformance 22. References 33. Definitions, acronyms, and abbreviations 53.1 Definitions 53.2 Acronyms and abbreviations 83.3 Data types. 94. Smart transducer functional specification 174.1 Foundation .
45、 174.2 Transducer channel types. 174.3 Functions 194.4 Addressing . 194.5 Interface data transport 234.6 Triggering 264.7 Control . 414.8 Status 414.9 Interrupt masks. 464.10 Interrupts 474.11 Hot-swap capability . 474.12 Channel groupings . 474.13 STIM version . 485. Transducer Electronic Data Shee
46、t (TEDS) specification. 495.1 Meta-TEDS data block 495.2 Channel TEDS Data Block 595.3 Calibration TEDS data block. 715.4 Meta-identification TEDS data block 805.5 Channel Identification TEDS data block . 855.6 Calibration Identification TEDS data block 895.7 End-Users Application-Specific TEDS data
47、 block 925.8 Generic Extension TEDS data block . 946. Transducer Independent Interface (TII) specification . 976.1 Principles 976.2 Line definition 996.3 Protocols 996.4 Timing 1046.5 Electrical specifications . 1096.6 Physical specification. 113Annex A (informative) Bibliography . 114Copyright 1998
48、 IEEE. All rights reserved.1IEEE Standard for a Smart Transducer Interface for Sensors and ActuatorsTransducer to Microprocessor Communication Protocols and Transducer Electronic Data Sheet (TEDS) Formats1. OverviewThis standard introduces the concept of a Smart Transducer Interface Module (STIM). A
49、 STIM can range incomplexity from a single sensor or actuator to many channels of transducers (sensors or actuators). Seventypes of transducer channels are recognized by this standard and provision has been made for other types tobe added. The transducer channel types are specied in 4.2.A transducer channel is denoted smart in this context because of the following three features: It is described by a machine-readable, Transducer Electronic Data Sheet (TEDS). The control and data associated with the channel are digital. Triggerin
