this post was submitted on 01 Feb 2024
12 points (100.0% liked)
Ask Electronics
3316 readers
1 users here now
For questions about component-level electronic circuits, tools and equipment.
Rules
1: Be nice.
2: Be on-topic (eg: Electronic, not electrical).
3: No commercial stuff, buying, selling or valuations.
4: Be safe.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Most of those devices do in fact sleep most of the time. It's like your phone: it may last 2-3 days standby with the screen off and nothing running but if you're running a heavy CPU/GPU load it'll chew through the battery in maybe 2-3 hours or even less pretty easily. A smart watch pretty much never runs at full power other than the maybe 5 seconds when you look at it and the display lights up and there's some animations going. Otherwise it's pretty much just polling the sensors every now and then, and going right back to sleep.
It's not hibernation or even conventional S3 where everything turns off, it's more like S2idle on modern laptops. It's still on but it does power off a lot of the peripherals and drop the clock to near nothing, but it's ready to wake up quickly on timers and interrupts, and it can handle some networking and go right back to low power within a millisecond. And similarly to PCs, those chips change speed based on demand. No point running at 800MHz if it only needs 50 MHz to read sensors every now and then and keep the Bluetooth connection alive.
Even Arduinos go from a few mA to a few μA when in sleep mode.
So basically its not possible for me with my little experience in embedded stuff and general tech savyness because its just so ridiculously well optimised and oiled? I could hack around and replicate some of it at least.
You will have a hard enough time just finding a SOC that you can get documentation for without signing and NDA and promising to buy massive quantities of them.
I thought of getting a low power arm cpu like the one in the raspberry pi zero 2 or something less powerfull and then use the rp2040 as a coprocessor. The rp2040 only uses a few ma so its a good choice and i could use interrupts to wake the main cpu. I can also put the rp2040 into sleep and only operate the screen and that would basically be a normal watch and it would last for months.
That's a lot to fit in a watch. The PCB layout will be difficult and the requirements for it will likely exceed what the usual prototype PCB manufacturers can produce.
The RP2040 is a power hog. It takes 180µA in its lowest power sleep mode. There are other microcontrollers that can be in run mode and use less power than a sleeping RP2040. I would suggest looking into some of the STM32L series microcontrollers. They can get down into the nanoamp range in sleep mode and run less than 100µA/MHz.
Thanks for the suggestion but of course ill look into what mcu i want better when it comes to that. A larger pcb at first doesnt bother me that much but i want to get down to watch size in the far-future. This is only a hobby project so nothings set in stone. Im also working on a flashlight right now so im balancing these two projects.