You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I converted the voltage curves from the product data sheet into data points that could then be used to find the state of charge given the voltage, current, and ambient temperature. Temperature only seems to affect the voltage at near-freezing temperatures, so I added a small correction term at cold temperatures (calculated from averaging the voltage difference between the 23C curve and the 0C/-20C curves). This also assumes that the battery pack has 24 cells in series and 10 in parallel (not sure of the exact specs so this was just an estimate, but can easily be changed to the actual series/parallel in the updateBatteryInfo() function).
This updates the getBatteryPercent abstraction, so it can be easily combined with the coulomb-counting branch without requiring many integration changes.
I measured the data points using a picture of the graph and an online converter. I tried contacting Molicel directly but couldn't get the exact data for the voltage curves—the converter seems to be fairly accurate though, e.g. measurement of the 0.84A curve:
May be inaccurate at extremely low temperatures when near full charge since the correction term is the averaged difference, and voltage difference between temperatures is greatest when near full charge
I decided to use a correction term only for the temperature even though it could potentially be used for both. My reasoning was that the current probably varies a lot, so having an accurate estimation based on current was more important than for estimating at sub-freezing temperatures.
Battery size is an input variable that determines the number of cells in parallel and has to be known at startup (potentially a user-inputted value?). I wasn't sure how to accurately differentiate between battery sizes—likely a combination of SOC, voltage derivative, and current could be used to get a rough idea of which size it is, but I think it would require already knowing the SOC. Unfortunately I didn't have the data for this so I just made battery size a user-input and default it to the 3.7kWh (24 series 10 parallel) battery.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I converted the voltage curves from the product data sheet into data points that could then be used to find the state of charge given the voltage, current, and ambient temperature. Temperature only seems to affect the voltage at near-freezing temperatures, so I added a small correction term at cold temperatures (calculated from averaging the voltage difference between the 23C curve and the 0C/-20C curves). This also assumes that the battery pack has 24 cells in series and 10 in parallel (not sure of the exact specs so this was just an estimate, but can easily be changed to the actual series/parallel in the updateBatteryInfo() function).
This updates the getBatteryPercent abstraction, so it can be easily combined with the coulomb-counting branch without requiring many integration changes.