• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 64 subscribers
  • Views 436 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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-R2: Learning Update Status stuck at 05 in R2 device

Jean Eddim
Prodigy 100 points
Part Number: BQ34Z100-R2
Other Parts Discussed in Thread: BQ34Z100-G1, BQSTUDIO

Dear all,


We have a design including a LIFEPO 8S2P battery. In order to do a learning task, we cannot get the complete Update Status going to 04-05 and finally 06.

We get the 05 (Qmax updated), but not 06 (Table Ra updated)

The learning procedure we use is as follows:


1)Battery discharged an relaxed.      Updated Status=0.    RupDIS=1, VOK=0, OCVTAKEN=0 CtrlStatus=0014 Flags=0116
2)It Enable.  Update Status goes to 04                               RUPDIS=0, VOK=1, OCVTAKEN=0 CtrlStatus=0013 Flags=0116
3)Reset.                                                                              RUPDIS=1, VOK=0, OCVTAKEN=0 CtrlStatus=0015 Flags=0116
4)Now wait until RDIS=0, VOK=0 and OCVTAKEN=1       RUPDIS=0, VOK=0, OCVTAKEN=1 CtrlStatus=0011 Flags=0196
5)Charge the battery at 1A                                                  RUPDIS=0, VOK=1, OCVTAKEN=0 CtrlStatus=0003 Flags=0116
... continue with the learning

If I continue the battery charging process, I get the FC, and finally an update of QmaxCell0. And Update Status=05

But as soon as battery start charging, the OCVTAKEN goes to 0, and this means that the learning process is not going to finish properly. Never goes to 1 afterwards
I think the charging of battery should not clear the OCVTAKEN, instead the Flags should continue at 0196.

This flag should be set when the battery is charging or discharging, and clear each time we have a new OCV reading

I attached the log obtained. It is not a complete log, but I am sure the error is located in this part of learning

Note: The learning task is performed with the FW2.01 in BQStudio (it is for device -R2), but I am doing the learning over a BQ34Z100-G1 device
If I use the same procedure with the FW0.16 (but with different parameters), it finishes learning correctly, But we suppose the new firmware 2.01 has some advantages we would like to use

Please help us with this issue. Maybe the parameters file has to be checked. Any advice would be appreciated.
Attached included the gg.csv and log file. if you can test it, please use a CHEMID=0474


0310.log.txt4034.param.gg.csv              

  • 0
    TI__Genius 12215 points

        The major feature of bq34z100R2 is the supporting on high voltage, high capacity batteries with its voltage or capacity value runs out of 32767, with some scaling factors facilitated to scale up the voltage and capacity. But v2.01 has some issues to be fixed, please go along with G1 at present.

        However, I would still like to take a look on the log file for learning cycle done with R2 device if you can upload the file to this E2E thread.

  • 0 in reply to Steven Yao
    Prodigy 100 points

    Hi all,

    We attached a complete learning log, where you can find last Update Status =05.

    Also we include the gg file after finished learning to this point (relax, charge, relax, discharge, relax)

    -Battery is a 6Ah. So the Qmaxcell0 it is updated in the gg file, and update status goes to 05

    - Ra0 table is updated as well, But Ra0x is not updated. And Update Status never goes to 06

    I think the OCVTAKEN flag during the battery charge is not correct. Please check the log and the gg file

    Please note this learning is done under the last firmware 2.02

    Thanks in advance

    Regards

    Param_after_learn=05.gg.csv            2577.log1.txt

  • 0 in reply to Jean Eddim
    TI__Genius 12215 points

        There is no OCV_TAKEN bit in R2, it is replaced by REST bit, it is replaced with REST bit which indicates the voltage is stable enough to be used as OCV, I found the relax time after discharge is pretty short, it needs at least five hours for Qmax update to happen, for LiFePO4, it could be 48hours under some particular condition.

       Please can you advise the chemical ID that has been programmed to the gauge before you do the learning cycle?

  • 0 in reply to Steven Yao
    Prodigy 100 points

    Hello,

    The battery pack is 6Ah LFP (8S2P). Chemid is custom, (0474)

    The test sequence is starting with a discharged, relaxed battery:

    Charge at 950mA
    When charged FC=1 (Flags= 0x0210)
    Relax 2h and Learned status=05
    Discharge at -990 mA (value between C/5 and C/10)
    Relax 5h. CtrlStatus = 0x0013. And never goes to 0x0011, so VOK=1 always

    In other test, I increased the relaxation time after charge to 5 hours, and increase after dicharge too, but it doesn clear VOK.


    In summary:
    The QmaxCell0  is updated, Ratable is updated but Raxtable is not updated and Learned Status is stuck at 05

    What are the requirements for Learned Status go to 06?. And why is not fulfilled all of them?

    Attached you can see the gg file and log file after the learning cycle

    Regards

    log1.xlsx             param1.csv   

  • 0 in reply to Jean Eddim
    TI__Mastermind 27321 points

    Hi Jean,

    The log shows you discharged with a rate of ~C/6 and discharged down to  22552 mV which is approximately 2.8V. 

    The chemID you are using has the following characteristics. 


    I suggest you charge to full (~3357 mV), this should be the same as the charging voltage stated in cell datasheet. Then discharge to empty. ChemID shows the lowest cell voltage is 2400 mV, you can confirm with the cell datasheet.

    You can try discharging with smaller rate. We recommend up to C/10. 

    Please export gg file before and after the learn cycle. This will tell you if Ra updated.

    Ensure that RUP_DIS is not set in the Control status before the discharge cycle. Sending IT_ENABLE command should disable RUP_DIS.

    Regards,
    Jose Couso