Re: [Tinyos-help] Problem with Netsync, restarting motes.

2006-08-20 Thread Henric Kärnhall
Hi Joe,

Yes, I have a node 0. And still, I don't know how to get synchronization
(a global time) together with a 100% dutycycle on the radio.

/Henric

- Original Message -
From: Joe Polastre <[EMAIL PROTECTED]>
Date: Friday, August 18, 2006 10:28 pm
Subject: Re: [Tinyos-help] Problem with Netsync, restarting motes.
To: Henric Kärnhall <[EMAIL PROTECTED]>
Cc: tinyos-help@millennium.berkeley.edu

> Hi Henric,
> 
>  Do you have a node 0 or a node connected to the PC running Trawler?
> These nodes serve as the reference for the synchronization, so one
> must exist in your network.  Programming a node with address=0 is
> usually the easiest way to achieve this.
> 
> -Joe
> 
> On 8/18/06, Henric Kärnhall <[EMAIL PROTECTED]> wrote:
> > Hi Joe!
> >
> > Thank you for your quick answer about Netsync.
> >
> > If I use "make tmote lowpower,#" I get a stable sync and a 
> maximum duty
> > cycle of 50% (as you told me).
> >
> > And when I use "make tmote" I get a dutycycle of 100% (as you 
> told me),
> > BUT a never get a stable sync! I fact I don't get sync at all. 
> When I
> > say stable sync I mean that GlobalTime.isValid() should be true 
> during a
> > long time period. I need this because I plan to use the 
> globaltime to
> > get a synchronized timestamp of samples with a high accuracy.
> >
> > QUESTION:
> > The problem is: How do I get 100% dutycycle AND synchronization 
> at the
> > same time? What parameters should I modify? Or is it not possible?
> >
> > I would be happy if you could answer this because I have been 
> working on
> > this problem for a very long time now.
> >
> > /Henric
> >
> > - Original Message -
> > From: Joe Polastre <[EMAIL PROTECTED]>
> > Date: Thursday, August 17, 2006 6:22 pm
> > Subject: Re: [Tinyos-help] Problem with Netsync, restarting motes.
> > To: Henric Kärnhall <[EMAIL PROTECTED]>
> > Cc: tinyos-help@millennium.berkeley.edu
> >
> > > Hi Henric,
> > >
> > >  When you want to use lowpower, you should compile with:
> > >
> > > make tmote lowpower
> > >
> > >  If you want a 100% duty cycle, then compile with:
> > >
> > > make tmote
> > >
> > >  To change the duty cycle that the application is compiled with 
> (from> > 1-50% are supported), you can compile with the following 
> option:> >
> > > make tmote lowpower,#
> > >
> > >  where # is a number between 1 and 50 representing the duty cycle.
> > >
> > >  Furthermore, you may want to check out
> > >
> > > http://www.moteiv.com/community/Moteiv_Boomerang_Fixes
> > >
> > >  for the most up-to-date supported patches.  There is a patch 
> there> > for NetSync with Boomerang 2.0.4, FYI.
> > >
> > > -Joe
> > >
> > >
> > > On 8/17/06, Henric Kärnhall <[EMAIL PROTECTED]> wrote:
> > > > Hi,
> > > >
> > > > I'm using tinyos 2.0.4 from Moteiv and the netsync component 
> to get
> > > > synchronized time information when i'm sampling data. I have
> > > changed the
> > > > dutycycle to 100%
> > > > LOWPOWER ?= 100 in the file lowpower.extra
> > > > to get a higher data rate on the radio. (Is this a  correct way
> > > to get
> > > > higher data rate with sync?)
> > > >
> > > > My problem is that it takes 3-5 (or more) minutes before the
> > > slave nodes
> > > > have a stable sync to the master node. The startup time is 
> not a big
> > > > problem but during that time the slave nodes are restarting 
> (?). It
> > > > seems like they get a reset? The StdControl.init() function is
> > > executed.> And it also happens that the slave nodes drops the 
> sync,> > 10-30 minutes
> > > > after it has stabilized, and the procedure must start all over
> > > again.>
> > > > Is this normal?
> > > >
> > > > /Henric
> > > >
> > > > ___
> > > > Tinyos-help mailing list
> > > > Tinyos-help@Millennium.Berkeley.EDU
> > > > https://mail.millennium.berkeley.edu/cgi-
> > > bin/mailman/listinfo/tinyos-help
> > > >
> > >
> >
> 

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


Re: [Tinyos-help] Problem with Netsync, restarting motes.

2006-08-18 Thread Henric Kärnhall
That is correct Phil, I meant Boomerang 2.0.4.

Sorry for that misleading information.

Do you have a solution to my problem? Take a look at my replay to Joe.

/Henric

- Original Message -
From: Philip Levis <[EMAIL PROTECTED]>
Date: Thursday, August 17, 2006 6:12 pm
Subject: Re: [Tinyos-help] Problem with Netsync, restarting motes.
To: Henric Kärnhall <[EMAIL PROTECTED]>
Cc: tinyos-help@Millennium.Berkeley.EDU

> On Aug 17, 2006, at 1:41 AM, Henric Kärnhall wrote:
> 
> > Hi,
> >
> > I'm using tinyos 2.0.4 from Moteiv and the netsync component
> 
> Do you mean Boomerang 2.0.4? TinyOS 2.0 is in beta2.
> 
> Phil

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


Re: [Tinyos-help] Problem with Netsync, restarting motes.

2006-08-18 Thread Henric Kärnhall
Hi Joe!

Thank you for your quick answer about Netsync.

If I use "make tmote lowpower,#" I get a stable sync and a maximum duty
cycle of 50% (as you told me).

And when I use "make tmote" I get a dutycycle of 100% (as you told me),
BUT a never get a stable sync! I fact I don't get sync at all. When I
say stable sync I mean that GlobalTime.isValid() should be true during a
long time period. I need this because I plan to use the globaltime to
get a synchronized timestamp of samples with a high accuracy.

QUESTION:
The problem is: How do I get 100% dutycycle AND synchronization at the
same time? What parameters should I modify? Or is it not possible?

I would be happy if you could answer this because I have been working on
this problem for a very long time now.

/Henric

- Original Message -
From: Joe Polastre <[EMAIL PROTECTED]>
Date: Thursday, August 17, 2006 6:22 pm
Subject: Re: [Tinyos-help] Problem with Netsync, restarting motes.
To: Henric Kärnhall <[EMAIL PROTECTED]>
Cc: tinyos-help@millennium.berkeley.edu

> Hi Henric,
> 
>  When you want to use lowpower, you should compile with:
> 
> make tmote lowpower
> 
>  If you want a 100% duty cycle, then compile with:
> 
> make tmote
> 
>  To change the duty cycle that the application is compiled with (from
> 1-50% are supported), you can compile with the following option:
> 
> make tmote lowpower,#
> 
>  where # is a number between 1 and 50 representing the duty cycle.
> 
>  Furthermore, you may want to check out
> 
> http://www.moteiv.com/community/Moteiv_Boomerang_Fixes
> 
>  for the most up-to-date supported patches.  There is a patch there
> for NetSync with Boomerang 2.0.4, FYI.
> 
> -Joe
> 
> 
> On 8/17/06, Henric Kärnhall <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I'm using tinyos 2.0.4 from Moteiv and the netsync component to get
> > synchronized time information when i'm sampling data. I have 
> changed the
> > dutycycle to 100%
> > LOWPOWER ?= 100 in the file lowpower.extra
> > to get a higher data rate on the radio. (Is this a  correct way 
> to get
> > higher data rate with sync?)
> >
> > My problem is that it takes 3-5 (or more) minutes before the 
> slave nodes
> > have a stable sync to the master node. The startup time is not a big
> > problem but during that time the slave nodes are restarting (?). It
> > seems like they get a reset? The StdControl.init() function is 
> executed.> And it also happens that the slave nodes drops the sync, 
> 10-30 minutes
> > after it has stabilized, and the procedure must start all over 
> again.>
> > Is this normal?
> >
> > /Henric
> >
> > ___
> > Tinyos-help mailing list
> > Tinyos-help@Millennium.Berkeley.EDU
> > https://mail.millennium.berkeley.edu/cgi-
> bin/mailman/listinfo/tinyos-help
> >
> 

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] Problem with Netsync, restarting motes.

2006-08-17 Thread Henric Kärnhall
Hi,

I'm using tinyos 2.0.4 from Moteiv and the netsync component to get
synchronized time information when i'm sampling data. I have changed the
dutycycle to 100%
LOWPOWER ?= 100 in the file lowpower.extra
to get a higher data rate on the radio. (Is this a  correct way to get
higher data rate with sync?)

My problem is that it takes 3-5 (or more) minutes before the slave nodes
have a stable sync to the master node. The startup time is not a big
problem but during that time the slave nodes are restarting (?). It
seems like they get a reset? The StdControl.init() function is executed.
And it also happens that the slave nodes drops the sync, 10-30 minutes
after it has stabilized, and the procedure must start all over again.

Is this normal?

/Henric

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] Synchronization and "high data rate" on radio?

2006-07-31 Thread Henric Kärnhall
Hi

I have posted these questions a few times but never got any clear
answers. I would be pleased if someone could give me some answers this time.

1. Why does netsync require "lowpower" mode? And what does it actually
mean to compile with the lowpower flag?
2. Is it possible to send data with high data rate on the radio when
using synchronization with netsync? (high data rate = same data rate as
without using netsync)
3. Is there any other way to get a synchronized global time without
using netsync?

/Henric
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] Maximum data rate on the radio?

2006-07-31 Thread Henric Kärnhall
Hi

What is the (practical) maximum data rate on the radio? I`m using the
tmote hardware from moteiv. 

I have seen these values:
  - max 25 packages / sec
  - max 29b / package
that is.. 25 * 29 * 8 = 5.8kbps. Correct??

But motive has this information on their homepage:
  - "250kbps 2.4GHz IEEE 802.15.4 Chipcon Wireless Transceiver"

I would like to sample data from one or more units at as high speed as
possible and send the sampled data in realtime on radio to a master unit.

/Henric
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] Questions on NetSync and lowpower

2006-06-21 Thread Henric Kärnhall
Hi

Thanks Joe for your answer on my last question.

I have a few more questions on NetSync and about the lowpower flag to 
make.

I want to use NetSync to get the GlobalTime. But to use NetSync I have 
to use the lowpower flag to make, correct? (e.g. make tmoteinvent MyApp 
lowpower). And by using the lowpower mode things doesn’t work as I 
would like to. For example the UART and radio is only enabled a short 
time period every two second.

To get the UART up and running I did like this:

call Timer.start(TIMER_REPEAT, 50);

...

event result_t Timer.fired(){
   if(call HPLUSARTControl.isUART() == FALSE)
  call HPLUSARTControl.enableUART();
}

Is that ok? Or a bad idea?

How can I get my network synchronized (with for example NetSync) but at 
the same time have full speed radio communication? And how do I switch 
between lowpower and full speed in runtime?

Best regards,
Henric

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] Problem with NetSync and UART

2006-06-20 Thread Henric Kärnhall
Hi

I have written a debug component that allow me to write debug data and 
text to the UART and read it in a simple terminal program.
In works fine. But when I’m using the NetSync and GlobalTime it fails. 
It seems like something is writing a lot of junk to the UART.
I think that the reason might be because NetSync is checking if 
something is connected to the UART by using Detect (?).
If this is the case, is there a way to disable this check? I don’t want 
someone else to write things to the UART.
(My debug component is using the call HPLUART.put(...) to write to the 
UART)

Best Regards,
Henric
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help