Car Diagnostics
Diagnostic tool

Manufacturer coding: how to activate "hidden" features on VAG, BMW and Mercedes via OBD

What long coding on VAG (VCDS) is, byte coding on BMW (ISTA/E-Sys), Xentry SCN on Mercedes. Which features you can legally enable, risks, and how not to "brick" an ECU.

AI-generated 3 min read

Manufacturer coding — changing ECU behaviour without physical intervention, via configuration bytes the manufacturer stored in firmware. VAG (VW/Audi/Skoda/Seat) calls it long coding, BMW — byte coding, Mercedes — SCN coding via Xentry. Below: what you can legally enable, which tools you need, and the risks.

What is NOT coding

  • Chip tuning / remap — replacing the entire firmware (not coding, but re-flash). Risky, often illegal.
  • Adaptation reset — resetting Adaptations — a separate operation via RoutineControl $31.

Coding is parameterisation of the existing firmware. E.g. activating “auto-fold mirrors on lock” which the manufacturer put in code but disabled for the base trim.

VAG Long Coding (via VCDS or OBDeleven)

VCDS ($240-450) — officially the best VAG tool. OBDeleven — cheaper alternative via smartphone.

  • Cornering lights (fog lights as “turn assist”)
  • Daytime Running Lights (DRL) on TFL
  • Auto-fold mirrors on lock
  • Comfort blinker (3 blinks instead of 1)
  • Highbeam Assist (if camera present)
  • Auto-lock doors after 15 km/h
  • Rear window wiper on reverse

How it’s done

  1. VCDS plugs into the OBD port
  2. Pick ECU (say, Comfort Module 09)
  3. Read Long Coding — a string of 15-20 hex bytes
  4. Change specific bits per the label file
  5. Write back

Key thing — the label file (a text-described list of what each byte does). For VAG publicly available via community (Ross-Tech Wiki).

BMW Byte Coding (via ISTA/D + E-Sys)

For BMW you need a computer + ENET cable ($30) + E-Sys ($0 open-source or via ISTA/D $200). ELM327 not supported — only BMW-native protocols.

  • Video-in-motion (nav not locked while driving)
  • iDrive from steering wheel
  • Comfort access (keyless) — if hardware already installed
  • Emergency brake light (flashes on hard braking)
  • DAB radio (if tuner present)

Risks

  • BMW often checks the “signature” of coding on firmware updates — after update your coding resets
  • Coding error can push the ECU into “cyclic reboot” — needs re-coding to recover

Mercedes SCN Coding (via Xentry)

Hardest — SCN (Software Calibration Number) online coding — needs an official Mercedes Xentry Diagnostics licence (shops only or grey market at $500+/session). Online link to Mercedes servers per coding.

Things you can change:

  • Auto-close on fob
  • Fuel-cap dispenser type
  • Cluster language (locale change)
  • Speed-limited plate (in Germany)

Actually practiced only at authorised shops via expensive software.

General risks of coding

  1. Warranty void — manufacturer sees non-standard bytes via diagnostic session at service
  2. Inspection issues — some codings (e.g. removing speed limit on US cluster) may fail inspection
  3. Coding overwritten on firmware update — annoying to lose after a dealer visit
  4. Coding disabled on battery replacement — then you have to redo
  5. Bricked ECU — on coding interrupt (battery dies) ECU can become “dead”, recovery only through dealer

What Car Diagnostics does

We don’t do coding — it’s risky and requires manufacturer protocols (not ELM327). Our app can:

  • Read current coding
  • Show delta between factory and current
  • Recommend the tool for the required change (VCDS for VAG, E-Sys for BMW)

That’s the info level. Real changes — through specialised tools.

To read current coding — pair an ELM327 adapter on free tier, in “ECU Coding Info” you’ll see the bytes. Label-file decoding — on paid tier for VAG and BMW.