Overview
This quick-reference maps BMW/MINI/Rolls-Royce chassis codes to the correct E-Sys Target so you can connect, read CAFD, and code without guesswork. It’s designed for coders and workshops who switch between F-, G-/U-series, i-series, RR models and BMW Motorrad.
How to Use
Quick Mapping (most common pairs)
Tips & Pitfalls
Why It Helps
Choosing the correct target first saves connection time, prevents CAFD mismatches, and reduces coding retries—especially on mixed fleets that span F/G/U platforms.
Applies To
E-Sys on Windows with Full PSdZData. Works across BMW F-/G-/U-series, MINI F-series, Rolls-Royce, and BMW Motorrad where supported.
Compatibility (environment)
Guide applies to E-Sys running on Windows 7, Windows 8.1, Windows 10, and Windows 11.
Tested on Windows 10 LTSC (2019), also verified on recent Windows 11 builds.
Disclaimer
All information was compiled from publicly available sources and community documentation for educational purposes. The forum does not host or distribute proprietary files, any references are to materials available on third-party services. Always follow OEM procedures and local laws.
This quick-reference maps BMW/MINI/Rolls-Royce chassis codes to the correct E-Sys Target so you can connect, read CAFD, and code without guesswork. It’s designed for coders and workshops who switch between F-, G-/U-series, i-series, RR models and BMW Motorrad.
- In E-Sys, open Target Selector.
- Pick the target that matches your chassis family (see the mapping below).
- Make sure your PSdZData matches the vehicle’s I-Level.
- If connection fails or CAFD is missing: try the adjacent family, update PSdZData, and re-read FA/VO.
Quick Mapping (most common pairs)
- F001 → F01/F02/F03/F04; also RR04/RR05/RR06
- F010 → F10/F11/F12/F13/F06
- F020 → F20/F21/F22/F23/F30–F36; M: F80/F82/F83/F87/F88
- F025 → F15/F16/F25/F26; M: F85/F86
- F056 → MINI F-series: F54/F55/F56/F57/F60
- I001 / I020 → i-series (i3/i8 by generation)
- K001 / KE01 / KS01 → BMW Motorrad platforms
- RR21 → Newer Rolls-Royce models
- S15A → Early G-series set (e.g., G30/G31/G32 and related)
- S18A → Later G/U-series (e.g., G05/G07/G01/G02; many 2018+)
- S15C → Specific RR projects
- U006 → New FAAR/UKL-based U-series (U06/U10/U11/U12/U025/U028 etc.)
Tips & Pitfalls
- “No CAFD for SWE” → wrong target or outdated PSdZData; switch family and re-read ECU.
- VO/FA reads but coding blocks are empty → vehicle I-Level newer than data set; update PSdZData.
- Post-flash codings missing → write FA to VCM, then code default values per ECU.
- MINI, RR, Motorrad use distinct families; don’t force F020/F056 on non-matching platforms.
Why It Helps
Choosing the correct target first saves connection time, prevents CAFD mismatches, and reduces coding retries—especially on mixed fleets that span F/G/U platforms.
Applies To
E-Sys on Windows with Full PSdZData. Works across BMW F-/G-/U-series, MINI F-series, Rolls-Royce, and BMW Motorrad where supported.
Compatibility (environment)
Guide applies to E-Sys running on Windows 7, Windows 8.1, Windows 10, and Windows 11.
Tested on Windows 10 LTSC (2019), also verified on recent Windows 11 builds.
Disclaimer
All information was compiled from publicly available sources and community documentation for educational purposes. The forum does not host or distribute proprietary files, any references are to materials available on third-party services. Always follow OEM procedures and local laws.
