Hi Joe, Yes, I have a node 0. And still, I don't know how to get synchronization (a global time) together with a 100% dutycycle on the radio.
/Henric ----- Original Message ----- From: Joe Polastre <[EMAIL PROTECTED]> Date: Friday, August 18, 2006 10:28 pm Subject: Re: [Tinyos-help] Problem with Netsync, restarting motes. To: Henric Kärnhall <[EMAIL PROTECTED]> Cc: tinyos-help@millennium.berkeley.edu > Hi Henric, > > Do you have a node 0 or a node connected to the PC running Trawler? > These nodes serve as the reference for the synchronization, so one > must exist in your network. Programming a node with address=0 is > usually the easiest way to achieve this. > > -Joe > > On 8/18/06, Henric Kärnhall <[EMAIL PROTECTED]> wrote: > > Hi Joe! > > > > Thank you for your quick answer about Netsync. > > > > If I use "make tmote lowpower,#" I get a stable sync and a > maximum duty > > cycle of 50% (as you told me). > > > > And when I use "make tmote" I get a dutycycle of 100% (as you > told me), > > BUT a never get a stable sync! I fact I don't get sync at all. > When I > > say stable sync I mean that GlobalTime.isValid() should be true > during a > > long time period. I need this because I plan to use the > globaltime to > > get a synchronized timestamp of samples with a high accuracy. > > > > QUESTION: > > The problem is: How do I get 100% dutycycle AND synchronization > at the > > same time? What parameters should I modify? Or is it not possible? > > > > I would be happy if you could answer this because I have been > working on > > this problem for a very long time now. > > > > /Henric > > > > ----- Original Message ----- > > From: Joe Polastre <[EMAIL PROTECTED]> > > Date: Thursday, August 17, 2006 6:22 pm > > Subject: Re: [Tinyos-help] Problem with Netsync, restarting motes. > > To: Henric Kärnhall <[EMAIL PROTECTED]> > > Cc: tinyos-help@millennium.berkeley.edu > > > > > Hi Henric, > > > > > > When you want to use lowpower, you should compile with: > > > > > > make tmote lowpower > > > > > > If you want a 100% duty cycle, then compile with: > > > > > > make tmote > > > > > > To change the duty cycle that the application is compiled with > (from> > 1-50% are supported), you can compile with the following > option:> > > > > make tmote lowpower,# > > > > > > where # is a number between 1 and 50 representing the duty cycle. > > > > > > Furthermore, you may want to check out > > > > > > http://www.moteiv.com/community/Moteiv_Boomerang_Fixes > > > > > > for the most up-to-date supported patches. There is a patch > there> > for NetSync with Boomerang 2.0.4, FYI. > > > > > > -Joe > > > > > > > > > On 8/17/06, Henric Kärnhall <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > > > > > I'm using tinyos 2.0.4 from Moteiv and the netsync component > to get > > > > synchronized time information when i'm sampling data. I have > > > changed the > > > > dutycycle to 100% > > > > LOWPOWER ?= 100 in the file lowpower.extra > > > > to get a higher data rate on the radio. (Is this a correct way > > > to get > > > > higher data rate with sync?) > > > > > > > > My problem is that it takes 3-5 (or more) minutes before the > > > slave nodes > > > > have a stable sync to the master node. The startup time is > not a big > > > > problem but during that time the slave nodes are restarting > (?). It > > > > seems like they get a reset? The StdControl.init() function is > > > executed.> And it also happens that the slave nodes drops the > sync,> > 10-30 minutes > > > > after it has stabilized, and the procedure must start all over > > > again.> > > > > Is this normal? > > > > > > > > /Henric > > > > > > > > _______________________________________________ > > > > Tinyos-help mailing list > > > > Tinyos-help@Millennium.Berkeley.EDU > > > > https://mail.millennium.berkeley.edu/cgi- > > > bin/mailman/listinfo/tinyos-help > > > > > > > > > > _______________________________________________ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
