MétaCan
Menu
Back to cohort
Record W3152426643 · doi:10.1109/access.2021.3068776

Lithium-Ion Battery Pack Robust State of Charge Estimation, Cell Inconsistency, and Balancing: Review

2021· article· en· W3152426643 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueIEEE Access · 2021
Typearticle
Languageen
FieldEngineering
TopicAdvanced Battery Technologies Research
Canadian institutionsMcMaster University
Fundersnot available
KeywordsBattery packState of chargeBattery (electricity)Computer scienceEstimationReliability engineeringAutomotive engineeringPower (physics)Engineering

Abstract

fetched live from OpenAlex

Lithium-Ion battery packs are an essential component for electric vehicles (EVs). These packs are configured from hundreds of series and parallel connected cells to provide the necessary power and energy for the vehicle. An accurate, adaptable battery management system (BMS) is essential to monitor and control such a large number of cells. Series and parallel connected cells also experience different production and operational conditions, which makes it challenging for the BMS to ensure the safe operation of each individual cell. The main functions of the BMS include battery state estimation, cell balancing, thermal management, and fault diagnosis. Robust estimation of the state of charge (SOC) is crucial for providing the driver with an accurate indication of the remaining range. This paper presents the state of art of battery pack SOC estimation methods along with the impact of cell inconsistency on pack performance and SOC estimation. Cell balancing methods, which are necessary due to cell inconsistencies, are discussed as well. Four categories of pack SOC estimation methods are presented, including individual cell, lumped cell, reference cell, and mean cell and difference estimation methods. The SOC estimation methods are compared in terms of algorithm type, computational load, and engineering effort to help practitioners decide which method best fits their application.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.672
Threshold uncertainty score0.547

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

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.

Opus teacher head0.029
GPT teacher head0.290
Teacher spread0.261 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it