Can Bus Communication Failure: Throttle Body and Trunk Latch No Response

When your trunk latch stops responding and you're also seeing throttle body codes, your first thought probably isn't "network problem." But modern vehicles connect these seemingly unrelated systems through a shared communication network called the CAN bus. A single fault on that network can knock out both the throttle body commands and the trunk latch actuator at the same time. Understanding how this happens saves you hours of chasing the wrong problem and hundreds of dollars in unnecessary parts.

What does CAN bus communication failure actually mean for these systems?

CAN bus (Controller Area Network) is the wiring network that lets different modules in your car talk to each other. The engine control module (ECM), body control module (BCM), throttle body, and trunk latch actuator all send and receive data across this shared line. When communication breaks down, modules stop getting the messages they need to function.

A CAN bus failure affecting both the throttle body and trunk latch usually points to a problem on the physical data bus damaged wiring, a corroded connector, a shorted module, or a termination resistor issue. The trunk latch might stop responding not because the latch itself is broken, but because the BCM never receives the unlock command over the bus.

Why would a throttle body problem affect the trunk latch?

This is the question that throws most people off. The throttle body and trunk latch seem completely unrelated. But on many vehicles especially GM, Ford, and some European makes they share the same CAN bus segment or are routed through the same wiring harness.

Here's what happens in practice:

A damaged wire in the harness chafes against the frame, creating an intermittent short on the CAN high or CAN low line.
The throttle body, which relies on real-time CAN communication for electronic throttle control, sets communication error codes (like U0100, U0073, or U0121).
The BCM, also starved of valid CAN messages, stops processing trunk release requests.
Both systems fail, but the root cause is one shared wiring fault not two separate broken parts.

What symptoms should you look for?

A CAN bus communication failure that hits both the throttle body and trunk latch usually produces a recognizable pattern:

Check engine light with throttle-related codes (P2101, P2111, P2112) alongside communication DTCs (U-codes).
Trunk latch won't respond to the key fob, interior button, or mechanical release in some cases.
Multiple warning lights appearing at once ABS, traction control, airbag, or stability control indicators.
Reduced engine power or limp mode because the ECM can't read throttle position data.
Intermittent behavior the trunk works sometimes, the throttle works sometimes, then both fail together.

That intermittent pattern is a strong indicator of a wiring or connector issue rather than a failed component. If both systems always fail at exactly the same time, start looking at shared wiring paths.

How do you diagnose a CAN bus failure affecting the throttle body and trunk latch?

Step 1: Scan for codes on all modules

Don't just pull engine codes. Use an OBD-II scanner that can read all modules body, chassis, powertrain, and network. Look for U-codes (communication errors) in multiple modules. If the BCM, ECM, and other modules all report "lost communication," the problem is almost certainly on the bus itself.

Step 2: Check the CAN bus wiring physically

The CAN bus uses a twisted pair of wires (CAN high and CAN low). Using a multimeter, you can check resistance between CAN high and CAN low at the OBD-II port with the battery disconnected. You should see approximately 60 ohms (two 120-ohm termination resistors in parallel). A reading far off from this tells you there's an open circuit, short, or failed resistor. If you need help checking the wiring around the throttle body and trunk latch area, this guide on testing the trunk latch circuit and throttle body ground wire walks through the process.

Step 3: Isolate the faulty section

Disconnect modules one at a time and recheck bus resistance. If unplugging the throttle body connector restores normal communication, the throttle body or its wiring is pulling the bus down. If unplugging the trunk latch module fixes it, the fault is in that circuit. The goal is to narrow down which section of the shared harness carries the fault.

Step 4: Inspect the wiring harness

Look for chafed wires, corroded pins, green crust on connectors, water intrusion, and rodent damage. Pay special attention to harnesses that run through door jambs, under carpet, or along the firewall these are high-friction and moisture-prone areas. A detailed approach to tracing wiring faults between the throttle body and trunk actuator can help you find the exact break point.

What are the most common mistakes people make?

Replacing the throttle body or trunk latch first. These parts are expensive, and they're rarely the root cause when both fail simultaneously. The CAN bus fault is upstream.
Only reading engine codes. Engine codes alone won't tell you about a network-wide communication problem. You need to scan every module.
Ignoring intermittent failures. If the trunk "sometimes works," don't dismiss it. Intermittent CAN faults are often the early stage of a wiring problem that will get worse.
Not checking ground wires. A bad ground can look like a CAN bus failure because modules can't reference the correct voltage. Always verify ground integrity.
Splicing into the CAN bus wires without proper technique. Twisted pair wiring must stay twisted to resist electromagnetic interference. A sloppy splice can introduce noise that corrupts the entire bus.

Can a bad throttle body itself cause the trunk latch to stop working?

In some cases, yes. If the throttle body's internal electronics develop a fault that drags down the CAN bus voltage pulling CAN high to ground, for example every other module on that bus segment will lose communication. The trunk latch isn't broken; it's just not getting commands. This scenario is covered in more detail in this guide on how the throttle body can cause trunk latch electrical faults.

However, this is less common than a shared wiring fault. Before blaming the throttle body, rule out the harness and connectors first.

What tools do you need for this diagnosis?

OBD-II scanner with multi-module capability (not just engine codes)
Digital multimeter for resistance and voltage testing on the CAN bus
Oscilloscope (optional but very helpful) to see the CAN bus waveform and spot noise or corruption
Wiring diagram for your specific vehicle year, make, model, and trim level matter
Basic hand tools for accessing connectors and harnesses

For reference on CAN bus signal standards and troubleshooting methods, CSS Electronics offers a solid CAN bus tutorial that explains the protocol in plain terms.

When should you take it to a professional?

If you've scanned for codes, checked bus resistance, and inspected visible wiring but still can't find the fault, a shop with an oscilloscope and factory-level diagnostic software can pinpoint the problem faster. CAN bus faults that involve internal module failure or hidden harness damage (inside door pillars or under the dash) often require professional-grade equipment and access to vehicle-specific repair databases.

Expect a proper diagnosis to take one to two hours of labor. That's far cheaper than replacing parts that aren't broken.

Practical next-step checklist

Scan all vehicle modules for DTCs write down every U-code, P-code, and B-code.
Measure CAN bus resistance at the OBD-II port (key off, battery disconnected). Expect ~60 ohms.
Check the throttle body connector and trunk latch connector for corrosion, loose pins, or water damage.
Visually trace the wiring harness between the throttle body and trunk latch area for chafing or breaks.
Disconnect modules one at a time to isolate which section is pulling the bus down.
Repair or replace the damaged wire or connector do not just splice loosely. Keep CAN wires twisted.
Clear all codes, test both the throttle response and trunk latch, and drive the vehicle to confirm the fix holds.

Tip: If the fault returns after repair, the damage may be in a second location on the same harness. Don't stop at the first bad spot you find inspect the full run from the BCM to the engine bay and from the BCM to the trunk area. Wiring problems rarely exist alone.