[erickarlborg]

Hi!

I have been searching info on this for a while now and have found so many different solutions so it would be very helpful to get a straight answer

I'm not new to coding, have done several successful codings on both 1, 3 and 5 series. I'm using the K+D cable from eBay and 01/18 daten files updated via the Tool.

So everything has worked just fine until I ran into this problem a while back:
VIN is faulty
Coapi-2000
ifh-0003

I then thought it was just that particular car but I now got the same error with another similar car.
The similarity is that they both are LCI and have iDrive/Navigation.
I have connected to other non-iDrive LCIs without any issues...

The error appears when I'm choosing ECU after the chassis. In Inpa I get both dots black but when I try to do something I get the same errors.

I would really appreciate any help I can get, I just want this to work!

Regards
Eric

[Doesha]

Close INPA completely before opening NCS.

[erickarlborg]

I have tried that also :/

[Doesha]

I would uninstall everything and start from the beginning again. If you are using Windows 10 also try compatibility mode

[erickarlborg]

Yeah maybe thats what I have to try. No I'm using an old XP pc.
It just feels like it would be some setting or something, or a faulty cable.

[Doesha]

Yeah double check your baud rate also. Im about to do a fresh install on another laptop. I know I will run into this issue, when I do it will click in my head. I'm like 75 perfent sure I uninstalled everything deleted everything and reinstalled and it fixed the issue.

[Doesha]

I just wt up another laptop and now I remember. Restart computer with cable already in USB port don't switch USB ports always use same one

[erickarlborg]

Thank you, I will try that!
Otherwise I will do the reinstall.

[Doesha]

Also make sure you choose your chassis first. I got the same issue this morning on my new install of a different laptop. you need to choose chassis first as e89 then continue with process ecu or choosing ecu

[erickarlborg]

Just a thought Doesha ,
Could it have something to do with program versions? Right now I'm running NCS 3.0.1, not sure about INPA/EDIABAS version. I think I will try to do a clean install with some later made package.
It just feels so strange that it would be the cable because I can access LCIs otherwise...

Do you know someone in here that is an absolute expert?

[Doesha]

Originally Posted by erickarlborg

Just a thought Doesha ,
Could it have something to do with program versions? Right now I'm running NCS 3.0.1, not sure about INPA/EDIABAS version. I think I will try to do a clean install with some later made package.
It just feels so strange that it would be the cable because I can access LCIs otherwise...

Do you know someone in here that is an absolute expert?

no I unfortunately do not. maybe hassmachine may know but not sure. most people have moved on since our cars are anywhere from 12 to 7 years old. or they want you to pay to do coding for you. have you gone to www.e90coding.com to look at additional tutorials, as well as youtube videos. also try setting up ncsdummy instead of ncsexpert that may work better for you. I feel like a dummy because I couldn't use or figure out ncsdummy but could figure out ncsexpert

[erickarlborg]

*SOLVED*

Update: Installed a switch on my cable and that was it, now works like a charm!
Apparently the iDrive does not communicate at all with the K-line.

[johnjohninsane3]

Originally Posted by erickarlborg

*SOLVED*

Update: Installed a switch on my cable and that was it, now works like a charm!
Apparently the iDrive does not communicate at all with the K-line.

How did you install it? I´m running with the same issue I´ve tried every single solution and non have worked.

[Joe@TopGearSolutions]

Originally Posted by johnjohninsane3

How did you install it? I´m running with the same issue I´ve tried every single solution and non have worked.

Check to make sure there isn't a jumper installed between pins 7/8. If there is, remove it.