bq34z1xxFVM battery lifetime issue

Gordon,
Do you mean that the SOC drops more than you expect? Have you verified that you have a good ChemID selection and have run the optimization cycle to update Qmax and the Ra table? These steps a critical to good gauging performance. Here are some links for more information.

e2e.ti.com/.../1774822

Tom

Hi Tom,
The steps in the 1774822 does not work for us. See below my comments. Could you please advise the correct step for this?

Thanks
Gordon

Configure the dataflash with appropriate parameters suitable for your application; configure pack's chemistry and perform calibration. (We did this. We selected the chemistry ID from the list in the Battery Management Studio)
Activate impedance track.(We did this)
Charge the pack to charge termination. (We did this)
Allow the pack to rest until the OCVTIAKEN flag sets. (We failed, OCVTAKEN always set(red))
Discharge the pack at a C/10 to C/5 rate to the Termination Voltage. (We did this)
Allow the pack to rest until the OCVTAKEN flag sets. Qmax should update and Update Status should increment to 05.(We failed, the bq34z1xxFM board loose the connect with the EV2300 when the battery depletes)
Fully charge the pack to charge termination.
Allow the pack to rest until the OCVTAKEN flag sets.
Discharge the pack at a C/10 to C/5 rate to the Termination Voltage.
Allow the pack to rest until the OCVTAKEN flag sets. The Ra table should update and Update Status should increment to 06.

Gordon

Please provide the log file and I will try to help you to determine why the optimization cycle failed. Also export a gg file from the gauge.

Tom

Hi Tom,

  The PC app does not recognize the EV2300 even we install the latest driver from your website under win10. We got the EV2300 working under the win 8 machine. However, it does not allow us to generate any log file under win 8. We went through couple charging and discharging cycles(we enabled the QEN through IT_ENABLE command and ignore the OCVTAKEN in the recommended step). It seem the percentage reading make more sense and as we expected now. We would like to run more test instead of this learning process. Should be disable the QEN and what other parameter should be disabled before running test on the battery? We also generated the golden image. How should we program the golden image into the IC in the future after test.

Thanks,

Gordon

Hi Tom,

   We calibrated the battery and exported the binary file to download. However, we bricked our bq34z1xxFVM board last time. How can we download the exported parameter to the dev kit without brick it?  We are also ready to download the parameters to our designed board. Could you please provide steps for us to download the parameters to the board. Our manufacturer also wondering how they should initialize the chip in the production.

Thanks,

Gordon

Gordon.
I reviewed your previous postings and I am not sure which version of the device is being used. Are you using the bq34z100 or the bq34z100-G1? The devices are physically the same, but the firmware is different. The bq34z100-G1 is the latest version and you should use this version. You will use the bqStudio evaluation program to communicate with this firmware and yo should be using version 1.3.52. If you are not using this version, then please download it from the bqStudio website. I have not used it with Windows 10, but i know that some people have been working with it.

You mentioned that you are trying to import parameters back into the device. Assuming that you are working with the -G1 device and bqStudio, are you trying to import the srec? Did you brick the device after programming the srec file to the device? Did you press select the Execute button after importing the file?

We also have a bqHiCellProduction tool that can be used to program and calibrate the device, but let's get the bqStudio option working first.
Tom

Hi Tom,

  Thank you for your reply. I believe it used bq34z100 in the bq34z100EVM dev kit we have. We used bq34z100-G1 on our own board.  We have exact same issue described in this thread after brick the dev kit: 

We did press the execute button after download the code.  Could you please provide instruction on how to download the parameter into the board after calibration?

Regards,

Gordon

  

The proper procedure to update the pack in production is to program the data flash and then calibrate the pack. You should keep IT disabled until these have been completed. You can then send the IT Enable and Seal commands. You have be programming a corrupted data flash file to the device. Please attach this file and I will check it.

Hi Tom,

  The battery management chip is only connected to our main processor through I2C bus. Do we need preload the data to our main processor and then download the data to the battery management chip using our main process? What data need be loaded into the data flash of battery management chip? Do we need calibrate each  unit in the production?

Regards,

Gordon

Hi Tom,

  Could you please answer my last post for us to understand more on the procedure on the manufacture side. Attached are the files we exported.

Regards,

Gordon

I failed to attached file. Do you have email or other approach I can use to send file to you

Gordon,
Your uC may be able to use the commands and data in the df.fs format file to program the data flash. The df.fs file contains the full data flash contents and it can be exported using the Golden Image screen in bqStudio. You mentioned that your uC is connected to the bus when trying to program the srec. There cannot be any I2C activity present when programming the srec or the device will get bricked.
Tom

Hi Tom,

  Is df.fs file the binary file we can write to the data flash directly? Do you have sample code we can use to write the df.fs file to data flash. We have I2C drive in our uC and we verified it can talk to the battery IC correctly.

Regards,

Gordon

The df.fs file is a txt file that can be edited with a program such as Notepad++. It contains the I2C commands and data to program the data flash memory. The df.fs format was originally used with the Flashstream tool for our single cell devices and here is the file format document that can help with the file.

4454.Flash Stream File Format.pdf

Hi Tom,

 I think to load the data from the uC  to the battery IC is fine. My understanding is we will need 1k flash memory on our uC to store the data for the battery IC. We did select the right chemical ID for  our battery. The performance is  fine from the  dev kit. I think we  have not test  it on our own board yet. We need the procedure to load the data  to the battery IC and test the performance. Cou

Hi Tom,

  Did you check the image file we sent to Dan? Are those files corrupted?  Our firmware engineer think it is not good idea to load the data flash using uC due to the limitation on our flash memory size of uC (this will be the last option if we do not have any other choice). We are thinking to bring out the pins for the I2C bus on our board. In the production, tour manufacturer may be use those pins to program the board using the bqstudio. Will this work? We are planning to test the process on the dev board before try our board using following steps. Please let us know if they are correct

1. Disable IT

2. Download the exported df file to the dev board using bqstudio

3. Calibrate the board (We are not sure how to calibrate in the production, please advice)

4. Enable IT

5. Read battery life time