BQ79600PWRQ1
Product Specifications
BQ79600PWRQ1
Texas Instruments — Power Management & Signal Chain
Product Overview
The BQ79600PWRQ1 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
BQ79600PWRQ1: automotive bridge between a host SPI or UART port and a battery monitor daisy chain
BQ79600PWRQ1 is a communication bridge that translates a host SPI or UART port into the daisy chain protocol used by automotive battery monitors in a TSSOP body of 16 pins. The part sits between the microcontroller and the monitor stack, converting host frames into the differential daisy chain signals and back. It also wakes the system when an unmasked fault appears on the chain, which is what lets a parked vehicle keep its monitors asleep and still detect a fault.
Order code and package
| BQ79600PWRQ1 | TSSOP PW, 16 pins, 2000 pieces on a large reel, marking BQ79600 |
| Moisture level | Level 2, 260 C, one year floor life |
| Temperature | minus 40 to plus 125 C ambient, AEC-Q100 grade 1 |
| ESD | HBM level 2 and CDM level C4B |
| Supply | 4.75 V to 40 V at the battery pin from the vehicle rail, with the inhibit output controlling the system regulators |
| Logic rail | VIO from 1.71 V to 5.25 V, which sets the host side levels |
| Qualification | developed for functional safety applications, systematic and hardware capability up to ASIL-D |
Electrical parameters that decide the application
| Host interfaces | SPI with a ready signal, or UART, selected by the state of a pin at wake up |
| Chain side | differential transmit and receive pair to the monitor stack, with a common mode pin |
| Battery input | 3.135 V to 24 V in the recommended operating conditions, with the absolute maximum above that |
| Logic input range | VIO referenced, 5.25 V maximum on the host side pins |
| Wake up | automatic wake of the monitors and the system when an unmasked fault is detected on the chain |
| Inhibit output | open drain PMOS control for the system regulators, with a pull up resistor |
| Transfers | host frames are translated bit by bit, so the chain timing follows the host clock within the device limits |
| Package thermal | junction to case 16 C per W, junction to board 102 C per W in the sixteen pin body |
Family variants and how they differ
| SPI mode | chip select, clock, master out and master in, plus a ready line that tells the host the bridge can take a frame |
| UART mode | a two wire port with the same frame format, used where the host has no spare SPI |
| Ring architecture | the automatic wake path assumes the chain is wired as a ring, so a fault can reach the bridge from either end |
| No thermal pad | the sixteen pin body has no exposed pad, so the copper is on the pins and the surrounding plane |
| Pin strapping | the interface mode is read at wake up, so the strap resistors have to be in place before the device leaves reset |
| Safety documentation | a safety manual and a functional safety analysis report are available for the ISO 26262 file |
Points to check before this part goes on a BOM
The interface mode is read once, at wake up. The strap that selects SPI or UART is sampled while the device comes out of reset, so a board that changes mode at run time has to power cycle. A strap resistor that is loaded by a nearby signal will select the wrong mode intermittently, and the symptom is a host that works on the bench and fails in the vehicle.
The bridge is the only part of the stack that is awake in a parked vehicle. The monitors sleep and the bridge watches the chain, which is why the supply range goes to 24 V in the recommended table and the quiescent current is the number that decides whether a parked car battery survives a month. That current is drawn from the vehicle rail, not from the pack.
The automatic wake path depends on the ring. In a ring, a fault can travel either way round and reach the bridge even if the chain is broken at one point. In a linear chain, a break between the bridge and the first monitor leaves the bridge deaf, so the wiring topology is a safety decision and not a cost decision.
The inhibit output controls the regulators, so its polarity matters at power up. The pin is an open drain PMOS driver with a pull up, and the system regulator is enabled or disabled by its state. A wrong pull up value holds the rail off, and the symptom looks like a dead board rather than a communication fault.
ASIL-D capability belongs to the device, not to the product. The hardware and systematic capability figures come with a safety manual and an analysis report, and the product's claim depends on how the device is used, what diagnostics are run and what the software does with them. The documents are the starting point for that argument, not a substitute for it.
Level 2 moisture applies to a body with a fine pitch. The reel has a one year floor life, and a body that has been out of the bag for longer needs baking. The part is small enough that a reflow profile copied from a larger board will not necessarily meet the peak the label states.
Why the bridge exists at all
A stack of monitors speaks a differential protocol with its own framing, its own timing and its own fault reporting. A microcontroller in a battery management unit is chosen for its peripherals, its safety documentation and its cost, and rarely for a spare differential port. The bridge converts one to the other in hardware, so the host firmware stays simple.
The second reason is wake behaviour. The host is asleep in a parked vehicle and cannot poll, so something has to watch the chain and start the system when a fault appears. That watchdog function is inside the bridge, and it is the reason the device is on the vehicle rail rather than on the pack.
What to check before a first build
The strap resistors for the interface mode, the pull up on the inhibit output and the coupling on the differential pair are the three things that decide whether the first board talks. All three are outside the device, and all three are easy to leave at a value copied from a reference circuit.
The second check is the fault path. An unmasked fault has to reach the bridge, and the bridge has to wake the host. A build that masks the fault in the monitor configuration has a working bridge and no wake, which reads as a firmware bug until the configuration file is compared with the one the safety case assumes.
Where this order code fits
Vehicle battery management systems, 48 V mild hybrid packs, fuel cell stacks and stationary storage. In every case a microcontroller that is not built for a differential chain has to talk to a stack of monitors, and the bridge is the component that makes that link without a custom protocol in the host. Teams comparing it with a neighbouring part start from our Power Management Cross Reference page, and teams replacing a part that has gone end of life start from the Component Obsolescence Management page.
Questions buyers ask
Can the host talk to the chain directly? Not without implementing the daisy chain protocol in software and driving a differential physical layer. The bridge does both, and presents the chain as a byte stream on SPI or UART, so the host firmware sees a register style interface.
Does the bridge need its own supply from the pack? It runs from the vehicle rail, not from the cell stack, which is why the recommended range starts at 3.135 V and goes to 24 V. That keeps the bridge alive when the pack is isolated, which is what the wake function needs.
What happens if the host stops clocking? The bridge holds the last state and the chain stays quiet. A host that hangs does not corrupt the monitors, but it also does not poll them, so the fault detection moves to the bridge wake path rather than to the host.
Is the same part used with monitors other than the automotive ones? It is written for the automotive monitor family, and the frame format follows that family. Using it with a different chain means matching that protocol, which the device does not translate.
How is the bridge tested on the line? With a loopback frame on the chain side and a register read on the host side. That catches a strap error, a wrong interface mode and a broken differential pair in one step, and it does not need the monitors to be fitted.
SUPERB holds and sources this line for production and repair demand, quoted against the exact ordering string with date codes, packing and country of origin stated on the offer. When a part is moving, the Incoming Inspection Plan page sets out the checks that keep a substitute from failing on the bench.