Hi everyone.
I own a BMW Z3 2.2i from 2002 (European model) and fixed various issues over the past 3 years using INPA.
Recently I came across ISTA-D and comparing that program to a printed screenshot from the dealership that printed me an overview of some active errors at the time before I got a diagnostics tool myself seemed very similar.
So I decided to install ISTA-D for myself on my own laptop.
First I had some trouble getting it running on Windows 7 (x86), presumably .NET framework related.
So I installed Windows 10 and ISTA-D pretty much worked out of the box.
Anyway, I decided to do a full-scan on my car and ISTA-D showed me a nice overview of my car's modules.
There were some errors active which I decided to clear, but to my surprise there were also quite some modules that ISTA-D marked as "ECU not responding".
Looking at those specific modules (IR, GM and BC_0xCD), it doesn't seem like they are really "broken" as I don't seem have any issues related to those modules (they seem to work just fine).
I also notice that there aren't a lot of modules compared to various screenshots and videos of ISTA-D I saw online. Is this always the case with E36 based cars?
As the car is relatively old, I can imagine that there aren't a lot of modules in these type of cars.
Do you guys (or gals) think the red modules really have communication issues in my car or if ISTA-D just marks them as false-positives?
Here are some screenshots of ISTA-D:
ISTA-D status 28-01-2019.png
ISTA-D status 28-01-2019 - 2.png
PS: I'm currently using Windows 10 Pro x86 with a K+DCAN USB cable using OBD.
Thanks!
Last edited by Olliek95; 01-28-2019 at 03:20 PM.
Make sure your cable latency is set to 1ms or 2ms in Device Manager.
-Abel
- E36 328is ~210-220whp: Lots of Mods.
- 2000 Z3: Many Mods.
- 2003 VW Jetta TDI Manual 47-50mpg
- 1999 S52 Estoril M Coupe
- 2014 328d Wagon, self-tuned, 270hp/430ft-lbs
- 2019 M2 Competition, self-tuned, 504whp
- 2016 Mini Cooper S
Thanks for your reply. I've checked and I do have the cable latency set to 1ms:
COM settings 2.png
COM settings 1.png
Bump. No-one?
Did you have any joy with this? I have the same issue with my 2011 E70 X5.
Sent from my ONEPLUS A6003 using Tapatalk
It would definitely seem to be a laptop/software issue or cable maybe as Carly via a Bluetooth dongle seems to work fine. I know Carly is less comprehensive but doesn't seem to have a problem communicating with the ECUs.
Sent from my ONEPLUS A6003 using Tapatalk
Your 2011 X5 is completely different in every possible way in terms of diagnostics than the E36 mentioned in first post.
-Abel
- E36 328is ~210-220whp: Lots of Mods.
- 2000 Z3: Many Mods.
- 2003 VW Jetta TDI Manual 47-50mpg
- 1999 S52 Estoril M Coupe
- 2014 328d Wagon, self-tuned, 270hp/430ft-lbs
- 2019 M2 Competition, self-tuned, 504whp
- 2016 Mini Cooper S
Yes i know, but as the issue appears to be with ISTA-D and not the car itself I was just curious if the OP had found a config issue or anything that might help.
Sent from my ONEPLUS A6003 using Tapatalk
If you're using a K+DCAN, i would first make sure that your latency is 1ms in device manager. Windows default is 16ms and often misses modules.
-Abel
- E36 328is ~210-220whp: Lots of Mods.
- 2000 Z3: Many Mods.
- 2003 VW Jetta TDI Manual 47-50mpg
- 1999 S52 Estoril M Coupe
- 2014 328d Wagon, self-tuned, 270hp/430ft-lbs
- 2019 M2 Competition, self-tuned, 504whp
- 2016 Mini Cooper S
I had a non-communication with a my immobilizer module in my E36/7 but my car worked fine which makes sense based on how it works (it doesn't use the diagnostic line to communicate with the DME). I found that it had a broken wire that was a pain in the butt to track down.
I have the EXACT same problem with my Z3. Even the same modules that are not responding. Did you or anyone find a cause? I checked all my cables with a multimeter but almost out of ideas. Do we have the same (bad) cable?
Kopie van IMG_5046.jpg
Bookmarks