Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]
SOLVED: ICOM & ISTA connectivity issues
05-11-2017, 22:15 PM,
(This post was last modified: 05-11-2017, 22:28 PM by aboulfad.)
Post: #1
|
|||
|
|||
SOLVED: ICOM & ISTA connectivity issues
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 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 ??? Code: Settings: Oh whats the chance that after I post this, I discovered that I was missing or I previousely removed this line from ediabas.ini: NetworkProtocol = TCP Now it works fine, can't believe how much time I wasted ... |
|||
05-11-2017, 22:38 PM,
Post: #2
|
|||
|
|||
SOLVED: ICOM & ISTA connectivity issues
Post your ediabas file
|
|||
05-11-2017, 22:38 PM,
Post: #3
|
|||
|
|||
RE: SOLVED: ICOM & ISTA connectivity issues
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
|
|||
05-11-2017, 22:40 PM,
(This post was last modified: 05-11-2017, 22:41 PM by aboulfad.)
Post: #4
|
|||
|
|||
RE: SOLVED: ICOM & ISTA connectivity issues
Thanks guys, but I discovered that I was missing or I previousely removed this line from ediabas.ini: NetworkProtocol = TCP
Now it works fine, can't believe how much time I wasted ... |
|||
« Next Oldest | Next Newest »
|
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Return to TopReturn to Content