BQ27421-G1: non-linear SOC values during linear (de-)charge

l.wittland

Part Number: BQ27421-G1
Other Parts Discussed in Thread: GPCCHEM, EV2400, BQSTUDIO, BQ27Z561-R1,

Hello,

I'm using a bq27421-G1A fuel gauge in a n embedded project.

The battery is a LiPo with 4.2V maximum charge (3.7V discharge) and 110 mAh (407 mWh) capacity. The terminate voltage of our design is 3.2 V.

Capacity, energy, and terminate voltage have been programmed to the fuel gauge via I2C. We didn't explicitely set the taper rate as the default is fine for us. We've also re-read them to verify that the values were set correctly.

After programming, we completely de- and recharged the battery one time as suggested by the documentation.

In the next decharge process, we continuously read the Voltage, SOC and average current from the fuel gauge and put them in a table:

Voltage is scaled on the left side of the diagram, the other values on the right (so SOC dropped from 96 to 2).

While the power consuption of the device was onstant most of the time and the voltage dropped more or less linary, the SOC dropped to fast in the middle of the recharge and nearly didn't change in the last third. Considering that the battery wasn't empty when we stopped the measuring (as terminate voltage was set to 3.2V), the SOC was at or below 10% when the battery was actually half full.

At charging, we got a similar table:

Scaling as above.

At the start, there were some funny readings I'm willing to ignore. After that, while the (loading) current was again quite stable and the voltage more or less linear, the SOC again shows a wrong behaviour, as it rises to slow in the first half and then does a sprint to catch up.

I know that the fuel gauge doesn't use the voltage to determine SOC but internal math and simulations. Unfortunately, these simulations don't seem to get it right in my case. Do you have any ideas what might have gone wrong here?

Regards,

Lasse

over 5 years ago

0 Wyatt Keller over 5 years ago

TI__Guru** 105590 points

Hello Lasse,

Did you perform a successful learning cycle on the gauge and upload the best chemID for your battery using the GPCCHEM tool to find the ID?

Could you log these cycles with bqStudio and an EV2400 and export the .gg file?

Sincerely,

Wyatt Keller

0 l.wittland over 5 years ago in reply to Wyatt Keller

Intellectual 425 points

Hello Wyatt,

what do you mean with with a successful learning cycle?

I let the battery discharge one time and then recharged it; the findings I posted came from the second discharge. I didn't enable fast learning, though. Will try this.

I didn't upload a ChemID to the fuel gauge, since the documentation claimed that it it is static in this device family.

Our company doesn't own a EV2400. Even if we did, I don't see how we could use it. The fuel gauge is integrated in an I2C bus on our device, there is no way we can route the I2C connections out to the EV2400 (or disconnect our microprocessor I2C host).

0 Wyatt Keller over 5 years ago in reply to l.wittland

TI__Guru** 105590 points

Hello Lasse,

It looks like you should be getting a valid Qmax from doing a cycle of the battery so you shouldn't need a full learning cycle. Can you upload the data you collected so we can take a look at it? Your pictures didn't populate from the first post.

You are correct, it should already have a chemID profile within the gauge and you should only need to update the parameters and get a Qmax update for best gauging.

Are you able to recreate the configuration with an EVM and EV2400? This would help with the debug greatly because of the functionality of bqStudio.

Sincerely,

Wyatt Keller

0 l.wittland over 5 years ago in reply to Wyatt Keller

Intellectual 425 points

Hello Wyatt,

I've attached the excel sheet with my measurements and curves; the time between two lines/readouts is 10 sec.

We don't have an EV2400 at our company. Even if we did, I don't see how we could use it since the fuel gauge is already placed on our circuit board and connected to an ARM via I2C. We don't have any 'naked' fuel gauges.

In the meantime I've tried to understand the learnuing process a little better. If I understood it right, the fuel gauge should adjust it's value for qMax and the RA table from time to time as it learns the battery chemistry. I believe this qMax value is "qMax cell 0" from the state subclass in data memory (although I havn't found a definitve answer to that in the documentation), so I've monitored this value for some time (read it every few minutes). The value didn't change for a complete decharge cycle (havn't tried recharge yet). The QMAX_UP-Flag in the CONTROL_STATUS wasn't set either.

As this isn't what I expected to see (and it would explain why my curves don't get better over time), is there any not-so-obvious setting that may prevent the fuel gauge from learning?

Best regards,

Lasse

Fuel_Gauge.xlsx

0 Wyatt Keller over 5 years ago in reply to l.wittland

TI__Guru** 105590 points

Hello Lasse,

Yes that's correct, the section in the TRM that explains Qmax cell 0 is 6.4.2.3.1.

We would need to see the VOK and RUP_DIS bits as well to see if the gauge is allowing Qmax updates and resistance updates or not.

It is easiest to debug when the system can be recreated with your battery and EVM so we can use bqStudio to log all the values to see what the gauge is doing during charge and discharge.

Sincerely,

Wyatt Keller

0 l.wittland over 5 years ago in reply to Wyatt Keller

Intellectual 425 points

Hello Wyatt,

your right, I overread that part in the documentation.

The values I read from CONTROL_STATUS are usually 0x008E or 0x008C. The 8x is the first byte I received via I2C, which I identified as the 'low byte' of the documentation. So RUP isn't set.

I tried to set qmax manually to 16410, that worked. Still, as I read it out a day later it was reverted to the default 16384 (most likely due to an empty battery).

What possible reasons could the fuel gauge have to not learn?

As for EVM:

I still don't understand how I could recreate my system with the EVM, since I cannot simply connect it to my embedded design via I2C. Neverless, we're trying to order one (and an EV2400, too).

Regards,

Lasse

0 Wyatt Keller over 5 years ago in reply to l.wittland

TI__Guru** 105590 points

Hello Lasse,

Good, I hope that resolves the problem. The Qmax should be set by the gauge when it learns the Qmax value for the battery. Because your battery is very small capacity it may be hard for the gauge to calculate the SOC without learning the Ra and Qmax values.

Using bqStudio with the EVM and your battery will let us see all the register values during charge and discharge with the logging feature so we can see if anything is preventing the Qmax update.

Sincerely,

Wyatt Keller

0 l.wittland over 5 years ago in reply to Wyatt Keller

Intellectual 425 points

Hello Wyatt,

while we wait for the equipment, I've put together everything we do to the fuel gauge. Maybe you can see something that may cause the update problem we face.

Generally, '-->FG' denotes data send to the fuel gauge (via I2C). Reversely, '<--FG' is data read from the fuel gauge. I've always omitted the I2C adress byte. The comments in () are what we expect the command to do.

At initialisation:

-->FG: 00 80 00 (Unsealing)
-->FG: 00 80 00 (Unsealing, 2nd time))
-->FG: 00 13 00 SET_CFGUPDATE
(1.5 sec gap to enter CFGUPDATE. We skip the polling here)
-->FG: 61 00 (block data memory control)
-->FG: 3E 52 (subclass 82)
-->FG: 3F 00 (block offset)
-->FG: 60 (read checksum)
<--FG: AC (returned checksum)
-->FG: 4A (read design capacity, design energy and terminate voltage)
<--FG: 05 3C 13 60 05 3C 0C 80 (returned values)
-->FG: 4A 00 6E 01 97 (write design capacity and design energy)
-->FG: 50 0C 80 (write terminate voltage)
-->FG: 60 AE (write new checksum)
-->FG: 00 42 00 (soft reset to exit CFG_UPDATE)
<--FG: -- (I'm not sure what this is)
(1.5 sec pause to leave CFG_UPDATE)

Notes:
-We do this every time the device (re-)boots, since we observed some cases in which the fuel gauge reset the values for design capacity, design energy and terminate voltage, which is quite anoying, too.
-We plan to add some code to write initial qMax and RA-values at this point, too (of course we still need those initial values, bringuing us back to the original problem).
-We skip the two polling steps suggested in paragraph 3.1 of the documentation; instead, we simply wait for 1.5 seconds. Doesn't seem to be a problem.
-We don't reseal the fuel gauge. This is for convenience, since the device may access the secured areas again at a later time and doesn't have to unseal it again.

At cyclic intervals (approx. every 10 sec):

-->FG: 1C (read SOC)
<--FG: 4E 00 (returned SOC)
-->FG: 04 (read voltage (and some other stuff))
<--FG: 93 0F 88 01 D3 03 DD 04 A9 03 +x (returned data (not all bytes shown in the log))
-->FG: 10 (read avg. current (and some other stuff))
<--FG: 30 00 FC FF 38 FF 3C 05 BF 00 +x (returned data)

Every minute, we also send:

-->FG: 00 00 00 (order to write CONTROL_STATUS to adress 0x00)
-->FG: 00 (read adress 0x00)
<--FG: 8E 00 (returned CONTROL_STATUS, the last byte is always 0x00)

If the QMAX_UP flag would ever be set we would read it and store it in processor RAM, to use it as initialisation values on the next initialisation.
Same goes for RA tables.
For a time, we always read the qMax value at this point just to assure we didn't check the wrong flag. However, the qMax value didn't change.

Any suggestions?

Best regards,

Lasse

0 Wyatt Keller over 5 years ago in reply to l.wittland

TI__Guru** 105590 points

Hello Lasse,

It looks like all your commands are correct, we will still need to check your configuration with the EV2400 and EVM to see if you can get valid updates with your battery.

Have you been able to do any further testing?

Sincerely,

Wyatt Keller

0 l.wittland over 5 years ago in reply to Wyatt Keller

Intellectual 425 points

Hello Wyatt,

I've received the EV2400 and the EVM module and tried another discharge and charge cycle.

The result: It didn't learn. I've never seen QMAX_UP or even RES_UP at '1', qMax stayed at 16384 the whole time (except for some readout glitches). I've added the logs.

Notes:

I've set design capacity, design energy and terminate voltage to the values of my batterie (105 mAh, 378 mWh, 3,2V) prior to the logging

I've inserted the EVM between the battery and my device. So there are actually two BG27421-G1A involved - the one from the evaluation bord and the one on my chip. I didn't monitor 'my' fuel gauge this time, but it's SOC seemed to be a little better than the one on the evaluation bord.

During discharge, the device unfortunately powered down on more than one occasion - as can easily seen in the avg. current column which didn't do the SOC any good.

So, what do we do next?

Sincerely,

Lasse

1778.discharge.log 8306.charge.log

0 Wyatt Keller over 5 years ago in reply to l.wittland

TI__Guru** 105590 points

Hello Lasse,

Are the logs you provided all the information the gauge logged? It seems to be missing other flags and config registers, it is also missing lots of data points and doesn't have time stamps.

I would read through section 6 in the quick start guide, we have to see the registers in order to know if the conditions have been met.

https://www.ti.com/lit/ml/sluuah7b/sluuah7b.pdf?ts=1594765297870&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FBQ27421-G1

Sincerely,

Wyatt Keller

0 l.wittland over 5 years ago in reply to Wyatt Keller

Intellectual 425 points

Hello Wyatt,

please try this files.

Sincerely,

Lasse

charge2.log charge2.log.err.txt 3005.discharge2.log discharge2.log.err.txt

0 Wyatt Keller over 5 years ago in reply to l.wittland

TI__Guru** 105590 points

Hello Lasse,

Sorry for the late reply.

These files have more data but it is still missing lots of values, can you try logging with the auto refresh off in bqstudio? It is the green button in the top left, sometimes the refresh happens at the same time as the log and the data gets distorted.

I can see from the log that an OCV was taken but your SOC is still jumping. Can you confirm you have written the correct design capacity into the gauge?

Was the output of the log file in the "debug1,2,3..." format already in the header?

Sincerely,

Wyatt Keller

0 l.wittland over 5 years ago in reply to Wyatt Keller

Intellectual 425 points

Hello Wyatt,

I've turned the auto refresh off, but that didn't help. the logs are still missing a lot of data.

> I can see from the log that an OCV was taken but your SOC is still jumping. Can you confirm you have written the correct design capacity into the gauge?

The studio shows the correct design parameters for my battery (see image)

> Was the output of the log file in the "debug1,2,3..." format already in the header?

I'm not sure what you mean. The files I send you last time are what the battery management studio wrote when I selected 'start log' in the registers tab. I didn't modify them in any way.

Sincerely,

Lasse

0 l.wittland over 5 years ago in reply to l.wittland

Intellectual 425 points

Hi again,

here is the mentioned picture

0 Wyatt Keller over 5 years ago in reply to l.wittland

TI__Guru** 105590 points

Hello Lasse,

Cold you export your .gg file with all the configurations? Are there any communication issues occurring with the boards?

This is operating very close to the smallest capacity of the gauge which may be why it is harder to get the gauging accuracy working well because of the lower resolution on current.

Sincerely,

Wyatt Keller

0 l.wittland over 5 years ago in reply to Wyatt Keller

Intellectual 425 points

Hello Wyatt,

here it is.

7607.config.gg.csv

Sincerely,

Lasse

0 Wyatt Keller over 5 years ago in reply to l.wittland

TI__Guru** 105590 points

Hello Lasse,

I've been going through your logs and .gg file, could you make sure the BAT_DET is set to 1 when performing the cycles? Gauge predictions won't be valid unless it is set, it will also allow the gauge to do fast Qmax updates.

You can set it with the BAT_INSERT command. Let me know if this helps with the SOC and getting a Qmax update.

Sincerely,

Wyatt Keller

0 l.wittland over 5 years ago in reply to Wyatt Keller

Intellectual 425 points

Hello Wyatt,

I've also noticed the missing BAT_DET. Unfortunately, it didn't solve my problem.

I've tried a decharge/charge cycle with the BIE flag cleared and the BAT_INSERT as well as with J3 switched so that the BIN port goes low (and BIE set). Before each try I disconnected the battery from the EMV to reset it's memory and wrote design capacity etc. again. In neither case Qmax changed or the QMAX_UP flag was set.

I've forgotten to log most of the time; all I have is one from the discharge (again with frequent errors (auto refresh was off)).

discharge3.log

Fullscreen discharge3.log.err.txt Download

Wed Jul 22 13:47:25 CEST 2020

Time,LogCaption,Error Code,Error String
2020-07-22 13:47:25,Voltage,772,No acknowledge from device.2020-07-22 13:48:57,FullChgCap Flt,772,No acknowledge from device.2020-07-22 13:49:13,RemCap,772,No acknowledge from device.2020-07-22 13:49:29,CtrlStatus,772,No acknowledge from device.2020-07-22 13:49:49,SOH,772,No acknowledge from device.2020-07-22 13:50:45,True StateOfChg,772,No acknowledge from device.2020-07-22 13:52:33,Int Temp,772,No acknowledge from device.2020-07-22 13:52:33,SOHStat,772,No acknowledge from device.2020-07-22 13:52:41,StbyCurrent,772,No acknowledge from device.2020-07-22 13:53:13,AvgCurrent,772,No acknowledge from device.2020-07-22 13:53:37,AvgPower,772,No acknowledge from device.2020-07-22 13:54:01,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 13:54:29,StbyCurrent,772,No acknowledge from device.2020-07-22 13:56:10,Debug6,772,No acknowledge from device.2020-07-22 13:57:41,RemCap UnFlt,772,No acknowledge from device.2020-07-22 13:58:17,Control,772,No acknowledge from device.2020-07-22 13:58:17,CtrlStatus,772,No acknowledge from device.2020-07-22 13:58:57,StateOfChg,772,No acknowledge from device.2020-07-22 14:01:02,Debug5,772,No acknowledge from device.2020-07-22 14:01:25,NomAvailCap,772,No acknowledge from device.2020-07-22 14:02:05,StbyCurrent,772,No acknowledge from device.2020-07-22 14:05:45,MaxLoadCurr,772,No acknowledge from device.2020-07-22 14:06:29,FullAvailCap,772,No acknowledge from device.2020-07-22 14:06:29,RemCap,772,No acknowledge from device.2020-07-22 14:06:34,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 14:08:29,NomAvailCap,772,No acknowledge from device.2020-07-22 14:08:29,FullAvailCap,772,No acknowledge from device.2020-07-22 14:10:06,FullChgCap Flt,772,No acknowledge from device.2020-07-22 14:10:18,AvgPower,772,No acknowledge from device.2020-07-22 14:10:30,RemCap Flt,772,No acknowledge from device.2020-07-22 14:11:38,SOHStat,772,No acknowledge from device.2020-07-22 14:13:01,AvgCurrent,772,No acknowledge from device.2020-07-22 14:13:02,StbyCurrent,772,No acknowledge from device.2020-07-22 14:13:10,True StateOfChg,772,No acknowledge from device.2020-07-22 14:13:10,Debug3,772,No acknowledge from device.2020-07-22 14:13:17,AvgCurrent,772,No acknowledge from device.2020-07-22 14:13:18,StbyCurrent,772,No acknowledge from device.2020-07-22 14:13:54,MaxLoadCurr,772,No acknowledge from device.2020-07-22 14:14:46,MaxLoadCurr,772,No acknowledge from device.2020-07-22 14:14:57,RemCap,772,No acknowledge from device.2020-07-22 14:15:38,SOH,772,No acknowledge from device.2020-07-22 14:15:42,Debug2,772,No acknowledge from device.2020-07-22 14:15:57,CtrlStatus,772,No acknowledge from device.2020-07-22 14:16:02,Debug3,772,No acknowledge from device.2020-07-22 14:18:01,CtrlStatus,772,No acknowledge from device.2020-07-22 14:19:18,SOHStat,772,No acknowledge from device.2020-07-22 14:19:18,Debug4,772,No acknowledge from device.2020-07-22 14:20:38,MaxLoadCurr,772,No acknowledge from device.2020-07-22 14:20:38,Debug1,772,No acknowledge from device.2020-07-22 14:20:38,AvgPower,772,No acknowledge from device.2020-07-22 14:21:30,Debug7,772,No acknowledge from device.2020-07-22 14:22:18,Debug5,772,No acknowledge from device.2020-07-22 14:22:46,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 14:23:18,Debug6,772,No acknowledge from device.2020-07-22 14:23:33,Flags,772,No acknowledge from device.2020-07-22 14:25:02,RemCap UnFlt,772,No acknowledge from device.2020-07-22 14:25:02,RemCap Flt,772,No acknowledge from device.2020-07-22 14:26:01,CtrlStatus,772,No acknowledge from device.2020-07-22 14:26:38,StateOfChg,772,No acknowledge from device.2020-07-22 14:26:38,Int Temp,772,No acknowledge from device.2020-07-22 14:26:42,Debug6,772,No acknowledge from device.2020-07-22 14:26:42,Debug7,772,No acknowledge from device.2020-07-22 14:27:06,FullAvailCap,772,No acknowledge from device.2020-07-22 14:27:10,StateOfChg,772,No acknowledge from device.2020-07-22 14:28:10,SOH,772,No acknowledge from device.2020-07-22 14:28:58,FullChgCap,772,No acknowledge from device.2020-07-22 14:29:06,RemCap UnFlt,772,No acknowledge from device.2020-07-22 14:29:06,RemCap Flt,772,No acknowledge from device.2020-07-22 14:29:06,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 14:29:14,SOHStat,772,No acknowledge from device.2020-07-22 14:29:46,StbyCurrent,772,No acknowledge from device.2020-07-22 14:29:58,AvgPower,772,No acknowledge from device.2020-07-22 14:30:02,Flags,772,No acknowledge from device.2020-07-22 14:31:26,RemCap UnFlt,772,No acknowledge from device.2020-07-22 14:31:38,True StateOfChg,772,No acknowledge from device.2020-07-22 14:32:22,RemCap,772,No acknowledge from device.2020-07-22 14:35:38,Temperature,772,No acknowledge from device.2020-07-22 14:36:14,Temperature,772,No acknowledge from device.2020-07-22 14:36:18,AvgCurrent,772,No acknowledge from device.2020-07-22 14:36:18,StbyCurrent,772,No acknowledge from device.2020-07-22 14:36:50,Debug7,772,No acknowledge from device.2020-07-22 14:37:22,Int Temp,772,No acknowledge from device.2020-07-22 14:37:22,SOHStat,772,No acknowledge from device.2020-07-22 14:37:41,CtrlStatus,772,No acknowledge from device.2020-07-22 14:37:54,Debug4,772,No acknowledge from device.2020-07-22 14:37:58,Debug6,772,No acknowledge from device.2020-07-22 14:38:22,Voltage,772,No acknowledge from device.2020-07-22 14:38:38,SOHStat,772,No acknowledge from device.2020-07-22 14:38:54,StbyCurrent,772,No acknowledge from device.2020-07-22 14:38:54,MaxLoadCurr,772,No acknowledge from device.2020-07-22 14:39:34,Flags,772,No acknowledge from device.2020-07-22 14:39:38,NomAvailCap,772,No acknowledge from device.2020-07-22 14:39:46,FullChgCap Flt,772,No acknowledge from device.2020-07-22 14:39:46,True StateOfChg,772,No acknowledge from device.2020-07-22 14:40:10,Temperature,772,No acknowledge from device.2020-07-22 14:40:10,Voltage,772,No acknowledge from device.2020-07-22 14:40:25,CtrlStatus,772,No acknowledge from device.2020-07-22 14:40:38,Temperature,772,No acknowledge from device.2020-07-22 14:41:38,True StateOfChg,772,No acknowledge from device.2020-07-22 14:41:38,Debug3,772,No acknowledge from device.2020-07-22 14:41:38,Debug4,772,No acknowledge from device.2020-07-22 14:41:46,SOHStat,772,No acknowledge from device.2020-07-22 14:41:53,Control,772,No acknowledge from device.2020-07-22 14:42:13,CtrlStatus,772,No acknowledge from device.2020-07-22 14:43:02,AvgPower,772,No acknowledge from device.2020-07-22 14:43:02,Debug6,772,No acknowledge from device.2020-07-22 14:43:02,Debug7,772,No acknowledge from device.2020-07-22 14:43:38,MaxLoadCurr,772,No acknowledge from device.2020-07-22 14:44:22,SOH,772,No acknowledge from device.2020-07-22 14:44:26,AvgCurrent,772,No acknowledge from device.2020-07-22 14:44:26,StbyCurrent,772,No acknowledge from device.2020-07-22 14:44:26,MaxLoadCurr,772,No acknowledge from device.2020-07-22 14:45:10,FullChgCap Flt,772,No acknowledge from device.2020-07-22 14:45:10,True StateOfChg,772,No acknowledge from device.2020-07-22 14:45:10,Debug3,772,No acknowledge from device.2020-07-22 14:45:10,Debug4,772,No acknowledge from device.2020-07-22 14:45:26,SOH,772,No acknowledge from device.2020-07-22 14:48:26,Int Temp,772,No acknowledge from device.2020-07-22 14:48:46,Int Temp,772,No acknowledge from device.2020-07-22 14:48:46,SOHStat,772,No acknowledge from device.2020-07-22 14:49:38,AvgPower,772,No acknowledge from device.2020-07-22 14:49:38,Debug2,772,No acknowledge from device.2020-07-22 14:50:02,Voltage,772,No acknowledge from device.2020-07-22 14:50:18,CtrlStatus,772,No acknowledge from device.2020-07-22 14:50:22,Debug5,772,No acknowledge from device.2020-07-22 14:50:34,Temperature,772,No acknowledge from device.2020-07-22 14:50:42,Int Temp,772,No acknowledge from device.2020-07-22 14:50:42,SOHStat,772,No acknowledge from device.2020-07-22 14:50:42,SOH,772,No acknowledge from device.2020-07-22 14:50:42,Debug4,772,No acknowledge from device.2020-07-22 14:51:50,StateOfChg,772,No acknowledge from device.2020-07-22 14:51:54,True StateOfChg,772,No acknowledge from device.2020-07-22 14:52:01,Control,772,No acknowledge from device.2020-07-22 14:52:02,SOHStat,772,No acknowledge from device.2020-07-22 14:52:02,Debug6,772,No acknowledge from device.2020-07-22 14:52:30,FullChgCap Flt,772,No acknowledge from device.2020-07-22 14:52:30,True StateOfChg,772,No acknowledge from device.2020-07-22 14:52:30,Debug3,772,No acknowledge from device.2020-07-22 14:52:58,Debug7,772,No acknowledge from device.2020-07-22 14:53:26,StbyCurrent,772,No acknowledge from device.2020-07-22 14:53:50,AvgPower,772,No acknowledge from device.2020-07-22 14:54:02,Debug7,772,No acknowledge from device.2020-07-22 14:54:34,FullChgCap Flt,772,No acknowledge from device.2020-07-22 14:55:18,CtrlStatus,772,No acknowledge from device.2020-07-22 14:56:30,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 14:56:46,Flags,772,No acknowledge from device.2020-07-22 14:56:46,NomAvailCap,772,No acknowledge from device.2020-07-22 14:56:46,FullAvailCap,772,No acknowledge from device.2020-07-22 14:57:10,StbyCurrent,772,No acknowledge from device.2020-07-22 14:57:54,SOH,772,No acknowledge from device.2020-07-22 14:58:10,SOH,772,No acknowledge from device.2020-07-22 14:58:42,RemCap,772,No acknowledge from device.2020-07-22 14:58:42,FullChgCap,772,No acknowledge from device.2020-07-22 14:58:42,AvgCurrent,772,No acknowledge from device.2020-07-22 15:00:18,CtrlStatus,772,No acknowledge from device.2020-07-22 15:00:26,Temperature,772,No acknowledge from device.2020-07-22 15:00:38,True StateOfChg,772,No acknowledge from device.2020-07-22 15:00:38,Debug3,772,No acknowledge from device.2020-07-22 15:00:38,Debug4,772,No acknowledge from device.2020-07-22 15:00:38,Debug5,772,No acknowledge from device.2020-07-22 15:00:58,FullChgCap,772,No acknowledge from device.2020-07-22 15:01:09,Control,772,No acknowledge from device.2020-07-22 15:01:10,RemCap UnFlt,772,No acknowledge from device.2020-07-22 15:01:10,RemCap Flt,772,No acknowledge from device.2020-07-22 15:01:22,CtrlStatus,772,No acknowledge from device.2020-07-22 15:01:54,True StateOfChg,772,No acknowledge from device.2020-07-22 15:01:54,Debug3,772,No acknowledge from device.2020-07-22 15:02:22,Debug6,772,No acknowledge from device.2020-07-22 15:02:22,Debug7,772,No acknowledge from device.2020-07-22 15:02:38,FullChgCap,772,No acknowledge from device.2020-07-22 15:03:17,Control,772,No acknowledge from device.2020-07-22 15:03:30,Debug4,772,No acknowledge from device.2020-07-22 15:03:54,FullChgCap Flt,772,No acknowledge from device.2020-07-22 15:03:54,True StateOfChg,772,No acknowledge from device.2020-07-22 15:04:02,AvgCurrent,772,No acknowledge from device.2020-07-22 15:04:10,RemCap,772,No acknowledge from device.2020-07-22 15:04:10,FullChgCap,772,No acknowledge from device.2020-07-22 15:04:18,StbyCurrent,772,No acknowledge from device.2020-07-22 15:04:34,Int Temp,772,No acknowledge from device.2020-07-22 15:06:14,Debug7,772,No acknowledge from device.2020-07-22 15:06:42,FullAvailCap,772,No acknowledge from device.2020-07-22 15:06:42,RemCap,772,No acknowledge from device.2020-07-22 15:07:16,Debug7,772,No acknowledge from device.2020-07-22 15:07:58,FullChgCap,772,No acknowledge from device.2020-07-22 15:07:58,AvgCurrent,772,No acknowledge from device.2020-07-22 15:08:50,CtrlStatus,772,No acknowledge from device.2020-07-22 15:09:46,Temperature,772,No acknowledge from device.2020-07-22 15:09:54,RemCap UnFlt,772,No acknowledge from device.2020-07-22 15:10:10,Debug1,772,No acknowledge from device.2020-07-22 15:10:22,True StateOfChg,772,No acknowledge from device.2020-07-22 15:11:06,NomAvailCap,772,No acknowledge from device.2020-07-22 15:11:26,FullChgCap,772,No acknowledge from device.2020-07-22 15:11:26,AvgCurrent,772,No acknowledge from device.2020-07-22 15:13:26,Debug4,772,No acknowledge from device.2020-07-22 15:13:54,SOHStat,772,No acknowledge from device.2020-07-22 15:14:02,CtrlStatus,772,No acknowledge from device.2020-07-22 15:14:02,Temperature,772,No acknowledge from device.2020-07-22 15:14:34,RemCap,772,No acknowledge from device.2020-07-22 15:14:34,AvgPower,772,No acknowledge from device.2020-07-22 15:14:34,Debug2,772,No acknowledge from device.2020-07-22 15:14:34,StateOfChg,772,No acknowledge from device.2020-07-22 15:14:34,Int Temp,772,No acknowledge from device.2020-07-22 15:15:47,Debug7,772,No acknowledge from device.2020-07-22 15:15:50,Control,772,No acknowledge from device.2020-07-22 15:16:22,Debug4,772,No acknowledge from device.2020-07-22 15:16:26,RemCap Flt,772,No acknowledge from device.2020-07-22 15:17:10,Debug2,772,No acknowledge from device.2020-07-22 15:17:22,Debug4,772,No acknowledge from device.2020-07-22 15:18:02,StbyCurrent,772,No acknowledge from device.2020-07-22 15:18:14,Debug3,772,No acknowledge from device.2020-07-22 15:18:38,StbyCurrent,772,No acknowledge from device.2020-07-22 15:19:46,Debug7,772,No acknowledge from device.2020-07-22 15:20:02,FullAvailCap,772,No acknowledge from device.2020-07-22 15:20:02,RemCap,772,No acknowledge from device.2020-07-22 15:20:02,FullChgCap,772,No acknowledge from device.2020-07-22 15:20:02,AvgCurrent,772,No acknowledge from device.2020-07-22 15:20:30,CtrlStatus,772,No acknowledge from device.2020-07-22 15:20:58,Debug3,772,No acknowledge from device.2020-07-22 15:21:26,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 15:22:34,CtrlStatus,772,No acknowledge from device.2020-07-22 15:22:34,Temperature,772,No acknowledge from device.2020-07-22 15:22:46,SOH,772,No acknowledge from device.2020-07-22 15:23:10,NomAvailCap,772,No acknowledge from device.2020-07-22 15:23:10,Debug4,772,No acknowledge from device.2020-07-22 15:23:26,Temperature,772,No acknowledge from device.2020-07-22 15:23:30,Control,772,No acknowledge from device.2020-07-22 15:23:46,CtrlStatus,772,No acknowledge from device.2020-07-22 15:23:46,Temperature,772,No acknowledge from device.2020-07-22 15:23:46,Voltage,772,No acknowledge from device.2020-07-22 15:23:46,Flags,772,No acknowledge from device.2020-07-22 15:24:58,FullChgCap,772,No acknowledge from device.2020-07-22 15:24:58,AvgCurrent,772,No acknowledge from device.2020-07-22 15:25:14,Control,772,No acknowledge from device.2020-07-22 15:25:18,MaxLoadCurr,772,No acknowledge from device.2020-07-22 15:25:22,StateOfChg,772,No acknowledge from device.2020-07-22 15:25:51,Debug6,772,No acknowledge from device.2020-07-22 15:25:51,Debug7,772,No acknowledge from device.2020-07-22 15:26:14,MaxLoadCurr,772,No acknowledge from device.2020-07-22 15:26:14,Debug1,772,No acknowledge from device.2020-07-22 15:26:58,Control,772,No acknowledge from device.2020-07-22 15:27:30,Int Temp,772,No acknowledge from device.2020-07-22 15:27:31,Debug5,772,No acknowledge from device.2020-07-22 15:28:06,NomAvailCap,772,No acknowledge from device.2020-07-22 15:28:06,FullAvailCap,772,No acknowledge from device.2020-07-22 15:28:06,RemCap,772,No acknowledge from device.2020-07-22 15:28:06,FullChgCap,772,No acknowledge from device.2020-07-22 15:28:06,AvgCurrent,772,No acknowledge from device.2020-07-22 15:28:06,StbyCurrent,772,No acknowledge from device.2020-07-22 15:28:06,MaxLoadCurr,772,No acknowledge from device.2020-07-22 15:28:06,Debug1,772,No acknowledge from device.2020-07-22 15:28:06,AvgPower,772,No acknowledge from device.2020-07-22 15:28:06,Debug2,772,No acknowledge from device.2020-07-22 15:28:06,StateOfChg,772,No acknowledge from device.2020-07-22 15:28:06,Int Temp,772,No acknowledge from device.2020-07-22 15:28:14,FullChgCap,772,No acknowledge from device.2020-07-22 15:28:14,AvgCurrent,772,No acknowledge from device.2020-07-22 15:28:14,StbyCurrent,772,No acknowledge from device.2020-07-22 15:28:14,MaxLoadCurr,772,No acknowledge from device.2020-07-22 15:28:14,Debug1,772,No acknowledge from device.2020-07-22 15:28:14,AvgPower,772,No acknowledge from device.2020-07-22 15:28:14,Debug2,772,No acknowledge from device.2020-07-22 15:28:14,StateOfChg,772,No acknowledge from device.2020-07-22 15:28:14,Int Temp,772,No acknowledge from device.2020-07-22 15:28:15,SOHStat,772,No acknowledge from device.2020-07-22 15:28:15,SOH,772,No acknowledge from device.2020-07-22 15:28:46,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 15:30:34,StateOfChg,772,No acknowledge from device.2020-07-22 15:30:34,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 15:31:06,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 15:31:06,FullChgCap Flt,772,No acknowledge from device.2020-07-22 15:31:06,True StateOfChg,772,No acknowledge from device.2020-07-22 15:31:07,Debug3,772,No acknowledge from device.2020-07-22 15:31:50,StateOfChg,772,No acknowledge from device.2020-07-22 15:32:10,SOH,772,No acknowledge from device.2020-07-22 15:32:50,Flags,772,No acknowledge from device.2020-07-22 15:32:50,NomAvailCap,772,No acknowledge from device.2020-07-22 15:32:50,FullAvailCap,772,No acknowledge from device.2020-07-22 15:32:50,RemCap,772,No acknowledge from device.2020-07-22 15:34:27,Debug3,772,No acknowledge from device.2020-07-22 15:34:27,Debug4,772,No acknowledge from device.2020-07-22 15:34:58,RemCap,772,No acknowledge from device.2020-07-22 15:38:51,Debug7,772,No acknowledge from device.2020-07-22 15:39:06,CtrlStatus,772,No acknowledge from device.2020-07-22 15:40:11,Debug5,772,No acknowledge from device.2020-07-22 15:40:15,RemCap UnFlt,772,No acknowledge from device.2020-07-22 15:40:42,CtrlStatus,772,No acknowledge from device.2020-07-22 15:40:47,SOHStat,772,No acknowledge from device.2020-07-22 15:41:34,CtrlStatus,772,No acknowledge from device.2020-07-22 15:41:54,Debug2,772,No acknowledge from device.2020-07-22 15:41:58,Voltage,772,No acknowledge from device.2020-07-22 15:42:35,RemCap UnFlt,772,No acknowledge from device.2020-07-22 15:42:59,FullChgCap Flt,772,No acknowledge from device.2020-07-22 15:43:02,AvgPower,772,No acknowledge from device.2020-07-22 15:43:23,True StateOfChg,772,No acknowledge from device.2020-07-22 15:43:35,StateOfChg,772,No acknowledge from device.2020-07-22 15:43:35,Debug5,772,No acknowledge from device.2020-07-22 15:43:38,FullAvailCap,772,No acknowledge from device.2020-07-22 15:44:14,CtrlStatus,772,No acknowledge from device.2020-07-22 15:44:35,Debug6,772,No acknowledge from device.2020-07-22 15:44:44,CtrlStatus,772,No acknowledge from device.2020-07-22 15:47:22,FullAvailCap,772,No acknowledge from device.2020-07-22 15:47:39,AvgPower,772,No acknowledge from device.2020-07-22 15:48:23,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 15:48:47,Debug1,772,No acknowledge from device.2020-07-22 15:48:59,AvgPower,772,No acknowledge from device.2020-07-22 15:49:10,MaxLoadCurr,772,No acknowledge from device.2020-07-22 15:50:22,Temperature,772,No acknowledge from device.2020-07-22 15:50:26,CtrlStatus,772,No acknowledge from device.2020-07-22 15:50:26,Temperature,772,No acknowledge from device.2020-07-22 15:50:35,Debug6,772,No acknowledge from device.2020-07-22 15:50:35,Debug7,772,No acknowledge from device.2020-07-22 15:50:43,AvgPower,772,No acknowledge from device.2020-07-22 15:50:58,Flags,772,No acknowledge from device.2020-07-22 15:51:10,Flags,772,No acknowledge from device.2020-07-22 15:51:50,CtrlStatus,772,No acknowledge from device.2020-07-22 15:52:03,Debug5,772,No acknowledge from device.2020-07-22 15:52:31,Int Temp,772,No acknowledge from device.2020-07-22 15:53:15,FullChgCap,772,No acknowledge from device.2020-07-22 15:53:15,AvgCurrent,772,No acknowledge from device.2020-07-22 15:53:15,StbyCurrent,772,No acknowledge from device.2020-07-22 15:53:15,MaxLoadCurr,772,No acknowledge from device.2020-07-22 15:53:15,Debug1,772,No acknowledge from device.2020-07-22 15:53:15,AvgPower,772,No acknowledge from device.2020-07-22 15:53:15,Debug2,772,No acknowledge from device.2020-07-22 15:53:15,StateOfChg,772,No acknowledge from device.2020-07-22 15:53:15,Int Temp,772,No acknowledge from device.2020-07-22 15:53:15,SOHStat,772,No acknowledge from device.2020-07-22 15:53:15,SOH,772,No acknowledge from device.2020-07-22 15:54:10,Temperature,772,No acknowledge from device.2020-07-22 15:54:55,Debug5,772,No acknowledge from device.2020-07-22 15:57:10,Voltage,772,No acknowledge from device.2020-07-22 15:57:50,Voltage,772,No acknowledge from device.2020-07-22 16:00:47,Debug7,772,No acknowledge from device.2020-07-22 16:00:55,FullAvailCap,772,No acknowledge from device.2020-07-22 16:00:55,RemCap,772,No acknowledge from device.2020-07-22 16:02:06,CtrlStatus,772,No acknowledge from device.2020-07-22 16:02:07,Debug5,772,No acknowledge from device.2020-07-22 16:02:11,FullChgCap,772,No acknowledge from device.2020-07-22 16:02:31,FullAvailCap,772,No acknowledge from device.2020-07-22 16:02:31,RemCap,772,No acknowledge from device.2020-07-22 16:02:31,FullChgCap,772,No acknowledge from device.2020-07-22 16:02:31,AvgCurrent,772,No acknowledge from device.2020-07-22 16:02:43,Voltage,772,No acknowledge from device.2020-07-22 16:02:43,Flags,772,No acknowledge from device.2020-07-22 16:03:51,NomAvailCap,772,No acknowledge from device.2020-07-22 16:04:07,SOH,772,No acknowledge from device.2020-07-22 16:10:43,SOHStat,772,No acknowledge from device.2020-07-22 16:11:18,CtrlStatus,772,No acknowledge from device.2020-07-22 16:11:55,Voltage,772,No acknowledge from device.2020-07-22 16:12:47,Debug3,772,No acknowledge from device.2020-07-22 16:13:59,AvgCurrent,772,No acknowledge from device.2020-07-22 16:13:59,StbyCurrent,772,No acknowledge from device.2020-07-22 16:16:55,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 16:20:19,Int Temp,772,No acknowledge from device.2020-07-22 16:20:55,Debug2,772,No acknowledge from device.2020-07-22 16:22:26,Control,772,No acknowledge from device.2020-07-22 16:22:26,CtrlStatus,772,No acknowledge from device.2020-07-22 16:22:35,NomAvailCap,772,No acknowledge from device.2020-07-22 16:22:55,Flags,772,No acknowledge from device.2020-07-22 16:22:55,NomAvailCap,772,No acknowledge from device.2020-07-22 16:22:55,FullAvailCap,772,No acknowledge from device.2020-07-22 16:23:31,Int Temp,772,No acknowledge from device.2020-07-22 16:23:31,SOHStat,772,No acknowledge from device.2020-07-22 16:24:19,Int Temp,772,No acknowledge from device.2020-07-22 16:24:51,Int Temp,772,No acknowledge from device.2020-07-22 16:24:51,SOHStat,772,No acknowledge from device.2020-07-22 16:25:23,Debug7,772,No acknowledge from device.2020-07-22 16:25:51,Debug2,772,No acknowledge from device.2020-07-22 16:25:51,StateOfChg,772,No acknowledge from device.2020-07-22 16:25:51,Int Temp,772,No acknowledge from device.2020-07-22 16:25:51,SOHStat,772,No acknowledge from device.2020-07-22 16:26:27,True StateOfChg,772,No acknowledge from device.2020-07-22 16:26:55,CtrlStatus,772,No acknowledge from device.2020-07-22 16:26:55,Temperature,772,No acknowledge from device.2020-07-22 16:27:15,Debug3,772,No acknowledge from device.2020-07-22 16:28:39,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 16:28:39,FullChgCap Flt,772,No acknowledge from device.2020-07-22 16:28:39,True StateOfChg,772,No acknowledge from device.2020-07-22 16:28:43,CtrlStatus,772,No acknowledge from device.2020-07-22 16:28:51,RemCap UnFlt,772,No acknowledge from device.2020-07-22 16:29:51,Debug4,772,No acknowledge from device.2020-07-22 16:29:51,Debug5,772,No acknowledge from device.2020-07-22 16:29:51,Debug6,772,No acknowledge from device.2020-07-22 16:30:15,RemCap,772,No acknowledge from device.2020-07-22 16:31:03,Int Temp,772,No acknowledge from device.2020-07-22 16:31:03,SOHStat,772,No acknowledge from device.2020-07-22 16:31:27,Int Temp,772,No acknowledge from device.2020-07-22 16:31:31,FullAvailCap,772,No acknowledge from device.2020-07-22 16:31:50,Control,772,No acknowledge from device.2020-07-22 16:31:51,CtrlStatus,772,No acknowledge from device.2020-07-22 16:31:59,Debug5,772,No acknowledge from device.2020-07-22 16:32:15,Flags,772,No acknowledge from device.2020-07-22 16:32:31,RemCap,772,No acknowledge from device.2020-07-22 16:32:31,FullChgCap,772,No acknowledge from device.2020-07-22 16:32:31,AvgCurrent,772,No acknowledge from device.2020-07-22 16:32:31,StbyCurrent,772,No acknowledge from device.2020-07-22 16:32:31,MaxLoadCurr,772,No acknowledge from device.2020-07-22 16:32:31,Debug1,772,No acknowledge from device.2020-07-22 16:32:31,AvgPower,772,No acknowledge from device.2020-07-22 16:32:31,Debug2,772,No acknowledge from device.2020-07-22 16:32:31,Int Temp,772,No acknowledge from device.2020-07-22 16:32:31,SOHStat,772,No acknowledge from device.2020-07-22 16:32:35,AvgCurrent,772,No acknowledge from device.2020-07-22 16:32:35,StbyCurrent,772,No acknowledge from device.2020-07-22 16:32:35,MaxLoadCurr,772,No acknowledge from device.2020-07-22 16:32:43,Debug6,772,No acknowledge from device.2020-07-22 16:32:43,Debug7,772,No acknowledge from device.2020-07-22 16:33:07,StbyCurrent,772,No acknowledge from device.2020-07-22 16:33:07,MaxLoadCurr,772,No acknowledge from device.2020-07-22 16:33:07,Debug1,772,No acknowledge from device.2020-07-22 16:33:15,FullChgCap Flt,772,No acknowledge from device.2020-07-22 16:33:15,True StateOfChg,772,No acknowledge from device.2020-07-22 16:33:59,RemCap UnFlt,772,No acknowledge from device.2020-07-22 16:34:03,Voltage,772,No acknowledge from device.2020-07-22 16:34:03,Flags,772,No acknowledge from device.2020-07-22 16:34:03,NomAvailCap,772,No acknowledge from device.2020-07-22 16:34:03,FullAvailCap,772,No acknowledge from device.2020-07-22 16:34:03,RemCap,772,No acknowledge from device.2020-07-22 16:34:03,FullChgCap,772,No acknowledge from device.2020-07-22 16:34:03,AvgCurrent,772,No acknowledge from device.2020-07-22 16:34:03,StbyCurrent,772,No acknowledge from device.2020-07-22 16:34:03,MaxLoadCurr,772,No acknowledge from device.2020-07-22 16:34:03,Debug1,772,No acknowledge from device.2020-07-22 16:34:03,AvgPower,772,No acknowledge from device.2020-07-22 16:34:03,Debug2,772,No acknowledge from device.2020-07-22 16:34:03,StateOfChg,772,No acknowledge from device.2020-07-22 16:34:03,Int Temp,772,No acknowledge from device.2020-07-22 16:34:03,SOHStat,772,No acknowledge from device.2020-07-22 16:34:19,SOH,772,No acknowledge from device.2020-07-22 16:34:23,Debug2,772,No acknowledge from device.2020-07-22 16:34:59,StateOfChg,772,No acknowledge from device.2020-07-22 16:35:55,Debug7,772,No acknowledge from device.2020-07-22 16:35:59,FullChgCap Flt,772,No acknowledge from device.2020-07-22 16:36:03,CtrlStatus,772,No acknowledge from device.2020-07-22 16:36:03,Temperature,772,No acknowledge from device.2020-07-22 16:36:03,Voltage,772,No acknowledge from device.2020-07-22 16:36:03,Flags,772,No acknowledge from device.2020-07-22 16:36:03,NomAvailCap,772,No acknowledge from device.2020-07-22 16:36:03,FullAvailCap,772,No acknowledge from device.2020-07-22 16:36:03,SOH,772,No acknowledge from device.2020-07-22 16:36:19,Debug3,772,No acknowledge from device.2020-07-22 16:38:19,CtrlStatus,772,No acknowledge from device.2020-07-22 16:38:19,Temperature,772,No acknowledge from device.2020-07-22 16:38:19,Voltage,772,No acknowledge from device.2020-07-22 16:38:19,Flags,772,No acknowledge from device.2020-07-22 16:39:19,NomAvailCap,772,No acknowledge from device.2020-07-22 16:39:19,FullAvailCap,772,No acknowledge from device.2020-07-22 16:39:19,RemCap,772,No acknowledge from device.2020-07-22 16:39:47,Int Temp,772,No acknowledge from device.2020-07-22 16:40:03,NomAvailCap,772,No acknowledge from device.2020-07-22 16:40:19,Temperature,772,No acknowledge from device.2020-07-22 16:40:19,Voltage,772,No acknowledge from device.2020-07-22 16:41:11,Debug4,772,No acknowledge from device.2020-07-22 16:41:15,Debug5,772,No acknowledge from device.2020-07-22 16:41:15,Debug6,772,No acknowledge from device.2020-07-22 16:41:15,Debug7,772,No acknowledge from device.2020-07-22 16:43:07,MaxLoadCurr,772,No acknowledge from device.2020-07-22 16:43:07,Debug1,772,No acknowledge from device.2020-07-22 16:43:19,Flags,772,No acknowledge from device.2020-07-22 16:45:03,FullChgCap,772,No acknowledge from device.2020-07-22 16:45:31,Voltage,772,No acknowledge from device.2020-07-22 16:45:31,Flags,772,No acknowledge from device.2020-07-22 16:45:31,NomAvailCap,772,No acknowledge from device.2020-07-22 16:45:31,FullAvailCap,772,No acknowledge from device.2020-07-22 16:45:47,RemCap UnFlt,772,No acknowledge from device.2020-07-22 16:45:51,RemCap UnFlt,772,No acknowledge from device.2020-07-22 16:46:23,Debug1,772,No acknowledge from device.2020-07-22 16:46:51,AvgCurrent,772,No acknowledge from device.2020-07-22 16:46:51,Debug6,772,No acknowledge from device.2020-07-22 16:47:03,NomAvailCap,772,No acknowledge from device.2020-07-22 16:47:55,Debug4,772,No acknowledge from device.2020-07-22 16:48:23,RemCap Flt,772,No acknowledge from device.2020-07-22 16:49:19,Int Temp,772,No acknowledge from device.2020-07-22 16:49:19,SOHStat,772,No acknowledge from device.2020-07-22 16:50:03,FullAvailCap,772,No acknowledge from device.2020-07-22 16:50:23,NomAvailCap,772,No acknowledge from device.2020-07-22 16:50:23,FullAvailCap,772,No acknowledge from device.2020-07-22 16:50:23,SOHStat,772,No acknowledge from device.2020-07-22 16:51:31,FullChgCap Flt,772,No acknowledge from device.2020-07-22 16:53:31,True StateOfChg,772,No acknowledge from device.2020-07-22 16:54:47,CtrlStatus,772,No acknowledge from device.2020-07-22 16:56:07,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 16:56:15,RemCap UnFlt,772,No acknowledge from device.2020-07-22 16:56:15,RemCap Flt,772,No acknowledge from device.2020-07-22 16:56:15,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 16:56:15,FullChgCap Flt,772,No acknowledge from device.2020-07-22 16:56:16,True StateOfChg,772,No acknowledge from device.2020-07-22 16:56:39,Temperature,772,No acknowledge from device.2020-07-22 17:01:19,RemCap,772,No acknowledge from device.2020-07-22 17:01:19,Debug1,772,No acknowledge from device.2020-07-22 17:03:28,Debug4,772,No acknowledge from device.2020-07-22 17:04:55,RemCap UnFlt,772,No acknowledge from device.2020-07-22 17:04:59,Debug1,772,No acknowledge from device.2020-07-22 17:04:59,AvgPower,772,No acknowledge from device.2020-07-22 17:05:19,RemCap UnFlt,772,No acknowledge from device.2020-07-22 17:06:59,Debug1,772,No acknowledge from device.2020-07-22 17:07:00,Debug7,772,No acknowledge from device.2020-07-22 17:08:04,Debug6,772,No acknowledge from device.2020-07-22 17:08:04,Debug7,772,No acknowledge from device.2020-07-22 17:10:07,CtrlStatus,772,No acknowledge from device.2020-07-22 17:10:07,Temperature,772,No acknowledge from device.2020-07-22 17:10:20,Debug7,772,No acknowledge from device.2020-07-22 17:11:31,Voltage,772,No acknowledge from device.2020-07-22 17:11:46,RemCap Flt,772,No acknowledge from device.2020-07-22 17:11:46,Debug4,772,No acknowledge from device.2020-07-22 17:12:11,Debug2,772,No acknowledge from device.2020-07-22 17:12:31,MaxLoadCurr,772,No acknowledge from device.2020-07-22 17:12:39,FullChgCap,772,No acknowledge from device.2020-07-22 17:12:39,AvgCurrent,772,No acknowledge from device.2020-07-22 17:12:39,StbyCurrent,772,No acknowledge from device.2020-07-22 17:12:40,AvgPower,772,No acknowledge from device.2020-07-22 17:12:44,Debug4,772,No acknowledge from device.2020-07-22 17:12:44,Debug5,772,No acknowledge from device.2020-07-22 17:12:44,Debug6,772,No acknowledge from device.2020-07-22 17:13:08,Debug3,772,No acknowledge from device.2020-07-22 17:13:08,Debug7,772,No acknowledge from device.2020-07-22 17:13:15,MaxLoadCurr,772,No acknowledge from device.2020-07-22 17:13:16,Int Temp,772,No acknowledge from device.2020-07-22 17:13:23,MaxLoadCurr,772,No acknowledge from device.2020-07-22 17:13:27,Control,772,No acknowledge from device.2020-07-22 17:13:28,AvgPower,772,No acknowledge from device.2020-07-22 17:13:31,RemCap,772,No acknowledge from device.2020-07-22 17:13:32,Debug5,772,No acknowledge from device.2020-07-22 17:13:32,Debug6,772,No acknowledge from device.2020-07-22 17:13:40,RemCap UnFlt,772,No acknowledge from device.2020-07-22 17:13:40,RemCap Flt,772,No acknowledge from device.2020-07-22 17:13:56,AvgPower,772,No acknowledge from device.2020-07-22 17:13:56,Debug2,772,No acknowledge from device.2020-07-22 17:13:56,StateOfChg,772,No acknowledge from device.2020-07-22 17:14:03,Voltage,772,No acknowledge from device.2020-07-22 17:14:04,Debug3,772,No acknowledge from device.2020-07-22 17:14:24,FullChgCap Flt,772,No acknowledge from device.2020-07-22 17:14:24,True StateOfChg,772,No acknowledge from device.2020-07-22 17:14:24,Debug3,772,No acknowledge from device.2020-07-22 17:14:24,Debug4,772,No acknowledge from device.2020-07-22 17:14:24,Debug5,772,No acknowledge from device.2020-07-22 17:14:28,RemCap UnFlt,772,No acknowledge from device.2020-07-22 17:14:32,StateOfChg,772,No acknowledge from device.2020-07-22 17:14:48,Int Temp,772,No acknowledge from device.2020-07-22 17:15:00,Debug5,772,No acknowledge from device.2020-07-22 17:15:00,Debug6,772,No acknowledge from device.2020-07-22 17:15:00,Debug7,772,No acknowledge from device.2020-07-22 17:15:03,CtrlStatus,772,No acknowledge from device.2020-07-22 17:15:03,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 17:15:08,Debug2,772,No acknowledge from device.2020-07-22 17:16:32,Debug5,772,No acknowledge from device.2020-07-22 17:16:40,Debug3,772,No acknowledge from device.2020-07-22 17:16:48,SOHStat,772,No acknowledge from device.2020-07-22 17:17:19,RemCap,772,No acknowledge from device.2020-07-22 17:17:40,Debug5,772,No acknowledge from device.2020-07-22 17:18:11,FullChgCap,772,No acknowledge from device.2020-07-22 17:18:11,AvgCurrent,772,No acknowledge from device.2020-07-22 17:18:12,StbyCurrent,772,No acknowledge from device.2020-07-22 17:18:12,MaxLoadCurr,772,No acknowledge from device.2020-07-22 17:18:15,Voltage,772,No acknowledge from device.2020-07-22 17:18:24,Debug4,772,No acknowledge from device.2020-07-22 17:18:44,RemCap Flt,772,No acknowledge from device.2020-07-22 17:18:44,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 17:18:44,FullChgCap Flt,772,No acknowledge from device.2020-07-22 17:18:44,True StateOfChg,772,No acknowledge from device.2020-07-22 17:18:44,Debug3,772,No acknowledge from device.2020-07-22 17:18:44,Debug4,772,No acknowledge from device.2020-07-22 17:18:44,Debug5,772,No acknowledge from device.2020-07-22 17:18:44,Debug6,772,No acknowledge from device.2020-07-22 17:18:44,Debug7,772,No acknowledge from device.2020-07-22 17:18:52,FullChgCap Flt,772,No acknowledge from device.2020-07-22 17:19:03,CtrlStatus,772,No acknowledge from device.2020-07-22 17:20:19,Voltage,772,No acknowledge from device.2020-07-22 17:21:28,True StateOfChg,772,No acknowledge from device.2020-07-22 17:21:28,Debug3,772,No acknowledge from device.2020-07-22 17:21:47,FullAvailCap,772,No acknowledge from device.2020-07-22 17:22:28,SOHStat,772,No acknowledge from device.2020-07-22 17:22:51,Voltage,772,No acknowledge from device.2020-07-22 17:22:55,CtrlStatus,772,No acknowledge from device.2020-07-22 17:23:19,Flags,772,No acknowledge from device.2020-07-22 17:23:24,MaxLoadCurr,772,No acknowledge from device.2020-07-22 17:23:24,Debug1,772,No acknowledge from device.2020-07-22 17:23:32,MaxLoadCurr,772,No acknowledge from device.2020-07-22 17:23:32,Debug1,772,No acknowledge from device.2020-07-22 17:23:51,Flags,772,No acknowledge from device.2020-07-22 17:24:24,StateOfChg,772,No acknowledge from device.2020-07-22 17:24:44,Int Temp,772,No acknowledge from device.2020-07-22 17:24:44,SOHStat,772,No acknowledge from device.2020-07-22 17:24:44,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 17:24:59,Control,772,No acknowledge from device.2020-07-22 17:25:08,RemCap,772,No acknowledge from device.2020-07-22 17:25:08,FullChgCap,772,No acknowledge from device.2020-07-22 17:25:08,AvgCurrent,772,No acknowledge from device.2020-07-22 17:25:08,Debug3,772,No acknowledge from device.2020-07-22 17:25:16,Debug2,772,No acknowledge from device.2020-07-22 17:25:43,Voltage,772,No acknowledge from device.2020-07-22 17:25:55,Temperature,772,No acknowledge from device.2020-07-22 17:25:55,Voltage,772,No acknowledge from device.2020-07-22 17:25:55,Flags,772,No acknowledge from device.2020-07-22 17:25:56,NomAvailCap,772,No acknowledge from device.2020-07-22 17:26:04,FullChgCap,772,No acknowledge from device.2020-07-22 17:26:16,AvgPower,772,No acknowledge from device.2020-07-22 17:26:16,Debug2,772,No acknowledge from device.2020-07-22 17:26:32,SOHStat,772,No acknowledge from device.2020-07-22 17:27:12,Int Temp,772,No acknowledge from device.2020-07-22 17:27:36,Debug3,772,No acknowledge from device.2020-07-22 17:27:44,True StateOfChg,772,No acknowledge from device.2020-07-22 17:28:00,Debug2,772,No acknowledge from device.2020-07-22 17:28:00,StateOfChg,772,No acknowledge from device.2020-07-22 17:28:00,Int Temp,772,No acknowledge from device.2020-07-22 17:28:00,SOHStat,772,No acknowledge from device.2020-07-22 17:28:20,FullAvailCap,772,No acknowledge from device.2020-07-22 17:28:20,Debug4,772,No acknowledge from device.2020-07-22 17:28:31,Control,772,No acknowledge from device.2020-07-22 17:28:36,SOH,772,No acknowledge from device.2020-07-22 17:28:39,CtrlStatus,772,No acknowledge from device.2020-07-22 17:28:52,Debug5,772,No acknowledge from device.2020-07-22 17:28:52,Debug6,772,No acknowledge from device.2020-07-22 17:28:56,StateOfChg,772,No acknowledge from device.2020-07-22 17:28:56,Int Temp,772,No acknowledge from device.2020-07-22 17:29:04,FullChgCap Flt,772,No acknowledge from device.2020-07-22 17:29:04,True StateOfChg,772,No acknowledge from device.2020-07-22 17:29:20,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 17:29:44,Debug6,772,No acknowledge from device.2020-07-22 17:29:48,Debug6,772,No acknowledge from device.2020-07-22 17:29:52,SOH,772,No acknowledge from device.2020-07-22 17:29:52,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 17:29:56,StbyCurrent,772,No acknowledge from device.2020-07-22 17:30:12,Debug6,772,No acknowledge from device.2020-07-22 17:30:32,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 17:30:36,FullAvailCap,772,No acknowledge from device.2020-07-22 17:30:52,Flags,772,No acknowledge from device.2020-07-22 17:30:56,StbyCurrent,772,No acknowledge from device.2020-07-22 17:30:56,MaxLoadCurr,772,No acknowledge from device.2020-07-22 17:31:04,FullChgCap Flt,772,No acknowledge from device.2020-07-22 17:31:04,Debug5,772,No acknowledge from device.2020-07-22 17:31:04,Debug6,772,No acknowledge from device.2020-07-22 17:31:12,Debug5,772,No acknowledge from device.2020-07-22 17:31:24,Flags,772,No acknowledge from device.2020-07-22 17:31:28,FullChgCap Flt,772,No acknowledge from device.2020-07-22 17:31:32,AvgCurrent,772,No acknowledge from device.2020-07-22 17:31:32,StbyCurrent,772,No acknowledge from device.2020-07-22 17:31:32,MaxLoadCurr,772,No acknowledge from device.2020-07-22 17:31:32,Debug1,772,No acknowledge from device.2020-07-22 17:31:32,AvgPower,772,No acknowledge from device.2020-07-22 17:31:39,Temperature,772,No acknowledge from device.2020-07-22 17:31:48,FullAvailCap,772,No acknowledge from device.2020-07-22 17:31:48,RemCap,772,No acknowledge from device.2020-07-22 17:31:48,FullChgCap,772,No acknowledge from device.2020-07-22 17:31:52,FullAvailCap,772,No acknowledge from device.2020-07-22 17:31:52,RemCap,772,No acknowledge from device.2020-07-22 17:31:52,Debug7,772,No acknowledge from device.2020-07-22 17:32:44,Debug3,772,No acknowledge from device.2020-07-22 17:33:28,AvgPower,772,No acknowledge from device.2020-07-22 17:33:28,Debug2,772,No acknowledge from device.2020-07-22 17:33:28,StateOfChg,772,No acknowledge from device.2020-07-22 17:33:28,Int Temp,772,No acknowledge from device.2020-07-22 17:33:28,SOHStat,772,No acknowledge from device.2020-07-22 17:33:52,MaxLoadCurr,772,No acknowledge from device.2020-07-22 17:33:56,Debug2,772,No acknowledge from device.2020-07-22 17:34:16,AvgPower,772,No acknowledge from device.2020-07-22 17:34:16,Debug2,772,No acknowledge from device.2020-07-22 17:34:16,StateOfChg,772,No acknowledge from device.2020-07-22 17:34:16,Int Temp,772,No acknowledge from device.2020-07-22 17:34:16,SOHStat,772,No acknowledge from device.2020-07-22 17:34:20,NomAvailCap,772,No acknowledge from device.2020-07-22 17:34:40,Int Temp,772,No acknowledge from device.2020-07-22 17:34:40,SOHStat,772,No acknowledge from device.2020-07-22 17:34:48,FullChgCap Flt,772,No acknowledge from device.2020-07-22 17:34:52,FullChgCap,772,No acknowledge from device.2020-07-22 17:34:52,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 17:35:24,AvgPower,772,No acknowledge from device.2020-07-22 17:35:24,Debug2,772,No acknowledge from device.2020-07-22 17:35:24,StateOfChg,772,No acknowledge from device.2020-07-22 17:35:24,Int Temp,772,No acknowledge from device.2020-07-22 17:35:24,SOHStat,772,No acknowledge from device.2020-07-22 17:35:24,SOH,772,No acknowledge from device.2020-07-22 17:35:28,True StateOfChg,772,No acknowledge from device.2020-07-22 17:35:28,Debug3,772,No acknowledge from device.2020-07-22 17:35:28,Debug4,772,No acknowledge from device.2020-07-22 17:35:28,Debug5,772,No acknowledge from device.2020-07-22 17:35:28,Debug6,772,No acknowledge from device.2020-07-22 17:35:28,Debug7,772,No acknowledge from device.2020-07-22 17:35:32,StateOfChg,772,No acknowledge from device.2020-07-22 17:35:40,Int Temp,772,No acknowledge from device.2020-07-22 17:36:00,AvgPower,772,No acknowledge from device.2020-07-22 17:36:04,Debug5,772,No acknowledge from device.2020-07-22 17:36:24,StateOfChg,772,No acknowledge from device.2020-07-22 17:36:24,FullChgCap Flt,772,No acknowledge from device.2020-07-22 17:36:40,Flags,772,No acknowledge from device.2020-07-22 17:37:16,Debug5,772,No acknowledge from device.2020-07-22 17:37:16,Debug6,772,No acknowledge from device.2020-07-22 17:37:16,Debug7,772,No acknowledge from device.2020-07-22 17:37:24,True StateOfChg,772,No acknowledge from device.2020-07-22 17:37:24,Debug3,772,No acknowledge from device.2020-07-22 17:37:24,Debug4,772,No acknowledge from device.2020-07-22 17:37:24,Debug5,772,No acknowledge from device.2020-07-22 17:37:24,Debug6,772,No acknowledge from device.2020-07-22 17:37:24,Debug7,772,No acknowledge from device.2020-07-22 17:37:36,FullChgCap UnFlt,772,No acknowledge from device.2020-07-22 17:37:36,FullChgCap Flt,772,No acknowledge from device.2020-07-22 17:37:36,True StateOfChg,772,No acknowledge from device.2020-07-22 17:37:56,Debug2,772,No acknowledge from device.2020-07-22 17:37:56,StateOfChg,772,No acknowledge from device.2020-07-22 17:38:12,Debug5,772,No acknowledge from device.2020-07-22 17:38:24,Debug2,772,No acknowledge from device.2020-07-22 17:39:00,True StateOfChg,772,No acknowledge from device.2020-07-22 17:39:00,Debug3,772,No acknowledge from device.2020-07-22 17:39:00,Debug4,772,No acknowledge from device.2020-07-22 17:39:00,Debug5,772,No acknowledge from device.2020-07-22 17:39:00,Debug6,772,No acknowledge from device.2020-07-22 17:39:00,Debug7,772,No acknowledge from device.2020-07-22 17:39:04,Debug5,772,No acknowledge from device.2020-07-22 17:39:04,Debug6,772,No acknowledge from device.2020-07-22 17:39:04,Debug7,772,No acknowledge from device.2020-07-22 17:39:07,CtrlStatus,772,No acknowledge from device.2020-07-22 17:39:12,Debug2,772,No acknowledge from device.2020-07-22 17:39:36,AvgPower,772,No acknowledge from device.2020-07-22 17:39:36,Debug2,772,No acknowledge from device.2020-07-22 17:39:36,StateOfChg,772,No acknowledge from device.2020-07-22 17:39:36,Int Temp,772,No acknowledge from device.2020-07-22 17:39:36,SOHStat,772,No acknowledge from device.2020-07-22 17:39:40,AvgCurrent,772,No acknowledge from device.2020-07-22 17:39:40,StbyCurrent,772,No acknowledge from device.2020-07-22 17:39:48,Debug4,772,No acknowledge from device.2020-07-22 17:40:48,RemCap,772,No acknowledge from device.2020-07-22 17:40:56,SOH,772,No acknowledge from device.2020-07-22 17:41:00,MaxLoadCurr,772,No acknowledge from device.2020-07-22 17:41:28,RemCap UnFlt,772,No acknowledge from device.2020-07-22 17:41:32,MaxLoadCurr,772,No acknowledge from device.2020-07-22 17:41:32,Debug2,772,No acknowledge from device.2020-07-22 17:41:44,StbyCurrent,772,No acknowledge from device.2020-07-22 17:42:00,Debug1,772,No acknowledge from device.2020-07-22 17:42:00,Int Temp,772,No acknowledge from device.2020-07-22 17:42:04,True StateOfChg,772,No acknowledge from device.2020-07-22 17:42:36,Voltage,772,No acknowledge from device.2020-07-22 17:42:44,AvgCurrent,772,No acknowledge from device.

Sincerely,

Lasse

0 Wyatt Keller over 5 years ago in reply to l.wittland

TI__Guru** 105590 points

Hello Lasse,

It looks like the SOC is mostly linear for the test, did you test sending the BAT_INSERT command with your embedded project to see if it was also linear?

The gauge should update in the field once the right conditions are met, if the SOC is correct from send the BAT_INSERT I would just try sending it with your application.

Sincerely,

Wyatt Keller

0 l.wittland over 5 years ago in reply to Wyatt Keller

Intellectual 425 points

Hello Wyatt,

sorry, but JUST TRY is not enough. The whole point in using this fuel gauge was the promise that it WILL learn.

As I wrote I've already tried the BAT_INSERT command, and I didn't see any update. That it SHOULD update doesn't help me when it DOESN'T do it.

That said, I have to admit "doesn't" isn't right in all cases. The log I send you yesterday was from a decharge in progress. After I send it to you the battery manager continued the log, and today in the morning I actually found an event in wich the fuel gauge did update the QMax value (not the RA tables, though). It's in the attached log, around line 8900. Still, this scenario is of limited use for me, as the update took place at a time when the battery was so weak that my application didn't run anymore (easily seen in the 'average current' colum). So I couldn't detect the QMAX_UP flag, and it was cleared approx. 8 hours later (before the battery was charged again and the application woke up again).

You wrote about the 'right conditions' for an update. What are these conditions (apart from BAT_DET = '1')? Why were they met in this case? What can I do to create them at a time when my application is actually running?

Sincerely,

Lasse

0 l.wittland over 5 years ago in reply to l.wittland

Intellectual 425 points

Hi, forgot the log (again). Here it is:

5808.discharge3.log

0 Wyatt Keller over 5 years ago in reply to l.wittland

TI__Guru** 105590 points

Hello Lasse,

If the BAT_DET isn't set the gauge will not perform Impedance Track, this is why the SOC was acting abnormally. Now Impedance Track is engaged the gauge is calculating SOC correctly, Qmax will update over time and keep the gauge accurate, just by programming in the design capacity the gauge already has it's starting Qmax point.

I meant to say by setting the BAT_DET in your application it should work well as it is in the test with the EVM, and you should test it to confirm this.

Qmax should update after discharge, the gauge looks like it is performing as it should now. The Qmax update criteria is in the TRM section 6.4.2.1.3.

Sincerely,

Wyatt Keller

0 l.wittland over 5 years ago in reply to Wyatt Keller

Intellectual 425 points

Hello Wyatt.

> Now Impedance Track is engaged the gauge is calculating SOC correctly, Qmax will update over time and keep the gauge accurate,

Sorry, but no. I've tried re- and decharging three more times during the last few days (with a reset and reprogrammed EVM), but I could not reproduce the qMax update I saw that one time. I even increased FastQmaxStartVoltageDelta, but it didn't make a difference.

> I meant to say by setting the BAT_DET in your application it should work well as it is in the test with the EVM, and you should test it to confirm this.

BAT_DET was set in my application the whole time! It was only the EVM where it wasn't set at the beginning.

> The Qmax update criteria is in the TRM section 6.4.2.1.3.

These criteria don't help me much. While I understand the voltage criterium, the DOD is less clear. Is DOD the opposite from SOC (it's nowhere explained; I've derived that it stands for depth of discharge and that 100% means totally depleted), meaning SOC = 80% --> DOD = 20%? If not, how do i know my DOD (as the documentation offers no way to read it from the fuel gauge)?

With 'Current' I believe the average current is meant, and with 'C' the design capacity. In this case the criterium should always be true for my application since the average decharge current is around 10 mA (against 107 / 4).

So the qMax measurement should always start as soon as my voltage drops below 3,325V.

The FastQmaxEnd criteria (section 6.4.2.1.4. don#t help me either, as I don't know what both DOD and the Numberof FastQmaxmeasurements are. Still 3 doens't sound that much, I'd expect the fuel gauge to reach that number fast.

One other thing I don't understand: when the fuel gauge only learns when it is (almost) empty, how can it learn in a scenario where the battery is kept at least partially capacity all the time?

As I see it we're back at the start. My fuel gauge doesn't learn (or does it at extremely rare occasions in which it fails to inform my application). The configuration you told me would work is the one I had from the beginning. I do see some differences in the measurements of 'my' fuel gauge and the EVM, mostly that the EVM gives better SOC values, but I don't know why it does.

Sincerely,

Lasse

0 Wyatt Keller over 5 years ago in reply to l.wittland

TI__Guru** 105590 points

Hello Lasse,

At the beginning of your log the SOH and other debug values are jumping from 0 to much larger values. Can you share the other logs you are collecting so we can look through them to see if we can find any issues?

If the BAT_DET was enabled on your first system the gauge should've been tracking with the same accuracy as the EVM if the other configurations are the same.

The impedance track algorithm is explained in the following document: https://www.ti.com/lit/an/slua450/slua450.pdf

It covers DOD and other parameters the gauges use.

If you are only cycling the gauge less than 37% all the time the gauging will degrade over time because it will not update the Qmax.

Sincerely,

Wyatt Keller

0 l.wittland over 5 years ago in reply to Wyatt Keller

Intellectual 425 points

Hello Wyatt,

I'll add the recent logs at the bottom of this Post.

I've read the document. If I understood it correctly, to do an initial qMax update, I have to do the following (please correct me if I'm wrong):

-charge the device as much as possible

-keep it fully charged for 5 hours to get a guaranteed DOD update

-discharge it as much as possible to reach/surpass 90% PassedCharge

-make sure it continuosly discharges with at least 4,28 mA to avoid entering relaxed mode and getting an intermediate DOD which screws the 90%

-after discharging, keep it discharged for 5 hours to get the 2nd DOD update, which triggers the qMax update

-keep it above 10°C and below 40°C all the time

This routine is lengthly, but managable, at least for the generation of a 'golden file'. However, we can't do this for thousands of devices in production just to unlock the lower 37% threshold for qMax updates, and we can't hope for our customers to meet the criteria above to do so (it is an unlikely scenario for the devices 'in the field'). Or does writing qMax count as a 'first measurement'?

For RA table updates, I'm completely lost. According to the document, the resistance updates depend on DOD measurements, but DOD measurements are only taken in relaxed mode. So, to update the whole table, I have to discharge the battery from 0% to 100% DOD while being in relaxed mode all the time? Even with no error margin this would take 25 hours. Please tell me I miss something here!

One last thing: the description of the UpdateStatus Value in Data Memory is different in slua450 and sluuac5c. Which one is correct?

I've started another update run with the above routine. I'll tell you if it works.

Now the logs:

No charge6, I've forgotten to start the log here

discharge6.log

Discharge6 is divided by three since the device went to sleep two times during discharging unintended; I now guess the fuel gauge made a DOD update during this time and so couldn't reach the 90% PassedCharge.

discharge6b.log

discharge6c.log

Sincerely,

Lasse

0 Wyatt Keller over 5 years ago in reply to l.wittland

TI__Guru** 105590 points

Hello Lasse,

I've been looking through the logs but I'm not seeing anything that could prevent updates. I'm talking with a colleague now about what could be the issue and I will let you know when I hear back.

You do not need to do a full 100% DOD cycle to update resistance, it will be updated after the Qmax is updated.

Different gauges have different update status, the document referring to your specific gauge is correct SLUA450 is talking about multiple gauges, the TRM is for your gauge specifically.

Sincerely,

Wyatt Keller

0 Wyatt Keller over 5 years ago in reply to l.wittland

TI__Guru** 105590 points

Hello Lasse,

I believe the reason you are having trouble getting updates is your currents are so low the gauge is entering sleep mode periodically and trying to perform calibrations. Your battery is on the border of the lowest capacity so this is a rare case of operation. I would recommend you change the sleep current lower, so that it is always lower than you discharge current but higher than the deadband.

See if this helps and let me know.

Sincerely,

Wyatt Keller

0 l.wittland over 5 years ago in reply to Wyatt Keller

Intellectual 425 points

Hello Wyatt,

I have lowered sleep current to 7 mA and increased the consumption of our device to ~13 mA. I also set the fast qMax start volt delta to 400 since I observed that the voltage does recover by 200 to 300 mV quickly after our device goes to shutdown.

Once again it did not learn.

8311.discharge8_before.gg.csv

1033.discharge8.log

discharge8_after.gg.csv

Sincererly,

Lasse

0 l.wittland over 5 years ago in reply to l.wittland

Intellectual 425 points

Hello Wyatt,

there is one more thing that gives me headaches. Assuming we finally can record a 'golden file' and I programm it to our newly produced devices, does the '90% passed charge for first measurement' rule still apply? Is there a way to tell the fuel gauge it shall use the 37% rule instead?

Sincererly,

Lasse

0 Kang Kang over 5 years ago in reply to l.wittland

TI__Mastermind 24870 points

Hello Lasse,

No, in this case, the gauge uses 37%. The way the gauge does this is with update status. It should go from 0x03 to 0x00.

0 l.wittland over 5 years ago in reply to Kang Kang

Intellectual 425 points

Hello Kang,

the update status of my fuel gauge is 0x00. It is 0x00 after a reset (battery disconnected), it is 0x00 after a charge/discharge cycle. The only way I got a value of 0x03 was when I wrote it to the register (via battery management studio). But it didn't clear back to 0x00 when I wrote new qMax or Ra values.

Does that mean that after a reset I'm always in the '37% mode'? If so, I'm even more confused why the fuel gauge doesn't learn properly.

Sincerely,

Lasse

0 Wyatt Keller over 5 years ago in reply to l.wittland

TI__Guru** 105590 points

Hello Lasse,

If you manually write the register it will stay until there is a POR because this is a ROM gauge.

Your logs show the gauge is going in and out of a lot of the different modes (control register is changing drastically) It's not clear what is causing this but you aren't getting an update because the gauge is switching modes so often.

Sincerely,

Wyatt Keller

0 l.wittland over 5 years ago in reply to Wyatt Keller

Intellectual 425 points

Hello Wyatt,

> If you manually write the register it will stay until there is a POR because this is a ROM gauge.

Ok, understood.

> Your logs show the gauge is going in and out of a lot of the different modes (control register is changing drastically)

> It's not clear what is causing this but you aren't getting an update because the gauge is switching modes so often.

Sounds good. So what can I do to find out what is going wrong here and to correct it?

If I understood the data (especially discharge9) correctly, the fuel gauge does reinitialize itself several times during the discharge (INITCOMP flag not set), which happens after a SLEEP or POR.

Regarding SLEEP: The device is nowere near the hibernate voltage of 2.2V. The current isn't constant on discharge, it might dop below 3mA for a short time, but on the average it is arount 9 to 13 mA. Still, I've never issued the SET_HIBERNATE command and the HIBERNATE flag isn't set, so I think it's unlikely the fuel gauge went to sleep.

Regarding POR: I havn't seen the ITPOR flag; also, the RAM contents weren't rewritten from the RAM, so that's unlikely, also.

Regards,

Lasse

0 Kang Kang over 5 years ago in reply to l.wittland

TI__Mastermind 24870 points

Hello Lasse,

To generally debug the non-linear behavior, you will want to check the following:

1. Does the gauge have "reset" commands sent to it from the host, this will cause non-linear behavior.

2. Did you do a learning cycle using a well matched ID using GPCCHEM?

3. Did you do an accuracy cycle at constant current discharge from full to empty and is this linear?

Thanks!

0 l.wittland over 5 years ago in reply to Kang Kang

Intellectual 425 points

Hello Kang,

1) I'm using an EVM and a MSP430 to debug/evaluate this problem. I'm sure I didn't send a reset on purpose through the battery management studio.

2) I'm using a BQ27421-G1A. The Chem ID is fixed, so I didn't use GPCCHEM. The Battery I use is this:

www.geyer-electronic.de/.../DYNAMIS-Lith-Polymer-LP402020_01.pdf

3) I'm doing discharges from full to empty for more than two months now. If you browse through this thread, you can find several discharge_x.log files I've recorded during this time. The discharge shown by the battery studio was constant at ~9 (later ~13) mAh - as I wrote before, there should be small spikes for a few ms when periperals like a LED get activated.

I'm not sure what you mean by 'accuracy' cycle.

Sincerely,

Lasse

0 Kang Kang over 5 years ago in reply to l.wittland

TI__Mastermind 24870 points

Hello Lasse,

I understand now. Please make sure you use a well-matched chemID, that will resolve the nonlinearities you see. If you use the generic chemID, this is potentially expected behavior.

Thanks!

0 l.wittland over 5 years ago in reply to Kang Kang

Intellectual 425 points

Hello Kang,

thanks, but how exactly do I use a 'well-matched' chemID, when the chemID of the fuel gauge is fixed?

Sincerely,

Lasse

0 Kang Kang over 5 years ago in reply to l.wittland

TI__Mastermind 24870 points

Hello Lasse,

We normally run through GPCCHEM to determine if the default ID is a good match first.

There may be other gauges that are a better fit such as the bq27z561-R1.

That will have configurable chemID.

0 l.wittland over 5 years ago in reply to Kang Kang

Intellectual 425 points

Hello Kang,

I don't look for a perfect match. I'm aware that the BQ27421-G1 with its fixed chem ID woun't be as accurate as a fuel gauge with a configurable one. I can live with the fuel gauge being a little inacurate.

What I cant cope with is:

-the fuel gauge being massively off, as it was in the cycles I opened this thread with. I understood that my fuel gauge was unlearned, and that it might get better once it learned qMax and the RA values.

-the fuel gauge not learning. This is a feature we and our customer expect to work. I managed to get a qMax update once (RA never), but I was unable to reproduce this or even create a golden file (which most of this thread and Wyatts input actually focused araund).

-a hardware change, especially to a gauge with a different pin-out.

What I need is a reproducable way to get the fuel gauge learning. With Wyatts help I've tried several things spread through this thread, but so far nothing worked.

When it has learned, I hope/expect it will measure the SOC more accurate than it does now. But that is step 2. Now I have to get it learning.

Sincerely,

Lasse

0 Kang Kang over 5 years ago in reply to l.wittland

TI__Mastermind 24870 points

Hello Lasse,

1. For the fuel gauge being off, it could be that the chemID default does not match the battery such that the learning cycle will also fail. Do you know if RUP_DIS was set during your learning cycle? If not, please check it.

2. See #1.

3. The best way would be to try and evaluate a bq27z561-R1 and check to see if it is better if you can modify the chemID.

0 l.wittland over 5 years ago in reply to Kang Kang

Intellectual 425 points

Hello Kang,

yes, RUP_DIS was usually set (I didn't check every single line of the logs, but where I did it was set).

The documentation (sluuac5c) states that RUP_DIS 'Indicates the Ra table updates are disabled'. Does this also apply to Qmax updates?

Sincerely,

Lasse

0 Kang Kang over 4 years ago in reply to l.wittland

TI__Mastermind 24870 points

Hello Lasse,

RUP DIS is only for resistance updates. Qmax should be updating if you provide ample relaxation.

Power management

Power management forum

BQ27421-G1: non-linear SOC values during linear (de-)charge