Yeah...I do plan to :/ sub to "lost in circuits" for that stuff, I'm in the middle of making the first video on there, but it's about ruining an oscilloscope kit 🤣
yes - I actually have one waiting to test. I think it can last a week with all the power save settings on full using this, but vid on that as soon as I get chance! :)
I didn't store that apparently (oops), but here's the repository for the next video (in progress and will be on my other channel!) code which has code in it on line 150 onwards to do the same thing. github.com/pufferfish-tech/m5stick_batterytests Basically all commands are in the AXP192 datasheet which I will explain a bit in the next video.
Thank you for making this video! Does the battery life change much depending on the use of the sensors? Did you have Wifi/Bluetooth on when testing this?
As far as this one was concerned I just wanted to know the basic battery life as it comes without optimization, as a baseline. But - watch this space! It turns out that the screen may not even be turning off when you ask it to, and this is the main consumer of power way above and beyond the wifi/bluetooth. This explains why the screen brightness doesn't affect the battery life as much as I expected. So as it stands, I am aware that you can send some commands directly to the axp192 chip as per community.m5stack.com/topic/1025/m5stickc-turn-off-screen-completely/15, and I am building a list to test in a more involved video. It's interesting to see how far it will go. In answer to your question though - my approach would be to fire the sensors and comms up on an interrupt, I have done this with arduino chips to good effect and had months of life from one set of batteries...so it's not a concern as long as it is able to be turned off and activated by interrupt :)
As usual...it appears it's not that simple, and looking into it raises other questions too. I seem to have opened a can of worms on this one, hoping to get some results and a video out in the next week if I can get enough data by then! :) Thanks for the sub!
@@LostInTech3D I run a program on M5stack that wakes up turns Wifi on grabs weather forecast every 10 minutes from internet and displays it. taking about 7 seconds. And then goes to sleep, while keeping the screen dimmed but on permanently. The m5Stack runs for days like this. So agreed the processor and wifi/bluetooth and then backlight use more power the screen on, in that order. It's all about application and battery life. So a hard test to do.look forward to your further tests
Hi, also from my side, please tell how much is the improved battery life
what about m5 stickC plus with 122mah?
Hi, are you still planning to release the findings on batter life improvements you teased! :)
Yeah...I do plan to :/ sub to "lost in circuits" for that stuff, I'm in the middle of making the first video on there, but it's about ruining an oscilloscope kit 🤣
Where can I buy charger for my m5stick c plus2?
XD genius
Yes true , this is true , thank you .
Is this next video coming?
A fair question. 🙄 I did a lot of work for it, and found a solution for 1 week battery, so I hope so.
@@LostInTech3D Any update on this video?
I think the m5stack tailbat battery is compatible with this.
yes - I actually have one waiting to test. I think it can last a week with all the power save settings on full using this, but vid on that as soon as I get chance! :)
whats the code for the battery details
I didn't store that apparently (oops), but here's the repository for the next video (in progress and will be on my other channel!) code which has code in it on line 150 onwards to do the same thing.
github.com/pufferfish-tech/m5stick_batterytests
Basically all commands are in the AXP192 datasheet which I will explain a bit in the next video.
Thank you for making this video! Does the battery life change much depending on the use of the sensors? Did you have Wifi/Bluetooth on when testing this?
As far as this one was concerned I just wanted to know the basic battery life as it comes without optimization, as a baseline.
But - watch this space! It turns out that the screen may not even be turning off when you ask it to, and this is the main consumer of power way above and beyond the wifi/bluetooth. This explains why the screen brightness doesn't affect the battery life as much as I expected.
So as it stands, I am aware that you can send some commands directly to the axp192 chip as per community.m5stack.com/topic/1025/m5stickc-turn-off-screen-completely/15, and I am building a list to test in a more involved video. It's interesting to see how far it will go.
In answer to your question though - my approach would be to fire the sensors and comms up on an interrupt, I have done this with arduino chips to good effect and had months of life from one set of batteries...so it's not a concern as long as it is able to be turned off and activated by interrupt :)
@@LostInTech3D wait, the screen isn't turning off really?
(Subbed by the way. Great content! Keep them coming)
As usual...it appears it's not that simple, and looking into it raises other questions too. I seem to have opened a can of worms on this one, hoping to get some results and a video out in the next week if I can get enough data by then! :) Thanks for the sub!
@@LostInTech3D I run a program on M5stack that wakes up turns Wifi on grabs weather forecast every 10 minutes from internet and displays it. taking about 7 seconds. And then goes to sleep, while keeping the screen dimmed but on permanently. The m5Stack runs for days like this. So agreed the processor and wifi/bluetooth and then backlight use more power the screen on, in that order.
It's all about application and battery life. So a hard test to do.look forward to your further tests
HELLO WORLD