Andreas, That's not the unwired timer. It's the radio chip. By default, the radio is on after power-up. It's the radio driver that puts it to sleep. The radio driver is not wired in the Null app, therefore, the transceiver is never put to sleep.
Janos On Fri, Nov 11, 2011 at 8:51 AM, Andres Vahter <[email protected]> wrote: > Hi, > I did some power consumption tests with Null app using custom Iris OEM > board. Measurements were made at 3.3 V using Keithley 2015 THD multimeter. > I got 3.3 mA with standard Null app, however if I just added components > ActiveMessageC; to NullAppC.nc it dropped to stable 21 uA. > After that I also added plain components new TimerMilliC() as Timer; and > after that average current went to 54 uA, however application logic really > did not use that timer at all - it is unwired. > Current draw seems to be around 20 - 30 uA but there are some high peaks if > Timer is used and those peaks increase average current draw. However if > Timer is not used I see very very stable 21 uA. > I also tried to stop that timer right after boot event, but it did not > affected the current draw. > I guess there is some kind of fundamental implementation detail that causes > this behaviour. > > NullAppC.nc: > configuration NullAppC{} > implementation { > components MainC, NullC; > components ActiveMessageC; // decreases average current draw from 1.3 mA > to 21 uA > components new TimerMilliC() as Timer; // increases average current draw > from 21 uA to 54 uA > MainC.Boot <- NullC; > } > NullC.nc: > module NullC @safe() > { > uses interface Boot; > } > implementation > { > event void Boot.booted() { > // Do nothing. > } > } > > Andres Vahter > _______________________________________________ > Tinyos-devel mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel > > _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
