Hello @Kampi

yes, the RTC (via PMS150G) is used to wake up the system.

And here you can see how the power off pulse is generated in M5Unified.

Thanks
Felix

Hello @Kampi

well, quickly looking though your code I see you are using ESP32 deep sleep. In ESP32 deep sleep the system consumes about 5 - 6 mA according to measurements I did a while ago. See here. And official values from M5Stack here.

With the 1800 mAh battery that gives you a theoretical run time of about 10 days. But since your system isn't in ESP32 deep sleep all the time and the battery cannot be completely emptied before the voltage is too low, 4 days sound about right.

If you want substantially longer runtime per battery charge you need to power off M5PaperS3 instead of using ESP32 deep sleep. Doing that brings the current down to a couple of uAs instead of mAs.

M5.Power.timerSleep(x) is used to shutdown M5PaperS3. See example here.

Thanks
Felix

Hello @katastrofiko

may I suggest that you - as a beginner - try something simpler to start with? Displaying an image from Unit CamS3 camera on M5Stack CoreS3 screen is not exactly a simple thing.

However if you insist on doing that then I suggest you feed the error message into your AI and let AI fix it. Or try the next 100 scripts AI spits out. (Edison ultimately had success too.)

Personal side note: As a human being and software engineer I am glad that AI was not (yet) able to figure it out. That gives me hope for mankind.

Thanks
Felix

Hello @Kombistack

hmm, probably publishing doesn't work due to the delays in loop.

Maybe this example in UIFlow2 Project Zone can help:

M5AtomS3_WiFi_MQTT_UIFlow2.1.5

Note: not tested again with latest UIFlow2.4.2. So it might not work anymore.

Thanks
Felix

Hello @drvval

when I run M5Core2 v1.1 from battery, power consumption gets down to about 5.2 mA @ 4.2 V in ESP32 deep sleep.

BTW: Interestingly when running from battery I can turn off the boost circuit.

In my test I now only turn LCD backlight to zero and turn off boost circuit. When I turn LCD and/or TP off things start to go wrong. My guess is that ESP32 SPI / I2C bus gets confused if devices are suddenly disappearing.

Thanks
Felix

Hello @drvval

BLDO2 controls the 5 V boost circuit.

When M5Core2 v1.1 is powered on, code in M5Unified library checks whether there is external 5 V power available (from M5Bus or Grove port).

If yes, the boost circuit is turned off, and M5Core2 is running from external power.

If no, the boost circuit is turned on (and consumes power) and M5Core2 is running from battery or USB.

Note: why, when running from USB or battery, turning the boost circuit off manually prevents ESP32 from waking up from deep sleep is not entirely clear to me.

In order to go lower you could try to power M5Core2 via 5V on the M5Bus or Grove port. And without USB connection.

(Testing gets a bit tedious this way, as one constantly needs to switch between USB for programming and external power for testing.)

Using external power via M5Bus (but without PIR connected) my M5Core2 v1.1 in deep sleep only consumes about 2.9 mA.

Thanks
Felix

Hello @sk-ys

currently PbHub does not support internal pull-up/pull-down resistors. See FAQ at the end of the documentation page here. I assume the same is true for EXT.IO2.

Note: I have no idea if there are plans to support this feature in the future.

BTW: I faced the same issue a while ago and I resorted to adding some 10 k SMD resistors to the inputs.

Thanks
Felix

Hi guys

curious about what's inside M5StickS3? I opened up mine so you don't have to. See here.

Thanks
Felix

@Micaelaman @torrix
Please notice that Core2 has 2 diffrent versions of PMIC chip, AXP192 and AXP2101. Make sure you are initialize PMIC correctly.

@10sor
Thanks for the feedback, this is indeed a very strange situation.
Could you please provide us the SN number on the package? So that we can check if this is a problem related to specific batch.