On Aug 1, 2007, at 9:20 AM, Todd Roper wrote:
I went ahead and reset the two suspect nodes yesterday and as
expected,
they started sending data into the network again. This morning, I
discovered that one of them was trying to send through a node 2 this
time. (node 2 is not in the network). It does retry 30 times every 5
minutes (that is my programmed interval for reporting).
I disconnected the Root node and then powered it back up after a few
minutes. I have attached a small log file showing some extra bytes in
the beacon packet every once in a while. I have also noticed that
I get
bits shifting in the messages every once in a while (seems odd given
that there is a checksum).
I am wondering if there could be packet corruption causing routing
corruption????
One other note is that once the node was stuck on trying to send to
Node
2, I noticed it no longer sends out its routing table info every
once in
a while.
Wondering where to look next...
Best regards,
This is interesting. Packet corruption definitely seems like a
possibility. But the fact that it no longer sends routing beacons is
disturbing. This suggests perhaps a deeper issue of a memory access
bug somewhere.
Any information/data/traces you could provide would be greatly
appreciated.
Phil
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
