We have recieved 83% of our goal ..


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Losing my mind with ISTA. Help needed!
#1
Decided to delete my very very old Windows 7 VM from 2017 where everything worked but it was bloated with some random other software and just got slow over very long time for using and installing various software, but it was mistake and here i am...


Im looking for help because Im completely stuck with ISTA connectivity. 

Every installation that i have made so far gets stuck on "Vehicle identification" part on ISTA and after some time it asks for VIN! No other errors anywhere else.


https://i.imgur.com/T8wJORX.jpeg
https://i.imgur.com/w69xutB.jpeg


I’ve spent the last 2 days / 16+ hours trying to get ISTA to work.
Im using VMware Workstation Player so I can quickly roll back to snapshots and retry installs/config changes. For example there is no problem with USB connectivity etc, because VCDS for VW works and connects like it should. There has to be that im doing wrong or installation manuals dont tell to do.

My goal is a Windows 10 VM that can handle both E-series (K+DCAN) and later F-series (ENET), ideally in one setup.
 
If that’s unrealistic or unstable, I’m also willing to run two separate VMs (one for E-series, one for F-series).

What ISTA version is most suitable for E series and F series?




And now little bit background information what i have tried and what versions.

ISTA never identifies the vehicle / cannot connect.

However, BMW Standard Tools works perfectly in the same environment:
  • INPA works
  • NCS Expert works
  • etc.

So the k-dcan cable/driver/COM setup seems fine, ISTA is the only thing that refuses to talk to the car.

OS tested
  • Windows 7 SP1
  • Windows 10 latest

Same result every time: ISTA cant find/connect to the car, but INPA/NCS still work.

All were downloaded from this forum except Rheingold 3.47.10 (found from other forum):
  • ISTA 4.53.4x
  • ISTA 4.52.4x
  • ISTA 4.49.2x
  • ISTA Standalone 4.39.20
  • ISTA Rheingold 3.47.10 (Windows 7)
Every install was done exactly according to the included instructions. Yes ediabas.ini connection type is selected alwsays on ISTA connection manager configuration tab.

At this point I don’t even know what else to try. Since Standard Tools software INPA etc connects fine...

I suspect the issue is within EDIABAS itself, possibly due to an incompatible version or mismatch between components or bad config?

I cant understand which EDIABAS from which directory ISTA uses and or what version is suitable for ISTA.

Have tried different versions of FTI drivers from http://www.ftdichip.com/Drivers/VCP.htm and some other found on different forums.


P.S. So far I’ve only tested connectivity with two different E series car. I havent yet tried an F series vehicle using an ENET cable.

Here are some EDIABAS config files from latest Windows 10 ISTA 4.39.20 installation, basically i have not changed on any installation other than connection type to STD:ODB and correct COM port.

C:\EDIABAS\BIN\EDIABAS.ini - https://pastebin.com/raw/Y6KDXRvC

C:\EDIABAS\BIN\obd.ini - https://pastebin.com/raw/w2edrjXB

C:\ec-apps\ISTA\Ediabas\BIN\EDIABAS.ini - https://pastebin.com/raw/gs3pdi5D


And some EDIABAS config files from Windows 7 ISTA Rheingold 3.47.10 installation.

C:\EDIABAS\BIN\EDIABAS.ini - https://pastebin.com/raw/U1sRnaAP

C:\EDIABAS\BIN\obd.ini - https://pastebin.com/raw/hGHM5Psz

C:\Program Files (x86)\Rheingold\Ediabas\BIN\EDIABAS.ini - https://pastebin.com/raw/0SmQ74nr

EDIT - COM port settings and driver version.

COM port settings - https://i.imgur.com/YglLTZ1.jpeg
Cable driver version(latest one that i tried, actually i went thru many versions of them) - https://i.imgur.com/SOZeiLg.png


Any help would be greatly appreciated.

Thank you!
Reply
#2
Any information about COM configuration (latency etc.)?
Reply
#3
(01-18-2026, 06:05 PM)Stratofortress Wrote: Any information about COM configuration (latency etc.)?

Sorry, totally forgot about this

COM port settings - https://i.imgur.com/YglLTZ1.jpeg
Cable driver version(latest one that i tried, actually i went thru many versions of them) - https://i.imgur.com/SOZeiLg.png
Reply
#4
Set bits per second to maximum for starters and make sure the Ediabas settings are correct for that involved with ISTA use.
Reply
#5
(01-18-2026, 10:24 PM)Stratofortress Wrote: Set bits per second to maximum for starters and make sure the Ediabas settings are correct for that involved with ISTA use.

I have tried with max com port speed also.
Question is, which settings are correct one Smile ?
Reply
#6
I see your Ediabas settings for ISTA is located at C:\ec-apps\ISTA\Ediabas\BIN\EDIABAS.ini and the interface is configured wrong for your needs.
[-] The following 1 user says Thank You to Stratofortress for this post:
  • ufo56
Reply
#7
(01-18-2026, 11:08 PM)Stratofortress Wrote: I see your Ediabas settings for ISTA is located at C:\ec-apps\ISTA\Ediabas\BIN\EDIABAS.ini and the interface is configured wrong for your needs.
Huhh, now i see my mistake, but probably one time or another i have tried STD:OBD here on that configuration file also. Going to try tomorrow. I will post update here after that.
Reply
#8
(01-18-2026, 11:08 PM)Stratofortress Wrote: I see your Ediabas settings for ISTA is located at C:\ec-apps\ISTA\Ediabas\BIN\EDIABAS.ini and the interface is configured wrong for your needs.

Hi

Windows 10 machine with ISTA 4.39.20 changing C:\ec-apps\ISTA\Ediabas\BIN\EDIABAS.ini to STD:OBD did not help, still not working.
On Windows 7 machine changed C:\Program Files (x86)\Rheingold\Ediabas\BIN\EDIABAS.ini to STD:OBD and it started to working. Not great but i can live with 2 virtual machines, one for E series and other for newer.
Reply
#9
ISTA interface settings configured for ediabas use on the Win10 setup? There are two versions of Ediabas installed on your Win10 setup, which creates a conflict. Better use 7.3 only as with your Win7 setup.
Reply
#10
(01-22-2026, 08:09 PM)Stratofortress Wrote: ISTA interface settings configured for ediabas use on the Win10 setup? There are two versions of Ediabas installed on your Win10 setup, which creates a conflict. Better use 7.3 only as with your Win7 setup.

Tried same settings as on Win 7.
These two versions came with installer that is from this forum. Nothing is installed additionally outside downloaded installer.
Reply




Users browsing this thread: 1 Guest(s)