《IEEE-1451.3-2003.pdf》由会员分享,可在线阅读,更多相关《IEEE-1451.3-2003.pdf(185页珍藏版)》请在三一文库上搜索。
1、IEEE Std 1451.3-2003 IEEE Standards 1451.3 TM IEEE Standard for a Smart Transducer Interface for Sensors and ActuatorsDigital Communication and Transducer Electronic Data Sheet (TEDS) Formats for Distributed Multidrop Systems Published by The Institute of Electrical and Electronics Engineers, Inc. 3
2、 Park Avenue, New York, NY 10016-5997, USA 31 March 2004 IEEE Instrumentation and Measurement Society Sponsored by the Technical Committee 9 on Sensor Technology (TC-9) IEEE Standards Print: SH95174 PDF: SS95174 Recognized as anIEEE Std 1451.3TM-2003 American National Standard (ANSI) IEEE Standard f
3、or a Smart Transducer Interface for Sensors and ActuatorsDigital Communication and Transducer Electronic Data Sheet (TEDS) Formats for Distributed Multidrop Systems Sponsor TC-9 on Sensor Technology of the IEEE Instrumentation and Measurement Society in cooperation with the National Institute of Sta
4、ndards and Technology (NIST) United States Department of Commerce Approved 11 September 2003 IEEE-SA Standards Board Approved 29 December 2003 American National Standards Institute Abstract:A digital interface for connecting multiple physically separated transducers to a single processor over a sing
5、le pair of wires. The interface can support both asynchronous and isochronous data transfers. Several Transducer Electronic Data Sheets (TEDS) and their data formats are described. An electrical interface, channel identifi cation protocols, time synchronization protocols, read and write logic functi
6、ons to access the TEDS, and transducers with a wide variety of attributes are defi ned. This standard does not specify signal conditioning, signal conversion, or how an application uses the TEDS data. Keywords:1451, communication protocol, digital interface, event sensor, microprocessor, NCAP, plug
7、and play, sensor interface, smart actuator, smart sensor, smart sensor interface, smart transducer interface, TBIM, TEDS The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright ? 2004 by the Institute of Electrical and Electronics Engineers,
8、Inc. All rights reserved. Published 31 March 2004. 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 for educational classroom use can also be obtained through the Copyright Clearance
9、 Center. Introduction This introduction is not part of IEEE Std 1451.3-2003, IEEE Standard for a Smart Transducer Interface for Sensors and ActuatorsDigital Communication and Transducer Electronic Data Sheet (TEDS) Formats for Distributed Multidrop Systems. The main objectives of this standard are t
10、o: Enable plug and play at the transducer level by providing a common communication interface for transducers which are physically separated Enable and simplify the creation of groups of networked smart transducers Facilitate the support of multiple networks The existing fragmented sensor market is
11、seeking ways to build low-cost, networked smart sensors. Many sensor network or fi eldbus implementations are currently available, each with its own strengths and weaknesses for a specifi c application class. Interfacing transducers to all these control networks and supporting the wide variety of pr
12、otocols represents a signifi cant and costly eff ort to transducer manufacturers. A universally-accepted transducer interface standard would not only allow for the development of smart sensors and actuators, it could also lead to lower development costs. Therefore, the goal of this standard is not t
13、o propose another control network, but to defi ne a smart transducer interface that will isolate the choice of transducers from the choice of networks. This would relieve the burden from the manufacturer of supporting a cross product of sensors versus networks, and would help to preserve the users i
14、nvestment if it becomes necessary to migrate to a diff erent network standard. There is currently only the IEEE Std 1451.2TM-1997acommon digital communication interface standard between transducers and Network Capable Application Processors (NCAPs). IEEE Std 1451.2-1997 supports transducers that can
15、 be physically included within one housing, but it does not support transducers that are physically separated but need to make their network connection through a single NCAP. IEEE Std 1451.2-1997 does, however, provide a comprehensive set of TEDSs that are the basis for the TEDS described in this do
16、cument. Care has been taken throughout the development of this standard to modify the IEEE Std 1451.2-1997 TEDS only as required to meet diff erent requirements of the diff erent environment and to provide for a translation path between the IEEE Std 1451.3-2003 TEDS and the IEEE Std 1451.2-1997 TEDS
17、. IEEE Std 1451.3-2003 utilizes the techniques designed to implement networking in the home by interconnection devices on the telephone lines. For IEEE Std 1451.3-2003, a single pair of conductors will be used to provide the following functions: synchronized data acquisition for an array of transduc
18、ers communicating with an array of Transducer Bus Interface Modules (TBIM) providing power for operation of transducers on the bus and their associated electronics Transducers built per this standard can be plugged into an IEEE Std 1451.3-2003 compatible system and be used without having to add spec
19、ial drivers, profi les or make any other changes to the system. The IEEE Std 1451.3-2003 TEDS provides for self-identifying transducers. The TEDS contains fi elds that fully describe the type, operation, and attributes of one or more transducers (sensors or actuators). By having the TEDS associated
20、with the transducer and module containing the transducer, the resulting hardware partition encapsulates the measurement aspects to a module. The application related aspects of the measurement are on the bus controller or NCAP and do not become a concern for the transducer manufacturer. ivCopyright ?
21、 2004 IEEE. All rights reserved. aInformation on references can be found in Clause 2. Data output over the bus may be in integer; single precision real or double precision real formats. The data is passed to the bus controller and from the bus controller to the rest of the system. Further processing
22、 of this data may take place both in the bus controller and in other processors in the larger system. Throughout this document it is assumed, but not required, that all processing will be performed on data in a single or double precision real format. All fi elds in the TEDS are specifi ed based on t
23、he assumption that, unless specifi cally stated to the contrary, all data will be converted to single or double precision real before any processing is performed. This standard provides areas that are open to manufacturers. It should be noted that any use of these areas compromises the plug and play
24、 potential of bus controllers and TBIMs. The IEEE Std 1451.3-2003 transducer interface is adaptable to the IEEE Std 1451.2-1997 interface and compatible with the IEEE Std 1451.1TM-1999 information model standard. Participants At the time this standard was completed, the Distributed Multidrop Systems
25、 Working Group had the following membership: Larry A. Malchodi, Chair Stephen Smith, Vice Chair Daniel Maxwell, Secretary Lee Eccles, Editor Jrgen BkkeAlice LawJim Read L. Wayne CatlinKang LeeAndrew Segal Fernando GenKuongRoberto LenarduzziRobert Sinclair Robert JohnsonTorben LichtMark Slack Charles
26、 JonesAllan OwenCharles Summey James LathropDavid PerrusselRich Valde Other individuals who have contributed to this standard are as follows: Dennis AlbertsenDavid GoetzingerPaul Moffitt Gregory BalchinRichard HamblyMike Moore Arati BaruahRob HammettChao Pang Thurston BrooksJames HooperRay Ritmiller
27、 Mark BucknerPaul HufnagelMark Schiefer Russell DominiqueRichard JonesT. J. Shahabi Craig EvensenRodney JuelfsBryan Tracy Brett GidgeEric LangeJay Zemel Carlos Lopez-Reyna The following members of the balloting committee voted on this standard. Balloters may have voted for approval, disapproval, or
28、abstention. Martin BaurRichard HamblyGary Michel Jacob Ben AryCharles JonesMark I. Schiefer L. Wayne CatlinJames KemerlingRobert Sinclair Keith ChowKang LeeStephen Smith Guru Dutt DhingraGregory LuriSteven Tilden Fernando GenKuongTremont MiaoStephen C. Webb Copyright ? 2004 IEEE. All rights reserved
29、.v When the IEEE-SA Standards Board approved this recommended practice on 11 September 2003, it had the following membership: Don Wright, Chair Howard M. Frazier, Vice Chair Judith Gorman, Secretary H. Stephen BergerDonald N. HeirmanDaleep C. Mohla Joseph A. BruderLaura HitchcockWilliam J. Moylan Bo
30、b DavisRichard H. HulettPaul Nikolich Richard DeBlasioAnant Kumar JainGray S. Robinson Julian Forster*Lowell G. JohnsonMalcolm V. Thaden Toshio FukudaJoseph L. Koepfinger*Geoffrey O. Thompson Arnold M. GreenspanThomas J. McGreenDoug Topping Raymond HapemanSteve M. MillsHoward L. Wolfman *Member Emer
31、itus Also included are the following nonvoting IEEE-SA Standards Board liaisons: Alan Cookson, NIST Representative Satish K. Aggarwal, NRC Representative Savoula Amanatidis IEEE Standards Managing Editor viCopyright ? 2004 IEEE. All rights reserved. Contents 1.Overview.1 1.1Scope2 1.2Purpose 2 1.3Co
32、nformance2 2.References 3 3. Defi nitions, acronyms, and abbreviations5 3.1Acronyms and abbreviations .5 3.2 Defi nitions6 4.Data types9 4.1Unsigned octet integer for counting 9 4.2Unsigned octet integer for enumeration 9 4.3Unsigned 16-bit integer for counting.10 4.4 Unsigned 16-bit integer for fi
33、eld length.10 4.5Signed 32-bit integer 10 4.6Unsigned 32-bit integer for counting.10 4.7 Unsigned 32-bit integer for fi eld length.10 4.8Single precision real.11 4.9Double precision real.11 4.10String11 4.11Physical units .11 4.12 Universal unique identifi cation12 4.13Arbitrary octet array13 4.14Ti
34、me-of-day14 5. Smart transducer functional specifi cation14 5.1Plug and play capability 15 5.2Addresses .15 5.3Common characteristics.16 5.4TransducerChannel type descriptions17 5.5Embedded TransducerChannels.20 5.6TransducerChannel groups21 Copyright ? 2004 IEEE. All rights reserved.vii 5.7Transduc
35、erChannel proxy21 5.8Attributes and operating modes 22 5.9Triggering.26 5.10Synchronization .29 5.11CommunicationsChannels30 5.12Status .31 5.13Service request logic.37 5.14Hot-swap capability.38 6.Commands .38 6.1Standard commands 39 6.2 Manufacturer-defi ned commands 53 7. Transducer Electronic Da
36、ta Sheet (TEDS) specifi cation.53 7.1General format for TEDS53 7.2Transmission of the TEDS 54 7.3Meta-TEDS54 7.4TransducerChannel TEDS.60 7.5Calibration TEDS73 7.6Frequency Response TEDS.82 7.7Transfer Function TEDS.84 7.8Text-based TEDS.90 7.9 End user application specifi c TEDS 94 7.10Commissionin
37、g TEDS .94 7.11 Manufacturer-defi ned TEDS .95 7.12PHY TEDS95 8.Upper layers of the ISO model (layer 3 through layer 7) .97 8.1 Data transmission order and bit signifi cance97 8.2 Protocol identifi ers.99 8.3Datagram protocol 99 8.4Streaming data protocol 102 8.5Trigger protocol. 102 8.6Command serv
38、ices protocol 104 8.7Reply protocol. 104 9. Standard services off ered by the Data Link Layer 106 9.1Syntax and semantics. 106 viiiCopyright ? 2004 IEEE. All rights reserved. 9.2Streaming mode management services on the TBC. 107 9.3Streaming mode protocol services 110 9.4Discovery services in the TB
39、C 112 9.5Discovery services in the TBIM . 113 9.6Transmitter control services . 114 9.7Datagram protocol services 115 9.8Trigger protocol services. 117 9.9Delay measurement services . 119 10.Lower layers of the ISO model (layer 1 and layer 2) 120 10.1 Data Link Layer protocol specifi cations 121 10.
40、2Data linkLogical Link Control (LLC) sublayer. 124 10.3Data linkMAC sublayer 125 10.4Physical layer 137 10.5 Physical specifi cations. 141 Annex A (informative) Bibliography . 147 Annex B (normative) XML schema for text-based TEDS 148 Annex C (informative) Example Meta-Identifi cation TEDS. 153 Anne
41、x D (informative) Example TransducerChannel Identifi cation TEDS 154 Annex E (informative) Example Calibration Identifi cation TEDS . 156 Annex F (informative) Example Commands TEDS 157 Annex G (informative) Example Location and Title TEDS . 160 Annex H (informative) Example physical units. 162 Anne
42、x I (informative) TEDS Read and Write protocols 169 Annex J (informative) Trigger logic confi gurations. 171 Copyright ? 2004 IEEE. All rights reserved.ix IEEE Standard for a Smart Transducer Interface for Sensors and ActuatorsDigital Communication and Transducer Electronic Data Sheet (TEDS) Formats
43、 for Distributed Multidrop Systems 1. Overview This standard introduces the concept of a Transducer Bus Interface Module (TBIM) and a Transducer Bus Controller (TBC) connected by a transducer bus. A TBIM is a module that contains the bus interface, signal conditioning, Analog-to-Digital and/or Digit
44、al-to-Analog conversion and in many cases the transducer. A TBIM can range in complexity from a single sensor or actuator to units containing many transducers (sensors and actuators). A TBC is the hardware and software in the Network Capable Application Processor (NCAP) or host processor that provid
45、es the interface to the transducer bus. The transducer bus provides the communications path between an NCAP or host processor and one or more TBIMs. Three types of transducers are recognized by this standard. They are sensors, event sensors, and actuators. A TransducerChannel is denoted smart in thi
46、s 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. Triggering, status, and control are provided to support the proper functioning of the TransducerChannel. A TBC,
47、 that may be part of an NCAP or host processor, controls a TBIM by means of a dedicated digital bus. The bus controller or NCAP mediates between the TBIM and a higher-level digital network, and may provide local intelligence. This standard provides for TBIMs that can be plugged into a system and be
48、used without having to add special drivers, profi les, or make any other changes to the system. This is referred to as plug and play operation. The primary features that enable plug and play operation are the TEDS and the basic command set. A TBIM may be added to or removed from an active transducer
49、 bus with no more Copyright ? 2004 IEEE. All rights reserved.1 than a momentary impact on the data being transferred over the bus. Hot swap is the term used to refer to this feature. This standard is organized 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 applying this standard. Clause 3: Defi nitions, acronyms, and abbreviations provides defi nitions that are either not found in other standards, or have been modifi ed for use w
链接地址:https://www.31doc.com/p-3770197.html