U0669

Lost Communication With Central Gateway Module 'B'

U0669 is a generic OBD-II network diagnostic trouble code: Lost Communication With Central Gateway Module 'B'. It is logged by the engine control unit when the network monitor detects that a specific fault threshold has been exceeded — typically resulting in the malfunction-indicator lamp (MIL / check-engine light) being illuminated.

Code
U0669
Group
Network
System
Network
Severity
Warning (MIL on, possible limp mode)
Need U0669 disabled?
RaceTune permanently disables any OBD-II trouble code on supported ECUs — for motorsport, off-road, and export use.
→

What U0669 means

U0669 is set when a module on the vehicle network loses contact with Central Gateway Module B. Modern vehicles use one or more gateway modules to route messages between separate CAN bus domains such as powertrain, body, chassis, and infotainment. A second gateway unit (designated B) appears on platforms with extended network topologies, including full-size trucks, large SUVs, and vehicles with extensive chassis electronics.

Loss of Gateway B communication can cascade into multiple simultaneous lost-communication codes across many modules because the gateway bridges inter-domain message routing. If the powertrain bus depends on Gateway B to receive chassis or body inputs, drivability symptoms such as limited throttle or transmission hold may appear, elevating the severity of this fault beyond a simple warning.

Diagnosis requires identifying the physical location of Gateway B, verifying its power and ground, and inspecting all bus connections at the module. Given the potential cascade effect, always start with a full scan and map all active codes before attempting any repairs.

Common causes

Most-frequently reported root causes when U0669 is logged.

  • 1
    Gateway B power supply fuse open or voltage feed interrupted.
  • 2
    Poor or corroded ground connection at the Gateway B mounting location.
  • 3
    Open or shorted CAN bus wiring on any segment connected to Gateway B.
  • 4
    Internal processor failure within Gateway B.
  • 5
    Damaged wiring harness connector at the gateway module.
  • 6
    Partial software update leaving Gateway B in an incompatible state.
  • 7
    Failed CAN termination resistor on a segment routed through Gateway B.

Symptoms drivers notice

MIL and multiple other warning lamps active simultaneously.
Large number of lost-communication DTCs stored across many modules.
Possible limited throttle, transmission limp mode, or stability control degradation.
Scan tool may be unable to reach modules on the bus domain served by Gateway B.
Instrument cluster may display multiple system-unavailable messages.

How to diagnose U0669

A typical diagnostic flow when this code is present.

  1. 1
    Record all DTCs across all modules; a large cluster of U-codes often points to a gateway or bus fault rather than individual module failures.
  2. 2
    Verify whether Gateway B appears on the module list of the scan tool.
  3. 3
    Check Gateway B power supply fuses and measure supply voltage at the module connector.
  4. 4
    Inspect all CAN bus wiring and connectors at Gateway B for damage or corrosion.
  5. 5
    Measure CAN Hi and CAN Lo voltages on each bus segment at the gateway connector.
  6. 6
    Perform a gateway software version check and compare against current calibration to detect a partial update.
  7. 7
    Replace or reprogram Gateway B only after confirming all wiring and power are within specification.

Related network codes

Frequently asked questions

Why do so many codes appear at once when U0669 is stored?

A gateway bridges multiple bus domains; when it goes offline, every module on each side loses messages from modules on the other side, generating a cascade of lost-communication codes.

Can U0669 cause the vehicle not to start?

Unlikely on most platforms, but if a start-authorisation message passes through Gateway B, an immobiliser or anti-theft system may be affected.

Should I replace all modules that have lost-communication codes?

No. When a gateway fails, most of the other codes are secondary effects; restore gateway communication first and re-scan before making further repairs.

Is Gateway B programmable?

Yes. Replacement gateway modules almost always require VIN-specific programming or configuration using an OEM scan tool before the vehicle network operates correctly.

Disabling U0669 in software

RaceTune can permanently disable U0669 — and any other OBD-II diagnostic trouble code — on every ECU family we support. The monitor is disabled inside the ECU itself, so the fault stops being logged: the warning light stays off and the engine never enters limp mode for this code. The change is tied to your exact software version.

Permanent
The monitor is disabled in the ECU itself — not just cleared. It cannot return.
Tailored to your file
Each patch is matched to your specific software version — never a one-size-fits-all file.
Reversible
The original file is always preserved. Reflash the stock to return the ECU to factory state.

Software modifications affect emissions compliance and are not road-legal in many jurisdictions. RaceTune service files are intended for motorsport, off-road, and export use.

Got U0669 in your scan?

Upload your ECU file — we'll identify the exact software version and confirm whether a disable is available for your car.

Upload your file