U140A – Terminal 30 open circuit (Skoda)

Skoda-specific code — factory diagnostic data

U140A means the Skoda Enyaq has a power supply problem on Terminal 30, and that can cause warning messages, module dropouts, or strange electrical behavior. In plain terms, the gateway noticed that a constant battery feed was missing when it should have been present. According to Skoda factory diagnostic data, this is a manufacturer-specific code defined as Terminal 30 open circuit. On this platform, that does not automatically prove the 19-Gateway has failed. It tells you the gateway detected an open in a battery-positive supply path, or saw that supply disappear, and diagnosis must confirm whether the fault sits in the fuse path, wiring, connection, or the module feed itself.

U140A Quick Answer

U140A on a Skoda points to an open circuit in Terminal 30, the unswitched battery supply circuit. The 19-Gateway logged that fault because it lost, or detected loss of, a constant power feed that should stay available.

What Does U140A Mean?

The official Skoda definition is simple: Terminal 30 open circuit. In practice, the gateway detected that a constant battery supply circuit was not present or not plausible. That matters because many vehicle networks depend on stable unswitched power for wake-up, memory retention, and communication management.

From a diagnostic standpoint, the code points to a suspected trouble area, not a confirmed bad part. The 19-Gateway monitors its supply environment and network state. If the module sees its Terminal 30 feed open, interrupted, or outside expected logic, it stores U140A. The real cause can be a blown fuse, poor fuse contact, loose terminal, damaged wiring, corrosion, or a power distribution issue elsewhere in the Skoda supply path.

Theory of Operation

Under normal conditions, Terminal 30 provides continuous battery voltage to selected control units, including network management functions. In the Skoda Enyaq, the 19-Gateway uses that stable feed to stay ready, retain learned data, and coordinate communication between multiple modules. Even when ignition status changes, Terminal 30 remains available as the base power source.

This code sets when that normal constant feed disappears or becomes electrically open. The failure can be hard, such as a broken wire or open fuse link. It can also be intermittent, such as spread terminal tension, heat damage, or corrosion in a connector or power distribution point. Once the gateway loses that feed, it may reset, stop routing messages correctly, or flag other network faults that only exist because its base power supply became unstable.

Symptoms

Symptoms vary with how often the Terminal 30 feed opens, but the pattern usually points to unstable power at the gateway or its supply path.

• Warning messages Cluster alerts may appear suddenly, especially after startup or during wake-up.
• Network faults Multiple communication codes may set in other modules after the gateway supply drops out.
• Intermittent operation Features may work normally one moment and then go offline without a clear pattern.
• No communication The scan tool may lose contact with the 19-Gateway or show intermittent response.
• Module reset behavior Time, settings, or module states may reset after the power feed opens.
• No-start or wake-up issues The vehicle may show startup irregularities if the network does not initialize correctly.
• Electrical glitches Infotainment, convenience, or body functions may behave erratically during low-contact events.

Common Causes

• Blown Terminal 30 supply fuse: A failed fuse in the constant battery feed path can leave the 19-Gateway without the expected Terminal 30 input.
• Loose power distribution connection: A spread terminal, loose fastener, or poor junction connection can open the battery feed intermittently under vibration or load.
• Corroded Terminal 30 wiring: Corrosion inside a splice, fuse holder, or connector increases resistance until the Gateway sees the constant supply drop out.
• Open circuit in the battery feed wire: A broken conductor anywhere between the power source and the Gateway can interrupt the Terminal 30 circuit completely.
• Connector terminal damage at the Gateway: Backed-out, overheated, or tension-lost terminals at 19-Gateway can break contact even when the connector looks seated.
• Water intrusion in a harness or connector: Moisture can corrode terminals and wiring, which creates intermittent opens and unstable supply voltage on Skoda network circuits.
• Poor battery positive distribution integrity: A fault upstream in the main positive distribution path can remove or weaken the constant feed that several control units expect to see.
• Weak system voltage during wake-up: Low battery state or unstable power during module wake-up can make the Gateway log a Terminal 30 open circuit if the feed collapses at the wrong moment.
• Gateway internal power input fault: The 19-Gateway can set this code if its internal monitoring sees a valid external feed path problem or a verified internal input-stage issue.

Diagnosis Steps

You need a capable scan tool, wiring diagram, DVOM, a test light or loaded circuit tester, and access to Skoda power distribution points. Use the scan tool to review freeze frame and related network faults. For this code, pay close attention to ignition state, vehicle speed, battery voltage, and any companion supply or communication DTCs.

1. Confirm U140A in 19-Gateway. Record stored, pending, and history status. Save freeze frame data before clearing anything. Freeze frame shows when the fault set. A manually triggered snapshot serves a different purpose and helps catch intermittent dropouts during a road test or key cycle.
2. Check whether 19-Gateway appears normally on the network scan. Then inspect the Terminal 30 circuit path visually before any meter work. Check related fuses, fuse holders, battery positive distribution points, and obvious harness damage first. A hard circuit fault often returns immediately on key-on because the monitor runs continuously.
3. Verify battery condition and system voltage, then test Gateway power and ground under load. Do not trust unloaded voltage alone. Use voltage-drop testing with the circuit operating. Ground drop should stay under 0.1 volt. A high-resistance connection can look normal with no load and fail as soon as current flows.
4. Backprobe the Terminal 30 feed at the Gateway connector and compare it to battery positive while the circuit remains loaded. If the feed drops out, move upstream step by step through the fuse, splice, and distribution path until the voltage loss disappears. That isolates the open or high-resistance point.
5. Inspect the Gateway connector closely. Look for loose fit, backed-out terminals, heat damage, oxidation, water traces, and poor terminal grip. Tug-test the suspect wire lightly. On the Enyaq, do not assume a seated connector has good terminal tension inside.
6. Inspect the harness between the Gateway and the power source. Focus on bends, pass-through points, bracket contact areas, and any place the loom can rub or pinch. If the fault acts intermittently, wiggle-test the harness while watching live voltage or DTC status on the scan tool.
7. Check for related DTCs in other modules. Multiple supply or network codes can point to a shared Terminal 30 feed problem rather than a Gateway-only issue. If several Skoda control units log undervoltage or communication loss together, trace the common power distribution path before condemning any module.
8. If the wiring diagram shows shared splices or junctions, isolate each branch and test continuity only after disconnecting power as required by service information. Continuity alone does not prove circuit integrity. Follow up with a loaded test to confirm the circuit can carry current without excessive voltage loss.
9. Cycle the ignition several times after repairs or circuit manipulation. Monitor live data, module wake-up behavior, and DTC return timing. If the code resets immediately, the fault remains hard. If it returns only during movement or wake-up, continue harness movement and load-based testing.
10. Confirm the repair by clearing codes, repeating the operating conditions from the freeze frame, and rescanning all modules. Make sure U140A stays out of 19-Gateway and no related supply or network faults return. Only consider module replacement after the Terminal 30 feed and grounds test good under load.

Professional tip: Terminal 30 faults often hide in fuse blocks and splice points, not in the Gateway itself. If U140A appears with other low-voltage or communication complaints on a Skoda Enyaq, trace the shared battery feed path first. Loaded voltage-drop testing finds these faults faster than continuity checks.

Possible Fixes

• Replace the failed fuse and correct the reason it opened: Install the proper fuse only after checking the downstream circuit for damage or excessive current draw.
• Repair the open in the Terminal 30 feed: Restore wiring integrity at the broken section, splice, or junction, then confirm the circuit carries load without abnormal voltage drop.
• Clean and tighten power distribution connections: Remove corrosion, restore terminal tension, and secure loose battery or fuse-block connections that interrupt constant power.
• Repair or replace damaged Gateway connector terminals: Correct backed-out, overheated, or loose terminals and verify pin fit before reconnecting the module.
• Repair water intrusion damage: Dry the affected area, fix the leak source if found, and replace corroded terminals or wiring that can no longer maintain reliable contact.
• Service the battery or main power supply issue: Correct weak battery or unstable supply conditions if testing shows the Terminal 30 feed collapses during module wake-up.
• Replace the 19-Gateway only after circuit proof: Consider module replacement only when Terminal 30 feed, grounds, connector integrity, and network behavior all test good and the fault remains.

Can I Still Drive With U140A?

You may be able to drive the Skoda Enyaq with U140A present, but you should not treat it as harmless. This code means the 19-Gateway detected an open in Terminal 30, which is the constant battery feed used to keep key modules powered and awake. If that open happens only for a moment, the vehicle may seem normal. If it happens again, modules can reset, warning lights can appear, and network functions can drop out without warning. A short trip to a safe repair location is usually reasonable if the vehicle starts and no critical warnings appear. Do not continue driving if multiple systems go offline, the vehicle will not stay in Ready mode, or communication faults spread across several modules.

How Serious Is This Code?

U140A ranges from an inconvenience to a significant electrical fault, depending on how often the Terminal 30 circuit opens and which modules lose power. At the mild end, you may only see stored faults after a low-voltage event or an intermittent connection. At the serious end, the gateway can lose reliable power sense, modules can reboot, and the Enyaq can set additional network and power supply codes. That can affect convenience systems, charging functions, and in some cases drivability or startup reliability. The code itself does not prove a failed gateway. It points to a power feed problem that needs prompt circuit testing. Treat it as high priority if the fault is current, repeatable, or tied to widespread communication loss.

Common Misdiagnoses

Technicians often replace the 19-Gateway too early because the code appears in the gateway and the scan tool shows several network complaints. That approach misses the real pattern. An open Terminal 30 feed can make a healthy gateway report secondary faults from other modules. Another common mistake is checking battery state only at rest and skipping loaded circuit tests. A battery connection, fuse link, power distribution point, or harness joint can pass a quick voltage check and still open under vibration or current draw. Some also clear codes before recording freeze-frame data, which erases the timing clues. Avoid wasted spending by tracing the constant power path first, checking voltage drop under load, and verifying connector tension before condemning any module.

Most Likely Fix

The most common confirmed repair is restoring a stable Terminal 30 feed to the 19-Gateway circuit, not replacing the gateway first. In practice, that often means correcting a loose or heat-damaged fuse connection, repairing corrosion at a power distribution point, or fixing an open or high-resistance section in the battery feed wiring. A poor ground can also confuse diagnosis, so verify grounds with the same discipline. After repair, clear faults, cycle the vehicle through normal sleep and wake events, and then road test it. The exact drive time varies because monitor enable criteria differ by Skoda platform and system, so check service information to confirm when the fault logic has fully rerun.

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