Note
This memo documents a part of TinyOS for the TinyOS Community, and @@ -319,15 +314,15 @@ requests discussion and suggestions for improvements. Distribution of this memo is unlimited. This memo is in full compliance with TEP 1.
This memo documents how sensor drivers are organized in TinyOS and how sets of sensor drivers are combined into sensor boards and sensor platforms, along with general principles followed by the components that provide access to sensors.
This section describes the basic organization principles for sensor drivers in TinyOS.
For background, a sensor can be attached to the microcontroller on a @@ -379,8 +374,8 @@ the driver MAY provide additional interfaces that would allow higher-level clients to obtain information needed to properly interpret the value.
A sensor HIL component MUST provide:
Sensors with a richer interface than would be supported by the SID interfaces MAY provide a HAL component in addition to a HIL component.
@@ -502,8 +497,8 @@ implementation { }Because the same physical sensor can be attached to TinyOS platforms in many different ways, the organization of sensor drivers SHOULD reflect the distinction between sensor and sensor interconnect.
@@ -572,8 +567,8 @@ code that will enter the core source tree. In general, sensor components can be placed anywhere as long as the nesC compiler receives enough -I directives to locate all of the necessary pieces.The Analog sensor requires two components
The Binary sensor gets a bit more complex, because it has three components:
The Digital sensor is the most complex out of the set, and includes six components: