[Tinyos-help] Deluge 1.0 and Surge MultiHopRouter issue

Stephen Chao stephenc.chao at gmail.com
Tue Sep 6 12:26:11 PDT 2005


Hi all,

I've come across an issue that seems to relate to Deluge1.0 and multihop 
routing. I was making a routing application (similar to Surge) that uses the 
Deluge protocol, but during my testing I found that after injecting a copy 
of my multihop-Deluge program into an image and rebooting, the base node 
would cease sending information to the PC. Figuring that I'd designed my 
code wrong, I went back and tested out a Deluge-enabled Surge application 
(added DelugeC and wired Main.StdControl -> DelugeC) just to check that such 
a system works. Unfortunately, the same problem showed up again - the 
following output from the Listen tool shows surge messages being heard while 
mote 0 is running the program directly programmed into RAM, and stopping 
after it reboots to an image, which contains the same program:

/** Output from Listen tool 
************************************************************/
// TinyOS 1.1.13, using ReliableRoute in xbow/apps
// I begin by installing 4 motes with Surge-Deluge, numbered 0 to 3. I 
inject the same
// program I've just installed them with into image 0, then reboot to 0.
// Then, I re-install mote 0 and open up the Listen tool. Deluge-ping at 
this point
// shows correctly that mote 0 is not running either image 0 or 1 (N/A)
Stephen at bebop ~
$ java net.tinyos.tools.Listen
7E 00 03 99 14 00 00 01 00 39 01 00 03 00 00 00 FF 03 00 FF FC 02 00 FF F3
7E 00 03 99 14 00 00 02 00 39 01 00 03 00 00 00 FF 03 00 FF FF 01 00 FF FF
7E 00 03 99 14 00 00 03 00 39 01 00 03 00 00 00 FF 01 00 FF FE 02 00 FF F3
// Surge messages
7E 00 11 99 16 00 00 01 00 3A 01 00 00 00 00 00 00 DF 00 80 DF 4D 5F 00 00 
38 60
7E 00 11 99 16 00 00 02 00 3A 01 00 00 00 00 00 00 DF 00 80 E2 42 5E 00 00 
38 61
// Lights on mote 0 flicker, indicating that it's rebooting to what the 
other motes are running
7E 00 A1 99 10 00 00 09 00 00 00 08 00 1F 1F 02 00 1B 1B 98 29
// No further messages from this point on...
// Deluge-ping tells me that mote 0's is running image 0 at this point
/* End of output 
**********************************************************************/

Someone else had this same issue, as described here:

https://mail.millennium.berkeley.edu/pipermail/tinyos-help/2005-March/008546.html

but I don't think it was ever resolved. If anyone has any insights or 
suggestions, I'd be very interested in hearing them. Thanks!

Stephen Chao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20050906/f36d86b7/attachment.htm


More information about the Tinyos-help mailing list