OBD-II trouble code
U0028: Vehicle Communication Bus B
An unqualified fault on the second vehicle bus — no error state named, no module named. The most informative thing available is not a meter reading but the list of which modules still answer.
Quick facts
- System
- Network
- Category
- Network Communication
- Severity
- High severity
- Drivable
- No — stop driving until repaired
- Repair cost range
- $120 – $1,400
- DIY difficulty
- Shop recommended
Browse every code in U0001–U0075, or start from the full code library.
What does U0028 mean?
U0028 reports that the second vehicle communication bus is not behaving correctly. What makes this code distinctive is everything it declines to say. It does not name a missing module, the way a lost-communication code does. It does not name a defined controller state, the way a bus-off code does. It is the unqualified member of the network catalogue, and that shapes how it should be worked.
Because the code carries no target, the highest-value information available at the start is the list of modules the scan tool can and cannot reach. That list is not incidental — it is a map. Modules on a shared segment fail together, and modules on separate branches do not, so the boundary between what answers and what does not falls at a physical place in the harness. Writing that list out before touching a meter frequently narrows a whole-vehicle problem down to one run of wire or one connector. Skipping it and going straight to measuring at the diagnostic socket throws away the cheapest evidence in the job.
There is a complication to that reading worth knowing about, because it catches people out. Most modern vehicles do not connect the diagnostic socket directly to every bus. A gateway module sits in between and relays requests onto the correct segment. So "the scan tool cannot see those modules" has two very different explanations: the segment is down, or the gateway is down and the segment behind it is perfectly healthy. Confirming that the gateway itself is responding, before concluding anything about Bus B, prevents a long search in the wrong half of the vehicle.
The physical failure that produces this code most reliably is worth naming because it is repairable rather than replaceable. On many vehicles the modules on a bus do not daisy-chain — they meet at a physical splice pack, a star point where a dozen branches are joined behind the dash, under a seat, or beneath the carpet at a sill. That single point is a magnet for water. A leaking windscreen seal, a blocked sunroof drain, a failed door membrane or a spilled drink reaching one of those locations takes down every branch at once and produces exactly this pattern of symptoms. So "has anything got wet in this car" is a legitimate diagnostic question, and a fault that started in the week after heavy rain or a windscreen replacement is pointing somewhere specific.
The last practical point is about how this repair is priced. A bus fault is almost entirely diagnostic labour with a small parts bill at the end — a repaired connector, a spliced wire, occasionally a resistor. An estimate that opens with a module replacement before any isolation work has been done is a warning sign, because there is nothing in an unqualified bus code that identifies a module. Ask what testing led to that conclusion. On the vehicles where a module genuinely is corrupting traffic, the technician will be able to tell you which one and how they proved it.
Common causes
- Water reaching a splice pack or star point where many Bus B branches are physically joined
- Leaking windscreen seal, blocked sunroof drain or failed door membrane feeding water into a harness run
- Chafed bus conductor rubbing against a bracket, seat rail or body seam
- Rodent damage to a harness section carrying the bus pair
- Corroded or backed-out terminal at a module connector on the Bus B branch
- Gateway module fault making a healthy segment appear unreachable from the diagnostic socket
- Failed terminating resistor on a high-speed Bus B segment
- A single module on the bus transmitting corrupted frames
- Harness damage from accident repair or aftermarket installation work
Symptoms
- Several warning lights appearing together with no single system obviously at fault
- A specific group of modules unreachable by scan tool while the rest respond normally
- Loss of the features served by the second bus, which varies entirely by manufacturer
- No-start or stalling where a module critical to running lives on that segment
- Gauges, displays or convenience systems frozen, blank or erratic
- Symptoms that began within days of heavy rain, a car wash, or windscreen work
- Faults that come and go with road vibration or with going over a speed bump
- A scatter of U-series codes stored across multiple modules describing the same segment
Diagnostic steps
- 1.Before any measurement, list every module the scan tool can reach and every module it cannot. The boundary between those two lists falls at a physical point in the harness.
- 2.Confirm the gateway module itself is responding. If it is not, the segment behind it may be entirely healthy and the search belongs elsewhere.
- 3.Get a wiring diagram and identify which modules and circuits actually constitute Bus B on this vehicle, since the letter is not standardised between manufacturers.
- 4.Ask whether the vehicle has been wet, washed, or had glass or trim work done recently, and locate the splice packs and star points for that segment.
- 5.Inspect those splice points directly for green corrosion, water staining or a damp carpet underneath before doing anything else.
- 6.With the key off and the battery disconnected, measure across the bus pair and compare against the service data for that specific segment.
- 7.Check the bus pair for shorts to ground and to supply with the segment isolated.
- 8.Inspect the harness along its run for chafe points at brackets, seat rails and body seams, and for rodent damage.
- 9.Disconnect modules on the segment one at a time and watch whether communication returns, which identifies a node corrupting traffic.
- 10.After repair, confirm every module on the segment reports for several full drive cycles rather than testing once in the workshop.
Repair cost
$120 – $1,400
Expect the bill to be mostly labour. Diagnosis is $150 to $350 because isolating an unqualified bus fault is methodical work with no shortcut. Drying and repairing a water-damaged splice pack is $150 to $500, and the associated water leak — a windscreen reseal, a cleared sunroof drain, a door membrane — is a separate $100 to $400 that should be done at the same time or the fault returns. A harness or connector repair runs $150 to $650 depending on access. A gateway or bus module replacement with programming is $400 to $1,100. Treat any quote that opens with a module before isolation work has been done as a question to ask rather than a number to accept.
Estimate your repair
Run the numbers for your vehicle
Open the Repair Cost Estimator with module communication / can bus diagnosis preselected. Adjust labor rate and vehicle category to fit your situation.
DIY vs shop
Leave this one to a qualified shop. The barrier here is module programming, security access, and bus-level diagnosis that need manufacturer-grade scan tools and the credentials to use them. DIY attempts often produce a more expensive problem than the original code.