Skip to main content
OBD-II Diagnostic Trouble Code
U0001

High Speed CAN Communication Bus

U
Network
modules / CAN bus
0
Generic
SAE standard
0
Network subsystem
01
High Speed CAN Communication Bus
Severity · general guide
High
The high-speed bus carries engine, brake, and stability data — a real bus fault can cause no-start, limp mode, or loss of ABS/ESC, so treat it promptly.
Code type
Generic
System
Network
Standard
ISO/SAE Controlled
Fault type
Communication Loss
Quick answer

Do not treat as minor. If the engine runs and no limp or safety lights are active, drive only to get it diagnosed; a genuine CAN-C fault can strand you or disable ABS and stability control without warning. U0001 is a general fault on the High Speed CAN (CAN-C) communication bus — the 500 kbps two-wire data backbone that links the powertrain, ABS, and other high-priority modules. A controller has detected the bus circuit itself as open, shorted to ground, or shorted to voltage, so this is a wiring/bus-integrity code, not a fault inside one specific module.

What U0001 means

The high-speed CAN-C bus is a twisted pair — CAN-High and CAN-Low — that carries time-critical messages such as engine speed, throttle, brake, and stability-control data between modules at 500 kilobits per second. The line is terminated by two 120-ohm resistors, which read as roughly 60 ohms measured across the pair, and every controller watches the differential signal continuously while the ignition is on. U0001 sets when a module sees the bus circuit go open, short to ground, or short to supply voltage, which corrupts or halts communication for everyone sharing that segment. Because the fault is in the shared wiring or a bus-off condition rather than a single named module, U0001 is deliberately broad: it points you at the harness, connectors, terminating resistors, and module power/grounds instead of at one component.

Symptoms

  • A cluster of warning lights lit at once — check-engine, ABS, traction/stability, and often airbag or EPS lamps — because many modules lose their shared data at the same time
  • Multiple U-codes stored across several modules (lost-communication and bus-off faults) that all appear together during a scan
  • Hard-start, no-start, or crank-no-run if the engine controller can no longer exchange the messages it needs to run
  • Limp-home or reduced-power operation as modules fall back to safe defaults when the bus data is missing
  • Gauges, warning lamps, HVAC, or infotainment behaving erratically or freezing as bus traffic drops out
  • A scan tool that struggles to connect to, or cannot see, one or more modules on the high-speed bus

Common causes

  • An open, short-to-ground, or short-to-voltage in the CAN-C twisted pair — chafed or pinched harness wiring, a broken conductor, or damage from prior repair work (the most common trigger)
  • Corroded, backed-out, or loose terminals and connectors at any module, splice, or the diagnostic connector on the bus segment
  • A failed or out-of-spec terminating resistor, so the pair no longer reads its expected ~60 ohms and signal quality collapses
  • Poor power supply or ground to the Body Control Module or the module that logged the code, making it drop off or corrupt the bus
  • Related upstream faults — battery-voltage, ignition-run, or VIN-broadcast message DTCs — that must be fixed before this code can be validated
  • Water intrusion into a connector or harness section causing an intermittent short across CAN-H and CAN-L
  • A single internally failed module dragging the whole bus down (confirmed only after wiring and power/grounds check out)

Severity & driving advice

Severity: High — The high-speed bus carries engine, brake, and stability data — a real bus fault can cause no-start, limp mode, or loss of ABS/ESC, so treat it promptly.

Can I drive? Do not treat as minor. If the engine runs and no limp or safety lights are active, drive only to get it diagnosed; a genuine CAN-C fault can strand you or disable ABS and stability control without warning.

Diagnostic approach

  1. Confirm the code is active and battery voltage is healthy — Make sure system voltage is in the 10-16 V window the module requires, then cycle the ignition on and read active DTCs with a full-system scan tool. This code is monitored continuously with the key on, so a truly active U0001 should be present, not just stored history.
  2. Record every module's codes and fix the prerequisites first — Scan all controllers and note which one set U0001 and what else is stored bus-wide. Repair any battery-voltage, ignition, or VIN-message faults first — the factory bus-integrity test is only valid once those prerequisites are satisfied, and clearing them often clears U0001.
  3. Verify power and ground to the BCM and the reporting module — Check the feeds and grounds for the Body Control Module and the controller that logged the fault. A weak ground or low supply can pull a module off the bus or make it broadcast a corrupt differential signal that looks like a bus short to the others.
  4. Measure CAN-C bus resistance and inspect the wiring — With the ignition off and battery disconnected, measure across CAN-High and CAN-Low; roughly 60 ohms confirms both 120-ohm terminators and continuity, near 120 ohms points to a lost terminator or open, and near 0 ohms indicates a short between the wires. Inspect the twisted pair, splices, and connectors for chafing, corrosion, backed-out pins, and water intrusion.
  5. Isolate a short or bus-off by disconnecting modules one at a time — If resistance or scope readings show a short or a bus-off condition, disconnect modules on the segment individually and re-measure to find whether one controller is loading down or shorting the bus. Watch for the fault clearing the moment a specific module is unplugged.
  6. Follow the bus-off performance path, then clear and road-test — On Stellantis vehicles an active U0001 routes into the U0002 (CAN-C Bus Off Performance) procedure and the stored-lost-communication routine; work those to pinpoint the failed segment. After the repair, clear all modules, cycle the key, and drive through the conditions that set the code to confirm it stays gone across the whole network.

FAQ

Is U0001 a bad module or a wiring problem?

U0001 is a bus-integrity code, so it points first at the shared CAN-C wiring, connectors, terminating resistors, and module power/grounds — not at one specific module. A failed controller can drag the bus down, but that is confirmed only after the harness, resistance, and grounds all check out. Replacing a module blindly is the wrong first move.

How is U0001 different from U0100 or the other 'lost communication with X' codes?

U0001 describes a fault on the high-speed CAN-C bus circuit itself — an open or short affecting the whole pair. The U01xx codes like U0100 name a specific module (for example, lost communication with the ECM/PCM). U0001 is broader and usually appears alongside a cluster of those module-specific codes when the shared bus goes down.

What should the CAN-C bus measure across CAN-High and CAN-Low?

With the system powered down, a healthy high-speed CAN bus reads about 60 ohms across the pair, because its two 120-ohm terminating resistors sit in parallel. Around 120 ohms suggests one terminator or a wire is open, and a reading near zero indicates the two wires are shorted together.

Can U0001 cause a no-start?

Yes. The high-speed bus carries the messages the engine controller and immobilizer need to run. If the bus is open or shorted, the required data may never arrive, so the vehicle can crank without starting or refuse to start at all until the bus fault is repaired.

Why did several unrelated warning lights come on with U0001?

Every module on the high-speed bus shares the same real-time data. When that traffic is disrupted, the ABS, stability, cluster, powertrain, and other controllers each detect the loss and light their own warning, so one bus fault can illuminate many lamps at once.