CONTROL AUTHORITY

BCU and BMU: split the system by who is allowed to act, not by where the boards sit

Both controllers measure. Only one of them decides. Drawing the line at authority rather than at hardware is what exposes the functions a design has quietly left to nobody.

Measurement is shared; authority is not

Describing the BMU as the one that measures and the BCU as the one that controls is close enough to be misleading. A module controller measures and also acts, because it runs balancing on its own cells. The distinction that matters is narrower: which device is permitted to open the contactors and stop the system.

In a conventional cluster architecture that authority belongs to the master alone, and every module controller can do no more than report a condition and wait. That single rule determines the whole safety argument, so it should be the first thing established when reading an unfamiliar architecture.

For what the term itself covers across vendors, and how to count units from an I/O list, see the BMU reference note.

Four functions that cannot be delegated downward

FunctionWhy it belongs to the masterWhat goes wrong when it is assumed
Contactor and precharge sequencingClosing onto a DC bus requires knowledge of the whole string and of the load side, which no module controller has.Nothing in the bill of materials actually commands the contactors, and it surfaces during commissioning.
Current measurementThere is one current through a series string, and it needs one authoritative sensor rather than several inferred values.Two devices disagree about current and the charge and discharge limits become unreliable.
State of charge and healthCoulomb counting needs the string current, and pack state needs the weakest cell across every module.Per-module estimates that cannot be combined, and a pack that reports a state no single number supports.
Insulation monitoringIsolation resistance is a property of the whole high-voltage system against the chassis, not of any one module.It is missing entirely, because each module controller reasonably assumed something above it was doing it.

How the JKESS high-voltage hardware maps onto this

The listing separates a BCU-B3 master control box from BMU-H5-16 slave control boxes. Each slave covers 9 to 16 series cell-voltage channels with eight temperature channels and 2A bidirectional active balancing. The master carries total-voltage and current measurement, insulation, interlock, SOC, SOH and SOP estimation, and the CAN and RS485 interfaces outward.

Read that split against the table above and the boundary is clear: everything in the right-hand column sits in the master, and the slaves hold only what has to be physically close to the cells. Order options include 100A and 200A master or slave control boxes, and those labels describe the selected box rather than the system it lands in.

The High Voltage Kit product page carries the supplied scope. The listing sells the control boxes selected; it is not a battery pack, a rack, a contactor cabinet, a PCS, an EMS, or a commissioned system.

Decide what happens when the link drops

A modular BMS has at least three links that can fail independently, and each one needs a defined response written down before commissioning rather than discovered during it.

  • A module controller stops reporting: does the master derate, open, or hold with an alarm, and after how long
  • The master stops reporting to the PCS: does the PCS fall back to its own limits, or stop
  • The master stops reporting to the EMS: does the site controller continue on last-known values, and for how long
  • The interlock loop opens while current is flowing: is that an immediate open or a controlled ramp down
  • Communication returns after a fault: does the system re-close automatically or require an operator

The last one causes more site disputes than the rest combined, because automatic re-closure and manual reset are both defensible and the two parties often each assumed the other.

Rate the control box against the path, not the label

A 100A or 200A label describes the box. The current the system can actually carry is set by the weakest element in the whole path: busbars, cables, lugs, the fuse, the contactor rating at the operating voltage, the current sensor range, and the temperature the enclosure allows all of it to reach.

For a bidirectional system, confirm charge and discharge separately and confirm how long a peak lasts. A rating that holds for a few seconds and one that holds continuously are different numbers, and a PCS running a peak-shaving duty will ask for the second.

Three communication links, defined separately

The kit lists CAN, RS485 and isoSPI-related functions, and those serve different links. The slave-to-master chain is an internal, isolated bus constrained by stack voltage and cable run. The master-to-PCS link carries limits that the PCS must act on. The master-to-EMS link carries telemetry and schedules. A service or monitoring interface is a fourth.

Specify each one on its own: protocol and revision, bitrate, addressing, termination points, and which end is master. The CAN and RS485 note covers why a shared bus name is not a shared message dictionary.

What a configuration review needs from you

  • Chemistry, total series count, and how it divides into modules
  • Nominal and maximum pack voltage, and the number of parallel clusters
  • Continuous and peak current, with peak duration, in both directions
  • PCS brand, model, power and the protocol it expects from a battery
  • Where the contactors, fuse and current sensor sit, and what commands them
  • Insulation monitoring and interlock loop requirements for the site
  • Rack arrangement, cable runs between modules, and the thermal environment
  • Quantity, destination and the schedule the project is working to

Settle the authority split before ordering boxes

Send the topology, the current path and the protocol requirements, and the gaps show up on paper rather than on site.

ENGINEERING NOTES

Settle the decision, then pick the part

Each note works through one decision end to end. Where a note and a product page disagree, the product page and the written quotation are the ones that bind.
SOURCE CHECKS

Check a JKBMS source

Check a JKBMS listing against what a reseller cannot restate: the four segments of the model code, the version the board reports itself, the visible port set, and a quotation that names its own exclusions.

Read guide
NAME TO PART

From brand name to part

All four spellings return the same hardware, so none of them narrows anything. This maps the term you searched to the artefact you were actually after: a model code, a manual, a firmware note or a cable.

Read guide
ORDERING

How ordering works

Two order paths run on this catalog. Work out which one a product uses, what shipping costs to your destination, which currency you will be charged in, and what has to be fixed before payment.

Read guide
ENCLOSURE DOCS

Battery box documents

Find the JKESS enclosure document that matches the format you were shipped, and work out the four cell measurements an enclosure manual assumes you already checked.

Read guide
PEAK SHAVING

Sizing peak shaving

Work peak shaving out of interval data: find the billing demand window, measure the energy above the threshold, size kW and kWh separately, and stop the recharge from setting the next peak.

Read guide
THERMAL

Air or liquid cooling

Estimate what a battery cabinet actually has to reject, judge the design on cell-to-cell temperature spread rather than average temperature, and price in what each cooling system costs to keep working.

Read guide
BMS ARCHITECTURE

What a BMU is

BMU means different things in different datasheets. Establish what a specific controller does from its I/O list, count units from channels rather than from kWh, and find where the interlock loop really terminates.

Read guide
SOURCING

Comparing ESS quotes

Normalise C&I ESS quotations before comparing price: usable against nameplate energy, what the warranty actually measures, the line items that fall outside the scope, and who owns the integration boundary.

Read guide
APP AND BLUETOOTH

JKBMS app and Bluetooth

Connect the JKBMS app over Bluetooth, understand pairing behaviour and permissions, and work through the connection failures reported most often.

Read guide
RS485 AND CAN WIRING

JK BMS RS485 and CAN wiring

Identify the RS485 and CAN ports on a JK BMS, verify the pinout against the manual for your model, and avoid the wiring mistakes that damage a port.

Read guide
FIRMWARE AND PARAMETERS

JKBMS firmware and parameters

Understand how JKBMS firmware versions affect available parameters, what to record before changing settings, and how to avoid an unrecoverable configuration.

Read guide
FAMILY TABLE

BD, PB, B1A and B2A side by side

One table showing what each family is built around, so a shortlist takes a minute instead of a browse.

Read guide
ENCLOSURE FIT

Fitting cells into an enclosure kit

Measure the cells before shortlisting a box: stack length with compression, height over the terminals, mass and rack loading.

Read guide
BOARD SELECTION

Narrowing the catalog to one code

Work from the pack and the inverter rating down to a handful of codes instead of browsing the list.

Read guide
BD OR PB

Which family the project needs

Local monitoring or an inverter protocol link. That question decides the family before anything else does.

Read guide
BALANCE CURRENT

How much balancing a pack needs

Balance current is a rate. Match it to how fast the pack drifts and how much idle time it has to recover.

Read guide
BUS CHOICE

CAN or RS485 for the link

The device at the far end decides the bus. Confirm pinout, bitrate and protocol profile before buying a cable.

Read guide
HIGH-VOLTAGE

Where contactor authority sits

Split responsibilities between module slaves and the cluster master, and find what nothing in the design owns yet.

Read guide
PROJECT INPUTS

What to fix before requesting a cabinet quote

The decisions that have to be settled first, and the ones that can safely stay open until the design review.

Read guide