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: Behavior of Gauge on client side

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

Hi,
I include the battery specifications here:

Our Battery pack Specifications

Series: BK220SCHU

Nominal Voltage:1.2 V

Rating Capacity: 2200 mAh

Cell Chemistry: NiMH

Charging: -deltaV per cell is 5-10mV (cell)

Rapid Charge temperature: 0-60 degree C

Discharge temperature: 0-75 degree C

ChemID: 6112 (TI suggested).

Battery pack configuration: 10S

Completed learning successfully: 

I flashed the golden file to our embedded board, started working on charge and discharge cycles:

Charge Cycle: we are using NiDV as the charge termination. charging algorithm Fast Charge 1.1A and Intermittent Charge 200 mA for the duration of 4 hrs.

Discharge Cycle: Actually it depends on our application, we have both high power and low power application.

As a result the FCC, RC and SOC are not equivalent in the first charge and discharge cycle, where as in the second cycle of charge and discharge cycle, the FCC and RC resulted correctly, but unfortunately we can't obligate the end user of our application to do Charge Discharge and Charge cycle before using!!
Any suggestions on this??

Thanks in Advance!!

Reddy

  • Hello Reddy,

    Let us look into this and get back to you.

    Sincerely,

    Wyatt Keller

  • Hi Reddy,

    Can you provide a bqStudo log file? Thanks.

    Andy

  • Hi Andy,

    Here I attach the log files of charge and discharge:

    In the attachment, file ChargeLog-00, as you can see the first charge and discharge cycle the the FCC and RC are not equivalent. Where as in the second cycle (Charge and Discharge) the FCC and RC were updated correctly and most serious problem is i cant see the gauge is doing -dV/t charge termination, because as soon the BQ34Z100-G1 see the SOC 100%, the Fast charge is terminated, but according to our algorithm gauge needs to do -dv/t first and then need to start intermittent charge, on other hand I can't obligate the client to do a Charge and discharge cycle.

    Thanks in advance!!

    Reddy,

    ChargeLog-00.xlsx

  • Hello Reddy,

    Please provide the gg.csv file prior to the start of test as well as the bqStudio log file on an EVM.

    Can you also provide some analysis in the text or in picture format of your expectation of the performance vs what the gauge is reporting so we can hone in on the issue you are seeing?