BQ7692006PWR
Product Specifications
BQ7692006PWR
Texas Instruments — Power Management & Signal Chain
Product Overview
The BQ7692006PWR from Texas Instruments is a power management / signal chain IC delivering high efficiency, precision regulation, and robust protection. Texas Instruments (TI) is a global leader in analog ICs, power management solutions, and embedded processors.
Superb Automation partners with leading brands including Qorvo, TI, ADI, XILINX, NVIDIA, Intel, ST, MACOM, Renesas, and Coilcraft to provide complete BOM and supply-chain solutions.
Key Features
- High-efficiency power conversion with low quiescent current
- Wide input voltage range with precision output regulation
- Integrated over-current, over-temperature, and short-circuit protection
- Small footprint packaging for space-constrained designs
- AEC-Q100 qualified options available for automotive applications
- Flexible sequencing and soft-start control
Key Specifications
| Input Voltage | V |
| Output Voltage | V |
| Output Current | A |
| Switching Frequency | kHz |
| Efficiency | % |
| Quiescent Current | µA |
| Topology | — |
| Package | — |
| Operating Temp | °C |
| Protection | — |
Applications
Request Quote — In Stock, 100% New & Original, Full Warranty
BQ7692006PWR: the 5S member of the BQ769x0 front end family
The BQ7692006PWR is an analogue front end for packs of three to five series cells, which is the 18 V class. It is the smallest member of a family that extends to 10 cells and 15 cells in wider packages, and all three share the same register set and the same host code, so a product line that spans an 18 V tool and a 48 V scooter can use one driver and one test script.
The part measures cell voltages, the voltage across the pack, the die temperature and up to three external thermistors, and it has a separate converter that counts charge through the sense resistor. The measurements are read by a host over I2C, and the part does not run a gauge model of its own. That is how the family is built: the front end measures and protects, and the host decides what the numbers mean.
Hardware protection for overcurrent in discharge, short circuit in discharge, overvoltage and undervoltage runs inside the part and does not wait for the host. A secondary protector fault input lets the pack also watch an independent device. The charge and discharge FETs are driven low side, and the balancing FETs are integrated.
Key data for the BQ7692006PWR
| Function | Battery monitoring analogue front end with hardware protection |
| Cell count | 3 to 5 series cells, 18 V class pack |
| Measurement | Cell voltage, pack current, die temperature, up to three 103AT thermistors |
| Converters | One converter for voltages and temperature, a separate one for pack current |
| Protection | Overcurrent in discharge, short circuit in discharge, overvoltage, undervoltage, secondary protector fault input |
| FET drive | Low side N channel charge and discharge drivers |
| Balancing | Integrated balancing FETs, controlled by the host |
| Interface | I2C, address 0x18 on this variant, alert output to the host |
| Regulator | 3.3 V regulator output for the host or a small load |
| Power modes | Normal operation with blocks switched off by the host, plus a ship mode for storage |
| Package | TSSOP, 20 pins |
| Ordering | BQ7692006PWR, 2000 pieces on a large tape and reel; BQ7692006PW, 70 pieces in a tube; both moisture level 2 with a one year floor life |
The variant suffix, and why it decides the build
The family ships several variants from one die, and the suffix sets the I2C address and the regulator voltage. This variant answers at 0x18 and regulates to 3.3 V; the base variant answers at 0x08 and regulates to 3.3 V; another answers at 0x08 and regulates to 2.5 V. Two packs on the same bus need two addresses, and that is the only reason the address variants exist.
A 2.5 V regulator variant is not a mistake in the catalogue, it is for a host that runs at 2.5 V and does not want a second converter. Fitting the wrong one does not damage anything, it simply leaves the host without a rail at the voltage it expects, and the fault shows up as a board that does not start rather than as a measurement error.
The variant also decides the CRC setting on some members. A pack that runs a CRC checked bus has to use the member that supports it, and the mismatch is caught at the first communication, which is the good news. The bad news is that a line that has been built with the wrong suffix will not discover it until the pack is assembled and tested.
The split between hardware protection and host policy
The comparators inside the part act on their own, with thresholds written at configuration time. They protect the cells against the conditions that damage a pack in milliseconds: a short across the terminals, a current beyond what the FETs can carry, a cell that runs above its limit. Nothing in that path involves the host, which is why the pack is still safe when the host is hung.
Everything slower is host policy. Balancing, state of charge, charge termination, the decision to allow a charge at a low temperature, all of that sits in the host code reading the registers. A pack built with a front end and no host is therefore protected and unmanaged, which is a valid build for a simple charger but not for a product with a fuel gauge on the display.
The alert output is the hand off between the two. It fires on a condition the host has to see, and the host then reads the status registers to find out which one. Polling the bus instead of using the alert works, but it costs bus time and it delays the host response by up to one polling interval.
Where it fits in a build
18 V class packs with a host that already runs the gauging: power tools, garden equipment, small scooters, portable instruments, and any product where the same host code is shared across several pack voltages. A 5S pack that has to run without a host is better served by a part that integrates the gauge and the protection behind a simple interface.
This family has been in production for years, which is both its strength and its risk. On a long programme the risk is the supply, and the safety stock planning page covers how we size a buffer against the build plan rather than against the order book.
The sourcing side of this part is covered on the strategic sourcing. For a front end that has been in production for years, that page covers how the supply is held across a long programme.
Questions we get on this code
Can it run a 6S pack? No, the BQ7692006 covers three to five cells. A 6S pack needs the 10 cell member of the family, which is a different package and a different pin count.
Does the host have to configure the protection thresholds? Yes, they are written into the part at start up. A part that has never been configured runs with its default values, which are not the limits a given pack needs.
Is the balancing automatic? No, the host decides when to balance and which cells. The FETs are in the part and the host drives them, usually during a rest period after a charge.
What happens in ship mode? The part turns off most of its own consumption so a pack can be stored for a long period without draining. Leaving ship mode needs a wake event on the pack terminals, and the host has to allow for the start up time before it expects a reading.