01 Factors Affecting Start-Stop System Functionality in Vehicl… • 02 B0017 and B0018: Right Front or Passenger Frontal Deploymen… • 03 How to choose the best engine oil for your car • 04 Car Won't Start or Running Rough? Don't Ignore a Faulty Cam… • 05 This Is Why Your Car’s Door Locks Keep Flickering • 06 What Happens When Car Safety Systems Fail • 07 Why Idling Your Car to Warm It Up Might Be a Waste of Fuel … • 08 That Rotten Egg Smell From Your Exhaust Isn't Normal: Here'… • 09 B0035 and B0036: Airbag Deployment System Closed or Shorted… • 10 What Happens When You Press the Start Push Button While the… •

DTC codes / U06xx · Network communication / U060B

U060BLost Communication With Turbocharger/Supercharger Boost Sensor A

U060B is a generic network communication code indicating that a control module on the vehicle's Controller Area Network (CAN) bus has lost contact with the turbocharger or supercharger boost sensor A. The computer detected that expected messages from that sensor, or from the module that relays its data, stopped arriving within the required time window, so it flagged the communication failure rather than a direct sensor performance fault.

SystemNetwork
Code typeGeneric (all makes)
SeverityMedium
Fix difficultyIntermediate
AreaNetwork communication

Symptoms you may notice

  • Illumination of the check engine light or a service vehicle soon message, often with no other noticeable symptoms.
  • Reduced engine power or a limp-home mode because the powertrain control module lacks boost pressure data.
  • Poor acceleration or sluggish throttle response, especially during merging or uphill driving.
  • Rough running, hesitation, or an unexpected drop in fuel economy.
  • In some vehicles, the boost gauge or driver information display shows no reading or a default value.
  • Intermittent warning light that clears and returns, particularly after rain, bumps, or temperature changes.

Common causes, most likely first

  1. Damaged, corroded, or loose electrical connector at the boost sensor itself.
  2. Chafed, pinched, or open wiring in the sensor's signal or power circuit.
  3. Failed boost sensor that no longer communicates on the network.
  4. Faulty or unpowered control module that acts as the gateway for the boost sensor data.
  5. Blown fuse or poor ground connection shared by the sensor or its module.
  6. CAN bus wiring fault, such as a short to ground or between the bus lines, disrupting messages.
  7. Software or calibration issue in a module that intermittently drops the boost sensor message.

How to diagnose and fix it

  1. Scan all modules for stored codes and record freeze-frame data to see whether the communication loss is continuous or intermittent.
  2. Inspect the boost sensor connector and harness for corrosion, loose pins, or chafing, and clean or repair as needed.
  3. Check the sensor's power, ground, and signal circuit with a multimeter or oscilloscope against the manufacturer's specification.
  4. Verify battery voltage and condition, then check fuses and grounds that feed the sensor and its control module.
  5. Perform a wiggle test on the harness while watching live data to expose an intermittent connection.
  6. If wiring and power are good, substitute a known-good boost sensor and clear codes to see whether U060B returns.
  7. If the fault persists, check the module that relays the sensor data and inspect the CAN bus for shorts or opens using a breakout box or oscilloscope.

What the boost sensor code really means

  • U060B is a communication code, not a performance code, so replacing the boost sensor without checking the connector and wiring often fails to fix the problem.
  • A weak or failing battery can cause multiple U-codes, including this one, because modules drop offline when voltage sags during cranking.
  • The boost sensor may share a five-volt reference or ground with other sensors, so a fault in that shared circuit can set U060B along with codes for those sensors.
  • Aftermarket electrical accessories tapped into the harness near the boost sensor can introduce noise or a short that intermittently kills communication.
  • Some vehicles require a relearn or module reset after repairing the circuit, and the code may remain stored until a full drive cycle completes.

Can I keep driving with U060B?

The vehicle is usually safe to drive to a repair shop, but avoid heavy acceleration, towing, or long trips because the engine may enter limp mode without warning. If the engine runs poorly or stalls, stop driving and have the vehicle towed.

Tools that help

Tools we recommend are in the Auto Veteran shop on Amazon. As an Amazon Associate we earn from qualifying purchases.

Guidance is general and written for all OBD-II vehicles. Exact tests and values vary by model, so confirm the fault before replacing parts.

Running on fumes Free guides aren't free to make. Top up the tank. Any amount, one time. Fuel the Garage