Thanks for your very useful answers, What is the difference between LinkEstimator sources in tos/lib/net/le and tos/lib/net/4bitle ? which one is used ?
I have read sources from le directory, I have seen how EETX is deduced from ratio msg_rcv/(msg_rcv + msg_fail) and data_success/data_total with EWMA. I don't know yet how I will add a data similarity estimation, because if I add it directly into the LinkEstimator I will have two data captures (one in a timer at an upper level (to do data aggregation) and one at the LEEP level), I don't see yet the solution maybe because I'm new with TinyOS and the wiring-oriented programmation (maybe there's a way to branch components to allow LEEP to use data captured at the App layer level, but I'm not sure). Thanks in advance, Rémi 2009/4/29 Omprakash Gnawali <[email protected]> > On Tue, Apr 28, 2009 at 9:34 AM, Rémi Villé <[email protected]> wrote: > > To reformulate my problem I will take an example : > > > > A sensor have the choice between two parents to connect itself to a > > collection data path. > > By default it chooses the bad parent in the sense that this one reads > very > > different datas. (assuming that a good parent is a sensor that read > similar > > datas) > > > > So what I would like to do is that when the sensor overhear (snoop) a > data > > message from the good potential parent, it indicates to the Ctp mechanism > > that it should consider this sensor as a better parent than the current > one. > > > > It would be like not only taking into consideration ETX but this global > > behavior too. > > > > Is there any way to perform that ? > > You will have to incorporate sensor data into your routing metric. You > might need to modify what a node advertises. You might be able to > modify LEEP to do this. You can take a look at tos/lib/net/4bitle. You > will need to augment the table lookup interface so that you can get > data values in addition to the link qualities. Then you should change > the router tos/lib/net/ctp/CtpRoutingEngineP.nc to make path selection > decision based on the sensor values. So yes, it can be done. The > standard code in the repository does not do this. You will need to > change it the way I suggested or in some other ways so that you can > make these different type of routing decisions. > > - om_p >
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
