Table of Contents
LTC6811-1 and LTC6811-2 can serve similar cell-measurement tasks while requiring different communication networks. Choosing the available suffix first and designing the host connection later creates avoidable board and firmware work.
Start with the battery system’s communication path, service access and fault-diagnosis needs. The topology choice should precede temperature grade, automotive ordering option and delivery packing.
What is the difference between the -1 and -2 communication networks?
LTC6811-1 supports daisy-chain isoSPI communication; LTC6811-2 supports individually addressed devices connected in parallel to the host. The distinction changes the wiring and host transaction model, not merely a label in the BOM.
The LTC6811-1/-2 datasheet describes both interfaces and their pin functions. For the daisy-chain arrangement, the host communicates along a chain of monitors. For the addressed arrangement, the host selects the intended device address on the network. Confirm the permitted connection details and interface components from the manufacturer’s design information.
The LTC6811 ordering directory separates -1 and -2 options, including LTC6811IG-1#TRPBF and LTC6811IG-2#TRPBF. A common package is insufficient evidence for substitution because the board uses more than the analog cell-input pins.
Which topology fits the service and fault-isolation task?
Choose after tracing how the host reaches every monitor and what information remains available when a communication segment fails. A wiring convenience that makes assembly easier may make field diagnosis harder.
| Planning question | Daisy-chain review | Addressed-network review |
|---|---|---|
| How are modules identified? | Position/order in the chain and host handling | Address assignment and uniqueness |
| How does a module reach the host? | Through the designed chain path | Through the addressed network connection |
| What happens after one connection opens? | Determine which downstream communication is lost | Determine which device or branch becomes unreachable |
| What changes during module replacement? | Chain order, orientation and reconnection | Address setting, network connection and host map |
| What evidence supports diagnosis? | Last reachable device and communication error record | Address-specific response and error record |
These are design questions, not universal fault-tolerance guarantees. The actual result depends on the board, interface implementation and firmware recovery behavior.
The service record should map physical module location to logical identity and cell numbering. If a technician replaces a module and the host associates its readings with the wrong physical position, electrically valid data can still be operationally misleading.

How should pin functions and firmware be compared?
Compare the complete schematic net assignment and the command/response handling for the selected variant. Preserve the communication-mode and addressing connections instead of treating all non-cell-input pins as equivalent.
Build a small host test before integrating a large stack. Verify initialization, repeated measurements, packet error checking, stale-data detection and recovery after a deliberately interrupted communication path. An application should distinguish a recent valid measurement from an old value retained after a link failure.
For a four-module system example, record each module’s identity, expected response length and physical cell range. Remove one communication connection under a controlled, safe test arrangement and record which data stops updating. Restore it and verify that the host reconstructs the correct map without silently accepting duplicate or misordered data.
Electrical and high-voltage testing must follow the project’s approved engineering procedures. The purpose of this comparison is to define the communication evidence, not to provide instructions for live battery-stack work.
Keep grade and packing decisions separate from topology
After the network is selected, compare the required temperature range and exact ordering option. The datasheet distinguishes I and H temperature grades and lists automotive products with 3ZZ ordering strings. None of those choices turns -1 into -2.
The battery-protection selection article covers protection thresholds and delays, a separate system task. Link the monitor BOM to that architecture without describing a measurement IC as proof that the entire battery meets a safety requirement.
A production purchase should preserve topology, grade, package, packing and the approved board/software revision. If a supplier offers another suffix, identify the changed field first. That lets the engineering team review the relevant network or qualification requirement instead of repeating an unfocused full-product comparison.
Frequently Asked Questions (FAQ)
Does the LTC6811 replace an independent battery protection function?
A cell monitor supplies measurements and associated functions; the complete battery system still needs its specified protection architecture. Do not infer system protection approval from the monitor selection.
Does #3ZZ identify a third communication topology?
No. The datasheet uses 3ZZ in automotive ordering options. Keep that ordering purpose separate from the -1/-2 communication distinction and confirm the exact option’s documentation.
Can a software address change alone convert a -1 board into a -2 board?
Do not assume so. The topology and relevant pin functions differ. Compare the schematic, wiring and command sequence before proposing any hardware or firmware conversion.
How should a spare module be mapped after replacement?
Record the physical location, logical address or chain position, expected cell range and host-side map before the swap. After installation, verify that the host attributes each reading to the correct physical module rather than accepting electrically valid but misordered data.