<![CDATA[Sleep Mode Description]]>How does sleep work, help doc doesn't explain it? When the device goes to sleep, what memory is retained? Does it continue from where it left off or restarts boot & main. Did I miss the doco for this?

]]>https://forum.pycom.io/topic/4304/sleep-mode-descriptionRSS for NodeSun, 14 Jun 2026 00:51:29 GMTWed, 30 Jan 2019 12:52:20 GMT60<![CDATA[Reply to Sleep Mode Description on Wed, 30 Jan 2019 12:52:20 GMT]]>How does sleep work, help doc doesn't explain it? When the device goes to sleep, what memory is retained? Does it continue from where it left off or restarts boot & main. Did I miss the doco for this?

]]>https://forum.pycom.io/post/25336https://forum.pycom.io/post/25336Wed, 30 Jan 2019 12:52:20 GMT<![CDATA[Reply to Sleep Mode Description on Wed, 30 Jan 2019 15:08:59 GMT]]>@misterlisty If you mean deep sleep, in all cases, all CPU memory and CPU state is lost, and on wake-up it's like the module was just powered on.

This is in the docs, though it's perhaps not that clear.

For machine.deepsleep:

https://docs.pycom.io/firmwareapi/pycom/machine/#machinedeepsleeptimems

Stops the CPU and all peripherals, including the networking interfaces (except for LTE). Execution is resumed from the main script, just as with a reset.

Note that at the ESP32 level the RTC domain including its memory is kept active, but there's no support for that at the micropython level.

In the case of Pysense/Pytrack/Deep Sleep Shield-controlled deep sleep, it's even worse, as power to the ESP32 is cut.

]]>https://forum.pycom.io/post/25341https://forum.pycom.io/post/25341Wed, 30 Jan 2019 15:08:59 GMT<![CDATA[Reply to Sleep Mode Description on Wed, 30 Jan 2019 16:03:07 GMT]]>The wording on that isnt brilliant. but yes. it restarts from the top of main.py again. ill update the docs to be clearer

]]>https://forum.pycom.io/post/25347https://forum.pycom.io/post/25347Wed, 30 Jan 2019 16:03:07 GMT<![CDATA[Reply to Sleep Mode Description on Wed, 30 Jan 2019 17:21:41 GMT]]>@paul-thornton To be precise, it actually starts from the top of boot.py :-)

While you're in the docs, I don't think the read_battery_voltage method for the Pysense/Pytrack/etc. is in the docs, you may want to add that as well.

]]>https://forum.pycom.io/post/25352https://forum.pycom.io/post/25352Wed, 30 Jan 2019 17:21:41 GMT<![CDATA[Reply to Sleep Mode Description on Wed, 30 Jan 2019 21:23:58 GMT]]>From what i read above, it would also restart boot.py?

]]>https://forum.pycom.io/post/25367https://forum.pycom.io/post/25367Wed, 30 Jan 2019 21:23:58 GMT<![CDATA[Reply to Sleep Mode Description on Wed, 30 Jan 2019 23:06:30 GMT]]>@misterlisty Yes, it acts exactly as on a power on, it executes boot.py then main.py.

The only way to know whether it's a power on or a wake from sleep (and what the reason for the wake up was) is to call machine.wake_reason.

The possible reasons are listed in the constants at the bottom of the page: machine.PWRON_WAKE, machine.PIN_WAKE, machine.RTC_WAKE, machine.ULP_WAKE.

]]>https://forum.pycom.io/post/25370https://forum.pycom.io/post/25370Wed, 30 Jan 2019 23:06:30 GMT<![CDATA[Reply to Sleep Mode Description on Thu, 31 Jan 2019 11:04:12 GMT]]>@jcaron said in Sleep Mode Description:

@paul-thornton To be precise, it actually starts from the top of boot.py :-)
While you're in the docs, I don't think the read_battery_voltage method for the Pysense/Pytrack/etc. is in the docs, you may want to add that as well.

Thanks ill get this added today if its missing.

]]>https://forum.pycom.io/post/25415https://forum.pycom.io/post/25415Thu, 31 Jan 2019 11:04:12 GMT