Thread: [Firebug-cvs] firebug/web steves_talk.ppt,NONE,1.1 blast.html,1.1,1.2 field_deploy.ppt,1.3,1.4
Brought to you by:
doolin
From: <do...@us...> - 2004-01-21 17:39:58
|
Update of /cvsroot/firebug/firebug/web In directory sc8-pr-cvs1:/tmp/cvs-serv27314 Modified Files: blast.html field_deploy.ppt Added Files: steves_talk.ppt Log Message: Start of ppt for Steve. --- NEW FILE: steves_talk.ppt --- (This appears to be a binary file; contents omitted.) Index: blast.html =================================================================== RCS file: /cvsroot/firebug/firebug/web/blast.html,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** blast.html 22 Jul 2003 03:48:50 -0000 1.1 --- blast.html 21 Jan 2004 17:39:54 -0000 1.2 *************** *** 1,16 **** ! <h2>Blast</h2> ! Blast is a routing stack of wireless ad-hoc networks for mote sensing application. ! Sensor readings are collected and encapsulated by the applications, ! blast will establish a self organizing network among the nodes,and route the packet to the basestation. ! All nodes in the network broadcast route messages, so every mode can choose parent node based on the link reliability caculated ! from the information of route messages. ! Once the network is established, each node can either sends its own packets or forwards its children's packets to its parent node. ! Packets can be forwarded to the base station in a multihop fashion.With this scheme, blast win the 90%+ receive rate of data packet ! in ideal environment. ! The two drawbacks of current version of blast are : The network setup time is relatively long, it is because it needs to collect enough ! route packet to caculate the reliability, another is it needs a mechanism to operate in power_saved mode to extend the longevity ! of the motes. \ No newline at end of file --- 1,112 ---- + <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> ! <html xmlns="http://www.w3.org/1999/xhtml"> ! <head> ! <title> ! BLAST multihop routing ! </title> ! <link rel="SHORTCUT ICON" href="./images/favicon.ico"> ! <link type="text/css" rel="stylesheet" href="firebug.css"> ! <meta name="author" content="David M. Doolin, UC Berkeley" /> ! </head> ! <body> ! <h1>BLAST multihop routing</h1> ! ! ! ! <p>Blast is a routing stack of wireless ad-hoc networks. ! Sensor readings are collected and encapsulated by the applications, ! and blast will establish a self organizing network among the ! nodes, routing the packet to the basestation. ! </p> ! ! <p> ! All nodes in the network broadcast route messages, so ! every mode can choose a parent node based on the link ! reliability caculated from the information of route messages. ! Once the network is established, each node can either ! sends its own packets or forwards child packets ! to its parent node. Packets can be forwarded to the base ! station in a multihop fashion. ! </p> ! ! ! <h2>BLAST performance</h2> ! <p> ! With this scheme, blast ! win the 90%+ receive rate of data packet in ideal environment. ! </p> ! ! ! <h2>BLAST limitations</h2> ! ! <p> ! Two drawbacks of current version of BLAST are: ! </p> ! ! ! <ol> ! <li> ! The network setup time is relatively long, it is ! because it needs to collect enough ! route packet to caculate the reliability. ! </li> ! <li> ! BLAST needs a mechanism to operate in ! power_saved mode to extend the longevity ! of the motes. ! </li> ! </ol> ! ! ! ! <h1>Experience with BLAST in the field</h1> ! ! <p> ! Our experience with BLAST has been a qualified success: ! the protocol appears to work as advertised. However, ! the following suggestions would help improve understanding ! and using the component in applications. ! </p> ! ! ! <ol> ! <li>Having an interface to set the RF transmitting power ! would be very helpful. The current BLAST code encapsulates ! the radio, which is good, but changing power settings ! requires changing constants in the CC1000 header file, ! or fiddling with BLAST or tos system code to do the same. ! None of these solutions are maintainable because ! different people on the same project may set the ! parameters differently, and tampering with any code in ! a system source tree renders could have side effects ! with other applications using the same components. ! </li> ! ! <li> ! BLAST has several tunable parameters to adjust ! stability, agility, etc., but it appears that ! adjusting tuning parameters requires changing ! BLAST source code. Having these parameters available ! for the programmer would be helpful. ! </li> ! ! <li> ! Documentation is scattered around several web sites. ! It would be really helpful to have some canonical ! documentation included with the source code package. ! </li> ! </ol> ! ! <hr /> ! ! <p> ! Last updated: $Date$ by $Author$. ! </p> ! ! </body> ! </html> Index: field_deploy.ppt =================================================================== RCS file: /cvsroot/firebug/firebug/web/field_deploy.ppt,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 Binary files /tmp/cvs3K5ire and /tmp/cvsyvqZ9t differ |