you are very welcome. I am glad to hear you got it working to your liking. And thank you for reporting back.

Thanks
Felix

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

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"..

please find my measurements here.

M5Dial.h includes M5Unified.h. See here.

Thanks
Felix

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..

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"

please find my example here.

Thanks
Felix

correct, that is what I did. I removed the 5 V pin of the M5Stamp.

Thanks
Felix

@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

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.

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

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?

@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

external power.

External power as-in via the green power terminals?

On the other hand when M5Dial is in shutdown mode the MOSFET is off (the only thing still running is the RTC IC). So then either the wake button or the RTC can power the M5Dial back on.

Agree!
This is completely similar to the CoreINK, but as I mentioned in this post: when the board is shut down but the BM8563 RTC is setup to wake it up then this is in "my book" also a kind of sleep mode.

from my understanding M5Dial has two sleep modes and a shutdown mode. The sleep modes are ESP32 specific (deep sleep and light sleep). The shutdown mode is done via MOSFET and HOLD GPIO.

In ESP32 deep or light sleep most of M5Dial is still powered; only ESP32 is actually sleeping. In other words the MOSFET is still on and therefore the wake button (or the RTC interrupt) cannot do anything and has no effect.

On the other hand when M5Dial is in shutdown mode the MOSFET is off (the only thing still running is the RTC IC). So then either the wake button or the RTC can power the M5Dial back on.

That said, in my tests I found that M5Dial can only fully shutdown when powered from the battery connector. If it is powered from USB or the green connector my M5Dial doesn't shutdown. (You can see that by the red LED in the back which is still on.)

BTW: here are my measurements for the two ESP32 sleep modes and shutdown mode when powered via battery connector:
ESP32 light sleep: ~18 mA / 4.2 V
ESP32 deep sleep: ~14 mA / 4.2 V
shutdown mode: ~ 4.8 uA / 4.2 V

Thanks
Felix

Maybe this only works when powered by a battery. In our use case it should be powered by an external source connected to the green connector on the back side.

(* Btw, the button itself works, i have checked that already in another test program *)