Applications
Products
Software
Knowledge
Company
Engineers working with comemso battery cell simulators in a BMS test laboratory

Battery management systems

BMS testing: prove your BMS handles faults you can't create with real cells

BMS testing shows whether a battery management system measures its cells correctly, balances them and reacts to faults in time. The Battery Cell Simulator replaces the battery with controlled cell and sensor signals. You create and repeat normal, boundary and fault conditions for EVs, energy storage, robots and drones – without building and abusing real battery packs.1

204 simulated cells, no new tool chain: BMS testing inside an existing CANoe setup.

Cell monitoringVoltage, temperature, balancing and sensor signals
Safety functionsDeep discharge, overcharge, overheating and electrical faults
Controlled faultsControlled fault combinations without real cells
Repeatable automationThe same scenario for every software release
In 30 seconds
What for
Teams that must show their BMS detects and handles faults – in EVs, energy storage, robots and drones.
What it does
Simulated cells and sensors repeat normal, boundary and fault conditions; published project: 204 simulated cells inside an existing CANoe setup.
Not for
Electrochemical characterisation of cells or packs.

A BMS that misses an unsafe cell state in the field turns a software bug into a safety incident.

Your path to BMS testing

Choose the setup for your BMS test

It starts with the application and a relevant project configuration; then we agree the technical requirements for your own setup.

1 · Suitable systemBattery Cell SimulatorYou configure cell, sensor and fault conditions around the real BMS under test.View the system →
2 · Project examples24-cell hybrid-BMS setupDocumented project with 24 cell channels, NTC/PTC temperature simulation and a Fault Simulation Unit.View the project setup →
3 · Next stepThe BMS test setupShare the BMS, channel count, sensor signals, fault cases and required integration for your project.Discuss the test task →

From the demo to your first test:

  1. 15-minute demo. An engineer shows your BMS test case on a real Battery Cell Simulator.
  2. Written quotation. Cell channels, sensor and fault simulation and integration for your task – then you order.
  3. Delivery and start. Commissioning and training are agreed in the quotation.

Cells and controller

The cells store energy. The BMS monitors and protects them.

  • Monitor cell conditionsThe BMS monitors voltage at each series position, alongside temperature and other safety-relevant signals.
  • Protect the battery systemThe BMS detects unsafe conditions and triggers protective action against overcharge, deep discharge and overheating.
  • Simulate cells and sensorsThe test system emulates cell voltages and sensor signals, allowing you to test BMS responses without real battery cells.
  • Automate repeatable testsApply supported operating states and fault combinations with defined, repeatable inputs to validate BMS behaviour.
Matched systemsBattery Cell Simulator · BMS HiL integration · optional comframe
Published proofTexas Instruments, Aalborg University and Skeleton Technologies.

Test matrix

What BMS testing checks – area by area

Eleven test areas cover what a BMS must do in operation: first measure and estimate, then protect. For each one, the tables show what the test proves, what the Battery Cell Simulator supplies or measures and which fault makes the test meaningful.

Measure, estimate, balance
Test areaWhat the test showsWhat the simulator supplies or measuresExample fault
Cell voltage measurementThe BMS reads its cell voltages within the specified accuracy.Cell voltage per channel, 0.1 to 8 VCalibration issue; open sense wire on one cell
Pack voltage measurementThe pack voltage the BMS measures matches the sum of its cells.Series-connected cell voltages, up to 1,500 V1Sum of the cell voltages differs from the measured pack voltage
Current measurementThe BMS measures the pack current correctly – the basis for SoC and protection.Current-sensor and shunt emulation1Sensor offset or wrong scaling
SoC and SoH estimationThe state estimate follows the simulated battery state.Cell voltages from a battery model or an SoC curve, with the current signalAged or imbalanced cells
BalancingThe BMS balances the right cells at the right time.Cell voltages with controlled imbalance; source and sink currentOne cell drifts away from the others
Quiescent and leakage currentThe BMS goes to sleep correctly and does not drain the cells – for example while you are on holiday.Quiescent and leakage current, measured per cell channelThe BMS stays awake and discharges the cells
Protect and detect faults
Test areaWhat the test showsWhat the simulator supplies or measuresExample fault
Protection: voltage, temperature, currentThe BMS triggers its protective response at the threshold and in time.Threshold ramps on the cell voltage; NTC/PTC temperature signals1; current signal1Overcharge, deep discharge, overheating
Wire break and short circuitThe BMS detects the fault, reports it and reaches a safe state.Fault simulation on the cell cascade, the BMS sense lines and the temperature sensors: wire break and short circuit; polarity reversal on cell channelsBroken sense line; shorted temperature sensor
Insulation monitoringThe BMS detects a falling insulation resistance.Insulation-resistance simulation1Insulation fault to chassis
Communication and diagnosticsThe BMS reports a fault and keeps its communication stable.Faults on communication channels1Broken CMC or CSC chain
State machine: pre-charge and contactorsThe BMS runs pre-charge and switches its contactors in the right order.Cell and sensor states that trigger each step; contactors and pre-charge circuit come from the HiL benchUndervoltage during pre-charge

Application-specific priorities

Match BMS tests to the battery application

Shared BMS functions come first; operating profiles, interfaces and safe-state behaviour of the final application follow.

Electric vehicle battery management
Electric mobility EV BMS testing for vehicle manufacturers and suppliers

Cell and sensor behaviour combine with high-voltage control, fast charging, regenerative braking, thermal management, isolation, contactors and vehicle communication.

  • Dynamic current and temperature profiles
  • CMC or CSC chain faults and sensor plausibility
  • Coordination with VCU, OBC and EVCC
Battery monitoring semiconductor development
Semiconductors BMS IC and AFE testing for chip manufacturers

Characterize analog front ends and monitoring ICs before integrating a complete battery pack. Faults in conversion, diagnostics and communication carry into later designs. With simulated cells you find them before a battery pack exists.

  • Linearity, channel matching, noise and timing
  • Open-wire and communication-chain diagnostics
  • Regression across devices, lots and temperature
Stationary battery energy storage
Stationary storage BESS BMS testing for energy storage manufacturers

Address long service life, rack and cluster structures, standby behaviour, parallel strings, module replacement and flat-voltage chemistries.

  • Drift, imbalance and self-discharge
  • Rack communication, isolation and contactors
  • Ageing distributions, service states and recovery
Battery-powered mobile robot
Mobile robotics BMS testing for AMRs, service robots and humanoid robots

Shows how the BMS handles high actuator peaks, regenerative load changes and frequent docking. Account for compact batteries, limited cooling space and the safe states required during critical motion.

  • Voltage sag and power-limit decisions
  • Thermal and communication faults in motion
  • Controlled derating, stop and dock behaviour
Battery-powered multicopter
Flight batteries BMS testing for octocopters, drones and UAVs

Shows how the BMS distinguishes a transient voltage sag from an unsafe battery state. Verifies the remaining-power information under high discharge and rapidly changing loads.

  • Cold, aged or imbalanced cells
  • Emergency return or landing signals
  • Vibration, temperature and wiring faults
Conceptual BMS research laboratory with simulation equipment and measurement displays
Research and validation BMS testing for research institutes and laboratories

Configurable models, open interfaces and repeatable electrical conditions support new cell chemistries, estimation algorithms, balancing concepts and safety strategies.

  • Parameter sweeps and algorithm comparison
  • Open-loop and closed-loop HiL
  • Traceable datasets and rapid reconfiguration
Further application fields E-aviation, marine propulsion, rail, off-highway machines, UPS, data centers, medical devices, power tools and industrial equipment.

Anonymized project examples

BMS validation and production testing in customer projects

You can compare published BMS configurations with 120 simulated cells in February 2025, 204 cell channels in September 2024 and 72 cells in December 2024. Each article describes the documented project configuration.

Long-duration BMS validation

Over 2 months and thousands of test hours

A Tier 1 BMS development HIL setup integrated 240 simulated cells and 16 temperature channels to enable continuous start-stop cycles, rest periods, and fault-injection scenarios.

Environmental robustness of an 800V BMS

240 simulated cells · 28 temperature channels

An OEM test architecture combined 240 simulated cells and 28 temperature channels with a climate chamber. This allowed environmental stress testing of the BMS without exposing real cells to the same conditions or risks.

End-of-line testing for series-produced CMCs

5 production lines · 216 cells per production line

Five Battery Cell Simulator systems were integrated into five automated end-of-line stations for functional validation and automated fault diagnosis in series production.

Battery Cell Simulator integration with MATLAB models for research and algorithm development

Direct model integration for scalable cell simulation

A university research team integrated its own battery models directly into a 36-cell simulation system, scalable to 48 cells for repeatable algorithm development and validation.

Battery Cell Simulator integration with simplified battery models and SoC curves

New in comframe Release 1.6.0

With comframe Release 1.6.0, you configure a simplified battery model for the Battery Cell Simulator in the user interface, including SoC curves. An example SoC curve is preset as the default value. Available from early November 2026.

Read the release news

Compact BMS development with integrated cell simulation

24 simulated cells · 8 temperature channels

A supplier replaced a power-supply-based test setup with an integrated Battery Cell Simulator. The system combined 24 simulated cell channels and 8 temperature channels for automated cell, sensor and fault simulation.

BMS-controller validation in practice

“At TI, we know having the right tools and support makes innovation possible. Our broad portfolio of devices for battery management systems coupled with comemso’s proven results and accuracy with their battery cell simulator helps accelerate design time. comemso offers the ability to test and measure your system on a cell level with high precision.”

Mark NgGeneral Manager for HEV/EV Powertrain, Texas Instruments

“Outstanding technical knowledge of comemso and customer application. High product quality and suitable for research.”

Prof. Dr. Remus TeodorescuAalborg University Denmark

“The flexible simulation of real-world battery conditions with the comemso BCS allows us to automatically test different real-life scenarios from our customers of grid, automotive, and transportation area and identify & eliminate safety-critical factors to improve performance at an early stage.”

Keijo LassSoftware Engineering Manager, Skeleton Technologies

How to test a BMS

  1. Define the controller requirement and expected response.
  2. Select cell, sensor and supported fault inputs with the necessary range and load conditions.
  3. Match the Battery Cell Simulator modules, device under test (DUT) supply, fixture/interlocks and automation interface.
  4. Apply the defined stimulus and capture the actual controller output.
  5. Compare observation against the pre-agreed threshold, timing and recovery conditions.
  6. Save the configuration, versions, run identity, data and interpretation.

For BMS HIL (hardware-in-the-loop) integration, distinguish the electrical simulator from the wider HIL environment. Confirm supported control interfaces and external components.

BMS test methods: stimulation, automation, HiL and faults

Test methods

Direct stimulation, automation, models and faults follow the BMS response you need to evaluate.

Open-loop stimulation

Deterministic cell and sensor values test measurement accuracy, thresholds, I/O and basic protection logic.

Automated scenarios

Repeatable sequences cover boundary sweeps, regression, software releases and configuration variants.

Closed-loop HiL

Let a battery model react to BMS commands, load profiles and thermal conditions for dynamic algorithm validation.

Fault insertion

Controlled electrical, sensor and communication faults. Detection, reaction timing and recovery, measured.

Environmental and endurance

Signal simulation combines with climate chambers, power cycling and long-duration operation.

Production and EOL

Development test records lead to fast, traceable checks for manufacturing and final inspection.

Test levels

Where the Battery Cell Simulator fits: MiL, SiL, HiL and production

BMS testing runs on several levels. Models come first, real hardware later. The Battery Cell Simulator starts where the real BMS controller enters the test.

Test levelWhat runsWhat it showsBattery Cell Simulator
MiL – model in the loopBMS algorithm and battery as modelsAlgorithm logic, early in the projectNot involved yet; your battery models can later drive the simulator
SiL – software in the loopCompiled BMS software, battery as a modelBehaviour of the real code on a PCNot involved yet
Bench test – open loopReal BMS hardware with fixed cell and sensor valuesMeasurement accuracy, thresholds, inputs and outputsSupplies the cell and sensor signals
HiL – hardware in the loopReal BMS, simulated cells and sensors, real-time modelTiming, protection, faults and recovery on the real controllerCore use: cell voltages, sensors and faults at the BMS connector
Production and EOLEvery series unitFunction and wiring of each unit, with traceable resultsIn use – for example in five EOL stations with 216 cells each

Free BMS testing whitepaper

Planning BMS temperature tests?

The whitepaper helps plan BMS temperature-validation scenarios: cold starts, heat exposure, climate-chamber connections and the cell and sensor stimuli required.

Engineer opens a climate chamber with a battery management board inside, connected to a comemso test system rack; she holds a step profile on her clipboard.
Explore the BMS testing whitepaper

Frequently asked questions

BMS testing FAQ

How do you test a BMS?

You connect the real BMS to simulated cells and sensors and set a stable normal state. Then you change one condition at a time – a cell voltage, a temperature, a fault – and compare the response with the requirement. The same sequence runs again after each software change.

BMS testing with real cells or with a cell simulator?

Both have their place. Real cells are needed when you characterise chemistry, capacity and ageing. For the controller test, a cell simulator is the better tool. It sets each cell voltage directly, injects wire breaks, shorts and polarity reversal without damaging cells and repeats a case exactly.

What is the difference between a BMS tester and BMS HiL testing?

A BMS tester such as the Battery Cell Simulator supplies the electrical cell and sensor signals at the BMS connector. BMS HiL testing is the complete method. A real-time computer runs a battery model, drives the BMS tester and evaluates the BMS response in a closed loop. The BMS tester is one part of the HiL bench and also works on its own for open-loop tests.

What is BMS testing?

BMS testing verifies the hardware and software functions that monitor, estimate, balance and protect a battery system. Apply normal operating conditions, limits, electrical faults and communication failures, then check the response and recovery.

How can a BMS be tested without a real battery?

A programmable cell and sensor simulator supplies the electrical inputs expected by the BMS. Engineers set cell voltages, temperatures, current signals and supported faults directly, without waiting for a physical pack to reach each state.

Which BMS functions should be validated?

Typical scope includes measurement, state estimation, balancing, contactor and pre-charge control, isolation monitoring, diagnostics, communication, wake and sleep behaviour, protection thresholds and recovery.

What is the difference between BMS testing and battery testing?

BMS testing validates the controller, algorithms, interfaces and protection decisions. Battery-cell testing characterises electrochemical cells or packs, including capacity, power, ageing and thermal behaviour. comemso focuses on the BMS controller and uses emulated cell signals; it does not characterise battery chemistry.

How do BMS manufacturers ensure the quality and safety of their products?

BMS manufacturers verify defined controller requirements with battery management system testing. They keep each requirement, test case, observed response and release decision linked in the test record.

Engineers apply controlled cell deviations, balancing conditions and supported sensor faults, then check the required protection response, diagnostics, communication and recovery.

Follow the BMS test procedure. Select the Battery Cell Simulator configuration.

How can BMS sleep behaviour and undervoltage response be tested together?

Define the permitted standby current, intended sleep state and required response to a cell undervoltage condition. Apply controlled cell and sensor signals, introduce a supported undervoltage condition and record current consumption, diagnostics and wake/sleep behaviour.

Compare the result with the controller requirement and repeat the test after software or hardware changes. That application requirement defines whether the BMS should remain awake or return to sleep.

More on this topic

Practical examples and further reading

Customer projects, success stories and technical articles related to this page.

BMS testing with a defined simulation boundary

BMS testing starts with defined inputs and expected responses. The BMS tester provides the selected cell boundary. BMS simulation adds a battery model, automation and BMS feedback to that electrical stimulation. The record shows which values came from the model, which physical outputs were measured and which decision the BMS made.

A battery cell simulator replaces the real cell connections. For a traceable fault test, change one condition at a time and repeat the same sequence after the correction. The BMS test record must also identify connection, contact and enable failures in the setup. Then an invalid measurement is not reported as a DUT failure.

BMS-controller test planning

Plan BMS validation

It starts with the battery architecture, operating scenarios and required monitoring, balancing and protective responses.

Technical updates from comemso

Choose your newsletter topics

Receive product and software updates, practical testing insights and invitations to comemso events.

Choose my newsletter topics

Choose your topics, then confirm your subscription by email. Unsubscribe at any time.

¹ Scope

Channel count, voltage and current ranges, sensor signals and fault types depend on the Battery Cell Simulator configuration and the software release. Integration into your HiL or test bench – including the safety concept and automatic stop behaviour – is defined in the project. The quotation confirms the scope.

  • Available fault channels, communication capture and automation depend on the selected configuration.
  • Testing these controller reactions does not establish cell chemistry or whole-pack performance.
  • A clear diagnostic status is one prerequisite for credible evidence; it does not prove every aspect of a test valid.