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: SOC Jump (99% --> 0%, 0% --> 100%)

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

Hello,

Could you please tell me the cause and how to deal with it?

attached log, gg file, golden image file

50001453_01.zip

regards,

Kagawa

  • Hi Kagawa,

    Is your RemainingCapacity and FullChargeCapacity always 0? I also noticed there are some parameters not filled in, did you remove them?

    Best,

    Jessica

  • HI Jessica-san,

    Yes, RemainingCapacity and FullChargeCapcacity are always 0 after SOC jumped from 99% to 0%.

    Which parameters ?

    Regards,

    Kagawa

  • Hi Jessica-san,

    How about this ?

    Regards,

    Kagawa

  • Hi Jessica-san,

    There is a information from customer as below.

    I tried RESET.
    The result remained unchanged at 0%.

    Specifically, I did the following, and there was no change at 0%.
    ・ Check that it is 0% in bqStudio.
    ・ UNSEAL, and after sending the RESET command, refresh the screen.
    ・ bqStudio relaunched just in case
    ・ UNLEAL_FULL_ACCESS, RESET command transmission, screen refresh
    ・ bqStudio relaunched just in case

    Regards,

    Kagawa

  • Hi Kagawa-san,

    Did your customer run a learning cycle on the gauge? Can you make sure they are using the correct chemID? If the RemainingCapacity and FullChargeCapacity are always 0, that means there is most likely something wrong with their configuration. 

    Best,

    Jessica

  • Hi Jessica-san,

    Customer did run a learning cycle on the gauge. Customer was using the GPCCHEM tool and 641 was best.

    Chemistry ID selection tool, rev=2.49		
    		
    Configuration used in present fit:		
    ProcessingType=1		
    NumCellSeries = 3		
    ElapsedTimeColumn = 0		
    VoltageColumn = 1		
    CurrentColumn = 2		
    TemperatureColumn = 3		
    		
    Best chemical ID : 641	Best chemical ID max. deviation, % : 4.49	
    		
    		
    		
    Summary of all IDs with max. DOD deviation below 15%		
    		
    Chem ID	max DOD error, %	Max R deviation, ratio
    641	4.49	0.5
    644	5.9	0.43
    643	7.36	1.2
    6112	7.54	1.3
    6111	7.84	-113.94
    6116	8.17	11.71
    6117	8.23	6.44
    6120	8.96	0.39
    6108	9.67	-113.94
    6119	11.01	1.04
    6103	11.67	-49.88
    6121	11.86	-45.6
    6107	14.04	-121.03
    		
    Max. deviations for best ID is within recommended range. Chosen best chemical ID is suitable for programming the gauge.		
    		
    		
    Selection of best generic ID for ROM based devices like bq274xx		
    		
    		
    Device / Family #1		
    Generic Chem ID	Device/ Voltage/ Chemistry	max DOD error, %
    3142	bq27421-G1D: 4.4V LiCoO2	100
    354	bq27411-G1C: 4.35V LiCoO2	100
    312	bq27421-G1B: 4.3V LiCoO2	200
    128	bq27421-G1A: 4.2V LiCoO2	200
    Best generic ID 3142		
    Warning: Generic ID Deviation is so high that it is most likely due to anomaly in the data. Please check that data files have recomended format, units and test schedule		
    		
    		
    Device / Family #2		
    Generic Chem ID	Device/ Voltage/ Chemistry	max DOD error, %
    1210	bq27621:  (ALT_CHEM1) 4.3V LiCoO2	100
    354	bq27621:  (ALT_CHEM2) 4.35V LiCoO2	100
    1202	bq27621: (default) 4.2V LiCoO2	200
    Best generic ID 1210		
    Warning: Generic ID Deviation is so high that it is most likely due to anomaly in the data. Please check that data files have recomended format, units and test schedule		
    		
    		
    Device / Family #3		
    Generic Chem ID	Device/ Voltage/ Chemistry	max DOD error, %
    3230	bq27426: (default) 4.35V LiCoO2	100
    3142	bq27426: (ALT-CHEM2) 4.4V LiCoO2	100
    1202	bq27426: (ALT_CHEM1) 4.2V LiCoO2	200
    Best generic ID 3230		
    Warning: Generic ID Deviation is so high that it is most likely due to anomaly in the data. Please check that data files have recomended format, units and test schedule		
    		
    		
    Warning - missing or corrupt parameter in config file: ProcessingType Default value 1 will be used		
    

    regards,

    Kagawa

  • Kagawa,

    Please confirm you are using a NiMH type cell chemistry? This type of chemID has unique challenges mainly in the charge direction. Please make sure you are correctly getting a VCT event. 

    1) The reason for the Jump to 100% is because FCC is going to 0mAh so 0RemCap/0Fcc is resulting in 100% RSOC. This will happen if Charge termination is learned low or resistance is learned too high whcih has the gauge simulate to FCC=0 right away. 

    2) What do you mean by PowerOn? Do you mean you are starting the load? 

    Thanks,

    Eric Vos

  • Hi Eric-san,

    This is a comment from customer.

    SOC and FCC were calculated by resetting the Ra Table and Cell V at Chg Term of DataFlash to the initial values.
    When only the Ra Table of DataFlash was returned to the initial value, SOC = 0%.

    The following are the initial values ​​of DataFlash and the values ​​of NG products.
    Battery is NiMH (4cell).
    Can you find out the cause of the SOC jump from these data?

    Cycle Count               Default:    0 , NG: 23
    Lifetime Max Temp         Default: 25.5 , NG: 54
    Lifetime Min Temp         Default: 25.0 , NG: -39.1
    Lifetime Max Chg Current  Default:    0 , NG: 1623
    Lifetime Max Dsg Current  Default:    0 , NG: -1028
    Lifetime Max Pack Voltage Default:  187 , NG: 297
    Lifetime Min Pack Voltage Default:  187 , NG: 158
    LT Flash Cnt              Default:    0 , NG: 34

    Cell V at Chg Term        Default: 1503 , NG: 1390
    Avg I Last Run            Default: -464 , NG: -442
    Avg P Last Run            Default: -582 , NG: -557
    Cell Delta Voltage        Default:    1 , NG: 4

    Ra Table (R_a0_14)        Default:11873 , NG: 20112
    CC Offset                 Default: -1483, NG: -1466

    Regards,

    Kagawa

  • Hello Kagawa,

    we experienced the same problem with the bq34z100-g1 and were pointed by a TI-employee that we had set the settings for 'Dsg Current Threshold', 'Chg Current Threshold' and 'Quit Current' incorrect. This caused the Ra-table to become dramatically unrealistic (you can check these), resulting in a wrong SoC calculation. The suggestion was to set 'Dsg Current Threshold' to C/16.7, 'Chg Current Threshold' to C/10 and 'Quit Current' to C/25. After this the SoC calculation at least did not show any jumps anymore and the Ra-table got corrected over time to more realistic values.

    Hope this helps, goodluck.

  • Hello C P van Teylingen-san,

    Thank you for your information.

    Eric-san,

    Is this condition valid for all NiMH ?
    Is there a way to determine this?

    Regards,

    Kagawa

  • Hello Kagawa-san,

    You should confirm that the values stated above are correct (their respective C rating) otherwise the gauge will not know if it's charging, discharging, or if it can enter relaxed state.

    Sincerely,

    Wyatt Keller