Other Parts Discussed in Thread: BQSTUDIO
I read through the application note: How to Configure the BQ35100 for EOS Mode and have a few queries for which I will need your valuable inputs:
- If the battery that I intend to use in my final application is already in the bqSTUDIO library, do I still need to perform the full discharge test of the battery as described in the application note? If yes, what benefit does it bring?
- How often does the battery draining test need to be carried out? Is it once per production batch?
- After reading posts related to BQ35100 on the forum, I understand that if EOS alert is the only expectation and no SOH level reporting is needed, then a Chem ID does not need to be programmed into the chip. Is my understanding correct? In that case, is the full discharge of the battery as outlined in query no. 1 needed?
- The application note talks about saving the scaled resistance and measured impedance on a Non-Volatile storage attached to the MCU. Since scaled resistance is generated from measured impedance based on the Chem ID, I believe that the example assumes that a Chem ID is already programmed into the chip. Is my understanding correct? The application note does not mention this step or requirement.
- Section 7 of the application note outlines the procedure to configure the EOS parameters. The recommendation about the parameter New Batt R Scale Delay needed for initial EOS learning is clear. However, I have questions about the parameter EOS Trend Detection. Won't a value of 20% be enough to determine the EOS event or does the value need to be determined based on when the battery becomes unusable based on individual circumstances?
- Other than the two parameters mentioned in query no.4, are there any other parameters in the Table 7-2 that needs to be set by the MCU?
Regards,
ashare