[Tinyos-help] CTP not reporting NET_C_FE_DST_MSG and NET_C_TREE_RCV_BEACON

Morten Tranberg Hansen mth at cs.au.dk
Fri Nov 19 19:29:09 PST 2010

Ok, so lets conclude.  Assuming a reliable logging system DST_MSG is not
needed if one logs when the max payload length test fails and RCV_BEACON
might overload the logging system in dense networks.

I guess what you need to decide is whether you want tinyos-main to log when
the max payload length test fails and/or add an ifdef to optionally enable
logging of RCV_BEACON.

I just brought this up as others (as well as I did) might wonder why these
events are defined but never reported.


On Fri, Nov 19, 2010 at 10:32 PM, Omprakash Gnawali <gnawali at cs.stanford.edu
> wrote:

> On Thu, Nov 18, 2010 at 2:39 PM, Morten Tranberg Hansen <mth at cs.au.dk>
> wrote:
> > Oh I didn't realize you were talking about the RCV_MSG event.  Yeah the
> only
> > unlogged event between the RCV_MSG event and a possible DST_MSG event at
> the
> > root would be if the max payload length test fails.  I'm not sure when/if
> > this test fails, but maybe it should be logged for correctness.
> The test can fail if the length field gets corrupted and still passes
> the CRC test. Or, if you have two versions of code (different max.
> available payload size) in the network and the received packet won't
> fit in the payload of the outgoing message. etc.
> Even if you have DST_MSG, keep in mind that there is no guarantee that
> this will be logged because the logging buffer could be full. You can
> detect that by looking for missing sequence number in the logged
> messages but that won't be enough either... So, if you want to be
> correct in the strictest sense, you probably need to do something much
> more sophisticated.
> If you are really worried about this test, a better approach might be
> to log when that test fails. That could be useful for understanding
> other problems that might occur in the network as well.
> - om_p

Morten Hansen, http://mortent.dk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20101120/40c5754c/attachment-0001.htm 

More information about the Tinyos-help mailing list