Set a timer to wake on the turn of the global second.
For non lead scouts, just go fully to sleep setting the usual symbol counter.
If you're a lead scout, use a systimer to sleep only the radio, so you're still alive for hq comms. Ive found that if you 'pause' the lwm stack in addition to putting it to sleep you can queue up to NWK_BUFFERS_AMOUNT (default 5) frames.
https://github.com/jacobrosenthal/library-atmel-lwm/tree/pause
Either way, on wakeup set a systimer for the wakems to put the device back to sleep again (current default 100ms)
Im seeing 2-4ma usage with this combination vs ~12-14ma fully on or 1ma fully off. But Im also able to communicate with 'sleeping' scouts. Its still takes a few attempts to get through as I dont have a synchronization protocol for meshOffset and thus meshtime yet.
A different take on sleep than #231
Set a timer to wake on the turn of the global second.
For non lead scouts, just go fully to sleep setting the usual symbol counter.
If you're a lead scout, use a systimer to sleep only the radio, so you're still alive for hq comms. Ive found that if you 'pause' the lwm stack in addition to putting it to sleep you can queue up to NWK_BUFFERS_AMOUNT (default 5) frames. https://github.com/jacobrosenthal/library-atmel-lwm/tree/pause
Either way, on wakeup set a systimer for the wakems to put the device back to sleep again (current default 100ms)
Im seeing 2-4ma usage with this combination vs ~12-14ma fully on or 1ma fully off. But Im also able to communicate with 'sleeping' scouts. Its still takes a few attempts to get through as I dont have a synchronization protocol for meshOffset and thus meshtime yet.