Dear All, Vanderbilt University has a perfectly working reimplementation of the Clock and Timer components. The number (running) of Timers are limited only by memory (10 bytes per timer). It has a low overhead, and the timer period can be specified in 1/32768 sec units. The Clock is run by the lowest period of all running timers. The timer with the lowest period is fired evenly, all other timers are fired exactly once in their period. It is a drop in replacement in most application. The Clock component also provides a 32bit local time counter in 1/32768 sec units.
We use these timers in timing critical applications, like in acoustic ranging. I would like other people to expolre and use this option, and to start a discussion on how to improve the timing infrastructure of TinyOS. Miklos Maroti PS. You can download these componenst from the CVS: minitasks/02/vu/tos Quoting Lin Gu <[EMAIL PROTECTED]>: > The signalling of AbsoluteTimer[id].fired() may need a little > modification. > > After signaling this event, clearing the corresponding bit in > useBit may not be enough. If this is the last active > AbsoluteTimer, the baseTimerIndex may not be set > correctly so that the next time the absolute timer is 'set', > the component may enter a strange state. > > This is an example, maybe the overall logic of AbsoluteTimer > logic need to be studies and some modification may be needed. > _______________________________________________ > Tinyos-bugs mailing list > [EMAIL PROTECTED] > http://mail.Millennium.Berkeley.EDU/mailman/listinfo/tinyos-bugs > ----------------------------------------------------------------- Maroti, Miklos Vanderbilt University Email: [EMAIL PROTECTED] _______________________________________________ Tinyos-users mailing list [EMAIL PROTECTED] http://mail.Millennium.Berkeley.EDU/mailman/listinfo/tinyos-users
