power management needs work; in particular:
- low power sleep ain't low enough
- simpletimer generates lots of clock events while
sleeping that waste power
- data loss rates are high when all of the motes have
to get data out in a single 1s window -- we need to
stagger things somehow, or something...
Logged In: YES
user_id=239615
the solution for now is to change TupleRouterM to use a
different SimpleTime clock rate when doing long installations.
obviously, this isn't really useful for people who aren't us, but
it means we can get long running deployments working in the
lab.