On May 8, 2007, at 7:49 PM, Muhammad Azhar wrote:
Hi,
I read TEP 119 (Collection) which says:
An implementation of this TEP (i.e. TEP119) can be found in
tinyos-2.x/tos/lib/net/ctp and tinyos-2.x/tos/lib/net/le, in the
CTP protocol. ........ This implementation is a reference
implementation, and is not the only possibility. It consists of
three major components, which are wired together to form a
CollectionC: LinkEstimatorP, CtpTreeRoutingEngineP, and
CtpForwardingEngineP.
Thus, if my assumption that CollectionC is "made up" from ctp and
link estimator is right, why does the MViz application also "use"
CtpP when it has already "used" CollectionC. I'm sorry if this
question is unclear, but I really don't know how to put it well,
'coz when I compared it to the MultihopOscilloscope application, it
simply defines CollectionC to do its routing and sending of data
packets.
If you look how MViz wires to CTP, it only accesses the CtpInfo
interface, which gives routing information. This is how MViz reports
link qualities. Note, for example, the MultihopOscilloscope doesn't,
because it only sends data and doesn't need internal routing state.
Phil
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
