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.

BQ4050: FCC and RC adjustment with cold temperatures

Part Number: BQ4050

We are using the bq4050 in a few development projects and are seeing a few inconsistencies between the different products while logging charge and discharge cycles at 5 degrees C.

The RSOCL bit is set to 1, meaning that we want the SOC to stay at 99% until a valid charge termination is detected. At 5 degrees C, the charge capacity is much less, as the battery internal resistance is much higher, and we can see that the SOC and RC can jump to 100%, from any value, as soon as a charge termination occurs. We can then observe, on one of our products (product 1 - 1 cell application), that the capacity then jumps back to the actual capacity, as soon as the current reaches the discharge threshold. This makes sense, as the FCC does not get changed in cold temperatures. 

We have a different product (product 2), with mostly the same settings, except that this one is setup for 4 cells in series. This product also does not have an external thermistor connected and makes use of the internal temperature sensor. On Product 2, we can observe that the SOC and RC will jump to 100%, from any value, if a charge termination occurs. The difference here is that the capacity does not jump back to the actual capacity when the current reaches the discharge threshold. This causes a misalignment during the discharge when EDV2,1 and 0 is reached. 

I cannot seem to find a setting that will cause this difference in this behaviour. I have attached the .gg.csv files for both products. Any help or clarification will be appreciated.


 TI_product_1.gg.csvTI_product_2.gg.csv

  • SOC will be 100%, by definition, if a valid charge termination is detected. It will not jump back down if a discharge current is detected. The gauge will start to coulomb count and subtract the measured passed charge from RM (=FCC after a charge termination) so SOC will drop smoothly.

    Please elaborate with an actual example what you observe for product #1. SOC should not jump to "actual capacity" based on discharge current threshold and measured current.

  • I have attached a charge and discharge log for product 1.

    In the charge log you can see that the RSOC charges to 91% and then jumps up to 100% as soon as the charge termination current is detected. Also, during the charge, the remaining capacity increases to 3912 mAh and then jumps to 4300 mAh (FCC value) as soon as the charge termination current is detected. 

    The discharge happens about 5 seconds after the charge has stopped. In the discharge log, you can see that the first entry with 26 mA (30 mA discharge current threshold) shows 100% RSOC and 4300 mAh Remaining capacity. In the seconds entry, the current is 1346 mA, the RSOC is back to 91% and the Remaining Capacity is back to 3912 mAh. After that, the capacity drops as expected.

    We did 5 charge/discharge cycles in cold temperature and have gotten the same result with each.



    Product_1_Charge_LOG.xlsxProduct_1_Discharge_LOG.xlsx

  • For product #1, the gauge will calculate a charging deficit if it detects premature full charge. If you enable CSYNC and CHG_DEFICIT_EN (both are in CEDV Gauging Configuration), the gauge will subtract the charging deficit at start of discharge.

    Your CEDV Gauging Configuration setting is 0x1B62, hence both CSYNC (0x0002) and CHG_DEFICIT_EN (0x0200) are set. If you don't want this behavior, set CHG_DEFICIT_EN to 0 (0x1962) 

  • This is the desired behaviour for our application, as this would prevent the Remaining Capacity and RSOC to prematurely drop to 0% at the end of the discharge. So, we want to keep this setup for product 1. We want this behaviour on product 2 as well but it does not seem to happen. The CEDV Gauging Configuration setting for product 2 is 0x1B62 as well, so I would expect it to work the same. Are there any other settings or variables that could influence this behaviour?

    For reference, the two major differences between the two products:

    Product 1 is a 1 cell application using an external thermistor to measure the battery temperature.

    Product 2 is 4 cells in series application using only the internal temperature measurement of the bq4050 to measure the battery temperature.

    I have attached a charge and discharge log at 5 degrees C for product 2 as well. You can see that during the charge, the RSOC jumps from 84% to 100% at the charge termination event. But when the discharge starts, the Charge deficit value does not get subtracted from the Remaining Capacity.

    Product_2_Charge_LOG.xlsx

    Product_2_Discharge_LOG.xlsx

  • The gauge will only perform this charge deficit compensation if it's enabled *and* for temperature *other* than JEITA Standard Low, Recommended and Standard High. Given that you reported that you use a different temperature measurement setup, it's probably related to your product #2 using a temperature that falls into Standard Low. Recommended or Standard High.