This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Unknown error using Gauging Parameter Calculator (GPC) to generate Golden Image

Other Parts Discussed in Thread: BQ40Z50-R1

Hi,

I am trying to generate the golden image for a BQ40Z50-R1.

I followed the steps from this document: http://www.ti.com/lit/ug/sluub45a/sluub45a.pdf

But when I upload the .zip folder (see attach) on this page: https://www.ti.com/powercalculator/docs/gpc/gpcUpload.tsp

I receive the report saying that "Computation was not successful". The files present in the zip are: config.txt, gg.csv, and sysrate_rel_dis_rel.csv, which seems to be right. I plotted the curves of the cycle, they look like the ones from the examples.

What am I missing?

Cheers,

Yann

2016-08-26gaugingCycleSMALLEST.zip

  • Hi Yann,

    What is the chemID for your battery? In your config file it's listed as 6c98. It should be a numerical number.

    Best Regards,
    Ben Lough
  • I solve the problem. The chem ID was wrong, it was actually 0189 in my case. It was wrong because first time I upload it, the error report was saying that the chem ID from config.txt and gg.csv didn't match. So I naively copied the value under "System Data,Integrity,Static Chem DF Signature" into the chem ID in the config.txt. After that, the error report isn't telling that the chem ID doesn't match anymore... this wasn't the source of the error.

    The error was because the chemistry configured in the golden image we were flashing in the memory was wrong (or just old? the chemID was the right one but not the Static Chem DF Signature), so we reconfigure the right chemID and generate a new gg.csv, and it was working.

    I just got a negative k temp, which is out of bound. This is probably expected considering the temperature profile provided. But still, a warning would be nice when computed values are actually out of the boundaries accepted by the chip.

    Thanks for the support,

    Yann