M5Paper Shutdown() / Deep Sleep / Wakeup
-
Hello @grundprinzip
you need to know that as long as M5Paper is connected and powered by USB it cannot shutdown. In order for
M5.shutdown()to actually power off your M5Paper, it needs to run from battery.Regarding deep sleep when running from battery and not waking up again:
In order for deep sleep (and light sleep for that matter) to work the ESP32 needs to be powered. M5Paper keeps itself powered via
M5EPD_MAIN_PWR_PIN. However by default GPIOs do not keep their state in deep sleep to conserve power. Therefore ESP32 gets unpowered as soon as it enters deep sleep and as a result it never wakes up again.To change that behaviour you can use the following to lines just before going to deep sleep to keep the required GPIO state even during deep sleep (at the cost of a slightly higher power consumption during deep sleep):
gpio_hold_en(M5EPD_MAIN_PWR_PIN); gpio_deep_sleep_hold_en();BTW: deep sleep and light sleep are two ESP32 sleep modes, but they can only work as long as ESP32 is powered. In contrast when M5Paper is in shutdown mode everything is w/o power except for the RTC clock which then can be used to power on M5Paper via RTC timer or alarm.
M5Paper (and M5CoreInk) have quite a different power architecture than other M5Stack products which can make it a bit challenging to work with. M5Paper also doesn't have a power LED (unlike M5CoreInk) so I find it quite difficult to tell whether it is powered on or off.
Good luck!
Felix -
I had thought to use the M5.shutdown() as a means of timing or delaying between processes. I thought that's how some of the remote sensors were done. Sleep for one minute, wake up, get the weather and stock data (sensor data) and display it or process it, and then go back to sleep, but with it being ignored when plugged in versus not, it's not viable way to do it. I thought oh this will be easy and will help me avoid all the "blink without delay" approach to delaying between processes, but I was wrong. When my device was plugged in, I was getting weather and stock every 5 seconds. Doh! I don't doubt, it all lies in my inexperience. This post and your comments are very helpful in my finding the best approach though. I need to read up and see if you can check to see if you're powered by the battery or by the USB and maybe switch between the two methods, but there again, if one method works for both scenarios, maybe just stick with it.
Thanks! -
Hello @ksprayberry
AFAIK the M5Paper power architecture doesn't allow to tell whether the device is powered by USB or by battery. If you have a solution I'd be interested to hear about.
Thanks
Felix -
@felmue Thanks for the explanation, I have come to a similar conclusion regarding the
M5.shutdown()call as well :) However, this post was stuck somewhere in an approval queue so I didn't reply earlier.Thanks again!
-
Hello @grundprinzip
no worries. Thank you for sharing your conclusion. I appreciate it.
Thanks
Felix -
Hi,
I'm currently using this small work-around to differenciate the power source between battery and USB.
It basically involves monitoring the voltage after initializing M5.BatteryADCBegin() (via M5.getBatteryVoltage() to be more precise). Measuring a voltage over 4200 mV (empirically evaluated!) indicates most of the time a USB-usage. Under that value, there are high chances that the device is on battery.
So far, this work-around is doing its job pretty well for me.
I hope it might help!
Cheers,
t. -
@felmue , I tried your proposal with Arduino IDE and my M5Stack Paper:
gpio_hold_en(M5EPD_MAIN_PWR_PIN);
gpio_deep_sleep_hold_en();but get an error :
invalid conversion from 'int' to 'gpio_num_t' [-fpermissive]
Whats going wrong?
Hans
-
Hello @middelbeek
sorry about that. Try:
gpio_hold_en((gpio_num_t) M5EPD_MAIN_PWR_PIN); gpio_deep_sleep_hold_en();Thanks
Felix -
@felmue Super, now it works! Thanks, Hans
-
-
As I promised here at end of my post under another thread, the
shutdown()is rather buggy in the way awakening is performed.
I'll describe here what I experienced.Anyway one should take this advice of @felmue in account.
There are differentshutdown()overload variations and here bugs or weird things I found.My goal was holding the M5Paper as much as possible sleeping, but at intervals of every full 5 minutes he should awake for about 10 to 15 seconds, perform some tasks (sensors) and go again sleeping to the next full 5-minute moment.
-
overload-2
int shutdown( int seconds );
Even if I calc enough seconds to next 5-minute moment, it seems impossible to stay asleep for remaining 5 minutes. Every 3th minute it is awakening too. This consumes unnecessary double battery power.
So where I want to have this wake up schedule: hh:00 hh:05 hh:10 hh:15 hh:20 ...and so on...
I get this wake up schedule: hh:00 hh:03 hh:05 hh:08 hh:10 hh:13 hh:15 hh:18 hh:20 ...and so on...
This overload-2 has no problems by passing the midnight moment. -
overload-3
int shutdown( const rtc_time_t &RTC_TimeStruct );
This variation works best. Passing midnight (so date change) is no problem but 24:00u should be given als 00:00u. -
overload-4
int shutdown( const rtc_date_t &RTC_DateStruct, const rtc_time_t &RTC_TimeStruct );
is working, but passing midnight in a way to set awake time at 00:00h and increasing the date-parameter does NOT work! Also 24:00u without increasing the date does NOT work.
The only way to pass midnight is awaking just some seconds before midnight and stay awake till after midnight, do the things that has to be done (sample sensors) and go asleep for remaining period (in my case to 00:05u).
I hope others can take advantage of this info.
-
-
I'm coming in a bit late, but fought with this a little bit.
For me,
shutdown()wouldn't wake up at all. The ultimate cause was that the i2c bus wasn't getting properly initialized (another issue for another post -- touchpanel related) so the command to the clock chip was never getting sent.Once it got sent, doing a
shutdown(10)to wake up after 10 seconds worked properly for me... in fact, so properly, you couldn't turn the device off because the alarm persists until deactivated.shutdown(-1)in setup() (after initializing i2c) is necessary to clear the timer alarm upon sketch restart (which I determined by inspecting the library source).Also by inspecting the source and datasheet, overload 4 that Jop says isn't working, I am guessing is because he only advanced the day of month. It looks as though the clock chip compares not just hour/minute/day, but also the day of week (e.g. Thursday) and, reviewing the source code, it doesn't ever consider the month or year at all, nor does the chip even have registers to alarm on these. But it has one for the weekday, so if you don't advance the weekday, the comparison will fail per the datasheet.
-
@casascius How did you even get that far? I have made a project using the new Unified library, and I can not even find the shutdown() functions at all.
EDIT: with the unified library, I am simply trying:M5.Power.timerSleep(600);Even when on USB power, this is 'caught', and so far wakeup is reliable.
-
@jop said in M5Paper Shutdown() / Deep Sleep / Wakeup:
overload-2 int shutdown( int seconds );
The timer function of the BM8563* is based on a 8 bit counter which can be set to be controlled by a clock frequency of 4096, 64, 1 or 1/60 Hz. This means it can timeout with following max interval @ resolution:
62,3 ms @ 244,1 µs
4 s @ 15,5 ms
255 s @ 1 s
15300 s (255 min) @ 60 s (1 min)so intervals above 255 seconds (4 min and 25 seconds) needs to be timed at one minute resolution.
I have however tested this on my CoreINK (UiFlow/mocropython) and found that it rounds down in intervals of 2 minutes (120 s) for some reason.
I made a script to that just put the unit to sleep but increases the sleep interval with 10 sec every time and then uses the clock to measure the actual sleep time. This was the result:
