Hi Micha, How do you know if the timer fails to fire?
I experienced the same problem before. Whenever the timer fires, a log is sent to the UART. If no log is received when a timer is supposed to fire, the timer is regarded to fail to fire. This turns out wrong because no log can be also caused by UART failure, which is the case. -Xiaohui On Friday, August 9, 2013, Ádám Erdélyi wrote: > Hi Micha, > > could you show us the wiring code for the timer, how you initialize the > timers and how you handle the firing event? Does it fire when started by > other functions? (e.g. a simple Timer.start) Did you use the unique() > function at the beginning? > > Cheers, > Adam > On Aug 8, 2013 3:02 PM, "Micha Rappaport" > <[email protected]<javascript:_e({}, 'cvml', '[email protected]');>> > wrote: > >> Hello, >> >> I am using multiple instances of the TimerMilliC component on a telosB >> mote. When I use the timer.startOneShot() command, the timer does not >> always fire. I checked the timer.isRunning() command which returns TRUE! >> >> Next I checked the times now, t0 and dt which look all promising: >> This works: >> now: 13530, t0: 13529, dt: 2500 >> This does not: >> now: 21513, to: 21512, dt: 2500 >> >> Any ideas where else the problem could lie? >> >> Thanks, >> Micha >> _______________________________________________ >> Tinyos-help mailing list >> [email protected] <javascript:_e({}, 'cvml', >> '[email protected]');> >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >> > -- -Xiaohui Liu TelosB TinyOS 2.1.2 www.cs.wayne.edu/xliu/
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
