[InAndAround]

My experience says that you need patience to use a icom diag head with e-sys, it's a 50/50 chance that it will work or not, or, something may not work. Last time I had a problem that I could code a lot of modules, except the BKOMBI module was uncodable (it gave a error on coding, don't know what type of error).

[KaiO]

Sorry, but that's nonsense. ICOM works without any problems with ESYS. The right settings presumed

[jararak]

My experience says that you need patience to use a icom diag head with e-sys, it's a 50/50 chance that it will work or not, or, something may not work. Last time I had a problem that I could code a lot of modules, except the BKOMBI module was uncodable (it gave a error on coding, don't know what type of error).

there is no chance icom wont work, there is sometimes issue, it get different IP from DHCP. Regarding your problem - you have to have old psdz daten files this is why you are not able to code kombi.

[InAndAround]

The error was something about the ethernet connection, so I don't think it was the PSDz daten being to old because the whole car wasn't updated a long time and it's a first year F20 (2010 or 2011 I think). Also the chinese icom head was never updated...

[jaki]

Same Problem.
I have used Icom A2 for years without any problem with hundereds of E and F- series(with Ista), but finally I had time to test it with E-SYS
So: first with itoolradar reserve -> went ok (I also use this for Inpa, in my Inpa there is some F-series scripts)
The started E-sys. In "target" there is anything!
My E-sys configuration is bought hardware ready from China, so I haven't configured it anyway. Is there somewhere communication manager or such in E-sys? NCS expert and all E-series are very familiar to me but not these F-series tools

[Roo]

I confirm that ICOM (at least chinese) may not always let to connect e-sys to the car.
ICOM web interface 169.254.92.38:60080 shows the channels. So sometimes "no blah-blah available" (sorry, don't remember the exact message) message is displayed there. People says that it happens due to periodic jam of ZGW module, and sleeping of the car for some time solves the problem.
Would be nice if someone could clarify this and elaborate.

[Jynkky]

sleeping of the car for some time solves the problem.
Would be nice if someone could clarify this and elaborate.

resetting zgw via d-can cable (or icom) with inpa etc, and sleeping of the car will always solve a problem, if a problem is stuck zgw

[jaki]

I confirm that ICOM (at least chinese) may not always let to connect e-sys to the car.
ICOM web interface 169.254.92.38:60080 shows the channels. So sometimes "no blah-blah available" (sorry, don't remember the exact message) message is displayed there. People says that it happens due to periodic jam of ZGW module, and sleeping of the car for some time solves the problem.
Would be nice if someone could clarify this and elaborate.

Ok, nice to hear that.
I totally forgot that I also have original Icom Next, I assume that it should also work with Esys. Me stupid, didn't test that at all...

EDIT: my mistake. The problem was in esys installation (was done only halfway thru). I made enet cable for testing, but the real problem was in data files. Probable my icom would also work ok, try it sometime later.