01317 – Instrument cluster control module No communication (Audi)

Audi-specific code — factory diagnostic data

01317 means the radio on an Audi TT cannot talk to the instrument cluster control module. In plain terms, the radio loses contact with the cluster over the vehicle network, so related display, coding, or shared data functions may stop working even if the car still starts and drives normally. According to Audi factory diagnostic data, this code indicates Instrument cluster control module No communication. This is a manufacturer-specific Audi code, not a universal SAE fault meaning. The exact network path and module arrangement can vary by Audi platform, so the code identifies a communication problem area, not a failed cluster.

01317 Quick Answer

On Audi vehicles, 01317 means the 56-Radio module no longer receives expected communication from the instrument cluster control module. The fault points to a network, power, ground, coding, or module availability problem that you must verify before replacing any part.

What Does 01317 Mean?

The official Audi definition is Instrument cluster control module No communication. In practice, the radio has stopped hearing from the cluster, so the radio flags a communication loss and stores 01317.

For diagnosis, separate the message from the cause. The code tells you what the radio detected, not why it happened. The radio monitors network communication with other modules and expects valid data or message traffic from the cluster. When that message path fails, times out, or drops off the bus, the radio sets this code. That matters because the fault can come from the cluster itself, the data bus, power or ground loss to one module, connector problems, or an installation and coding issue on the Audi network.

Theory of Operation

Under normal conditions, the Audi TT instrument cluster does more than show speed and warning lamps. It also acts as a network participant that shares status information with other modules. The 56-Radio uses that shared communication for functions that depend on cluster presence, gateway routing, and module identification on the vehicle bus.

This code appears when that normal message exchange stops. The radio does not prove that the cluster failed internally. It only proves the radio could not communicate with the cluster when it expected to. On Audi systems, that breakdown can come from an open data line, a shorted network circuit, weak module power or ground, poor connector contact, or a cluster that stays offline. If the stored fault includes FTB -049, treat that suffix as subtype information only. In this context, it supports a no signal style communication loss and strengthens the need to verify the network path first.

Symptoms

Communication faults between the radio and cluster often show up first during a full vehicle scan.

• Scan tool behavior: The instrument cluster may fail to respond, drop out intermittently, or show communication errors in multiple modules.
• Radio functions: The radio may lose shared display features, retained settings, or proper interaction with vehicle information.
• Cluster behavior: The instrument cluster may reset, stay dark, act erratically, or show related warning indicators.
• Multiple stored faults: Other Audi modules may also log no-communication codes for the cluster at the same time.
• Intermittent operation: The fault may appear only during startup, after battery events, or while driving over bumps.
• Coding complaints: Replacement radio or cluster concerns may appear after module installation, battery disconnect, or configuration work.
• Network side effects: Convenience or infotainment features that rely on shared data may act inconsistently.

Common Causes

• Instrument cluster power loss: A blown fuse, weak power feed, or poor ignition supply can take the Audi cluster offline and make 56-Radio log no communication.
• Instrument cluster ground fault: High resistance at a cluster ground point can let the module wake up poorly or drop off the data bus intermittently.
• Open circuit in the communication wiring: A broken wire between the cluster and the Audi network can stop message traffic even when the cluster still has power and ground.
• Shorted communication line: A short to ground, short to power, or short between network wires can block normal bus bias and prevent the radio from seeing the cluster.
• Loose or corroded connector terminals: Terminal spread, oxidation, or water intrusion at the cluster, radio, or junction connectors can create intermittent loss of communication.
• Aftermarket radio or wiring disturbance: Incorrect radio installation or tapped wiring can disturb shared power, ground, or data circuits on the Audi TT.
• Low system voltage during start-up: A weak battery or unstable charging system can drop one module offline long enough for the radio to store 01317.
• Network disruption from another module: A different control unit on the same Audi communication network can pull the bus down and make the cluster appear missing.
• Instrument cluster internal failure: Internal circuit faults in the cluster can stop communication, but you must prove power, ground, and network integrity first.

Diagnosis Steps

Use a scan tool that can access all Audi modules, not just generic OBD-II data. You also need wiring information, a digital multimeter, a test light, and backprobing tools. For this communication fault, compare freeze frame data to current conditions. Focus on vehicle speed, ignition state, and any related DTCs. Freeze frame shows when the code set. A scan tool snapshot helps catch an intermittent dropout during testing.

1. Confirm 01317 in 56-Radio and record all stored, pending, and related network codes. Save freeze frame data, especially vehicle speed, ignition state, and companion module faults. Run a full network scan and see whether the instrument cluster appears on the scan tool list.
2. Check battery condition, charging performance, and all relevant fuses before you probe the cluster. Inspect the power distribution path and visible harness routing first. Because this is a communication code, verify whether the cluster stays online during key cycles and whether the fault returns immediately on key-on. A hard fault often returns at once under continuous monitoring.
3. Verify instrument cluster power and ground under load. Do not trust unloaded voltage or simple continuity tests. Use voltage-drop testing with the circuit operating. Ground drop should stay below 0.1 volt. A high-resistance feed or ground can show normal voltage with no load and still knock the module offline.
4. Inspect the cluster connector, radio connector, splice points, and any accessible network junctions. Look for loose terminals, corrosion, backed-out pins, water entry, and harness damage. Pay close attention to areas behind the dash and around any aftermarket radio work on the Audi TT.
5. Use the scan tool to attempt direct communication with the instrument cluster. If the tool connects, review live data and module identification. If communication drops in and out, wiggle-test the harness and connectors while watching module presence on the scan tool.
6. Check the communication line condition with ignition on. Bias voltage only exists with the network powered, so ignition-off readings do not give a valid reference for line voltage. Compare both network wires to ground and look for a pulled-up or pulled-down circuit that suggests a short.
7. If service information shows a CAN-based network path for this circuit on the Audi platform you are testing, measure CAN resistance with ignition off and the battery disconnected. Measure between CAN+ and CAN- at an accessible module connector. A healthy bus reads about 60 ohms. An open on one conductor often moves the reading toward 120 ohms or OL.
8. Reconnect the battery, switch ignition on, and check CAN bias voltage if the cluster communicates over CAN on that Audi platform. A healthy network typically shows about 2.5 volts on both CAN+ and CAN- to ground at rest. If one line stays pinned high or low, isolate the shorted branch or module.
9. If the cluster does not communicate but power, ground, and network tests pass, isolate the fault by unplugging suspect modules one at a time only if service information supports that method. Watch for bus recovery and for the cluster to reappear on the network scan.
10. After repairs, clear codes and cycle the ignition several times. Repeat the full network scan. Road test the vehicle while monitoring module presence. Use a manual scan tool snapshot if the fault acts intermittent. Then confirm 01317 does not reset in 56-Radio.

Professional tip: On Audi communication faults, do not condemn the instrument cluster because one module reports it missing. The reporting module only tells you it lost contact. First prove the cluster lost power, lost ground, lost network access, or stopped transmitting. That test order prevents expensive misdiagnosis.

Possible Fixes

• Repair the verified open, short, or high-resistance fault in the communication wiring between the instrument cluster and the Audi network.
• Clean, tighten, or replace damaged connector terminals at the cluster, radio, fuse panel, or network junction after you confirm poor terminal contact.
• Restore proper cluster power or ground by fixing the failed fuse feed, corroded splice, or high-resistance ground connection found during voltage-drop testing.
• Correct wiring errors from an aftermarket radio installation if added equipment disturbed shared power, ground, or communication circuits.
• Repair the underlying low-voltage problem if battery or charging instability caused modules to drop offline during start-up.
• Replace or reprogram the instrument cluster only after you verify that power, ground, and network circuits remain correct under load and the cluster still fails to communicate.
• Repair or isolate another network module that drags the bus down if disconnect testing and circuit checks prove it causes the cluster communication loss.

Can I Still Drive With 01317?

You usually can drive an Audi TT with 01317 present, but you should not ignore it. This code means the 56-Radio module lost communication with the instrument cluster control module. That often affects information sharing, not basic engine operation. Still, the cluster is a central gateway for warnings, status messages, and driver information on many Audi platforms. If the cluster shows other faults, goes blank, resets, or loses multiple functions, stop and inspect the power and network issue first. Driving becomes a poor choice when other modules also drop offline, warning lamps act abnormally, or the vehicle shows signs of a wider communication problem.

How Serious Is This Code?

01317 ranges from an inconvenience to a significant electrical fault, depending on what else fails with it. In the mild case, the radio simply cannot exchange data with the cluster, so display integration or convenience functions stop working. In the more serious case, the lost communication points to a shared power, ground, or data bus problem. That can affect multiple control modules on the Audi network. The code itself does not prove the cluster failed. It only identifies a suspected trouble area. Treat it as more serious when the scan tool cannot reach several modules, the cluster behaves erratically, or the TT shows repeated low-voltage symptoms. Confirm the network condition before replacing any module.

Common Misdiagnoses

Technicians often replace the instrument cluster or radio too early. That wastes money and usually misses the real fault. On Audi vehicles, this code commonly appears after low system voltage, battery disconnect events, water intrusion, or connector problems. Another frequent mistake involves scanning only the radio and stopping there. You need a full module map. If the scan tool reaches the cluster normally, the issue may be intermittent, stored history, or limited to one communication path. If the scan tool cannot reach the cluster, verify cluster power, ground, fuse feeds, and network integrity before condemning the unit. Always inspect connectors for spread terminals and corrosion, especially in known moisture-prone areas.

Most Likely Fix

The most common confirmed repair direction is restoring proper power, ground, or network continuity to the instrument cluster or the radio circuit involved in communication. That may mean cleaning and tightening a poor ground, repairing a damaged data wire, correcting connector terminal fit, or fixing a fuse feed problem. On some Audi TT cases, battery voltage instability also triggers stored communication faults, so charging system condition and voltage retention matter. Cluster or radio replacement only becomes a valid path after the scan tool findings, wiring checks, and module power and ground tests prove the hardware cannot communicate correctly under normal conditions. After repair, drive the vehicle through the operating conditions that allow the affected network fault logic to run and confirm the code stays gone.

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.