U1054 – Information electronics 1 control unit no communication (Skoda)

Skoda-specific code — factory diagnostic data

U1054 means the Skoda network cannot talk to the Information electronics 1 control unit. In real life, that often shows up as infotainment-related features not responding, missing menu functions, or a control unit that will not appear on a scan. According to Skoda factory diagnostic data, this code means Information electronics 1 control unit no communication. On an Enyaq, the 19-Gateway logs this fault when it stops receiving expected communication from that module. That description points to a communication loss, not a confirmed bad control unit. Diagnosis must prove whether the problem comes from power supply, ground, wiring, connector issues, software state, or the network path itself.

U1054 Quick Answer

U1054 on a Skoda Enyaq means the 19-Gateway cannot communicate with the Information electronics 1 control unit. Start by proving module power, ground, connector condition, and network integrity before you replace any electronics.

What Does U1054 Mean?

The official Skoda definition says the Information electronics 1 control unit has no communication. That means the gateway expected to exchange data with that module and could not. In practice, the vehicle may lose infotainment-related functions, related settings access, or proper communication with systems that depend on that module being online.

Technically, the 19-Gateway monitors network participation and message availability from other modules. It does not identify the root cause by code text alone. This DTC tells you what the gateway detected, not which part failed. The fault can come from a sleeping or crashed control unit, missing power or ground, high resistance at a connector, damaged network wiring, or a wider network segment problem. That distinction matters, because the repair depends on what stopped the module from talking.

Theory of Operation

Under normal conditions, the 19-Gateway manages message traffic between the Enyaq’s onboard networks and keeps track of which modules are present. The Information electronics 1 control unit powers up, joins the network, and exchanges regular data with the gateway and other modules. The gateway uses that communication to support system coordination, diagnostics, and feature availability.

This code sets when that normal message exchange stops. The breakdown can happen because the module never wakes up, loses B+ or ground, drops off the bus, or remains physically connected but cannot transmit valid messages. A network fault elsewhere can also block communication to that module. That is why a complete check includes module wake-up status, fuse feed, loaded ground quality, connector fit, and bus integrity, not just a quick module swap.

Symptoms

Communication loss to this Skoda module can show up in both scan data and vehicle operation.

• Scan tool: Information electronics 1 does not respond, appears missing from the module list, or drops in and out during a full vehicle scan.
• Infotainment functions: The center display, media features, connected menus, or related user settings may freeze, reboot, or stay unavailable.
• Stored faults: The 19-Gateway and other dependent modules may log communication DTCs tied to missing data from information electronics.
• Intermittent behavior: The fault may appear after key cycles, during wake-up, or after the vehicle goes to sleep and wakes again.
• Feature loss: Functions routed through the information electronics path may stop working or respond slowly.
• Warning messages: The driver may see system unavailable messages tied to infotainment or convenience features.
• Battery draw concerns: A module that crashes or fails to sleep can create communication faults and abnormal standby behavior.

Common Causes

• Loss of power feed to the information electronics 1 control unit: An open fuse, weak power distribution point, or high-resistance supply circuit can shut the module down and make the 19-Gateway report no communication.
• Poor ground at the information electronics 1 control unit: A corroded or loose ground can let the module wake up inconsistently, reset during operation, or drop off the network.
• CAN bus open circuit: An open in one network conductor can prevent reliable message exchange between the information electronics 1 control unit and the Skoda gateway.
• CAN bus short to ground, short to power, or short between bus wires: A network short can pull bus bias out of range and block communication for one module or multiple modules.
• Connector corrosion or terminal spread: Moisture, oxidation, or loose terminal tension at the module or inline connector can create intermittent contact and trigger U1054.
• Harness damage in a flex or pinch area: Chafed wiring, trim pressure, or previous repair damage can interrupt power, ground, or CAN circuits to the information electronics module.
• Gateway-side network issue: A fault in the 19-Gateway connector, power supply, or network branch can make the Enyaq gateway lose contact with the addressed control unit.
• Control unit internal failure: Internal electronics failure can stop the information electronics 1 module from booting, staying awake, or transmitting on the network, but you must prove all external circuits first.

Diagnosis Steps

You need a capable scan tool that can perform a full network scan, view installed module lists, and capture snapshots. Use a wiring diagram, a digital multimeter, and backprobing tools. A lab scope helps with intermittent CAN faults. For resistance checks, disconnect battery power and follow Skoda service precautions before unplugging network modules.

1. Confirm U1054 in the 19-Gateway and record all stored, pending, and related network codes. Save freeze frame data, especially ignition state, vehicle speed, and any companion communication faults. Freeze frame shows the exact conditions when the DTC set. A scan tool snapshot serves a different job. Use it later during a road test if the fault acts intermittent.
2. Run a complete network scan before any deep circuit testing. Check whether the information electronics 1 control unit appears on the scan tool module list. Then inspect the relevant fuses and power distribution feeds for that module and the 19-Gateway. If the module does not appear at all, treat that as a hard communication loss and verify the power supply path first.
3. Verify power and ground at the information electronics 1 control unit under load. Do not trust unloaded voltage or continuity alone. Perform voltage-drop testing with the circuit operating. Ground drop should stay below 0.1 volt with the circuit loaded. A weak feed or high-resistance ground can let the module look powered while it actually resets or stays offline.
4. Inspect the module connector, gateway connector, and harness routing. Look for backed-out pins, water entry, green corrosion, terminal spread, and signs of trim pressure or rub-through. Pay close attention to areas that move, bend, or sit near sharp brackets. On the Skoda Enyaq, network faults often come down to connection quality, not the module itself.
5. With ignition off and the battery disconnected, measure resistance between CAN+ and CAN- at an accessible connector on the affected network branch. A healthy terminated CAN bus reads about 60 ohms. A reading near 120 ohms or OL points to an open or missing termination on one side. A very low reading suggests a shorted bus or a failed module pulling the network down.
6. Reconnect battery power and switch ignition on. Measure CAN bias to ground on both bus wires at an accessible point. Healthy high-speed CAN typically sits near 2.5 volts on both lines at rest. Ignition-off readings do not count here because the network bias only appears when the circuit powers up. If one line stays low, high, or fixed, isolate the short or open before condemning any control unit.
7. Check whether the information electronics 1 control unit wakes up and communicates intermittently during key cycles. Watch live network status in the gateway if the scan tool supports it. Compare module presence after connector movement, harness flexing, and light tap testing near suspect areas. If communication returns during movement, focus on a connection fault rather than a software assumption.
8. If the module still stays offline, isolate the fault path with directed circuit tests. Verify continuity end to end on each CAN conductor only after you disconnect both ends of the circuit. Check for short-to-ground and short-to-power on each line. If service information shows splices or branch connectors, inspect those points closely because one poor branch can create a single-module no-communication code.
9. If the module powers up correctly and the bus checks pass, evaluate gateway reporting and installation status with the scan tool. Confirm the 19-Gateway coding and installed module map align with the vehicle equipment. On some Skoda platforms, a coding mismatch, incomplete setup, or post-repair configuration issue can make the gateway flag a module as missing even when wiring remains intact.
10. After repairs, clear the codes and run another full network scan. Verify the information electronics 1 module communicates normally, no related U-codes return, and all monitored functions operate as expected. If the original fault was intermittent, use a scan tool snapshot during a drive or key-cycle test to confirm stable communication under the same conditions shown in freeze frame.

Professional tip: Do not replace the information electronics 1 control unit just because U1054 names it. Per SAE J2012 logic, the code identifies a trouble area, not a root cause. On a communication fault, prove power, ground, connector integrity, and CAN network health first. A module that lacks clean power or a stable bus will look failed even when it is not.

Possible Fixes

• Repair the module power supply circuit: Replace the failed fuse, correct the open feed, or restore the high-resistance power distribution connection only after testing confirms the supply fault.
• Clean and secure the ground path: Repair the ground eyelet, terminal, or splice if voltage-drop testing shows excessive resistance under load.
• Repair damaged CAN wiring: Fix the open, short, or chafed section in the network pair and protect the harness against repeat damage.
• Service corroded or loose connectors: Correct terminal fit, remove corrosion, and repair water intrusion at the information electronics 1 module, gateway, or inline connection point.
• Correct gateway configuration issues: Update installation coding or complete required setup only if scan-tool checks show the module hardware and circuits are sound.
• Replace the information electronics 1 control unit: Replace the module only after you verify proper power, ground, network integrity, and configuration, and the module still fails to communicate.

Can I Still Drive With U1054?

You can usually drive a Skoda Enyaq with U1054 if the vehicle starts, shifts normally, and no critical warning messages appear. This code means the 19-Gateway lost communication with the Information Electronics 1 control unit. That often affects infotainment, convenience features, or related network functions more than core propulsion. Still, do not treat it as harmless. A network fault can spread if power supply, ground integrity, or CAN wiring has a larger issue behind it. If the Enyaq shows multiple communication faults, repeated resets, battery drain, or missing driver information, limit use until you test the network. Driveability may stay normal, but system availability and fault escalation can change quickly.

How Serious Is This Code?

U1054 ranges from an inconvenience to a higher-priority electrical fault, depending on what else the Skoda network is doing. On its own, it often points to a loss of communication with the Information Electronics 1 module, so the driver may notice infotainment problems, screen issues, missing settings, or functions that stop responding. That scenario rarely creates an immediate safety risk. The picture changes when the 19-Gateway logs several U-codes at once, the module drops off the network repeatedly, or other control units lose data they expect. In that case, the fault may involve shared power, shared grounds, water intrusion, or bus wiring trouble. Those conditions can affect more than one system. Treat the code as more serious if the vehicle shows gateway faults, low-voltage history, intermittent no-start events, repeated control unit resets, or widespread communication loss. Diagnose it soon, because network faults seldom fix themselves and often worsen with heat, moisture, vibration, or battery state changes.

Common Misdiagnoses

Technicians often misread U1054 as proof that the Information Electronics 1 control unit has failed. That mistake drives unnecessary module replacement. On a Skoda platform, the 19-Gateway only reports that communication stopped. It does not identify the root cause. Another common error is checking scan results once, seeing the module offline, and stopping there. Intermittent wake-up problems, weak battery support, poor grounds, connector tension loss, or bus faults can all make a healthy module disappear. Some shops also overlook topology context and fail to compare which modules share the same fuse feed, splice, ground point, or network branch. Others clear codes too early and erase freeze-frame clues about when the dropout occurred. The fix is straightforward: verify battery condition, confirm power and ground under load, inspect the connector and harness, check network integrity, and then see whether the module communicates consistently before any replacement decision.

Most Likely Fix

The most common confirmed repair direction for U1054 on a Skoda Enyaq is restoring the Information Electronics 1 control unit’s power, ground, connector fit, or network circuit integrity rather than replacing the module first. Corrosion, loose terminals, harness stress, or a supply issue can interrupt communication long before a control unit actually fails. A second common repair path involves software recovery or module replacement only after you prove the circuits are correct and the module still will not come online. After repair, verify the fix by cold-starting the vehicle, cycling sleep and wake states, and road-testing long enough for the network to complete its normal communication checks. Enable criteria vary by platform and system, so consult Skoda service information for the exact confirmation routine.

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