Unless otherwise indicated, the foregoing is not admitted to be prior art to the claims recited herein and should not be construed as such.
The amount of electric charge that a battery can store is typically referred to as the battery's “capacity”. The state of charge (SoC) of a battery expresses the battery's present capacity (how much electric charge is presently stored) as a percentage of the battery's maximum capacity (the maximum amount of electric charge that can be stored). The SoC is usually displayed so the user has an idea as to when to recharge the battery. The SoC may not always reflect the battery's actual present capacity, however.
For example, it is typical for some devices to power down when the battery level falls below a cutoff voltage level. The device (e.g., mobile phone) will initiate a power down sequence in order to properly shutdown certain applications and the device itself, for example, in order to maintain data integrity. However, since the battery in fact still contains a non-zero amount of charge, the SoC will accordingly show a non-zero level. This can lead to confusion as the device begins to power down even though the user sees a non-zero SoC.
SoC inaccuracy may arise during battery recharging. The charging sequence for charging a battery includes a so-called “constant current” charging phase where the battery is charged with a constant charging current. When the battery voltage reaches a predetermined voltage level (sometimes referred to as the “charge float voltage”), the charging sequence changes to a so-called “constant voltage” charging phase. In constant voltage charging, a charging current continues to flow into the battery until the current flow falls below a termination current level. Constant voltage charging begins when the battery reaches some percentage (say, for example, 95%) of its capacity, at which time the SoC display will show about 95%. However, the time it takes for battery capacity to reach maximum can be as long as the time it takes for battery capacity to go from 0% to 40%. Accordingly, the user will see the SoC to be at 95% for an unexpectedly long time, which can lead to confusion.
Some battery management systems (BMS) may perform an “auto recharge” sequence when the battery is fully charged. This may happen, for example, if the source of power is still available (e.g., wall adapter is still plugged in). As a result, the displayed SoC may initially display 100% to indicate a fully charged battery, and then display a decreasing SoC as the device consumes power from the battery. Meanwhile, the BMS may perform an auto recharge to bring the battery charge level back up to 100%, and the SoC display will reflect that fact by displaying in increasing SoC. The fluctuations in the displayed SoC resulting from auto recharge can lead to confusion since one would not expect fluctuations to occur when the battery appears fully charged and the adapter is still plugged in.
In accordance with the present disclosure, a system state of charge (SoC) is presented to the user in place of a battery SoC that is estimated based on battery measurements. In some embodiments, an SoC curve may be provided to map an estimated battery SoC to a system SoC. The SoC curve may be periodically updated using predetermined voltage and current values, and making battery SoC estimates using the predetermined voltage and current values. The estimated battery SoC may define endpoints of the SoC curve. The SoC curve may then be used to map estimates of battery SoC (made using measurements of battery voltage and battery current) to system SoC, which may then be presented to a user.
The following detailed description and accompanying drawings provide a better understanding of the nature and advantages of the present disclosure.
With respect to the discussion to follow and in particular to the drawings, it is stressed that the particulars shown represent examples for purposes of illustrative discussion, and are presented in the cause of providing a description of principles and conceptual aspects of the present disclosure. In this regard, no attempt is made to show implementation details beyond what is needed for a fundamental understanding of the present disclosure. The discussion to follow, in conjunction with the drawings, make apparent to those of skill in the art how embodiments in accordance with the present disclosure may be practiced. In the accompanying drawings:
In the following description, for purposes of explanation, numerous examples and specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be evident, however, to one skilled in the art that the present disclosure as expressed in the claims may include some or all of the features in these examples, alone or in combination with other features described below, and may further include modifications and equivalents of the features and concepts described herein.
As shown in the embodiment shown in
expressed with reference to the terms shown in
In some embodiments, when a computed battery SoC is ≧min % and ≦max %, then the system SoC can be determined in accordance with the expression above. When the computed battery SoC is <min %, the system SoC is 0%, and when the computed battery SoC is >max % the system SoC is 100%. The system SoC may then be presented to the user, e.g., on the display component of an electronic device (e.g., 10,
Referring for a moment to
Referring to
In some embodiments, the processing shown in
At block 202, the fuel gauge 14 may receive data that defines an initial SoC curve (e.g., 100). The data may be stored in the memory 18 (
After the SoC curve 100 is initialized, the fuel gauge 14 may compute a value for battery SoC. Thus, for example, at block 204, the fuel gauge 14 may receive a battery voltage measurement. In some embodiments, for example, the fuel gauge 14 may include analog-to-digital converter (ADC) circuitry to make a measurement of the voltage on the battery 22 and perform a conversion to produce a battery voltage measurement. In other embodiments, the battery voltage measurement may be provided by other circuitry in the electronic device 10.
At block 206, the fuel gauge 14 may receive a battery current measurement. In some embodiments, the battery current measurement and the battery voltage measurement may be made concurrently. In some embodiments, the fuel gauge 14 may include an ADC to measure the current flowing through the battery 22 and provide a measurement of the battery current. In other embodiments, the battery current measurement may be provided by other circuitry in the electronic device 10.
At block 208, the fuel gauge 14 may determine or otherwise compute a battery SoC value using the battery voltage and battery current measurements. In some embodiments, for example, the fuel gauge 14 may evaluate a battery model as part of the processing to produce a battery SoC. In some embodiments, the fuel gauge 14 may include circuitry for taking battery temperature to factor in battery temperature in computing the battery SoC. For example, the fuel gauge 14 may include ADC circuitry to make a measurement of the battery temperature. Additional details of the battery SoC will be described below.
At block 210, the fuel gauge 14 may update the SoC curve. In some embodiments, this SoC curve may be updated by updating either or both endpoints (e.g., 102, 104) of the SoC curve. For example, either or both endpoints may be updated by evaluating a battery model. Referring for a moment to
At block 212, the fuel gauge 14 may evaluate the SoC curve using the battery SoC determined at block 208 to obtain a system SoC value. The system SoC value may then be presented (block 214) to the user, e.g., on the display component 16 of the electronic device 10.
The process may then return to block 204 and repeated with the next battery voltage and battery current measurements. With each iteration, the SoC curve may be updated. Accordingly, the mapping from battery SoC to system SoC may vary from one iteration to the next. Referring to
Methods for computing battery SoC (block 208,
Referring to
At block 504, the estimated battery voltage produced by the battery model in block 502 may be compared to a predetermined minimum voltage. In a particular embodiment, for example, the minimum voltage level is the system cutoff voltage. As can be seen in
Referring to
A maximum endpoint condition, for example, may be based on battery charging. Battery charging conventionally occurs in two phases, a constant current phase followed by a constant voltage phase. Battery charging usually proceeds initially in the constant current phase. When the battery voltage reaches a predetermined voltage level (referred to as the “battery charge float voltage”), battery charging then enters a constant voltage phase. Charging continues in this phase until current flowing into the battery falls below a predefined termination current, sometimes referred to as the charger termination current.
When the battery voltage reaches the battery charge float voltage during charging, it may be desirable to show a system SoC of 100%, since the battery voltage will remain substantially at the battery charge float voltage until the charger termination current is reached. Accordingly, in a particular embodiment, the maximum endpoint may be computed using the battery charge float voltage and a “system termination current”. The system termination current may be a value higher than the charger termination current. The system termination current may be pre-programmed value stored in memory 18. In some embodiments, the system termination current may be an instantaneous value measured at the time of switching over from constant current phase to constant voltage phase.
The elements of the battery model may be functions of one or more of the inputs to the battery model. The elements of the battery model may include an open circuit voltage (OCV) element, an equivalent series resistance (ESR) component, and a resistance Rslow that represents a transient response behavior of the battery. For example, when the battery model is being evaluated to compute the battery SoC, the current that is provided to the battery model may be the measured battery current. The SoC that is provided to the battery model may be the previously computed battery SoC. When the battery model is being evaluated to update the minimum (maximum) endpoint value of the SoC curve (e.g., 100,
It will be appreciated that the 0% and 100% endpoints (e.g., 102, 104,
where 0% BatterySoC is the battery SoC at the 0% endpoint and
BatterySoC is an estimated battery SoC.
The compensation can be used to produce an Rseries value for the ESR according to:
where SoC_CutOff is the corrected 0% system SoC described above.
In various embodiments, the transient response resistor Rslow in the battery model for updating the 0% endpoint may be evaluated in several ways. For example:
where kCOMP may represent an average of
Similarly, in some embodiments, when using the battery model to update the 100% endpoint of the SoC curve, the series resistance Rseries of the ESR may be dynamically estimated. A compensation may be extrapolated to predict values of Rseries for different SoCs. In a particular embodiment, for example, a compensation function fRSERIES-COMP(BatterySoC) may be defined as:
where 100% BatterySoC is the battery SoC at the 100% endpoint and
BatterySoC is an estimated battery SoC.
The compensation can be used to produce an Rseries value for the ESR according to:
where SoC_Full is the corrected 100% system SoC described above.
In various embodiments, the transient response resistor RSLOW in the battery model for updating the 100% endpoint may be evaluated in several ways. For example:
As explained above, the 0% and 100% system SoC endpoints of the SoC curve can vary each time the SoC curve is updated. Consequently, the system SoC for a given battery SoC may increase or decrease; e.g., during a charging state or a discharging state. Accordingly, in some embodiments, the system SoC value may be “filtered” to account for varying SoC curves, before it is presented to the user. In some embodiments, for example, when the system is discharging, only decreases in the system SoC are presented to the user; an increase in system SoC can be ignored and the presently displayed SoC remains unchanged. Conversely, when the system is charging the battery and the charging current is greater than the system demand, then only increases in the system SoC are presented to the user.
When a change in the system SoC follows the system status (e.g., decreases during discharging state or increases during charging state), then a slope filtering may be applied to ensure that the a previously applied monotonic filter will not produce a sudden change in the displayed system SoC when the system crosses over between discharging and charging states; e.g., a power adapter is plugged in, or the power adapter is removed.
The above description illustrates various embodiments of the present disclosure along with examples of how aspects of the particular embodiments may be implemented. The above examples should not be deemed to be the only embodiments, and are presented to illustrate the flexibility and advantages of the particular embodiments as defined by the following claims. Based on the above disclosure and the following claims, other arrangements, embodiments, implementations and equivalents may be employed without departing from the scope of the present disclosure as defined by the claims.
The present disclosure claims priority to U.S. Provisional App. No. 61/798,570 filed Mar. 15, 2013, the content of which is incorporated herein by reference in its entirety for all purposes. The present disclosure is related to (1) a non-provisional application entitled “ACTIVE MEASUREMENT OF BATTERY EQUIVALENT SERIES RESISTANCE” (Applicant ref. no. 132005U1) filed herewith and (2) U.S. application Ser. No. 13/719,062 entitled “BATTERY FUEL GAUGE” filed Dec. 18, 2012 the content of both of which are incorporated herein by reference in their entireties for all purposes.
Number | Date | Country | |
---|---|---|---|
61798570 | Mar 2013 | US |