• State Verified Answer
  • Replies 5 replies
  • Subscribers 89 subscribers
  • Views 540 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 349446
Options

Long nPM1300 battery profiling time

pipoket

Dear Nordic Devzone,

I have some questions regarding battery profiling procedures.

1. Is it normal for battery profiling to take longer than 8 days? As you can see in the attached screenshot, I'm trying to profile the battery with 5,000mAh capacity but it does not end even after 5 days. I think it will take at least 3 days more for the profiling to be complete judging by the rate. I do understand that the profiling will take longer than 48 hours if I try to profile the capacity larger than 800mAh but 5 days seems too much for me. Would there be anything that I might be doing wrong?

2. AFAIK, the maximum configurable capacity value on nPM PowerUP software has been reduced from 3000mAh to 800mAh since the version 2.1.0. I was able to configure the maximum capacity up to 3000mAh on the version 2.0.1 and the profiling also completed within 4-5 days even with the 5000mAh battery. I think that the profiling speed become significantly slow after the update. Is this an intended behavior? Is there any way for me to increase the profiling speed? If not, is it ok for me to downgrade and go back to the version 2.0.1?

Sincerely,
Woosuk Suh

Parents
  • 0

    Hmm thats sounds about right. I did the profiling with 1800mAh battery and its took two complete days to finish. With 5000mAh battery, 4-5days falls in the range. Not sure though why the profiler takes so long anyways. Could be made faster >>>>>>>>

  • 0 in reply to rajeev

    The problem is that the current sinking capabilities of the FG Board isn't strong enough to discharge large batteries within the same timeframe as smaller batteries. The process involves discharging the battery using 1/5 C  pulses, but the FG board can maximum discharge 600 mA or so. This means that a 5000 mAh battery could take twice as long as normal. However, 5 days does sound a bit excessive. Can you look at the "all events" log file and confirm whether the process is still active? The expected output is idle periods of measurements of ibat=0, followed by active periods where ibat=~0.6. The idle period is typicall 20 minutes, and the active period 10 minutes

Reply
  • 0 in reply to rajeev

    The problem is that the current sinking capabilities of the FG Board isn't strong enough to discharge large batteries within the same timeframe as smaller batteries. The process involves discharging the battery using 1/5 C  pulses, but the FG board can maximum discharge 600 mA or so. This means that a 5000 mAh battery could take twice as long as normal. However, 5 days does sound a bit excessive. Can you look at the "all events" log file and confirm whether the process is still active? The expected output is idle periods of measurements of ibat=0, followed by active periods where ibat=~0.6. The idle period is typicall 20 minutes, and the active period 10 minutes

Children
No Data
Related
Terms of service