What is long coding on OBDeleven?

Long coding is editing the raw coding value inside a control module, byte by byte and bit by bit. Each bit is a switch the factory set for your car's exact specification. Long coding changes those switches directly, which is how features the car already has in software but never had enabled get turned on.

Do I have to code a new battery on a VW or Audi?

On any VAG car with energy management, yes. The car tracks the age and state of the battery it thinks is fitted and adjusts its charging strategy accordingly. Fit a new battery without registering it and the car keeps charging to the old battery's worn-out profile, which shortens the new battery's life. Registering it means writing the new capacity and part number so the strategy resets.

What is the difference between OBDeleven credits and the Pro plan?

Credits are consumable and pay for one-click apps — prewritten routines that apply a known change for you. The Pro plan is a subscription that unlocks the manual tools: long coding, adaptation channels, and deeper live data. Credits do not expire into Pro and Pro does not make one-click apps free; they are two separate things.

VCDS is a Windows laptop tool with a one-off purchase and dealer-grade depth, and it is the reference the VAG community documents against. OBDeleven is a Bluetooth dongle driven from your phone, cheaper to get into, with one-click apps that make common changes safe for beginners. If you code occasionally and want it in your pocket, OBDeleven. If you do heavy diagnostic work and want everything unlocked with no subscription, VCDS.

Which cars does OBDeleven work on?

The VAG group — Volkswagen, Audi, Seat, Škoda and Cupra. It also does generic OBD2 fault reading on other makes, but the coding and adaptation features that make it worth owning are VAG-only.

OBDeleven Long Coding, Battery Coding & Credits Explained (2026)

What long coding actually is

Every control module in a VAG car carries a coding value — a block of bytes the factory wrote to match your exact car. Each bit inside those bytes is a yes/no switch: fog lights fitted or not, mirrors fold or they don't, seatbelt chime on or off.

Long coding is editing those switches directly. You are not adding a feature — you are enabling one the car's software already understands but was told it doesn't have. That distinction matters, because it explains the single most common disappointment: if the hardware isn't physically there, no amount of coding will conjure it. Coding cornering fogs into a car with no fog lamps gives you nothing.

What it does reliably: folding mirrors on lock, needle sweep on start, comfort windows from the key, disabling the start-stop default, lap timer on Audi MMI, video in motion, seatbelt chime, coming-home lighting duration, gauge staging. All of these are switches, not additions.

Before you touch anything. Read and save the module's original coding value first — photograph it if nothing else. A wrong long-coding value is usually harmless and reversible, but only if you know what it said before. This is the whole reason experienced coders never work without a backup of the string.

Battery coding — the one job that is not optional

If your car has energy management (essentially every VAG car of the last fifteen years), the battery is not a dumb box. The car keeps a record of the battery it believes is fitted: capacity, technology, part number, and how tired it thinks that battery is. It uses that record to decide charging voltage and when to shed load.

Fit a fresh battery without telling the car and the car keeps charging to a worn-out battery's profile. The new battery gets managed as if it were four years old — chronically undercharged, cycling in a way it wasn't designed for. This is the mechanism behind the common complaint that a replacement battery "died in two years."

Registering the battery writes the new capacity and part number and resets the ageing counter. Two things worth knowing:

Same-spec swaps — you are mostly resetting the history counter so the strategy starts fresh.
Changing type or size — going from a conventional flooded battery to AGM, or changing Ah, must be coded. Get this wrong and the charging profile is matched to a chemistry you don't have, which is worse than not coding at all.

This single job is the reason a lot of people buy the tool: one battery registration usually costs more at a workshop than the dongle does.

Credits and Pro — what each one actually buys

This is the most misunderstood part of OBDeleven, and the reason for a lot of buyer's remorse.

	Credits	Pro plan
What it is	Consumable tokens	Subscription
Pays for	One-click apps — prewritten routines that make a known change for you	The manual tools: long coding, adaptation channels, deeper live data
Runs out?	Yes, per use	No, but it lapses when you stop paying
Best for	One specific retrofit you'll do once	Anyone who wants to code freely and learn the modules

They are separate products. Buying Pro does not make one-click apps free, and stacking credits does not unlock long coding. If your plan is "enable folding mirrors and never touch it again," credits are the cheaper route. If you intend to actually learn your car, Pro is what you want, because long coding is where the real capability lives.

OBDeleven vs VCDS

These get compared constantly and the honest answer is that they're built for different people.

	OBDeleven	VCDS
Runs on	Phone, Bluetooth dongle	Windows laptop, USB cable
Cost model	Cheap entry, then credits or subscription	One-off purchase, everything included
Beginner safety	High — one-click apps are guided	Lower — you drive it manually
Depth	Very good; some deep functions sit behind Pro	Dealer-grade, nothing withheld
Community docs	Growing	The reference most guides are written against

Practical rule: if you code occasionally, want it in your pocket, and value being talked through a change — OBDeleven. If you do sustained diagnostic work, want zero subscription, and are following community write-ups that quote VCDS screens — VCDS. Plenty of people who work on VAG cars seriously own both.

Live data — the underrated part

Coding gets the attention, but live data is what turns the tool into a diagnostic instrument rather than a toy. Reading measuring blocks while the engine runs is how you find the fault instead of guessing at the code: fuel trims that tell you about an unmetered air leak, requested versus actual boost that separates a turbo problem from a sensor problem, misfire counters per cylinder, DPF soot load and regeneration status, lambda response.

A fault code names a symptom. Live data is where the cause shows up.

Where it stops

Worth knowing before you spend money:

Hardware still has to exist. Coding enables, it does not install.
Some late modules are locked. Newer platforms with component protection or security access will refuse coding without dealer-level authorisation, no matter which tool you hold.
It is not a flash tuner. Coding and adaptation are not the same thing as remapping the engine ECU.
VAG only for the good stuff. Generic OBD2 reading works on anything; the coding depth does not.

Questions people actually ask

Will long coding void my warranty?

Coding is recorded in the module and a dealer can see the value has changed. In practice, a cosmetic change is unlikely to cause trouble on an unrelated warranty claim, but anything safety-adjacent — lighting behaviour, restraint systems, driver assistance — is a genuinely bad idea on a car still under warranty. Save the original value so you can put it back before a service visit.

Can I brick a module?

A wrong long-coding value normally produces a fault light or a feature that misbehaves, and writing the original value back fixes it. Real damage comes from interrupting a write — a flat car battery mid-coding is the classic way to turn a reversible mistake into an expensive one. Code with a healthy battery or a charger connected.

Does it work on my non-VAG car?

For reading and clearing generic engine fault codes, yes. For coding, adaptations and the module-level work described on this page, no — that depth is VAG-specific. For other makes, the brand interfaces in our shop are the right route.

Do I need Pro just to read fault codes?

No. Reading and clearing faults across modules works without a subscription. Pro is about the manual coding and adaptation tools, not basic diagnostics.

Is the battery registration worth doing myself?

It is the clearest payback on the tool. Workshops charge for the procedure, it takes a couple of minutes once you know where it lives, and skipping it measurably shortens a new battery's life.

The tool this page is about.

OBDeleven NextGen — €119, shipped free, 2-year warranty.

See it in the shop → All VW / Audi tools

OBDeleven: long coding, battery coding and credits, explained