Power Profiler v.4.2.0 + PPK2 - Plot stops working after a while

[jmaha9000]

Reporting this here as the project GitHub asked that bugs be reported via DevZone.

The latest Power Profiler v4.2.0 has introduced an annoying issue - when running the Power Profiler for a long time (sourcing 3.7V power and collecting logging data, set to 1,000 samples/sec, sampling forever), typically leaving it to run overnight, after a whlie it stops logging new data. Pressing Stop and Start doesn't restart the graph, it just stays blank despite sourcing power to the DUT. If I close + restart the Power Profiler app, it works again. Additionally, I can deselect the PPK2 device and re-select it, and then starting logging works again.

I'm running macOS Sonoma 14.5 on a MacBook Pro with an M1 Max chip.

[jmaha9000]

Here's a video of the app in this nonfunctional state. This time it appears to be fully connected, with all controls visible, but stopping/starting the graph results in a blank graph.

 

[jmaha9000]

I should mention too that this happens consistently when the app is left running overnight. In previous versions I used to leave the app running for long periods of time with no issues; the plot would stop when the buffer filled up, but I could stop/start recording no problem.

[jmaha9000]

I'm not quite sure what buffer size I was using previously. I generally left it at whatever the default setting was.

[Kenneth]

Okey, do you remember any other configuration, such as sampling rate?

Kenneth

[jmaha9000]

I left that as the default selection as well.

[jmaha9000]

Some more information - this failure is affecting me probably 10 times per day. I'm using the PPK to power a device and characterize its behavior.

When this failure happens:

• The nRF PPK stops supplying current to the DUT and stops being able to log data, interrupting any ongoing test I'm running

To resolve it, I have to:

• Click the "Eject" button next to the PPK2 info in the upper left
• Click "Select Device" and select the PPK2
  • it will appear to connect successfully but does not
  • This enters the weird state where the "Set supply voltage" box is unavailable but the "Enable power output" toggle is functional but does nothing
• Click "Eject" button again
• Click "Select Device" and select the PPK2
  • The app now functions again.

[Kenneth]

Hello,

I have reported your latest findings, and the team is aware of the issue. Unfortunately the problem seems difficult to fix, so I don't have an timeline for you. I guess you will need to periodically check for new releases of the PPK software and hopefully it will be fixed not too long.

Kenneth

[jmaha9000]

Thanks for the update.

[jmaha9000]

Some additional info if it's helpful. I've reverted to Power Profiler v4.1.3 and it appears to be more stable. I have "auto reconnect" enabled. It seems to lose connection and shut off power to the device around once or twice per day, but this is much more manageable than 4.2.0 cutting out every hour or so. Additionally, when it does happen, I can just reenable the "Enable power output" toggle and press "Start" and it immediately starts working again, without having to jump through the whole "select device multiple times" workaround I was having to do with 4.2.0.

[Ziga Miklosic]

I'm facing the same issues with the PPK v4.2.1 on Win10. Start buttom seems to gets broken after a while and furhtermore measurements over the night always stops as soon as I left the office -.- 

 Nordic QA  Any update on that topic?

[Ziga Miklosic]

I'm facing the same issues with the PPK v4.2.1 on Win10. Start buttom seems to gets broken after a while and furhtermore measurements over the night always stops as soon as I left the office -.- 

 Nordic QA  Any update on that topic? Are there any 


Update: 

I've played around a bit and found out if I set "TEMP DISC" slider to minimum solved my issues. I'm not sure what is happening. Some clarifications would be nice.

By reducing "TEMP DISK" slider increases "Available disk space". For me, measurements weren't working as avalilable disk space was 0GB.

My recomendation is to add some sort of warning pop up window in case there is no available disk space and the "Start" button is pressed. So that users won't get confused and potencially think that the "Start" button is broken (as I was). 

Let me know what do you think 

[Kenneth]

Hi,

I don't think the problem you experience with Win10 is related to the Mac issue, but it's good to hear you found the problem with Win10. I have forwarded your observation with Win10 so it can be looked into and improved (maybe throwing an warning of disk full or similar).

Kenneth