Re: [Tinyos-help] Make quot; [program] Error 57quot; on uisp command

2010-09-17 Thread David
Hi everyone

Has anyone been able to resolve the problem  Make [program] error 57???

Thanks for your time and responses

David


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


Re: [Tinyos-help] Fwd: UDPEcho in iris

2010-09-17 Thread Miklos Maroti
Hi!

Read the following files:

tos/chips/rf2xx/README
tos/chips/rf2xx/rf230/README

This can be set in your Makefile by adding the line

CFLAGS += -DSOFTWAREACK_TIMEOOUT=2000

By the way, it seem that the problem lies with the serial
communication between the PC and the IRIS. We try to find the exact
cause of this.

Best,
Miklos

On Fri, Sep 17, 2010 at 8:42 AM, nithin k n nithin6low...@gmail.com wrote:
 where can i find SOFTWAREACK_TIMEOUT to increase it?

 Nithin

 On Thu, Sep 16, 2010 at 2:14 AM, Miklos Maroti mmar...@math.u-szeged.hu
 wrote:

 Hi Stephen,

 I think the stack never duplicates data packets. Do you mean that if
 an ack packet does not arrive on time, then BLIP will retry, which on
 a MAC level is a new message, but on the BLIP level it is a duplcate
 UDPEcho packet?

 Zsolt and Krisztian, can you increase the SOFTWAREACK_TIMEOUT to 2000
 and see if that improves the situation? (By the way, on our tests we
 saw only 1-2% duplicate packets on IRIS).

 Best,
 Miklos

 On Wed, Sep 15, 2010 at 5:37 PM, Stephen Dawson-Haggerty
 stev...@eecs.berkeley.edu wrote:
  I believe this is an issue with the iris radio stack when using
  software acks?  I remember that its ack timeout was set to be shorter
  than the software turnaround time on an epic platform.  However, I'm
  not an iris expert...
 
  Steve
 
  On Mon, Sep 6, 2010 at 10:16 PM, nithin k n nithin6low...@gmail.com
  wrote:
 
  hi there
 
  UDPEcho is not behaving well, for eg, while pinging the UDPEcho
  installed
  motes, the basestation gets too many DUP! packets in reply,
  on an average, the count of DUP! packets is more than actual ping reply
  packets.
  Reason for this?
 
  Regards,
  Nithin
 
 
  ___
  Tinyos-help mailing list
  Tinyos-help@millennium.berkeley.edu
 
  https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
 
 
 
 
  --
  stephen dawson-haggerty
  http://cs.berkeley.edu/~stevedh
  uc berkeley wireless and embedded systems lab
  berkeley, ca 94720
  ___
  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


[Tinyos-help] ImportError: No module named TOSSIM

2010-09-17 Thread Parisa Panjideh
Hi,

 

I face to a problem trying to import TOSSIM. I wanna use TOSSIM
simulator with the help of
http://www.tinyos.net/dist-2.0.0/tinyos-2.x/doc/html/tutorial/lesson11.h
tml .

I compile it successfully but trying to import TOSSIM as follow:

 

$ python

 from tossim import *

 

 I see this error message:

 

Traceback (most recent call last):

  File stdin, line 1, in module

ImportError : No module named tossim

 

I have also exported PYTHONPATH. As I see this is a common problem but I
cannot find the answer..

 

Any help would be appreciated!

 

Best regards,

Parisa

 

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

[Tinyos-help] Problems in working with TOSSIM

2010-09-17 Thread Gaurav Agrawal
Hello friends,
I was trying to work upon TOSSIM for the first time. I started working upon
the TOSSIM tutorial on the wiki. when i did the make micaz sim for the
RadioCountToLeds it gave me the below error can anybody please help. Any
sort of help would be really appreciated.
**
**
*agrawalg-RadioCountToLeds-)* make micaz sim
mkdir -p simbuild/micaz
  placing object files in simbuild/micaz
  writing XML schema to app.xml
  compiling RadioCountToLedsAppC to object file sim.o
ncc -c -shared -fPIC -o simbuild/micaz/sim.o -g -O0 -tossim
-fnesc-nido-tosnodes=1000 -fnesc-simulate
-fnesc-nido-motenumber=sim_node\(\) -Wall -Wshadow -Wnesc-all -target=micaz
-fnesc-cfile=simbuild/micaz/app.c -board=micasb -DDEFINED_TOS_AM_GROUP=0x22
--param max-inline-insns-single=10 -DIDENT_APPNAME=\RadioCountToLed\
-DIDENT_USERNAME=\agrawalg\ -DIDENT_HOSTNAME=\uf053\
-DIDENT_USERHASH=0x6c88d777L -DIDENT_TIMESTAMP=0x4c938e3cL
-DIDENT_UIDHASH=0x938ce7bbL -Wno-nesc-data-race RadioCountToLedsAppC.nc
-fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants
-fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags
-fnesc-dumpfile=app.xml
  compiling Python support and C libraries into pytossim.o, tossim.o, and
c-support.o
g++ -c -shared -fPIC -o simbuild/micaz/pytossim.o -g -O0
-DIDENT_APPNAME=\RadioCountToLed\ -DIDENT_USERNAME=\agrawalg\
-DIDENT_HOSTNAME=\uf053\ -DIDENT_USERHASH=0x6c88d777L
-DIDENT_TIMESTAMP=0x4c938e3cL -DIDENT_UIDHASH=0x938ce7bbL
/home/P09/agrawalg/mywork1/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx
-I/usr/include/python2.5
-I/home/P09/agrawalg/mywork1/tinyos-2.x/tos/lib/tossim -DHAVE_CONFIG_H
/home/P09/agrawalg/mywork1/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:26:20:
error: Python.h: No such file or directory
/home/P09/agrawalg/mywork1/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:296:
error: ISO C++ forbids declaration of 'PyObject' with no type
/home/P09/agrawalg/mywork1/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:296:
error: expected ';' before '*' token
/home/P09/agrawalg/mywork1/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:297:
error: 'PyObject' has not been declared
/home/P09/agrawalg/mywork1/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:302:
error: 'PyObject_HEAD' does not name a type
/home/P09/agrawalg/mywork1/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:306:
error: expected initializer before '*' token
/home/P09/agrawalg/mywork1/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:313:
error: 'FILE' has not been declared
/home/P09/agrawalg/mywork1/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In
function 'int swig_varlink_print(swig_varlinkobject*, int*, int)':
/home/P09/agrawalg/mywork1/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:316:
error: 'fprintf' was not declared in this scope
/home/P09/agrawalg/mywork1/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:317:
error: 'struct swig_varlinkobject' has no member named 'vars'
/home/P09/agrawalg/mywork1/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: At
global scope:
/home/P09/agrawalg/mywork1/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:325:
error: expected initializer before '*' token
/home/P09/agrawalg/mywork1/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3496:
error: expected '}' at end of input
make: *** [sim-exe] Error 1

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

[Tinyos-help] cc2420 Active Period increased (LPL)

2010-09-17 Thread themrora...@hotmail.it
Hi all,

I'm using the default Low Power Listening from the Blip stack  
(tinyos-2.1.1) and I've measured the CC2420 active period while it  
senses the channel and no signal is in the air.
According with my osciloscope, the cc2420 reads the CCA pin for  
approximately 6 msec if there is no signal on the radio.

In my module I have recently added an async event called  
infolowlayer that get data from the cc2420 (provided by IPDispatchP).

I have also added a task, called info, which process data get by the  
async event infolowlayer. The task info is periodically posted by  
a timer so event and task have access to the same variables.

I don't have errors and the application seems to work fine at the  
beginning but using this event and the task CC2420 active period is  
always about 100msec.

I tried to declare variables using norace and accessing to the  
shared variables by atomic block  but still I cannot understand what  
is the problem.

Please, could you give me a suggestion?

follows the important part of the code

Many thanks

Davide
Research Engineer
NIMBUS - Networked Embedded Systems Research Centre
Cork Institute of Technology
Rossa Avenue, Bishopstown
Cork, Ireland


/ / - - -
norace uint_8 tmprssi;
norace uint_8 tmplqi;


task info()
{
   atomic {
myrssi = tmprssi;
mylqi = tmplqi;
 }
}


event void Timer.fired()
{
   post info();
}


async event voild InfoLowLayer.infolowlayer (uint_8 rssi, uint_8 lqi)
{
   atomic {
 tmprssi = rssi;
 tmplqi = lqi;
 }
}
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] CC2420 Active period increased (LPL)

2010-09-17 Thread TheMrOrange
Hi all,

I'm using the default Low Power Listening from the Blip stack  
(tinyos-2.1.1) and I've measured the CC2420 active period while it  
senses the channel and no signal is in the air.
According with my osciloscope, the cc2420 reads the CCA pin for  
approximately 6 msec if there is no signal on the radio.

In my module I have recently added an async event called  
infolowlayer that get data from the cc2420 (provided by IPDispatchP).

I have also added a task, called info, which process data get by the  
async event infolowlayer. The task info is periodically posted by  
a timer so event and task have access to the same variables.

I don't have errors and the application seems to work fine at the  
beginning but using this event and the task CC2420 active period is  
always about 100msec.

I tried to declare variables using norace and accessing to the  
shared variables by atomic block but still I cannot understand what is  
the problem.

Please, could you give me a suggestion?

follows the important part of the code

Many thanks

Davide
Research Engineer
NIMBUS - Networked Embedded Systems Research Centre
Cork Institute of Technology
Rossa Avenue, Bishopstown
Cork, Ireland


/ / - - -
norace uint_8 tmprssi;
norace uint_8 tmplqi;


task info()
{
  atomic {
   myrssi = tmprssi;
   mylqi = tmplqi;
}
}


event void Timer.fired()
{
  post info();
}


async event voild InfoLowLayer.infolowlayer (uint_8 rssi, uint_8 lqi)
{
  atomic {
tmprssi = rssi;
tmplqi = lqi;
}
}
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] error: ‘tos_state’ undecla red (first use in this function)

2010-09-17 Thread Raihan -Ul - Islam
Dear  All

I  installed python 2.6.5 and tiny os but when  i want to complie for TOSSIM
i am getting following error.


rai...@raihan-laptop:~/tinyos/Powerup$ make micaz sim
mkdir -p simbuild/micaz
  placing object files in simbuild/micaz
  writing XML schema to app.xml
  compiling PowerupAppC to object file sim.o
ncc -c -shared -fPIC -o simbuild/micaz/sim.o -g -O0 -tossim
-fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido- -Wall -Wshadow
-Wnesc-all -target=micaz -fnesc-cfile=simbuild/micaz/app.c -board=micasb
-DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=10
-DIDENT_APPNAME=\PowerupAppC\ -DIDENT_USERNAME=\raihan\
-DIDENT_HOSTNAME=\raihan-laptop\ -DIDENT_USERHASH=0xf3751655L
-DIDENT_TIMESTAMP=0x4c935e36L -DIDENT_UIDHASH=0x06241b9aL
-I/usr/include/python2.6 -Wno-nesc-data-race PowerupAppC.nc
-fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants
-fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags
-fnesc-dumpfile=app.xml
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc: In function
‘SimMoteP$SimMote$isOn’:
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc:57: error: ‘tos_state’
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc:57: error: (Each undeclared
identifier is reported only once
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc:57: error: for each function it
appears in.)
/opt/tinyos-2.1.1/tos/lib/tossim/TossimActiveMessageC.nc: In function
‘TossimActiveMessageC$Model$receive’:
/opt/tinyos-2.1.1/tos/lib/tossim/TossimActiveMessageC.nc:105: error:
‘tos_state’ undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/tossim/SimSchedulerBasicP.nc: In function
‘SimSchedulerBasicP$sim_scheduler_submit_event’:
/opt/tinyos-2.1.1/tos/lib/tossim/SimSchedulerBasicP.nc:70: error:
‘tos_state’ undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/tossim/SimSchedulerBasicP.nc: In function
‘SimSchedulerBasicP$sim_scheduler_event_handle’:
/opt/tinyos-2.1.1/tos/lib/tossim/SimSchedulerBasicP.nc:78: error:
‘tos_state’ undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/tossim/SimSchedulerBasicP.nc: In function
‘SimSchedulerBasicP$Scheduler$init’:
/opt/tinyos-2.1.1/tos/lib/tossim/SimSchedulerBasicP.nc:163: error:
‘tos_state’ undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/tossim/SimSchedulerBasicP.nc: In function
‘SimSchedulerBasicP$popTask’:
/opt/tinyos-2.1.1/tos/lib/tossim/SimSchedulerBasicP.nc:114: error:
‘tos_state’ undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc: In function
‘SimMoteP$SimMote$getEuid’:
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc:48: error: ‘tos_state’
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc: In function
‘SimMoteP$SimMote$setEuid’:
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc:51: error: ‘tos_state’
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc: In function
‘SimMoteP$SimMote$getStartTime’:
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc:54: error: ‘tos_state’
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc: In function
‘SimMoteP$SimMote$turnOff’:
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc:78: error: ‘tos_state’
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc: In function
‘SimMoteP$sim_mote_boot_handle’:
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc:153: error: ‘tos_state’
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc: In function
‘sim_mote_set_start_time’:
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc:120: error: ‘tos_state’
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc: In function
‘SimMoteP$SimMote$turnOn’:
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc:65: error: ‘tos_state’
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc: In function
‘sim_mote_enqueue_boot_event’:
/opt/tinyos-2.1.1/tos/lib/tossim/SimMoteP.nc:162: error: ‘tos_state’
undeclared (first use in this function)
make: *** [sim-exe] Error 1


Please advice me.. How can i solve it..
Thanks
Raihan
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] CC2420 Active period increased (LPL)

2010-09-17 Thread Pusceddu Davide

Hi all,


I'm using the default Low Power Listening from the Blip stack  
(tinyos-2.1.1) and I've measured the CC2420 active period while it  
senses the channel and no signal is in the air.
According with my osciloscope, the cc2420 reads the CCA pin for  
approximately 6 msec if there is no signal on the radio.


In my module I have recently added an async event called  
infolowlayer that get data from the cc2420 (provided by IPDispatchP).

I have also added a task, called info, which process data get by the  
async event infolowlayer. The task info is periodically posted by  
a timer so event and task have access to the same variables.

I don't have errors and the application seems to work fine at the  
beginning but using this event and the task CC2420 active period is  
always about 100msec.

I tried to declare variables using norace and accessing to the  
shared variables by atomic block but still I cannot understand what is  
the problem.



Please, could you give me a suggestion?


follows the relevant part of the code


Many thanks

Davide
Research Engineer
NIMBUS - Networked Embedded Systems Research Centre
Cork Institute of Technology
Rossa Avenue, Bishopstown
Cork, Ireland


/ / - - -
norace uint_8 tmprssi;
norace uint_8 tmplqi;


task info()
{
  atomic {
   myrssi = tmprssi;
   mylqi = tmplqi;
}
}


event void Timer.fired()
{
  post info();
}


async event voild InfoLowLayer.infolowlayer (uint_8 rssi, uint_8 lqi)
{
  atomic {
tmprssi = rssi;
tmplqi = lqi;
}
}
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


Re: [Tinyos-help] Message filtering

2010-09-17 Thread mojtaba raznahan
Hi Dear Deeksha,

Thanks for your solution.

But the problem is ,when I modify ReceiverP file,Changes will not affect the
program.even if i write a irrelevant words in the middle of ReceiverP file!

Cheers.

I'm useing Make micaz sim and  then simulate it by TOSSIM.
Where is the problem?

On Wed, Sep 15, 2010 at 11:56 AM, Deeksha Rao Sahib 
eced...@ece.iisc.ernet.in wrote:


 Hey,

 Check the CC2420ReceiveP.nc program. In the receiveDone_task(show below)
 the Receive.receive is signalled after checking for the address in the
 function passesAddressCheck(). So after the address part is over you have
 to implement the logic you want to add. Try it out. I have not worked with
 anything like this.

 task void receiveDone_task() {

cc2420_metadata_t* metadata = call CC2420PacketBody.getMetadata(
 m_p_rx_buf );

cc2420_header_t* header = call CC2420PacketBody.getHeader( m_p_rx_buf);

uint8_t length = header-length;

uint8_t tmpLen __DEPUTY_UNUSED__ = sizeof(message_t) -
 (offsetof(message_t, data) - sizeof(cc2420_header_t));

uint8_t* COUNT(tmpLen) buf = TCAST(uint8_t* COUNT(tmpLen), header);



metadata-crc = buf[ length ]  7;

metadata-lqi = buf[ length ]  0x7f;

metadata-rssi = buf[ length - 1 ];



if (passesAddressCheck(m_p_rx_buf)  length = CC2420_SIZE) {

 #ifdef CC2420_HW_SECURITY

  if(securityOn == 1){

if(m_missed_packets  0){

  m_missed_packets --;

}

if(authentication){

  length -= micLength;

}

  }

  micLength = 0;

  securityOn = 0;

  authentication = 0;

 #endif

  m_p_rx_buf = signal Receive.receive( m_p_rx_buf, m_p_rx_buf-data,

   length - CC2420_SIZE);

}

 atomic receivingPacket = FALSE;

waitForNextPacket();

  }




  Thanks Dear Deeksha,
 
  Yes I want to know that in which layer this logic is checked In order to
  change it to my scenario.
  In my scenario I want to use AM_BROADCAST_ADDR .But i dont like every
 node
  in the listening distance receives this packet.Just some nodes with a
  characteristic inside the node can receive the broadcastet message.
 
  So do you know which file or module I have to change ?
 
  On Tue, Sep 14, 2010 at 12:43 PM, Deeksha Rao Sahib 
  eced...@ece.iisc.ernet.in wrote:
 
  Hey,
 
  I gather that you are talking about the unicast instead of broadcast.
  The checking of the destination address is done in some lower layers
  before it is pushed to the application where Receive.receive is
  signalled.
 
  If you want to include another parameter in making this decision, then
  you
  will have to include some extra details and logic at the place where it
  is
  checking  for the destination.
 
  These details might be like the structure inside the packet(data field
  of
  message_t), any exclusive packet type that you are using your
  application(ex: alarm pkt, event pkt, status pkt might have a field
  which
  will distinguish them from each other)
 
  Hope this helps you
 
   Hi Dear Jeonghoon,
  
   Thanks for your answer.
  
   I didn't get your solution.May be I'm not making myself clear.
  
   I want to avoid signaling the Receive.receive event.
   The scenario is this:
   when we use AMSend.Send(*node1*,...)(I mean not broadcasting),every
  other
   node in the listening node of sender will receive the signal,But
  because
   the
   destination of the message is *node1* so only this node will receive
  the
   packet(Receive.receive of other nodes will not triggered). I want to
  add
   another factor(beside the destination of the message). for example a
   variable in the node.So if we are sending a message to *node1*,the
  message
   should be received by a node by the the address of *node1* as well as
   having
   the mentioned factor.
  
   Any Solution?
  
  
   On Mon, Sep 13, 2010 at 5:41 PM, Jeonghoon Kang
   gadin.k...@gmail.comwrote:
  
   Hi,
  
   How about trying to use different AM type.
  
   command send[1]
   command send[2]
   event receive[1]
   event receive[2]
  
   or
  
   if (NODE_ID == 0x00) { ~~~ }
  
   Jeonghoon Kang
   Managerial Researcher
   at Korea Electronics Technology Institute(www.keti.re.kr)
   TinyOS Korea Forum Administrator
   www.tinyos.or.kr
   work = bu...@keti.re.kr
   private = gadin.k...@gmail.com
   www.pinkfloyd.re.kr/rnd/
   *Kmote Connector
   http://www.tinyos.re.kr/bbs/upload/kmote_connector.pdf
  
  
  
  
   2010/9/11 mojtaba raznahan mojtaba.razna...@gmail.com:
Hi,
   
How can I filter a message depending on some feature of nodes ?I
  mean
   a
   way
to prevent the Receive.receive from being signaled.
   
your help would be highly appreciated.
   
--
Mojtaba Raznahan
BS of Computer engineering
TMU university
www.raznahan.com
   
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu