A Hardware-Oriented Design Approach for Light Electric Vehicles: Onboard State-of-Charge Estimation
Bibliographic record
Abstract
The development of a battery management system (BMS) necessitates the collaboration of multiple engineering disciplines to create a customized solution. To optimize power and energy density at the pack level, the BMS must be seamlessly integrated, occupying minimal space in the overall assembly. This becomes particularly crucial for light electric vehicles (EVs) with limited space compared to passenger cars. Electronic hardware design is influenced by mechanical assembly, requiring careful component and sensor selection for optimal firmware performance. However, the literature often introduces algorithm solutions without proper validation on embedded processors, compromising accuracy for real applications. While selecting a lower-cost microcontroller may reduce retail expenses, it can impact firmware performance. This article explores the key aspects of BMS design and validation, emphasizing that comprehensive system awareness is essential for certain design decisions. It underscores the significance of validating algorithms for the battery state, crucial for effective lithium-ion battery (LiB) utilization, cautioning against compromising these algorithms for cost reduction. It includes a validation cycle case study to highlight the benefits of early validation in the process.
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.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
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".