BMW ENET E-sys F, G, I Series Coding Guide

Anyone can do it if you report well to beginners. This guide is tralsted from Korean. Just for sharing purpose. You are at your risk.


Materials

-PC (laptop, desktop, etc.)

-program

- coding data (Psdzdata or SDP)

-cable



1. PC: OS Win 10 can be up to 64bit

2. Programs

  -BMW program: E-sys

  -BMW and others: E-sys Launcher Premium

 ※ There is a paid version E-sys Launcher Pro version, but if you are coding only my car, it is enough for Premium version.


3. Coding data (Psdzdata)

To code a vehicle, you need to have the data for that vehicle.

The coding data required for F, G, and I series is called Psdzdata (or SDP).

- Lite (for coding), Full (for programming) → Lite version is used for coding.



4. Cable (Interface)

The cable (interface) for connection with F, G, I series vehicles is called "ENET cable".

or ENET (Ethernet to OBD) Interface

※ BMW ICOM is a little bit specialized, but E-net cable is enough for coding only.

▶ Install the program

• Preinstallation program

      - Microsoft Netframework 4.5 or later: LINK

      - JAVA latest version: LINK

• E-sys installation (E-sys 3.27.1 or E-sys 3.30.1): LINK

• E-sys Launcher Premium 2.8.0: LINK


▶ Loading coded data (Psdzdata)

☞ Shortcut Latest Psdzdata 4.12.12 Lite: LINK

☞ Unzip the downloaded Psdzdata and copy it to C: \ Data \ psdzdata

※ Psdzdata Target / Chassis code

▣ Normal coding (FDL coding)

Run the E-sys LauncherPremium to proceed with the coding.
→ Automatically recalls E-sys.

☞ Coordinate file by model: LINK
☞ CheatKey file by car: LINK (from 'Coding Sharing Center')





VO (FA) coding (Vehicle Order)

Used to change the option status of the vehicle

☞ 'FA (VO) coding' go to: http://blog.obdii365.com/2018/04/27/enable-bmw-f46-cruise-control-by-vo-coding/


※ TokenMaster's NCD / CAFD Tool V 0.5.2

Useful program to know the contents of NCD / CAFD file, comparison, FA, etc.

☞ NCD / CAFD Tool V 0.5.2 Program: LINK


☞ 'How to use NCD / CAFD Tool': http://www.bimmerfest.com/forums/showthread.php?t=749668


If you want to study about other coding, please refer to the forum.

http://www.obdii365.com/producttags/bmw-enet-cable.html

BMW F Series ISTA failed to connect to ENET Cable Solution

Problem:

I have a F25 X3 to which I am trying to connect it to ISTA for diagnostics. The ENET cable I know works because it connects to E-SYS just fine for coding.

The ISTA program i have works fine as I use it when connecting to my E90 via a K+DCAN cable.

So I have changed the setting to ENET as shown here;

I then click on READ OUT VEHICLE DATA and then SETUP CONNECTION

So ISTA does actually find my car as it shows the VIN, etc

But then it struggles to identify the vehicle.

What am i doing wrong? Any ideas for a fix?

Solution:

Your edibas.ini is messed up. Try this one:

https://mega.nz/#!b1lxzC5I!xVslO1w_Uno_wkxrw_J2ebbzaGxdeP3AUdYqfvGRcG8

FLY: There are 2 ways to connect ISTA to ENET cable.

There is 2 option.
1-HO-ICOM/ENET direct connection. You can check connection via ZGW search-You will see IP, VIN, etc-then Your network adapter is setup correctly and connection is fine

I use it for enet
the last ENET connection
HO-ICOM/ENET direct connection
then you choose ENET and you have a connection
without the intermediation of EDIABAS.

2-Ediabas Standard Settings, EDIABAS.ini must setup for using with ENET

You must use “Ediabas Standard Settings” with BMW Enet cable and use Ediabasconfigurator to connect to Enet.

With Ediabas Configurator 2.0 is very easy to create a EDIABAS.INI no matter STD: OBD or ENET.

Reference: How to configure ICOM , ENET, K+DCAN cable for Rheingold ?

http://blog.obdii365.com/2018/07/15/bmw-ista-failed-to-connect-f-series-enet-cable-solution/