U0164 – CAN Communication bus with fully automatic temperature control (FATC) (timeout)

U0164 means your vehicle lost communication with the Fully Automatic Temperature Control (FATC) module on the CAN network for long enough to time out. For most drivers, that shows up as HVAC problems first. You may lose automatic climate control, get stuck on one temperature, or see the blower act wrong. The engine often still runs normally, but comfort features can degrade fast. According to factory diagnostic data, this code indicates a CAN communication timeout involving the FATC controller. This is a network fault type. It points to a suspected communication path issue, not a confirmed bad module.

U0164 Quick Answer

The U0164 code points to a CAN bus timeout with the FATC (automatic HVAC control) module. Check FATC power/ground and its CAN wiring at the module connector before condemning the controller.

What Does U0164 Mean?

U0164 is a network communication loss code. The vehicle’s other control modules expected to hear messages from the Fully Automatic Temperature Control (FATC) module, but they did not. In plain terms, the car “can’t see” the automatic HVAC controller on the network. That can disable auto climate functions, cause incorrect air distribution, or trigger HVAC warnings on the dash.

Technically, “timeout” means a module monitors CAN message traffic and flags U0164 when FATC messages stop arriving within an expected time window. The code does not prove the FATC failed. A power feed dropout, a weak ground, corrosion in the connector, or a CAN circuit fault can all produce the same timeout. Diagnosis must confirm whether the FATC is offline, the network segment is damaged, or another module drags the bus down.

Theory of Operation

On vehicles with fully automatic temperature control, the FATC module commands the blower, air mix doors, mode doors, and A/C requests based on cabin targets. It exchanges data with other modules over the CAN bus. Typical shared data includes engine operating status, compressor enable requests, blower requests, ambient temperature data, and body control status. The instrument cluster may also display HVAC status using network messages.

U0164 sets when that message flow breaks. A hard power loss at the FATC will take it off the bus. A high-resistance ground can let the module “boot loop” and drop off intermittently. A shorted CAN wire, poor terminal tension, or water intrusion can corrupt traffic and prevent valid communication. In some cases, another module or a damaged harness can load the CAN network and make the FATC appear missing.

Symptoms

U0164 symptoms usually show up as HVAC control loss or scan tool communication issues with the climate module.

• Scan tool: FATC/HVAC module missing from the module list, shows “no communication,” or drops out during a network scan
• Climate control: automatic mode inoperative or reverts to manual default settings
• Airflow control: mode doors stuck (defrost only, floor only, or panel only) or air distribution does not match the display
• Temperature control: stuck hot or stuck cold, or temperature changes do not respond to knob/button inputs
• Blower operation: blower stuck on one speed, intermittent blower, or blower works only after cycling the key
• Dash indicators: HVAC warning message, flashing HVAC indicators, or climate panel resets intermittently

Common Causes

• FATC module power feed issue: A blown fuse, weak relay contact, or voltage drop on the ignition feed can reboot the FATC and trigger a timeout.
• FATC module ground high resistance: Corrosion or a loose ground point can let the module power up but fail under load, which stops CAN messaging.
• CAN bus open circuit near the HVAC/FATC harness: A pulled pin, broken wire, or poor splice can interrupt CAN-H/CAN-L, so other modules stop receiving FATC messages.
• CAN bus short to ground or short to power: Chafed wiring can clamp the network and block communication, which sets U0164 as a timeout.
• Connector terminal fit or fretting at the FATC connector: Light oxidation and poor pin tension create intermittent contact that drops messages without fully killing module power.
• Water intrusion at the dash/HVAC control head area: Moisture can bridge terminals and raise resistance, which disrupts network traffic and module operation.
• Network interference from another module or aftermarket accessory: A shorted module, remote start, radio, or alarm tap can corrupt bus traffic and make the FATC appear offline.
• Incorrect module configuration after replacement or programming: A misconfigured or uninitialized HVAC control head may stay on the network but fail to transmit the expected messages.
• Control module internal fault (rare): An internal transceiver or logic fault can prevent the FATC from responding even when power, ground, and bus wiring test good.

Diagnosis Steps

Tools: a scan tool that can run a full network scan, a DVOM for voltage-drop testing, and the correct wiring diagrams for the CAN bus and FATC power/ground. Use back-probing leads and terminal test tools to avoid damage. A lab scope helps confirm bus activity, but you can still verify many faults with careful DVOM checks.

1. Confirm the U0164 code and record freeze-frame data and code status. Focus on ignition state, vehicle speed, and any related network codes that show which modules also lost communication.
2. Run a full network scan and note whether the FATC appears and communicates. If it does not show up, treat the problem as power/ground, connector, or bus wiring until proven otherwise.
3. Check for pending vs confirmed/stored U0164 and document which modules report it. Type B communication faults may need two trips to confirm, while a hard network or power fault often returns immediately after clearing.
4. Inspect fuses, power distribution, and any HVAC-related relays before probing the module. Verify the fuse has power on both sides with the key in the same position shown in freeze frame.
5. Verify FATC power and ground under load using voltage-drop tests, not just continuity. Command the HVAC on and check ground drop stays under 0.1V while the circuit operates, then check power feed drop from battery positive to the module feed.
6. Perform a targeted visual inspection of the FATC control head connector and nearby harness routing. Look for backed-out terminals, pin fit issues, water tracks, and chafe points around brackets and the steering column area.
7. With ignition ON, check CAN bus integrity at the FATC connector or a nearby splice point. Ignition-off readings do not provide a valid reference because CAN bias voltage only appears when the network powers up.
8. If the scan tool cannot reach the FATC, isolate the network segment methodically. Disconnect suspected aftermarket devices first, then unplug modules on the same bus one at a time while watching for network recovery.
9. Use continuity and short checks only after you confirm power and ground integrity. Test CAN-H and CAN-L for opens between the FATC connector and the next known junction, then test for shorts to power or ground.
10. Use a scan tool snapshot during a road test if the fault acts intermittent. Freeze frame shows when U0164 set, while a snapshot captures live dropouts when you hit bumps, change blower speed, or cycle ignition.
11. After repairs, clear codes, rerun the network scan, and confirm the FATC stays online. Complete a drive cycle and recheck for pending codes before returning the vehicle.

Professional tip: When U0164 sets, do not start by replacing the HVAC control head. Prove power and ground with voltage-drop under load first, then prove the bus can carry messages with ignition ON. Most repeat comebacks come from a loose terminal or a weak ground that “tests good” with no load.

Possible Fixes

• Repair power feed or ground issues to the FATC module, including cleaning and tightening the ground point.
• Repair CAN bus wiring faults such as opens, chafing shorts, or poor splices near the dash harness.
• Clean, reseat, and tension-test FATC and network connectors, then address any water intrusion sources.
• Remove or rewire aftermarket accessories that load or corrupt the CAN network.
• Reconfigure, program, or replace the FATC module only after verifying power/ground and CAN circuit integrity.

Can I Still Drive With U0164?

You can often drive with a U0164 code, but expect HVAC problems. The vehicle usually runs and shifts normally because this is a network fault, not a direct powertrain fault. Still, loss of communication with the Fully Automatic Temperature Control (FATC) can remove automatic temperature regulation. You may get stuck on full hot, full cold, or defrost defaults. In cold weather, that can become a visibility issue if defrost control fails. In hot weather, cabin comfort drops fast and can distract the driver. If you also see multiple U-codes, a no-start, or repeated battery drains, park it and diagnose the network. Those patterns point to a wider CAN issue, not just a climate control complaint.

How Serious Is This Code?

U0164 ranges from inconvenience to a real safety concern. It stays mostly an inconvenience when the only effect is lost auto climate control or intermittent HVAC display glitches. Severity increases when the system defaults to defrost only, loses blower control, or cannot manage windshield clearing. A CAN timeout can also appear during low voltage events. That matters because low voltage can trigger several modules to drop offline. If you see U0164 with other communication codes, treat it as a network health problem. Diagnose it before it strands the vehicle. When the code sets as “confirmed” and returns quickly after clearing, you should expect an active fault.

Common Misdiagnoses

Techs commonly replace the HVAC control head or the FATC module too early. A timeout code does not prove the module failed. Power, ground, or a wake-up feed can drop out and make a good module look dead. Another frequent miss involves ignoring battery and charging system condition. Low system voltage causes CAN nodes to reset and stop talking. Shops also chase the wrong bus. Some vehicles route HVAC messages through a gateway module, so a gateway issue can mimic “FATC offline.” Finally, people clear codes and call it fixed without checking pending codes and a network scan. If the module still shows “not responding,” the fault remains.

Most Likely Fix

Most confirmed U0164 repairs start with restoring stable power and ground to the FATC control module or HVAC panel. That includes blown fuses, loose grounds, or high resistance at the connector. The next common direction involves CAN wiring integrity near the HVAC module, dash harness, or any recent accessory install. Look for backed-out terminals, corrosion, or pin fit issues that create an intermittent open. Only after the module powers and grounds test good under load, and the CAN circuits pass basic checks, does module replacement or programming become a rational next step. Verify communication before you buy parts.

Repair Costs

Network and communication fault repairs vary by root cause — wiring/connectors are often the source, but module-level repairs or replacements can be significantly more expensive.

Last updated: April 2, 2026