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.

BQ40Z80: Learning process - VOK bit not setting after initial discharge and rest period

Part Number: BQ40Z80

Hi,

I have a problem with the learning process part of making a golden file for my battery. The [VOK] bit is not setting after the initial discharge and rest period.

The initial discharge is done with C/3 current (this current is not specified in the learning process document) and the battery is resting until the IT Status:[REST] bit is set and left for a few more hours.
When I start to charge the battery the IT Status:[VOK] bit is not set automatically which in turn does not update QMax when resting after charging.

The steps are the same as in the SLUA848 document:
1. Send the GAUGE_EN command to set the [QEN] and [GAUGE_EN] bits high
2. Send RESET command to set [RDIS] bit high
3. Check to see if LStatus() is 0x4 (only the [ITEN] bit is high)
4. Discharge the battery to empty
5. At end of discharge the [TD] and [FD] bits are high and the [EDV] is high when the Term Min Cell V is reached
6. Rest until [REST] bit is high, sometimes the [RDIS] bit did not clear even after more than 5 hours 
7. Start charge, the [VOK] bit doesn't set 

The battery used is a Tattu LIPO 12000mAh 15C 22.2V 6S1P.
Battery voltage range 19.2-25.2V (3.2-4.2V per cell) 
Nominal voltage 22.2V

The GPC report for this battery said that the best Chem ID match is 5201 with a 1.33% deviation. 

The GPC_report, gg, and log file of the discharge, rest, charge, rest are attached.

Tattu_12Ah_Learning_process.gg.csvTattu_12Ah_Learning_process.log

Chemistry ID selection tool, rev=2.52		
		
Configuration used in present fit:		
ProcessingType=2		
NumCellSeries=6		
ElapsedTimeColumn=0		
VoltageColumn=1		
TemperatureColumn=2		
CurrentColumn=3		
		
Best chemical ID : 5201	Best chemical ID max. deviation, % : 1.33	
		
		
		
Summary of all IDs with max. DOD deviation below 3%		
		
Chem ID	max DOD error, %	Max R deviation, ratio
5201	1.33	1.25
1669	1.66	1.05
1138	2.02	1.19
1939	2.03	1.85
298	2.05	1.62
1146	2.06	1.62
2634	2.08	1.58
5166	2.19	1.3
1279	2.2	3.34
2597	2.32	1.07
2341	2.41	1.38
2029	2.73	5.25
2071	2.93	1.66
1222	2.97	5.33
		
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	12.12
354	bq27411-G1C: 4.35V LiCoO2	12.41
128	bq27421-G1A: 4.2V LiCoO2	101.93
312	bq27421-G1B: 4.3V LiCoO2	110.81
Best generic ID 3142		
Warning: Deviation for best generic ID is above recommended level for this device / family. Consider using another device, flash based gauge or RAM programming of custom ID.		
		
		
Device / Family #2		
Generic Chem ID	Device/ Voltage/ Chemistry	max DOD error, %
1210	bq27621:  (ALT_CHEM1) 4.3V LiCoO2	12.06
1202	bq27621: (default) 4.2V LiCoO2	12.14
354	bq27621:  (ALT_CHEM2) 4.35V LiCoO2	12.41
Best generic ID 1210		
Warning: Deviation for best generic ID is above recommended level for this device / family. Consider using another device, flash based gauge or RAM programming of custom ID.		
		
		
Device / Family #3		
Generic Chem ID	Device/ Voltage/ Chemistry	max DOD error, %
3142	bq27426: (ALT-CHEM2) 4.4V LiCoO2	12.12
1202	bq27426: (ALT_CHEM1) 4.2V LiCoO2	12.14
3230	bq27426: (default) 4.35V LiCoO2	13.68
Best generic ID 3142		
Warning: Deviation for best generic ID is above recommended level for this device / family. Consider using another device, flash based gauge or RAM programming of custom ID.		
		
		

  • Hey Vladimir,

    There are some interesting parameters in your gg file that stand out to me (cc gain is quite low) and I will be digging deeper into this over the next few days. I will get back to you as soon as I have a solution here.

    Best,

    Jackson

  • Vladimir,

    Sorry for the delay, this has just been a very interesting case that has required a great deal of testing to try to find a root cause.

    It is still unclear to me why exactly you are not getting a QMax update after the initial dsg-relax period. Typically when the REST bit is set and RDIS is cleared a QMax update has occurred. There are a few things that could disqualify a QMax update but none of those are immediately present to me either.

    As mentioned before, the one thing in your gg file that sticks out is your cc gain at .103 mOhm. This seems quite low and could contribute to an offset error >1% which would disqualify your QMax update. 

    I have two things you can try here:

    1. Set the cc gain value closer to 1 and log this behavior. I expect this should fix it but I am still curious to see the behavior here

    2. Wait over 5 hours after the initial dsg-relax cycle to see if a forced QMax update is taken here.

    Try each of these and get back to me with your results. If setting the cc gain higher does not solve this issue let me know and we can proceed further.

    Thanks,

    Jackson