I've found the BattLab-One a helpful tool to determine how a change in MCU firmware affects power consumption of the DUT. The cost vs reward ratio is quite fantastic. It is not without it's quirks, but once you use it a few times you'll figure out how to work around them.

A few things to note:

1. The DUT Sleep Duration value on the main screen is only used for calculations. To change the actual sleep mode duration you want to capture for, the setting is in the Options pull down menu at the top. It defaults to 1 second which is insufficient if you say have a BLE device that only advertises every 4 seconds for example.

2. The unit appears to sometimes report strange usage patterns if the DUT is sending a PWM signal to an LED for example. To deal with this, sometimes you need to run the Capture again.

3. Be sure you set your output voltage before click PSU Output to On. You can fry some sensitive components this way. Fortunately the software starts up with a default value of 1.5V which is usually not going to cause much a problem.

4. The sleep current range setting may need to be adjusted back to the default of 800uA-500mA if you are making use of the 'Persist Sense Resistor' function. Otherwise when you wake your DUT up, it could brown out.

And one suggestion I have for the developer:

It would be nice to see the Data Acquisition settings to obviously separate from the Data Calculation settings. Mixing them together is a bit confusing. I would move 'Number of Cells', 'Battery Capacity', 'DUT Cutoff Voltage', and 'DUT Sleep Duration' down near Step 4 as they have no bearing (that I can tell) on to how the data collection is performed.

Thanks for making a great tool!

Looking at previous reviews I can say the software has improved. I'm on a W10 machine, no crashes, lockups, or hanging. When I need sub 10uA reading I put a precision resistor in parallel with the load and do the arithmetic. I found one bug, see github issues, and it was fixed in a day. I have a uCurrent and a Current Ranger on my bench and the logging capabilities of the BattLab-One make it the go to device when working on low power projects. Should you call the sleep(100) or the deepSleep(100) function while waiting for the temperature sensor? That delay(100) is costing you more than you know.

Don't want to hand over your DMM7510 to the software guy, the BattLab-One is the solution. Doesn't matter how much time you spend sourcing that low Iq LDO if firmware isn't up to the task.

I hate to give a bad review. The hardware is well designed other than the 10 uA minimum for current which I knew about before buying it. 1 uA should be the target current. The PC software hasn't been working for me, i.e. locks up frequently with the exe image provided (I have to pull the USB cable and restart the program), I haven't been able to load all the python libs yet to run the latest script. It takes a long time to start, I'm thinking the code is walking though all the com ports to auto-detect, I would rather the program launch quick and have me select the port. I was hoping to at least use it to monitor (in real-time) to see the current profile (that would be worth $100) but this is not a feature of the current python script. The Digilent USB Discover with a current sense front end is what I normally use which is a great tool for current profiling (~$300). The Otti is also good also but more expensive (~$600). So the python script needs work I'm thinking of trying to update the python code. The hardware should have provided the JTAG connector since it is open source.