Thanks for your reply. I have been experiencing some packet loss, this requiring retries at the application level. Since i have a few other tasks doing various other things in the system, i presumed that it could be because the the Timer used by LowPowerListening might not be getting scheduled at the right time if sufficient tasks are ahead of it in the queue. I also noticed that if i increased the listen duration, the number of retries reduced
On Wed, Jan 8, 2014 at 8:53 AM, Miklos Maroti <[email protected]>wrote: > Hi, > > Why do you need to have it fired in async mode? Why do you want to use > something else than the Timer.fired()? > > Miklos > > On Sun, Dec 29, 2013 at 8:13 PM, Roadstar Runner <[email protected]> > wrote: > > Hi, > > I am trying to move all my communication tasks to a high priority task > > queue. I have already tweaked the scheduler so that it can handle 2 > > priority levels. > > One of the tasks used by the low power listening module > > (LowPowerListeningLayerP.nc) relies on a Timer task(Timer.fired() event > ) to > > schedule/change the radio states. Since only TImer0 runs in sleep mode, i > > cannot use the AlarmMicro32C component since they (Timer1,2,3) will > prevent > > the micro from sleeping. > > Is there any way to have a timer/alarm that can run in sleep mode and > > provide an async event. > > Please advise. > > Thanks > > > > > > Platform Iris > > > > _______________________________________________ > > 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
