-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Current integral is not accurate? #46
Comments
Starting of measurements can give 1A spikes, ignore the beginning, then compare the bottom sleep current with GUI. |
I'm experiencing the same issue, even when ignoring the spike at the beginning of the measurement. I have a device that wakes up periodically and I wanted to measure how much charge it takes for every wakeup, measuring through the GUI gave me a consistent measurement every time. Measuring using a python script and this library gave me very inconsistent results with a range or up to +-10% of what it should be. I even compared to a different current measurement taken with Keysight equipment and I got the same results as I got using the GUI. I would really appreciate help on this matter. |
Side note: |
In my tests I used only one PPK, and just changed the method of sampling (GUI vs python) |
You could try it with constant voltage plus resistor in series with PPK and a good DMM, if that's the same then it's a timing thing. |
I'm trying to use this library with my PPK2 in order to calculate the total current consumption of my device, by integrating the current samples.
Calculating the integral works and gives me some number, but the number is way off, when comparing it to a 2nd ppk2 running alongside with the original GUI. E.g. when measuring over 20 minutes, I measure 57 Coulomb with the library, compared to 46 Coulomb with the original GUI.
Did someone run into a similar problem? Could it be, that the device is configured differently when used by the nordic GUI? (Spike filter?)
The text was updated successfully, but these errors were encountered: