HomeTrouble CodesU0642

U0642 — Lost Communication Evap System Pressure Sensorswitch Circuit B

Generic OBD-II · all makesNetwork / communication

OBD-II code U0642 indicates the powertrain control module (PCM) has lost communication on the data network with the evaporative emission (EVAP) system pressure sensor/switch Circuit B. This is a network communication fault, not a fuel-system performance fault, meaning the sensor is either not responding on the bus or its power/ground/network wiring is disrupted. The code commonly appears alongside other EVAP-related codes and is most frequently caused by wiring or connector problems rather than a failed sensor.

Symptoms

What causes it — most likely first

1. Damaged or corroded wiring/connector to the EVAP pressure sensor B

Chafed, broken, water-intruded, or corroded harness and pins on the sensor connector or CAN/power/ground wiring are the most frequent cause of a 'Lost Communication' code.

2. Failed EVAP system pressure sensor/switch (Circuit B)

The sensor itself can fail internally so that it no longer responds on the network or no longer produces a valid signal to the module reading it.

3. Loss of power or ground to the sensor

A blown fuse, broken ground strap, or shared ground point failure will prevent the sensor from powering up and communicating, even if the wiring to it is intact.

4. Network (CAN bus) issues affecting this node

A short, open, or high resistance on the CAN high/low circuits servicing the EVAP sensor can keep it offline and generate a lost-communication fault.

5. Moisture or contamination in the EVAP pressure sensor port/hose

Water intrusion, a cracked hose, or a stuck/damaged sensor port can produce a no-response condition on some systems, especially after a fuel fill or cold soak.

6. Fault in the control module (PCM/ECM)

An internal failure of the module that interfaces with the sensor is the least common cause and should be considered only after every wiring, connector, power, ground, and sensor test has been ruled out.

How it's diagnosed

  1. Scan the vehicle for all stored and pending codes, including those from other modules, and record freeze-frame data for U0642.
  2. Visually inspect the EVAP pressure sensor B connector, harness, and routing for corrosion, bent pins, chafing, or damage; repair as needed and clear codes to recheck.
  3. Verify battery voltage and check the sensor's dedicated fuse, power supply, and ground using a wiring diagram for the specific vehicle.
  4. With the connector disconnected, test the sensor's internal resistance/spec or apply the manufacturer-specified test to confirm whether the sensor itself has failed.
  5. If power, ground, and the sensor test good, check the CAN/network wiring between the sensor and the control module for shorts to power, ground, or opens, including resistance measurements of the bus.
  6. Only after all of the above pass should the control module be suspected; recheck for TSBs, software updates, and module DTCs before considering replacement.

Code facts & related codes

SystemNetwork / communication
StandardizationSAE generic — identical on every make

Frequently asked

Is replacing the PCM the right fix for U0642?

Usually not. U0642 is a lost-communication code, and the large majority of cases are caused by wiring, connector, power/ground, or sensor faults. The PCM is the least likely cause and should only be considered after all of the above have been ruled out with proper testing.

Can I keep driving with U0642 stored?

In most cases, yes. The vehicle typically still runs and drives normally, but the EVAP emissions monitor will be incomplete, which can cause a failed emissions or smog inspection until the fault is repaired.

Does U0642 mean my gas cap is loose?

Not directly. A loose or leaking gas cap usually sets a different code (commonly P0455 or P0442). U0642 points specifically at communication with the EVAP pressure sensor Circuit B rather than a simple vapor leak, although a damaged seal or hose near that sensor can contribute.

Will clearing the code fix the problem?

No. Clearing or erasing the code only removes the stored information temporarily; the code will return as soon as the same condition is detected on the next drive cycle, which is why proper diagnosis of the wiring, power, ground, and sensor is required.