A damaged, corroded, or loose electrical connector at the intake manifold runner position sensor or at the module that reports its signal.; Wiring harness damage such as chafing, pinched wires, or broken strands between the sensor and its control module, often near the intake manifold or engine mount.; A failed intake manifold runner position sensor that no longer powers up or communicates on the network.; A faulty control module or network gateway that has lost the ability to relay the sensor's message to other modules.; Low battery voltage or a weak charging system causing modules to drop offline intermittently and set communication codes.; Water intrusion or oil contamination in the sensor connector or harness, common on engines with intake manifold runner actuators.; Aftermarket electrical accessories or poor ground connections that introduce noise or voltage drops on the communication bus.

DTC codes / U06xx · Network communication / U064F

U064FLost Communication With Intake Manifold Runner Position Sensor Bank 1

U064F is a network communication code indicating that a control module on the vehicle's Controller Area Network (CAN) bus has lost contact with the intake manifold runner position sensor on bank 1. The computer detected that the expected periodic messages from that sensor, or from the module that reports its position, stopped arriving within the required time window, so it flagged the sensor as missing rather than reporting an out-of-range reading.

SystemNetwork

Code typeGeneric (all makes)

SeverityMedium

Fix difficultyIntermediate

AreaNetwork communication

Symptoms you may notice

Illumination of the check engine light or service vehicle soon message, often with no other noticeable symptoms.
Rough or unstable idle quality, especially when the engine is cold, because the intake manifold runner may default to a fixed position.
Reduced engine performance or a flat spot during acceleration if the runner stays in the wrong position.
A stored communication code in multiple modules, sometimes accompanied by a U-code for the module that hosts the sensor.
Intermittent drivability complaints that come and go with temperature or vibration, matching the intermittent loss of communication.
No start or extended crank in rare cases if the lost sensor shares a communication path with a module needed for engine start.

Common causes, most likely first

A damaged, corroded, or loose electrical connector at the intake manifold runner position sensor or at the module that reports its signal.
Wiring harness damage such as chafing, pinched wires, or broken strands between the sensor and its control module, often near the intake manifold or engine mount.
A failed intake manifold runner position sensor that no longer powers up or communicates on the network.
A faulty control module or network gateway that has lost the ability to relay the sensor's message to other modules.
Low battery voltage or a weak charging system causing modules to drop offline intermittently and set communication codes.
Water intrusion or oil contamination in the sensor connector or harness, common on engines with intake manifold runner actuators.
Aftermarket electrical accessories or poor ground connections that introduce noise or voltage drops on the communication bus.

How to diagnose and fix it

Perform a full scan of all modules to confirm U064F is current and to see whether other communication codes point to a shared power, ground, or bus fault.
Inspect the intake manifold runner position sensor connector and the module connector for corrosion, loose pins, or pushed-out terminals, and clean or reseat as needed.
Check battery voltage and charging system output, then clear the code and test-drive to see whether low voltage was the trigger.
Wiggle-test the harness between the sensor and its module while watching live data or the code status to expose an intermittent wiring fault.
Measure resistance and continuity on the sensor's power, ground, and signal circuits, comparing to factory specifications, and repair any open or shorted wire.
If wiring and connectors are good, substitute a known-good sensor or perform a bidirectional actuator test to confirm whether the sensor itself has failed.
After repair, clear all codes, verify communication returns, and complete a drive cycle to confirm U064F does not reset.

What most technicians miss on U064F

This code often appears after a low-voltage event such as a jump start or a weak battery, and the sensor itself is fine once the charging system is repaired.
A single failed module on the network can set U064F in several other modules, so the code does not always mean the intake manifold runner sensor is the faulty part.
Corrosion inside the sensor connector can cause an intermittent loss of communication that only shows up in damp weather or after a car wash.
Technicians sometimes replace the intake manifold runner sensor when the real fault is a chafed harness near the engine mount or a poor ground shared with other sensors.
U064F can be stored alongside performance codes for the intake manifold runner, and clearing the communication code without fixing the underlying wiring will let it return.

Can I keep driving with U064F?

The vehicle is generally safe to drive to a repair shop because the engine will default to a fixed runner position, but avoid heavy acceleration or towing until the fault is repaired. If the engine runs rough, stalls, or other modules also report communication loss, stop driving and have the electrical system checked promptly.

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.