Hi Janos,
I have also used AlarmHybridMicro32C component to get pulse values. As you
said I have saved all alarm fire events at pulse variable and sent it
through
TimeSyncAMSend.send(...) . However, again I always get hude clock drifts and
cannot estimate relative hw clock rate of the reference
Hi Sinan,
I have used 3 nodes. One of the nodes (reference node) broadcast a packet
using TimeSyncAMSend interface at every 0x50 microseconds and the other
nodes which are in the broadcast range of the sender receive this message
and queries the corresponding local time transformation of
Hi Janos,
I achieved 0x50 microsecond periodicity by such a way:
- I set a milli timer of (of 0x1400 milliseconds)
- I store the local time at the first fire ıf the timer at a variable called
pulse
- At each timeout of the timer, I add 0x50 to the pulse variable
- And I give pulse as a
Sinan,
I achieved 0x50 microsecond periodicity by such a way:
- I set a milli timer of (of 0x1400 milliseconds)
- I store the local time at the first fire ıf the timer at a variable called
pulse
- At each timeout of the timer, I add 0x50 to the pulse variable
- And I give pulse as
Hi Janos,
I haven't compiled your test application yet but I have developed a sample
application and I have only used your msp430 library /tinyos-2.x-
contrib/vu/tos/chips/msp430 for my application.
Let me explain how the application works:
I have used 3 nodes. One of the nodes (reference node)
Hi Sinan,
I have just run the test app
(tinyos-2.x-contrib/vu/apps/TestPacketTimeSync), but didn't see any
extreme inconsistencies apart from some clock drift. Would you mind
running this app and sharing the output with me? Also, can you send me
the compilation output (output of PFLAGS=-v make
Sinan,
The problem is that it's not possible to tell the radio stack to
transmit a message at time t. The time delay between
TimeSyncAMSend.send() being called and the message actually going out
has a significant jitter (clear channel assessment, collision
avoidance mechanism is going on in
Hi Janos ,
I am doing the same steps. I am still searching what did I do wrong... I am
using system which has been newly checked out from tinyos-2.x development
repository.
Is it possible to use only the codes in the directory *
/tinyos-cvs/tinyos-2.x-contrib/vu/tos/chips/msp430* without
Sinan:
I am doing the same steps. I am still searching what did I do wrong... I am
using system which has been newly checked out from tinyos-2.x development
repository.
Which setup do you use out of the two I described? Can you please send
me the numbers you get?
Janos
06 Ağustos 2010 17:27
Hi Janos,
I have downloaded tinyos-2.x from repository as well as tinyos-2.x-contrib.
I have applied the steps you have written previously to use your stack.
I have a transmitter node which transmits a message every 5 seconds. The
nodes which receive this message get timestamps of the received
Hi Thomas,
I am working on a similar platform to Telos I think... (It is Genetlab
Sensenode platform). I have connected TimerA to the SFD line as you said. I
have modified the file HplCC2420InterruptsC.
configuration HplCC2420InterruptsC {
provides interface GpioCapture as CaptureSFD;
Hi again,
I wanted to add some comments to my last reply.
When I connect Timer A to SFD, I could get time= 0 from *async event void
CaptureSFD.captured( uint16_t time )* and it means all timestamps are
invalid. Also, I could not get time values LocalTimeMicroC component and it
always returns
Sinan,
Things are not that easy, unfortunately. For port 4.1, that's where
the interrupt line of the cc2420 is connected, you must use timer B
for capture. This means that you will need to reprogram the whole
timer subsystem such that timer B is driven by the internal DCO, and
timer A is driven
Sinan,
I actually have an alternative cc2420 radio stack implementation under
tinyos-2.x-contrib/vu that does what you want. That is, the msp430
timer subsystem is reprogrammed such that timer A is the 32kHz timer
and timer B is the micro timer. The radio stack uses the micro timer
for
Hi Sinan,
The problem is not in the TinyOS code. The hardware you use (I assume
TelosB or Sky?) does not support these timestamps by default. The
timestamps are taken when the SFD line toggles. This line is connected
to the TimerB, which is sourced from the 32kHz signal. Thus, you can
not get
15 matches
Mail list logo
