[mikkaav]

Hello dear CT community!

I have been using ENET cables occasionally for some years now and I don't remember having issues with connections before.
But lately I am having a hard time to get ISTA+ to read out vehicle data or ESYS to see ZGW on G30.
Only way to get a working session is by leaving the car locked untill it goes to sleep (Emergency Triangle light goes out) and then enter car, connect ENET to car and laptop and then put the car into Diagnostic Mode. Only then I can read out Vehicle Data with ISTA+ or see the ZGW in ESYS.
When the car hasn't gone to sleep, then I can see ENET with IP and VIN in ISTA+ connection manager, but it will fail to read out vehicle data every time.
Also annoying is when I finish a successful session, go for test drive and after try to re-connect the car, then same problem happens - without letting the car go to sleep no new session can be read out (ENET IP and VIN still present).
Is my ENET cable gone bad? Or is the car's recently updated software preventing ENET access?
I would appreciate all ideas

OEM ICOM Next works every time all the time in every situation.

[noobontour]

Did you have a chance to test the cable and your computer on an other car?
Sounds to me like misconfiguration in software. had similar issues once with ISTA+ because of missing vcredist software.

[mikkaav]

Did you have a chance to test the cable and your computer on an other car?
Sounds to me like misconfiguration in software. had similar issues once with ISTA+ because of missing vcredist software.

I have tested on 3 different G30/G31 cars - same story. ENET not connecting when car comes from drive. Cars need to go to sleep before ENET can read out vehicle data.

I re-checked all the required softwares - all should be set and good to go.

[noobontour]

Did you have a chance to test the cable and your computer on an other car?
Sounds to me like misconfiguration in software. had similar issues once with ISTA+ because of missing vcredist software.

I have tested on 3 different G30/G31 cars - same story. ENET not connecting when car comes from drive. Cars need to go to sleep before ENET can read out vehicle data.

I re-checked all the required softwares - all should be set and good to go.

So this sounds to me that you are having a problem with your software. If i remember right in the past some users also had problems to connect to a car while switching between ISTA and E-Sys. Also there only letting the car fall asleep helped with connection problems. Unfortunatly i cant rememeber if this was ever fixed. I dont hink that it is on the cable because communication in general is working. For me it seems like windows is causing the problem. Have you changed something in the past? Any new software installed or changes in your securitysuite?

Last chance in my opinion would be a real cleaninstall from windows with only all windowsupdates and then fresh ISTA install without seperate ediabas stuff and other softwares. Just ISTA and then set ISTA to HO-ICOM / ENET local network and try to connect to your car only with ignition on. Dont forget, before installing ISTA, to install vcredist stuff. Also, for diagnostic only, the blp data would be enough.

[Node]

If you use ICOM it assigns IP addresses to a car over DHCP protocol. If your ENET is configured with APIPA addresses, car will not be visible after that...

---

P.S. Common guys, DHCP problems couple of pieces a day in this forum... Maybe read what it is, what is does and TRY to understand...