Hey there...

All under XP mode in a win7 x64 host

INPA, working, showing battery and ignition ON
when INPA is running, the system tray has the icon where I can click and get a window showing stuff about EDIABAS

NCSExpert, I try to read VIN from ECU and get told
VIN is faulty
no response from ecu

clicking the system tray thing talks about NCSExpert being 7.2, but no words about EDIABAS (all blank)

my usb obdii cable is attached into the xp mode VM, is assigned a COM3 that I've set latency to 1

Now, I have no ghetto/mix of files. I have a straight install of "bmw standard tools 2.11" where I chose the COM3 options, did not check the usb-serial option...

and then I had a R56 datens folder, put stuff in the right place and ran LADEN.bat

any ideas where to get started? bought the cable recently, when plugged in I see an orange LED, when INPA is running IIRC i saw it green... it has a sticker on it BMW INPA K+DCAN

 

Just an update on something I tried -- I've read the built-in "FAQ" about the error code I was getting and their suggestions included:
1) ensure you're using the OBD interface. I was.
2) something about COM1 which I'll try too later...

Now I also found that the OBD.ini file may contained "USB" as an option, which I tried and then INPA stops working, so I conclude that leaving STD:OBD and leaving OBD.ini as was configured by the setup is the right thing.

Any other ideas? I'm still hung up on noticing that while NCSExpert is open after failing the vin read, the system tray icon does not show EDIABAS's path or anything...

 

:-(

I recently re-installed from https://www.northamericanmotoring.co...beginners.html using datens v40 right away, INPA shows both black dots, NCSExpert gives me the same error of getting no answer, code 9.

On this pin 7-8 business I opened up the cable end and looked and 7 and 8 are not soldered together or jumpered together. Based on what I read that's OK...

 

Everything I have read says the software dislikes 64-bit OS

 

NCSExpert is a 16-bit program which does not work on x64 Windows. The rest of the programs work fine, as all of them are 32-bit.

As far as I know, this setup can only work if the host has EDIABAS 6.4.7. Version 7 does not work in a server setup. Having EDIABAS 7 in the virtual machine should work ok.

However if INPA is indeed working, then I would imagine you have a faulty installation, rather than configuration. You said you used v40 Datens... Did you update the ECU files in the EDIABAS installation (virtual side)?

 

hey alex, thanks for chiming in.

to be clear, I'm running everything in XP Mode's virtual machine (which IIRC is a 32bit OS config, even when on win7 x64). I also noticed that INPA was fine on Win7 but NCSExpert wasn't, that's when I went 100% XP Mode VM.

I actually did update the ECU folder under EDIABAS (which I think the 1st time I ever tried anything I mistakenly placed under C:\NCSEXPERT).

I keep not wanting to install old versions of things, but I think my next step will just be to follow one of my guides 100% even though its stuff that's older than some other individual installers I have. So far I keep wanting to use BMW Standard Tools 2.11 (whereas another guide/kit is using 2.5 or something IIRC, and v38 datens)

See, I'm most worried about running a sw version and datens older than what I have on my car... it's an 09 but has had a jcw tuning kit and sw upgrades late 2011.

 

I just came back from another try - Ediabas 6.something, BMW tools 2.something less than 11, XP mode, ECU in ediabas folder got some files, and datens/r56 as well as sgdat ...
and asking to read the CAS module thing (F1, F3) I see the cable light up green with a few blinks and then... "no response from ECU"

Could this be a symptom of too new a car/needing even newer datens ?

 

Hmmm.... As always, do use the latest version of the DATENs available to you. What I certainly know, the latest ECU files often do not work with older versions of EDIABAS.

Anyway... Apart from the DATENS did you also copy the SGDAT folder from the R56 folder over to NCSExpert folder?

 

Yeah, I had copied SGDAT.

Next step for me is to go back to BMW Standard Tools 2.11, and simply try and install the absolute latest and greatest datens files. I have what is claimed to be V45, but its archive carries a bunch of directories:

cfgdat
daten
ecu
format
kmmData
sgdat

one thing is I think last i tried I got something that sounded like bad files, but I had not learnt that ECU goes into EDIABAS, not ncsexpert!

hope I get there soon

 

Two things come to mind. The latest R56 daten files are v45 and v46. You definitely need the latest ones for newer cars and for cars that have been updated by a dealer with new firmware. Also, NCSexpert needs the cable to be on Com1. You can see the setup of the software at www.bmwcoding.com and www.bmwcoders.com. There are a lot of cables for sale that do not work properly. The one from One Stop Electronics in south east Asia is good quality, $99 but works well. I have coded a bunch of BMWs with it, just getting started looking at MINIs. Lastly, NCSexpert and 64bit windows really do not agree with each other. Best to load up an older laptop or NetBook with Windows 7 x32 and go from there. It is much easier!