电池性能分析

/** **************************************************************************************** * * @file custom_socf_battery_profile.h * * @brief a battery profile data for State Of Charge * * Copyright (C) 2016 Dialog Semiconductor. * This computer program includes Confidential, Proprietary Information * of Dialog Semiconductor. All Rights Reserved. * **************************************************************************************** */ #ifndef CUSTOM_SOCF_BATTERY_PROFILE_H_ #define CUSTOM_SOCF_BATTERY_PROFILE_H_ #define VOL2SOC_LUT_SIZE 11 /* Battery profile data for 110mA battery */ #define SOCF_BATT_LOW_CURRENT 2000 //2mA load #define SOCF_BATT_HIGH_CURRENT 110000 //110mA load #define SOCF_BATTERY_CAPACITANCE 110 //Battery capacity (110mAh) #define SOCF_CHARGING_CURRENT 90 static const int16_t vol_dis_low_0[VOL2SOC_LUT_SIZE] = { 3450, 3510, 3561, 3591, 3634, 3681, 3743, 3833, 3934, 4053, 4170 }; static const int16_t vol_dis_high_0[VOL2SOC_LUT_SIZE] = { 2900, 3193, 3291, 3346, 3392, 3443, 3509, 3595, 3694, 3802, 4021 }; static const int16_t vol_chg_0_0 = 3447; //90mA charging #endif /* CUSTOM_SOCF_BATTERY_PROFILE_H_ */

I added calls to socf_get_avg_current(active_count, active_period), and it seems to report correct values. If I take the returned value from socf_get_avg_current() and divide it by 0.277, I should get the result in uA, is this correct?

I am using the PXP_Reporter demo with the following modifications:
_ 32MHz crystal instead of 16MHz

_ updated the custom_socf_battery_profile.h with the code attached above.

I figured out that this
#define SOCF_BATT_CAPACITANCE_ADJ (1)

will set the capacity to 1000 after end of charge is detected.

The reported socf_soc still seems to be off by a lot. In my particular case after using 44mAh (60%), the socf_soc still reported 90% battery level.

1) Reverted the custom_socf_battery_profile.h to default SDK

2) #define DEBUG_SOC

3) pm_set_sleep_mode(pm_mode_active)

in pxp_reporter and build debug option. Flashed the custom board and watched the terminal output.

The first read of the battery seems to report approximately correct SOC and the voltage reporting is accurate. However, as time go by, with a ~1.5mA constant drain on the battery (from running pxp_reporter, no additional load placed onto device), the SOC level goes up as voltage goes down. Log below:

[ 1 sec] DLG_SWFG SOC= 904 VOL=4104 ... [ 1000 sec] DLG_SWFG SOC= 908 VOL=4075

Here's some finding from enabling #debug_soc:

Debug Count Average is the average count of the reported active_count used during socf_get_soc_active(void).

Debug Current Average is the average count divided by 1000 of the socf_get_avg_current from the active_count inside socf_get_soc_active(void).

Joulescope是measuring instrument's average current during that time period.

Delta is the differnce in reported value by the SOC and the Joulescope.

Notice the Delta is not linear, it increases as the current increases.

I believe it is obvious the Coulomb count is inaccurate.

Please setup a call with me to discuss this. It is urgent and it's affecting our development time. In particular I need to know where your formula are coming from and how we can fix these to get the correct results.

How is this number determined?

#define SOCF_MAX_COULOMB_COUNT_PER_MA_SEC 73584LL

Why are these two scenario needed?

if (count > 0) { offset_current = 500 - (250 * avg_current) / 5000; } else { offset_current = SOCF_DEFAULT_OFFSET_CURRENT - (avg_current * 50) / 1500; }