Hi Urs,
I used a testbed of 15 IRIS sensor nodes which are placed in communication
range of the reference broadcaster. I constructed a line topology by
configuring each node such that it will accept incoming messages from the
nodes with id one more or one less of the id of the current node.
Hi Janos,
In fact I have developed another time synchronization protocol and I have
tested it using the same testbed. I can get 2-3 miroseconds accuracy. Thus,
I feel that the timestamping mechanism works well (but just a feeling :)). I
just suspect about if some modification to TimeSyncP is
Hi Janos,
I have done the modifications as you have said and also used the NoSleepC
component of your implementation in tinyos-2.x-contrib repository. But I
don't get tight skew values on a line of 5 iris sensor nodes.
Here are the results after a 15 minute run:
1287678021203: [nodeid=0x1]
I can make some wild guesses, but can't give you a solution.
- The 7.3mhz crystal has a precision of 50ppm. The beaconing rate of
FTSP is 10 seconds by default (can be set with
PFLAGS+=-DTIMESYNC_RATE=value in the Makefile), which can result in
an 500 us error per hop. However, FTSP's linear
Sinan,
It's not there, but it's not terribly complicated to accomplish. Just
take a look at TimeSyncC and TimeSync32kC, and based on those, come up
with your TimeSyncMicroC. As far as I can tell, this is the only file
you'll need to cook for yourself, you don't need to touch anything
else.
A
