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: Internal calculation timing diagram?

Part Number: BQ34Z100-G1
Other Parts Discussed in Thread: BQ34Z100

Hi Team,

Is  there a timing diagram that shows how long you need to wait until the internal register's are updated after a measurement is taken. I am looking for a similar table to the below  but for the  BQ34Z100-G1

  • Hi Julio,

    Unfortunately this information is not available for the bq34z100.

  • Thanks Batt, then how does a customer know when the register's have been updated? and how do you know the difference of when one measurement was taken versus another?

    This is for a customer with an NDA, should i email your directly instead?

  • Hi Julio,

    Typically customers are concerned about updates to the RAM registers. That happens once per second when the gauge is awake and in sleep it happens at the sleep time interval. DF updates typically take a few hundred ms per row but they can be batched. When a flash update happens the gauge can program a word in 2ms.

    This is the only information that the DS has. If you would like to you can certainly email me.

  • Batt,

    Thank you very much for the feedback.  Correct me if i am wrong, the device takes a measurement once every second. After that happens the device will update the DF (Data Flash, could not find if this is where the Device stores current, voltage and temperature?) which will take "few hundred" ms "per row". ( I dont know what batched means)

    So the time to wait after a measurement is taken to read those register's is equal to "few hundred ms" X row of data correct? If so, what does "few hundred ms " mean and how many rows?

  • Hi Julio,

    No, the device doesn't store V, I, and T in df. It stores it in the RAM. Whenever a value is updated in the df, it's for something like a temperature exceeding a previous maximum, or a resistance change, or a Qmax change. When these updates happen, especially Ra updates, they can be written back to back at the same time to the df. That is what I meant by batched.

    There should be no need for you to scan registers more than once a second. It is highly unlikely that you need data from df more than once a minute. So, in either of these cases df reads will not give you stale data. You really should not be worried about how long df writes takes.