The macro UARTDETECT_POLL is set to 3 seconds, so the base expects a UartDetectMsg message before that. The Trawler application sends the message every 2 secs. If you are sending only every 5 secs it would explain why UART detect requests keep appearing.
I also have the problem where the base station sometimes 'locks up'. If you connect the base station to Serial Forwarder and then open up Trawler (via SF) you will see that the 'packets written' counter increments every 2 secs (as it should). After a random time I start getting a Write Failed message in the SF window, again every 2 secs. This problem happens both with and without the lowpower compile option. Apropos your comment about receiving messages that were queued up, isn't that what is supposed to happen? Finally I spotted another issue which may or may not be relevant to you. I am using heterogeneous hardware. My base station is a telosb and the motes are homebrewed. Netsync has a mechanism to detect slippage between the 32KHz clocks of the base station and the mote. With a heterogenous system its probaby more likely to happen as the 32KHz crystals were sourced differently. Making a base station based upon my homebrew is a bit difficult as the UART1 lines are inaccesible. Even if I could I'm not convinced that a heterogeneous net would not exhibit slippage between crystals.
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
