Other Parts Discussed in Thread: BQ40Z50-R2,
BACKGROUND:
I am designing a product that uses a battery pack with this IC in it.
This products application is such that it is not likely to meet the automatic Qmax update criteria.
Because of this i am making a special mode for the product to run the battery pack through a Qmax update profile as needed.
A profile without any intelligence would for instance charge the pack to 100%, wait 5-6 hours, discharge to near empty, wait 5-6 hours and then ideally the calibration flag would be reset. This unintelligent profile takes up to 24 hours to perform in my application.
GOAL:
I would like to be able to have this Qmax update profile ran with intelligence in order to minimize the downtime of the product when a Qmax update profile is ran.
By intelligence, what i mean is to have trigger points to know when to start discharging/charging the pack to take the second OCV reading.
For example: Query the pack to know when the first Qmax update OCV reading has been performed then discharge the battery, query the battery again until the second Qmax update OCV reading is taken and confirm that the Cal Flag has been reset.
QUESTION:
I see that the VOK and QEN are related to the Qmax update, but both slua364b and sluu493 are not explicitly clear on what these status bits mean.
Could you provide a clearer description of when these are set/reset and how that relates to the Qmax update?
As it relates to the above example, would either VOK or QEN be good status bits to query to know when a Qmax Update OCV reading has been completed?
-Justin
