U1110 – Function restriction caused by communication interruption (Skoda)

Skoda-specific code — factory diagnostic data

Skoda code U1110 means a control module has entered a restricted-function or degraded-mode state because it detected an interruption in CAN bus communication — either losing contact with one or more modules it depends on, or detecting that the CAN bus itself was temporarily unavailable. This is a Skoda/VAG manufacturer-specific code that appears in the module that was affected by the communication loss, not necessarily in the module that was the source of the interruption. U1110 is an umbrella code: the specific cause requires checking which module stores it and which other U-codes or lost-communication codes accompany it. The most common causes are a weak 12V battery causing bus-wide voltage drops, a faulty gateway module, a damaged CAN bus wire, or a module that went offline.

U1110 Quick Answer

U1110 on a Skoda means a module reduced its own function because CAN communication was interrupted. Check the 12V battery first — a weak battery causing voltage dips at start-up is the most common trigger. Then perform a full system scan and count all U-codes: multiple modules showing U1110 points to a bus-level event (voltage, wiring, or gateway). A single module showing U1110 alongside a specific lost-communication code points to a single offline module.

What Does U1110 Mean?

Official meaning (Skoda): U1110 – Function restriction caused by communication interruption. The U-prefix identifies this as a network communication code. U1110 specifically indicates that the affected module did not just detect a missing peer — it also entered a degraded operating mode as a result. This degraded mode is a safety feature: rather than operating with missing input data (which could cause incorrect outputs), the module defaults to a safe state and logs U1110 to flag the condition.

Context matters for diagnosis: U1110 found in the gateway module points to a systemic bus issue (power supply, bus wiring). U1110 found in a specific body or chassis module alongside a lost-communication code for another module points to that other module going offline — either a power issue at that module or a wiring break on its CAN node. Always read U1110 in combination with all other U-codes in the scan to understand what was missing.

Theory of Operation

Skoda MEB and MQB platform vehicles use multiple CAN bus segments (powertrain CAN, comfort CAN, infotainment CAN) connected through a central gateway module. Each module on the bus transmits periodic “heartbeat” messages at defined intervals. When a module stops receiving another module’s expected messages beyond the network timeout window, it logs a lost-communication fault for that module and may enter a restricted mode if the missing data is critical to its operation — logging U1110 to record this restriction.

U1110 is therefore a secondary symptom. The primary cause is always a module going offline or a bus segment becoming unavailable. Common triggers include: a voltage dip that resets a module at start-up; a CAN bus fault (short between H and L lines) that collapses the differential signal; a broken CAN wire at a harness flex point; or a module that has genuinely failed and stopped transmitting. The gateway module is a common failure point on high-mileage VAG vehicles — it connects all CAN segments and a gateway failure can produce U1110 across many modules simultaneously.

Symptoms

Symptoms depend on which module stored U1110 and how critical the lost communication was.

• Multiple warning lights — ESP, ABS, EPS, climate, or infotainment warnings depending on which modules restricted their functions
• Functions in degraded mode — e.g. climate defaulting to fixed settings, adaptive cruise not available, park assist disabled
• U1110 in one or more modules — confirmed by VCDS, OBD11, or ODIS full scan
• Multiple U-codes across modules — when the CAN bus was the fault source, most modules will show U-codes from the same event
• Symptoms are intermittent — if a bad battery or loose connection causes brief voltage dips, faults are logged at start-up and may not be visible during the workshop visit
• Fault cleared on its own after a power cycle — U1110 often stores as a historical fault after a transient event; if the bus is now healthy, the code may clear and not return after the underlying cause (battery) is fixed

Common Causes

• Weak 12V battery: The most common cause on the Skoda Enyaq and other MEB EVs. The DC-DC converter maintains the 12V bus during driving, but at ignition-off and during the initial power-up sequence, the 12V battery alone supplies all modules. A battery that dips below 9–10V at cold start causes every CAN module to reset briefly, with each one logging U1110 for lost communication during its own restart sequence.
• Gateway module fault: The central gateway connects all CAN segments. A failing gateway causes U1110 to appear across all segments simultaneously. On MEB vehicles (Enyaq), the gateway is part of the vehicle electrical system control module (VX) — a documented failure point.
• CAN bus wiring fault: A short between CAN H and CAN L lines, or a broken wire on a shared CAN segment, causes all nodes on that segment to lose communication simultaneously. The fault is positional — check harness flex points, connector cavities, and areas of known chafe.
• Module power or ground failure: A blown fuse or corroded ground at a specific module causes that module to go offline and disappear from the CAN bus — all modules that depended on it for data will log U1110 plus a lost-communication code for the offline module.
• Water or moisture in connectors: Water intrusion into multi-pin CAN connectors can bridge CAN H and CAN L, causing intermittent bus collapse. Common on Enyaq at the front battery management unit connector on vehicles with drainage issues.
• Software bug or module lockup: Rare — a module software fault causes the module to stop transmitting on the bus without a hardware fault. Usually resolved by a power cycle or software update from Skoda.

Diagnosis Steps

Use VCDS or ODIS for a full system scan with all modules. Work from the top down: power supply first, then network architecture, then individual modules.

1. Perform a complete scan of all accessible modules and export the full fault list. Count U1110 and U-code occurrences. If U1110 appears in more than 5 modules simultaneously, the event was bus-wide — do not investigate individual modules until the power supply and CAN bus are confirmed healthy.
2. Test the 12V battery under load. On MEB EVs, the 12V battery is typically a small AGM unit (often 50–70Ah). Have it tested with a conductance tester. A battery at less than 70% health is a replacement candidate. Also confirm the DC-DC converter is outputting 13.5–14.5V when the HV system is active.
3. Check all fuses associated with the gateway module and the most commonly offline modules found in the fault list. A blown fuse is a definitive finding that explains a specific module dropping off the bus.
4. Measure CAN bus termination resistance at the OBD2 port (pins 6 and 14 for the main CAN bus). With ignition off and all modules unpowered (wait 2–3 minutes): expect ~60Ω for a healthy bus. Less than 50Ω indicates CAN H to CAN L short. Greater than 150Ω or open indicates a missing or disconnected terminator or a broken bus wire.
5. If termination resistance is abnormal, locate the fault. Disconnect individual harness connectors at suspected flex points and re-measure until the resistance normalises — this isolates the segment containing the fault.
6. Check gateway module function specifically. In VCDS, the gateway shows all available modules — compare the list of accessible modules against the vehicle’s known configuration. Modules missing from the gateway’s network view are offline. Cross-reference with the physical vehicle to identify the offline module.
7. After correcting battery, wiring, or module faults: clear all codes, key cycle the vehicle, and allow all modules to wake up (approximately 2 minutes from ignition on). Re-scan. U1110 should be absent. If U1110 persists in a specific module only, investigate that module’s power supply, ground, and CAN connections individually.

Professional tip: On the Skoda Enyaq specifically, U1110 appearing simultaneously in the battery management system (BMS), power electronics module, and charging system module after a 12V battery event is a well-documented pattern. The HV system enters a protective standby state when 12V supply is interrupted — replace the 12V battery, clear codes, and allow the HV system to reinitialise (may require a drive cycle with the HV battery connected) before declaring any other module faulted.

Possible Fixes

• Replace the 12V battery: Most common confirmed fix for simultaneous U1110 across multiple modules. Register the new battery with ODIS after replacement.
• Repair CAN bus wiring: Correct any short or open on the CAN network segments. Restore correct termination resistance.
• Repair module power supply or ground: Replace blown fuse, clean corroded ground, or repair damaged supply wiring at the offline module.
• Replace gateway module: If the gateway itself is confirmed faulty — requires ODIS coding to match vehicle configuration.
• Software update: If a module lockup or software bug is confirmed as the cause, apply available Skoda software updates via ODIS or OTA.

Can I Still Drive With U1110?

Drivability depends on which module restricted its function. If the ESP, ABS, or EPS modules are affected, safety-critical systems may be degraded — do not drive in adverse conditions. If only comfort or infotainment modules are affected (climate, audio, navigation), the vehicle is safe to drive to a workshop. Identify the affected modules before deciding how urgently to seek repair.

How Serious Is This Code?

U1110 is a high-priority diagnostic code because it signals that active safety systems may be operating in a reduced mode. It is particularly concerning on MEB EV platforms where the 12V supply is separated from the HV traction battery — a 12V failure can simultaneously affect ESP, ABS, EPS, and the charging system. Diagnose promptly, especially if multiple modules are affected.

Common Misdiagnoses

The most common error is replacing individual modules that show U1110 without first addressing the power supply. On a vehicle where 12 modules show U1110 after a battery event, no module is individually at fault — they all reacted correctly to an inadequate supply voltage. Replacing a gateway or BCM in this scenario wastes parts and does not fix the root cause. A second error is clearing U1110 without retesting after a power cycle — some faults are historical only and do not return once the battery is replaced, but clearing without retesting prevents confirmation that the fix worked.

Most Likely Fix

For Skoda U1110, the majority of confirmed repairs resolve at the 12V battery — replacement plus BMS registration eliminates the voltage drop that caused the communication interruption. CAN wiring repair is the confirmed fix when termination resistance is abnormal. Gateway and individual module replacements are found in a minority of persistent cases following complete power supply and wiring verification.

Repair Costs

Battery replacement is by far the most cost-effective fix. Gateway and module replacements are significantly more expensive.