U1122 – Data bus message implausible (Skoda)

Skoda-specific code — factory diagnostic data

U1122 means the Skoda Enyaq has a network message problem, not an immediate proof of a bad part. In real use, lane change assistance may switch off, show a warning, or work intermittently because the module no longer trusts one of the data messages it receives. According to Skoda factory diagnostic data, this code indicates data bus message implausible. That wording matters. It tells you the 3C-Lane change assistance module detected a message on the vehicle network that did not make sense for current operating conditions, message content, or related signals. The code points to a communication plausibility issue that requires network, power, ground, and data comparison checks before any module replacement.

U1122 Quick Answer

U1122 on a Skoda means the lane change assistance module received a data bus message that it judged implausible. On an Enyaq, that usually disables or limits blind spot or lane change assistance until you find why the message content, timing, or supporting inputs no longer agree.

What Does U1122 Mean?

The official Skoda definition is data bus message implausible. In plain English, the 3C-Lane change assistance module saw network information that did not fit what it expected to see, so it stopped trusting that message. That can affect driver assistance functions that depend on shared data from other control units.

For diagnosis, separate the wording carefully. The definition tells you what the module detected, not which part failed. The module checks incoming bus messages for logic, timing, and agreement with other data. If a message arrives with incorrect content, missing companion data, unstable timing, or poor network integrity, the module can set U1122. That matters because root cause often sits outside the lane change assistance unit itself. Power supply issues, ground loss, wiring faults, gateway problems, or a different module sending bad data can all trigger the same code.

Theory of Operation

Under normal conditions, the Skoda lane change assistance system does not work alone. It relies on data shared across the vehicle network. That data can include vehicle speed, steering angle, gear status, yaw information, gateway routing, and status messages from related driver assistance modules. The 3C-Lane change assistance module compares those messages against internal logic. If the data agrees and arrives on time, the system allows normal operation.

This code sets when that trust breaks down. A message may still be present, yet its value may conflict with other inputs or change in a way the module considers impossible. The fault can also appear when corrosion, low supply voltage, poor grounds, connector tension problems, or bus errors distort message content or timing. On the Enyaq, that means you must diagnose the network path and the supporting modules, not just the module that stored U1122.

Symptoms

Communication plausibility faults usually show up first in scan data and driver assistance availability.

• Scan tool behavior: One or more modules respond intermittently, drop off the network list, or show related communication faults.
• Driver assistance warning: Lane change assistance or blind spot monitoring shows unavailable, restricted, or fault messages.
• Function shutdown: The system disables intervention or warning output until the fault clears.
• Intermittent operation: The feature works at one key cycle, then drops out during another.
• Multiple network codes: Other control units may log message plausibility, missing message, or no communication faults.
• No obvious hardware symptom: Sensors may appear physically intact even though network data remains invalid.
• Voltage-related complaints: Faults may appear after low battery events, module wake-up issues, or unstable charging system conditions.

Common Causes

• Intermittent CAN bus wiring fault: A partial open, rub-through, or wire tension issue can distort messages enough for the lane change assistance module to flag them as implausible.
• Connector corrosion or poor terminal fit: Corrosion, spread terminals, or moisture at a network connector can add resistance and alter message quality on the Skoda communication bus.
• Low system voltage during module operation: Weak battery support, unstable charging, or a power distribution issue can make one or more modules transmit invalid data.
• High-resistance ground for a networked control unit: A poor ground can keep a module awake but unstable, which often creates implausible data rather than a full no-communication fault.
• Fault in a related networked module: Another Skoda control unit can send out corrupted or unreasonable information that the 3C-Lane change assistance module rejects as implausible.
• Gateway or bus routing issue: A fault in the network gateway or its power and ground feeds can corrupt message handling between modules on the Enyaq platform.
• Water intrusion in harness or module area: Moisture can create leakage paths, intermittent shorts, and changing resistance that only appear in certain weather or temperature conditions.
• Incorrect coding or software mismatch: A configuration error or software inconsistency after module work can cause message content to fail plausibility checks even when wiring remains intact.
• Aftermarket equipment affecting the network: Added electronics spliced into power, ground, or data circuits can load the bus and disturb message timing or integrity.

Diagnosis Steps

You need a capable scan tool with full module access, wiring information, a DVOM, and preferably a lab scope. Use the scan tool first. Record stored, pending, and related network faults. For this communication code, freeze frame should include vehicle speed, ignition state, and all related DTCs. Freeze frame shows when the code set. A snapshot captures an intermittent fault during your road test.

1. Confirm U1122 in the 3C-Lane change assistance module. Record whether the code shows as pending, confirmed, or stored. Save freeze frame and note vehicle speed, ignition state, network status, and any companion faults in gateway, radar, camera, ABS, steering, or power supply modules.
2. Run a complete network scan before touching the module. Check whether the lane change assistance module appears on the scan tool list and whether other modules report communication or plausibility faults. Then inspect related fuses, shared power distribution points, and visible network harness routing for obvious damage before any meter work.
3. Verify module power and ground under load. Do not rely on unloaded voltage or continuity alone. Perform voltage-drop tests with the circuit operating. Ground drop should stay below 0.1 volt. A high-resistance feed or ground can keep the module online but make its messages unstable.
4. Inspect the 3C-Lane change assistance connector, gateway connector, and any accessible inline connectors on the affected network path. Look for moisture, bent pins, terminal spread, fretting, green corrosion, poor latch tension, and harness strain near brackets or body pass-through points.
5. If the module stays online, compare live data from the lane change assistance module with related modules that supply shared inputs. Look for a value that drops out, freezes, or becomes unreasonable when U1122 resets. On this Skoda fault, the implausible message matters more than simple bus presence.
6. Check CAN bus integrity. With ignition off and the battery disconnected, measure resistance between CAN+ and CAN- at an accessible module connector. A healthy network reads about 60 ohms. A reading near 120 ohms or open circuit points to a missing termination or an open in one bus conductor.
7. Reconnect the battery and switch ignition on. Measure CAN+ and CAN- bias voltage to ground with the network powered. Use ignition-on readings only, because bus bias does not exist with the circuit asleep. Healthy high-speed CAN commonly sits near 2.5 volts on both lines at rest.
8. If resistance or bias voltage looks wrong, isolate the faulted branch. Disconnect suspect modules one at a time only when service information allows it. Watch for the bus to recover. If the network returns to normal after one branch disconnects, inspect that branch for shorts, water intrusion, or a failed node.
9. If the network tests pass, focus on plausibility rather than bus integrity. Review coding, adaptation, and software part numbers for the lane change assistance module and any recently replaced related module. A coding mismatch can create implausible data without setting a classic open or short code.
10. Use a scan tool snapshot during a road test if the code appears intermittently. Trigger the snapshot when the warning appears or when live data drops out. Compare the snapshot to freeze frame. Freeze frame shows the exact setting conditions. The snapshot helps catch the fault developing in real time.
11. After repairs, clear codes and repeat the network scan. Confirm all modules communicate normally. Road test the Enyaq under similar ignition and vehicle speed conditions to the original freeze frame. Then verify U1122 does not return as pending or confirmed.

Professional tip: U1122 does not prove the lane change assistance module has failed. On Skoda vehicles, an implausible message often starts with power quality, ground quality, connector condition, gateway behavior, or bad data from another control unit. Prove the network and module supplies first. Replace a control unit only after the bus, wiring, coding, and message source all check out.

Possible Fixes

• Repair damaged CAN wiring: Fix any confirmed open, short, rub-through, or high-resistance section in the network branch serving the affected Skoda modules.
• Clean and restore connector integrity: Remove corrosion, correct terminal tension, dry moisture intrusion, and secure connector locks where testing finds unstable communication.
• Correct power or ground faults: Repair fuse feeds, splice issues, ground points, or power distribution problems that fail voltage-drop testing under load.
• Repair harness water intrusion: Seal leaks, replace contaminated connector parts, and repair any moisture-damaged wiring where the Enyaq harness shows evidence of water entry.
• Update or correct module coding: If testing finds no wiring fault, correct configuration or software inconsistencies in the lane change assistance or related networked module.
• Repair the faulted message source module: If another control unit sends implausible data and all circuits test good, diagnose and repair that module and its inputs before condemning it.
• Replace a control module only after proof: Replace the 3C-Lane change assistance module or another implicated unit only after verifying power, ground, wiring, network integrity, and coding.

Can I Still Drive With U1122?

You can usually drive a Skoda Enyaq with U1122 if the vehicle otherwise operates normally, but you should not trust lane change assistance to work correctly. This code tells you the 3C-Lane change assistance module received a data bus message that did not make sense for the situation. That can disable blind spot warning, rear side monitoring, or related driver-assistance functions. The engine and brakes often remain unaffected, but network faults can spread and trigger more warnings if power, ground, or bus integrity continues to degrade. Drive only if no other critical faults appear, no major communication loss exists, and the vehicle shows no braking, steering, or stability warnings. Treat the assistance system as unavailable until you confirm the root cause and complete any required repair verification.

How Serious Is This Code?

U1122 ranges from an inconvenience to a real safety concern, depending on what else the network fault affects. In many cases, the issue only knocks out lane change assistance functions and turns on warning messages. That still matters, because the driver may expect blind spot monitoring to warn about adjacent traffic when it cannot. The risk increases if the Enyaq stores multiple communication codes, loses communication with other driver-assistance modules, or shows unstable live data from the lane change assistance system. Since this code sits in an ADAS-related module, take repairs seriously and verify the system fully before returning it to service. If you replace a related module, radar unit, or other ADAS component, Skoda procedures may require coding, initialization, and calibration before the system is safe to use. Do not assume a cleared warning means the system now sees traffic correctly.

Common Misdiagnoses

Technicians often replace the lane change assistance module too early. That wastes money and misses the actual fault. U1122 does not prove the 3C module failed. It only shows that the module judged a bus message implausible. The real problem often comes from low system voltage, poor ground quality, connector drag, moisture intrusion, gateway issues, or a second module sending bad data. Another common mistake involves reading one stored code and ignoring the network picture. You need a full vehicle scan, fault timestamps, and communication status for all related modules. Shops also skip wiggle testing and voltage-drop checks under load, then miss an intermittent power or ground fault. Avoid guesswork. Verify supply circuits, inspect connectors, compare live data, and confirm whether the suspect message source reports its own faults before replacing any control unit.

Most Likely Fix

The most common confirmed repair direction is restoring clean communication or stable power to the lane change assistance system, not replacing parts on first sight. On Skoda vehicles, that often means correcting corrosion, terminal spread, poor pin fit, harness damage, or ground issues at the 3C-Lane change assistance module or at a related message-sending module. A second common repair path involves correcting faults in the upstream module that transmits the implausible data. If testing proves a module, sensor, or radar unit failed internally, follow Skoda repair steps for coding and any ADAS calibration. After the repair, do not stop at code clearing. Road test the vehicle under the conditions that enable the affected monitor and assistance function. Those enable criteria vary by platform and system, so check service information before you call the repair complete.

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