ANSI IEEE 1451.3-2003 Standard for a Smart Transducer Interface for Sensors and ActuatorsDigital Communication and Transducer Electronic Data Sheet (TEDS) Formats for Distributed M.pdf

《ANSI IEEE 1451.3-2003 Standard for a Smart Transducer Interface for Sensors and ActuatorsDigital Communication and Transducer Electronic Data Sheet (TEDS) Formats for Distributed M.pdf》由会员分享，可在线阅读，更多相关《ANSI IEEE 1451.3-2003 Standard for a Smart Transducer Interface for Sensors and ActuatorsDigital Communication and Transducer Electronic Data Sheet (TEDS) Formats for Distributed M.pdf（186页珍藏版）》请在麦多课文档分享上搜索。

1、IEEE Std 1451.3-2003IEEE Standards1451.3TMIEEE Standard for a SmartTransducer Interface for Sensors andActuatorsDigital Communicationand Transducer Electronic Data Sheet(TEDS) Formats for DistributedMultidrop SystemsPublished by The Institute of Electrical and Electronics Engineers, Inc.3 Park Avenu

2、e, New York, NY 10016-5997, USA31 March 2004IEEE Instrumentation and Measurement SocietySponsored by theTechnical Committee 9 on Sensor Technology (TC-9)IEEE StandardsPrint: SH95174PDF: SS95174Recognized as an IEEE Std 1451.3TM-2003American National Standard (ANSI)IEEE Standard for a SmartTransducer

3、 Interface for Sensors andActuatorsDigital Communicationand Transducer Electronic DataSheet (TEDS) Formats for DistributedMultidrop SystemsSponsorTC-9 on Sensor Technology of theIEEE Instrumentation and Measurement Societyin cooperation with theNational Institute of Standards and Technology (NIST)Un

4、ited States Department of CommerceApproved 11 September 2003IEEE-SA Standards BoardApproved 29 December 2003American National Standards InstituteAbstract: A digital interface for connecting multiple physically separated transducers to a singleprocessor over a single pair of wires. The interface can

5、support both asynchronous andisochronous data transfers. Several Transducer Electronic Data Sheets (TEDS) and their dataformats are described. An electrical interface, channel identification protocols, time synchronizationprotocols, read and write logic functions to access the TEDS, and transducers

6、with a wide variety ofattributes are defined. This standard does not specify signal conditioning, signal conversion, or howan application uses the TEDS data.Keywords: 1451, communication protocol, digital interface, event sensor, microprocessor,NCAP, plug and play, sensor interface, smart actuator,

7、smart sensor, smart sensor interface,smart transducer interface, TBIM, TEDSThe Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USACopyright C223 2004 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 31 March 2

8、004. Printed in the United States of America.IEEE is a registered trademark in the U.S. Patent 1 978 750 8400. Permission to photocopy portions of any individual standard foreducational classroom use can also be obtained through the Copyright Clearance Center.IntroductionThis introduction is not par

9、t of IEEE Std 1451.3-2003, IEEE Standard for a Smart Transducer Interface forSensors and ActuatorsDigital Communication and Transducer Electronic Data Sheet (TEDS) Formats forDistributed Multidrop Systems.The main objectives of this standard are to: Enable plug and play at the transducer level by pr

10、oviding a common communication interfacefor transducers which are physically separated Enable and simplify the creation of groups of networked smart transducers Facilitate the support of multiple networksThe existing fragmented sensor market is seeking ways to build low-cost, networked smart sensors

11、.Many sensor network or fieldbus implementations are currently available, each with its own strengthsand weaknesses for a specific application class. Interfacing transducers to all these control networksand supporting the wide variety of protocols represents a significant and costly eort to transduc

12、ermanufacturers. A universally-accepted transducer interface standard would not only allow for thedevelopment of smart sensors and actuators, it could also lead to lower development costs. Therefore,the goal of this standard is not to propose another control network, but to define a smart transducer

13、interface that will isolate the choice of transducers from the choice of networks. This would relieve theburden from the manufacturer of supporting a cross product of sensors versus networks, and wouldhelp to preserve the users investment if it becomes necessary to migrate to a dierent networkstanda

14、rd.There is currently only the IEEE Std 1451.2TM-1997acommon digital communication interfacestandard between transducers and Network Capable Application Processors (NCAPs). IEEE Std1451.2-1997 supports transducers that can be physically included within one housing, but it does notsupport transducers

15、 that are physically separated but need to make their network connection througha single NCAP. IEEE Std 1451.2-1997 does, however, provide a comprehensive set of TEDSs that arethe basis for the TEDS described in this document. Care has been taken throughout the developmentof this standard to modify

16、the IEEE Std 1451.2-1997 TEDS only as required to meet dierentrequirements of the dierent environment and to provide for a translation path between the IEEE Std1451.3-2003 TEDS and the IEEE Std 1451.2-1997 TEDS.IEEE Std 1451.3-2003 utilizes the techniques designed to implement networking in the home

17、 byinterconnection devices on the telephone lines. For IEEE Std 1451.3-2003, a single pair of conductorswill be used to provide the following functions: synchronized data acquisition for an array of transducers communicating with an array of Transducer Bus Interface Modules (TBIM) providing power fo

18、r operation of transducers on the bus and their associated electronicsTransducers built per this standard can be plugged into an IEEE Std 1451.3-2003 compatible systemand be used without having to add special drivers, profiles or make any other changes to the system.The IEEE Std 1451.3-2003 TEDS pro

19、vides for self-identifying transducers. The TEDS contains fieldsthat fully describe the type, operation, and attributes of one or more transducers (sensors oractuators). By having the TEDS associated with the transducer and module containing the transducer,the resulting hardware partition encapsulat

20、es the measurement aspects to a module. The applicationrelated aspects of the measurement are on the bus controller or NCAP and do not become a concernfor the transducer manufacturer.iv Copyright C223 2004 IEEE. All rights reserved.aInformation on references can be found in Clause 2.Data output over

21、 the bus may be in integer; single precision real or double precision real formats. Thedata is passed to the bus controller and from the bus controller to the rest of the system. Furtherprocessing of this data may take place both in the bus controller and in other processors in the largersystem. Thr

22、oughout this document it is assumed, but not required, that all processing will beperformed on data in a single or double precision real format. All fields in the TEDS are specifiedbased on the assumption that, unless specifically stated to the contrary, all data will be converted tosingle or double

23、 precision real before any processing is performed.This standard provides areas that are open to manufacturers. It should be noted that any use ofthese areas compromises the plug and play potential of bus controllers and TBIMs.The IEEE Std 1451.3-2003 transducer interface is adaptable to the IEEE St

24、d 1451.2-1997 interface andcompatible with the IEEE Std 1451.1TM-1999 information model standard.ParticipantsAt the time this standard was completed, the Distributed Multidrop Systems Working Group had thefollowing membership:Larry A. Malchodi, ChairStephen Smith, Vice ChairDaniel Maxwell, Secretary

25、Lee Eccles, EditorJrgen Bkke Alice Law Jim ReadL. Wayne Catlin Kang Lee Andrew SegalFernando GenKuong Roberto Lenarduzzi Robert SinclairRobert Johnson Torben Licht Mark SlackCharles Jones Allan Owen Charles SummeyJames Lathrop David Perrussel Rich ValdeOther individuals who have contributed to this

26、standard are as follows:Dennis Albertsen David Goetzinger Paul MoffittGregory Balchin Richard Hambly Mike MooreArati Baruah Rob Hammett Chao PangThurston Brooks James Hooper Ray RitmillerMark Buckner Paul Hufnagel Mark SchieferRussell Dominique Richard Jones T. J. ShahabiCraig Evensen Rodney Juelfs

27、Bryan TracyBrett Gidge Eric Lange Jay ZemelCarlos Lopez-ReynaThe following members of the balloting committee voted on this standard. Balloters may have votedfor approval, disapproval, or abstention.Martin Baur Richard Hambly Gary MichelJacob Ben Ary Charles Jones Mark I. SchieferL. Wayne Catlin Jam

28、es Kemerling Robert SinclairKeith Chow Kang Lee Stephen SmithGuru Dutt Dhingra Gregory Luri Steven TildenFernando GenKuong Tremont Miao Stephen C. WebbCopyright C223 2004 IEEE. All rights reserved. vWhen the IEEE-SA Standards Board approved this recommended practice on 11 September 2003, ithad the f

29、ollowing membership:Don Wright, ChairHoward M. Frazier, Vice ChairJudith Gorman, SecretaryH. Stephen Berger Donald N. Heirman Daleep C. MohlaJoseph A. Bruder Laura Hitchcock William J. MoylanBob Davis Richard H. Hulett Paul NikolichRichard DeBlasio Anant Kumar Jain Gray S. RobinsonJulian Forster* Lo

30、well G. Johnson Malcolm V. ThadenToshio Fukuda Joseph L. Koepfinger* Geoffrey O. ThompsonArnold M. Greenspan Thomas J. McGreen Doug ToppingRaymond Hapeman Steve M. Mills Howard L. Wolfman*Member EmeritusAlso included are the following nonvoting IEEE-SA Standards Board liaisons:Alan Cookson, NIST Rep

31、resentativeSatish K. Aggarwal, NRC RepresentativeSavoula AmanatidisIEEE Standards Managing Editorvi Copyright C223 2004 IEEE. All rights reserved.Contents1. Overview.11.1 Scope21.2 Purpose 21.3 Conformance22. References 33. Definitions, acronyms, and abbreviations53.1 Acronyms and abbreviations.53.2

32、 Definitions64. Data types94.1 Unsigned octet integer for counting94.2 Unsigned octet integer for enumeration94.3 Unsigned 16-bit integer for counting.104.4 Unsigned 16-bit integer for field length.104.5 Signed 32-bit integer104.6 Unsigned 32-bit integer for counting.104.7 Unsigned 32-bit integer fo

33、r field length.104.8 Single precision real.114.9 Double precision real.114.10 String114.11 Physical units .114.12 Universal unique identification124.13 Arbitrary octet array134.14 Time-of-day145. Smart transducer functional specification145.1 Plug and play capability 155.2 Addresses .155.3 Common ch

34、aracteristics.165.4 TransducerChannel type descriptions175.5 Embedded TransducerChannels.205.6 TransducerChannel groups21Copyright C223 2004 IEEE. All rights reserved. vii5.7 TransducerChannel proxy215.8 Attributes and operating modes 225.9 Triggering.265.10 Synchronization .295.11 CommunicationsCha

35、nnels305.12 Status .315.13 Service request logic.375.14 Hot-swap capability.386. Commands .386.1 Standard commands 396.2 Manufacturer-defined commands 537. Transducer Electronic Data Sheet (TEDS) specification.537.1 General format for TEDS537.2 Transmission of the TEDS547.3 Meta-TEDS547.4 Transducer

36、Channel TEDS.607.5 Calibration TEDS737.6 Frequency Response TEDS.827.7 Transfer Function TEDS.847.8 Text-based TEDS.907.9 End user application specific TEDS947.10 Commissioning TEDS .947.11 Manufacturer-defined TEDS .957.12 PHY TEDS958. Upper layers of the ISO model (layer 3 through layer 7) .978.1

37、Data transmission order and bit significance978.2 Protocol identifiers.998.3 Datagram protocol998.4 Streaming data protocol1028.5 Trigger protocol.1028.6 Command services protocol 1048.7 Reply protocol.1049. Standard services oered by the Data Link Layer1069.1 Syntax and semantics.106viii Copyright

38、C223 2004 IEEE. All rights reserved.9.2 Streaming mode management services on the TBC.1079.3 Streaming mode protocol services1109.4 Discovery services in the TBC1129.5 Discovery services in the TBIM .1139.6 Transmitter control services .1149.7 Datagram protocol services1159.8 Trigger protocol servic

39、es.1179.9 Delay measurement services .11910. Lower layers of the ISO model (layer 1 and layer 2)12010.1 Data Link Layer protocol specifications12110.2 Data linkLogical Link Control (LLC) sublayer.12410.3 Data linkMAC sublayer12510.4 Physical layer13710.5 Physical specifications.141Annex A (informati

40、ve) Bibliography.147Annex B (normative) XML schema for text-based TEDS148Annex C (informative) Example Meta-Identification TEDS.153Annex D (informative) Example TransducerChannel Identification TEDS154Annex E (informative) Example Calibration Identification TEDS .156Annex F (informative) Example Com

41、mands TEDS157Annex G (informative) Example Location and Title TEDS .160Annex H (informative) Example physical units.162Annex I (informative) TEDS Read and Write protocols169Annex J (informative) Trigger logic configurations.171Copyright C223 2004 IEEE. All rights reserved. ixIEEE Standard for a Smar

42、tTransducer Interface for Sensors andActuatorsDigital Communicationand Transducer Electronic DataSheet (TEDS) Formats for DistributedMultidrop Systems1. OverviewThis standard introduces the concept of a Transducer Bus Interface Module (TBIM) and a TransducerBus Controller (TBC) connected by a transd

43、ucer bus. A TBIM is a module that contains the businterface, signal conditioning, Analog-to-Digital and/or Digital-to-Analog conversion and in manycases the transducer. A TBIM can range in complexity from a single sensor or actuator to unitscontaining many transducers (sensors and actuators). A TBC

44、is the hardware and software in theNetwork Capable Application Processor (NCAP) or host processor that provides the interface to thetransducer bus. The transducer bus provides the communications path between an NCAP or hostprocessor and one or more TBIMs. Three types of transducers are recognized by

45、 this standard. Theyare sensors, event sensors, and actuators.A TransducerChannel is denoted smart in this context because of three features: It is described by a machine-readable, Transducer Electronic Data Sheet (TEDS). The control and data associated with the TransducerChannel are digital. Trigge

46、ring, status, and control are provided to support the proper functioning of theTransducerChannel.A TBC, that may be part of an NCAP or host processor, controls a TBIM by means of a dedicateddigital bus. The bus controller or NCAP mediates between the TBIM and a higher-level digitalnetwork, and may p

47、rovide local intelligence.This standard provides for TBIMs that can be plugged into a system and be used without having toadd special drivers, profiles, or make any other changes to the system. This is referred to as plug andplay operation. The primary features that enable plug and play operation ar

48、e the TEDS and the basiccommand set. A TBIM may be added to or removed from an active transducer bus with no moreCopyright C223 2004 IEEE. All rights reserved. 1than a momentary impact on the data being transferred over the bus. Hot swap is the term used torefer to this feature.This standard is orga

49、nized as follows: Clause 1: Overview provides the scope of this standard.Clause 2: References lists references to other standards and documents that are useful in applyingthis standard. Clause 3: Definitions, acronyms, and abbreviations provides definitions that areeither not found in other standards, or have been modified for use with this standard. Clause 4: Datatypes defines the data types used in the standard. Clause 5: Smart transducer functionalspecification specifies the functions required of a TBIM and of each TransducerChanne