Hi,
I'm trying to find out how people automate current measurements with the PPK2 beyond doing it by hand in the Power Profiler app.
From the threads here it looks like most people use the unofficial Python API (ppk2-api) in their own scripts, e.g. for production tests or long CI-style runs. A few of those threads mention instability (random bad readings, the PPK2 ending up blinking red after hours), so I'm curious what works for you in practice.
A few questions:
- Do you automate PPK2 measurements at all? With what: ppk2-api, a custom script, something else?
- What does the flow look like (build, flash, measure, compare to previous firmware)?
- What breaks or annoys you most?
I've built a small extension on top of the nRF Connect Power Profiler app that does this from the GUI. The original Data Logger and Scope views stay as they are, and next to them there are tabs where you define scenarios and plans (firmware image, voltage, steps), run them with build/flash/measure done automatically (flashing via J-Link), and compare results between runs. It also has a simulation mode that runs without a PPK2 or a board, and a small energy calculator (e.g. for estimating battery life from the measured profile). It's an unofficial personal project and not available publicly yet, so I'm mostly checking whether this is a real problem for others or just for me. If it sounds useful, tell me what you would need from it (OS, boards, CI support) and I'll share a build with interested people.
Thanks!
(demo:)
/cfs-file/__key/communityserver-discussions-components-files/4/PPK2_2D00_extension_2D00_recording.mp4