Thanks for those replies: I have a better understanding now of how the CTP+LPL timeouts work.
Fyi: I am seeing about 5-6 hour delays in re-establishing the mesh network when there's a problem Here's the use case: - 2 motes, pretty far away from the basestation, but the signal is able to get through. Each mote is transmitting a sensor reading over CTP+LPL once a minute (except when the mote is still busy in a sensor read or send, from a previous cycle). - Occasionally, something happens to interrupt the mesh network (maybe something in the office that adds some interference), and then both the motes drop off the network (basestation stops receiving data over CTP+LPL), and don't want to come up again again. - If I take both motes and put them right next to the basestation, the data still doesn't come through - About 5-6 hours later, the signals start coming through again on both motes at around the same time. I've seen this type of pattern a couple of times so far. I think that this might be because of the CTP send code on both motes, taking a very long time to time out, possibly combined with the mesh network having trouble re-establishing. If it becomes a problem, I'll see if using the send "cancel" interface to CTP on the motes helps a bit, to get the data coming through from the motes again sooner. Or maybe I need to try something like making all the motes reboot themselves after an hour of CTP inactivity, or explicitely turning the CTP algorithm off and on on all the motes, to help restart the logic? Thanks for your advice so far. PS: With regards to my earlier question, CTP+LPL, with a 1 second duty cycle, seems to be working very well for me so far in terms of low power usage. _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
