U0049

U0049: Vehicle communication bus C (+) low

DIY difficulty 3/5

Print shop one-pager Take this page to the shop — causes, fair prices, and sharp questions on one sheet.

Your car's computers share information over wiring networks called data buses. This code means one of those networks is damaged or down, so the computers on it can't hear each other. You'll often see several warning lights at once — that's the modules complaining about each other, not necessarily several broken parts.

Key facts

Symptoms

Likely causes

Too many suspects? Answer 4–6 quick questions and this page's published cause list re-orders itself for your situation — plus the cheapest test to run next. Start the elimination wizard →

Before you buy the part — 5 checks

Work these checks before spending money — each one rules a cause in or out, cheapest first.

  1. Read all codes with a scan tool and list which modules report bus faults. If nearly every module reports it, suspect the bus itself or one failed module dragging it down rather than several bad modules. Tests: A failed module dragging the whole bus down
  2. Look for aftermarket devices tapped into the data bus (remote starters, alarms, trackers, plug-in dongles) and disconnect them first — they are a very common cause of bus faults. Tests: Aftermarket device tapped into the bus (remote starter, alarm, fleet tracker, plug-in…
  3. Inspect the bus wiring and connectors for chafing, corrosion, and water intrusion, especially where the harness flexes (doors, trunk, under seats) or was recently disturbed. Tests: Chafed, pinched, or corroded bus wiring, especially where the harness flexes or was…
  4. Check the gateway module's power, ground, and connector — it routes messages between buses and is a single point of failure for cross-bus communication. Tests: Failed CAN terminating resistor or gateway module (uncommon — check wiring first)
  5. If the wiring is sound, isolate a failed module by unplugging modules on that bus one at a time while watching whether the bus fault clears — the one that brings the bus back is the culprit.

No scan tool yet? The Veepeak OBDCheck (~$32) reads and clears codes from your phone in about two minutes.

Typical price range

Parts$0 – $600
Labor$150 – $400

Wiring repair or removal of an aftermarket device (most common). National-average estimate for the most common repair for this code. Actual quotes vary by vehicle, region, and shop - get a local written estimate.

Dealer vs independent shop: these ranges reflect typical independent-shop prices. A dealer will usually quote higher — higher labor rates plus OEM-only parts — so a dealer quote at the top of (or a bit above) this range isn't automatically a rip-off. For a big dealer number, get a second quote from an independent shop before authorizing the work.

Got a shop quote? Grade it →

What will this cost to fix? A code doesn’t name the repair — run the code-first estimator to see the most likely fixes for U0049 ranked, each with a price range.
They handed you a printout at the parts store? Decode it before you buy.

DIY difficulty

3 of 5 — Reading the code is easy; finding the damaged wire or the module dragging the bus down takes a careful hands-on hunt.

Watch this repair on YouTube

Parts & tools

Electrical diagnosis toolkit — what the job actually takes

Torque specs: Module connectors: hand-tight until they click — never force them.

Pro tip: Check powers AND grounds before condemning a module — most “module failures” are wiring. Disconnect the battery before unplugging modules.

As an Amazon Associate, WrenchFair earns from qualifying purchases.

Related codes

Check another code
Got a quote?Grade it →Shop one-pagerPrint it →Another code?Look it up →
Who's behind this guide? WrenchFair is built by a fellow DIYer, not a repair shop. Code meanings follow the SAE J2012 standard; cause rankings come from real-world repair evidence (service bulletins, owner reports, NHTSA records); prices are typical US ranges, not quotes. Read the full methodology →