SOLVED: ICOM & ISTA connectivity issues

SOLVED: ICOM & ISTA connectivity issues - Printable Version

+- CarTechnoloGY (https://cartechnology.co.uk)
+-- Forum: Discussions All about Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=310)
+--- Forum: Automotive Help & Discussions / Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=40)
+---- Forum: BMW - Mini - Rolls Royce (https://cartechnology.co.uk/forumdisplay.php?fid=61)
+---- Thread: SOLVED: ICOM & ISTA connectivity issues (/showthread.php?tid=29612)

SOLVED: ICOM & ISTA connectivity issues - aboulfad - 05-11-2017

I have received a loaner ICOM from a fellow generous member and have been battling to get it working with ISTA and my F82. I usually sucessfully use ENET with ISTA but wanted to give an ICOM a try ...

PC communicates with ICOM, ICOM is able to retrieve car's VIN and it shows up in ISTA connection manager. And ICOM's web servers shows the following:

Code:
Vehicle ethernet available

HSFZ gateway available at:

Diag Addr: 0x10 Diagnostic Port: 50160 Control Port: 50161

The following HSFZ ECUs are available:

Diag Addr: 0x63 Diagnostic Port: 50990 Control Port: 50991

So all is good, but ISTA fails to perform vehicle ident or basic tests and returns the following error:

Quote:The connection to the vehicle could not be successfully restored, since it is not the same vehicle.Re-connect the vehicle...and if you click on details its EDIABAS INITIALIZATION Error NET-003. Which I traced it to ediabas not liking the INTERFACE = remote. If I start tool32, it barks with the same error, see pic.

Any ideas ??? read

Code:
Settings:

PC: win10, ISTA 4.08.12, no DHCP srv, using an APIPA IP addr 169.254.xx.yy

ICOM pkg v.03.15.00, sys v01.26.00, app v01.41.00

[b]ediabas.ini[/b] relevant entries: 

Interface         = REMOTE                          <--- this causes ediabas to generate error net-003

TCP RemoteHost             = 169.254.191.158  <--- ICOM IP addr

XETHERNET RemoteHost = 169.254.191.158

ISTA: Using default options in "Vehicle Interface"

Oh whats the chance that after I post this, I discovered that I was missing or I previousely removed gavel

this line from ediabas.ini:
NetworkProtocol = TCP

Now it works fine, can't believe how much time I wasted ...

SOLVED: ICOM & ISTA connectivity issues - Fordy51 - 05-11-2017

Post your ediabas file

RE: SOLVED: ICOM & ISTA connectivity issues - bimmer71 - 05-11-2017

Are you using windows 10, if so make sure any other adaptors are disabled or you will not be able to scan vehicle , unsure what's up with windows 10 but after you disable other connection other than wired lan , scanning car is possible , in if you not using windows 10 , this is useless , hope this helps

RE: SOLVED: ICOM & ISTA connectivity issues - aboulfad - 05-11-2017

Thanks guys, but I discovered that I was missing or I previousely removed gavel

this line from ediabas.ini: NetworkProtocol = TCP

Now it works fine, can't believe how much time I wasted ...