The ever-shrinking size of electronics and sensors has allowed wearables to help us quantify more and more about ourselves in smaller and smaller packages, but one major constraint is the size of t…
Sleep mode, (and other effectively off modes) where it is functionally useless, it can do.
MSP430 can do 140uA/MHz. That is ~7 times the power that this application supplies, and that is not counting any single other chip quiescent current or chip that actively provides useful data. You would have to have a battery anyway or a big cap to provide the needed current for on-states. Or you could run it extremely low frequencies like you said, but those tend to not scale linearly at all with per MHz power ratings. Quiescent currents tend to catch up fast at that scale. I would be extremely doubtful that 150kHz would scale perfectly and wouldn’t have already exponentially decayed to around its lowest possible on-state consumption for the chip. I would definitely have to see tests on that.
The smallest of batteries like the VARTA tiny cells in TWS’s are infinitely more useful and practical and it would take this application months to fill a single cell, discounting all losses.
The MSP430 is just the chip I happen to use at work, if you’re not convinced you could try looking for an actual ultra low power chip, I found the STM32U0 at 70uA/MHz and the STM32U5 at 16uA/MHz in the first result.
Even ignoring selecting a more efficient micro, a smattering of tiny ceramic caps will buy you a few hundred microjoules for bursts. If you’re already operating at 2V you can get a 6V rated 100uF cap in a 1210 package - and that’s after considering the capacitance drop with DC biasing. Each one of those would buy you 200 microjoules, even just one ought to be plenty to wake up for a few tens of milliseconds every second to get a reading from some onboard peripheral (as an example) then go to sleep again.
For sure, you’re not going to be doing any heavy lifting and external peripherals could be tricky, but there are certainly embedded sensor use cases where this could be sufficient.
You said it right there in your comment.
Sleep mode, (and other effectively off modes) where it is functionally useless, it can do.
MSP430 can do 140uA/MHz. That is ~7 times the power that this application supplies, and that is not counting any single other chip quiescent current or chip that actively provides useful data. You would have to have a battery anyway or a big cap to provide the needed current for on-states. Or you could run it extremely low frequencies like you said, but those tend to not scale linearly at all with per MHz power ratings. Quiescent currents tend to catch up fast at that scale. I would be extremely doubtful that 150kHz would scale perfectly and wouldn’t have already exponentially decayed to around its lowest possible on-state consumption for the chip. I would definitely have to see tests on that.
The smallest of batteries like the VARTA tiny cells in TWS’s are infinitely more useful and practical and it would take this application months to fill a single cell, discounting all losses.
The MSP430 is just the chip I happen to use at work, if you’re not convinced you could try looking for an actual ultra low power chip, I found the STM32U0 at 70uA/MHz and the STM32U5 at 16uA/MHz in the first result.
Even ignoring selecting a more efficient micro, a smattering of tiny ceramic caps will buy you a few hundred microjoules for bursts. If you’re already operating at 2V you can get a 6V rated 100uF cap in a 1210 package - and that’s after considering the capacitance drop with DC biasing. Each one of those would buy you 200 microjoules, even just one ought to be plenty to wake up for a few tens of milliseconds every second to get a reading from some onboard peripheral (as an example) then go to sleep again.
For sure, you’re not going to be doing any heavy lifting and external peripherals could be tricky, but there are certainly embedded sensor use cases where this could be sufficient.