POWER & BATTERY MANAGEMENT
BMS SOC and SOH Estimation: What Industrial OEMs Should Verify
A battery management system’s state of charge (SOC) and state of health (SOH) are estimates, not measurements directly available from a single pack-voltage reading. BMS SOC estimation depends on the selected cells, measured current and voltage, temperature, starting state and the algorithm that interprets these inputs. Before asking a supplier for “accurate SOC,” an OEM should define which values are required, which device computes them, under what operating profile, and how error will be tested. Do not assume a BMS with a communication port automatically reports a verified SOC or SOH value.
What is the difference between SOC and SOH?
SOC describes an estimate of the charge currently available relative to an agreed capacity reference and operating window—roughly “how full is the usable battery now?” SOH describes an aging-related condition relative to a defined new-battery reference, such as available capacity under specified conditions. Neither term is a universal scalar unless its definition and test conditions are documented. A machine’s displayed runtime is yet another estimate: load profile and usable-power limits matter.
Analog Devices’ technical review describes SOC/SOH methods and the roles of current, cell voltage, temperature and initial state. Its algorithms and simulation outcomes are specific to that paper and must not be used as VOLUXIN accuracy claims. Texas Instruments’ battery-gauging fundamentals also distinguishes protectors, cell monitors and fuel gauges. That distinction matters when comparing catalogues: a board can offer protection and communication yet still require a separate, confirmed estimator to meet an OEM’s display requirement.
Why can a voltage reading mislead BMS SOC estimation?
A terminal voltage is affected by load current, temperature, cell history and relaxation. An open-circuit-voltage mapping requires conditions appropriate to the actual chemistry and cells; a machine that is always working or charging may not provide a useful rest interval. The VOLUXIN BMS balancing guide already notes that voltage alone does not always identify an SOC difference and that lithium iron phosphate may have a relatively flat voltage curve across much of its SOC range. This article therefore focuses on estimator requirements and validation, not cell-balancing methods.
Coulomb counting integrates measured current over time. It can follow changes during operation, but inaccurate initial SOC, sensor offset, missed current paths and changes in usable capacity introduce drift. Model-based methods may use additional measurements and corrections, but their validity depends on the exact pack characterization and implementation. The responsible designer should specify what information is actually available from the proposed BMS before promising a gauge algorithm or an accuracy figure.
Request an SOC and SOH data contract
| Question for the supplier and integrator | Why it changes the answer | Evidence to request |
|---|---|---|
| Is SOC or SOH calculated, transmitted, stored or not supported? | Protection, monitoring and gauging are not interchangeable. | Function list and communication-map revision for the exact configuration. |
| What is the SOC denominator and allowed operating window? | A display percentage depends on the usable-capacity definition. | Cell/pack capacity reference, cutoff policy and declared calculation definition. |
| How are current and temperature measured? | Offset, sensor position and unmeasured paths affect estimates. | Sense-path diagram, sensor details and calibration/test plan. |
| How is initial state established or corrected? | Starting error can persist during coulomb counting. | Start-up/rest/full-charge correction logic, if present. |
| What is meant by SOH? | Capacity, power capability and resistance describe different aspects of aging. | SOH definition, measurement procedure and reference conditions. |
| Which device owns the number shown to the driver? | BMS, vehicle controller, charger and display may each transform data. | Message-map units, update period, validity flag and timeout behaviour. |
| What happens on a fault or data loss? | A stale but plausible percentage can mislead operations. | Diagnostic state and display/controller fallback test. |
| How is accuracy accepted? | An unqualified single percentage is not a reproducible promise. | Test matrix across representative loads, temperatures, age states and cell batches. |
The table is a procurement question list, not a representation that every VOLUXIN model offers an SOC or SOH output. The VOLUXIN BMS hub explicitly asks customers to confirm chemistry, series mapping, current paths and communication for the exact configuration. The BA48-MNS11 AGV model page lists 13S or 15S as discrete options and CAN/485 (isolated), protocol and option to confirm; it does not prove a particular SOC/SOH algorithm, numeric accuracy or message map.
How should an OEM validate BMS SOC estimation?
First agree the pack hardware revision, cell chemistry and cell manufacturer’s limits. Then establish an appropriate, qualified reference method for charge and discharge under representative equipment duty. Log cell/pack voltage, pack current, relevant temperatures, calculated SOC, charger state, fault/status flags and time synchronization. Compare the estimator’s trajectory and end-of-run behaviour with a documented reference, not with a single screenshot from a fully rested pack. Obtain cell supplier input and qualified engineering oversight for hazardous or endurance tests.
Test varied states: start after rest, repeated short work cycles, a longer run, charging, cold or warm conditions within the pack’s approved limits, and intermittent communication. Record every assumption. A pack never cycled deeply or allowed to rest may provide fewer correction opportunities; the algorithm’s error and usable-capacity model must be evaluated under the actual usage pattern. ADI’s analysis discusses these input and initialization limits; its reported experimental errors are not transferable to a VOLUXIN catalogue item.
Most importantly, separate a display function from protection. A working battery percentage does not establish that cell overvoltage, overtemperature or overcurrent protections have been accepted. For fault and restart questions, refer to the BMS selection guide and the configuration-specific safety plan. To discuss available model outputs and protocols, use VOLUXIN engineering support.
Frequently asked questions
Can a BMS determine SOC from pack voltage alone?
Sometimes voltage can inform an estimate under defined conditions, but load, temperature, cell chemistry and rest time change the relationship. Ask for the method and validation over the intended duty cycle.
Does SOC of 100% guarantee the original energy capacity?
No. SOC refers to a chosen present operating range; aging and temperature can change usable capacity. Request a defined SOH/capacity measurement if the OEM needs aging information.
Is SOH a single standardized percentage?
Do not assume so. Ask whether it represents capacity, power capability or another defined metric, and under what reference conditions it was obtained.
Will a CAN-enabled BMS automatically transmit SOC and SOH?
No. An electrical interface does not specify the data fields, calculation availability or message validity. Request a configuration-specific function list and message map.
Can a cell-balancing feature fix an inaccurate SOC estimate?
Not by itself. Balancing addresses cell differences; estimate quality also depends on input measurements, initialization, current integration, cell model and verification.
What proof should an OEM request before showing runtime on a vehicle display?
Ask for the exact output definition and units, reference-test procedure, results over representative loads and temperatures, update/timeout behaviour and responsibility for the final displayed value.
Technical references and project enquiry
- Analog Devices, A Closer Look at State of Charge and State of Health Estimation Techniques for Batteries — algorithm assumptions and validation; third-party examples, not VOLUXIN performance data.
- Texas Instruments, Battery Gauging Fundamentals — sensing, coulomb counting, fuel-gauge limits and protector/monitor/gauge distinctions; manufacturer-specific training examples.
- Analog Devices, Maximizing Cell Monitoring Accuracy and Data Integrity in Energy Storage BMS — measurement integrity and correlated inputs in a different system.
- VOLUXIN BMS catalogue and cell-balancing guide — public company references used to limit catalogue claims and avoid duplicate coverage.
Need a charge display or aging estimate in your equipment? Send the cell data, work/charge profile, required controller fields and acceptance conditions through VOLUXIN’s BMS enquiry. If a function or performance target is not documented for the proposed configuration, mark it as an engineering question rather than a promised feature.
Tell us what your equipment needs.
Share your application, product requirements and any details you have already confirmed. We can then discuss the available options.
Discuss Your Requirements
