U1123 – Databus error value received (Skoda)

Skoda-specific code — factory diagnostic data

U1123 means the Skoda network saw a message that contained an invalid or error value. In the Enyaq, that often causes warning messages, odd body electrical behavior, or intermittent function loss before it causes any hard no-start or no-drive symptom. According to Skoda factory diagnostic data, this code indicates Databus error value received. That wording does not name a failed part. It tells you the 09-Electronic central electric module received data from another control unit that did not make sense or did not pass its plausibility checks. The real job in diagnosis is to identify which sending module or network path produced the bad value.

U1123 Quick Answer

U1123 on a Skoda Enyaq means the central electrics module received an invalid value over the vehicle databus. Diagnose the sending module, its power and ground, and the network path before replacing any controller.

What Does U1123 Mean?

The official Skoda definition for U1123 is Databus error value received. In plain English, the module did hear from another module, but the information inside that message was not usable. That matters because this code points to a communication quality or data plausibility problem, not automatically to a dead module.

Technically, 09-Electronic central electric monitors expected bus messages from other controllers and checks whether key values stay valid and plausible. The module sets U1123 when a received message contains an error state, implausible content, or a value that conflicts with what the rest of the vehicle reports. For diagnosis, separate three things: the official definition, the specific signal group that failed plausibility, and the reason that bad data appeared on the Skoda network.

Theory of Operation

Under normal conditions, the Enyaq uses multiple control modules that exchange status, requests, and operating values over the databus. The central electrics module acts as a major body-system coordinator. It relies on clean network traffic so it can control lighting, access functions, wake-up logic, and other electrically managed features without guessing.

This code appears when normal message exchange continues, but one value inside a message arrives flagged as faulty or arrives in a form the receiving module cannot trust. That breakdown can come from unstable power or ground at the sending module, bus wiring issues, connector problems, software mismatches, or a module that stays online but transmits corrupted or implausible data. Because U-codes use intentionally broad wording, the code identifies a trouble area. It does not identify the root cause by itself.

Symptoms

Symptoms depend on which message stream failed, but these are the patterns technicians and owners usually notice first on a Skoda network fault like U1123.

• Scan tool behavior: One module may show intermittent communication, delayed identification, or related communication faults stored across several controllers.
• Warning messages: The cluster may display body electrical, convenience, or general electrical system warnings.
• Intermittent functions: Exterior lighting, interior electrical features, or convenience functions may work inconsistently.
• Multiple stored codes: Other modules may log plausibility, missing message, or signal quality faults at the same time.
• Startup irregularities: Wake-up or sleep behavior may seem abnormal, with delayed module readiness after key-on.
• Feature shutdown: A dependent function may disable itself because it cannot trust the received data.
• No obvious driver symptom: Some Enyaq vehicles store U1123 without a clear complaint, especially when the fault occurs briefly.

Common Causes

• Intermittent CAN bus wiring fault: A loose, rubbed, pinched, or partially open network wire can corrupt messages and make the central electric module receive an error value.
• Poor power or ground at a communicating module: Low supply quality at one Skoda control unit can distort its transmitted data and trigger U1123 in 09-Electronic central electric.
• Connector corrosion or terminal spread: Increased resistance at a network or module connector can alter message integrity and create invalid databus values.
• Water intrusion in body electronics areas: Moisture around junctions, connectors, or control units can bridge terminals or create intermittent resistance changes on the Enyaq network.
• Faulty data from another control module: A module can stay online yet transmit implausible or corrupted information that the receiving module flags as an error value.
• Gateway or network routing issue: A problem in message routing between bus segments can pass incomplete or invalid data to the central electric module.
• Aftermarket electrical equipment interference: Non-OEM accessories, splices, trackers, or dash cameras can load power circuits or disturb network integrity on Skoda vehicles.
• Low system voltage during operation: Weak battery performance or unstable charging support can upset control module communication and create stored databus faults.
• Harness damage near moving or high-stress areas: Repeated flexing near hinges, trim edges, or mounting points can break strands and cause intermittent network errors.

Diagnosis Steps

You need a capable scan tool with full Skoda module access, wiring information, a digital multimeter, and preferably a scope. Use the scan tool for a complete network scan, freeze-frame review, and live data monitoring. Use the meter for loaded power and ground tests, connector checks, and CAN resistance and bias checks. A manual snapshot during a road test helps with intermittent faults.

1. Confirm U1123 in 09-Electronic central electric. Record whether it shows current, intermittent, pending, or stored status. Save freeze-frame data and note ignition state, vehicle speed, and all related network DTCs. Freeze frame shows the exact conditions when the code set. A scan-tool snapshot serves a different job. It captures live conditions during your test drive when the concern repeats.
2. Run a full vehicle network scan before any deep circuit testing. Check whether all expected modules appear on the scan tool. Look for companion communication, supply voltage, or gateway faults. Then inspect the relevant fuse feeds and power distribution for the affected networked modules. On this communication code, that step comes before measuring at any control unit.
3. Verify module power and ground under load, not with open-circuit voltage alone. Backprobe the power and ground circuits for 09-Electronic central electric and any suspect transmitting modules. Load the circuit while testing. Ground voltage drop must stay below 0.1 volt with the circuit operating. A weak ground can pass a simple voltage check and still corrupt bus traffic.
4. Inspect connectors and harness routing at the central electric module, gateway area, and any modules flagged by related codes. Look for backed-out terminals, corrosion, moisture, poor pin tension, harness chafe, or repair splices. Pay close attention to body harness sections that flex or sit in moisture-prone areas on the Enyaq.
5. With ignition off and the battery disconnected, measure resistance between CAN+ and CAN- at an accessible network connector. A healthy terminated CAN bus reads about 60 ohms. A reading near 120 ohms or open circuit points to an open leg or missing termination. A very low reading suggests a shorted bus or a shorted module pulling the network down.
6. Reconnect the battery and switch ignition on. Measure CAN+ and CAN- to ground at an accessible point. Communication line bias exists only with the circuit powered, so ignition-off voltage readings do not help here. On a healthy high-speed CAN network, both lines typically sit near 2.5 volts to ground. Large imbalance or a line pinned high or low indicates a wiring or module fault.
7. Use the scan tool to identify which message source looks implausible. Compare live data from 09-Electronic central electric with the suspected source module. If one module reports impossible status, missing updates, or inconsistent values while others stay normal, focus on that module’s power, ground, and network circuits before condemning the module itself.
8. If the fault acts intermittently, perform a harness wiggle test while watching live communication status and related data parameters. Move one section at a time. Do not shake the whole harness at once. If the code resets or live values drop out when you move a specific branch, isolate that section and inspect it more closely.
9. Check for software-related clues only after circuit integrity passes. Review module identification, coding status, and any technical service information that applies to the Skoda platform. Invalid or mismatched coding can create message interpretation faults. Do not attempt programming until you confirm stable battery support and clean network integrity.
10. Clear the codes after repairs. Repeat the network scan, cycle the ignition, and road test under conditions similar to the freeze frame. Confirm that U1123 does not return and that all communicating modules stay present on the network. If the code returns immediately at key-on, treat it as a hard fault and recheck supply, ground, and bus integrity.

Professional tip: U1123 does not prove that 09-Electronic central electric has failed. On Skoda vehicles, this code often means the receiving module saw bad data from somewhere else on the network. Let the network scan, freeze frame, loaded voltage-drop results, and bus measurements guide you to the source. Replace a module only after its powers, grounds, network circuits, and message behavior all fail verification.

Possible Fixes

• Repair damaged CAN wiring: Fix opens, shorts, chafed insulation, or poor splice repairs found during resistance, bias, or wiggle testing.
• Restore clean power and ground: Repair loose fuse feeds, corroded ground points, or high-resistance supply circuits that fail loaded voltage-drop testing.
• Clean and secure affected connectors: Correct terminal tension problems, remove corrosion, dry moisture intrusion, and lock connectors fully into place.
• Remove or correct aftermarket wiring issues: Isolate non-factory accessories that disturb module supply quality or databus integrity.
• Repair water entry sources: Seal the leak path and repair any connector or harness damage caused by moisture in body electronics areas.
• Update or recode the verified affected module: Perform software or coding correction only after power, ground, and network integrity test good.
• Replace the verified faulting module: Replace a control unit only when it stays within specification for power and ground but still transmits invalid data.

Can I Still Drive With U1123?

You can often drive a Skoda Enyaq with U1123 if the vehicle starts, charges normally, and no major warning messages appear. This code means the 09-Electronic central electric module received an implausible or error value over the databus. That points to a communication quality problem, not an automatic part failure. Still, body electrical functions may act unpredictably. Exterior lighting, convenience features, wipers, locking, or status messages can drop out depending on which network message turned invalid. Do not keep driving if other control modules also log communication faults, if multiple systems malfunction at once, or if the vehicle shows reduced-function warnings. The safe approach is short, necessary trips only until you confirm power, ground, connector condition, and network integrity on the affected Skoda platform.

How Serious Is This Code?

U1123 ranges from minor to significant, depending on which databus message failed and what system depended on it. In many Enyaq cases, it starts as an inconvenience. You may see intermittent warnings, inoperative comfort features, or occasional electrical oddities. The severity rises fast when the invalid message affects lighting control, access systems, charging coordination, or gateway-managed network traffic. If the fault appears with multiple U-codes, low-voltage events, or module reset symptoms, treat it as a broader network problem. That can lead to no-start conditions, charging complaints, or widespread body electronics issues. This code does not identify the root cause by itself. The fix comes from testing, not guessing. Verify module communication, check live data plausibility, inspect connectors for water or terminal spread, and load-test power and ground paths before any control unit replacement on a Skoda.

Common Misdiagnoses

Technicians often misread U1123 as proof that the 09-Electronic central electric module failed. That mistake leads to expensive and unnecessary module replacement. Another common error is chasing the module named in a companion code without checking whether the central electric module merely reported a bad incoming value. On Skoda vehicles, one unstable power feed, one poor ground, or one corroded network connector can create several misleading databus faults. Many also skip a full vehicle scan and miss the module that actually originated the implausible message. Others clear codes too early and erase the fault pattern. Avoid wasted spending by checking network topology, module presence, freeze-frame conditions, battery state, charging history, and live data consistency before you condemn any controller.

Most Likely Fix

The most common confirmed repair direction is not module replacement. It is correcting the reason the 09-Electronic central electric module received a bad network value. In practice, that often means repairing a weak power or ground supply, cleaning and tightening a corroded connector, fixing terminal fit, or repairing databus wiring damage near a harness bend, splice, or moisture entry point. A second common repair path involves the module that transmitted the implausible value, but only after scan-tool communication, input plausibility, and network checks prove that module is the source. After repair, clear faults, repeat a full network scan, and road test the Enyaq long enough for the affected system to meet its enable criteria. Those criteria vary by vehicle and function, so check service information before calling 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