BMW Forum - BimmerFest BMW Forums banner

Coding: (No Request) Latest Software Links

5 reading
1.3M views 6.2K replies 2.1K participants last post by  shawnsheridan  
#1 · (Edited)
What is Included:

  1. Software Overview and Requirements
  2. Latest Software Links & Installation Instructions
NOTE1: URL Links are in BLUE and pictures are links to larger images.

NOTE2: Click here for Getting Started Guides, Tips, & Cheat Sheets

1. Software Overview and Requirements:

This guide serves Fxx, Ixx, and Gxx-series vehicles. For E-series, different software and cable are used. Complete Software & Interface Overview.

Supported Chassis Code Overview
Image


Prerequisites:
  • Windows 7+ Computer.
  • E-Sys = Main Coding Software
  • PSdZData Lite(~2.5 GB) = ECU Data Files. Works for VO & FDL Coding.
  • Bimmer Utility = Provides License (ie Activation), FDL-Coding mapping, Cheat Codes (Section 7), & other optimization.
  • Connection Interface = ENET Cable (OBDII to RJ45 Ethernet) or ICOM. For computers without an ethernet port, you can use USB-to-ethernet adapters


2. Software Installation:

NOTE: Links never change. The latest versions are usually found below.
  • Add a comment to the thread if links down or you need newer versions
E-Sys - Install Instructions - v.15.pdf (Guide courtesy of member Shawnsheridan)

Bimmer Utility - Mapping 4.35.42 - Only and recommended solution
  • Auto-updated and supports the latest mapping for the most accurate coding experience
    • Purchase directly from the developer's website.
  • E-sys 3.39.1 - Used with Bimmer Utility or alone for Programming and VO coding.

Latest PSdZData_Lite (~2.5 GB) WORKS FOR ALL FDL CODING & VO CODING
  • Use this guide to determine your I-Step.
  • You only need one lite version for coding that is equal to or greater than your I-Step.
    • NOTE: If you get a "Not Found [C012]" error when "Read Coding Data," it is time to update.
  • Do NOT merge. DELETE old PSdZData folder & REPLACE w/ new PSdZData folder.


By Resource:
  1. NCD / CAFD: Read *.ncd files offline and easily search for a function, viewing current settings as well as other options
  2. NCD Compare: Load *.ncd files using Folder icons or drag & drop and then the far right button initiates compare. Popup showing Left vs right values which you can highlight and copy if you choose. It also highlights *.ncd trees differences in red & you can scroll up and down.
  3. Decrypt CAFD: not just for CFDs. It also works for other Psdzdata files (eg FAFP).
  4. FA / FP: viewer; tool includes mapping (eg 430 Inter Exter mirror anti dazzle). You can search loaded FA or entire FAFP (ie available options). FP viewer allows you to view options by Vehicle Profile (FP) without loading FA (Vehicle Order).
  5. FA Compare: like #2, but comparing fas.
  6. FA-CAFD: You load individual ECUs *.ncd and can see how FA additions will affect (ie "what-if).
  7. SVT-CAFD: You load the entire saved SVT file and see how FA changes will affect (ie "what-if).
 
#1,176 ·
OP #1 says: Certain E-sys installation require a minimum Psdzdata:

Image


i.e. E-sys 3.27.1 needs minimum PSdZdata 5.01.02

but Latest PSdZData_Lite link is 4.20.20.

So, I think I need the latest PSdZData lite or/and full link from Shaw please.

Thank you!
Those 2 versions are not comparable. 4.20.20, is actually the latest psdzdata, but it requires E-Sys 3.3x if I recall.

I know 4.16.x psdz data works with 3.27.1, cant remember where it changes, others would know.

/Weebyx
 
#1,178 ·
Thank weebyx and Almaretto!

So, in the 1st post of Almaretto, section 2. Software Installation, I can download from the links of E-Sys 3.27.1 - Preferred version, and Latest PSdZData_Lite, they should work together. If I need latest/compatible Latest PSdZData_full I can request the link/download from Shawn in another thread. Is that right?

Thank you, again!
 
#1,179 ·
Thank weebyx and Almaretto!

So, in the 1st post of Almaretto, section 2. Software Installation, I can download from the links of E-Sys 3.27.1 - Preferred version, and Latest PSdZData_Lite, they should work together. If I need latest/compatible Latest PSdZData_full I can request the link/download from Shawn in another thread. Is that right?

Thank you, again!
Yes.
 
#1,184 ·
Good evening,

I have a F01 760i ('09) with i-step F001-19-03-530

Can I use Esys 3.27? And do you have a link to the right PSdZData full for me?

Thanks in advance!
You can use E-Sys 3.27.1 for Coding.

Full is needed only if flashing. Are you going to actually flash ECU? If so, Full weighs in as a 45 part archive totaling 177 Gb in Compressed form.
 
#1,185 ·
#1,190 ·
After my dealer updated the software in my car in response to a recall and I have updated to the latest PSdZData, I now face a different problem in E-Sys: some FDLs are unmapped (e.g., 3020_2_2_32: aktiv [01]) and some are mapped to clearly nonsensical things (e.g., one FDL in DME is mapped to LmmIdx06_Priority: passive [00]). Is it safe to code with "partial" mappings as long as the FDLs that I want to code are mapped correctly? For example, TCM_MSA_MEMORY is still mapped to branch 3020, byte 19, bit 2 (start=19, end=19, mask=00000010b). I think it should not be a problem to code in this situation but I wanted to confirm with the resident experts here before getting ahead of myself.

Second question: can users update Esys mappings or only TokenMaster can do it? I am happy to spend the time helping figure out the updated mappings, but it's not clear to me how to go about it.
 
#1,191 ·
It is common to have a CAFD with partial mapping. It is fine to code the ones that are mapped.

Only way to get updated mappings is newer versions of Launcher or E-SysX, and that is assuming Developers have added updated the mapping in newer builds.
 
#1,192 ·
Thanks, Shawn. When do you sleep? You seem to be monitoring the forum 24/7.

Do you know if anyone discussed with the developers whether they would be amenable to opening up the mappings to others? Or at least allow others to submit corrections to mappings? It seems like the current system puts a lot of burden on them to keep up to speed with all the changes that BMW makes to all the CAFD files.
 
#1,193 ·
I sleep 3 hours per night, whether I need it or not.

If you have mapping updates / corrections, just email developers. They will incorporate.
 
#1,200 ·
Hi I recently went from a 2012 f10 to a 2016 and went to use my old esys 3.26.1 that i had on my laptop. I am able to connect fine but now it is asking for a token when i go to code. Also are there any newer files I will need? it looks like i installed this on the laptop 3/25/15 and it was juts collecting dust since coding before.

It did give some other errors so assume i may need to update some stuff
 
#1,201 ·
Hi I recently went from a 2012 f10 to a 2016 and went to use my old esys 3.26.1 that i had on my laptop. I am able to connect fine but now it is asking for a token when i go to code. Also are there any newer files I will need? it looks like i installed this on the laptop 3/25/15 and it was juts collecting dust since coding before.

It did give some other errors so assume i may need to update some stuff
You need to uninstall / delete all that and start over with the latest everything. PM sent.
 
#1,206 ·
I'm really not having any luck getting this to work. I've got the following setup:

* Windows 8.1 Pro x64
* Esys 3.27.1
* Esys Launcher Premium 2.8.2.155

I run Esys Launcher which asks me for a PIN and then says a token was created. I then see the main launcher dialog and choose F13 for the series and click Launch Now which then asks me to enter a PIN for another EST token. nce I click Generate Token, it then says the token was created and again asks me to enter a PIN for a new token and this repeats itself.

I am thinking that maybe I have a version mismatch somewhere?
 
#1,207 ·
#1,208 ·
Shawn.. we retroffited a Tow hitch yesterday and wanted to code it now. I did not use Esys nor the Launcher Pro since months... Now tried to start it and it states only "Verification failed" I tried also newer versions of the Launcher without success.
Is there an issue on Tokenmasters-Server, do you know?

Is it possible to use the Launcher Pro 2.8.2 on Parallels? I knew the Premium is not running on Parallels.

Thank you
 
#1,210 ·
Shawn.. we retroffited a Tow hitch yesterday and wanted to code it now. I did not use Esys nor the Launcher Pro since months... Now tried to start it and it states only "Verification failed" I tried also newer versions of the Launcher without success.
Is there an issue on Tokenmasters-Server, do you know?

Is it possible to use the Launcher Pro 2.8.2 on Parallels? I knew the Premium is not running on Parallels.

Thank you
Sorry, I have no idea. I have Launcher PRO 3.x with Static Activation activated long time ago, so I have no idea on current Server issue. Also, I do not use MAC, so I have no idea on Mac VM use.
 
#1,209 ·
Shawn.. we retroffited a Tow hitch yesterday and wanted to code it now. I did not use Esys nor the Launcher Pro since months... Now tried to start it and it states only "Verification failed" I tried also newer versions of the Launcher without success.
Is there an issue on Tokenmasters-Server, do you know?

Is it possible to use the Launcher Pro 2.8.2 on Parallels? I knew the Premium is not running on Parallels.

Thank you
 
#1,214 · (Edited)
Unclear FDL Coding under 3.33.4

Hello Shawn,

I got the new Launcher pro 3.6 from Tokenmaster.

I used this with Esys 3.33.4, but the Coding section shows different to V. 3.31.0.

There is no possibility to jump to the FDL Editor section after reading out the Unit. Also the FDL Coding Button is named NCD Codieren now....

Do you know the difference between this VersionS.

Thanks
 
#1,216 ·
Hello Shawn,

I got the new Launcher pro 3.6 from Tokenmaster.

I used this with Esys 3.33.4, but the Coding section shows different to V. 3.31.0.

There is no possibility to jump to the FDL Editor section after reading out the Unit. Also the FDL Coding Button is named NCD Codieren now....

Do you know the difference between this VersionS.

Thanks
Yes, there is. Right Click on CAFD and select SvtCompareView.edit.fdl.name.
 
#1,228 ·
Two Questions

Firstly, thanks to shawnsheridan and Almaretto (and others) for their work and support in this area.

First question: Is PSdZ different than PSdZData for our purposes? Post #1 shows minimum versions for PSdZ for various versions of Esys -- but the PSdZ versions listed are all higher than the latest version of PSdZData being distributed at the moment. For example for Esys 3.27.1, the minimum PSdZ version listed 5.01.02. I pulled down PSdZData Full v4.19.4 less than two weeks ago. If these are two different things, what does one do with this minimum PSdZ version information?

Second question, maybe related:

In Esys 3.27.1, I'm able to both VO and FDL code without problems. But in Coding (or TAL-Calculating) under "KIS/SVT Target", the Calculate button is always grayed out and I-Steps are always "not available" as soon as I activate my FA. Googling this, the advice is usually to use 3.27.1...the version I'm using. BUT, if I use 3.33.4, the above works as expected. (I understand you don't need to Calculate for coding, though I wonder why BMW put it on the coding page then... :confused:) Perhaps relevant, I have BDC_Body so no VCM if I understand correctly.

In post #1 there's a note under Esys 3.33.4 that says "PSdZData > v.4.17.20: Flashing ECU's & injecting CAFD". That implies I won't be able to flash with 3.27.1, and calculating TAL is a step toward flashing -- so is that what I'm running into? Should everyone use 3.33.4 for anything related to flashing since the only PSdZData versions available now (to newbies anyway) are >4.17.20? If so I'm a little confused by the "Preferred version (All functions work)" note for 3.27.1 in post #1.

Thank you!
 
#1,229 ·
Firstly, thanks to shawnsheridan and Almaretto (and others) for their work and support in this area.

First question: Is PSdZ different than PSdZData for our purposes? Post #1 shows minimum versions for PSdZ for various versions of Esys -- but the PSdZ versions listed are all higher than the latest version of PSdZData being distributed at the moment. For example for Esys 3.27.1, the minimum PSdZ version listed 5.01.02. I pulled down PSdZData Full v4.19.4 less than two weeks ago. If these are two different things, what does one do with this minimum PSdZ version information?

Second question, maybe related:

In Esys 3.27.1, I'm able to both VO and FDL code without problems. But in Coding (or TAL-Calculating) under "KIS/SVT Target", the Calculate button is always grayed out and I-Steps are always "not available" as soon as I activate my FA. Googling this, the advice is usually to use 3.27.1...the version I'm using. BUT, if I use 3.33.4, the above works as expected. (I understand you don't need to Calculate for coding, though I wonder why BMW put it on the coding page then... :confused:) Perhaps relevant, I have BDC_Body so no VCM if I understand correctly.

In post #1 there's a note under Esys 3.33.4 that says "PSdZData > v.4.17.20: Flashing ECU's & injecting CAFD". That implies I won't be able to flash with 3.27.1, and calculating TAL is a step toward flashing -- so is that what I'm running into? Should everyone use 3.33.4 for anything related to flashing since the only PSdZData versions available now (to newbies anyway) are >4.17.20? If so I'm a little confused by the "Preferred version (All functions work)" note for 3.27.1 in post #1.

Thank you!
PSdZ and PSdZData are not the same. PSdZ version is defined in E-Sys version (as opposed to PSdZData ripped from ISTA):



Injecting CAFD (Detect CAF for SWE) and Flashing ECU's with >= v.4.17.20 PSdZData requires using newer E-Sys 3.30.0 or higher.
 
#1,237 ·
I sure did however I am not getting any of the names when right click and select Edit FDL so I cannot see what they are called and can't search for them either
If you check out my second screenshot they are missing all their names unlike the values in this video at 6:43 time:
CAFD is Trimmed. Trimmed PSdZData means either E-Sys has Incorrect Target Connection, or you do not use E-Sys Launcher to open E-Sys, or you use E-Sys Launcher PREMIUM but select wrong car Series or this particular ECU CAFD is not mapped in E-Sys Launcher's CAFD Mapping Database, or you have insufficient Java Memory in order for E-Sys Launcher to map it.
 
#1,241 ·
Coding is ECU Specific, not Chassis specific, thus maybe it works for all G20 ECU or only some G20 ECU. Try 2.8 PRO as it is better CAFD mapping than 2.8 PREMIUM, but if you have issue, you likely need PRO 3.x.