Help with coding a BMW M2 2024 G87 Kombi8

• You'll need PSdZData 4.46.4x or newer to cover the 23-07-540 integration level and include CAFD 00006D4E011001002 for the Kombi8 (HU-BHIGH) on the G87.
• Check your current PSdZData version in E-Sys: Expert Mode → PSdZ → Show PSdZ Properties.

1. Update your PSdZData — Look for a full PSdZData package in the 4.46.4x or 4.47.x range. Check the Resources section of this forum or the usual BMW coding community sources.
2. Extract from ISTA+ — If you have a current ISTA+ installation (4.46+), the CAFD files exist inside the ISTA data directory. You can locate the specific CAFD and manually place it into your E-Sys PSdZData structure under psdzdata\swe\cafd\.
3. Read from the car — If you only need to tweak specific FDL parameters, you can read the current CAFD directly from the module via E-Sys (SVT → Read ECU → KOMBI) and use that as a basis for FDL coding. This won't help for a full VO-code, but works for individual changes.

1. Find the specific CAFD — You need a PSdZData version that actually contains CAFD00006D4E-011001_002.caf.lzma. Try PSdZData in the 4.46.4x–4.50.x range. Earlier builds around that iSTEP (S18A-23-07-540) are more likely to still include that specific revision.
   
2. Inject it manually — Once you find the file, copy it into your current PSdZData structure:
   
   Code:

   psdzdata\swe\cafd\CAFD_00006D4E-011_001_002.caf.lzma

   E-Sys should then be able to resolve it during VO-coding or CAFD injection.
   
3. Alternative: extract from ISTA+ — If you or someone you know has an ISTA+ installation from around that iSTEP period, the CAFD will be in the ISTA data folders. Search for 00006D4E in the SWE directory.
   
4. Check the actual Kombi8 SW version — Before injecting, confirm the software version on the module by reading the SVT. If the Kombi8 firmware was updated at a dealer, the expected CAFD revision may have changed. If the SW was updated but the CAFD reference still points to _011_001_002, you may need to flash the matching SW+CAFD pair together via TAL.

• BTLD000082F8015005040
• CAFDFFFFFFFF255255255 ← corrupted/wiped
• FLSL000084EA015005040
• HWEL0000A929004000005
• SWFL000084EC015005040
• SWFL000084EE015005040

1. Find the correct CAFD for SW 015005040 — The matching CAFD is likely CAFD00006D4E015005040 (or a revision within the 015.xxx range), not the 011001002 version. Where did you get the 011001002 reference? Was it from a backup, or from the iSTEP/TAL calculation?
2. Run a TAL calculation in E-Sys — Go to TAL Calculation → Read FA (VO) → Calculate TAL. E-Sys should tell you exactly which CAFD it wants to write for DKOMBI8 based on your current FA and SVT. That will give you the correct CAFD filename to search for.
3. Check ISTA+ if available — An ISTA+ installation with current data will have the full SWE set. Search for files starting with 00006D4E in the SWE/CAFD directories.

• I-Step (shipment): S18A-23-07-540
• I-Step (target): S18A-25-07-562
• Error C325 / KIS [1966]: PSdZ can't access the KIS data for target iSTEP S18A-25-07-562

1. Manually type S18A-23-07-540 in the I-Step (target) field
2. Hit Calculate again
3. Check if the TAL now shows a cdDeploy action for DKOMBI8 with a specific CAFD filename

1. Close E-Sys
2. Open C:\Data\SVT\svt m2.xml in Notepad++
3. Search for the iSTEP/integration level value and change it to match your original shipment level (S18A-23-07-540)
4. Save, reopen E-Sys, Load the edited SVT, and try Calculate again

1. Go to Expert Mode → Coding
2. Read the FA (VO) from the car
3. Select DKOMBI8
4. Try Activate FA → Calculate CAF for VO — this may generate and write a new CAFD based on your FA without needing a TAL

psdzdata\swe\cafd\CAFD_00006D4E-011_001_002.caf.lzma

• ISTA+ installation — If you have ISTA+ 4.46 or newer, search the ISTA data directories for 00006D4E. The file will be in the SWE storage.
• Older PSdZData package — Try PSdZData in the 4.46.4x–4.50.x range. Those versions are more likely to still include this CAFD revision since your 4.59.11 apparently dropped it.
• Another G87 owner — Anyone with the same car and a working Kombi8 at the same SW level could export the CAFD via E-Sys (Read Coding Data).

Gemini said:

The PSdZData containing iSTEP S18A-23-07-540 is fairly recent, so it's not always easy to find in public repositories.

A few pointers:

• You'll need PSdZData 4.46.4x or newer to cover the 23-07-540 integration level and include CAFD 00006D4E011001002 for the Kombi8 (HU-BHIGH) on the G87.
• Check your current PSdZData version in E-Sys: Expert Mode → PSdZ → Show PSdZ Properties.

Some options:

1. Update your PSdZData — Look for a full PSdZData package in the 4.46.4x or 4.47.x range. Check the Resources section of this forum or the usual BMW coding community sources.
2. Extract from ISTA+ — If you have a current ISTA+ installation (4.46+), the CAFD files exist inside the ISTA data directory. You can locate the specific CAFD and manually place it into your E-Sys PSdZData structure under psdzdata\swe\cafd\.
3. Read from the car — If you only need to tweak specific FDL parameters, you can read the current CAFD directly from the module via E-Sys (SVT → Read ECU → KOMBI) and use that as a basis for FDL coding. This won't help for a full VO-code, but works for individual changes.

What version of PSdZData and E-Sys are you currently running? And what specifically are you trying to code on the Kombi8 — individual features, or a full VO-code (e.g., after a module swap)?

Click to expand...