If you post those messages you get on the serial port and if I
recognize them, I will tell you what they are.
- om_p
>
> Hello, Omprakash, thank you for your answer!
>
> I have commented everything related to collection debug and debug overall
> code, but something might have slipped, it's possible.
> Even if they are debug messages, why do you think it takes that amount of
> messages to start receiving actual correct frames? Can it be by any chance a
> way to measure the time taken to establish a tree? If they're debug, and if
> the tree forms instantly (or close), why the wait?
>
> Thank you!
>
> Pedro
>
> On 7/14/07, Omprakash Gnawali <[EMAIL PROTECTED]> wrote:
> >
> >
> > >
> > > So let me redo the questions:
> > >
> > > How does the P bit enabling works? Who/what causes it and why?
> >
> > To add to what Phil said, the current implementation sets PULL bit
> > like this:
> >
> > ...
> > else if (routeInfo.parent == INVALID_ADDR) {
> > beaconMsg->etx = routeInfo.etx;
> > beaconMsg->options |= CTP_OPT_PULL;
> > } else {
> > ...
> >
> > (When a node does not have a parent, for example, when a node boots
> > up.)
> >
> >
> >
> > > The question about the 14 data messages remain.
> > >
> >
> > Did you disable the debug messages? Those messages on the serial
> > interface are probably debug messages. CTP should not send bogus
> > messages on the serial port - if the tree is built, it will send data
> > messages, otherwise there will be no data messages to forward. Debug
> > messages are independent of the data messages and if they are enabled,
> > not only the base station, but all the motes should send some debug
> > messages on the serial port.
> >
> > - om_p
> >
>
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
