C1695 – CAN message failure – FATC (Hyundai)

C1695 means your Hyundai has lost a required CAN-network message from the FATC system. Most owners notice HVAC problems first. You may lose accurate blower control, temperature control, or A/C requests. In some cases, the dash may show HVAC-related warning behavior. According to Hyundai factory diagnostic data, this code indicates “CAN message failure – FATC.” This is a manufacturer-specific chassis DTC. The exact module that sets it can vary by model and platform. Treat it as a direction to test the network and module communication. Do not replace parts until you confirm power, ground, and CAN integrity.

C1695 Quick Answer

C1695 on Hyundai points to a CAN communication failure involving the FATC (Fully Automatic Temperature Control) messages. Diagnose the CAN network, FATC power/ground, and related connectors before replacing any module.

What Does C1695 Mean?

Official definition: “CAN message failure – FATC.” In plain terms, one control module expected to hear HVAC control data from the FATC module, but it did not. In practice, the vehicle may limit HVAC operation or ignore some A/C and temperature commands. The code does not prove the FATC unit failed.

What the module checks: the receiving module monitors for specific FATC CAN messages at the correct timing and with valid content. When those messages stop, arrive corrupted, or fall outside expected timing, it flags C1695. Why it matters: this DTC points to a communication path problem first. You must confirm network health, module power and ground, and connector condition before you condemn the FATC or any other ECU.

Theory of Operation

On Hyundai vehicles, the FATC panel acts as more than switches. It shares cabin temperature requests, blower commands, and A/C enable requests over the CAN network. Other modules use that data to coordinate compressor control, idle-up logic, and defrost strategies.

C1695 sets when the expected FATC message stream stops or becomes invalid. A power or ground drop at the FATC can silence it. A CAN-H/CAN-L wiring fault can block or distort messages. Another module can also disrupt the network if it shorts the bus, loads it down, or loses its termination integrity.

Symptoms

Symptoms vary by Hyundai platform, but communication-related patterns stay consistent.

• Scan tool behavior FATC may not appear in the ECU list, may show “no response,” or may drop out intermittently.
• HVAC control Temperature does not change as commanded, or the system defaults to a fixed mode.
• Blower operation Blower speed may stick high, stick low, or ignore AUTO changes.
• A/C request A/C may not engage, cycles unexpectedly, or the A/C indicator does not match operation.
• Defrost logic Defrost or mode door operation may act delayed or inconsistent.
• Cluster messages Some models display HVAC-related warnings or disable certain climate features.
• Intermittent behavior Symptoms change with bumps, temperature, or steering column movement due to connector tension.

Common Causes

• FATC module offline on the CAN network: If the Full Auto Temperature Control module stops transmitting, other Hyundai modules log a CAN message failure for FATC.
• Loss of power feed or ignition feed to the FATC: A blown fuse, failing relay, or poor power distribution prevents the FATC from waking up and sending messages.
• High-resistance FATC ground connection: Corrosion or a loose ground can let the FATC power up partially, then drop out under load and trigger message loss.
• CAN-H or CAN-L open circuit between FATC and the network: An open in either CAN line breaks communication, so expected FATC messages never arrive.
• CAN-H to CAN-L short or a short to ground/battery: A short collapses bus signaling and blocks normal messages, often creating multiple communication DTCs.
• Connector issues at the FATC or junction connectors: Spread terminals, water intrusion, or fretting causes intermittent contact and “no signal” or “erratic” message failures.
• Aftermarket equipment interfering with the CAN bus: Remote start, alarm, audio, or telematics splices can load the bus or introduce poor connections near the HVAC stack.
• Network-wide fault (another module pulling the bus down): A different module or harness short can disrupt the entire CAN segment, and the symptom shows up as missing FATC messages.
• Incorrect configuration or variant coding (FTB 2E Not Configured where applicable): A replaced module or incorrect coding can prevent expected FATC message IDs from matching what the receiving module expects.

Diagnosis Steps

Use a scan tool that can run a Hyundai network scan and show HVAC/FATC data and DTC subtypes. Have a DVOM for voltage-drop testing and a back-probing kit. A two-channel oscilloscope helps confirm CAN integrity fast. Use current service information for connector views and splice locations on your Hyundai platform.

1. Confirm DTC C1695 and record all stored and pending DTCs across modules. Save freeze frame data and note ignition state, vehicle speed, battery voltage, and any companion CAN or HVAC codes. Freeze frame shows conditions when the fault set. Use a scan tool snapshot later to catch an intermittent dropout during a wiggle test or road test.
2. Run a full network scan and verify whether the FATC appears as a responding module. If the scan tool cannot communicate with FATC, treat the issue as “module offline” first. If FATC responds, compare timestamps and note which module logged C1695. That tells you who missed the message.
3. Check the Hyundai power distribution basics before probing any module pins. Inspect HVAC-related fuses, IG/ACC feeds, and any junction block signs of heat. Load-test fuses with the circuit powered. Do not rely on visual checks alone.
4. Verify FATC power and ground under load using voltage-drop testing. Command the blower or A/C request ON to load the circuit. Measure ground drop from FATC ground pin to battery negative and keep it under 0.1V with the circuit operating. Measure power-side drop from battery positive to the FATC power feed while loaded. A good-looking ground can fail only under load.
5. Inspect FATC and nearby harness routing with your eyes and hands. Focus on the center stack area, behind the control head, and any sharp brackets. Look for pinched wiring, previous radio work, liquid intrusion, or signs of terminal fretting. Unplug connectors and check for backed-out pins and spread terminals.
6. Use the scan tool to evaluate live data from FATC if communication exists. Watch for module resets, implausible status changes, or comm counters dropping to zero. If the scan tool offers “CAN bus off” or “communication error count,” use it. An intermittent reset often points to power/ground, not CAN wiring.
7. Check CAN physical layer at the FATC connector with ignition ON. Measure CAN bias voltage only with the circuit powered, because bias does not exist key-off. If your Hyundai uses multiple CAN networks, verify you test the correct CAN pair for the FATC. Use the wiring diagram to confirm CAN-H and CAN-L pins.
8. Scope the CAN-H and CAN-L signals with ignition ON and the network awake. Look for a clean differential waveform and stable amplitude. A noisy, flat, or “stuck” line points to a short, excessive loading, or a module pulling the bus down. If the waveform collapses when you connect the FATC, suspect the module or its connector.
9. Isolate the fault if the bus shows a problem. Disconnect the FATC and recheck bus behavior at an accessible point. If the network recovers with FATC unplugged, inspect FATC connector pins and harness for shorts first. Only after wiring checks should you suspect an internal FATC fault.
10. If FATC stays online but C1695 returns, focus on message expectation and configuration. Check for FTB subtype clues when available. For example, FTB 31 “No Signal” fits a missing message, while 1C “Erratic/Intermittent” fits dropouts. If you see 2E “Not Configured,” verify variant coding and installed options match the vehicle.
11. Confirm the repair. Clear DTCs, run the same ignition mode that set the code in freeze frame, and repeat a network scan. Perform a road test if the code set at speed, then recheck for pending and stored codes. Remember: some communication faults store as pending first, while a hard network fault often returns immediately on key-on.

Professional tip: On Hyundai communication faults, the fastest separator is “FATC missing” versus “network disrupted.” A module that disappears from the network scan usually lost power/ground or crashed. A module that stays present while others log C1695 often points to CAN wiring integrity or configuration. Always prove power and ground with voltage-drop under load before condemning the FATC.

Possible Fixes

• Restore FATC power supply: Replace the failed fuse or relay and repair the underlying short or overload that caused it.
• Repair high-resistance ground: Clean and tighten the ground point, repair damaged ground wiring, and confirm less than 0.1V drop under load.
• Repair CAN wiring faults: Fix opens, shorts, or chafed sections in CAN-H/CAN-L, then verify normal scope patterns with ignition ON.
• Service connectors and terminals: Correct backed-out pins, replace spread terminals, and address water intrusion at the FATC or junction connectors.
• Remove or correct aftermarket interference: Rework poor splices, relocate connections, or remove devices that load the Hyundai CAN network.
• Perform correct configuration where applicable: Program or code the module to match vehicle options when FTB 2E “Not Configured” fits the evidence.
• Replace the FATC only after verification: If power/ground and CAN circuits test good and the network recovers when FATC disconnects, replace the module and recheck network health.

Can I Still Drive With C1695?

You can usually drive with C1695, but expect reduced HVAC control. This Hyundai manufacturer-specific chassis code means a module lost CAN messages from the FATC (Front Automatic Temperature Control) system. When that message stream drops out, other modules stop trusting HVAC-related inputs and status. The vehicle still steers, brakes, and accelerates normally in most cases. Comfort features may degrade fast, especially defrost performance. Do not ignore windshield fogging risk. If the blower, mode doors, or A/C logic acts erratically, limit driving in rain or cold. Treat this as a network communication fault first. Confirm network integrity before replacing the FATC control head.

How Serious Is This Code?

C1695 ranges from inconvenience to a visibility and comfort issue. Most drivers notice weak or stuck temperature control. Many also lose AUTO mode behavior. The bigger concern comes from defrost strategy. Some Hyundai platforms share HVAC requests with other controllers over. That includes A/C request, blower status, or compressor cut logic. The code itself does not prove a failed module. Per SAE J2012-DA, the DTC message points to a suspected trouble area only. If the CAN fault also sets multiple “no signal” style codes (FTB 0x04 subtype 31) across modules, treat it as a broader network problem. Diagnose power, ground, and CAN wiring before any parts.

Common Misdiagnoses

Technicians often replace the FATC control head because the scan tool labels it. That wastes money when the real issue sits in the CAN backbone. Another common mistake involves chasing blower or actuator complaints first. Those symptoms can result from missing CAN messages. Many also overlook the FTB suffix meaning. With DTC Format Identifier 0x04, an FTB like 31 (“No Signal”) or 1C (“Erratic/Intermittent”) changes the plan. “No signal” pushes you toward power, ground, and network continuity checks. “Intermittent” pushes you toward connector tension, moisture intrusion, and harness movement tests. Avoid guessing. Prove the communication loss with a network scan and module ping test.

Most Likely Fix

The most common confirmed repair direction for C1695 involves restoring reliable CAN communication with the FATC module. Start by verifying FATC power and ground under load. Perform a voltage-drop test at the FATC connector while operating HVAC loads. Next, inspect and test the CAN High and CAN Low circuits to the FATC for open circuits, shorts, or high resistance at connectors and splice points. If the scan tool cannot communicate with the FATC while other modules respond, focus on FATC power/ground and its local CAN branch. Only consider module replacement after you prove correct power, ground, and network signals at the module pins.

Repair Costs

Repair cost depends on whether the confirmed root cause is wiring, connector condition, a sensor, a module, or the labor needed to diagnose the fault correctly.

Last updated: March 31, 2026