BimmerByte

BMW coding · E, F, G & U series · BimmerCode · E-Sys · Carly

Code your BMW
like a pro.

Tell us what you want to unlock — in plain English. Drop your VIN or chassis code and we'll give you the exact module, the exact parameter, the exact value, and ordered steps in the wording of the tool you actually have — BimmerCode, E-Sys, Carly, or ISTA.

No more cross-checking three forum threads from 2014 that don't match your CAFD version. Every answer comes with a confidence rating and flags the parameters where a wrong value means a rollback.

  • Chassis-aware. F30, G20, F32, G30 — answers differ, and we know how.
  • Tool-specific. Steps written in the exact wording of your coding tool.
  • Brick-safe. Backups and rollback notes called out before the risky bit.
Ask BimmerByte
1 query left · guest

What do you want to code today?

Mention your chassis (e.g. F30) and headunit if you know it — answers get sharper.

1 query left · guest · see pricing

Popular requests

tap one to pre-fill
Video in motion
NBT EVO · F & G series
Pre-fills chassis F30 →
Folding mirrors on lock
F30 · F32 · G20 · G30
Pre-fills chassis F30 →
Sport displays in iDrive
NBT EVO · ID7
Pre-fills chassis F30 →
DRL behavior
F & G series
Pre-fills chassis F30 →
Welcome / goodbye lights
F22 · F30 · G20
Pre-fills chassis F30 →
Disable legal disclaimer
NBT · NBT EVO · ID7
Pre-fills chassis F30 →
Comfort access tweaks
F & G series
Pre-fills chassis F30 →
Auto start/stop memory
F30 · G20 · G30
Pre-fills chassis F30 →
Digital speed in HUD
F & G series with HUD
Pre-fills chassis F30 →

How it works

I.

Describe what you want

Plain English. Drop your VIN or chassis code so the answer is tailored to your car, not a generic forum thread.

II.

Get exact instructions

Module, parameter, value, the right tool, ordered steps, and the warnings that matter.

III.

Code with confidence

Every answer carries a confidence rating and points out the bits that can brick a module.

What you get in every answer

  • Module + ECU
    FEM_BODY, KOMBI, HU_NBT, etc. — addressed by name, not by guesswork.
  • Exact parameter + value
    Old value, new value, units. No 'change the one that looks right'.
  • The right tool
    Written in BimmerCode / Carly / E-Sys wording — not generic.
  • Ordered steps
    From plug in cable to verify it worked, with no skipped middle.
  • Warnings + rollback
    What can brick. What to back up. How to revert.
  • Confidence rating
    Low / medium / high so you know when to double-check.
  • Chassis + headunit chips
    At a glance — does this apply to my car?
  • Follow-up thread
    Ask a clarifying question without restarting.

Works with the tool you already own

Pick the tools you actually have when you ask — we'll write the workflow in that tool's terms. Multiple tools? You'll get a separate workflow for each.

BimmerCode

Phone app. Great for everyday F & G coding via an OBD dongle. We write steps in BimmerCode's wording.

E-Sys

Laptop + ENET cable. Full FDL/VO coding, CAFD edits, NBT/EVO retrofits. We give you the module SWE, parameter, and value.

Carly

Phone app. Coding map differs from BimmerCode — we account for that and translate the parameter names.

ISTA+ / ISTA-D

BMW dealer-grade software. Useful for diagnostics and some coding; we include ECU SG codes when relevant.

Bimmer Tool

Service-mode utilities — registration, calibrations, adaptations. We separate these from coding so you know what's safe to do.

Better than two hours of forum trawling

The old way
  • · Twelve tabs of conflicting forum advice from 2014
  • · “Worked on my E60, dunno about yours”
  • · Parameter names that don't match your CAFD version
  • · Half a YouTube video, ad break, lost the timestamp
  • · Hours later, still scared to plug the cable in
BimmerByte
  • · One answer, scoped to your chassis + headunit
  • · Module, parameter, value — named exactly
  • · Tool-specific steps (your tool, not someone else's)
  • · Warnings flagged before the part that can brick
  • · Follow-up thread for the “wait, which address?” moment

Frequent questions

Will this brick my car?
Not if you back up your CAFD first and follow the steps. We flag the modules and parameters where a wrong value will need a rollback — and we tell you exactly what to back up before touching them.
Do I need a coding cable or just an OBD dongle?
Depends on the change. App-level tools (BimmerCode, Carly) work over an OBD dongle for most F & G coding. E-Sys jobs (CAFD edits, NBT retrofits, deep VO changes) need an ENET cable and a laptop. We tell you which one you need for your specific request.
Which chassis are supported?
F and G series are the sweet spot — that's where the answers are most reliable. E-series (E9x and earlier) coding is covered for common requests but the parameter space is narrower. I-series and U-series support is growing as new modules get documented.
Where does the answer come from?
A current LLM grounded on BMW module / CAFD references and community coding databases, with a confidence rating attached. Every step lists the exact module, parameter, value, and tool — not a paraphrased forum thread.
Can I ask a follow-up?
Yes. Every answer has a follow-up thread under it — clarify a step, ask about a specific address, or check whether a parameter changes between chassis. Each follow-up uses one query slot.

Your data, plainly

When you sign in with Google we receive your email address and basic profile name only — used to create your BimmerByte account and keep your saved queries tied to you. We don't ask for Drive, Gmail, calendar, contacts, or any other Google scope. Your coding questions and vehicle details are stored on Supabase and the question text is sent to Google's Gemini API to generate the answer. We don't sell your data, run ad trackers, or share it with anyone outside the services we need to run the product.

Full details: Privacy policy · Terms of service

Three free queries. No card needed.

Try it on the coding job you've been putting off. If it doesn't save you an hour, don't come back.

Start coding now →