Skip to main content
8 events
when toggle format what by license comment
Mar 25, 2015 at 1:56 comment added Ignacio Vazquez-Abrams 43% is... less terrible, but still not great.
Mar 25, 2015 at 1:35 comment added ulidtko @ConnorWolf Well, if you do actually measure the rail current of an Uno running the delay-based blink sketch vs a rewrite of the same based on timer interrupts and properly deep sleeping — you'll see that sleeping the MCU is not so pointless. In my case, the numbers were something like 30 mA vs 17 mA. Still quite a drain; but your point has been invalidated by an experiment.
Mar 27, 2014 at 3:48 comment added Ignacio Vazquez-Abrams @Mr.Floppy: IOW, pick something else. Something with fewer pieces.
Mar 27, 2014 at 3:31 comment added Connor Wolf Yep, but my point is that you can't even get meaningfully relevant power conservation on most any arduino boards, since even their vregs have horrible quiescent current (2 ma +, IIRC). Then there is the FTDI/ATmega16U2, which you can't turn off, etc....
Mar 27, 2014 at 3:30 comment added Ignacio Vazquez-Abrams Absolutely. Someone that wants to conserve every last bit of energy will design their own board and spec their components out accordingly.
Mar 27, 2014 at 3:28 comment added Connor Wolf Really, if you want to actually get an arduino to be low-power, you need an arduino pro (or any other board with no onboard usb-serial), and then you'd need to put a regulator with decently low quiescent current draw on it. It's a bit involved.
Mar 27, 2014 at 3:25 comment added Connor Wolf Sleeping the MCU is pointless, since the rest of the parts on a common uno consume so much power it doesn't provide any meaningful reduction in overall consumption..
Mar 27, 2014 at 3:20 history answered Ignacio Vazquez-Abrams CC BY-SA 3.0