U1663 – Ethernet application server 3 for system 1 infotainment no communication (Skoda)

Skoda-specific code — factory diagnostic data

U1663 means the Skoda network cannot talk to part of the infotainment Ethernet system. In the Enyaq, that often shows up as missing media, screen features that do not load, or intermittent infotainment faults before you notice any deeper network issue. According to Skoda factory diagnostic data, this code indicates “Ethernet application server 3 for system 1 infotainment no communication.” That makes this a manufacturer-specific Skoda code, not a universal definition. The fault tells you the 19-Gateway lost communication with a specific infotainment-side Ethernet function. It does not prove a failed module. You must confirm whether power, ground, wake-up, connector condition, or the Ethernet path caused the loss.

U1663 Quick Answer

U1663 sets when the 19-Gateway on a Skoda no longer receives expected communication from infotainment Ethernet application server 3 for system 1. In plain terms, the gateway sees an infotainment network node go offline or stop responding.

What Does U1663 Mean?

The official Skoda definition is “Ethernet application server 3 for system 1 infotainment no communication.” In practice, the gateway expects that infotainment-related server function to be present and exchange data. When it does not, the gateway stores U1663 and related infotainment functions may become unavailable, slow, or unstable.

Technically, the 19-Gateway monitors network participation and message availability on the vehicle communication architecture. For this code, it is not measuring a bad speaker, bad display, or bad app directly. It is detecting the absence of expected communication from a defined Ethernet-based infotainment participant. That matters because diagnosis must focus on network integrity, power and ground to the affected node, connector condition, and module wake-up logic before any module replacement decision.

Theory of Operation

Under normal conditions, the Skoda Enyaq uses the 19-Gateway to supervise communication between vehicle networks and the infotainment domain. Ethernet carries high-data infotainment traffic more efficiently than older low-bandwidth networks. The gateway expects certain infotainment servers or control functions to appear on the network, respond within normal timing, and remain available during operation.

This code sets when that normal exchange breaks down. The problem can come from a powered-down infotainment node, a poor ground, a connector issue, damaged wiring, or a fault in the Ethernet communication path. A software issue can also stop the node from joining the network correctly. The gateway only reports the communication loss. It does not identify the root cause by itself.

Symptoms

Communication loss in this area usually affects infotainment operation first, and the scan tool often reveals the issue before the driver notices every missing feature.

• Scan tool behavior: The infotainment-related node may appear offline, missing, or intermittent in the control module list.
• Infotainment faults: Media, navigation, online services, or app-based functions may fail to load or may restart unexpectedly.
• Startup delay: The center display or related infotainment functions may take longer than normal to boot.
• Function dropout: Audio sources, phone integration, or connected services may work intermittently and then disappear.
• Stored network codes: The gateway may store additional communication faults that point to the same infotainment network event.
• Intermittent reset: The infotainment system may reboot, freeze, or recover only after a key cycle or sleep cycle.
• Customer complaint pattern: The issue may worsen after low battery events, recent software work, or connector disturbance during other repairs.

Common Causes

• Application server power supply loss: A blown fuse, weak feed, or interrupted wake-up supply can keep the infotainment Ethernet application server 3 offline.
• Poor module ground path: High resistance at a ground point can let the module power up intermittently and then drop off the network.
• Ethernet twisted-pair wiring damage: An open, short, pinched, or chafed Ethernet pair can stop data exchange between the infotainment server and the 19-Gateway.
• Connector terminal spread or corrosion: Loose or oxidized terminals add resistance and disrupt the high-speed network signal even when the connector looks plugged in.
• Water intrusion in infotainment area wiring: Moisture at connectors or harness junctions can create intermittent communication loss and multiple network faults.
• Gateway or infotainment software issue: A coding, adaptation, or software fault can make the 19-Gateway report a missing Ethernet participant that is not responding correctly.
• Network wake-up failure: If the infotainment subnet does not wake when commanded, the gateway will log no communication with the expected Ethernet server.
• Internal application server fault: The server itself can stop booting or stop transmitting on the Ethernet network after power and wiring faults are ruled out.

Diagnosis Steps

You need a capable scan tool with full Skoda network topology access, service information, a digital multimeter, and preferably a lab scope. Use the scan tool to compare installed module lists, related faults, and live network status. For intermittent faults, save both freeze frame data and a manual snapshot during operation, because they serve different purposes.

1. Confirm U1663 in the 19-Gateway and record all stored, pending, and related network DTCs. Review freeze frame for vehicle speed, ignition state, and companion communication faults. Freeze frame shows the exact conditions when the code set. A manual snapshot helps catch an intermittent drop during your road test or key-cycle test.
2. Check the vehicle network scan and see whether the infotainment Ethernet participant tied to application server 3 appears online. Then inspect the related fuses, power distribution, and wake-up feeds before you probe the module. If the server never appears on the network map, focus first on power supply, grounds, and the Ethernet path.
3. Verify module power and ground with the circuit loaded. Do not trust an unloaded voltage reading or a simple continuity test. Perform voltage-drop testing on the ground side while the circuit operates. Keep ground drop below 0.1 volt. A weak ground can look normal at rest and fail only under load.
4. Inspect the infotainment-related connectors and harness routing carefully. Look for backed-out terminals, bent pins, moisture, green corrosion, terminal spread, and harness damage near sharp edges or trim mounts. On a Skoda Enyaq, pay close attention to any area where interior trim pressure or previous accessory work could stress the network wiring.
5. Check whether the affected module wakes up and stays awake during key cycles and scan tool requests. Compare live data and network status with other infotainment-related control units. If the gateway repeatedly drops only this Ethernet server while others stay stable, isolate that module path rather than condemning the whole infotainment system.
6. Test the Ethernet communication circuit according to the Skoda wiring diagram. Check each conductor for opens, shorts to ground, shorts to power, and shorted pairs. Use connector-end isolation when needed. If you measure communication line voltage levels, take those readings with ignition on, because powered network bias is the only valid reference.
7. Wiggle-test the harness and connectors while monitoring module presence on the scan tool. Do not rely on stored codes alone. Watch for the application server to appear and disappear during movement. That pattern usually points to terminal tension loss, internal connector damage, or a harness break inside the insulation.
8. Review coding, adaptations, and software level only after power, ground, and wiring checks pass. A gateway can report no communication when a control unit sits offline from a software or configuration issue, but that conclusion comes after you verify the electrical side first.
9. If all external checks pass, isolate the suspect module from the network only as service information allows, then retest network behavior. If the rest of the infotainment Ethernet network stabilizes and the application server still will not communicate with verified power, ground, and wiring, the module becomes the likely fault area.
10. Clear the codes and confirm the repair with multiple key cycles, a full network scan, and an operational check of infotainment functions. Make sure U1663 does not return as pending or confirmed. On hard communication faults, the code usually returns quickly if the problem remains.

Professional tip: Do not replace the infotainment server because the scan tool says “no communication.” On this Skoda fault, the code identifies a missing network participant, not the root cause. Prove power feed quality, ground integrity, connector condition, and Ethernet circuit integrity before you condemn a module.

Possible Fixes

• Repair the power feed fault: Restore the blown fuse circuit, damaged feed, or failed wake-up supply that keeps the infotainment application server offline.
• Correct the ground problem: Clean, tighten, or repair the affected ground path after voltage-drop testing confirms excess resistance.
• Repair Ethernet wiring or terminals: Fix the open, short, corrosion, or terminal tension issue in the twisted-pair network circuit.
• Clean and reseat affected connectors: Remove moisture, corrosion, or pin fit problems that interrupt communication between the server and gateway.
• Repair harness damage: Restore chafed, pinched, or stretched wiring where trim, brackets, or previous repairs damaged the network path.
• Perform required software or configuration correction: Update or correct coding only after electrical and network integrity checks prove the hardware path is sound.
• Replace the failed application server only after verification: Install a module only when power, ground, network wiring, and configuration all test good and the server still will not communicate.

Can I Still Drive With U1663?

You can usually drive an Enyaq with U1663 if the fault only affects the infotainment Ethernet network. In most cases, this code points to lost communication with an infotainment application server, not a brake, steering, or propulsion controller. Expect feature loss instead of a no-start or stall. The screen may reboot, navigation may fail, online services may drop out, and some menu-driven vehicle functions may become unavailable. Still, do not dismiss it. Skoda integrates many convenience functions through shared network paths and gateway management. If the vehicle shows multiple network faults, repeated battery drain, gateway communication issues, or abnormal module wake-up behavior, stop using it until you test the network. Drive it only if basic vehicle functions remain normal and no critical warning messages appear.

How Serious Is This Code?

U1663 ranges from moderate inconvenience to a broader network concern. On the mild end, it causes infotainment problems only. That includes blank displays, missing audio, phone pairing failures, and unstable connected services. In that situation, the code is irritating but not usually a direct safety issue. The seriousness rises fast if the 19-Gateway logs several communication faults at the same time. That pattern can indicate a power supply issue, connector trouble, Ethernet wiring damage, water intrusion, or a control unit that fails to wake up or stays awake too long. Those faults can create battery drain, module resets, and loss of user access to vehicle settings. Treat the code as a network fault first, not as proof of a failed infotainment unit. Confirm power, ground, wake-up behavior, and Ethernet circuit integrity before you replace any module.

Common Misdiagnoses

Technicians often replace the display, head unit, or an application server too early. That mistake happens because the scan description sounds module-specific. In reality, the 19-Gateway only reports that communication stopped. It does not prove why. A weak power feed, poor ground, partial connector spread, moisture at an inline connection, or disturbed Ethernet twisted-pair integrity can all set the same code. Another common error is checking for battery voltage with no load and calling the circuit good. Network modules need clean supply and ground under operating load. Shops also miss intermittent wake-up faults after software updates or low-voltage events. Avoid wasted spending by scanning the full vehicle, checking related U-codes, verifying whether the target module responds directly, and load-testing its power and ground before touching parts.

Most Likely Fix

The most common repair direction is restoring reliable communication to the affected infotainment server path, not immediately replacing a module. On Skoda platforms, that usually means correcting a power or ground fault at the infotainment server or repairing Ethernet wiring or connector issues between the server and the network path monitored by the 19-Gateway. If the wiring, supply, ground, and connector fit all test good, then software recovery or module replacement becomes a valid next step. After any repair, clear the fault and verify operation through several key cycles and a normal drive period. The exact confirmation time varies because enable criteria differ by platform. Use service information and scan-tool fault status to confirm the monitor runs and 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.

Last updated: April 11, 2026