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.

BQ34Z100-G1: Step-by-step manual to setup the bq34z100 device

Part Number: BQ34Z100-G1
Other Parts Discussed in Thread: GPCCHEM

Hi forum!

The task to setting up the bq34z100-g1 device to control a 12V NiMH battery from a custom dragino based PCB is becoming a nightmare for us.

Our problem is related with charge time and battery duration: this is a sequence of charge/discharges we have evaluated:

24h charging ==> battery duration: 5h ==> 4h charging ==> battery duration: less than 1h ==> 24h charging ==> battery duration: less than 3 hours

Is this a normal behaviour? Can it be related with a bad calibration of the controller?

We would really appreciate a manual explaining all the procedure to calibrate this controller step-by-step. Along with the datasheet you can find a bunch of documentation spread over the forum and it's completely impossible to choose the right direction to calibrate this properly.

Thank you in advance! :)

  • In another post of the forum I found this should be the procedure to follow:

    1. Configure the basic parameters in the data flash.
    2. Calibrate the pack
    3. Use the GPCCHEM tool to find a good ChemID match for your cells.
    4. Update the ChemID.
    5. Run the optimization cycle.
    6. Verify gauging accuracy by running a few cycles.
    7. Create the golden file for production packs.

    Related with that, these are my questions:

    1. Which are the basic parameters in the data flash we must set up?
    2. What is the procedure to calibrate the pack?
    3. How can we find the ChemID in Linux?
    5. How the optimization cycle works?
    7. How do we create a golden file and save it into different batteries?

  • Related with point number 3, I found document slva725.pdf. It explains there is an online service to discover the battery ChemId:

    https://www.ti.com/powercalculator/docs/gpc/gpcUpload.tsp

    I am sending a test.zip file with two compressed files inside it. Included files are just an example extracted from slva725.pdf document, just for testing the service:


        $ cat roomtemp_rel_dis_rel.csv
        elapsed time (sec),voltage (mV),current (mA),temperature (C)
        20,2975.308,0,28.95893
        30,2974.984,0,28.88429
        40,2975.308,0,28.91459
        50,2974.984,0,28.73499
        60,2975.308,0,28.74904
        70,3008.069,99.9098,28.89834
        80,3023.314,99.9098,28.77718
        90,3300.643,1300.396,28.79125
        100,3360.975,1300.396,28.79125
        110,3404.115,1300.221,28.58133
        120,3439.146,1300.572,28.59754

        $ cat config.txt
        ProcessingType=2
        NumCellSeries=10
        ElapsedTimeColumn=0
        VoltageColumn=1
        CurrentColumn=2
        TemperatureColumn=3

    The service responses with a test-report.zip file with this contents:

        $ cat MiscInfo.txt
        ProcessingType= 2

        $ cat GPC_report.txt
        0
        Error: Wrong data format, start could not be found, make sure file has no multy-line header and is coma or tab separated values. Name: roomtemp_rel_dis_rel.csv

    I tested it with and without the first (header) line, I have converted roomtemp_rel_dis_rel.csv file to DOS format (EOL = \r\n), but I'm getting exactly the same response.

    What is wrong with my csv file? 

  • Gauging Parameter Calculator support send this explanation to me via email:

    "Your file is to small to produce meaningful results (needs to have rest / discharge /rest).
    Certain functions will fail if there is less than 20 points.
    It also should be coma or tab separated, but because of too small size neither would work.
    Try with real test data, preferable coma separated."

    I will try as soon as I have a useful battery available to test.

  • We have used real data obtained from our battery to generate the roomtemp_rel_dis_rel.csv file with this contents:

    30,601,65413,31.950000
    60,599,65406,31.750000
    90,598,65411,31.750000
    120,596,65409,31.750000
    150,595,65410,31.750000
    180,594,65410,31.750000
    210,592,65402,31.750000
    240,592,65410,31.650000
    270,591,65407,31.650000
    300,590,65410,31.650000
    330,589,65407,31.650000
    360,587,65404,31.650000
    390,587,65408,31.550000
    420,586,65405,31.650000
    450,586,65408,31.650000
    480,585,65407,31.650000
    510,584,65408,31.650000
    540,583,65406,31.650000
    570,582,65407,31.650000
    600,582,65404,31.650000
    630,580,65406,31.650000
    660,580,65403,31.650000
    690,579,65406,31.650000
    720,578,65404,31.550000
    750,577,65406,31.550000
    780,577,65408,31.650000
    810,576,65407,31.650000
    840,575,65408,31.650000
    870,574,65406,31.650000
    900,573,65407,31.650000
    930,572,65405,31.650000
    960,571,65407,31.650000
    990,570,65403,31.650000
    1020,569,65406,31.650000
    1050,568,65400,31.750000
    1080,567,65405,31.650000
    1110,565,65403,31.650000
    1140,564,65404,31.650000
    1170,563,65406,31.550000
    1200,562,65402,31.550000
    1230,560,65405,31.550000
    1260,557,65399,31.650000
    1290,541,65396,31.750000
    1320,460,65362,31.650000
    1350,426,65365,31.650000
    1380,418,65365,31.750000
    1410,332,65343,31.650000
    1440,295,65303,31.550000
    1470,292,65297,31.450000

    After sending zip file to online service, we received this response:

    Error: Computation was not successful, but the specific reason was not identified.
    Please check that all files are prepared according to the documentation.
    The support personnel have been informed

    We are waiting support from Texas Instruments to fix this. The service is temporarily offline:

    Sorry! We are currently doing site maintenance.

    This part of the TI website is currently undergoing scheduled system maintenance.
    We apologize for the inconvenience and ask that you try again later.