Other Parts Discussed in Thread: BQSTUDIO
Hi Team,
My customer is seeing an issue with the reported capacity on the BQ27510-G3 and I'd like to get your help.
They have written all the design parameters relevant to their system (design capacity, temperature thresholds, charging voltage, etc.) in the data flash of the BQ27510-G3. They've reset the device, and confirmed the parameters are still as expected. They are implementing this with their host MCU and not the BQ tool.
At what point will the reported SOC, NominalAvailableCapacity, FullCapacity, RemainingCapacity, and FullChargeCapacity, be accurate? They've done a full discharge and charge cycle, and still see inaccurate values for these reads. Is there a bit that needs to be set, or routine that needs to be done to get the fuel gauge to know where the battery is in its discharge / charge cycle?
Do note that they are still operating in the UNSEALED state. From what we can tell, the only benefit of the SEALED state is to avoid accidental writes to the data flash. Does the unit need to be SEALED for accurate data?
The reason they are hesitant to enter the SEALED state is because they cannot enter the FULL ACCESS state from the UNSEALED state. The data flash says the default key is 0x00 (Assuming 0x0000 0x0000), yet they can't seem to enter the FULL ACCESS state.
Any hints you can provide here would be very helpful!
Thanks,
Mitchell
