On Thu, Jun 19, 2008 at 12:07 AM, jiwen zhang <[EMAIL PROTECTED]> wrote:
...
> so i think the implementation of CtpInfo.getNeighborRouteQuality should
> change into :
> command uint16_t CtpInfo.getNeighborRouteQuality(uint8_t n) {
> return (n < routingTableActive)? evaluateEtx(call
> LinkEstimator.getLinkQuality(routingTable[n].neighbor)) +
> routingTable[n].info.etx:0xfffff;
> }
> what do you think , Omprakash ?
You are right - we need to not only fix getNeighborRouteQuality as you
suggested but also getNeighborLinkQuality for the same reason.
Unfortunately, this will have to wait until after the 2.1 release.
> a bug :
> in component CtpSenderP , it use the component CtpC , i don't find the
> component . can you check it , Omprakash ?
Yes, this is a bug. The fix will need to wait a week or so. It turns
out we had those files to enable running multiple collection protocols
at the same time but that work was never completed. We will look into
this after the release.
- om_p
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
