Thank for your help, its nice to know that it's not only me the one who had this thinking before :) At least it's good to have recommendations on how to deal with this issue from more experienced people.
Once more, thanks! 2010/1/21 MIchael Schippling <[email protected]>: > Good question...I don't remember seeing any actual specs. > > I have witnessed intermittent failures in a TOS program > that had a task that blocked for 1ms, with Telosb under > T1 and Boomerang. So I would tend to try to keep things > much shorter than that. I don't know what got blocked, > but it eventually caused the program to loose sync with > it's neighbors. > > You can count instructions or toggle an LED and measure > the time with a scope to get an idea of your task's > execution timing. > > MS > > Ruben Rios wrote: >> >> Hello everyone, >> >> I have been reading around about the problem of having computationally >> heavy operations and decompossing such operations into lighter tasks. >> But my question is, when should I do this? I mean, is there a rule of >> thumb (such as loops over 50000 repetitions) to know when should I use >> tasks ??? >> >> Thanks >> > -- Ruben _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
