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.

BQ28Z610: SOC is always showing 100% on Bq studio

Part Number: BQ28Z610
Other Parts Discussed in Thread: BQSTUDIO

Hi  Team,

I am Using Bq28z610  for single cell gauging, I configured the following setting 

1) Selected proper Chem id.

2)Ensure DA  configuration to 0x00

3)Fet options to 0x20

4) Updated design capacity and other parameters, even though gauge is always reporting 100% soc.

. As per my understanding, SOC should vary on charging and discharging but it always remains fixed on  100%.

  • Hi Abishek,
    You need to perform a learning cycle before the gauge can accurately report SOC. Pls see app note below on the procedure.
    www.ti.com/.../getliterature.tsp
    thanks
    Onyx
  • Hi  Onyx ,

    Perform learning cycle, got update status 0X0E. 

    1).Can I use this srec file as the Golden image? 

    2).I tried to write  srec file from learned gauge to new gauge out of 5  in two I  can write successfully. With other three I am getting acknowledgment is not received from the device only during programming. These are device which I power up earlier and the battery was connected so the battery is getting charged and discharged without setting proper parameter. Kindly suggest how I can resolve this.  

     

  • Hi Onyx ,

    Solved second issue not doing UNSEAL FULL ACCESS, able to sucessfully program one more board , other two boards are not getting connected with BQstudio at all, one board got connected once after that it is not getting connected.
  • Ensure that your battery voltage is high enough, >3.4V. Also, i suggest updating the firmware on your ev2300. I see you are using version 3.1c. You should be using version 3.1m or 3.1r. Also, ensure to press the wake up button or connect a voltage on pack + to wake the device from shut down mode. If you are unable to communicate with a device, you might be in ROM mode. Uncheck the "execute after programming" field and click the execute button to exit ROM mode.

    hope one of these proposals helps.

    thanks
    Onyx