BQ20Z95: IIC BUS data issue

Cherry Zhou

Mastermind 22235 points

Part Number: BQ20Z95
Other Parts Discussed in Thread: BQSTUDIO

Hi team,

Here're some follow-up information regarding the original post:

Please see bqStudio setting information, they only monitor real-time temperature.

Set scan cycle is 1 second, log cycle is 1 second.

Please see log file there is a error record:

The question is what dose this message mean? is there no data be measured？ what information be sent to out MCU at this situation?

In the log file, there are "Sample" number and "Elapsed(s)" number, at the beginning, the Elapsed(s) number = Sample number, but as the time fly, the Elapsed number become much bigger than Sample number, could you explain what's reason and what happened?

Could you help check the follow-ups? Thanks.

Best Regards,

Cherry

over 3 years ago

0 Jackson DiGiovanna over 3 years ago

TI__Expert 8815 points

Hi Cherry,

Could you send me the entire log file? I also am curious why samples are taking 1s in the beginning and what appears to be around 1.4s as the file goes on.

Best Regards,

Jackson

0 Cherry Zhou over 3 years ago in reply to Jackson DiGiovanna

TI__Mastermind 22235 points

Hi Jackson,

Thanks for your support.

Please see the file here:

https://e2echina.ti.com/cfs-file/__key/communityserver-discussions-components-files/24/907-22-03.log

https://e2echina.ti.com/cfs-file/__key/communityserver-discussions-components-files/24/9141102.log

Please note the customer had changed the time interval from 3 second cycle to 1 second cycle at first file at the monitor beginning stage.

Thanks and regards,

Cherry

0 Jackson DiGiovanna over 3 years ago in reply to Cherry Zhou

TI__Expert 8815 points

Hi Cherry,

I will take a deep look at these logs now and get back to you on Monday.

Best Regards,

Jackson

0 Shirish over 3 years ago in reply to Jackson DiGiovanna

TI__Guru 57697 points

Hello Cherry,

We do not recommend logging at 1s unless it is required for some debug. This hammers the gauge with too much communication, leaving it less time to perform gauging. The communication errors are common when the gauge is busy with some simulation. The register for which there was a communication error will be blank in the log.

0 Jackson DiGiovanna over 3 years ago in reply to Jackson DiGiovanna

TI__Expert 8815 points

Hi Cherry,

It seems like the sample rate is not exactly 1s. As the log goes on, the discrepancy between time and sample number increases. I am not sure of the cause but this seems constant throughout the file. As far as the error goes, I would not be too concerned here. This can be caused by a number of things but should not yield any gauging inaccuracies. Additionally, the values recorded during the error sample seem to be consistent anyways. Errors in logs are common (especially when not using a bqstudio log) and should not impact gauging performance.

Best Regards,

Jackson

0 Cherry Zhou over 3 years ago in reply to Jackson DiGiovanna

TI__Mastermind 22235 points

Hi Jackson and Shirish,

Thanks for your help.

When CPU (host) read data from battery, but battery has error happen at this time, like log file record: no data present, what data will be read by CPU (host)? 0x00, 0xFF, or others random data or last measure data? is there rule of the battery communication protocol define this condition?

Thanks and regards,

Cherry

0 Shirish over 3 years ago in reply to Cherry Zhou

TI__Guru 57697 points

Hello Cherry,

The battery will NACK under this condition, so there will be no data returned. The CPU will not get any data back.

Power management

Power management forum

BQ20Z95: IIC BUS data issue