I have not used Tymo myself. I hope someone else in the list could help you.
best regards, Faisal Aslam Ellen Shlossberg wrote: > Hi Faisal, > > Thanks for the suggestion. I had tried briefly to install Dymo before > but found I was missing some key wirings, among other problems. Do you > know if there is an available code example that works (along with .h, > config and implementation files)? > > Also, right now all 20 motes can talk to each other within one hop. > What is a good way to decrease the radio range for the mica2 - say no > more than 1 or 2 meters? Is it the CC1000 control? Could you point me > to a good help file on correctly implementing the controller? > > Thanks again, > Ellen > > On Wed, Jul 29, 2009 at 10:55 AM, Faisal Aslam > <as...@informatik.uni-freiburg.de > <mailto:as...@informatik.uni-freiburg.de>> wrote: > > I will say use tinyOS implementation of Dymo routing > (http://docs.tinyos.net/index.php/Tymo). They called it Tymo. > Dymo is modified form of AODV. They remove the routes after > sometimes if it is not used and there is some timeout for each > route maintained. > However, you could modify it to fulfill your needs (may be > increase the timeout or remove it). > They have a variable DYMO_ROUTE_TIMEOUT for the timeout. See their > code.... > > best regards, > Faisal Aslam > > > > Ellen Shlossberg wrote: > > Hello All, > > I have been reading through the mailing list and relative > papers on multi-hop routing in TinyOS and I am hoping someone > can suggest a good and simple implementation. I am using > tinyos-2.x with mica2 motes and the options for routing aren't > always applicable to both 2.x and mica2. This is a document I > found useful on describing the routing types, but it does not > specify the locations of files and how to implement the protocols. > > http://db.lcs.mit.edu/madden/html/tinyos-nsdi04.pdf > > My goal is to have around 20 motes turn on, discover routes to > each other by talking to their one-hop neighbors, and then > maintain this network and notice if any new mote has entered > or if an existing one has left. It appears that AODV would be > useful, but the routes would have to be retained in a routing > table for an extended period (not just for one-time use). What > would be the best routing method to use? > I have Dissemination and Collection working, but I believe > they do not maintain specific routes, but rather used route > discovery each time they need to disseminate or collected. > I've also read about multiHopRoute - but could not find a > specific implementation. Same for LQI and CTP. Do these work > with mica2? Is there a simple way to test these out in a > small network of motes - say 4 or 5 motes? > Any help is appreciated! > > Thanks, > Ellen > > -- > Ellen Shlossberg > Columbia University > MS Electrical Engineering > > ------------------------------------------------------------------------ > > _______________________________________________ > Tinyos-help mailing list > Tinyos-help@millennium.berkeley.edu > <mailto:Tinyos-help@millennium.berkeley.edu> > > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > > > > > -- > Ellen Shlossberg > Columbia University > MS Electrical Engineering _______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
