Re: [Tinyos-help] Collection ack retransmission

2008-05-13 Thread Nahr ...
Thank you very much.
yes yes colection concerns routing not link layer.

Cheers,
Nahr Elk

2008/5/13, Omprakash Gnawali [EMAIL PROTECTED]:

 On Mon, May 12, 2008 at 12:27 PM, Nahr ... [EMAIL PROTECTED] wrote:
  Hi,
  I just want to know how much a node retransmit a not acked msg and how
 long?
  for exemple A sends msg to B
  B receive the msg and sends Ack
   :(   ack is lost.
 
  1. How long A wait the msg ack?

 Collection does not send an ack - it relies on link layer ack.

  2. How much A retransmit the not acked msg ?

 CTP will usually retransmit 5-7 times before it switches the parent.

 - om_p

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Collection Tree Protocol

2008-05-13 Thread Antonio Prados Vilchez
Hi TinyOS users!
 
I'm trying to implement a network involving three MICA2 motes (one of them as a 
base station). I've been doing some research about dynamic routing algorithms, 
and I've decided to use the Collection Tree Protocol (CTP). I find TinyOS 
documentation about CTP very interesting, but I don't know how to use the 
components and interfaces properly (I'm a bit lost). Does anybody know about 
some example code or any other detailed documentation?
 
Thanks in advance. 
==
Este mensaje se dirige exclusivamente a su destinatario, y puede contener 
información confidencial sometida a secreto profesional, o cuya divulgación 
esté legalmente prohibida.Cualquier opinión en él contenida es exclusiva de su 
autor y no representa necesariamente la opinión de la empresa. Si ha recibido 
este mensaje por error, le rogamos nos lo comunique de forma inmediata por esta 
misma vía y proceda a su eliminación, así como a la de cualquier documento 
adjunto al mismo. El correo electrónico vía Internet no es seguro y no se puede 
garantizar que no haya errores ya que puede ser interceptado, modificado, 
perdido o destruido, o contener virus. Cualquier persona que se ponga en 
contacto con nosotros por correo electrónico se considerará que asume estos 
riesgos.

This e-mail is addressed exclusively to the recipient and may contain 
privileged information under a professional confidential agreement or it may be 
against the law to disclose its contents. Any opinion contained in it belongs 
exclusively to his/her author and does not necessarily reflect the company's 
view. If you receive this e-mail in error, please let us know immediately (by 
return e-mail) and proceed to its destruction, as well as any document attached 
to it. The sending of e-mails through the Internet is not safe and, therefore, 
error-free communications cannot be guaranteed, as they can be intercepted, 
changed, misled or destroyed or they might contain a virus. Any user contacting 
us through e-mails shall be understood to be assuming these risks.
==___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] why is s-mac not implemented for CC2420-based platforms in TOS2?

2008-05-13 Thread Erwing R. Sanchez

Hi Abhishek,
you're right! It seems that a great deal of the work has already been  
done. I'll try to stick a little bit more on my implementation,  
because I need it anyway, but it doesn't seem to have a brigth future...



Le 9 mai 08 à 04:11, abhishek chanani a écrit :


Hi Erwing,

Thanks for your reply. I am not sure how long I ll stick around with  
this project but do have a look at the paper A Component-Based  
Architecture for Power-Efficient Media
Access Control in Wireless Sensor Networks by Kevin Klues∗ ,  
Gregory Hackmann, Octav Chipara, Chenyang Lu.


I think they have already done a lot of the work.

On Thu, May 8, 2008 at 8:15 PM, Erwing R. Sanchez [EMAIL PROTECTED] 
 wrote:


Le 8 mai 08 à 15:24, abhishek chanani a écrit :


Hi Erwing,

Just wanted to know whats your progress in implementing S-MAC on the  
telosb platform. I m doing some similar work and thought you might  
be able to help.



Hi Abhishek,
I'm still working on it. At first I wanted to port the code from  
tos1 on top of platform-specific modules in tos2. That'd allow the  
code to be used with any platform; however I realized that'll be a  
lot of work so now I'm just focusing only on telosb and its cc2420  
stack. My idea is to re-use  the tinyos2 stack as much as possible,  
and that means, basically, that I'm trying to insert the s-mac layer  
into the ActiveMessage stack (speciffically on top of CsmaC). This  
is just my approach, and I think it makes sense but I will be  
willing to discuss with you any other ideas.

Erwing



--
Regards,
Abhishek Chanani
Academic Affairs Secretary,
315-Mandakini Hostel
Indian Institute of Technology, Madras
Mobile: +919444005765
Phone: (044) 22578540
[EMAIL PROTECTED]


___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Reading ADC values in atmega128L using TinyOS 2x platform

2008-05-13 Thread Shikhar Sachan
Greetings
I am facing slight difficulty in reading values directly from the ADC
pins in my MicaZ motes.
I need to retrieve values from ADC1,2 and 3. In tinyOS 1x,there was an
ADC interface defined which could be used.

However, this is not the case in tinyos 2x because of so much abstraction.
I would be thankful if someone could pass me on the code.

regards
Shikhar
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] Fwd: Reading ADC values in atmega128L using TinyOS 2x platform

2008-05-13 Thread Shikhar Sachan
Greetings
 I am facing slight difficulty in reading values directly from the ADC
 pins in my MicaZ motes.
 I need to retrieve values from ADC1,2 and 3. In tinyOS 1x,there was an
 ADC interface defined which could be used.

 However, this is not the case in tinyos 2x because of so much abstraction.
 I would be thankful if someone could pass me on the code.

 regards
 Shikhar
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] Low Power Listening

2008-05-13 Thread Nitin Sharma
For Low Power Listening in the default Tinyos 2.x cvs stack
(Box-MAC-2?) , the two interfaces as below:

command void setLocalSleepInterval(uint16_t sleepIntervalMs);
command void setRxSleepInterval(message_t *msg, uint16_t sleepIntervalMs);

The Node (Receiver and Transmitter) would set its local sleep interval
from the first command. The Receiver of course, if is peer-to-peer
synchronized following the same sleep interval would be awake at that
interval for receive check ? Why do we need to set the interval on the
packet we're sending?

Please let me understand.

Thanks

-- 
Nitin Sharma
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


Re: [Tinyos-help] Fwd: Reading ADC values in atmega128L using TinyOS 2x platform

2008-05-13 Thread Philip Levis

On May 13, 2008, at 11:04 AM, Shikhar Sachan wrote:

 Greetings
 I am facing slight difficulty in reading values directly from the ADC
 pins in my MicaZ motes.
 I need to retrieve values from ADC1,2 and 3. In tinyOS 1x,there was an
 ADC interface defined which could be used.

 However, this is not the case in tinyos 2x because of so much  
 abstraction.
 I would be thankful if someone could pass me on the code.


Please take a look at

platform/mica/VoltageC.nc
platform/mica/VoltageP.nc

They show how to write a simple ADC sample. VoltageP is just 3 lines  
of code that tell the ADC how to be configured for the sample.

Phil
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


Re: [Tinyos-help] Low Power Listening

2008-05-13 Thread Janos Sallai
Nitin,

 Why do we need to set the interval on the
 packet we're sending?
Because the recipient of the message may have a different sleep interval
from that of the sender.

LPL is explained in TEP 105, which is available at
http://www.tinyos.net/tinyos-2.x/doc/html/tep105.html .

Also, I recommend that you also read
http://docs.tinyos.net/index.php/Writing_Low-Power_Applications .

Janos

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nitin
Sharma
Sent: Tuesday, May 13, 2008 1:08 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [Tinyos-help] Low Power Listening

For Low Power Listening in the default Tinyos 2.x cvs stack
(Box-MAC-2?) , the two interfaces as below:

command void setLocalSleepInterval(uint16_t sleepIntervalMs);
command void setRxSleepInterval(message_t *msg, uint16_t
sleepIntervalMs);

The Node (Receiver and Transmitter) would set its local sleep interval
from the first command. The Receiver of course, if is peer-to-peer
synchronized following the same sleep interval would be awake at that
interval for receive check ? Why do we need to set the interval on the
packet we're sending?

Please let me understand.

Thanks

-- 
Nitin Sharma
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


Re: [Tinyos-help] Low Power Listening

2008-05-13 Thread David Moss
Your node has a local sleep interval defining how often the radio wakes up
to perform a receive check.

Other nodes in the vicinity may have different sleep intervals.  For
example, maybe you have a node nearby that is not actually part of your
network and is awake all the time.

It would be bad to assume that every node around your node is on the same
sleep schedule.  Therefore, your node must specify the destination's sleep
interval before sending the packet, which may be different than your local
sleep interval.  That way the radio stack will know how to deliver the
packet to its intended destination.

-David



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nitin
Sharma
Sent: Tuesday, May 13, 2008 11:08 AM
To: tinyos-help@millennium.berkeley.edu
Subject: [Tinyos-help] Low Power Listening

For Low Power Listening in the default Tinyos 2.x cvs stack
(Box-MAC-2?) , the two interfaces as below:

command void setLocalSleepInterval(uint16_t sleepIntervalMs);
command void setRxSleepInterval(message_t *msg, uint16_t sleepIntervalMs);

The Node (Receiver and Transmitter) would set its local sleep interval
from the first command. The Receiver of course, if is peer-to-peer
synchronized following the same sleep interval would be awake at that
interval for receive check ? Why do we need to set the interval on the
packet we're sending?

Please let me understand.

Thanks

-- 
Nitin Sharma
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


Re: [Tinyos-help] Low Power Listening

2008-05-13 Thread Nitin Sharma
Thanks Janos and David.

I have got yet another query.

So i assume, the transmitter could decide to send as soon as it has a
packet to send and the radio is on .And keep on retransmitting (within
the receive check period interval ) unless acked or timeout.

http://docs.tinyos.net/index.php/Writing_Low-Power_Applications says
The transmitter stops sending once it receives a link-layer
acknowledgment or a timeout of twice the check period.

My concern is for a recipient with a relatively longer schedule. Does
it keep on retrying for twice the check period in the worst case? Any
insight into how many retransmissions?

Thanks again.

Nitin


On Tue, May 13, 2008 at 1:46 PM, David Moss [EMAIL PROTECTED] wrote:
 Your node has a local sleep interval defining how often the radio wakes up
  to perform a receive check.

  Other nodes in the vicinity may have different sleep intervals.  For
  example, maybe you have a node nearby that is not actually part of your
  network and is awake all the time.

  It would be bad to assume that every node around your node is on the same
  sleep schedule.  Therefore, your node must specify the destination's sleep
  interval before sending the packet, which may be different than your local
  sleep interval.  That way the radio stack will know how to deliver the
  packet to its intended destination.

  -David




  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of Nitin
  Sharma

 Sent: Tuesday, May 13, 2008 11:08 AM
  To: tinyos-help@millennium.berkeley.edu
  Subject: [Tinyos-help] Low Power Listening



 For Low Power Listening in the default Tinyos 2.x cvs stack
  (Box-MAC-2?) , the two interfaces as below:

  command void setLocalSleepInterval(uint16_t sleepIntervalMs);
  command void setRxSleepInterval(message_t *msg, uint16_t sleepIntervalMs);

  The Node (Receiver and Transmitter) would set its local sleep interval
  from the first command. The Receiver of course, if is peer-to-peer
  synchronized following the same sleep interval would be awake at that
  interval for receive check ? Why do we need to set the interval on the
  packet we're sending?

  Please let me understand.

  Thanks

  --
  Nitin Sharma


 ___
  Tinyos-help mailing list
  Tinyos-help@millennium.berkeley.edu
  https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help






-- 
Nitin Sharma
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] Modifying TestSerial.h - nx_uint16_t to nx_uint8_t

2008-05-13 Thread Daniel Pereira
Dear all,

I'm creating a new protocol to transfer data between the computer and PC.
So, I have modified the struct test_serial_msg as follow:

typedef nx_struct test_serial_msg {
   nx_uint8_t counter;
} test_serial_msg_t;

But the TestSerialMsg has been created with counter as short.

What is wrong?

Thanks all
Daniel Patrick
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


Re: [Tinyos-help] Low Power Listening

2008-05-13 Thread David Moss
I've updated this wiki doc:

The transmitter stops sending once it receives a link-layer acknowledgment
or a timeout. The timeout is a few milliseconds longer than the receiver's
check period.

We no longer transmit for twice the receive check period because receive
check reliability has increased since 2.0.1.

Worst case is your transmitter will transmit for a few milliseconds longer
than the destination's receive check period.

-David



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nitin
Sharma
Sent: Tuesday, May 13, 2008 12:58 PM
To: tinyos-help@millennium.berkeley.edu
Subject: Re: [Tinyos-help] Low Power Listening

Thanks Janos and David.

I have got yet another query.

So i assume, the transmitter could decide to send as soon as it has a
packet to send and the radio is on .And keep on retransmitting (within
the receive check period interval ) unless acked or timeout.

http://docs.tinyos.net/index.php/Writing_Low-Power_Applications says
The transmitter stops sending once it receives a link-layer
acknowledgment or a timeout of twice the check period.

My concern is for a recipient with a relatively longer schedule. Does
it keep on retrying for twice the check period in the worst case? Any
insight into how many retransmissions?

Thanks again.

Nitin


On Tue, May 13, 2008 at 1:46 PM, David Moss [EMAIL PROTECTED] wrote:
 Your node has a local sleep interval defining how often the radio wakes up
  to perform a receive check.

  Other nodes in the vicinity may have different sleep intervals.  For
  example, maybe you have a node nearby that is not actually part of your
  network and is awake all the time.

  It would be bad to assume that every node around your node is on the same
  sleep schedule.  Therefore, your node must specify the destination's
sleep
  interval before sending the packet, which may be different than your
local
  sleep interval.  That way the radio stack will know how to deliver the
  packet to its intended destination.

  -David




  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of Nitin
  Sharma

 Sent: Tuesday, May 13, 2008 11:08 AM
  To: tinyos-help@millennium.berkeley.edu
  Subject: [Tinyos-help] Low Power Listening



 For Low Power Listening in the default Tinyos 2.x cvs stack
  (Box-MAC-2?) , the two interfaces as below:

  command void setLocalSleepInterval(uint16_t sleepIntervalMs);
  command void setRxSleepInterval(message_t *msg, uint16_t
sleepIntervalMs);

  The Node (Receiver and Transmitter) would set its local sleep interval
  from the first command. The Receiver of course, if is peer-to-peer
  synchronized following the same sleep interval would be awake at that
  interval for receive check ? Why do we need to set the interval on the
  packet we're sending?

  Please let me understand.

  Thanks

  --
  Nitin Sharma


 ___
  Tinyos-help mailing list
  Tinyos-help@millennium.berkeley.edu
  https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help






-- 
Nitin Sharma
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


Re: [Tinyos-help] Modifying TestSerial.h - nx_uint16_t to nx_uint8_t

2008-05-13 Thread Philip Levis

On May 13, 2008, at 1:13 PM, Daniel Pereira wrote:

 Dear all,

 I'm creating a new protocol to transfer data between the computer  
 and PC.
 So, I have modified the struct test_serial_msg as follow:

 typedef nx_struct test_serial_msg {
   nx_uint8_t counter;
 } test_serial_msg_t;

 But the TestSerialMsg has been created with counter as short.

 What is wrong?

Nothing is wrong. Java does not have unsigned types. So to represent  
values in the range of 0 to +255, a byte (-128 to +127) is  
insufficient and you need a short (-32768 to +32767).

Phil

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] Linking C files into Tinyos

2008-05-13 Thread Hugh Hartwig
I am attempting to compile and link c code into tinyos-1.x.  So far I have
been able to include c files at the top of NESC files, but this appears to
make everything inline, thus taking up significant code and memory space.
Is there a way to compile and link the C files such that they aren't created
inline?  

 

Thanks,

Hugh

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] NESC Linking

2008-05-13 Thread Hugh Hartwig
How is linking performed in tinyos-1.x and is there a *.lnk or similar file
somewhere?

 

Thanks,

Hugh

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help