E-Sys Launcher PRO — Secure BMW E-Sys Start-up & Full FDL Coding (3.24–3.30)

E-Sys Launcher Secure - BMW Automotive Coding Utility 2.8.1.155

Sign in to download for free
E-Sys Launcher PRO — Secure BMW E-Sys Start-up & Full FDL Coding (3.24–3.30)
E-Sys Launcher Secure - BMW Automotive Coding Utility 2.8.1.155
Sign in to download for free
If you see your VIN, your cable and network connection are working correctly. The "Connect" button is grayed out because you have not selected a Target (Chassis) in the top window yet.

The connection window is divided into two parts:

1. Top Box (Target Selector)
This list contains the database files (psdzdata) for different chassis.
  • You must scroll through this list and find your chassis code (e.g., F020 for F30/F32/F80, or F010 for F10/F11).
  • Click on the line that looks like this: F020_19_11_530_v_004_000 (The numbers will vary based on your data version).
  • IMPORTANT: Do NOT select the one ending in _DIRECT.

2. Bottom Box (Interface)
This is where you saw "Connection via VIN".
  • Select the radio button "Connection via VIN".
  • Your VIN should appear there (which you said you already see).

Once you click and highlight the Target in the top box AND select the VIN in the bottom box, the "Connect" button will turn clickable.

If the Top Box is empty:
This means your psdzdata is not installed or linked correctly.
  • Check if you have a folder named psdzdata inside C:\Data\ (or wherever you installed it).
  • If the folder is empty or missing, you need to download the "PSdZData Lite" package and extract it there.
The listed i provided is what was given in the top box. this was a mirror i downloaded then accidentally closed the page. I was doing a search to see where i got the mirror from but difficult to find it now.
 
The listed i provided is what was given in the top box. this was a mirror i downloaded then accident...

It sounds like your PSdZData (the database files required to code the car) is either missing, empty, or not linked correctly in the E-Sys settings.

The "Top Box" (Target) should list chassis codes like F010, F020, S15A, etc. If you are seeing generic text like "gateway connection" there, or if the list is empty/incorrect, E-Sys cannot find the definitions for your car.

Please check these two things:

1. Check the Folder Structure
Go to your C: drive in Windows Explorer.
Do you have a folder named C:\Data\psdzdata?
Open it. It should contain subfolders like mainseries, mapping, swe, etc.
  • If the folder is empty or missing, you need to download "PSdZData Lite" and extract it there.
  • If you have a folder like C:\Data\psdzdata\psdzdata\... (a double folder), move the contents up one level.

2. Check E-Sys Settings
If the files are on your drive, E-Sys might be looking in the wrong place.
  • Open E-Sys.
  • Go to Options (top menu) -> Settings.
  • Click on the Program tab.
  • Look at the Data Path (Directories - Data).
  • It should point to C:\Data.

If the path is correct and the files are there, close E-Sys and reopen it. The Top Box should now populate with the chassis codes (Targets). Once you select the correct Target (e.g., F020 for 3/4 series) and your VIN at the bottom, the Connect button will work.
 
It sounds like your PSdZData (the database files required to code the car) is either missing, empty, or not linked correctly in the E-Sys settings.

The "Top Box" (Target) should list chassis codes like F010, F020, S15A, etc. If you are seeing generic text like "gateway connection" there, or if the list is empty/incorrect, E-Sys cannot find the definitions for your car.

Please check these two things:

1. Check the Folder Structure
Go to your C: drive in Windows Explorer.
Do you have a folder named C:\Data\psdzdata?
Open it. It should contain subfolders like mainseries, mapping, swe, etc.
  • If the folder is empty or missing, you need to download "PSdZData Lite" and extract it there.
  • If you have a folder like C:\Data\psdzdata\psdzdata\... (a double folder), move the contents up one level.

2. Check E-Sys Settings
If the files are on your drive, E-Sys might be looking in the wrong place.
  • Open E-Sys.
  • Go to Options (top menu) -> Settings.
  • Click on the Program tab.
  • Look at the Data Path (Directories - Data).
  • It should point to C:\Data.

If the path is correct and the files are there, close E-Sys and reopen it. The Top Box should now populate with the chassis codes (Targets). Once you select the correct Target (e.g., F020 for 3/4 series) and your VIN at the bottom, the Connect button will work.
the psdzdata folder is empty
 
the psdzdata file is empty

That is the problem. Without those files, E-Sys is just an empty shell and cannot identify your car.

You need to download PSdZData Lite.

Since you are only doing coding (VO Coding to remove 524), the Lite version is all you need. Do not download the "Full" version (which is huge and used for flashing ECU firmware).

Steps to fix this:

1. Download: Search this forum thread or the "Coding" section for the latest PSdZData Lite (usually v4.xx.xx).
2. Extract: Once downloaded, extract the archive.
3. Install: Copy the contents into your empty folder.

Crucial Folder Structure:
Make sure you do not create a double folder layer when extracting. The structure must look exactly like this:

C:\Data\psdzdata\mainseries
C:\Data\psdzdata\mapping
C:\Data\psdzdata\swe
...and so on.

Incorrect: C:\Data\psdzdata\psdzdata\mainseries (This will not work).

Once you fill that folder, restart E-Sys. The "Target" list in the top box will now populate with chassis codes, and you will be able to connect.
 
That is the problem. Without those files, E-Sys is just an empty shell and cannot identify your car.

You need to download PSdZData Lite.

Since you are only doing coding (VO Coding to remove 524), the Lite version is all you need. Do not download the "Full" version (which is huge and used for flashing ECU firmware).

Steps to fix this:

1. Download: Search this forum thread or the "Coding" section for the latest PSdZData Lite (usually v4.xx.xx).
2. Extract: Once downloaded, extract the archive.
3. Install: Copy the contents into your empty folder.

Crucial Folder Structure:
Make sure you do not create a double folder layer when extracting. The structure must look exactly like this:

C:\Data\psdzdata\mainseries
C:\Data\psdzdata\mapping
C:\Data\psdzdata\swe
...and so on.

Incorrect: C:\Data\psdzdata\psdzdata\mainseries (This will not work).

Once you fill that folder, restart E-Sys. The "Target" list in the top box will now populate with chassis codes, and you will be able to connect.
this was a 84MB file
 
this was a 84MB file

That file is too small to be the data files. 84MB is likely just the E-Sys program installer or the Launcher itself.

PSdZData Lite (which contains the ECU definitions needed to populate that list) is typically around 1.5 GB to 2.5 GB in size (compressed).

You need to find the link for the data pack specifically. It is almost always a separate download from the program itself.

Once you find and download the correct ~2GB file:
  • Delete whatever is currently in your C:\Data\psdzdata folder.
  • Extract the new large archive into that folder.
  • Restart E-Sys.

Without those large data files, E-Sys cannot function.
 
That file is too small to be the data files. 84MB is likely just the E-Sys program installer or the Launcher itself.

PSdZData Lite (which contains the ECU definitions needed to populate that list) is typically around 1.5 GB to 2.5 GB in size (compressed).

You need to find the link for the data pack specifically. It is almost always a separate download from the program itself.

Once you find and download the correct ~2GB file:
  • Delete whatever is currently in your C:\Data\psdzdata folder.
  • Extract the new large archive into that folder.
  • Restart E-Sys.

Without those large data files, E-Sys cannot function.
I just remembered. I have the psdzdata 4.57..30 lite rar file. Is that what I need to work with this?
 
I just remembered. I have the psdzdata 4.57..30 lite rar file. Is that what I need to work with this...

Yes, that is exactly the file you need.

How to install it:

1. Open that RAR file.
2. Extract the contents directly into
Code:
C:\Data\psdzdata
3. Important: Ensure you do not create a double folder structure.
* Correct:
Code:
C:\Data\psdzdata\mainseries
* Incorrect:
Code:
C:\Data\psdzdata\psdzdata\mainseries

Once the extraction is complete:
1. Restart E-Sys.
2. Click the Connect button.
3. The "Target" list (top box) will now be populated with chassis codes.
4. Select your chassis (e.g., F020) in the top box, select "Connection via VIN" in the bottom box, and the Connect button will become clickable.
 
The "Connect" button stays grayed out until you select a Target from the list at the top of the connection window.

Here is the correct procedure:

  1. Target Selector (Top List):You must click on your chassis code here.
    • If you have an F30, F32, F80, etc., select F020.
    • If you have an F10, F11, select F010.
    • IMPORTANT: Do NOT select the option that ends with _DIRECT. Select the clean one (e.g.,
      Code:
      F020_18_03_520_v_004_000
      ).
  2. Interface (Bottom Section): Select Connection via VIN.
  3. Since you can already see your VIN, select it.

Once you highlight the correct Target in the top list and select "Connection via VIN" at the bottom, the Connect button will become clickable.
targetselector: project=f010_25_07_540
and
targetselector: project=f010_25_11_550
 
targetselector: project=f010_25_07_540
and
targetselector: project=f010_25_11_550

Great, that means your PSdZData is now correctly installed and E-Sys is reading it.

Those entries represent the chassis definitions for the 5-Series (F10/F11/F07) and 6-Series (F06/F12/F13).

Here is what to do:

1. Select the Target:
In that top box, click on the F010 line with the highest numbers (latest date).
* Example: If you have F010_25_11_550 and F010_25_07_540, select F0102511_550.
* Important: Do NOT select the line that ends with _DIRECT.

2. Select the Interface:
In the bottom box, select the radio button "Connection via VIN".
(Your car's VIN should be listed there).

3. Connect:
Click the Connect button.

Once connected, you can proceed to the "Expert Mode" -> "Coding" tab to read your FA (Vehicle Order) and SVT (ECU list).
 
That is good news. Removing option code 524 (Adaptive Headlights) from your Vehicle Order is purely VO Coding.

You do not need the Launcher or a Token for this. You do not need to wait for the download link to be fixed.

You can simply run E-Sys.exe directly (usually located in C:\EC-Apps\ESG\E-Sys\E-Sys.exe) and proceed.

Here is the quick procedure since you don't need the Launcher:
  1. Connect to the car.
  2. Go to Expert Mode > Coding.
  3. Read FA -> Save FA -> Edit FA.
  4. In the FA Editor, expand the tree to SALAPA-Element.
  5. Delete "524," from the list.
  6. Right-click on FA at the top and select Calculate FP (to ensure no errors).
  7. Save the FA and go back to the Coding tab.
  8. Load your modified FA file.
  9. Right-click on the FA and select Activate.
  10. Select the ECUs that control the lights (usually FEMBODY or BDCBODY, and potentially FLE, LHM, or TMS depending on your chassis).
  11. Click Code (Green button). Do NOT click "Code Default".

This will reset those modules to factory settings based on the new VO (without option 524), effectively disabling the adaptive function.
I right-clicked and a list of folders with numbers appeared in the vehicle profile. I can assume that its all good or do I need to check the folders?
 
I right-clicked and a list of folders with numbers appeared in the vehicle profile. I can assume tha...

It sounds like you have successfully read the FA (Vehicle Order) and expanded the tree structure. Seeing those folders means the data was read correctly from the car.

However, you cannot change anything in that main "Coding" view. You are currently in "View" mode. To remove an option code (like 524), you must switch to the FA-Editor.

Here is the exact process to modify the list:

1. Save the FA:
In the "Vehicle Order" box (top left), click the Save button. Save the file as FA_Original.xml somewhere safe.

2. Open the Editor:
With the FA file still highlighted, click the Edit button. This will switch your screen to the "FA-Editor" tab.

3. Find the Option Codes:
In the FA-Editor, expand the folder tree on the left:
  • Right-click on FA -> Expand
  • Expand FZAuftrag
  • Expand Type
  • Click on SALAPA-Element

4. Edit the List:
Once you click "SALAPA-Element", look at the bottom window (labeled "SALAPA-Element"). You will see a long list of codes separated by commas (e.g., 1CA, 230, 423, 524, ...).
* Find the code you want to remove (e.g., 524).
* Delete it and the comma following it.
* Important: Do not leave double commas or trailing spaces.

5. Apply Changes:
* Right-click on FA (at the very top of the tree) and select Calculate FP.
* If there are no errors, click the Save icon (floppy disk) in the top toolbar.
* Click the Back button (green arrow) to return to the Expert Mode -> Coding tab.

Now you are ready to load this modified FA and code the car. Let me know when you are back on the main Coding screen.
 
It sounds like you have successfully read the FA (Vehicle Order) and expanded the tree structure. Seeing those folders means the data was read correctly from the car.

However, you cannot change anything in that main "Coding" view. You are currently in "View" mode. To remove an option code (like 524), you must switch to the FA-Editor.

Here is the exact process to modify the list:

1. Save the FA:
In the "Vehicle Order" box (top left), click the Save button. Save the file as FA_Original.xml somewhere safe.

2. Open the Editor:
With the FA file still highlighted, click the Edit button. This will switch your screen to the "FA-Editor" tab.

3. Find the Option Codes:
In the FA-Editor, expand the folder tree on the left:

  • Right-click on FA -> Expand
  • Expand FZAuftrag
  • Expand Type
  • Click on SALAPA-Element

4. Edit the List:
Once you click "SALAPA-Element", look at the bottom window (labeled "SALAPA-Element"). You will see a long list of codes separated by commas (e.g., 1CA, 230, 423, 524, ...).
* Find the code you want to remove (e.g., 524).
* Delete it and the comma following it.
* Important: Do not leave double commas or trailing spaces.

5. Apply Changes:
* Right-click on FA (at the very top of the tree) and select Calculate FP.
* If there are no errors, click the Save icon (floppy disk) in the top toolbar.
* Click the Back button (green arrow) to return to the Expert Mode -> Coding tab.

Now you are ready to load this modified FA and code the car. Let me know when you are back on the main Coding screen.
I actually did that already. I saved, then clicked edit as instructed
 
I actually did that already. I saved, then clicked edit as instructed

Perfect. Now that you are in the FA-Editor, follow these steps to remove the code and apply the changes to the car:

1. Edit the SALAPA Elements
  • Expand the folder tree on the left: FA -> FZAuftrag -> Type.
  • Click on SALAPA-Element.
  • Look at the bottom window. You will see the list of codes (e.g., 1CA, 230, 524, etc.).
  • Find 524 and delete it.
  • Make sure you also delete the comma that was attached to it, but do not delete the commas for the other numbers.

2. Validate the FA
  • Right-click on FA (at the very top of the tree).
  • Select Calculate FP.
  • A window should pop up showing the vehicle profile. If there are no errors (red text), it is valid.

3. Save and Return
  • Click the Save icon (floppy disk) in the top toolbar.
  • Click the Back button (green arrow) to return to the "Expert Mode -> Coding" tab.
  • A popup might ask if you want to reload the FA. Click Yes.

4. Code the ECU (VO Coding)
Now you need to reset the lighting module so it realizes 524 is gone.
  • In the "Vehicle Order" box (top left), right-click on FA and select Activate FA. (The FA folder should turn green).
  • In the "SVT Actual" box (right side), click Read SVT (VCM).
  • Scroll down the ECU list and find FRM (Footwell Module).
  • Right-click on the FRM folder itself (not the underlying CAFD files).
  • Select Code.

Warning: Do NOT select "Code Default Values". Just select "Code".

Once the process finishes and says "0 errors", the FRM has been reset to factory settings based on your new FA (without Adaptive Lights), and the error should be gone.
 
Perfect. Now that you are in the FA-Editor, follow these steps to remove the code and apply the changes to the car:

1. Edit the SALAPA Elements
  • Expand the folder tree on the left: FA -> FZAuftrag -> Type.
  • Click on SALAPA-Element.
  • Look at the bottom window. You will see the list of codes (e.g., 1CA, 230, 524, etc.).
  • Find 524 and delete it.
  • Make sure you also delete the comma that was attached to it, but do not delete the commas for the other numbers.

2. Validate the FA
  • Right-click on FA (at the very top of the tree).
  • Select Calculate FP.
  • A window should pop up showing the vehicle profile. If there are no errors (red text), it is valid.

3. Save and Return
  • Click the Save icon (floppy disk) in the top toolbar.
  • Click the Back button (green arrow) to return to the "Expert Mode -> Coding" tab.
  • A popup might ask if you want to reload the FA. Click Yes.

4. Code the ECU (VO Coding)
Now you need to reset the lighting module so it realizes 524 is gone.
  • In the "Vehicle Order" box (top left), right-click on FA and select Activate FA. (The FA folder should turn green).
  • In the "SVT Actual" box (right side), click Read SVT (VCM).
  • Scroll down the ECU list and find FRM (Footwell Module).
  • Right-click on the FRM folder itself (not the underlying CAFD files).
  • Select Code.

Warning: Do NOT select "Code Default Values". Just select "Code".

Once the process finishes and says "0 errors", the FRM has been reset to factory settings based on your new FA (without Adaptive Lights), and the error should be gone.
0 errors. I hope my ac and heat works now too. lol
 
0 errors. I hope my ac and heat works now too. lol

That is great news! "0 errors" means the coding went through perfectly.

Regarding the AC and heat:
Technically, the FRM (Footwell Module) you just coded controls lighting, windows, and mirrors. The climate control is handled by a different module called IHKA.

However, if the bad headlight module was flooding the communication bus with errors, it is possible it was interfering with other systems. Hopefully, calming down the FRM helps everything else stabilize.

Next Steps:
1. Disconnect: Click the "Disconnect" button in the top toolbar of E-Sys.
2. Test: Turn off the car, lock it, wait about 15 seconds, and unlock it. Start the engine.
3. Verify: Check if the "Adaptive Headlight Malfunction" warning on the dashboard is gone.

If the warning is gone, you are done!

(Note: You have currently coded the car to ignore the adaptive lights, but you haven't written this change permanently to the car's "Master" memory (VCM). This is actually safer. It means the car works now, but if a dealer ever updates the software, the error might come back, and you'd just have to do this quick process again.)
 
That is great news! "0 errors" means the coding went through perfectly.

Regarding the AC and heat:
Technically, the FRM (Footwell Module) you just coded controls lighting, windows, and mirrors. The climate control is handled by a different module called IHKA.

However, if the bad headlight module was flooding the communication bus with errors, it is possible it was interfering with other systems. Hopefully, calming down the FRM helps everything else stabilize.

Next Steps:
1. Disconnect: Click the "Disconnect" button in the top toolbar of E-Sys.
2. Test: Turn off the car, lock it, wait about 15 seconds, and unlock it. Start the engine.
3. Verify: Check if the "Adaptive Headlight Malfunction" warning on the dashboard is gone.

If the warning is gone, you are done!

(Note: You have currently coded the car to ignore the adaptive lights, but you haven't written this change permanently to the car's "Master" memory (VCM). This is actually safer. It means the car works now, but if a dealer ever updates the software, the error might come back, and you'd just have to do this quick process again.)
The AC still isn't working
 
The AC still isn't working

Sorry to hear that. As I mentioned earlier, the FRM only handles lights and windows, so fixing the headlights doesn't automatically fix the climate control.

However, since you are already connected and have the FA loaded, you can try "resetting" the AC module (IHKA) to factory settings just like you did with the lights. If the AC issue is caused by bad coding or a glitch, this will fix it.

Try this:

  1. Ensure your FA is still Active (Green folder in the top left).
  2. Look at the SVT list (the ECU list on the right).
  3. Scroll down and find IHKA (Integrated Automatic Heating/Air Conditioning).
  4. Right-click on the IHKA folder.
  5. Select Code.

If it finishes with "0 errors" and the AC still doesn't work, then the problem is not coding-related. It is likely a mechanical issue (low refrigerant, bad compressor, blown fuse) or a sensor fault. You would need diagnostic software like ISTA+ to read the specific error codes for the AC system.
 
Sorry to hear that. As I mentioned earlier, the FRM only handles lights and windows, so fixing the headlights doesn't automatically fix the climate control.

However, since you are already connected and have the FA loaded, you can try "resetting" the AC module (IHKA) to factory settings just like you did with the lights. If the AC issue is caused by bad coding or a glitch, this will fix it.

Try this:

  1. Ensure your FA is still Active (Green folder in the top left).
  2. Look at the SVT list (the ECU list on the right).
  3. Scroll down and find IHKA (Integrated Automatic Heating/Air Conditioning).
  4. Right-click on the IHKA folder.
  5. Select Code.

If it finishes with "0 errors" and the AC still doesn't work, then the problem is not coding-related. It is likely a mechanical issue (low refrigerant, bad compressor, blown fuse) or a sensor fault. You would need diagnostic software like ISTA+ to read the specific error codes for the AC system.
Do you know where i can find ISTA? lol. jk. I'll check
 
Do you know where i can find ISTA? lol. jk. I'll check

ISTA+ is definitely the tool you need for that. E-Sys is for coding (changing options), while ISTA is for diagnosis (finding out what is broken).

Since you already have the ENET cable working:
  • Check the sticky threads in the Diagnostic Software section for the download links.
  • When you install it, set the interface to ENET in the VCI Config.

It will scan the IHKA module and tell you exactly why the AC isn't starting (e.g., low pressure, bad sensor, etc.). Good luck!
 
Back