I tried presenting this on the mbed site, but it may be a mDot issue…

I’ve been experimenting with the example code mDot_DS18B20
https://developer.mbed.org/teams/Thing-Innovations/code/mDot_DS18B20/

I’m trying to understand what the “sleep” mode is doing as called at the bottom of main.cpp.

I simplified the code and added a simple integer, count, into the outputted message. My code increments “count” so that each time the mDot transmits, a different value is sent. However, the Gateway always receives “count” as 0.

So, after some debugging, it appears that the “sleep” mode being entered causes the CPU to start from the beginning (reinitializing my count) as if being reset.

1) Is this true?

I tried experimenting with the s-called “deepsleep” value passed – here’s the prototype:

void sleep(const uint32_t& interval, const uint8_t& wakeup_mode = RTC_ALARM, const bool& deepsleep = true);

but it appears that no matter the value I pass for “deepsleep”- “no value” (therefore using the default), a value of ‘0’, or a value of ‘1’, the results are the same – the mDot resets and I lose my “count”.

Any help would be appreciated. Thanks.

Mike

• This topic was modified 8 years, 7 months ago by Michael.