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

BMW E-SYS connection tips and guides for all those with ICOM cables or ENET Ethernet interface…

BMW ICOM settings for E-SYS:

Step 1: Run ISTA-D and check ICOM IP (occasionally, slightly different of Windows IP 169.254.55.70)
Possibly iToolRadar will do exactly the same

BMW-E-SYS-1

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

BMW-E-SYS-2

Step three: Run E-sys

BMW-E-SYS-3 BMW-E-SYS-4

Connect through 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 two:
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 four:
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 by means of ICOM. You will need to lock IP with program like EasyConnect or Itool Radar
With ENET, you connect through VIN.
You connect by means of 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 ICOM 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 distinct IP to lock with Itool Radar. For ICOM A2, are you selecting 4th interface form and putting in the identical 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’)

How to convert HALOGEN to LCI HEADLIGHT with a ICOM cable

It’s a HALOGEN TO LCI HEADLIGHT Tutorial!!!!

Excuse my English I hope this help some of you guys!

In this site you will see the diagram for wiring!

Now after you know what your going to do with the wiring uninstall the frm and install frm2.

You will need NCS expert and Winkfp and inpa! and the icom cable obd to the computer! when you get the cable just read instruction and you ill be fine.. but just in case if your cable didnt bring the instruction here is how to program the cable make sure the computer read the cable if not download the driver after your pc read cable go to start on computer right click properties, device manager,then PORT click on it look for the cable then double click then a window will open lick on port setting (tap) click on advance at the bottom and make sure to set COM to COM1 and the latency to 1 it should be on 16 from default click ok and you are ready to go!

After you install all this software you need to open NCS expert to Change VO and VIN to yor frm2. And then program it!

OK now if you have AHL you need to add this VOs $522 and $524 to CAS and FRM and change production date that is going to be like this for example (#1205) you have to change it to at least #0307. and if you have just xenon add $522 and production date #0307. NOW question is how to do it.

open NCS expert on file tap load profile select expert mode F1,F3 select chassis e89 and select CAS now F2 (ENTER FA) select chassis again then enter vin# of the car

now a new window will open with a list of numbers.. is gonna say attribute ADD and OK at the bottom now we are going to add $522 and $524 and click in top of the first one that is the production date and hit the delete bottom on your keyboard and add the #0307 and click OK then F6 back then choose F4 choose CAS then F2 change job to FA_WRITE and F3 execute job and you are done!

Now you have to pass that information to “NFRM”

1.open NCS expert

2.File-Load profile

3.select EXPERMODE

4.press F1

5.press F3

6.select E89<for E90>

7.select CAS

8.F6 back

9.now you will be able to see your (FG) VIN # at top and (FA) VO

10.press F4<CHOOSE ECU>

11.select NFRM

12.after that select F2 chenge Job

13 choose FA_WRITE

14.F3 executive job wait a little bit and it will say courin beenet or coded ended something like that! now your VO are the same CAS and NFRM

NOW to change VIN

I did it the same way as CAS but instead of choose FA_WRITE i Choose FG_SCHREIBEN

1.open NCS expert

2.File-Load profile

3.select EXPERMODE

4.press F1

5.press F3

6.select E89<for E90>

7.select CAS

8.F6 back

9.now you will be able to see your (FG) VIN # at top and (FA) VO

10.press F4<CHOOSE ECU>

11.select NFRM

12.after that select F2 chenge Job FG_SCHREIBEN then F3 execute Job

now to make sure everything is good Go back to the main menu (or restart ncs-expert) and get the vehicle order from the “NFRM” module. Make sure NFRM returns YOUR VIN and YOUR VO. We want the VIN (FG) and VO (FA) to be the same in both CAS and NFRM. To do this same steps load profile expertmode F1,F3 select chassis and select “NFRM” NOT CAS!!! and it should be your VIN and VO the same as CAS.

Now to program NFRM you have to use Winkfp but first you need to know the part number of the NFRM using inpa that is gonna show on inpa FRM_70. go to inpa folder and look for inpaload select chassis and a window will open and select the first one functional jobs then f2 indet in there you will look for FRM_70 and copy the ZUB that is the part number IT should say for example (9204527) this is a example copy that number down and close inpa. now open Winkfp and choose confort mode F1 enter ZUSB put the number that you wrote down here and ill look for your frm automatically click ok then F4 Enter Vin put your car vin # click ok and then update ZUSB look for the one that gives you in the first step for ex(FRM2) then click on done! if it gives you an error 106 is because you dont have the cable plug in into the car! after that lick on F3 Prog. ZB UPdate and wait until is done and you are done!

Now to make sure BMW Diagnostic Software NFRM is default in NCS expert

load profile then go back to file and click edit file and click on FSW/PSW and uncheck the option “FSW/PSW manipulate with FSW_PSW.MAN” then click ok and choose profile info and on the name put whatever name that will remember you that thats the profile to code to factory any ecu using NCS expert then click ok and ok again that windows will close and click file save as and put the name that you choose.. Then F1, F3 choose chassis then CAS then F4 choose NFRM then F2 SG_codieren then F3 done!

Now to code with NCS expert you will need to create a FSW_PSW TRC file..

here is a video on Youtube but just in case if the video is not working ill write it down

To do this you have to Open NCS expert load profile expertmode

same F1,F3 select chassis select CAS F6 back choose ecu F4 NFRM and change job F2 CODIERDATEN_LESEN then f3 execute job now dont close ncs expert and go to ncs expert folder then to work folder and you will see that there is a FSW_PSW trc file open the file change what ever you need to change and after you change everything save the file.. go to file and click save as and write FSW_PSW.MAN now go back to NCS expert and Click on file edit file and go to FSW_PSW click on it and make sure to check the option FSW_PSW manipulate with FSW_PSW.MAN click ok then choose ECU F4 select the Ecu that you choose to read with CODIERDATEN_LESEN earlier and now change to to SG_codieren and F3 execute job and You are DONE coding!

THANK YOU FOR READING I HOPE THIS WILL HELP SOMEONE I SPENT 2 WEEK TO LEARN ALL THIS AND NOW I WANT TO SHOW IT TO YOU GUYS!