Development of a Fast Running Equivalent Circuit Model with Thermal Predictions for Battery Management Applications
Bibliographic record
Abstract
Equivalent circuit modelling (ECM) is a powerful tool to study the dynamic and non-linear characteristics of Li-ion cells and is widely used for the development of the battery management system (BMS) of electric vehicles. The dynamic parameters described by the ECM are used by the BMS to estimate the battery state of charge (SOC), which is crucial for efficient charging/discharging, range calculations, and the overall safe operation of electric vehicles. Typically, the ECM approach represents the dynamic characteristics of the battery in a mathematical form with a limited number of unknown parameters. Then, the parameters are calculated from voltage and current information of the lithium-ion cell obtained from controlled experiments. In the current work, a faster and simplified first-order resistance–capacitance (RC) equivalent circuit model was developed for a commercial cylindrical cell (LGM50 21700). An analytical solution was developed for the equivalent circuit model incorporating SOC and temperature-dependent RC parameters. The solution to the RC circuit model was derived using multiple expressions for different components like open circuit voltage (OCV), instantaneous resistance (R0), and diffusional parameters (R1 and C1) as a function of the SOC and operating temperature. The derived parameters were validated against the virtual HPPC test results of a validated physics-based electrochemical model for the voltage behavior. Using the developed RC circuit model, a polynomial expression is derived to estimate the temperature increase of the cell including both irreversible and reversible heat generation components. The temperature predicted by the proposed RC circuit model at different battery operating temperatures is in good agreement with the values obtained from the validated physics model. The developed method can find applications in (i) onboard energy management by the BMS and (ii) quicker evaluation of cell performance early in the product development cycle.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.002 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.005 | 0.003 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".