IEEE 1451.3-2003
$98.04
IEEE Standard for a Smart Transducer Interface for Sensors and Actuators – Digital Communication and Transducer Electronic Data Sheet (TEDS) Formats for Distributed Multidrop Systems
Published By | Publication Date | Number of Pages |
IEEE | 2003 |
New IEEE Standard – Inactive-Withdrawn. A digital interface for connecting multiple physically separated transducers to a single processor over a single 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 identification protocols, time synchronization protocols, read and write logic functions to access the TEDS, and transducers with a wide variety of attributes are defined. This standard does not specify signal conditioning, signal conversion, or how an application uses the TEDS data.
PDF Catalog
PDF Pages | PDF Title |
---|---|
1 | Cover |
2 | IEEE Standard for a Smart Transducer Interface for Sensors and Actuators-Digital Communication and Transducer Electronic Data Sheet (TEDS) Formats for Distributed Multidrop Systems |
5 | Introduction |
6 | Participants |
7 | Contents |
12 | 1. Overview 1.1 Scope 2. References |
13 | 1.2 Purpose 1.3 Conformance |
16 | 3. Definitions, acronyms, and abbreviations 3.1 Acronyms and abbreviations |
17 | 3.2 Definitions |
20 | 4. Data types 4.1 Unsigned octet integer for counting 4.2 Unsigned octet integer for enumeration |
21 | 4.3 Unsigned 16-bit integer for counting 4.4 Unsigned 16-bit integer for field length 4.5 Signed 32-bit integer 4.6 Unsigned 32-bit integer for counting 4.7 Unsigned 32-bit integer for field length |
22 | 4.8 Single precision real 4.9 Double precision real 4.10 String 4.11 Physical units |
23 | 4.12 Universal unique identification |
24 | 4.13 Arbitrary octet array |
25 | 4.14 Time-of-day 5. Smart transducer functional specification |
26 | 5.1 Plug and play capability 5.2 Addresses |
27 | 5.3 Common characteristics |
28 | 5.4 TransducerChannel type descriptions |
31 | 5.5 Embedded TransducerChannels |
32 | 5.6 TransducerChannel groups 5.7 TransducerChannel proxy |
33 | 5.8 Attributes and operating modes |
37 | 5.9 Triggering |
40 | 5.10 Synchronization |
41 | 5.11 CommunicationsChannels |
42 | 5.12 Status |
48 | 5.13 Service request logic |
49 | 5.14 Hot-swap capability 6. Commands |
50 | 6.1 Standard commands |
64 | 6.2 Manufacturer-defined commands 7. Transducer Electronic Data Sheet (TEDS) specification 7.1 General format for TEDS |
65 | 7.2 Transmission of the TEDS 7.3 Meta-TEDS |
71 | 7.4 TransducerChannel TEDS |
84 | 7.5 Calibration TEDS |
93 | 7.6 Frequency Response TEDS |
95 | 7.7 Transfer Function TEDS |
101 | 7.8 Text-based TEDS |
105 | 7.9 End user application specific TEDS 7.10 Commissioning TEDS |
106 | 7.11 Manufacturer-defined TEDS 7.12 PHY TEDS |
108 | 8. Upper layers of the ISO model (layer 3 through layer 7) 8.1 Data transmission order and bit significance |
110 | 8.2 Protocol identifiers 8.3 Datagram protocol |
113 | 8.4 Streaming data protocol 8.5 Trigger protocol |
115 | 8.6 Command services protocol 8.7 Reply protocol |
117 | 9. Standard services offered by the Data Link Layer 9.1 Syntax and semantics |
118 | 9.2 Streaming mode management services on the TBC |
121 | 9.3 Streaming mode protocol services |
123 | 9.4 Discovery services in the TBC |
124 | 9.5 Discovery services in the TBIM |
125 | 9.6 Transmitter control services |
126 | 9.7 Datagram protocol services |
128 | 9.8 Trigger protocol services |
130 | 9.9 Delay measurement services |
131 | 10. Lower layers of the ISO model (layer 1 and layer 2) |
132 | 10.1 Data Link Layer protocol specifications |
135 | 10.2 Data link—Logical Link Control (LLC) sublayer |
136 | 10.3 Data link—MAC sublayer |
148 | 10.4 Physical layer |
152 | 10.5 Physical specifications |
158 | Annex A (informative)—Bibliography |
159 | Annex B (normative)—XML schema for text-based TEDS B.1 Introduction to text-based TEDS |
160 | B.2 Schema |
164 | Annex C (informative)—Example Meta-Identification TEDS C.1 Introduction C.2 Example instance document |
165 | Annex D (informative)—Example TransducerChannel Identification TEDS D.1 Introduction D.2 Example instance document |
167 | Annex E (informative)—Example Calibration Identification TEDS E.1 Introduction E.2 Example instance document |
168 | Annex F (informative)—Example Commands TEDS F.1 Introduction F.2 Example situation F.3 Example instance document |
171 | Annex G (informative)—Example Location and Title TEDS G.1 Introduction G.2 Example situation G.3 Example instance document |
173 | Annex H (informative)—Example physical units H.1 Approach |
176 | H.2 Examples |
178 | H.3 System considerations |
179 | H.4 Conclusions H.5 Acknowledgments |
180 | Annex I (informative)—TEDS Read and Write protocols I.1 TEDS access I.2 First step in a TEDS access I.3 Writing a TEDS I.4 Reading a TEDS |
182 | Annex J (informative)—Trigger logic configurations J.1 Trigger logic augmented with an embedded time delay actuator |
183 | J.2 Trigger logic augmented with time-of-day sensor |
184 | J.3 Trigger logic augmented with time interval sensor |
185 | J.4 Trigger logic based on event recognition |