I know this isn't really hugely helpful ... but what you'll have to do is use a less-complex time sync.
Depending on the accuracy you are interested in (~1us, ~1ms, ~1s) maybe the recently-discussed time sync stuff in tinyos-devel will be more compact/useful? Or, if you can accept some error in the measurement you could transmit a time field that gets updated at each mote... e.g. mote 1 transmits with time=0 mote 2 starts a <ms> counter N2 on receiving this message mote 2 transmits the message with time=0 + t(N2) mote 3 starts a timer... ... last mote receives the time = sum(all the intermediate node's counters) which is the total number of counter ticks (ignoring skew between motes) from start to finish? This would result in some (~8ms ave error for micaz is quite likely) error for each hop but should give you an end to end time that isn't too far off depending on the accuracy required (depending how you transmit the time and when you start the counter you could be more accurate) Cheers, Ben > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > [EMAIL PROTECTED] > Sent: 09 April 2008 14:05 > To: [email protected] > Subject: [Tinyos-help] TsyncC and Deluge > > > Hi, > I want to measure time that Deluge T2 use for disseminating a new > image. > For this scope I need that motes are time syncronized so I can > measure what I need. > (Once motes are syncronized, BaseStation before > disseminate -d command read current time > and last mote that receiving > image read current time immediatly after receiving image. > The > difference between this two times give me total time for > disseminating > an image) > > For syncronizing motes I need to include component of time > syncronization into Deluge code. > I chose component TsyncC as time > syncronizing component (proposed from tinyos-2.x-contrib/iowa/T2. > tsync). > The problem is that Deluge (without component TsyncC) is: > > 32726 ROM > 1239 RAM > While component TsyncC is: > 21748 ROM > > 912 RAM > > My motes are tmote sky (48KByte of ROM), when I include > component TsyncC in Deluge > I can't compile because I have an error: > msp430-ld: address 0x111e8 of build/telosb/main.exe section .text is > not within region text > msp430-ld: section .vectors [0000ffe0 -> > 0000ffff] overlaps section .text [00004a00 -> 000111e7] > msp430-ld: > build/telosb/main.exe: section .vectors lma 0xffe0 overlaps previous > sections > make: *** [exe0] Error 1 > > If I don't wrong, this error means > that my application is too big, go over maximum size of my motes ROM > (48Kbyte). > How can I solve this problem? > > Thanks. > Elisa > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/t inyos-help ******************************************************************************* 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
