date:20051215


Hi Sankar,

look at contrib/xbow/beta/tools/src/xcmd. That's what I'm using to command 
my motes. You can give the mote ID on the command line.


Regards,

Harri

At 01:41 PM 12/14/2005 -0600, Sankar Gorthi wrote:

Hi,

Quick newbie doubt. Has any code been written to address a particular node
in a network?

Basically trying to run a command like "put node no. X to sleep".

Thanks,

Sankar Gorthi.
___
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] 802.15.4 ACKs

2005-12-15 Thread Martin Gercke


Hi,

I have a small question about acknowledgments in 802.15.4.
According to the standard they don't hold any address information. 
Neither source nor destination.
So, in a PAN with many devices all in radio reach of each other it could 
happen that 2 messages are send with the same DSN from 2 different motes 
(e.g. A->B and C->D),
messages from A-B gets acknowledged but message from C->D is lost. Since 
both messages have the same DSN C could confuse ACK send from B->A with 
the one he's waiting for, right?


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

[Tinyos-help] TinyOS 2.x how best to support timers

2005-12-15 Thread Cormac Duffy

HI, I am porting tinyos 2.x to the dsys25z, its a platform very similar
in architecture to the miaz, in that it has an atmega128 processor and a
cc2420 radio. Unfortunately the architecture doesnt support a 32khz
external oscillator to externally clock timer0 as in the case of the
micaz. After looking up the atmega128 source tree i noticed that the
AlarmCounterMilliC.nc passes in prescaler values directly to the
hardware components, so there seems to not be too much flexibilty,
unless I change that file (obviously any changes I make I would like to
just keep to my platform directory).  

So i recon because I dont have this 32khz oscillator, i cant prescale
the timer to a millisecond, so i suppose the best thing to do would be
prescale the 8mhz oscillator as far down as i can and use a variable to
prescale the rest maybe interrupt it processor when it reaches a number
or something. Any advice for implementing it, it terms of specific
components i should use where to put the director wise etc. Alss the
best Cormac
   

Cormac Duffy B.Sc, M.Sc Computer Science Dept. University College
Cork, College Rd., Cork, Ireland. 

email: [EMAIL PROTECTED] telephone: 0872039750 


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

Re: [Tinyos-help] 802.15.4 ACKs

2005-12-15 Thread Arnau Quintana

Hi Martin,

I am not really an expert in 802.15.4 but I have thought about your question.

I suppose you are assuming a mesh topology, where nodes are allowed to
transmit and receive information between them, not only with the
PAN coordinator.

In this kind of peer-to-peer topologies, the standard does not specifies anything about ACK's, as it says un section 5.4.2.3.

>From my point of view, there would be no problem in confusing the
ACK's. In P2P topoplogy, without using a synchronization mechanism,
nodes should "listen" constantly to the channel, and send frames using
unslotted CSMA-CA.

These means that if A is sending a message to B, and C wants to
transmit at the same time, C would perform a channel sensing. When it
detects the ongoing transmission (A<-->B) it should backoff and
try again later on. The backoff perdid should be long enough to allow A
and B to finish their communication (including ACK's and other
messages). Then, if C uses the same DSN, there would no problem of
confused ACK's, because A and B would have ended their transmissions.

An ACK frame is only "correct" in the context of the communication established between two nodes.

However, this can be a problem when using differents PAN's. In this
case a node could confuse ACK frames, but I think this is covered also
in the standard.

A - B
|
|
|
|
C --- D

PAN1 = A and B
PAN2 = B and C
PAN3 = C and D

In this case there could be some problems. Let's suppose B sends a
message to A and waits for the ACK, and at the same time D sends a
message to C and also waits for ACK. This can happen because when D
performs channel sensing, it does not "hear" the transmission from B.

If the ACK form A is lost, B could still receive an ACK from C,
(destined to D) because it is in his coverage area. If DSN field is the
same, a confusion can happen.

I am not an expert of 802.15.4 and I think this aspect is taken on account on the standard, but now I can not remember exactly.

Maybe I am not right, so any remarks, comments or further explanations would be welcomed.

I hope this can help you.
Regards,

Arnau Quintana

On 12/15/05, Martin Gercke <[EMAIL PROTECTED]> wrote:
Hi,I have a small question about acknowledgments in 802.15.4.According to the standard they don't hold any address information.Neither source nor destination.So, in a PAN with many devices all in radio reach of each other it could
happen that 2 messages are send with the same DSN from 2 different motes(e.g. A->B and C->D),messages from A-B gets acknowledged but message from C->D is lost. Sinceboth messages have the same DSN C could confuse ACK send from B->A with
the one he's waiting for, right?Martin___Tinyos-help mailing listTinyos-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] XMTS310 not sleeping?




Hi,

I've understood that the XMesh apps use power saving by default. After 
studying the sources, I noticed that I should "#define FEATURE_UART_SEND = 
1" (and program with ID other than 0) to include the parts that call 
PowerMgrEnable(). I did, but observing the current consumption shows it 
won't go into power save. What am I doing wrong?


(Platform = MicaZ)

Thanks in advance,

Harri

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

Re: [Tinyos-help] TinyOS 2.x how best to support timers

I'm more of an MSP430 guy, so others can comment better about
particular choices for the ATMega128 platform.

But from the sound of it, yes, scale the 8MHz clock down.  If you
scale to some precision that isn't 32khz or microseconds, then define
a custom timer precision tag for it in your platform.  Then use the
timer library helper components -- specifically, TransformCounterC and
TransformAlarmC -- to convert it the rest of the way to 32khz.

See TEP 102 Timers in tinyos-1.x/beta/teps/.

Hope that helps, best,
Cory

On 12/15/05, Cormac Duffy <[EMAIL PROTECTED]> wrote:
> HI, I am porting tinyos 2.x to the dsys25z, its a platform very similar
> in architecture to the miaz, in that it has an atmega128 processor and a
> cc2420 radio. Unfortunately the architecture doesnt support a 32khz
> external oscillator to externally clock timer0 as in the case of the
> micaz. After looking up the atmega128 source tree i noticed that the
> AlarmCounterMilliC.nc passes in prescaler values directly to the
> hardware components, so there seems to not be too much flexibilty,
> unless I change that file (obviously any changes I make I would like to
> just keep to my platform directory).
>
> So i recon because I dont have this 32khz oscillator, i cant prescale
> the timer to a millisecond, so i suppose the best thing to do would be
> prescale the 8mhz oscillator as far down as i can and use a variable to
> prescale the rest maybe interrupt it processor when it reaches a number
> or something. Any advice for implementing it, it terms of specific
> components i should use where to put the director wise etc. Alss the
> best Cormac
>
>
> Cormac Duffy B.Sc, M.Sc Computer Science Dept. University College
> Cork, College Rd., Cork, Ireland.
>
> email: [EMAIL PROTECTED] telephone: 0872039750
>
>
> ___
> 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] TinyOS 2.x how best to support timers

On 12/15/05, Cory Sharp <[EMAIL PROTECTED]> wrote:
> See TEP 102 Timers in tinyos-1.x/beta/teps/.

Check that, see tinyos-2.x/doc/.

- Cory

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

[Tinyos-help] Time needed between send and receive.

2005-12-15 Thread Terence Joseph


Hi All,

I am using the Tmote Sky.  Assume Node A is sending a value to Node B who 
upon receipt of this message resends some other value back to node A 
straight away.  Is there any problems that might occur in this scenario?  
For example is it possible that node A may not have time to switch to 
receive mode after it has sent its message and therefore miss the message 
from Node B?  The reason I ask is I have a similar setup and Node A doesn't 
appear to be receiving anything at all but is sending.  Any ideas on a 
solution?


Best Regards,
Terence

_
Search and browse smarter - get MSN Search Toolbar with Desktop Search! 
http://toolbar.msn.ie


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

Re: [Tinyos-help] Time needed between send and receive.

2005-12-15 Thread Andrea Pacini


Yes this is the same problem , I think, that I have met some time ago.
The problem is that when a node sends a message the other node receives 
this message ONLY IF it is not running any code.
(only in this case the receive event is triggered). It seems that the 
node cannot buffer the RECEIVE event if it is running something.
So , if you want that a node receives surely a message you must write 
your code so that when it should receive a message it has run

all the previous code.
It is a strange behaviour in my opinion, I don't know if it is only for 
Tmote Sky (TelosB) or for all platforms.


To highlight this behaviour try these situation:

NODE A: 
NODE B:


[...]  
  event Receive (){ call Leds.redOn(); }
call Send();  // sends something
StdControl.start () { }

[]

Node B does nothing; it only waits for A message. Clearly, it receives 
the message from A.

Now try these:

NODE A: 
NODE B:


[...]  
  event Receive (){ call Leds.redOn(); }
call Send();  // sends something
StdControl.start () { 
[]   
for (i=0;i<500;i++) ;
   
}


Now A sends a message while B is running a FOR cycle (make sure that A 
sends its message while B is running the for cycle)
You should see that red Led doesn't turn on, because the Receive event 
seems to be "LOST".



Andrea


Terence Joseph wrote:


Hi All,

I am using the Tmote Sky.  Assume Node A is sending a value to Node B 
who upon receipt of this message resends some other value back to node 
A straight away.  Is there any problems that might occur in this 
scenario?  For example is it possible that node A may not have time to 
switch to receive mode after it has sent its message and therefore 
miss the message from Node B?  The reason I ask is I have a similar 
setup and Node A doesn't appear to be receiving anything at all but is 
sending.  Any ideas on a solution?


Best Regards,
Terence

_
Search and browse smarter - get MSN Search Toolbar with Desktop 
Search! http://toolbar.msn.ie


___
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] Time needed between send and receive.



Can't this situation be helped by changing the receive evens to async?

Harri

At 12:58 PM 12/15/2005 +0100, Andrea Pacini wrote:

Yes this is the same problem , I think, that I have met some time ago.
The problem is that when a node sends a message the other node receives 
this message ONLY IF it is not running any code.
(only in this case the receive event is triggered). It seems that the node 
cannot buffer the RECEIVE event if it is running something.
So , if you want that a node receives surely a message you must write your 
code so that when it should receive a message it has run

all the previous code.
It is a strange behaviour in my opinion, I don't know if it is only for 
Tmote Sky (TelosB) or for all platforms.


To highlight this behaviour try these situation:

NODE A:
NODE B:

[...] 


  event Receive (){ call Leds.redOn(); }
call Send();  // sends something
StdControl.start () { }
[]

Node B does nothing; it only waits for A message. Clearly, it receives the 
message from A.

Now try these:

NODE A:
NODE B:

[...] 


  event Receive (){ call Leds.redOn(); }
call Send();  // sends something
StdControl.start () { 
[] 


for (i=0;i<500;i++) ;


}

Now A sends a message while B is running a FOR cycle (make sure that A 
sends its message while B is running the for cycle)
You should see that red Led doesn't turn on, because the Receive event 
seems to be "LOST".



Andrea


Terence Joseph wrote:


Hi All,

I am using the Tmote Sky.  Assume Node A is sending a value to Node B who 
upon receipt of this message resends some other value back to node A 
straight away.  Is there any problems that might occur in this 
scenario?  For example is it possible that node A may not have time to 
switch to receive mode after it has sent its message and therefore miss 
the message from Node B?  The reason I ask is I have a similar setup and 
Node A doesn't appear to be receiving anything at all but is 
sending.  Any ideas on a solution?


Best Regards,
Terence

_
Search and browse smarter - get MSN Search Toolbar with Desktop Search! 
http://toolbar.msn.ie


___
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 mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Time needed between send and receive.

2005-12-15 Thread Andrea Pacini


But we need to change TinyOS system files and all dependencies ?
Because simply declaring :

async event Receive ...

doesn't work because compiler plains about previous declaration of receive.
Anyway if I remember correctly , when async word misses, automatically
the behaviour is set to asyncronous.

Harri Siirtola wrote:



Can't this situation be helped by changing the receive evens to async?

Harri

At 12:58 PM 12/15/2005 +0100, Andrea Pacini wrote:


Yes this is the same problem , I think, that I have met some time ago.
The problem is that when a node sends a message the other node 
receives this message ONLY IF it is not running any code.
(only in this case the receive event is triggered). It seems that the 
node cannot buffer the RECEIVE event if it is running something.
So , if you want that a node receives surely a message you must write 
your code so that when it should receive a message it has run

all the previous code.
It is a strange behaviour in my opinion, I don't know if it is only 
for Tmote Sky (TelosB) or for all platforms.


To highlight this behaviour try these situation:

NODE A:
NODE B:

[...]
  event Receive (){ call Leds.redOn(); }
call Send();  // sends something
StdControl.start () { }
[]

Node B does nothing; it only waits for A message. Clearly, it 
receives the message from A.

Now try these:

NODE A:
NODE B:

[...]
  event Receive (){ call Leds.redOn(); }
call Send();  // sends something
StdControl.start () { []
for (i=0;i<500;i++) ;


}

Now A sends a message while B is running a FOR cycle (make sure that 
A sends its message while B is running the for cycle)
You should see that red Led doesn't turn on, because the Receive 
event seems to be "LOST".



Andrea


Terence Joseph wrote:


Hi All,

I am using the Tmote Sky.  Assume Node A is sending a value to Node 
B who upon receipt of this message resends some other value back to 
node A straight away.  Is there any problems that might occur in 
this scenario?  For example is it possible that node A may not have 
time to switch to receive mode after it has sent its message and 
therefore miss the message from Node B?  The reason I ask is I have 
a similar setup and Node A doesn't appear to be receiving anything 
at all but is sending.  Any ideas on a solution?


Best Regards,
Terence

_
Search and browse smarter - get MSN Search Toolbar with Desktop 
Search! http://toolbar.msn.ie


___
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 mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Time needed between send and receive.



Obviously this would be a job for the TinyOS authors if that's the case. 
Your second thought cannot be true, how could you declare sync events in 
that case?


Regards,
Harri

At 02:04 PM 12/15/2005 +0100, Andrea Pacini wrote:

But we need to change TinyOS system files and all dependencies ?
Because simply declaring :

async event Receive ...

doesn't work because compiler plains about previous declaration of receive.
Anyway if I remember correctly , when async word misses, automatically
the behaviour is set to asyncronous.

Harri Siirtola wrote:



Can't this situation be helped by changing the receive evens to async?

Harri

At 12:58 PM 12/15/2005 +0100, Andrea Pacini wrote:


Yes this is the same problem , I think, that I have met some time ago.
The problem is that when a node sends a message the other node receives 
this message ONLY IF it is not running any code.
(only in this case the receive event is triggered). It seems that the 
node cannot buffer the RECEIVE event if it is running something.
So , if you want that a node receives surely a message you must write 
your code so that when it should receive a message it has run

all the previous code.
It is a strange behaviour in my opinion, I don't know if it is only for 
Tmote Sky (TelosB) or for all platforms.


To highlight this behaviour try these situation:

NODE A:
NODE B:

[...]
  event Receive (){ call Leds.redOn(); }
call Send();  // sends something
StdControl.start () { }
[]

Node B does nothing; it only waits for A message. Clearly, it receives 
the message from A.

Now try these:

NODE A:
NODE B:

[...]
  event Receive (){ call Leds.redOn(); }
call Send();  // sends something
StdControl.start () { []
for (i=0;i<500;i++) ;


}

Now A sends a message while B is running a FOR cycle (make sure that A 
sends its message while B is running the for cycle)
You should see that red Led doesn't turn on, because the Receive event 
seems to be "LOST".



Andrea


Terence Joseph wrote:


Hi All,

I am using the Tmote Sky.  Assume Node A is sending a value to Node B 
who upon receipt of this message resends some other value back to node 
A straight away.  Is there any problems that might occur in this 
scenario?  For example is it possible that node A may not have time to 
switch to receive mode after it has sent its message and therefore miss 
the message from Node B?  The reason I ask is I have a similar setup 
and Node A doesn't appear to be receiving anything at all but is 
sending.  Any ideas on a solution?


Best Regards,
Terence

_
Search and browse smarter - get MSN Search Toolbar with Desktop Search! 
http://toolbar.msn.ie


___
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 mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Time needed between send and receive.

2005-12-15 Thread Martin Gercke

Are you sure that this behaviour has nothing to do with the fact that 
you call your loop in StdControl.start?
E.g. you could try to drop a task in the StdControl.start and see if the 
problem still persists.
I doubt that this would cause any problems since the packets are 
received in an interrupt and any function run in that interrupt will be 
called directly, right?

Not too sure about this though.

Martin


Andrea Pacini wrote:


Yes this is the same problem , I think, that I have met some time ago.
The problem is that when a node sends a message the other node 
receives this message ONLY IF it is not running any code.
(only in this case the receive event is triggered). It seems that the 
node cannot buffer the RECEIVE event if it is running something.
So , if you want that a node receives surely a message you must write 
your code so that when it should receive a message it has run

all the previous code.
It is a strange behaviour in my opinion, I don't know if it is only 
for Tmote Sky (TelosB) or for all platforms.


To highlight this behaviour try these situation:

NODE 
A: 
NODE B:


[...]  
  event Receive (){ call Leds.redOn(); }
call Send();  // sends something
StdControl.start () { }

[]

Node B does nothing; it only waits for A message. Clearly, it receives 
the message from A.

Now try these:

NODE 
A: 
NODE B:


[...]  
  event Receive (){ call Leds.redOn(); }
call Send();  // sends something
StdControl.start () { 
[]   
for (i=0;i<500;i++) ;
   
}


Now A sends a message while B is running a FOR cycle (make sure that A 
sends its message while B is running the for cycle)
You should see that red Led doesn't turn on, because the Receive event 
seems to be "LOST".



Andrea


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

[Tinyos-help] Every motes acts as a router??

2005-12-15 Thread Silvia


Hello!
I´m trying to do an application in order that the motes transmit radio
messages to the most nearby neighbor and this one will do the same thing, up
to coming to the base. Does the application Surge_Reliable do this? Looking
at the code of SurgeM.nc I don´t find anything that the motes do when they
receive a message of another mote...

Is there any application that makes this, already implemented?
I´m grateful for any type of information about it.

Thank you very much!



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

Re: [Tinyos-help] Every motes acts as a router??



Yes, Surge_Reliable does it. Forwarding is taken care of in the lower 
(Router) levels, that's why you don't see it in the application file.


Regards,
Harri

At 02:47 PM 12/15/2005 +0100, Silvia wrote:


Hello!
I´m trying to do an application in order that the motes transmit radio
messages to the most nearby neighbor and this one will do the same thing, up
to coming to the base. Does the application Surge_Reliable do this? Looking
at the code of SurgeM.nc I don´t find anything that the motes do when they
receive a message of another mote...

Is there any application that makes this, already implemented?
I´m grateful for any type of information about it.

Thank you very much!



___
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] Read packets from SerialForwarder in java

2005-12-15 Thread Chalermphol Thammapalerd

Hi Daniel,
 
In this case, You may extract the information seperately by using the OscopeMsg class.
Then try it's methods like get_sourceMoteID(), get_channel() or else.
 
However, have you tried the "Listen" tool?
The usage is "java net.tinyos.tools.Listen".
 
Good Luck,
Chalermphol 
On 12/15/05, Daniel Larsson <[EMAIL PROTECTED]> wrote:
HiI'm using OscilloscopeRF together with TOSBase and SerialForwarder to make the packets available over the network.
I was able to connect to the SerialForwarder server on port 9001, but how do I read the packets and extract the information from them in java?The start of my code looks something like this:Socket sock = new Socket(server_name, TCP_PORT);
DataInputStream is = new DataInputStream(    new BufferedInputStream(sock.getInputStream( )));    Regards, Daniel ___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] XNP working in 1.1.14?

2005-12-15 Thread 刘巍

Liu, Ping \(Research\),您好！

In tinyos1.1.14,I also can not find XNP support.Maybe it is not stable 
i think.Why not use Deluge2.0 in tinyos1.1.14

=== 2005-12-14 11:59:24 您在来信中写道：===

>Hi, 
>
>Just wondering if XNP is still working in 1.1.14?  The "TOS In-Network 
>Programming User Reference" mentioned that it needs to be on ATMega128, not 
>sure if it works on MSP430 as well.  Also, does it work on micaz platform? 
>
>Any information would be very much appreciated! 
>
>Thanks,
>-Tiffany
>
>___
>Tinyos-help mailing list
>Tinyos-help@Millennium.Berkeley.EDU
>https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

= = = = = = = = = = = = = = = = = = = =


致
礼！
 
 
刘巍
[EMAIL PROTECTED]
　　2005-12-15


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

Re: [Tinyos-help] Addressing node by id

2005-12-15 Thread Sankar Gorthi


Thank You Tran and Harri.

Sankar.


On Thu, 15 Dec 2005 03:32:55 -0600, Harri Siirtola <[EMAIL PROTECTED]>  
wrote:



Hi Sankar,

look at contrib/xbow/beta/tools/src/xcmd. That's what I'm using to  
command my motes. You can give the mote ID on the command line.


Regards,

 Harri

At 01:41 PM 12/14/2005 -0600, Sankar Gorthi wrote:

Hi,

Quick newbie doubt. Has any code been written to address a particular  
node

in a network?

Basically trying to run a command like "put node no. X to sleep".

Thanks,

Sankar Gorthi.
___
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 mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Time needed between send and receive.

2005-12-15 Thread Andrea Pacini


Yes, I have tested also this variant but with the same results:

void task dummy_task() {
   uint32_t i;
call Leds.redOn();  
for (i=0;i<500;i++) ; 
call Leds.redOff();
  }


 command result_t StdControl.start(){
   post dummy_task();
   return SUCCESS;
}

The receive event IS NOT TRIGGERED during the task.

Martin Gercke wrote:

Are you sure that this behaviour has nothing to do with the fact that 
you call your loop in StdControl.start?
E.g. you could try to drop a task in the StdControl.start and see if 
the problem still persists.
I doubt that this would cause any problems since the packets are 
received in an interrupt and any function run in that interrupt will 
be called directly, right?

Not too sure about this though.

Martin


Andrea Pacini wrote:


Yes this is the same problem , I think, that I have met some time ago.
The problem is that when a node sends a message the other node 
receives this message ONLY IF it is not running any code.
(only in this case the receive event is triggered). It seems that the 
node cannot buffer the RECEIVE event if it is running something.
So , if you want that a node receives surely a message you must write 
your code so that when it should receive a message it has run

all the previous code.
It is a strange behaviour in my opinion, I don't know if it is only 
for Tmote Sky (TelosB) or for all platforms.


To highlight this behaviour try these situation:

NODE 
A: 
NODE B:


[...]  
  event Receive (){ call Leds.redOn(); }
call Send();  // sends something
StdControl.start () { }

[]

Node B does nothing; it only waits for A message. Clearly, it 
receives the message from A.

Now try these:

NODE 
A: 
NODE B:


[...]  
  event Receive (){ call Leds.redOn(); }
call Send();  // sends something
StdControl.start () { 
[]   
for (i=0;i<500;i++) ;
   
}


Now A sends a message while B is running a FOR cycle (make sure that 
A sends its message while B is running the for cycle)
You should see that red Led doesn't turn on, because the Receive 
event seems to be "LOST".



Andrea



___
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: Re: [Tinyos-help] XNP working in 1.1.14?

2005-12-15 Thread 刘巍

Hi,

Does Deluge support mica2?Why not mentioned it in your support list?

=== 2005-12-15 01:04:27 您在来信中写道：===

>Hi,
>
>It's the old protocol which was already replaced by Deluge.
>Deluge works with both telos and micaz. I haven't seen any action on
>XNP for some time.
>
>Krisakorn
>
>On 12/14/05, Liu, Ping (Research) <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> Just wondering if XNP is still working in 1.1.14?  The "TOS In-Network 
>> Programming User Reference" mentioned that it needs to be on ATMega128, not 
>> sure if it works on MSP430 as well.  Also, does it work on micaz platform?
>>
>> Any information would be very much appreciated!
>>
>> Thanks,
>> -Tiffany
>>
>> ___
>> 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

= = = = = = = = = = = = = = = = = = = =


致
礼！
 
 
   刘巍
   2005-12-15   
     
   中国科学院计算技术研究所  
   电话：010-62565533-9247 
   Mail:[EMAIL PROTECTED]   
   网址：http://wsn.ict.ac.cn 
   -



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

[Tinyos-help] event, command, atomic ...

2005-12-15 Thread Martin Gercke


Hi,

I am a little confused about this:

reading a tinyos tutorial (by Chien-Liang Fok) i noticed that there is 
code that is called async and some is called sync.
This is interested concerning shared variabels and the importance of 
using the atomic statement in these cases.
Events can interrupt tasks but two tasks cannot be interrupted by each 
other.
the tutorial also said "Do not confuse an event from the NesC event 
keyword!!"


So, just to sort things in my head: an event being a part of a 
components interface definition can be called in a task and would be 
sync code.
If it is called as result of an interrupt however the code would be 
async, right?


Martin

P.S.: What about variabels that are shared between to async functions? 
... will this be safe and if so, why?

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

Re: [Tinyos-help] event, command, atomic ...

On 12/15/05, Martin Gercke <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am a little confused about this:
>
> reading a tinyos tutorial (by Chien-Liang Fok) i noticed that there is
> code that is called async and some is called sync.
> This is interested concerning shared variabels and the importance of
> using the atomic statement in these cases.
> Events can interrupt tasks but two tasks cannot be interrupted by each
> other.
> the tutorial also said "Do not confuse an event from the NesC event
> keyword!!"
>
> So, just to sort things in my head: an event being a part of a
> components interface definition can be called in a task and would be
> sync code.
> If it is called as result of an interrupt however the code would be
> async, right?

Clearly, the terminology and explanations are still confusing ;-)
Partly because people aren't always paying attention to the difference
between:
- a function definition F
- all the code that might be executed if you call F (typically
includes lots of other functions)
A command or event is just a function definition. A task or interrupt
handler has a function definition (its entry point), but also (at
least in typical terminology) includes all the code that executes when
you call that entry point.

The rule for async is actually straightforward: if you want to be able
to call this command or event from an interrupt handler, it *must* be
marked async. Note also that the decision about whether something is
async or not is made in the interface definition. i.e., by the
interface designer rather than the component implementer.

Some of the confusion comes from the fact that some documentation uses
the word "event" to mean "interrupt handler". This is compounded by
the fact that the component based approach often leads to signaling
information about an interrupt using an "event" (in the
command-and-event sense).

As to atomic: if you consider when a data race can occur:
- tasks are run to completion one after another, so there can be no
data races between two tasks.
- interrupt handlers are "spontaneously" called by the hardware at
"any" time. So if a variable V is accessed by an interrupt handler,
there might be a race with any interrupt handler or task that also
accesses V (and note that because interrupts may be reentrant, there
is always the possibility of a data race with yourself).

Thus, any variable access in an interrupt handler might cause a data
race. Atomic is one way around this: the code in atomic statements is
guaranteed to run as-if no other code in an atomic statement is
executing at the same time (in practice, in nesC, this is done by
disabling interrupts). If you don't ensure that all accesses to
variables accessed from an interrupt handler are protected by atomic,
you will get a warning from the nesC compiler. You can disable these
warnings by adding a norace qualifier to the variable (if you know
that that particular race cannot occur for some reason).

David Gay

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

[Tinyos-help] is there any WiFi product has the same functionality as T-mote

2005-12-15 Thread yicheng









Hi Forks,

 

The same functionality means that the WiFi product
also has processor, memory and transceiver, which is battery driven, suitable
for development of different types of applications on it, the only difference
is that they use WiFi protocol instead of 802.15.4. I want to make a comparison
between them. Anybody knows it?

 

Thanks!

Yicheng






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

[Tinyos-help] TinyOS 2.X how best to support the timers

2005-12-15 Thread Cormac Duffy


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

[Tinyos-help] What could be the reason for "write failed" in serialForwarder

2005-12-15 Thread Liu, Ping \(Research\)

Hi, 

What could be the reason for "write failed" while trying the serialForwarder?

I am on 1.1.14. and serialForwarder was working fine for me earlier on 1.1.7. 

Thanks many!
-T.

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

[Tinyos-help] TOS_msg sendSecurityMode?

2005-12-15 Thread James Horey

Hi,

Does anyone mind telling me the purpose of the TOS_msg sendSecurityMode and 
receiveSecurityMode? Thanks.

-James Horey <[EMAIL PROTECTED]>


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

RE: [Tinyos-help] XMTS310 not sleeping?

2005-12-15 Thread Mudlagiri Baleri

Hello Harri,

It is correct that XMesh apps use power saving by default.

FEATURE_UART_SEND should be defined only if you want to debug the
application and have the packet sent to UART for data collection.
PowerMgrEnable() is called by XMesh by default.

To put the mote into sleep mode, just remove the "#define
FEATURE_UART_SEND = 1" in your makefile. 

Giri

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Harri
Siirtola
Sent: Thursday, December 15, 2005 2:50 AM
To: tinyos-help@Millennium.Berkeley.EDU
Subject: [Tinyos-help] XMTS310 not sleeping?



Hi,

I've understood that the XMesh apps use power saving by default. After
studying the sources, I noticed that I should "#define FEATURE_UART_SEND
= 1" (and program with ID other than 0) to include the parts that call
PowerMgrEnable(). I did, but observing the current consumption shows it
won't go into power save. What am I doing wrong?

(Platform = MicaZ)

Thanks in advance,

Harri

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

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

Re: [Tinyos-help] What could be the reason for "write failed" in serialForwarder

That's usually a mismatched baud rate -- the serial forwarder is
configured for a different baud rate than what the mote is using. 
This page, while not exactly appropriate for your problem, will give
you some idea about where you can look:

http://www.moteiv.com/community/Change_the_default_UART_baud_rate

Cory

On 12/15/05, Liu, Ping (Research) <[EMAIL PROTECTED]> wrote:
> Hi,
>
> What could be the reason for "write failed" while trying the serialForwarder?
>
> I am on 1.1.14. and serialForwarder was working fine for me earlier on 1.1.7.
>
> Thanks many!
> -T.
>
> ___
> 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] What could be the reason for "write failed" in serialForwarder

I haven't used MicaZ motes in Linux.  Hopefully someone else can chime
in.  - Cory

On 12/15/05, Liu, Ping (Research) <[EMAIL PROTECTED]> wrote:
> Cory,
>
> Thanks for the reply.
>
> I am using xbow micaz motes on linux.  Isn't the baudrate automatically set 
> to be 57600? Or I need to set it specifically again.
>
> java net.tinyos.sf.SerialForwarder -comm serial@/dev/ttyS0:micaz
>
> Thanks again.
> T.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
> Cory Sharp
> Sent: Thursday, December 15, 2005 2:57 PM
> To: Liu, Ping (Research)
> Cc: tinyos-help@millennium.berkeley.edu
> Subject: Re: [Tinyos-help] What could be the reason for "write failed"
> in serialForwarder
>
>
> That's usually a mismatched baud rate -- the serial forwarder is
> configured for a different baud rate than what the mote is using.
> This page, while not exactly appropriate for your problem, will give
> you some idea about where you can look:
>
> http://www.moteiv.com/community/Change_the_default_UART_baud_rate
>
> Cory
>
> On 12/15/05, Liu, Ping (Research) <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > What could be the reason for "write failed" while trying the 
> > serialForwarder?
> >
> > I am on 1.1.14. and serialForwarder was working fine for me earlier on 
> > 1.1.7.
> >
> > Thanks many!
> > -T.
> >
> > ___
> > 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] TestTinyViz help

2005-12-15 Thread L Tony


hi,

When I run TestTinyViz,as the tinyos tutorial,
export DBG=usr1
tinyviz -run build/pc/main.exe 30
I got "unable to run simulation: java.io.IOException". Is there anybody who 
can help me to solve this problem? Another question is, what's the editor 
for programming nesC?

Thanks.

Best regards,
Tony

_
免费下载 MSN Explorer:   http://explorer.msn.com/lccn  


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

Re: [Tinyos-help] issues with ncc compiler porting tinyos 2.0

On 12/12/05, Cormac Duffy <[EMAIL PROTECTED]> wrote:
> Hi
> Im trying to port tinyos 2.0 to UCC's DSYS25, the platform is very
> similar to the mica2 in that they both use the same atmega128 processor.
> For the moment I am just trying to set up the make files such that I can
> get ncc to compile with "make dsys25"
>
> I copied the mica2.target file, renamed it dsys25, and replaced mica2
> with dsys25 within the file, I also copied the mica2 platform folder and
> renamed it to dsys25, (I know all this is a bit of a hack but am tryig
> to start somewhere),

This should work, as long as the dsys25 directory is in the platforms
directory. If not, you need a -I directive pointing to the dsys25
directory. Try following/adding print statements to ncc itself if you
still can't get it to work.

> anyway
>  end result is
>
> make dsys25z
> mkdir -p build/dsys25z
> compiling BlinkAppC to a dsys25z binary
> ncc -o build/dsys25z/main.exe -Os -finline-limit=10 -Wall -Wshadow
> -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=dsys25z
> -fnesc-cfile=build/dsys25z/app.c -board=micasb -I%T/lib/oski
> BlinkAppC.nc -lm
> Unknown target dsys25z
> Known targets for TinyOS directory /opt/tinyos-2.x/tos
> and the specified include directories are:
>   telosa null micaz telosb mica2

ncc couldn't find a dsys25 platform. See comment above.

David Gay

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

Re: [Tinyos-help] Problems switching from Tinyos 2.x to Tinyos 1.x

On 12/5/05, Joe Polastre <[EMAIL PROTECTED]> wrote:
> Your analysis is correct, although I'm not quite sure why the 2.x
> tools would choose to abandon installing programs on the Telos and
> Tmote Sky platforms.
>
> If you want a version that Moteiv certifies will work, check out the
> Tmote Sky downloads on our webpage: http://www.moteiv.com/community

I've now fixed the 1.x make stuff (in CVS) to use tos-bsl if it's
available, and msp430-bsl otherwise. Things should now work if you've
installed the 2.x tools (once you get TinyOS from CVS, or from the
next snapshot, of course).

> On 12/5/05, Dongyan Chen <[EMAIL PROTECTED]> wrote:
> > Dear all,
> >
> >   When switching back to Tinyos-1.x tree, I changed the environment
> > variables as instructed in
> > http://www.tinyos.net/dist-2.0.0/tinyos-2.0.0pre2/doc/html/upgrade-tinyos.html.
> > While my programs compile, I can't upload them to TMote. The following
> > is the error:
> >
> > $ make tmote reinstall
> > cp build/telosb/main.ihex build/telosb/main.ihex.out
> > found mote on COM5 (using bsl,auto)
> > installing telosb bootloader using bsl
> > msp430-bsl --telosb -c 4 -r -e -I -p 
> > /opt/tinyos-1.x/tos/../beta/Deluge/Deluge/T
> > OSBoot/build/telosb/main.ihex
> > MSP430 Bootstrap Loader Version: 2.0
> >
> > USAGE: /opt/msp430/bin/msp430-bsl [options] [file]
[...]

David Gay

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

Re: [Tinyos-help] Problems switching from Tinyos 2.x to Tinyos 1.x

2005-12-15 Thread Joe Polastre

On 12/15/05, David Gay <[EMAIL PROTECTED]> wrote:
> I've now fixed the 1.x make stuff (in CVS) to use tos-bsl if it's
> available, and msp430-bsl otherwise. Things should now work if you've
> installed the 2.x tools (once you get TinyOS from CVS, or from the
> next snapshot, of course).

This doesn't solve the problem.  All you did was change it to use
tos-bsl if available, but tos-bsl doesn't install for Telos Rev
B/Tmote Sky.

-Joe

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

Re: [Tinyos-help] Problems switching from Tinyos 2.x to Tinyos 1.x

On 12/15/05, Joe Polastre <[EMAIL PROTECTED]> wrote:
> On 12/15/05, David Gay <[EMAIL PROTECTED]> wrote:
> > I've now fixed the 1.x make stuff (in CVS) to use tos-bsl if it's
> > available, and msp430-bsl otherwise. Things should now work if you've
> > installed the 2.x tools (once you get TinyOS from CVS, or from the
> > next snapshot, of course).
>
> This doesn't solve the problem.  All you did was change it to use
> tos-bsl if available, but tos-bsl doesn't install for Telos Rev
> B/Tmote Sky.

Well it works fine on my tmote sky's... And if my memory is not
playing me tricks, the code for tos-bsl came from Cory.

Bug reports would be appreciated (this thread relates to the fact that
in the 2.x tools distribution, msp430-bsl is not the telos-specific
version - see the original message).

David

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

[Tinyos-help] ACK frame structure in CC2420 BMAC

2005-12-15 Thread Krisakorn Rerkrai

Hi,

- I would like to know the structure of ACK frame in BMAC for CC2420
radio. I found one post about BMAC in CC1000
http://mail.millennium.berkeley.edu/pipermail/tinyos-devel/2005-March/000635.html
but I am not sure whether this could apply to CC2420 radio since
CC2420 should follow the 802.15.4 standard or? What I recall from the
standard is that ACK frame contains 11 bytes: preamble 4B, SFD 1B,
length 1B, FCF 2B, Sequence number 1B, FCS 2B.

- Also how much would be the delay of this ACK frame?

Thank you very much.

Regards,
Krisakorn

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

[Tinyos-help] Javacomm 2.0

2005-12-15 Thread Jie Liu

I am trying to start a clean TinyOS 1.x intallation on a XP box and following the instructions from page: http://www.tinyos.net/tinyos-1.x/doc/install.html#windows
. However, the link http://java.sun.com/products/javacomm/ is not longer pointing to Java Comm 2.0 (it is 3.0 instead, which I assume is completely different). Does anyone how I can proceed for a working TinyOS installation? 

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

Re: [Tinyos-help] Javacomm 2.0