Thats great, now it all makes sense ; )
Thanks for all the help Zainul and Roy! Both mail-Lists are really nice,
very active... Fast responses, thanks !
Alessandro Stamatto.
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.mi
Howdy,
> That said, I don't quite know why each node starts with an offset of
> 800.
This additional wait is coming from the clock initialization. Take a
look at Init.init in tos/platforms/mica/MeasureClockC.nc for details.
If we un-inline this call and disable avr-gcc optimizations we can g
Apologies for cross posting, I believe this may be useful to both communities.
The reason that the one node starts 100 cycles after the other is
because John's example command includes a stagger-start interval of
that amount.
That said, I don't quite know why each node starts with an offset o
Hi,
Indeed i had the old version, but after updating the Avrora Source Tree i
still got an odd output. I runned RadioCountToLeds in Avrora and the
simulation output started like this:
" 1 9007934 off off on
1 9007936 off on on
1 9007938 on on on
1 9007940
Hello guys,
I checked Avrora, sugested by Andrey/Zainul and i really liked it.
But, following a Quickstart Guide (
http://www.cs.utah.edu/~regehr/tos_avrora.html ) i encounter a major problem
the author says:
"If you just see output from node 0 around time 800 and then node 1
around 900,
