Isolating a Module Pulling Down the CAN Bus

CAN Bus Module Isolation: Pinpointing the Module That Is Killing the Network

Written by Anthony Calhoun, ASE Master Tech A1-A8

You hook up the scan tool and half the modules will not communicate. The ones that do respond are throwing U-codes — U0100, U0101, U0140, U0155 — codes that point at every other module on the car. The customer says three warning lights came on overnight and the car barely starts. You already know what this is. Something on the CAN bus is dragging the entire network down, and until you find it, you are not fixing anything.

CAN bus module isolation is one of the most methodical diagnostic processes in modern automotive repair. It is not difficult, but it is systematic. Skip steps and you will chase ghosts. Follow the process and you will find the faulty module every time. This article covers the full isolation procedure — from scope-based waveform analysis to resistance measurements to split-half testing — at the level of detail a working technician actually needs.

When Module Isolation Is Needed

Not every U-code means the bus is down. A single module that lost power or ground will throw U-codes in other modules that depend on it. That is a missing module, not a bus fault. Module isolation becomes necessary when the bus itself is compromised — meaning one module's internal CAN transceiver circuit has failed in a way that shorts or pulls the bus to an abnormal voltage state.

The signs that tell you the bus is being actively corrupted rather than simply missing a module are:

• Multiple U-codes spread across many different modules with no clear pattern
• Scan tool struggles or completely fails to communicate on one or more buses
• Modules that were communicating drop off mid-scan
• The same U-codes return immediately after clearing, even with key off then back on
• Voltage readings on CAN-H or CAN-L are stuck — not switching, not oscillating

When a CAN transceiver fails with an internal short, it pulls CAN-H low, pulls CAN-L high, or drags both lines to the same voltage. That kills the differential signal every other module on the bus depends on. The bus looks flat to a scope. Communication stops. Every module that relies on that bus starts logging U-codes for every module it can no longer hear from. That is why you see the shotgun pattern of codes across the entire network.

One additional cause worth noting early: aftermarket devices. A poorly wired remote start, an added trailer brake controller, or any device that was spliced into the CAN bus incorrectly can load the bus enough to corrupt communication. Always ask what has been added or serviced recently before you start pulling connectors on factory modules.

Understanding CAN Bus Topology

Before you can isolate a module, you need to understand how the bus is physically structured. The topology determines your disconnection strategy.

Backbone Topology

Most vehicles use a backbone or linear bus topology. The CAN-H and CAN-L wires run in a single path from one end of the bus to the other. Each module connects to the main bus through a short stub — a branch off the main backbone. The bus is terminated at each end by a 120-ohm resistor. The two termination resistors in parallel produce the 60-ohm reading you measure at the DLC between pins 6 (CAN-H) and 14 (CAN-L) with the key off and all modules connected.

In a backbone topology, a shorted transceiver anywhere on the bus brings down every module on that backbone. The entire bus sees the corrupted signal simultaneously.

Star Topology

Some manufacturers — notably certain Ford and GM architectures — use a star topology where all modules connect to a central hub or splice point. The wires radiate outward from the center like spokes. Star topologies are less common on the main powertrain bus but appear on body and convenience bus networks. With a star topology, a shorted module may affect fewer other modules depending on how the hub is designed.

Termination Resistors

The 120-ohm termination resistors at each end of a backbone bus are critical reference points for your diagnostic. Their location varies by manufacturer and by which bus you are testing. On many vehicles, one termination resistor is integrated into the ECM or PCM and one is integrated into another module at the far end of the bus — commonly the BCM or instrument cluster. On some vehicles, the resistors are stand-alone components in a connector or inline in the harness. The wiring diagram will tell you where they are. You need to know this before you start disconnecting things, because unplugging a module that contains a termination resistor changes your resistance baseline.

The key numbers to remember: 120 ohms at each end, approximately 60 ohms total between CAN-H and CAN-L at the DLC with everything connected and key off. A reading significantly below 60 ohms means something is shorting the two lines together or pulling one line down. A reading significantly above 60 ohms — or open — means a termination resistor is missing or a break exists in the bus wiring.

The Scope-Based Approach

The oscilloscope is the fastest tool for confirming whether the bus is being actively corrupted and for watching in real time as you disconnect modules. Connect your scope probes to the DLC — CAN-H on pin 6, CAN-L on pin 14 — referenced to chassis ground. Set your time base to 200 microseconds per division to start. CAN bus operates at 500 kbps on the high-speed powertrain bus (HS-CAN) and 125 kbps on medium-speed body buses. You want to see the bit transitions clearly.

What a Healthy Bus Looks Like

On a healthy high-speed CAN bus, CAN-H idles at approximately 2.5 volts (recessive state) and swings up to approximately 3.5 volts during a dominant bit. CAN-L idles at 2.5 volts and swings down to approximately 1.5 volts during a dominant bit. The two signals are mirror images of each other, differential. When you see both lines moving symmetrically in opposite directions, the bus is communicating. Transitions are clean. Square waves with defined edges.

The differential voltage — CAN-H minus CAN-L — is approximately 0 volts in the recessive state and approximately 2 volts in the dominant state. If your scope has a math channel, display CAN-H minus CAN-L to see this clearly. Noise shows up as spikes or instability in the differential signal even when individual channels look plausible.

What a Corrupted Bus Looks Like

A shorted transceiver typically pulls one or both lines to a fixed voltage. You might see CAN-H stuck at 0 volts and CAN-L stuck at 5 volts, or both lines pulled to the same voltage with no differential. In other failure modes, the bus is partially active — some bits get through — but the waveform is noisy, asymmetrical, or shows erratic spikes that corrupt valid frames. Error frames look different from data frames: the recessive-dominant pattern becomes irregular and you may see the bus sitting in an error-passive or bus-off state with long periods of inactivity followed by bursts of retransmit attempts.

Document your scope waveform before you start disconnecting modules. Take a screenshot or a photo. You want a baseline to compare against as modules are removed.

Systematic Disconnection — One Module at a Time

With the scope connected to the DLC and the bus waveform visible, begin disconnecting modules one at a time. Watch the scope after each disconnection. When the waveform cleans up — when you go from a flat or corrupted signal to clean, symmetrical square waves — the last module you disconnected is the one dragging the bus down.

The strategy for which module to disconnect first matters. On a backbone bus, start at the ends and work toward the middle. The modules at the physical ends of the bus are often the easiest to reach, and starting at the ends avoids disconnecting a termination resistor (which would change your resistance baseline). Work inward methodically.

A few procedural rules for systematic disconnection:

1. Disconnect one module at a time. Do not pull multiple connectors at once or you lose track of which one changed the waveform.
2. After each disconnection, wait five to ten seconds and observe the scope. Some modules take a moment to drop off the bus as error counters increment to bus-off state.
3. If the waveform does not change after disconnecting a module, reconnect it before moving to the next one. You want to keep as much of the bus intact as possible so the corrupted signal remains visible.
4. Keep a written log of the order you disconnected modules. When the bus clears, you need to know exactly which module was last unplugged.
5. Be aware of modules that contain termination resistors. When you unplug one, your 60-ohm resistance reference changes to 120 ohms. Factor that into your scope observations — the bus impedance changes but the waveform quality is what you are watching for.

The Resistance-Based Approach

If you do not have a scope available, or if you want to use resistance as a secondary confirmation method, measure between CAN-H (pin 6) and CAN-L (pin 14) at the DLC with the key off. The reading should be approximately 60 ohms. This method works best for finding dead shorts rather than transceiver failures that only corrupt the bus when active.

A reading below 20 ohms indicates a hard short between CAN-H and CAN-L somewhere in the network — either in the wiring or inside a module's transceiver. A reading above 120 ohms or an open indicates a missing termination resistor, a broken bus wire, or a module with an open CAN circuit.

To isolate with resistance: disconnect modules one at a time with the key off and measure after each removal. When the resistance reading shifts toward 60 ohms — or when the abnormally low reading jumps back up — the module you just removed was the one shorting the bus. Again, be aware that removing a module containing a termination resistor will shift the reading toward 120 ohms on its own, which is expected and not necessarily the fault.

The resistance method has one important limitation: a module whose transceiver only fails when energized will not show up as a resistance fault with the key off. That is why the scope-based approach with the bus active is the more reliable primary method. Use resistance testing as confirmation, not as the only tool.

Using the Wiring Diagram

Before you start pulling connectors, pull up the wiring diagram for every CAN bus on the vehicle. You need to identify:

• Which modules are on the specific bus that is corrupted — not every module is on every bus
• The physical connector locations for each module
• Which modules contain built-in termination resistors
• Where splice points or inline connectors join the bus backbone
• Which modules are on sub-buses and connect through a gateway

Modern vehicles may have four or more separate CAN buses: a high-speed powertrain bus, a medium-speed body bus, a low-speed convenience bus, and additional special-purpose buses for infotainment or chassis systems. A problem on one bus does not automatically mean every bus is affected, though a gateway failure can cascade across multiple buses. Your scan tool communication failures will tell you which bus is down. Confirm this by checking which specific U-codes are set and which modules are failing to communicate.

Plan your disconnection sequence on paper before you start. Note the connector location for each module in the order you plan to disconnect them. Accessibility matters — a module with a connector in the dash might take twenty minutes to reach while a door module might take thirty seconds. Plan an efficient route. Note any modules that are under the vehicle, inside trim panels, or that require other components to be removed for access. You want to factor that into your sequence without compromising the logical order of working from the ends inward.

Gateway Module Considerations

The gateway module — sometimes called a central gateway, body control module with gateway function, or TIPM on Chrysler platforms — is the hub that routes CAN traffic between buses. On many modern vehicles, if you want to communicate from the scan tool on the HS-CAN powertrain bus to a module on the medium-speed body bus, that data passes through the gateway. The gateway translates and forwards messages between networks.

When the gateway module itself fails, you can see communication problems on multiple buses simultaneously even though the buses themselves are physically intact. This looks like the entire network is down but is actually a single module failure.

Testing around a potential gateway failure requires connecting the scan tool and attempting to communicate on each bus independently. Some scan tools allow you to select a specific bus protocol and communicate directly on that bus. If the powertrain bus communicates cleanly when you bypass the gateway but body bus modules are unreachable, the gateway is a strong suspect. Confirm with a scope on each bus separately — if the powertrain bus waveform is clean and the body bus waveform is clean but the gateway cannot route between them, the gateway's internal processing or its connection to one of the buses has failed.

The TIPM on Chrysler vehicles deserves a specific call-out. The TIPM combines the function of the fuse and relay center with gateway and bus termination functions. A failed TIPM can corrupt the bus, drop termination resistance, and disable power to modules all at the same time. It is a common failure point and a frequent culprit when you have a whole-vehicle communication failure on a Ram truck, Grand Cherokee, or Dodge Charger.

The Split Testing Technique

When you have many modules on a bus, disconnecting them one at a time is slow. The split testing technique cuts that time roughly in half with each step.

Instead of starting at one end, find a splice point, inline connector, or accessible point near the physical middle of the bus backbone. Disconnect the bus at that point, splitting it into two halves. Test each half independently by connecting the scope to the DLC and observing which half still shows the corrupted signal. The clean half is not your problem. Focus on the corrupted half.

Now find the midpoint of the corrupted half and split again. Test each quarter of the original bus. Repeat. Each split cuts the number of modules you need to check in half. On a bus with twelve modules, a one-at-a-time approach might require eleven disconnections in the worst case. Split testing finds the faulty half in one step, the faulty quarter in two steps, and the faulty eighth in three steps — that last split likely gives you only one or two modules to check.

The practical challenge with split testing is finding accessible split points in the middle of the bus. Splice points inside the harness are rarely accessible without cutting into the harness, which you do not want to do until you know where the problem is. Look for in-line connectors that manufacturers use to route harnesses through firewalls or body panels — these are natural split points. Some vehicles also have junction blocks or inline connectors that give you a clean separation point without cutting anything. The wiring diagram will show you these locations.

Common Culprit Modules

Experience in the field shows certain modules fail more often as CAN bus killers than others. Knowing the common suspects helps you prioritize your disconnection sequence without skipping the methodical approach entirely.

Door modules deserve extra attention because their failure mode is often intermittent. The wiring harness that runs between the body and the door flexes every time the door opens. Over time, the CAN wires inside that harness fatigue and develop cracks in the conductor. The bus works fine with the door closed, fails when the door is opened to a certain angle, then clears again. If the customer's complaint is intermittent, wiggle the door jamb harness while watching the scope before you start unplugging module connectors.

Aftermarket remote starts are a persistent problem. Shops that do remote start installations sometimes tap into the CAN bus to allow the module to communicate with the vehicle. A device with incorrect termination, a damaged CAN transceiver inside the aftermarket unit, or a CAN splice that was done with the wrong wire gauge can load the bus enough to corrupt communication. Always check for added devices before blaming a factory module.

Repair and Verification

Once you have identified the faulty module — the one whose disconnection cleaned up the bus waveform — do not simply replace it and button everything up. Verify your finding thoroughly before ordering a part.

Verification Before Replacement

With the faulty module still disconnected, reconnect every other module you removed during the isolation process. Now observe the bus on the scope with all other modules reconnected. The waveform should be clean and the scan tool should communicate with all available modules. If the bus is still corrupted with the suspect module disconnected and all others reconnected, you either have two faulty modules or there is a wiring fault — a chafed wire, a bad splice, or water contamination in the harness itself.

Also verify that the issue is the module and not its connector or wiring. Inspect the connector body for bent pins, pushed-back terminals, corrosion, and water ingress. Probe the CAN-H and CAN-L circuits at the module connector with the module unplugged and key on — confirm the bus voltage is correct at that point in the harness. A module that has been sitting with a corroded connector may clean up with a proper pin cleaning and reseating even without replacement. Verify everything before committing to a new module.

After Replacement

After replacing or repairing the faulty module, reconnect it to the bus. Observe the scope waveform with the replacement module connected. The waveform should remain clean. If the new module immediately corrupts the bus again, you have a wiring problem feeding that module — possibly a short to power or ground on the CAN lines that damaged the original module and will damage the new one too. Find and repair the wiring fault before installing another module.

With a clean bus confirmed on the scope, connect the scan tool and verify that all modules on all buses communicate correctly. Retrieve and clear all stored U-codes from every module in the vehicle — not just the ones you were focused on. A whole-vehicle scan will confirm that all modules are back online and that no secondary codes were set during the diagnostic process. Perform a short drive cycle and re-scan to confirm no codes return.

Document your findings: which module failed, what the scope showed before and after, which modules were disconnected during isolation, and how the repair was verified. That documentation protects you if the customer returns with a related complaint and gives the next technician useful information if the vehicle comes back years later.

Putting It Together

CAN bus module isolation follows a clear path. Confirm the bus is being actively corrupted using a scope at the DLC. Pull up the wiring diagram and identify every module on the affected bus. Plan your disconnection sequence starting from the ends of the bus and working inward, or use the split-half method to cut your time in half. Disconnect modules one at a time while watching the scope. When the bus clears, the last module removed is the problem. Verify by reconnecting all other modules with the suspect still out. Repair or replace the faulty module, confirm clean waveform on scope, perform a full communication scan, and clear all codes.

The technicians who dread CAN bus diagnostics are the ones who skip the scope and start guessing at modules. The technicians who work through it methodically — scope first, diagram in hand, one module at a time — find the fault every time. It takes discipline and the right tools, but it is a completely solvable problem. The bus always tells you what it needs. You just have to listen on the right pins.