We are working on specifying the multi-hop routing framework for TinyOS 2. Here are some documents you can read that describes what we have so far:
http://tinyos.cvs.sourceforge.net/tinyos/tinyos-2.x/doc/txt/tep119.txt?view=markup http://tinyos.cvs.sourceforge.net/tinyos/tinyos-2.x/doc/txt/tep118.txt?view=markup http://tinyos.cvs.sourceforge.net/tinyos/tinyos-2.x/doc/txt/tep123.txt?view=markup You were curious if Collection has anything to do with a routing framework. Collection related documents (TEP 123, for example) describe the routing protocol - how a path is selected. It also describes the interfaces that different components of Collection (link estimation, routing, and forwarding) use to interact with each other. Is this what you were looking for? We would also be interested in hearing if what you want to do is not supported by these interfaces. It is quite possible that we missed something and it would be good to get your feedback. Thanks. - om_p ---------------- Hello, I am going to implement an ad-hoc routing protocol (DYMO) on TinyOS. I have already played a bit with TinyOS 2, nesC and TOSSIM, but now I am wondering how I will integrate my implementation in TinyOS. I have read TinyOS 1 & 2 documentations, and I have found in TinyOS 1 documentation that there was a set of components to implement an ad-hoc routing protocol : RouteSelect, MultiHopSend, etc. But it seems it doesn't exist anymore in TinyOS 2, and I found nothing similar (Dissemination and Collection have nothing to do with a routing framework, right ?). Did I miss something ? Or should I first rewrite these TinyOS 1 interfaces in TinyOS 2 and then implement them ? I know I could make my own interfaces, but it would be better if I implemented something standard so that it can be useful for others. Thanks for your help, Romain _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
