BMW Programming: ISTA-P vs WinKFP vs E-sys

This is for those who are interested in tools used for programming/flashing a BMW car.

There is ISTA-P and E-SYS and Winkfp.

ISTA-P(ISSS-NEXT): Programming and coding software system
WINKFP: Engineer Software for E series, for programming

E-SYS: Engineer Software for F series (available for programming and coding)
ISTA vs WinKFP vs E-sys:

Which one should you use and why?

What are the advantages and disadvantages to use the one or the other?
http://www.chinacardiags.com/wholesale/bmw-icom-software.html
ISTA: simple, mainly new modules
WinKFP: main use is on Used Modules or Modified cars
E-sys: is a substitution for WinKFP
This world now has toooooo much money a float(read note#1)... before i used many used modules and so i used WinKFP... now a day i tell to people NO MORE USED Modules ONLY NEW so therefor i MAINLY use ISTA...... Many Shops in USA using AutoLogic Diag system... about a 1~1.5 year ago Autologic made an updated of it's software and now it does not allow to use used module.
So now a days in USA it's kinda a standard to use NEW modules ONLY everywhere you go (European cars)
If you mention "can mechanic use used module in my car" you get a respond maybe some other shop by not this one
Note: In South Bay Area California about a week ago or two it has been made into a law that if a family of 2 makes $250,000 or less, then family considers to be LOW-INCOME family, basically a homeless family.
Why do i need a hassle to reprogram used module when people that make $200+K are homeless... Driving a BMW.....
The last...
ISTA P will program used modules no problem in expert mode as long as it's the correct version of the module. Done it many times. But winkfp is easier.
But FYI, ISTA/P will not always program used modules.
Used modules such as airbag control unit in e6x will no proceed for example. Because of the non matching VIN number.
Will have to use WinKFP for this as it erases the VIN then encode the module.
Other modules such as active steering wheel control module to in E6x will not be flashed in ISTA/P if used. VIN will need to be erased first.

 Original:BMW Programming: ISTA-P vs WinKFP vs E-sys

BMW Programming: ISTA+ vs ISTA-P - Chinacardiags.com

What’s the main difference between ISTA-P and ISTA+?
First, functionality

• ISTA+ programs, but only with ICOM.
• ISTA-P and ISTA+ only encode (ie VO coding). If you want to FDL-code, use E-sys.

Second, the software installation

With ISTA+: You need ISTA Launcher, Admin License, BMW_ISPI_ISTA-APP *.msi, *.xml's, & *.istapackage.
With ISTA-P does not use ISTA Launcher. You can install with major version plus updates of *.istap & *.exe. Then, you need Admin License or ISTA-P loader to run.
Third, the vehicle coverage 

From the release notes, following series are supported for programming in ISTA+ and iLevels for each series:

• F001 (F0x, RR4, RR5) F001-16-11-501
• F010 (F06, F1x) F010-16-11-501
• F020 (F2x, F3x, F80, F82, F83, F87) F020-16-11-501
• F025 (F15, F16, F25, F26, F85, F86) F025-16-11-501
• F056 (F4x, F5x, F6x) F056-16-11-501
• S15A (G1x, G3x) S15A-16-07-506
• I001 (I03, I08) I001-16-07-506

The following Mini/RR programming is not supported in ISTA+

• R056 (R55, R56, R57, R58, R59, R60, R61)
• RR01 (RR1, RR2, RR3)

You can use ISTA/P to program these cars.
On a side note, Ista+ expert mode is Ista P expert mode

Attachment: ISTA+ and ISTA-P File Requirements:
Here take version 4.04.xx
Base:
BMW_ISPI_ISTA-META_4.03.13b.xml
BMW_ISPI_ISTA-META_4.03.22.xml
BMW_ISPI_ISTA-META_4.03.31.xml
BMW_ISPI_ISTA-META_4.04.31.xml
BMW_ISPI_ISTA-APP_4.03.13.18485.msi
BMW_ISPI_ISTA-APP_4.03.21.18572.msi
BMW_ISPI_ISTA-APP_4.03.31.18804.msi
BMW_ISPI_ISTA-APP_4.04.31.19448.msi
Service Data:
BMW_ISPI_ISTA-DATA_GLOBAL_4.03.12.istapackage
BMW_ISPI_ISTA-DATA_DELTA_4.03.21.istapackage
BMW_ISPI_ISTA-DATA_DELTA_4.03.30.istapackage
BMW_ISPI_ISTA-DATA_DELTA_4.04.30.istapackage
Language Data:
BMW_ISPI_ISTA-DATA_en-GB_4.03.12.istapackage
BMW_ISPI_ISTA-DATA_DELTA_en-GB_4.03.21.istapackage
BMW_ISPI_ISTA-DATA_DELTA_en-GB_4.03.30.istapackage
BMW_ISPI_ISTA-DATA_DELTA_en-GB_4.04.30.istapackage
Programming Data:
BMW_ISPI_ISTA-META_SDP_4.02.13.xml
BMW_ISPI_ISTA-META_SDP_4.02.20.xml
BMW_ISPI_ISTA-META_SDP_4.02.31.xml
BMW_ISPI_ISTA-META_SDP_4.02.31_for_4.03.10.xml
BMW_ISPI_ISTA-META_SDP_4.03.20.xml
BMW_ISPI_ISTA-META_SDP_4.03.30.xml
BMW_ISPI_ISTA-META_SDP_4.04.21.xml
BMW_ISPI_ISTA-META_SDP_4.04.31.xml
BMW_ISPI_ISTA-META_SDP_4.04.32.xml
BMW_ISPI_ISTA-SDP-DELTA_4.02.13.istapackage
BMW_ISPI_ISTA-SDP-DELTA_4.02.20.istapackage
BMW_ISPI_ISTA-SDP-DELTA_4.02.31.istapackage
BMW_ISPI_ISTA-SDP-DELTA_4.03.20.istapackage
BMW_ISPI_ISTA-SDP-DELTA_4.03.30.istapackage
BMW_ISPI_ISTA-SDP_FULL_4.02.12.istapackage
BMW_ISPI_ISTA-SDP-DELTA_4.04.31.istapackage
BMW_ISPI_ISTA-SDP-DELTA_4.04.32.istapackage
Other (Dependencies):
ISPI_PUK_ISPI-Process-Services_6.7.0.0.msi
BMW_ISPI_ISTA-LAUNCHER_1.8.0.2716.exe
BMW_ISPI_ISTA-META_ICOM-FW_03-14-04_1.xml
BMW_ISPI_ICOM-FW_03-14-04.msi
BMW_ISPI_ISTA-META_ICOM-Next-FW_03-14-10-1.xml
BMW_ISPI_ICOM-Next-FW_03-14-10.msi
If you want to use Admin Client (Again, you will need license):
BMW_ISPI_iLean_ISPI_Admin_Client_4.2.7.87.msi
ISTA/P from scratch (Admin Client and License are required or use ISTA/P Loader as Almaretto mentioned):
BMW_ISPI_ISTA-P_DAT_3.60.0.600.istap
BMW_ISPI_ISTA-P_DAT_3.60.1.003.istap
BMW_ISPI_ISTA-P_DAT_3.60.2.001.istap
BMW_ISPI_ISTA-P_DAT_3.60.3.001.istap
BMW_ISPI_ISTA-P_DAT_3.60.4.000.istap
BMW_ISPI_ISTA-P_SYS_3.60.0.600.exe
BMW_ISPI_ISTA-P_SYS_3.60.1.003.exe
BMW_ISPI_ISTA-P_SYS_3.60.2.001.exe
BMW_ISPI_ISTA-P_SYS_3.60.3.001.exe
BMW_ISPI_ISTA-P_SYS_3.60.4.000.exe
Major ISTA/P release:
BMW_ISPI_ISTA-P_SYS_3.61.0.500
BMW_ISPI_ISTA-P_DAT_3.61.0.500
BMW_ISPI_ISTA-P_SYS_3.61.1.001
BMW_ISPI_ISTA-P_DAT_3.61.1.001
BMW_ISPI_ISTA-P_SYS_3.61.2.002
BMW_ISPI_ISTA-P_DAT_3.61.2.002

Original:BMW Programming: ISTA+ vs ISTA-P

How to connect BMW E-SYS to ICOM or ENET cable

BMW E-SYS connection tips and guides for those with ICOM cables or ENET Ethernet interface...
BMW ICOM settings for E-SYS:
Step 1: Run ISTA-D and check ICOM IP (sometimes, slightly different of Windows IP 169.254.55.70)
Probably iToolRadar will do the same

Step 2: Run Easyconnect
TYPE: REMOTE
IP: 169.254.55.83 (edit file ip_dv.txt and add IP)
MODE: OBD_ab625
ICOM Lock
Check

Step 3: Run E-sys
Connect via ICOM cable/Ethernet interface (tcp://169.254.55.83:50160)

Esys Connection Questions & Answers:
Question & Answer 1:
Q: I used the ISTAD method to obtain the IP address. However, I was not able to get EasyConnect utility to work. Fortunately, I was still able to get ESys working and coded the RDC_Safety and blinker # back to what it was before.
A: EasyConnect just to displays IP. You can use ZGW to ID as well as iToolRadar to lock.
Also, trimmed data has no affect on connection. Using the incorrect launcher chassis, target & interface, or neither external charger or running engine to provide power to certain modules, can result in the ECU_ETHERNET map error.
Question & Answer 2:
Q: I connected via ICOM/Ethernet not URL.
As for the connection issue, I'm not sure what it was but I was able to to get it sorted out.
A: URL is used for flash programming, but you will use VIN for ENET and ICOM/ENET for ICOM to code.
Question & Answer 3:
Q: Why is url for flashing ?
Can i also take ICOM/ENET for flashing, with a icom clone ?
A: Actually only ZGW must be flash programmed via IP.
ENET can be used with E-sys or ISTA-P to flash.
ICOM (including clone) can be used with E-sys, ISTA-P, or ISTA+.
Question & Answer 4:
Q: Which settings i must choose for flashing in e-sys (URL or ICOM/ENET) ?
A: I believe it is still URL, but you must use DHCP (either software or router).
Question & Answer 5:
Q: I did exactly as mentioned to connect ICOM to OBDII and to my computer, but then when I get to connect using ESys, I got the following error message:
"Connection check failed. Gateway/ECU are not correctly connected or not responding. However Function using ODX-Data can be used. [G188]"
A: With ICOM, you connect via ICOM. You will need to lock IP with program like EasyConnect or Itool Radar
With ENET, you connect via VIN.
You connect via gateway URL if flashing. That error message occurs when you have incorrect IP.
Question & Answer 6:
Q: For ICOM, I was using ITool Radar to lock the IP, then in ESys, I used the IP found in ITool Radar to connect. Am I doing the right thing? Or do I still need to use ISTA to get the IP address??
And with ENet, after plugging in everything, my computer failed to recognize any connection from the Ethernet port. What I mean is that, there wasn't even a flashing light on the port that indicates my computer is connected to something, not normal, right?
A: For ICOM, you do not need to separately use ISTA+; that is just another way to discover IP.
With ENET, you should get fallback IP (169.x.x.x)
Question & Answer 7:
Q: So if I don't need ISAT+ to get the IP, then any clue why I still get that error on ESys after I press connect? Seems like I am getting the proper IP address off ITool Radar... any chance that my car computer is not responding?
And with ENET, it is not getting any fallback coz my computer don't even know it is plugged in... no steady nor blinking lights on the port...
Some others suggested that my car computer could be in some kind of safe/protection mode that it blocks external connection... is there such thing?
A: With ICOM, you can certainly try with ISTA+ to see if you get a different IP to lock with Itool Radar. For ICOM, are you selecting 4th interface type and putting in the same IP?
For ENET, are you selecting 5th option (VIN)? Are you getting anything populated?

• Make sure motor is running if car is not on a Charger.
• Third party Security Suites (Antivirus / Firewall / etc) are disabled
• LAN Adapter is set for DHCP and not using a Static IP.
• The Target Connection Window should not be blank (It should show multiple target connections for different chassis')