ECU TOOLS
Bench & diagnostic tooling
Tools / Identification

BMW E-Sys Target Selector Finder

Find the E-Sys target selector for a BMW from its chassis code, and pull the short VIN out of a full VIN. Runs in your browser — nothing is uploaded.

freeruns locallyread-only
[Tool]
client-side

About this tool

A target selector in E-Sys has two halves, and they come from two different places. The series group — F020, G011, I001 and so on — comes from the car's chassis. The I-Step suffix that follows it comes from the PSdZData you happen to have installed, not from the car. Most of the confusion around target selectors is really confusion about which half is which, so this tool answers the first and explains the second rather than pretending a lookup table can know what is on your disk.

Pick the chassis from the dropdown and you get the series group. The list covers 152 chassis codes across 15 groups, from F001 and F10 through the G-series and the K-series motorcycles, and it is grouped so you can see which codes share a target. Enter a full 17-character VIN and you also get the seven-character short VIN, which is the value E-Sys actually asks for when you connect — it is simply the last seven characters, and the tool highlights them in place so you can see that. Paste a target selector string you already have and it is split into its group and its I-Step.

The tool deliberately does not try to guess the chassis from the VIN. BMW does not encode it in a form that can be decoded without a model table, and a guessed chassis would produce a confidently wrong target selector. Pick the chassis; it is written on the car's data and you almost always know it.

Everything runs locally with no network requests. Coding a BMW is not risk-free: the wrong target selector loads the wrong CAF and SVT data, so confirm the series group against the vehicle, read the car's own I-Step rather than assuming it, and back up before writing anything.

BMWE-SysESystarget selectorI-StepPSdZDatacodingchassisshort VINF30G20

Questions

What actually goes wrong if I pick the wrong target selector?
E-Sys loads CAF and SVT data belonging to a different vehicle generation. Reads come back as nonsense or fail outright, and if you write on that basis you are writing data that was never meant for the module. It is the first thing to check when E-Sys behaves strangely on a car it should handle.
Which I-Step should I choose?
Match the series group to the chassis first, then take the newest I-Step your PSdZData offers for that group which is at or above the car's own I-Step. Read the car's I-Step rather than assuming it — no lookup can tell you what is installed on your machine.
Why will it not work out the chassis from my VIN?
Because it cannot do so reliably, and a wrong answer here is worse than no answer. BMW's VIN does not carry the chassis code in a decodable form without a model table. What the VIN does give you, reliably, is the short VIN — the last seven characters — which is what E-Sys prompts for.
Can I add groups my E-Sys has and this list does not?
Yes. Open the reference data panel and paste from your own E-Sys installation, one entry per line. It is parsed and stored only in your browser, is never uploaded, and is used alongside the built-in mapping rather than replacing it.
Why do some chassis codes show a question mark?
Four entries in the S18A group were obscured in the source table they were transcribed from, so the code itself may be misread. They are marked rather than quietly presented as solid, and selecting one shows a warning. Check those against E-Sys before relying on them.

Support this tool

These tools are free and stay free — there is no trial, no account and no cap on how many times you use them. If one of them saved you a job, you can put something back; it pays for the domain and the hosting.

Donate
Verify before you write. This tool reads a dump and reports what it finds. Always confirm the values against your programmer before writing anything to a module, and only work on vehicles you own or are authorised to service.