[Tinyos-devel] Request for comments: TEP-108

[Miguel Freitas]

Hi Kevin,

On 11/5/06, Kevin Klues <klueska at gmail.com> wrote:
> Dear TinyOS developer community:
>
> Matt Welsh sent out a request for comments on TEP 108 on October 20th.
>  Until now no one has responded to this request, and the deadline
> before  the TEP moves into final review is November 17th.

I'm a newcomer here, so please take my comments with a grain of salt.
I have replied Matt directly with both comments and questions, below
is the email i've sent him.

---

On 10/31/06, Miguel Freitas <mfreitas at gmail.com> wrote:
> Matt,
>
> I'm investigating the porting of the mts300 sensorboard to latest
> tinyos-2.0 standards, and resource arbitration is a key point.
>
> i have 2 sensors sharing a single resource (the same adc channel). to
> make things more fun, the original mts300 code implemented a 10ms
> delay after changing adc source as a matter of "stabilization" of the
> signal.
>
> my plan for implementing this would be using the Resource /
> ResourceRequested interfaces. for example:
>
> implementation of the command "read()" of one of the sensors:
>
> 1. check if isOwner(), proceed with ADC conversion if true and go (5).
> 2. if not owner, request() resource.
> 3. on granted(), start a 10ms timer.
> 4. on timer's fired(), proceed with ADC conversion.
> 5. do not release resource.
> 6. on requested() event, call release()
>
> this way, every time the resource is changed between sensors i would
> have the 10ms delay. consecutive reads to the same sensor do not need
> to use the timer.
>
> the problem is: requested() event is only available from
> ResourceController which is a single instance on arbiters. there is no
> such thing called ResourceRequested on tinyos cvs.
>
> what should i do?
>
> is that TEP waiting for general agreement before ones starts coding
> support for ResourceRequested?
>
> am i trying a wrong/bad/stupid solution for this problem?
>
> Miguel
>