U1406 – Static current too high (Skoda)

Skoda-specific code — factory diagnostic data

U1406 means the Skoda Enyaq has a battery draw problem while the vehicle should be asleep. In plain terms, something stays awake or keeps consuming too much power after shutdown, so the 12-volt battery can discharge and cause warning messages, no-start complaints, or repeated low-voltage faults. According to Skoda factory diagnostic data, this manufacturer-specific code means static current too high. On this platform, the 19-Gateway logs the fault when it sees an excessive quiescent current condition during the vehicle’s rest phase. That does not prove one bad module. It tells you the Gateway detected abnormal current draw and you must identify what remains active, powered, or network-awake.

U1406 Quick Answer

U1406 on a Skoda means the Gateway detected excessive current draw with the vehicle at rest. Something in the Enyaq stays powered, wakes the network, or leaks current when it should not.

What Does U1406 Mean?

The official Skoda definition is simple: static current too high. In practice, the 19-Gateway has recognized that the vehicle did not settle into a normal low-power sleep state, or that the standby current stayed above the expected range long enough to set a fault.

For diagnosis, separate the message from the root cause. The code reports an abnormal current condition, not a failed part. The Gateway is monitoring vehicle sleep behavior, power management status, and module activity across the network. That matters because one awake control unit, a sticking relay, a powered accessory, poor power management logic, or wiring leakage can all create the same U1406 fault.

Theory of Operation

Under normal conditions, the Skoda Enyaq enters a controlled sleep sequence after shutdown. The 19-Gateway coordinates network traffic, power state transitions, and wake-up requests between control modules. As timers expire, modules stop messaging, loads switch off, and the 12-volt system current drops to a low standby level.

U1406 sets when that shutdown process does not complete correctly. A module may keep transmitting, a door or latch input may falsely report activity, an accessory may remain energized, or a power feed may bypass normal sleep control. The result stays the same: the Gateway sees excessive static current and flags a network-related power management fault that requires current draw testing and sleep-state verification.

Symptoms

This code usually shows up with battery drain complaints, sleep-state faults, or scan results that point to an awake network.

• Scan tool behavior: Multiple modules stay awake, respond slowly, or show recent wake-up activity after shutdown.
• Battery drain: The 12-volt battery loses charge after the Enyaq sits parked.
• No-start or low-voltage start: The vehicle may not power up normally after sitting.
• Warning messages: The cluster may show low electrical system voltage or convenience system faults.
• Intermittent faults: Several low-voltage or communication codes may appear across different modules.
• Sleep disruption: Interior systems, control units, or network activity may continue longer than normal after lock-up.
• Convenience issues: Remote access, charging timers, or body functions may behave erratically if modules never enter full sleep.

Common Causes

• Battery state of charge too low: A weak high-voltage support strategy or a poorly charged low-voltage battery can keep Skoda control units awake and trigger a static current too high fault in the 19-Gateway.
• Battery condition degraded: An aged or internally weak low-voltage battery can distort sleep behavior and make the gateway interpret standby current draw as excessive.
• Control module fails to enter sleep mode: One networked module can stay awake after shut-down and continue drawing current, which the gateway then flags as abnormal static current.
• Wake-up signal remains active: A stuck switch input, door status signal, latch input, or network wake request can prevent the vehicle from reaching normal quiescent current.
• Aftermarket accessory draw: Added trackers, cameras, chargers, audio equipment, or non-OEM telematics often draw power during key-off and can keep the Skoda network active.
• Corrosion or high resistance at power or ground connections: Poor connections can cause unstable module shutdown behavior and repeated wake events that increase standby current.
• Fuse-box or power distribution fault: A sticking internal feed path or damaged fuse carrier can leave one branch energized when the Enyaq should be asleep.
• Harness damage in a wake or communication circuit: Chafed wiring can short a signal or intermittently wake modules, which raises key-off current draw.
• Gateway software or coding issue: Incorrect gateway configuration or outdated Skoda software can mismanage sleep authorization or misreport current-related faults.

Diagnosis Steps

You need a capable scan tool with full Skoda module access, a wiring diagram, a current clamp or ammeter, and a digital multimeter. Use the scan tool first. Then verify power distribution and network sleep behavior. For this code, freeze frame data matters. Review ignition state, vehicle speed, and all related DTCs. Use a snapshot during shutdown if the fault acts intermittently.

1. Confirm U1406 in the 19-Gateway and record all stored, pending, and related network or body DTCs. Save freeze frame data before clearing anything. For this communication and gateway-related fault, note ignition state, vehicle speed, terminal status, and any module that logged sleep, wake, or undervoltage faults. Freeze frame shows the exact conditions when the code set. A scan-tool snapshot helps later if the current draw problem appears only during a shutdown cycle.
2. Check whether all expected control units appear on the network scan. Then inspect fuses, fuse carriers, and main power distribution before probing the gateway or any module connector. Look for a branch that stays powered when the vehicle should begin shutdown. On the Enyaq, this early step often reveals a wake source or a module that never drops offline.
3. Verify battery condition and low-voltage supply stability. Then test gateway and suspect module powers and grounds with voltage-drop testing under load. Do not trust unloaded voltage or continuity alone. A high-resistance ground can look normal with no load. With the circuit operating, ground drop should stay below 0.1V. If power or ground quality fails here, fix that first.
4. Inspect the 19-Gateway connectors, nearby harness routing, ground points, and fuse-box connections. Check for spread terminals, moisture, corrosion, heat damage, and poor terminal tension. Follow the harness toward any recently serviced or accessory-equipped areas. Skoda network faults often trace back to connector fit or a disturbed ground eyelet rather than a failed gateway.
5. Review live data for terminal status, bus sleep status, wake-up source information, and module awake counters if your scan tool provides them. Compare shutdown behavior across modules. A healthy system goes to sleep in stages. If one unit stays awake, identify which network branch remains active and focus there instead of replacing parts blindly.
6. Measure actual key-off current draw with an ammeter or current clamp after the vehicle enters its normal sleep window. Do not open doors, wake the network, or disturb latches during the test. If current stays high, pull fuses one at a time only after the sleep period completes. Watch for the current to drop. That isolates the branch causing the excessive static draw.
7. If the suspect branch contains networked modules, test communication integrity on that branch. For CAN wiring checks, measure resistance between CAN+ and CAN- with ignition off and the battery disconnected. A healthy bus reads about 60 ohms. A reading near 120 ohms or OL points to an open or lost termination. Next, with ignition on, check CAN bias voltage to ground. Healthy CAN+ and CAN- typically sit near 2.5V. Ignition-off voltage readings do not provide a valid reference.
8. Check for wake-up inputs that remain active after shutdown. Verify door, hood, latch, handle, charger-port, and convenience inputs in live data if applicable to the Skoda platform you are testing. If a switch never changes state, or toggles by itself, inspect that input circuit and its connector. One false wake request can keep several modules alive.
9. Investigate aftermarket equipment and recent repairs. Disconnect non-OEM accessories from their power feeds one at a time, then repeat the sleep-current test. Many repeat U1406 cases come from add-on devices that backfeed a wake circuit or pull current after key-off.
10. Only after circuit, power, ground, network, and sleep-state checks pass should you consider software updates, coding corrections, or a control module fault. Verify current Skoda service information and check whether the gateway or another module has a software campaign or calibration revision related to battery management or sleep behavior.
11. Clear codes only after you correct the root cause. Then repeat the full shutdown process, confirm normal sleep current, and rescan all modules. Make sure U1406 does not return as pending or stored. If a hard fault remains, it usually returns quickly at key-on or during the next sleep cycle.

Professional tip: Do not condemn the 19-Gateway just because it set U1406. The gateway often acts as the reporter, not the cause. On Skoda vehicles, the real fault commonly sits in a module that stays awake, a wake input that never rests, or a power distribution issue that prevents sleep. Prove the current path before replacing any control unit.

Possible Fixes

• Charge, test, and replace the low-voltage battery if it fails verification: Restore proper standby voltage only after you confirm battery condition and charging support problems.
• Repair poor power or ground connections: Clean, tighten, or repair corroded grounds, fuse-box feeds, and power distribution connections that fail voltage-drop testing.
• Repair damaged wiring or connectors in the wake or network circuit: Correct opens, shorts, chafed insulation, water intrusion, or terminal spread found during harness inspection.
• Correct the module or branch that stays awake: Fix the verified module, switch input, or network branch that prevents normal sleep mode and causes excess static current.
• Remove or rewire aftermarket accessories: Isolate added devices from wake-sensitive circuits and use an approved power strategy if the accessory caused the drain.
• Update or correct Skoda module software or coding: Apply verified software updates or coding corrections when testing shows normal hardware but sleep management remains incorrect.
• Replace a control module only after full verification: Replace the gateway or another module only when power, ground, network integrity, and wake inputs all test good and the module still fails sleep-control logic.

Can I Still Drive With U1406?

You usually can drive a Skoda Enyaq with U1406 if the vehicle starts normally and no critical warnings appear. This code points to excessive static current draw, logged by the 19-Gateway, not a confirmed failed module. In many cases, the immediate issue is battery drain during key-off periods, not an active driving fault. Still, you should not ignore warning messages, repeated low-voltage events, or network faults that appear with it. A high parasitic draw can pull system voltage down, wake control units, and trigger erratic electronic behavior. If the Enyaq shows no-start symptoms, repeated 12-volt battery discharge, gateway communication issues, or multiple control module warnings, limit use until you test the battery, charging support strategy, and sleep-state current draw.

How Serious Is This Code?

U1406 ranges from an inconvenience to a significant reliability problem. At the mild end, the vehicle may drive fine but discharge the 12-volt battery after sitting. That creates customer complaints, repeat jump-starts, and misleading low-voltage codes. At the serious end, excessive static current can keep network modules awake, destabilize the gateway, and create intermittent communication faults across the Skoda platform. The code itself does not prove a safety system failed, but unstable supply voltage can affect many modules at once. Treat it as more urgent if the Enyaq has recurrent dead-battery conditions, gateway faults that return quickly, or signs that a control unit never enters sleep mode. The key risk is loss of reliability and false network symptoms, not a single obvious failed part.

Common Misdiagnoses

Technicians often replace the 12-volt battery first, then stop testing when the vehicle starts again. That wastes money when a module stays awake, a door or latch input remains active, or an accessory circuit keeps drawing current after shutdown. Another common mistake is blaming the 19-Gateway because it stored the code. The gateway often reports the problem, but another module or circuit usually causes it. Some also measure current too early, before the Skoda network enters sleep mode, and misread normal post-shutdown activity as a fault. Others unplug modules randomly, which can wake the network and invalidate the test. You avoid misdiagnosis by using a stable test setup, waiting for sleep conditions, checking wake-up inputs, and confirming which circuit changes current draw before replacing anything.

Most Likely Fix

The most common repair direction is correcting the reason the Skoda network does not go to sleep. That often means repairing a wake-up input, latch or switch signal, wiring issue, poor ground, connector corrosion, or an aftermarket device that keeps a control unit active. Another frequent fix is addressing a specific module that continues drawing current after shutdown, but only after you verify power, ground, network integrity, and current change during isolation testing. Do not treat the gateway as the default failed part. After the repair, let the vehicle complete a full shut-down period, then recheck static current and confirm U1406 does not reset. The exact confirmation time varies by platform and monitor enable criteria, so consult Skoda service information before final delivery.

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