Dear Phil,

        Many many thanks for your answer... 

>>
>> 1) How can I manage to start first a specific mote on TOSSIM? eg. I  
>>would like to boot first the mote 0 and then boot all the others.

> You can't in 1.x. TOSSIM in 2.x allows you to control the boot times.

Is there any way to put something in my code, in init or start functions to
boot the motes in the order I want. Or is there any tricky function to show
to a mote if mote X has been started or not??

>> 2) How can I see the EEPROM file? I use the main.exe -ef=text.txt  
>> command but I get a 5Mbyte file .empty!!
>Have you written anything to the EEPROM? If not, it will be empty.  
>Also, it's not a text file. It's just the state of the EEPROM stored  
>in a file. If you application stores binary data, the EEPROM file  
>will have binary data in it. It's like a loopback file system.

Yea... I should have thought that. I have binary data in it..


>>9: Popping event for mote 6 with time 0:0:19.16369425.
>> SIM: Reading command from client fd 7
>> SIM: Reading in GuiMsg header of size 14 with length 0
>> SIM: Closing client socket 7.
>>
>> [EMAIL PROTECTED]@spoon /opt/tinyos-1.x/apps/BlinkSIM: 
>> commandReadThreadFunc:  
>> error in selec
>
>> t(): Bad file descriptor
>> SIM: Reading command from client fd 7
>> SIM: Reading in GuiMsg header of size 14 with length 0
>> $ SIM: Closing client socket 7.

>If the socket closes abruptly, you might see this error. E.g., if you  
>connect  to TOSSIM then disconnect. I assume you're not seeing a big  
>problem with this?

Yea..let it be...

>> 4) TOSSIM runs code instantaneously. Why a msg from a mote (eg.0)  
>> delays independently to arrive to the motes. I thought the message  
>> should arrive at the same time to all motes but this doesn't not  
>> seem to happen.
>The radio stack works at the bit level. Each node is sampling the  
>channel at 40kHz to read in data. Those sample times are not  
>synchronized: two motes might both be sampling at 40kHz but have a  
>phase difference of 10us. The node receives the packet based on the  
>interrupt timing. So nodes will receive the packet with very close  
>but not necessarily identical times.

Hm...that explains a lot of things.. And If I have enable many debug
messages in dbg...the delay is getting bigger and bigger...


>Phil

Thanks,
Nick




____________________________________________________________________
http://www.freemail.gr - äùñåÜí õðçñåóßá çëåêôñïíéêïý ôá÷õäñïìåßïõ.
http://www.freemail.gr - free email service for the Greek-speaking.
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to