cable arrived, drivers installed, coding begun...

So far I've done these:
Remote closing windows
Auto Door Unlock

With the "Auto Door Unlock" does anyone know if there is a way to make everything unlock instead of just the drivers door?

This thread ended up helping me the most. My post above regarding bimmerforum was for NCS for dummies. I never could get that to work, I guess I'm "too" dummy. But the guide on the above thread was very clear and easy, so thanks to all that put that together

Can't wait to get further into whats possible!

 

Dez

Can you share the link where to download the software and drivers?

 

That thread has all the links and datens etc you need.

Good luck.

 

--

 

You must not End inpa. You should exit inpa (Shift+F10).

 

--

 

After installing all the stuff (including drivers for the cable), I got to the point where I connect the cable to the car and run Inpa to check for battery and ignition. But both ignition and battery show "off" and circles are not solid. What could be the problem here? My cable?

 

Just to confirm you have the ignition turned on correct?

 

Yeah. Ignition turned on. Not sure where I got the cable; it was a few years ago. So that is why I am thinking maybe it's the cable.

The cable lights up amber when I connect it to the laptop, but then the light goes away. Is it supposed to light up when connected to obd?

 

The light on my cable does go off and still appears to be connected to the car in Inpa.

Are you running NCSExpert and Inpa on a native windows machine or virtualized on a MAC?

Maybe you accidentally connected the cable to the MAC OS?

I run a virtualized environment and make sure I have VMWare and windows up before I connect the cable. It then prompts me which OS to connect it to, and I choose Windows.

Other then that, it might be worth trying another cable.

 

I am on Windows 7. I am going to try another cable. Is this one from the first page is still a good cable to get? http://www.ecutool.com/productshow.a...ortsid=&sorts=

 

It used to be almost guaranteed to be a good source for the cable but something happened a while back and people have received bad cables from them.

Maybe there is someone in your area that has a good cable that you could try.

 

This is great stuff but I do have one question. Does all this work on a 2002 base justa R50?

 

Yes, this also works for R50/52/53. We don't have as many cool features as the R56-later folks, but there are things we can change. I've added the double-blink hazards, fog lights stay on with high beams, disabled seatbelt warning light, added the 2nd trip meter on the OBC, and turned off the unlock beep on the remote.

Look here for more info on how to get NCSExpert working on a 1st gen MINI. There's a minor edit you'll need to make on the R50 daten file.

https://www.northamericanmotoring.co...de-add-in.html

https://www.northamericanmotoring.co...onal-info.html

 

You may be able to fix this by changing the option in the on-board computer using the control stalk to change it so that a single press of the keyfob will unlock both doors. I don't recall the exact location off the top of my head, but if you hold the button at the end of the stalk to enter into the settings, you should be able to find a setting (which is specific to which key you are using).

 

Originally Posted by DirtyMini
Anyone want to take a stab at this before I head to bmwcoding...trying to code in satellite radio to the 2RAD and I keep getting error in CABD, COAPI-2041: wrong ecu coding index, A-E65R: CODIERINDEX = 34h Using v38 datens. Should I update the datens to a later version?

I'm thinking I just ran into this.. I have a new cable on order anyway.. still reading to find or verify the fix.
and I'll try defaulting CAS and FRM modules to see if the VO changes work

 

You cannot use NCS Expert to code in SAT radio. You need an FSC code or something like that.

It might be true for all model years, I've forgotten what the exact details are.

 

timing Just PM'd you

 

I just bought the cable and plan to start using NCS expert soon, but I am very confused about a few things. Ive read through many threads on the subject but can't find the answer.

How do I know which datens to use? I see V38, V40, all the way up to V53. Would the newest datens work on an older software version? How do I know what version I'm running? Would using the wrong datens brick the car?

Can I use 64bit windows 7 in compatibility mode or will I need to run a virtual machine?

Has anything changed from the original guide at the beginning of the thread?

 

It is best to use the most recent datens (Data Sets). They are backward compatible.

You can use Win7 64bit natively if you have Standard Tools 2.12 and NCS Expert 4.

 

Thats the critical info I needed. Thanks!

Is that the version included in the beginning of this thread?

 

No, I don't believe so. I sent you a PM.

 

So I used cerenkov's files and everything installed fine. However, I am getting an error.
I followed the instructions explicitly (twice) and got the same result. I got INPA to to connect without a problem (showed ignition and battery as on). However, when I tried to get NCS to connect to module I got an error. "VIN is faulty" COAPI-2000

I confirmed that none of the pins are shorted internally. It appears to be some problem with the files or possibly my SW version. I am currently on C3.45.00 . Is anyone else on this SW version? Any ideas? Cerenkov and I were unable to figure it out.

Album of OBC menu here: http://imgur.com/a/2xRdH

 

Chances are you're needing a newer version of datens than what you're trying to use now.

 

Question for the experts around here. My previous experience with coding rear fog lights was on a 2009 Clubman S. I went to code a local club member's 2009 JCW Hardtop after he installed the rear fogs and switch toggle, however using the exact same steps as I did on the Clubman, I can only get the left fog light working on the JCW.

My steps were to add $588 to the VO, then default the car with the new VO string. I then went in to IHKS and changed the value for NEBEL_SCHLUSSLEUCHTE from nicht_aktiv to aktiv. Coded the car and everything worked as it should, minus the fact that only the left is lit.

I read that there was a second value in IHKS that also needed to be changed to aktiv, which was NSL_FUNKTION_SZM. I checked the TRC file that was pulled, and it was listed as aktiv already. So that part of the equation is correct.

What am I missing to get the right side lit as well? I'm also trying to make sure everything is sound coding wise before looking into possible wire issues.