ICT Centre, CSIRO Australia has a position open for a software engineer in
sensors networks. The position is affiliated with ASLab, located in
Brisbane, QLD and is for a 9 month term. We are looking for a person with
TinyOS development experience and ability to work at lower levels of OS (HW
driver
On 15/11/2010, at 4:26 AM, wafa jaballah wrote:
> Hello,
>
> I want to calculate the local and global time in the receiver's side in order
> to do use them in further calculations so I have used the following code:
>
> event message_t* RadioReceive.receive(message_t* data, void* payload,
> ui
hi sinan,
2011/1/10 Sinan Yildirim :
>
> Do you have any knowledge about how to get microsecond precision timestamps on
> Micaz sensor nodes using the current Tinyos 2.1.1 distribution? I have done
> some modifications but I am not quite sure if it is stable or completely
> correct. It would be r
Michael Collett wrote:
> Hi,
>
> I'm planning on setting up an investigation into clock drift as follows:
>
> *Connect two MicaZ nodes via MIB510s to a laptop's serial ports (am
getting a twin serial port adapter)
> *Node A transmits its clock value to node B. Node B then logs it's
clock value w
Hi Martin,
I ported both 32khz and TMicro based FTSP to T2 and tested it on micaz with
~1.5 clock-tick average global time error (11 nodes, 4 hops, 100 minutes).
More details are here:
http://tinyos.cvs.sourceforge.net/tinyos/tinyos-2.x-contrib/stanford-lgl/apps/TestFTSP/
Cheers,
Brano
On 2/8/
he system during longer runs? In the original
implementation I noticed time synchronization problems when the
local/global timer counter wraps around. I have not yet tested this in
the T2 implementation, but the code looks very similar
Martin
> -Original Message-
> From: Branisl
there are two versions of FTSP:
32khz version (TimeSyncC) has 1/32khz ticks
TMicro version (TimeSyncMicroC) has 8/7.3728MHz ticks
brano
On 3/18/08, John Griessen <[EMAIL PROTECTED]> wrote:
Branislav Kusy wrote:
> Hi Martin,
>
> I ported both 32khz and TMicro based FTSP to T2 a
hi paul,
i haven't really written timer routines - they are part of T2. i was
only testing FTSP for micaZ and the component that provides TMicro
counter for micaZ is tos/platforms/mica/CounterMicro32C.nc
i just did a quick search and i found
tos/chips/msp430/Msp430CounterMicroC.nc which provid
SP for T2? Thanks
>
> On Fri, Apr 11, 2008 at 12:52 AM, Branislav Kusy <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
>
> hi paul,
>
> i haven't really written timer routines - they are part of T2. i was
> only testing FTSP for micaZ and th
hi,
you may want to look at gumstix.com - it has very good OS support
through openembedded, it has WiFi/ethernet extension board and you can
plug in USB devices (for t-mote, you need mini usb to regular usb cable
and usb female/female adapter).
brano
dmanjunath D wrote:
> We are planning to b
hi zhang,
the FTSP paper is:
Maroti M., Kusy B., Simon G., Ledeczi A. "The Flooding Time
Synchronization Protocol". ACM 2nd International Conference on Embedded
Networked Sensor Systems (SenSys). Baltimore, MD, November 2004.
currently, FTSP supports cc2420 chip only in T2 - and it's still wo
jiwen zhang wrote:
> Hello brano :
> I want to make FTSP working on my computer , what should i do ?
> at present , i have the cvs tree , and the the cvs codes of FTSP ,
> also i have micaz motes .
>Firestly , i should compile the app successfully on my computer . for
> example , if i
> Hi,
>
> I have some questions regarding the calculation of the time offset in FTSP:
>
> "async event void PacketLastTouch.touch(message_t* msg)
>{ [...]
> footer->time_offset = local->event_time - call
> PacketTimeStamp.get(msg);
>[...] }"
> local->event_time is the time of giving
hi jiwen,
looking at the cvs head, CC2420CsmaP.nc provides interface RadioBackoff
(http://tinyos.cvs.sourceforge.net/*checkout*/tinyos/tinyos-2.x/tos/chips/cc2420/csma/CC2420CsmaP.nc?revision=1.4)
you may want to update your CVS.
brano
jiwen zhang wrote:
> Hello brano :
>
> can you give
hi jiwen,
jiwen zhang wrote:
> Hello brano :
> The file CC2420CsmaP.nc i mentioned in last email is in
> tinyos-2.x-contrib/stanford-lgl/tos/chips/cc2420/csma , and the file
> CC2420CsmaC is in tinyos-2.x/tos/chips/cc2420/csma .
>i have set the LGLDIR (export
> LGLDIR="$HOME/local2/src/
Marco Langerwisch wrote:
> Hi Brano,
>
> theres still something I don't understand:
>
> > it has access to the SFD_tx timestamp; instead of transmitting T1^ and
> > T_SFD_tx separately, it transmits their offset T_offset=T1^-T_SFD_tx
> > (saving 4 bytes).
> As I can see, T-SFD_tx is in Local
Marco Langerwisch wrote:
> "code moved to T2.1 repository"
>
> Where can I find the T2.1 repository?
>
for now, get the cvs HEAD from
tinyos.cvs.sourceforge.net:/cvsroot/tinyos, module tinyos-2.x
it will be tagged later this week.
brano
___
Tinyos-h
Anton wrote:
> Hello,
>
> in the file
>
>
> http://tinyos.cvs.sourceforge.net/tinyos/tinyos-2.x/tos/chips/cc2420/CC2420TimeSyncMessageP.nc?revision=1.1&view=markup
>
>
>
> from the line 96 it is clear that the usual packet data payload is
> increased by 4 bytes (where event_time is pla
hi marco,
you're seeing the offset because it takes a while for the radio chip HW
to decode the message. cc1000 is byte oriented radio and the decoding
time for 1 byte is about 58 jiffies (1 jiffy is 1 tick of 1/32khz clock
~= 30.5us) at 19.2kbps. this time, however, depends on the settings of
Geoffrey Werner-Allen wrote:
> Hey Brano:
>
> I noticed that you've added a precision tag to the GlobalTime interface
> provided by TimeSyncC. All well and good. What is the TMilli tag (the
> only one supported!?) supposed to indicate? The granularity of the
> resulting value, or its *accura
> Hi,
>
> I'm looking at TestFTSP and it looks like it only works over a single
> hop. Is this correct or am I missing something? If so, are there any
> test applications that deal with FTSP over multiple hops?
if you define CFLAGS += -DTIMESYNC_DEBUG in the Makefile, multihop will
be enforced
guys,
the new _WIN32 support in serialsource.* doesn't compile for me under
cygwin (see the attched log). could you add a compile time flag which
would make using the _WIN32 optional?
the old version of serialsource* compiles and works fine (ie. when i
comment out the _WIN32 stuff).
brano
--
compiles fine now. thanks david!
brano
David Gay wrote:
> On Fri, Dec 5, 2008 at 11:00 AM, Branislav Kusy <[EMAIL PROTECTED]> wrote:
>> guys,
>>
>> the new _WIN32 support in serialsource.* doesn't compile for me under cygwin
>> (see the attched log). could y
hi carlos,
the reason why FTSP does not support T32khz is that there is currently
no HIL component providing T32khz time. however, the timestamping code
on cc2420 platforms supports T32khz. in particular, TimeSyncMessageC.nc
provides interfaces with both TMilli and T32khz precision.
thus i'd s
yes, this was a bug. it should be TS_TIMER_MODE instead of TS_USER_MODE.
i fixed this bug a long time ago in tinyos-1.x, but it mysteriously
propagated back when we ported ftsp from T1 to T2.
thanks jiangjie, i committed the fix.
brano
Omprakash Gnawali wrote:
> Looks like a bug - I think mode
25 matches
Mail list logo
