2017 330e ISTA unable to get into "Control unit tree" screen

[feels1]

2017 330e F30 B48
eNet OBDII connector with network cable
ISTA v4.8.13.21258 Date 2014-09-17

Just bought a 330e and downloaded ISTA with newly purchased after market eNet connector.

In the Operations > Read Out Vehicle Data screen, both "Complete identification" and "Identification without vehicle test" buttons are not able to recognize my car.

I have to use Operations > VIN screen to input last 7 digit of the VIN number to get into "Vehicle information" screen. Then it does let me choose the network device of the OBDII connector.

I believe this leads me to problem to access Vehicle information > Control unit tree, and I lost many functionality to scan the car for potential issue. The tab is grey out.

I have a low fuel pressure issue with CEL light that I scanned by generic OBDII scanner, and planning to use ISTA to understand more.

Anyone know whether there is a specific ISTA version that will support hybrid 330e?

Thank you in advance

[328 Power 04]

What are your connection settings in ISTA configuration like?

Does your laptop see an IP address in the Ethernet port?

[feels1]

Does manually entering VIN will not able to use ENET adapter? In other word, it will be offline mode?

ISTA configuration setting (Wrench icon > Vehicle interface tab) is "Dealer organisation ICOM/ENET local area network"

In ISTA "Vehicle" VIN screen, it does prompt me to select the ENET interface with remote ENET IP of 169.254.104.86. See screenshot below

ISTA_Connection manager.png

My laptop can further ping the ENET's IP without issue. This confirms the laptop can talk to the ENET adapter with remote ENET's IP
ipconfig.png

Following is the ""The vehicle could not be identified" error when using either "Complete identification" or "Identification without vehicle test" button:
Vehicle cound not be identified.png

I almost forgot that I'm getting following message by either entering VIN, or select car's model (in tab Basic Features)
The vehicle could not be idenified. Please check the access to the vehicle and check whether the testing-analysis-diagnosis has been activated
alternative drive vehicle.png

I just installed v4.39.20 with files dated 2022-11-30. The "Read Out Vehicle Data" is failing as well. Clicked on "Details" button on error screen shows "IFH-0035: CONFIGURATION ERROR"
ISTA IFH err 1.png

I double checked several times that I have started the car (hold brake + Start button), when connecting in "Read Out Vehicle Data" screen

Thanks ahead for the help

[328 Power 04]

Oh, that's weird, it sees the car, but then it can't talk to it? The configuration is correct then.

A. Make sure that your Ethernet port doesn't have a static IP. It must be on automatic.
B. If that doesn't work, disconnect the car battery/batteries' ground for 30 seconds to reset the gateway (this sometimes happens)
C. If that doesn't work, check the OBD port pins for any pins pushed in/damaged. Pins 3, 11, 12, and 13 are the communication ones and the most important. 8 & 16 is a little important too.

If the pins are pushed in, you'll have to push them back forwards again. I've seen that a few times.

- - - Updated - - -

You should not need to type in a VIN at all. All of it would be automatic when it communicates correctly.

[feels1]

Disconnect battery - 330e has two 12V batteries. One at the front hood (AUX), one at rear trunk. Which one I should disconnect? Both?

Sorry, I'm new to F30. Owner of E46 with INPA, and single battery cars.

[328 Power 04]

I would do both

[feels1]

Identified the root cause as conflicting EDIABAS setting.

The laptop has INPA installed with EDIABAS. ISTA installed its own EDIABAS under its own directory again.

So previous EDIABAS (INPA) has a Windows environment variable EDIABAS_CONFIG_DIR which leads to ISTA failed to detect the car ("Complete identification" or "Identification without vehicle test" button) when it is calling EDIABAS in the background. This environment variables override its own EDIABAS and "talks" to the INPA's EDIABAS.

Following is how I fix it temporary:
1. Run CMD
2. Checks Windows environment variable to list down anything that define EDIABAS
3. If found environment variable EDIABAS_CONFIG_DIR set, then reset/delete it
4. Runs ISTAGUI.exe from CMD
Fix env var.png

Permanent workaround to keep both INPA and ISTA working:
1. Writes a Windows batch program that do above
2. Uses my custom batch program to run ISTA instead of the Windows shortcut

I'm able to see the fault code now
Fault code.png

[328 Power 04]

That should not be necessary at all

It's all in your configuration. I run 2 Ediabas installations and ISTA as well

[feels1]

I only need to remove Windows environment variable EDIABAS_CONFIG_DIR, then both "Complete identification" or "Identification without vehicle test" button work.

I can put back the environment variable to re-test and confirm this is the root cause.

I will update when I'm free.