[Tinyos-8051wg] Re: [Tinyos-2.0wg] Aligning TEP 101 (ADC) with TEP 108 (Resource Arbitration) and 109 (Sensorboards)

[David Gay]

On 5/9/05, David Gay <dgay42 at gmail.com> wrote:
> > 3. "Services"
> >
> > Services are built on top of the wrappers that represent a Sensor. A
> > service component wires to a single or multiple wrappers and extends
> > or combines the functionality of these wrappers. Examples are a round
> > robin service or a service returning multiple samples taken at precise
> > points in time. Services are (mostly) platform independent. Example
> > configuration:
>
> I like this. We can save clients a bit of typing with:

There's now an implementation of this for convenient access to the
(proposed) ADC HIL, in the tos/system/ADCChannelC.nc and
ADCNowChannelC.nc generic components. You can simply say

  components new ADCChannel(CHANNEL_RSSI) as RSSIAdc;

  MyStuff.AcquireData -> RSSIAdc.AcquireData;

to get your own "private" AcquireData interface on the RSSI channel.

It's built out of fairly generic subcomponents, so this can easily be
made available for other data acquisition components or with a
different arbiter (it's currently using RoundRobinArbiter).

There is also a mica A/D HIL component (ADCC) following the proposed
tep101 changes from this thread.

David

_______________________________________________
Tinyos-2.0wg mailing list
Tinyos-2.0wg at Mail.Millennium.Berkeley.EDU
http://Mail.Millennium.Berkeley.EDU/mailman/listinfo/tinyos-2.0wg