If you issue all those commands in succession with no delays in between, then I expect the behavior to be something like:
WAKE -2000ms- WAKE -2000ms- WAKE (immediate sleep) -1000ms- WAKE -1000ms- ... But it's hard to say... If you tell LPL to setLocalSleepInterval(0), it will immediately turn on. As soon as you tell LPL to begin duty cycling, the radio will turn off. There may be problems calling these commands in quick succession. Maybe applying some unit testing to this will bring out any edge case bugs if any exist. -David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Murray, Ben Sent: Tuesday, October 30, 2007 11:02 AM To: Murray, Ben; 'Tinyos help Forum (E-mail)' Subject: [Tinyos-help] RE: manipulating LPL SLEEP periods Very Sorry - hit the wrong button! Full message follows: Hi again - sorry, one more quick question... If I initiated a tinyOS program using setLocalSleepInterval(2000), and then subsequently issued the following set of commands after 4250 ms: setLocalSleepInterval( 0 ) setLocalSleepInterval( 500 ) setLocalSleepInterval( 1000 ) Should the following pattern be observed for the LPL wake periods?: WAKE -2000ms- WAKE -2000ms- WAKE (-750ms-) WAKE -1000ms- WAKE -1000ms- ... where the (-750ms-) is made up of 250ms, LPL being stopped [which should initiate starting the radio up], but then LPL being started again immediately with a sleep period of 500 [which should immediately shut the radio off again], and finally LPL being set up to change the sleep period upon the next WAKE event... Are there any potential problems/overlaps due to the setLocalSleepInterval calls being so close to one another? Regards, Ben **************************************************************************** *** Please consider the environment before printing this email. **************************************************************************** *** This email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed and may not be divulged to any third party without the express permission of the originator. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thales Research & Technology (UK) Limited. **************************************************************************** *** _______________________________________________ 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
