BQ76952 targets 3 to 16 series lithium-ion, lithium-polymer, and lithium-iron-phosphate packs, integrating voltage, current, temperature, and protection functions. Chip functions are not a complete battery-system design; cells, power switches, fuses, harnesses, chargers, and thermal management still require joint definition. For abnormal cell voltage, check series-count mapping, wiring, and configuration before diagnosing measurement-chain faults.
Map cell nodes to lines sequentially
For every sense wire, list the cell node, connector pin, PCB net, input filter, and IC pin, highlighting unused-channel handling. Below 16 series cells, do not arbitrarily short sense inputs; follow applicable manual connections and enabled-channel configuration. Connector orientation and wire colors are aids, not substitutes for continuity checks.
| Mapped Field | Design Input | Verification Output |
|---|---|---|
| Cell Count and Battery Cells | Chemical system, number of strings, and operating range | Enable channel and node sequence |
| Sampling line | Connector, filter, and cable length | Line-by-line correspondence, open circuit, and reverse connection risks |
| Current | Shunt location, resistance, and polarity | Charge/discharge direction and engineering unit conversion |
| Temperature | Thermal components, voltage dividers, and mounting positions | All input functions and fault states |
On initial boards, use controlled cell simulators or approved low-energy arrangements to check channels, not actual high-energy packs as wiring tools. Change one simulated cell voltage at a time, confirm the matching software channel responds without erroneous changes elsewhere, then check total voltage against the cell-voltage sum.
Verify shunts and temperature inputs independently
The manual specifies ±200 mV current-measurement range across the shunt, but resistance still depends on range, dissipation, pulses, and error budgets. At an assumed 20 A and 2 mΩ, drop is 40 mV and DC dissipation 0.8 W. This is not a recommended battery-protection setting. Check charge/discharge direction, Kelvin sensing, and software sign together to avoid reversed accumulated-charge direction.
Bind temperature channels to thermistor curves, bias networks, and mounting positions. Cell surfaces, power MOSFETs, and ambient temperature serve different purposes; one point cannot replace all. Define handling of open, shorted, and out-of-range readings so extreme values from disconnected sensors are not treated as real temperatures in control.
Thresholds, delays, and recovery form complete protection rules
Protection parameters should follow cell limits, charge/discharge needs, power devices, and system safety design, not generic article voltages or temperatures. For each item, record trigger threshold, delay, detection conditions, switching action, recovery threshold/wait conditions, and host involvement. Startup inrush and sustained overcurrent have different response tasks requiring separate review.
Distinguish autonomous IC protection, MCU decisions, and external fuses/contactors. Reading a fault does not establish interruption of the power path. Verify drive outputs, MOSFET gate-source voltage, actual charge/discharge current, and recovery. Use approved energy-limited arrangements/procedures for fault tests, especially checking whether repeated retries create new thermal stress.
Balancing changes measurement and local temperature
Balancing addresses cell-state differences; bypass current does not replace charging management. Check internal/external balancing methods, allowed combinations, sampling timing, dissipation, and neighboring-component temperature rise. Software balance-enable indications do not establish expected current; verify resistor drops, temperatures, and status reads together.
If a cell reading changes only during balancing, compare filtering/sampling timing, node connections, and balancing paths. If adjacent channels fail together, check common wires and returns. Retain balancing-on/off comparisons rather than first changing calibration coefficients to conceal state-dependent offsets.
The configuration package must support complete board readback
Released configurations should include full part numbers, data-memory parameters, enabled protections, channel mappings, temperature-input functions, balancing strategies, and current calibration. Retain revisions, checksums, and readback results, identifying volatile/nonvolatile destinations. Host-interface screenshots alone cannot establish actual shipped-board parameters.
Power-mode transitions also require communication/measurement recovery verification. Sleep, shutdown, wake, and reset can affect data validity and cached state. Firmware should reconfirm actual modes/configurations rather than retain pre-reset assumptions. Save command results, supply sequences, and first-valid-sample times.
Verify measurement before verifying protection action
| project | Controlled Input | Output Record |
|---|---|---|
| Sectional Measurement | Simulate voltage per channel with independent reference | Channel mapping, error, and total voltage |
| Current Direction | Controlled bidirectional shunt signals | Symbols, scale, and integration direction |
| Open Circuit and Temperature Fault | Disconnect or simulate sensor per design | Identification, status, action, and recovery |
| Protection chain | Approved threshold crossings and durations | Timing from trigger to switch action |
| Balancing | Fixed input versus enabled state | Current, temperature, and reading changes |
Production parameter releases need input/output verification
After engineering configuration approval, create release packages by board revision and cell chemistry. Include readable parameter tables, programming files, checksums, programming steps, and readback comparisons. Identify values derived from cell specifications, power-device limits, and system strategies. Unexplained configuration files prevent service and purchasing teams from assessing applicability.
Read back and compare every field after first-article programming, then verify measurements/protection. Include preprogrammed differences, ordering options, and host-tool defaults in material/configuration checks. When different software versions write identical parameters, verify units, scaling, and field meanings; identical displays may conceal different underlying contents.
Recheck configuration impacts after changing input filters, shunts, or balancing resistors. Approve hardware BOMs and software parameters together; higher balancing currents or different shunts cannot change only in assembly tables. Temperature-sensor substitutions also require updated curves and mounting locations, not merely similar room-temperature readings.
Protection verification should record the full timing chain from out-of-range input through device state and drive changes to actual current interruption, then verify expected recovery. Software alarms, hardware shutdown, and mechanical actuators may occur sequentially. A host fault icon alone cannot establish interrupted energy paths.
For shipping, long storage, or service modes, confirm sleep, shutdown, and wake paths, including recovery from external chargers or buttons. Low-quiescent-current measurements should cover the entire board, including dividers, communication, LEDs, and isolated supplies. IC sleep current is not pack standby consumption.
Trace all fault-test inputs, energy limits, and recovery methods. Conditions untested on real packs remain uncovered. Final documents describe verified combinations; the number of IC protection functions is not the battery system's safety rating.
Can default device parameters go directly into production?
Defaults do not establish suitability for any cell or pack; they describe initial device state. Generate and verify configurations against system requirements. Acceptance outputs include wiring tables, readback configurations, calibration data, fault-injection/recovery records, and covered series counts, board revisions, and actuators. Chip feature lists cannot replace system-protection evidence.
Exception channels must retain original values and status
For sudden cell-voltage changes, log all cell voltages, total voltage, current, temperature, balancing state, and power mode together. Recording only the triggering channel misses common-wire/configuration issues. Smoothed software values may hide open-wire transients, so timestamp raw data and status together.
Beyond triggering protection, check states after clearing conditions, reconnecting chargers, and power cycling. Different recovery paths may require different strategies; parameter tables and actual outputs must agree. Unverified cells, series counts, or power-board combinations cannot inherit existing passes. Reconfirm according to change impacts.
Source material and applicable scope
- Texas Instruments, “BQ76952 3-Series to 16-Series High Accuracy Battery Monitor and Protector”; version Rev. B; checked 2026-10-17; relevant sections: Cell Voltage Measurement, Current Measurement, Protection, Cell Balancing, Power Modes, Application, Layout. Supports device monitoring/protection and connection methods; cells and system requirements determine thresholds.
