I just checked with a scope, and this is what I see on a standard unprogrammed Puck with 1v89 firmware and no code on it.
It's exactly what you'd expect - so if you're seeing something strange on your meter I'd probably put any problems down to that. I wouldn't waste too much time trying to narrow down uA consumption until you can stick it on something where you can really reliably view the power consumption over time, or you might just end up chasing artefacts of your meter :)
It's likely that the sample window of your meter is such that occasionally the pulse of power draw gets inside it, and occasionally it doesn't - you're basically seeing an interference pattern :)
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
I just checked with a scope, and this is what I see on a standard unprogrammed Puck with 1v89 firmware and no code on it.
It's exactly what you'd expect - so if you're seeing something strange on your meter I'd probably put any problems down to that. I wouldn't waste too much time trying to narrow down uA consumption until you can stick it on something where you can really reliably view the power consumption over time, or you might just end up chasing artefacts of your meter :)
It's likely that the sample window of your meter is such that occasionally the pulse of power draw gets inside it, and occasionally it doesn't - you're basically seeing an interference pattern :)