ESP 01 DEEP SLEEP POWER CONSUMPTION MANUAL
ESP 01 DEEP SLEEP POWER CONSUMPTION SERIES

That being said, in a non sterile environment (in terms of 2.4ghz noise), and the distance they've mentioned, 1MBps (8mbps) out of the possible 54mbps sounds right to me for real life said in ESP-NOW: Esp-now long range mode seems like a better use case overall. Either way I wouldn't choose the highest bitrates even if I were, as there are maybe a handful of use cases (like the esp-cam), and the drawback of reduced reliability and range at those rates. I'm sure such a board could be useful for many MCUs.Īs for the data rates, I've never measured, nor would I get the maximum speed even if I did, since I'll never be that close to the router with a clear line of sight.

ESP 01 DEEP SLEEP POWER CONSUMPTION MANUAL

If anyone ever designs a general purpose board with a tpl5010, a resistor for the timer, a mosfet, feedback from the mcu to latch the mosfet or signal the timer the work is done, and maybe even an optional spot for a low quiescent LDO regulator like the ht7333, me6211, or mcp1700, capacitors, and a manual override for a button or sensor interrupt, I would love if you could share it. Since most of my project are 1 off, I don't have experience with designing pcbs or working with such small package components. Power on the device and observe how absolutely not-flat and super-spikey your micro is while running under normal use.That sounds like a really nice idea.

ESP 01 DEEP SLEEP POWER CONSUMPTION SERIES

Put a low-ohm shunt resistor in series with your supply and place your scope probes across the resistor. It's the reason the entire market for IoT power development tools exists, because existing solutions are worse than non-functional, they will straight up lie to you.Įdit: if you have an oscope on the bench you can see this behavior for yourself. They're great for seeing how fast your phone is charging, not so great on picking up the power profile of microcontrollers, particularly when developing for low power where you'll be implementing a lot of deep sleep and short wake intervals. If you buy a cheap USB power tester (handy as they are) and start using it to develop a low power solution, you're going to be REALLY confused when the device is consuming way more power than what is shown on the USB power meter you're using.Īs handy as they are, they simply aren't suitable as development tool because the thing you are specifically looking for is exactly the thing they can never pick up. That's exactly the problem I'm pointing at. You need to be able to catch transients on the order of microseconds. The USB-based power monitor units you're thinking of have a sample time on the order of single digit hertz. Likewise, their discharge curve can also model a battery. Higher end models can work in both directions, so they can also have power pushed back to them and they'll 'charge' to simulate a specified battery chemistry, allowing you to bench test and synthesize performance against various types and sizes of batteries. tl dr: fast switching between a bank of 6 different shunt resistors to get the dynamic range you need. If you want a deep dive, TSP did a video review of one of the popular options (Joulscope) explaining exactly how the thing works. This is kind of the worst case for digital sampling as you can often trade speed for resolution but here you need both.

Also, the values you want to measure can be between nanoamps and amps, which is a huge dynamic range. Problem here is that transient power spikes happen quickly so you need a very fast sampling speed to deal with that. You'd think it'd be straightforward to just keep a running tally of how much energy a device is using but it's surprisingly difficult.

Esp 01 deep sleep power consumption