The word is not standardised
In most modular high-voltage architectures a BMU is the module-level slave: it sits on or near a battery module, measures the cells in front of it, and reports upward to a master. In other documents the same three letters describe a complete battery-management controller with contactor authority.
Both usages are in circulation and neither is wrong. That makes the term useless as a specification, which matters when a system diagram from one vendor is being read against a datasheet from another.
Five questions that pin down any controller
Whatever the datasheet calls it, the answers to these five questions tell you what the device is and what still has to be provided by something else.
- How many cell voltage taps does it have, and what series count does that support
- How many temperature channels, and are they placed on cells or on the board
- Which bus does it use upstream, and is it electrically isolated
- Does it switch anything -- contactors, precharge, a relay output -- or only measure
- Does the high-voltage interlock loop terminate here, or pass through to somewhere else
Count units from channels, never from kWh
The number of module-level controllers in a system follows from the series cell count divided by the taps per unit, then rounded up per physical module because a unit rarely spans a mechanical boundary. Temperature channels can force the count higher than the voltage taps alone would suggest.
Energy in kWh does not enter this calculation at all. Two systems with identical kWh can need very different unit counts depending on cell capacity, series arrangement and how the modules are split.
What the master above it owns
A cluster-level controller combines the readings from every slave and holds the decisions that need a whole-pack view: pack state of charge and health, charge and discharge current limits, contactor and precharge sequencing, main current measurement, insulation resistance monitoring, and the external protocol to the PCS or EMS.
Do not assume a module-level unit performs any of those. If a design needs insulation monitoring or contactor control and no device in the bill of materials explicitly provides it, it is missing rather than implied.
How many interlocks does a BMU have?
There is no universal number, and a datasheet figure quoted without a schematic is not an answer. In most architectures the interlock loop is a series circuit closed through every point that must be intact before the pack is allowed to energise, and it terminates at the controller that commands the contactors -- which is usually not the module-level unit.
Count the loop from the system drawing: service disconnect, enclosure doors, high-voltage connector position switches, the contactor box, emergency stop, and whatever the site adds. Then confirm what the system does when the loop opens under load and when the communication link is lost while the loop is intact, because those are different events with different correct responses.
The slave chain is a physical design constraint
The link between module controllers and the master constrains the mechanical layout more than most designs expect. Node addressing has to survive a module replacement, isolation has to hold across the full stack voltage, the bus needs termination at its physical ends, and the total cable run has a limit that a tall rack can reach.
CAN, RS485 and isolated daisy-chain links are not interchangeable just because all three carry data. Establish which one the architecture uses before laying out the enclosure.
Questions this raises most often
Battery Management Unit. In most modular high-voltage systems it is the module-level slave that measures local cells and temperatures, but some vendors use the term for a complete controller, so read the I/O list rather than the acronym.
Series cell count divided by voltage taps per unit, rounded up per physical module, and raised further if temperature channels demand it. Stored energy in kWh does not enter the calculation.
No. It is one controller inside a BMS. Pack state, current limits, contactor sequencing, insulation monitoring and the external protocol normally belong to the master above it.
There is no universal count. The interlock loop is a series circuit through every point that must be intact before energising, and it terminates at the controller that commands the contactors. Count it from the system schematic.
Take it to a part number
Ratings vary between codes that read almost the same, so settle the decision here and then confirm the figures on the product page for the exact code.