[Tinyos-contrib-commits] CVS: tinyos-1.x/contrib/rincon/apps/MeshCollect readme.txt, 1.1, 1.2 MeshCollect.h, 1.1, NONE MeshCollectC.nc, 1.1, NONE

[dmm]

Update of /cvsroot/tinyos/tinyos-1.x/contrib/rincon/apps/MeshCollect
In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv12130/contrib/rincon/apps/MeshCollect

Modified Files:
	readme.txt 
Removed Files:
	MeshCollect.h MeshCollectC.nc 
Log Message:
Uploaded new utilities:
* FlashBridge updates
* Configuration
* Leds
* RandomGen

Removed some apps:
* MeshCollect (in progress)
* FlashBridge moved from apps->lib

Updated some readme's.

Index: readme.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-1.x/contrib/rincon/apps/MeshCollect/readme.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** readme.txt	27 Jul 2006 23:38:25 -0000	1.1
--- readme.txt	28 Aug 2006 17:57:39 -0000	1.2
***************
*** 1,74 ****
! A demo app is provided in /apps/TestMeshCollect
! Make sure your radio's ack's are enabled!
  
- /**
-  * This Mesh Network component is based on MultiHopLQI, with updates:
-  *
-  *  > Built on top of Transceiver, which provides a publically shared 
-  *    message pool that's application-wide and managed automatically.
-  *
-  *  > QuickJoin functionality allows the mote to quickly 
-  *    connect to its surrounding network.  QuickJoin is run when 
-  *    the mote is first turned on, and when it loses communication.
-  *
-  *  > MultiHop and SingleHop Transceivers allow an application
-  *    to either transmit data out to the base station through the network,
-  *    or communicate directly with a nearby mote.
-  * 
-  *  > Collect message signatures allows an application to know for sure
-  *    if a sent/received message is really a multihop message.
-  *
-  *  > Increased simplicity by removing Snoop and Intercept - which does
-  *    decrease functionality to some degree, but makes the overall component
-  *    more of a no-brainer. The SinglehopTransceiver makes up for this somewhat.
-  *
-  *  > Mesh Analysis provides the ability to find out how the network is doing.
-  *    At the moment, custom implementation is involved to do anything
-  *    useful with the locally heard or multihop collected analysis packets.
-  *
-  *  > Multiple base stations are allowed, and it's easy to force a mote
-  *    to be a base station at compile time by setting the FORCE_BASE_STATION
-  *    preprocessor variable to 1
-  *
-  *  > Ability to dynamically turn a mote into a base station mote and back,
-  *    if you ever need that functionality.
-  *
-  * 
-  * This is not a replacement for Drain, it's something a little different
-  * with its roots still more toward automated tree maintenance. I also
-  * changed some of the names and references from 'MultiHop' to 'MeshCollect'
-  * to emphasize the fact that we are not multihopping packets to and from
-  * any location in the network; we're specifically collecting data from the 
-  * network and removing it using the base station node.  I'm sure that's why
-  * Drain got the name it has as well.
-  *
-  * Some files were renamed from MultiHopLQI, but maintain similar functionality:
-  * MultiHopC became MeshCollectC
-  * MultiHopEngineM became MeshTransferM
-  * MultiHopLQIM became MeshManagerM
-  *
-  * According to Phil Levis's comments in TinyOS devel (6/8/2006)
-  * the history of this protocol goes something like:
-  *
-  * Berkeley:
-  * MHOP -> BLESS -> lib/Route -> lib/MintRoute -> lib/MultiHopLQI -->
-  *    --> Drain
-  *    --> MeshCollect
-  *
-  * So you see, Drain and MeshCollect are on two different branches from
-  * MultiHopLQI.  Phil writes, "The change between MultiHopLQI and Drain was that
-  * Drain produces a static tree, which can be regenerated from the tree root,
-  * while MultiHopLQI, following the MintRoute approach, has a continuously
-  * updated tree."
-  *
-  * This component, MeshCollect, follows the MintRoute/MultiHopLQI approach
-  * in that the tree is continuously updated. It uses the same
-  * parent selection algorithms as MultiHopLQI.  The QuickJoin functionality
-  * and deployment analysis were added after gaining experience from
-  * actual deployed networks, and the code was completely revamped to make
-  * it easier to debug and hack. Flexibility is provided by 
-  * altering the compile time preprocessor variables.
-  * 
-  * @author David Moss - dmm at rincon.com
-  */
-  
--- 1,3 ----
! Temporarily removed the MeshCollect router to improve functionality and
! perform maintenance.
  

--- MeshCollect.h DELETED ---

--- MeshCollectC.nc DELETED ---