The TimerC period is in "binary" milli-secs, I think 1024/second, which comes out to about 1.4 sec/min skew...using that you should be able to do accurate time measurements within the unpredictability of interrupt interleaving, etc...
For T1 versions above .10, the min Timer count is 3. I'm not clear why that was hacked in at that point, but probably something to do with the micaz... To send messages as fast as things can go, skip the timer thing and just start a new message from the sendDone() of the previous. MS Tao Wu wrote:
According to TinyOS1.x TimerC and ClockC' s implementation, for a repeated timer, the min Timer interval is about 2 or 3 ms. And my experiment measure shows that for 1000 ms interval, there are about 1 sec bias per minute. If you want to do it more accurately, try to use ISR directly. Tao On Nov 15, 2007 9:10 AM, RamKishore <[EMAIL PROTECTED]> wrote:Hi all, I fire timer at 100msec.For each firing, I transmit a packet.To increase the Rate of transmission, Timer's time-period can be decreased.what factors should be included in estimating the timer's time period? and Whats the min. Time period that can be achieved? Regards, Kishore _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
