We have recieved 83% of our goal ..


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
KDCAN doesnt work with ISTA/INPA
#1
Hello,
I’ve encountered a problem and I’m not sure how to solve it. I recently started getting into and using ISTA/INPA diagnostics for E/F/G series BMW vehicles. With the F/G series and an ENET cable, there are no issues at all – ISTA works exactly as it should. However, with the E series it’s a bit of a mystery. When using a K+DCAN cable with an E series car in ISTA, it either works partially or doesn’t work at all.
In my case, ISTA sometimes reads the E series vehicle data immediately and works normally, but other times it’s the opposite – every time it asks me to enter the vehicle VIN, and it all ends there, showing only the vehicle’s information. It’s not possible to read faults or select control units; the only option is to click “start vehicle test” and that’s it.
INPA behaves similarly – sometimes it works, sometimes it doesn’t respond at all. I’m using ISTA version 4.39.20 (as far as I know, the latest version that still supports the K+DCAN interface via Ediabas). All drivers are installed, including runtime, vcredist, Java, and the K+DCAN cable’s FTDI drivers. In Device Manager, the COM port is set correctly with 1ms latency. In ediabas.ini, the interface is set to
Code:
STD:OBD
, and in obd.ini the correct COM port is also selected.
I prepared two laptops for my friends with identical setups, but for them, ISTA with E series cars practically doesn’t work at all – it stops right after asking for the VIN. INPA doesn’t respond either, not even showing battery or ignition status. I would suspect faulty cables, but it’s unlikely – I bought three of them, and the chance that all are defective is extremely low. The seller is reputable.
On the laptops I prepared for my friends, as expected, F/G series cars with ENET work perfectly.
The cable has a switch that changes the 7-8 pin connection; I thought the issue might be related to that, but the result is exactly the same in both positions.

Thank you for your help..
Reply
#2
I advise you to make a separate laptop or Virtual machine for Exx , which you need to have :

1- windows 10 max , forget about Windows 11
2- very old version of ISTA+ , probably v3.xx or max v4.0
3- BMW Standard tools including Tool32 - INPA - NCS and WINKFP
4- Proper D-CAN cable and driver

From long experience , I found it hard these days to have one machine which can do all BMW Series, that's why I started using Virtual machines with VMware workstation pro . I have one for Exx which has windows 7 and no ISTA , and one for F / G / I with all kind of tools available.

Good luck , and hopefully other members who use D-Can these days can shade some light on how to solve your problem.
Reply
#3
Im using almost oldest w10 version. v1903 or v1906 i guess. I actually dont care what kind of ista it is, if one app could work with E series and F (G optional). Using standart tools from this topic - https://www.bimmerscene.com/showthread.php?tid=6292.

I think the problem might be in the cables, even i find that hard to believe, because the seller has 4k+ sales, and my cable partly works with my ista setup..

p.s is it normal for ISTA to ask VIN for bmw E series or it varies from car to car? Sometimes it asks, sometimes not.

p.s Even if INPA would work, that tool for me is too hard to use, and i find ISTA much easier and more informative for begginers such as me.
Reply
#4
Im having the same problem. Have bimmergeeks Expert KDcan cable. everything set correctly. It will be working great but whenever i switch over to scan my F30. everything goes to shit with switching back to E series and the cable will no longer work. I literally had to do a full system image recovery to get a base line again. Switching between these two cables ( K dcan & Enet) are no doubt an issue. Enet will Always work fine but its the Kdcan is somewhere in the issue of the driver / it becomes corrupt. because i have a lesser ( basic kcan ($15 cable) and it seems to work but its not NEARLY as fast and wouldnt want to risk coding with it just in case of some failure.
Reply
#5
(08-14-2025, 03:55 PM)Medicineman843 Wrote: Im having the same problem. Have bimmergeeks Expert KDcan cable. everything set correctly. It will be working great but whenever i switch over to scan my F30.

D-CAN and F30 ????? seriously bro Undecided
Reply
#6
any more ideas?
Reply
#7
(08-14-2025, 08:57 PM)ek1978 Wrote:
(08-14-2025, 03:55 PM)Medicineman843 Wrote: Im having the same problem. Have bimmergeeks Expert KDcan cable. everything set correctly. It will be working great but whenever i switch over to scan my F30.

D-CAN and F30 ????? seriously bro  Undecided

bimmergeeks DCAN should be able to connect to F series
Reply
#8
(08-14-2025, 08:57 PM)ek1978 Wrote:
(08-14-2025, 03:55 PM)Medicineman843 Wrote: Im having the same problem. Have bimmergeeks Expert KDcan cable. everything set correctly. It will be working great but whenever i switch over to scan my F30.

D-CAN and F30 ????? seriously bro  Undecided

Swtiching between Enet(F series) and Kdcan ( E series).
Reply
#9
strange, everything works clearly for me
Reply




Users browsing this thread: 1 Guest(s)