BMW Forum - BimmerFest BMW Forums banner

Coding: (No Request) Latest Software Links

3 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,121 ·
Really stupid question, I think I'm just doing something stupid. I got the latest version of the Pzdsdata Lite files and was doing some coding. When I right clicked to Code the DSC ECU I got a message in the popup saying

VCM update : VCM update is deactivated .VCM will not be update (c197)

there was no error code after it

So I think either

a) I need the full Pzdsdata files to do this (not the lite version)

or

b) I need to check the Update VCM after TAL execution checkbox which appears on the Options tab of the Settings popup which appears when you click Options-->Settings in ESYS

Thanks
 
#1,127 ·
I am running Launcher Pro 3.4 with E-Sys versions 3.27.1 and 3.33.4 on my laptop. Everything works fine. Can I install ISTA+ on the same laptop or will this cause issues for E-Sys? If E-Sys and ISTA+ can coexist, do I simply install ISTA+ in the preferred folders mentioned in the ISTA+ installation guide?
 
#1,148 ·
hello.
anyone can help me, I want to program start stop on two cars, but I don't mind. Few body always writes me a mistake. I attach pictures. anyone in the proceedings can explain to me what I need to do to correct the error.

can anyone send me plsdata?
FEM HWEL in svt_soll is Blue, and not Black, then "SVK-Ist does not match expected SGBMIDs for ecu means you choose wrong I-Step Shipment".
 
#1,150 ·
After you calculate KIS/SVT Target, check the box that says "HW-IDs from SVTactual" and then Save as SVT_soll, and see if ECU HWEL is Black, not Red/BLue. If Black, it is safe to flash it. If Red/Blue, the only thing you can do is try different I-Step Shipment dates until hopefully one turns ECU HWEL Black. This is simply Trial and Error.
 
#1,159 ·
Not sure i understand what you ask. An I-Level (e.g. S15A-19-07-555) cross references to the ISTA+ version (e.g ISTA+ 4.19.4x) used to program car.
 
#1,161 ·
PM sent.

Lite Link is in Post #1. But if you have Full, there is Zero reason to also have Lite, and not that you would ever need it, but you could just make Lite from full.
 
#1,164 ·
My dealer updated the software in my car yesterday and my current I-Step is now S15A-19-11-520. I have downloaded the latest PSdZData. The target selector window now lists S15A-19-11-530 as the latest target for S15A. Is it safe to code? As I understand it, because the I-Step in my car is lower than the highest I-Step supported by the PSdZData data I have just downloaded, it is okay to code. The problem would the the reverse--i.e., a higher I-Step in the car than in the target selector window. Do I understand it correctly?
 

Attachments

#1,168 ·
Yeah, I got an error when reading coding data. This led to me to updating the PSdZData to the most recent version linked to in post #1. I just was not sure if that version was sufficient for my car or whether I should wait a few weeks until a new version becomes available. But given Shawn's and your replies I now understand how to interpret the info that shows up in target selector. Thank you both again!