• State Not Answered
  • Replies 6 replies
  • Subscribers 63 subscribers
  • Views 249 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 324212
Options

NPM1300 battery profiling capacity vs vTerm

robsrick

I'm profiling a battery with the following specs

I've just finished the first profile and for a capacity of 500mAh i only got down to about 3.2V and it gave me a warning about not fully discharging which may mean the profile won't be accurate. I guess the capacity is higher than nominal for that particular battery, so it's not covering the full discharge profile.

1) Why doesn't the software just discharge to the cut off voltage and provide a capacity to ensure it covers the full capacity?

2) should i be giving an artificially high capacity to make sure it covers the full range, or is the way i'm doing it okay?

Regards

Robert

Parents
  • 0

    1) nPM PowerUP should discarge down to the configured cut off voltage, it is hard to say why this didn't happen. Can you please share the files generated by the profile session so we can take a look?

    2) No need to set artificially high battery capacity. nPM PowerUP uses this to set correct discharge current during profiling. The battery model generated by the profiling will represent the real battery capacity.

  • 0 in reply to ketiljo

    Hey, the 3 temp profiles have now finished.  I think i misunderstood the warning i was getting in the first instance. it was telling me that the capacity had exceeded the 500mAh i had stated so it took longer than expected to get to the cut off voltage?

    I've been testing 4C, 25C and 45C and the final profile, 45C finished last night. Unfortunately i got the following error. I checked it last night and it had gotten to about 476mAh discharged and was all going fine but this morning i saw the following:

    when i restart profiling i get the following:

    I tried unplugging the battery from the PMIC and re plugging but no luck. Next, i plugged the battery into my custom board which charged it using an NPM1300 successfully for a minute or two. When i plugged it back into my NPM1300EK for profiling it was then detected so i pressed continue to charge the battery again.

    I'm going to re-run the 45C profile but i'd like to understand what might have caused this error and how i can prevent it?

    Robert

Reply Children
Related

core_v2_widget.Hide()