OBDeleven long coding

OBDeleven long coding library

Long codings, one vehicle at a time

A shared library of OBDeleven long codings. Each entry stands on its own and is tied to a vehicle and a module. This is not a forum.

Add a long coding Browse vehicles

Latest

Volkswagen Golf 7 · MQB

Golf 7 Cent Elect (J519)

Module 09 · Central electrics Moderate risk 0

Volkswagen Golf 7 · MQB

Golf 7 Auto HVAC (J301)

Module 08 · Climate control Moderate risk 0

Volkswagen Golf 7 · MQB

Golf 7 ABS BRAKES (J104)

Module 03 · Brakes Moderate risk 0

Audi Q3 F3 · MQB

2020 Q3 F3 AUTO TRANS (J743)

Module 02 · Transmission electronics 2020 Moderate risk 0

All long codings

Browse vehicles

Updated 18 Nov 2026

What is OBDeleven long coding?

Long coding is how many Volkswagen Group cars store feature flags inside a control module. Instead of a single on/off switch, the module keeps a coding string made of bytes. Each byte is eight bits. Changing one bit can enable or disable a function that the hardware already supports, such as lighting behaviour, convenience menus, or how a driver-assistance module presents itself.

Tools such as OBDeleven (and VCDS) read that string from the car, let you alter selected bytes or bits, and write the result back. That is different from adaptation channels, which usually hold single parameters or thresholds. It is also different from OBDeleven One-Click Apps: those wrap a known change behind a guided flow. Manual long coding means you open the module yourself, inspect the coding string, and apply the change described on an entry in this library.

Long Coding Hub is a community library for that manual path. Every published entry is one vehicle and one module, with the coding string and notes the contributor shared. The site does not invent values and does not certify that a string is correct for your car.

How to use a long coding from this site with OBDeleven

  1. Find your vehicle in Browse vehicles, or search by model, module, or title. Open the model page, then the module that matches the entry.
  2. Read the entry carefully: the coding string, risk level, SFD status, equipment notes, and what the contributor says the change does. Compare the vehicle, platform, and year range with your own car.
  3. In OBDeleven, connect to the car and open the same control module. Make a backup of the current coding before you change anything.
  4. Locate the byte and bit described in the entry (or paste/compare the full string if that is how the entry is written). Apply one change at a time. Write the coding, then verify that the car still starts and that the expected feature behaves as described.
  5. If something looks wrong, restore the backup you saved. Do not stack several untested changes in one session.

Menu labels inside OBDeleven vary by app version and vehicle, so this site keeps the steps general. Follow OBDeleven’s own screens for connection, security access, and writing coding. If an entry mentions SFD or a specific tool generation, treat that as a community note, not a guarantee for your car.

Safety

Always back up the original coding first. Change one bit or byte at a time and write down the before and after values. Risk labels on this site are community hints, not a safety certification. Long coding can affect lighting, comfort features, and driver assistance. If you do not understand a string, do not apply it. Long Coding Hub is not responsible for damage, failed inspections, or warranty issues that follow from using a published coding. Read the full disclaimer before you change anything.

Supported brands

The catalog covers Volkswagen Group vehicles that people commonly code with OBDeleven: Volkswagen, Audi, Skoda, SEAT, and Cupra. Open a model page to see modules and shared long coding for that car, for example Audi A4 B9, Volkswagen Passat B8, Skoda Octavia IV, SEAT Arona, or Cupra Formentor. Use the vehicle browser above for the full list.

FAQ

Is long coding with OBDeleven safe?

It can change how a module behaves, so it is never risk-free. Back up first, change one value at a time, and only apply strings you understand. Community risk labels are hints, not approval. You use every coding at your own risk — see the disclaimer.

Do I need a paid OBDeleven plan for long coding?

Access to manual long coding depends on OBDeleven’s own plans, app version, and the vehicle. This site does not sell or configure OBDeleven. Check OBDeleven’s documentation for what your account can write, and match any tool notes on an entry (for example OBDeleven or OBDeleven Next) to what you actually use.

What is the difference between long coding and adaptation?

Long coding is the module’s coding string: bytes and bits that turn features on or off. Adaptation channels are usually single parameters or thresholds. An entry on this site targets long coding unless it clearly says otherwise.

How is this library different from One-Click Apps?

One-Click Apps are guided changes inside OBDeleven. This library collects community-submitted coding strings you apply yourself, one vehicle and one module at a time. The site does not run apps or write to your car.