A vehicle CAN bus is a communication link, not a supply. Two wires twisted together carry differential voltage signals that let control modules exchange short messages many times a second. No module is powered through it. Understanding that distinction explains why back-probing it carelessly, splicing accessories into it, or adding a device that does not respect the protocol can take an entire vehicle off the road.
How the two wires carry information
The bus uses a differential pair, conventionally called high and low. When the bus is idle, both sit near a common resting level. To send a dominant bit, a transmitting module drives one line up and the other down. Receivers look at the difference between the two rather than at either one against ground. Because any interference picked up along the run affects both wires nearly equally, subtracting one from the other cancels most of it. That is the entire reason the pair is twisted, and it is why untwisting a length to make a splice tidy degrades noise immunity exactly where you introduced the join. Keeping the pair twisted right up to the connector is part of the design, not a manufacturing habit you can improve upon.
Arbitration, priority and why messages do not collide
Any module can start transmitting when the bus is quiet. If two begin at once, the protocol resolves the conflict without either being corrupted: the dominant state wins bit by bit, so the message with the numerically higher priority identifier proceeds and the other backs off and retries. This means a vehicle network has no master, and it also means a single misbehaving device that transmits constantly at high priority can starve everything else. Aftermarket gadgets that inject messages onto the bus are participating in this negotiation whether their makers thought carefully about it or not. Error counters inside each transceiver also track how often a node fails to transmit, and a node that exceeds a threshold removes itself from the bus.
Termination resistors are part of the circuit
A high-speed bus needs matched terminating resistance at each end of the backbone to absorb signal reflections. Those resistors live inside specific modules, and the vehicle depends on both being present. Remove or disconnect a module that carries one and communication can become unreliable in ways that look like a dozen unrelated faults. Measuring resistance across the pair with the system fully off is a standard quick check, because a result far from the expected combined value points at a missing terminator or an added one. The specific expected value depends on the network, so consult service information rather than assuming. Stub lengths matter as well, since a long branch off the backbone behaves like an unterminated line and reflects signals back.
Why probing and splicing cause damage
Piercing probes leave a hole in the insulation that admits moisture and starts corrosion inside the conductor, and the resulting intermittent fault may not appear for months. Shorting either line to supply or to ground, even briefly, can destroy transceivers in multiple modules at once, because every device on the segment shares the same pair. Powering an accessory from a bus wire, which happens when someone assumes any wire with voltage on it is a supply, is worse still. Use the diagnostic connector and proper breakout tooling, and never scotch-lock into a network pair. Corrosion inside a conductor raises resistance unevenly between the two wires, which destroys the symmetry the differential scheme relies on.
What this means for accessories and diagnostics
Devices that read vehicle data legitimately do so through the diagnostic connector or through a gateway designed for the purpose, and well-built ones listen far more than they talk. Cheap trackers and performance dongles left permanently installed are a known source of both parasitic drain and bus disturbance. Many vehicles now run several separate networks at different speeds with a gateway between them, so a tool that works on one segment may see nothing on another. Before adding anything that touches the network, confirm the manufacturer supports it and that it can be removed cleanly. Documenting anything you add is worth the trouble, because a future diagnosis that does not know about your device will go badly.
What to check before you act
- Never power an accessory from a network wire or splice into the pair.
- Use the diagnostic connector and a breakout box rather than piercing probes.
- Check termination resistance against the value in service information.
- Remove permanently installed dongles before chasing network or drain faults.
Common questions
Can a bad module take down the whole network?
Yes. A device that shorts a bus line or transmits continuously can prevent every other module from communicating, even though the rest of them are perfectly healthy.
Why do I see voltage on the bus wires?
Because the transceivers drive the lines to defined levels to represent bits. That voltage is a signal reference, not a supply capable of running anything.
The practical takeaway
Treat the pair as a signal path with specific impedance requirements and no spare energy. Keep the twist, avoid piercing the insulation, verify termination when communication is unreliable, and remove aftermarket bus devices before diagnosing anything unexplained.
References and further reading
- FCC: electromagnetic compatibility background relevant to signal wiring and interference
- CDC and NIOSH: electrical fundamentals and safe measurement practice
- NFPA: electrical safety education and wiring integrity concepts
Numerical scenarios are illustrative unless identified otherwise. Follow the exact product instructions; component ratings and local installation requirements can differ.
