• State Not Answered
  • Replies 5 replies
  • Subscribers 74 subscribers
  • Views 854 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 283659
Options

PPK2 save to CSV

wayne roberts

I try the new save to CSV feature in v3.4 power profiler.

I try to save all, but it says 0MB.

The sample rate is 100ksps, and duration is 301 seconds, but would result in 30.1 million samples in the CSV file.

I think maybe there is a limit to how many samples can be saved to CSV in v3.4 of power profiler?

I try again at 10k samples per second, for 255 seconds, and it can export about 2.5 million lines, and the csv file is good.

  • 0

    Hi

    Thank you for reporting this, we had an unintentional limit to the .ppk files we were able to export from the Power Profiler in an earlier version, so it might be a similar thing with the CSV feature now. I'll report this to the developers and let you know what I find out.

    Best regards,

    Simon

  • 0

    Hi

    We have identified the bug I think. We will release a fix for this soon. Until then, the workaround will be to set a higher sampling than you would like, and then manually stop the sampling before it stops automatically.

    Best regards,

    Simon

  • 0

    Hi

    v3.4.1 of the Power Profiler app was just released and should have fixed this issue. If you want to use the export all feature on an old file (by loading one) you will need to use the new SELECT ALL feature that came with this release and use export selection. Thank you for reporting this!

    Best regards,

    Simon

  • 0

    yes, it was fixed.  I recorded in data logger for 300 seconds at 100ksps.  After it finished, export to CSV geneated 30 million records and a 840Mbyte output file size.   Too much data  for me, 10ksps is enough for me.  But 100k is the default, and its working.  Its all good.

    The other completely different thing i noticed with pc-nrfconnect-ppk is in the REAL-TIME mode, it appears that the stop button doesnt work if its not triggering on the current level.  But stop button works eventually when current level occurs.  So the stop button should always work in real-time mode after starting.   As a side note, it appears that real-time trigger is rising edge on current, and perhaps there should be choice to select falling edge or both rising or falling trigger on current.  I don't need real time mode, data logger is good, but i just noticed it.

  • 0

    Hi

    Glad to hear we fixed the initial problem. Indeed, the real-time mode is a bit "laggy". We're working on improving the experience here as well, and it will likely improve with future releases. I generally prefer using the data logger either way though, but I understand there are uses for the real time logger as well. Thank you for your report though!

    Best regards,

    Simon

Related
Terms of service