M5Dial, no wake up with button
-
Hello guys
@Cognitive5525 : everybody can call any of the sleep / shutdown modes as they like. I try to be consistent in writing deep or light sleep when I mean the sleep modes of the ESP32 and shutdown mode when I mean it is done via MOSFET.
@HappyUser : yes, that is what I am saying. The reason that it cannot be woken up from deep sleep is because the wake button is connected to a non RTC GPIO like you wrote initially. And when powered from the green connector (or USB) M5Dial never fully shuts down (at least in my experiments) and therefore it cannot be powered on by wake button (as it hasn't shutdown in the first place.)
Note: I haven't fully understood why M5Dial cannot shutdown when powered from the green connector. The schematic suggests it should be possible, but maybe the schematic is wrong?
BTW: you can also check if M5Dial has fully shutdown by measuring the 5 V output of the both Groove connectors.
Thanks
Felix -
@felmue said in M5Dial, no wake up with button:
everybody can call any of the sleep / shutdown modes as they like. I try to be consistent in writing deep or light sleep when I mean the sleep modes of the ESP32 and shutdown mode when I mean it is done via MOSFET.
Agree and I know you are. Unfortunately M5Stack are not very consistent! They call it "sleep" when the board is shut down. Their timerSleep() function is supposed to shut down their boards with BM8563 RTC.
I also agree the M5Dial should be able to "shutdownsleep" (new term 😜) when powered from the green power terminals (P5 ?).
However, where does this one lead?
-
Hello @Cognitive5525
you are correct, M5Stack is not consistent and the function
M5Dial.Power.timerSleep(10);, when followed down the rabbit hole, does all of the above (deep / light sleep or shutdown) depending on the core and possibilities.Good find. M5V is the 5V of the M5Stamp. Now we know why M5Dial stays powered on when powered from the green connector. I wonder why M5Stack thought this connection is needed as M5Stamp is already powered through 3.3V. Strange.
Thanks
Felix -
Thank you all for sharing your insights. I hope it offers help to others.
For us it means back to the drawing board.
Regards to you all.
Btw, M5Din meter is also not an option because I recognize the same electronic scheme. -
Hello guys
@Cognitive5525 : I think I know the reason for that 5 V connection between M5Stamp and the M5Dial board. It is required for battery charging when powered from USB. But M5Stack probably should have used a diode there to make sure power can only flow from USB to the battery charger, but not the other way round.
BTW: as an experiment to prove the above I removed the 5 V connection between M5Stamp and M5Dial board and now I can power M5Dial from the green connector and it does a proper shutdown (same as when powered from battery) and can be woken by the wake button.
Please note: If you go that route yourself, please be aware that I cannot be held responsible for any damage that might occur and you most likely void the warranty of your M5Dial.
Thanks
Felix -
Wow, I take full responsibility for my own. But how did you do that? Please elaborate.
I assume you removed the 5volt pin of the M5Stamp. ? -
-
Final question : how did you enter sleep mode or power down?
-
-
@felmue said in M5Dial, no wake up with button:
BTW: as an experiment to prove the above I removed the 5 V connection between M5Stamp and M5Dial board and now I can power M5Dial from the green connector and it does a proper shutdown (same as when powered from battery) and can be woken by the wake button.
Excellent! Now I'm curious : what is the current consumption on the external power input when the board is powered off or "sleeping"
-
@felmue said in M5Dial, no wake up with button:
please find my example here.
I can see you import M5Dial.h is this supposed to be a part of M5Unified?
I use M5Unified.h in my code for my Core INKs.. -
Hello @Cognitive5525
please find my measurements here.
M5Dial.hincludesM5Unified.h. See here.Thanks
Felix -
@felmue said in M5Dial, no wake up with button:
please find my measurements here.
What voltage did you use?
M5Dial.h includes M5Unified.h. See here.
Ah OK! I see you are using a "dedicated" library for M5Dial which in term relies on the "general" M5Unified library. I found a similar "dedicated" for the CoreINK but that seem not to use M5Unified.
So I stick with using M5Unified "directly".. -
Hello @Cognitive5525
above measurements have been done via battery connector @ 4.2 V.
If I use the green connector (and with aforementioned hardware modification) then in shutdown mode I measure about: ~ 1.5 mA @ 6 V
I guess the higher shutdown current (compared to when powered via battery connector) is due to the DC/DC converter converting +VIN into +5VIN and the battery charger IC which both stay powered even in shutdown mode.
Thanks
Felix -
Thanks to Felix.
I also tried his solution of removing the 5V pin from the M5Stamp, power down and wake up with button works perfectly. Even in combination with power timer sleep. Very low current. A big relief for us, save us a lot of time (and €) to find another solution for an unexpected behaviour. Many thanks to Felix!
Btw, you really have to cut the 5 volt pin short because otherwise it still makes contact. -
Hello @HappyUser
you are very welcome. I am glad to hear you got it working to your liking. And thank you for reporting back.
Thanks
Felix
