Todd Roper wrote:
Phil, Great to hear on the CTP 1) We are running deployed around the office here. Simple temp gathering 2) The platform is the isi1000, this is a hybrid we have made that has the MSP430 on it with the CC1000 radio. All other apps seem to work as expected with the exception of this one (Antitheft). I only had to do some minor changes in the CC1000 stack to remove the ATMEGA dependencies and then wire it up to the MSP. 3) Using TinyOS 2.0.1 (latest release from early May). I was wondering if this may have to do with some of the mesh statistics for the routing in the /ctp (rssi/parent,etc). Reason is that sometimes I can reset one node and 5 others will start reporting in again as if they now have a valid path to the root.
CTP does not use RSSI; it directly measures ETX through packet acknowledgements. There acknowledgements are layer 2, though, so do not consider queue drops. It sounds like one node is wedged and other are trying to route through it. If it can't send packets, then it will drop all packets it receives. When you reboot it, it either finds a route and continues forwarding packets or the prior children choose new routes.
By "all other apps" do you mean MultihopOscilloscope? That would be an easy to to separate an Anti-Theft failure from a CTP failure.
One thing you can do is program a BaseStation and snoop on traffic around a crashed node. If you see other nodes sending it packets but it doesn't send anything, then it's a local fault. You could also then plug that node into a serial port to see if CTP is sending any debug messages or whether the node has crashed/locked up.
Phil _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
