Home / DTC / U0046 — Vehicle Communication Bus C

U0046 — Vehicle Communication Bus C

Detailed page for trouble code U0046.

33,355codes
59brands
10,894generic
22,461specific
Reset
Code

U0046

MERCEDES-BENZ U — Network/User

Vehicle Communication Bus C

Views: UK: 18 EN: 32 RU: 14
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Open or short in CAN/LIN wiring for Bus C
  • Failed CAN/LIN transceiver in one or more control modules
  • Missing or incorrect termination resistor(s) on the bus
  • Corroded/damaged connectors or poor ground/power to a node
  • High bus load or electrical noise from aftermarket equipment
  • Faulty module (gateway/module hardware) or incorrect/old software calibration

Symptoms

  • One or more control modules report "no communication" or set related U-codes
  • Warning lights and messages for systems on Bus C (may include comfort, gateway, ADAS or body functions)
  • Intermittent or permanent loss of functions controlled by modules on Bus C
  • Possible battery drain or inability to perform module programming if gateway unresponsive

What to check

  • Read all stored and pending DTCs from all control modules and note freeze-frame/occurrence data
  • Identify which modules report lost messages and whether multiple modules report Bus C faults
  • Perform a visual inspection of wiring, connectors and grounding points along Bus C trunk and at modules
  • With vehicle key on (engine off) measure idle voltages on CAN_H and CAN_L for Bus C at a connector near the gateway
  • Measure termination resistance across CAN_H and CAN_L (typical ~60 Ω for two 120 Ω terminators in parallel)
  • Check for shorts to battery voltage or ground on CAN_H/CAN_L (resistance and voltage tests)

Signal parameters

  • Typical CAN recessive voltage: CAN_H ≈ 2.5 V, CAN_L ≈ 2.5 V (vehicle dependent)
  • Typical CAN dominant voltages: CAN_H ≈ 3.5 V, CAN_L ≈ 1.5 V during active frames (approximate)
  • Differential voltage during dominant state ≈ 2.0 V ±0.5 V
  • Termination resistance across CAN_H and CAN_L ≈ 60 Ω (two 120 Ω terminators in parallel)
  • Bus data rate varies by vehicle and network (e.g., 125/250/500 kbps or other - check manufacturer spec)

Diagnostic algorithm

  1. Record all U-codes and freeze-frame info from every module and note which modules are offline or reporting Bus C faults.
  2. Check vehicle service information for the topology and pinouts of Bus C (which modules are on this bus, bus length, termination location, data rate).
  3. Visually inspect harnesses, splice points and connectors for damage, corrosion or water ingress; repair obvious issues.
  4. With key on, engine off, measure CAN_H and CAN_L voltages at gateway and at end-node connectors; compare to expected values from service data.
  5. Measure termination resistance across CAN_H/CAN_L to confirm ~60 Ω; if out-of-range, locate and test terminators or open circuits.
  6. Check for shorts to 12 V or ground (measure resistance to battery + and - with connectors unplugged).
  7. Disconnect suspect modules one at a time (or isolate network segments via service connector) to identify a module that causes the bus to fail when connected (watch for bus voltage normalization).
  8. If a specific module is suspected, verify module power and ground, inspect connector pins, and bench-test or replace module transceiver if available.
  9. Check for software/calibration updates or known network bugs and reflash/update gateway and affected modules per manufacturer guidance.
  10. After repairs, clear codes, perform full communication check and road test to confirm no re-occurrence. If intermittent, perform extended monitoring with scope/trace log.
  11. Safety note: avoid probing live circuits with power applied in ways that could short CAN lines; follow vehicle manufacturer safety procedures.

Likely causes

  • Damaged harness or connector at a module on Bus C
  • Faulty CAN transceiver inside a control module
  • Loss of bus termination (open or shorted resistor)
  • Module losing power or ground causing communication loss

Fault status

⚠️ Status
Bus C communication fault — messages missing or invalid. One or more modules on Bus C are not communicating normally.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

HTML Workshop Manuals AI manual library for MERCEDES-BENZ Click to show available manuals 25

MERCEDES-BENZ 2015 B Electric Drive

HTML Manual
B Electric Drive Years: 2015 Manual in English Sections: 28,208 AI chunks: 28,208
Short description
MERCEDES-BENZ · B Electric Drive · 2015

MERCEDES-BENZ 2000 C 230K (Motor 111)

HTML Manual
C 230K Years: 2000 Manual in English Sections: 17,064 AI chunks: 17,064
Short description
MERCEDES-BENZ · C 230K · 2000 · (Motor 111)

MERCEDES-BENZ 2000 C 280 (Motor 112)

HTML Manual
C 280 Years: 2000 Manual in English Sections: 17,367 AI chunks: 17,367
Short description
MERCEDES-BENZ · C 280 · 2000 · (Motor 112)

MERCEDES-BENZ 2000 C 43 AMG (Motor 113)

HTML Manual
C 43 AMG Years: 2000 Manual in English Sections: 16,253 AI chunks: 16,253
Short description
MERCEDES-BENZ · C 43 AMG · 2000 · (Motor 113)

MERCEDES-BENZ 2000 CL 500 113

HTML Manual
CL 500 Years: 2000 Manual in English Sections: 16,205 AI chunks: 16,205
Short description
MERCEDES-BENZ · CL 500 · 2000 · 113

MERCEDES-BENZ 2000 CLK 320 (Motor 112)

HTML Manual
CLK 320 Years: 2000 Manual in English Sections: 15,746 AI chunks: 15,746
Short description
MERCEDES-BENZ · CLK 320 · 2000 · (Motor 112)

MERCEDES-BENZ 2000 CLK 320 Cabriolet (Motor 112)

HTML Manual
CLK 320 Cabriolet Years: 2000 Manual in English Sections: 15,736 AI chunks: 15,736
Short description
MERCEDES-BENZ · CLK 320 Cabriolet · 2000 · (Motor 112)

MERCEDES-BENZ 2000 CLK 430 (Motor 113)

HTML Manual
CLK 430 Years: 2000 Manual in English Sections: 15,643 AI chunks: 15,643
Short description
MERCEDES-BENZ · CLK 430 · 2000 · (Motor 113)
Your experience will help others
+100 karma for a short comment :)
Send to email