[mcrussell]

Hi Guys,

Has anyone had an issue where an ENET Connection works in eSys but fails to find vehicle in ISTA & INPA with EDIABAS set to "ENET AUTOCONNECT"
My PC has been fine until a few days ago, tested on another PC & it all works as expected so I know its not the car or cable.

eSys connects fine, ZGW finds the car but ISTA see the car but in connection manager but fails to read the vin.. ICOM Works fine.

I have tried deleting LAN Drivers but no difference.

Any pointers would be appreciated Thanks

[redog4dy]

Hello, the same problem i had today, when checked my new laptop.

Esys was reading it, ista no.
So i reinstalled standard tools + ista and now everything is ok .

[mcrussell]

Just tried re-install of both Standard Tools & ISTA but still the same

[noobontour]

Didnt you have to set Connection in ISTA to "HO-ICOM/ENET local Network" to work with ENET?

[Wibbles]

Check the IPV4 settings on the ENET network adaptor on your PC, make sure you have it set to DHCP and not a fixed IP

[user0086]

Also make sure "search broadcast" includes the broadcast address of your DHCP range, usually the IP address with the last number replaced by 255, e.g. 192.168.68.255 in a typical setup.

[glljh2016]

Has the ISTA port been switched?

[mcrussell]

Didnt you have to set Connection in ISTA to "HO-ICOM/ENET local Network" to work with ENET?

If you select “ICOM over local Network“ it brings the connection manager window up then you select the vin of the car & it usually reads car or EDIABAS settings if you set Easy connect to ENET Autodetect then it just starts reading car directly

---

Check the IPV4 settings on the ENET network adaptor on your PC, make sure you have it set to DHCP and not a fixed IP

Thanks, I did check that just in case but they are set to DHCP, what’s weird is the ISTA connection manager sees the vin & shows ETH as the connection method but fails to read car once selected, if I use the icom I can diagnose & program without issue.
I feel a fresh copy of windows is going to be the only fix but I would love to get to the bottom of it.

---

Has the ISTA port been switched?

ENET Port in EDIABAS.ini is below:

[XEthernet]
;=============================================================================
RemoteHost =autodetect
HeaderFormat = 0
TesterAddress = F4,F5
ControlPort = 6811
DiagnosticPort = 6801
TimeoutConnect = 20000

& attached is the ISTA Config

[willisodhiambo]

I had a similar problem and in my case easy connect had corrupted my ediabas. Copied ediabas from another working computer and it now works. Maybe get a copy of bin file from a working system

[noobontour]

I never use ediabas settings for connecting ISTA with ENET cable and it always works like a charme.
Also ISTA has its own ediabas under "Ediabas\BIN" inside the ISTA installationsfolder. Maybe you sould change settings there.