B1916 – Backup battery service life critical (Skoda)

Skoda-specific code — factory diagnostic data

Last updated: April 13, 2026

Definition source: Skoda factory description · Autel MaxiSys Ultra&EV. Diagnostic guidance is based on factory-defined fault logic for this code.

B1916 means the telematics unit has judged its backup battery near the end of usable life. In plain terms, your Skoda Enyaq may still drive normally, but emergency or connected backup functions can become unreliable if main vehicle power drops out. This is a manufacturer-specific Skoda code, not a universal meaning shared across all brands. According to Skoda factory diagnostic data, B1916 indicates backup battery service life critical in the body system, logged by the 75-Telematics Communication Unit. The code points to a monitored reserve power source and its health status. It does not prove the telematics module itself has failed, and it does not justify parts replacement before basic power, ground, and battery-condition checks.

🔍Decode any Skoda Enyaq VIN — free recalls, specs & safety ratings — free VIN decoder with NHTSA data

B1916 Quick Answer

On a Skoda Enyaq, B1916 means the telematics control unit sees its internal or associated backup battery at a critical end-of-life condition. The telematics module monitors charge acceptance and retention over time — not just voltage. A battery that reads 3.7 V at rest can still fail the module’s capacity test if it cannot hold a charge under load. The usual result is reduced reserve power for telematics functions during a main power interruption.

What Does B1916 Mean?

The official Skoda definition for B1916 is backup battery service life critical. That means the 75-Telematics Communication Unit detected that its reserve battery can no longer support the function it was designed to protect. In practice, the vehicle may show no driveability issue, yet the telematics unit may lose operation sooner than expected during a power loss or low-voltage event.

For diagnosis, separate the message from the root cause. The code tells you what the module detected, not which part failed. The telematics unit monitors the backup power source through internal battery-management logic, charging status, and plausibility checks. Aged battery chemistry, poor charging feed, high resistance at connectors, unstable module power or ground, or an internal fault in the monitored battery path can all trigger the same service-life-critical judgment.

Theory of Operation

Under normal conditions, the Skoda Enyaq telematics system runs on vehicle power and maintains a small backup energy source — typically a lithium polymer or lithium iron phosphate cell in the 3.6–3.8 V nominal range — for continuity. That reserve supply keeps the 75-Telematics Communication Unit alive briefly if primary 12-volt power drops. The module supervises backup battery condition continuously. It does not simply measure resting voltage. Instead it evaluates charge acceptance rate, self-discharge rate, capacity retention under load, and internal plausibility over many charge-discharge cycles.

This code sets when that supervision logic decides the backup battery has reached a critical service-life state. The problem may come from the cell itself, but the charging path matters just as much. Low supply quality, excessive resistance, connector corrosion, or poor module ground can distort the battery health calculation. That is why external circuit verification always comes before condemning the battery or the module.

Symptoms

Drivers often notice little or nothing at first, so the scan result and module behavior matter more than a dramatic warning.

• Warning message: A connected-services, emergency-call, or telematics warning may appear in the instrument cluster or infotainment system.
• Stored code: B1916 appears in the 75-Telematics Communication Unit, sometimes without any other body faults.
• Intermittent telematics functions: Connected features may act inconsistently after low-voltage events or after the vehicle sits.
• Emergency backup concern: Reserve operation for telematics-related functions may shorten during a main power interruption.
• No driveability complaint: The Enyaq usually drives normally because this code targets a body-system backup power function, not the high-voltage traction system.
• Low-voltage history: Other modules may show undervoltage or supply-related faults if the vehicle has had 12-volt battery or charging issues.
• Return after clearing: The code often comes back after a self-test if the backup battery health remains below the module’s acceptable threshold.

Common Causes

• Aged telematics backup cell reaching end of capacity: The small lithium cell inside or connected to the 75-Telematics Communication Unit loses charge retention over time. The module flags this as critical service life once capacity drops below its programmed threshold.
• Backup battery charge deterioration from repeated low-voltage events: Repeated deep discharge caused by a weak 12-volt battery or charging faults accelerates cell wear and brings the module’s health calculation forward.
• Poor power or ground feed to the telematics unit: High resistance in the main supply or ground path prevents the backup cell from receiving adequate charge current, causing the module to underestimate actual cell health.
• Connector corrosion or terminal spread: Added resistance at the telematics unit connector or, where accessible, at the backup cell connector skews charging, monitoring, or plausibility checks.
• Harness damage in the telematics power circuit: A rubbed, pinched, or partially open wire can interrupt charge current or status feedback and set the code prematurely.
• Battery monitoring logic detecting true end-of-life trends: The telematics unit calculates health from charge retention and internal response rather than voltage alone. A cell can read correct open-circuit voltage and still fail the capacity check.
• Incorrect previous repair or coding issue: An improperly installed telematics component or an unmatched replacement battery assembly can produce implausible battery health data and false critical-life flags.

Diagnosis Steps

You need a capable scan tool that can communicate with VAG/Skoda body modules, a digital multimeter, a battery support unit, and access to wiring information for the Enyaq MEB platform. A milliohm or low-resistance adaptor helps for contact resistance checks. Do not rely on static voltage alone at any point — the backup cell and the supply circuit require loaded testing to surface real faults.

1. Record all stored faults before clearing anything. Connect to the 75-Telematics Communication Unit and read every stored, pending, and confirmed DTC. Save freeze frame values, especially battery voltage at fault entry, ignition state, and any backup battery health or charge-state parameter the module exposes. Also read fault memory from adjacent modules such as the 19-Gateway and 61-Battery Regulation, because recurring low-voltage events there often precede a backup battery service-life flag in the telematics unit. Do not clear codes yet.
2. Inspect the 12-volt supply circuit to the telematics unit before touching the module. Check the fuse feeding the 75-Telematics Communication Unit. Measure supply voltage at the module connector with the ignition on. You should see 12.5–14.5 V depending on charge state. A value below 11.8 V under accessory load points to a 12-volt system problem, not a backup battery problem. Fix the main supply before continuing.
3. Perform a loaded voltage-drop test on both the supply and ground sides of the telematics unit. With the ignition on and the module active, place the positive meter lead at the supply terminal of the module connector and the negative lead at the battery positive terminal. Reading above 0.2 V indicates a resistance fault in the feed path. Repeat with the meter measuring from the module ground terminal to battery negative — drop above 0.1 V means a compromised ground. Repair any resistance fault found before evaluating the backup battery, because a weak feed causes the cell to charge slowly or partially and distorts the module’s learned health value.
4. Inspect all connector faces and harness routing for the telematics unit. Unplug the main connector and check terminal tension, pin fit, moisture tracks, and corrosion. On Enyaq MEB platforms, the telematics unit is typically mounted in the front electronics compartment or behind the instrument panel. Follow the harness through trim-covered areas where wiring can trap moisture or chafe against brackets. Backed-out terminals at the module connector cause intermittent charging faults that do not always show as a hard circuit fault in the DMM test.
5. Use the scan tool to review live data for backup battery status. Request live data from the 75-Telematics Communication Unit. Parameters of interest include backup battery voltage, backup battery charge state percentage (if available), and any backup battery health or service-life value exposed by the platform. A healthy backup cell in a MEB Skoda telematics system typically reads 3.6–3.85 V at rest on platforms that expose this data. Values below 3.2 V at rest with no recent discharge event, or a charge-state percentage below 20 % at rest, suggest the cell has lost significant capacity. Note that voltage alone cannot confirm end-of-life — a cell can read 3.6 V at rest and still fail a capacity test.
6. Evaluate backup battery capacity — not just voltage. This is the step most technicians skip, and it is the most important one for B1916. If your scan tool does not provide a capacity readout, assess the cell indirectly: clear the DTC, perform a complete key-off sleep cycle with the vehicle fully locked for at least 10 minutes, then wake the system and immediately re-read backup battery live data. A healthy cell should show minimal self-discharge. If the module logs B1916 again within one or two key cycles after clearing, and external supply and ground circuits tested good in steps 2–4, then the cell’s charge retention has genuinely failed. On platforms where a guided test or component test is available for the telematics unit backup battery, always run it before condemning the cell — the guided test applies a controlled load and measures the voltage response, which directly evaluates capacity rather than just resting state.
7. Check for related charging-system and 12-volt battery faults in the 61-Battery Regulation module and the 19-Gateway. A backup battery service-life code often follows repeated episodes of low 12-volt system voltage. If the main LV battery is marginal or the DC-DC converter in the Enyaq has logged low-voltage events, those conditions accelerate cell wear inside the telematics unit. Confirm the LV battery state of health and the DC-DC converter output. A DC-DC output below 13.5 V at highway speed on an Enyaq under typical load is worth investigating. Correct any charging-system finding before replacing the telematics backup cell.
8. Determine serviceability before ordering parts. On MEB-based Enyaq platforms, the backup battery may be integrated into the telematics unit assembly or available as a separate service part. Check Skoda ELSA or official parts information for the exact build year. If the cell is serviceable separately, match the replacement to the OEM specification — lithium polymer cells are chemistry-sensitive, and substituting an incorrect capacity or chemistry produces incorrect health readings and may re-trigger B1916 after installation. If the cell is not separately serviceable, the full telematics unit requires replacement.
9. Perform required adaptation after replacement. After replacing the backup battery or the telematics unit assembly, complete any basic setting, adaptation, or coding procedure specified in Skoda service information. Some platforms require a learned reset so the module begins with a fresh health baseline for the new cell. Skipping this step can cause the module to carry over a worn-battery learned value and flag the new cell as critical-life within a short time.
10. Verify the repair with sleep-cycle confirmation. Clear B1916, allow the vehicle to complete at least one full key-off sleep cycle (vehicle locked, no remote access, minimum 30 minutes), then wake the system and re-read fault memory and live data. If backup battery voltage and charge state show normal values and B1916 does not return after two or three complete sleep cycles, the repair is confirmed. If the code returns immediately on wake-up, recheck the supply circuit and ground under load — a resistance path that was borderline at test time can worsen when module current draw peaks during the telematics wake sequence.

Professional tip: A resting voltage check on a lithium backup cell tells you very little about its true condition. Always combine voltage data with a self-discharge evaluation across a sleep cycle, or use a scan tool guided test if the platform supports one. Technicians who condemn the telematics unit based on resting voltage alone often find the fault returns after replacement because the supply or ground circuit was the real driver of premature cell wear.

Possible Fixes

• Repair high-resistance power or ground connections: Clean, tighten, or repair the verified feed or ground fault that prevents correct telematics backup battery charging.
• Repair damaged telematics wiring or terminals: Fix any confirmed open, chafed, corroded, or loose connection in the backup battery or telematics supply circuit.
• Address the main 12-volt low-voltage condition: Correct a weak LV battery, DC-DC converter fault, or repeated low-voltage event that accelerated backup battery wear.
• Replace the backup battery if serviceable and confirmed end-of-life: Follow Skoda service information after circuit integrity and supply quality checks pass and capacity evaluation confirms the cell cannot hold charge.
• Replace the telematics unit assembly if the backup cell is integrated: Only after external wiring, supply, and ground tests pass and capacity evaluation supports an internal cell fault.
• Perform required adaptation or coding after replacement: Complete any necessary basic setting or reset procedure so the Enyaq can learn the health baseline of the new backup battery correctly.

Can I Still Drive With B1916?

You can usually keep driving a Skoda Enyaq with B1916, because this code points to backup battery service life in the 75-Telematics Communication Unit, not to the high-voltage drive system. The vehicle will often drive normally. The real risk involves reduced telematics reserve power. That can affect connected-services and emergency-call functions that rely on the module staying alive when main 12-volt power changes or drops out. Treat it as a body-system fault requiring timely diagnosis, not a no-drive command. If other communication, emergency-call, or LV battery-management faults appear alongside B1916, inspect the system promptly and verify module power, ground, and stored fault data before replacing any battery or control unit.

How Serious Is This Code?

B1916 usually starts as an inconvenience, but it can become relevant if the telematics unit needs its backup power during a low-voltage event. In most cases, the driver notices no drivability problem. That said, the code means the module has judged the backup cell’s service life as critical, so reserve operation may no longer meet Skoda’s expected standard. On an Enyaq, that matters more for connected-services and emergency-backup functions than for propulsion. Severity rises if the vehicle also logs telematics communication faults, internal module faults, or unstable 12-volt supply codes. Diagnose it soon, especially before condemning the telematics unit, because poor charging, connector resistance issues, or main LV battery degradation can falsely accelerate a backup cell’s apparent service life.

Common Misdiagnoses

The most frequent error is replacing the telematics unit or backup cell based on resting voltage alone. A lithium backup cell can show 3.6–3.7 V at rest and still fail a capacity check, because end-of-life lithium cells lose charge retention rather than resting voltage first. Technicians who check voltage at the module connector, see a normal reading, and then order the module anyway skip the self-discharge evaluation that actually matters for this code. A second common mistake is ignoring the 12-volt supply circuit entirely. On Enyaq MEB vehicles with marginal LV batteries or repeated low-voltage events from overnight accessory use, the real problem is chronic undercharging of the backup cell — fixing the main LV system resolves the B1916 without touching the telematics unit. Also avoid relying on a single key cycle for confirmation. This code requires sleep-cycle verification because the module re-evaluates backup battery health during the wake sequence, not immediately at key-on.

Most Likely Fix

The most common repair path is to confirm clean supply and ground to the telematics unit, rule out main LV battery degradation, then replace the backup cell (or the telematics assembly if the cell is not separately serviceable) after self-discharge evaluation across a sleep cycle confirms lost capacity. A second frequent repair involves correcting a marginal or failed 12-volt battery or DC-DC converter fault that chronically undercharged the backup cell and caused premature service-life deterioration. After any repair, perform the required adaptation, clear B1916, and confirm the code does not return across at least two complete sleep cycles with normal live data values for backup battery voltage and charge state.

Repair Costs

Repair cost depends on whether the confirmed root cause is wiring, connector condition, the backup cell, or the telematics unit assembly.