Power Profiler Kit tremendous delay, what's going on?

[Davide]

Hello, I'm trying to measure the current profile with the PPK (HW Rev:1.1.0, SW: 1.1.0) but I see a lot of strange behaviors.

My firmware initializes everything and the waits a button event. When it detect the button event it starts scanning with the maximum duty cycle, it also starts advertising. I expect to see the current consumption to go to something between 6mA and 10mA when I press the button, but that is not happening. What I see is something like having the graph updated with huge delay (10-20 sec, maybe more). It is very difficult to say what is happening because what I see on the graphs seems to be totally independent of what the MCU is doing.

Now I notice that if I set the Average Window to be 4 sec long it takes 10 second to fill the whole graph....This doesn't make sense to me.

Thank you, Davide.

EDIT:

System details:

OS: windows 10 Enterprise (10.0.15063)

Python: 2.7.13

Screenshots:

What I see just after the calibration ends:

After a while (15s), without touching anything on the board, the consumption grows to 2mA (it may be the CPU in the while(1) loop, I'm not sure because I didn't optimize energy consumption aspects, I'm sure the radio is off here)

When I press the button (see the mark) that turns the radio on nothing change on the current. You can see the terminal monitor that indicate both the scanning and the advertising are ON.

finally after 60 sec I see the consumption to go to the expected value

[wlgrd]

I think it is because of the logging module introduced in 1.1.0.

Can you try commenting out line 196 of ppk.py;

# plotter.start_log_thread()

This was primarily tested on Windows 7, which seemed to have handled it fine, but not on Windows 10 and Linux.

[wlgrd]

Davide; to me it got perfect (switching between external and dk measurement shows up instantaneous), but I know people are struggling if using hubs and older machines. Can you make sure to use a proper cable directly to your computer? No docking stations or the like. Also, can you post some hardware specs for your computer?

Also, as the user guide says; don't run trigger at the same time as average if you want the average to be your main focus. It causes some package drops as well as some delay for some people.