[jphughan]

Originally Posted by Barrique_Red

I ordered mine today...I have a 2006 E90 (325xi), and am wanting to change my battery. Planning to use the cable and associated s/w to register my new battery.

mikey.

It works for that, I've done it. There are DIYs on this forum, search register battery. Use the Tool32 method, not INPA.

[steelersfan]

Joy and Pain

The joy: My cable arrived today....didn't expect it until atleast next week.
The Pain: I can't seem to get this to work.

I'm running Windows XP in a VMWare Fusion virtual machine on Mac OSX Lion.
I have a 2011 335i E90.

I've installed the software (NCSEXPER.rar) as per the NCS_DIY.pdf file at the beginning of the thread.

Of course I'm using the "recommended" cable from "one-stop electronics", or vendor 'Automotive-Tools' on ebay.

It also came with an additional adapter: see below

Not sure if I should be using the adapter or not? I've tried with and without the adapter and still no joy.

I did remove the cable headshell, after reading some thread notes about removing 8 pin. It looks like pin is still soldered in on my cable. Do I need to desolder pin 8 in order for the cable to work on a 2011???

[jphughan]

Originally Posted by steelersfan

Joy and Pain

The joy: My cable arrived today....didn't expect it until atleast next week.
The Pain: I can't seem to get this to work.

I'm running Windows XP in a VMWare Fusion virtual machine on Mac OSX Lion.
I have a 2011 335i E90.

I've installed the software (NCSEXPER.rar) as per the NCS_DIY.pdf file at the beginning of the thread.

Of course I'm using the "recommended" cable from "one-stop electronics", or vendor 'Automotive-Tools' on ebay.

It also came with an additional adapter: see below

Not sure if I should be using the adapter or not? I've tried with and without the adapter and still no joy.

I did remove the cable headshell, after reading some thread notes about removing 8 pin. It looks like pin is still soldered in on my cable. Do I need to desolder pin 8 in order for the cable to work on a 2011???

If you have an adapter then Pin 8 is deactivated; the purpose of the adapter is to reactivate it for older cars. And no you shouldn't be using it on a 2011. Automotive-tool always deactivates Pin 8, so if it looks active to you, you might be looking at the wrong pin.

As far as your issue, "I can't get it to work" is way too broad for us to help you out. What part of the DIY are you stuck on? Are you seeing a particular error message or behavior? Have you updated your daten since you're coding a 2011? The more info you provide, the more we can help.

[steelersfan]

Originally Posted by jphughan

If you have an adapter then Pin 8 is deactivated; the purpose of the adapter is to reactivate it for older cars. And no you shouldn't be using it on a 2011. Automotive-tool always deactivates Pin 8, so if it looks active to you, you might be looking at the wrong pin.

As far as your issue, "I can't get it to work" is way too broad for us to help you out. What part of the DIY are you stuck on? Are you seeing a particular error message or behavior? Have you updated your daten since you're coding a 2011? The more info you provide, the more we can help.

My bad: Let me update the post:

My original problem was at step 13, when I ran INPALOAD, "no black circles".
That problem has been solved. Turns out, WinXP in a VMWARE Fusion VM mapped my virtual USB Serial Port COM3 vice COM1. "Thanks srwatters" I corrected that and I'm in and talking to the car. Now I've run into another hiccup at step 40 of the DIY. CAS is selected and I press OK and I get this message: "Following Feature is invalid for FA $6NR".

Is that the result of an outdated "daten" file? Ifso, it's more reading to determine how to update the "daten" file.

[matrix76]

I am just about ready to code my 2011 E90 w/nav and here is my list. Did I leave anything out that I should be adding to the list?

Coding 2011 E90

Unlock Doors CAS ER_KEYOUT_AUOVR
Close Win/SunR CAS KOMFORTSCHLIESSUNG_FB
Fog Lights + HB’s NFRM FL_UND_NSW_NICHT_GLEICHZ
Fold Mirrors w/Fob NFRM ASP_KOMFORT_EINKLAPP
AE’s 12V NFRM PWM_RL_BL_1_FKT_SL Change wert_06 to _01
Digital Mpg/Kpl KOMBI DIGITAL_KVA
Digital Speed KOMBI BC_DIGITAL_V
Digital Speed Value KOMBI BC_DIGITAL_V_KORREKTUR
Auto Sensitivity KOMBI LICHT_AUT_WERT_1 aktiv, LICHT_AUT_WERT_2 aktiv, LICHT_AUT_WERT_3 aktiv

[jphughan]

Originally Posted by steelersfan

My bad: Let me update the post:

My original problem was at step 13, when I ran INPALOAD, "no black circles".
That problem has been solved. Turns out, WinXP in a VMWARE Fusion VM mapped my virtual USB Serial Port COM3 vice COM1. "Thanks srwatters" I corrected that and I'm in and talking to the car. Now I've run into another hiccup at step 40 of the DIY. CAS is selected and I press OK and I get this message: "Following Feature is invalid for FA $6NR".

Is that the result of an outdated "daten" file? Ifso, it's more reading to determine how to update the "daten" file.

Yes, that error is old daten; the version you have now don't know how to deal with the new 6NR option. You need at least V42 which is when 6NR support was added, though your car might even have V43 installed. Instructions and the daten files themselves should be quick to find.

[jphughan]

Originally Posted by matrix76

I am just about ready to code my 2011 E90 w/nav and here is my list. Did I leave anything out that I should be adding to the list?

Coding 2011 E90

Unlock Doors CAS ER_KEYOUT_AUOVR
Close Win/SunR CAS KOMFORTSCHLIESSUNG_FB
Fog Lights + HB’s NFRM FL_UND_NSW_NICHT_GLEICHZ
Fold Mirrors w/Fob NFRM ASP_KOMFORT_EINKLAPP
AE’s 12V NFRM PWM_RL_BL_1_FKT_SL Change wert_06 to _01
Digital Mpg/Kpl KOMBI DIGITAL_KVA
Digital Speed KOMBI BC_DIGITAL_V
Digital Speed Value KOMBI BC_DIGITAL_V_KORREKTUR
Auto Sensitivity KOMBI LICHT_AUT_WERT_1 aktiv, LICHT_AUT_WERT_2 aktiv, LICHT_AUT_WERT_3 aktiv

Auto sensitivity only works on non-iDrive cars. Never tried that 12V setting, but make sure it's valid for the hardware FRM module version you have.

[matrix76]

Originally Posted by jphughan

Auto sensitivity only works on non-iDrive cars. Never tried that 12V setting, but make sure it's valid for the hardware FRM module version you have.

Thanks, I also heard that the auto sensitivity can be added to the idrive? I will also will look into the 12v setting, t/y.

[steelersfan]

Originally Posted by jphughan

Yes, that error is old daten; the version you have now don't know how to deal with the new 6NR option. You need at least V42 which is when 6NR support was added, though your car might even have V43 installed. Instructions and the daten files themselves should be quick to find.

Thanks: Found and updated to V43 DATEN file. No more errors

btw: I know this might sound like a dumb question, but is there somewhere you can look to see what DATEN version you're running?

I also found 2 versions of ediabas 7.2:
filename: EDIABAS_7_2_0.rar has a version 7.2.0_Package_1.2 version number is the versions.def file

filename: EDIABAS_7[1].2.0.504.7z has a version 7.2.0_Package_2.0 version number is the versions.def file

Which one is the right one to use for those who have upgraded to 7.2?

[revlimit]

[QUOTE=jphughan;11065451]If you have an adapter then Pin 8 is deactivated; the purpose of the adapter is to reactivate it for older cars. And no you shouldn't be using it on a 2011. Automotive-tool always deactivates Pin 8, so if it looks active to you, you might be looking at the wrong pin.

I just place an order for the cable. So if I have an 09 E92, I will need to use this adapter?

[steelersfan]

So as I was going through the steps of the DIY , hopefully on my way towards my first successful coding up to the step where you select the module to read from the ECU, I looked up and noticed lights on the instrument cluster flashing, my windshield wipers were wiping even though I never touched the wiper stalk. It was kind of "nerve racking" for lack of a better description.

Is that "normal" behavior to be expected when you're in the process of coding, or reading the ECU from the car?

I was on the original Ediabas version 6.4.7 (I believe) although I had updated the daten file, to version 43.

Note: I don't remember exactly when the madness started, but I intend on finding out today.

[jphughan]

Originally Posted by steelersfan

btw: I know this might sound like a dumb question, but is there somewhere you can look to see what DATEN version you're running?

I also found 2 versions of ediabas 7.2:
filename: EDIABAS_7_2_0.rar has a version 7.2.0_Package_1.2 version number is the versions.def file

filename: EDIABAS_7[1].2.0.504.7z has a version 7.2.0_Package_2.0 version number is the versions.def file

Which one is the right one to use for those who have upgraded to 7.2?

Daten version is just determined by the Modified date of the daten files themselves; nothing in the files actually lists the version numbers.

As for EDIABAS, I'm not sure why you're seeing different 7.2 packages floating around, but try either one. All you should need to do is rename your existing EDIABAS folder to EDIABAS-old, copy the new one to C:\, copy the ECU folder from your active daten package into the new EDIBAS folder, and then check EDIABAS.INI to make sure the 3 Path configuration lines at the top all start with C:\EDIABAS (on my package one of them started with P:\ and that broke stuff).

Originally Posted by revlimit

I just place an order for the cable. So if I have an 09 E92, I will need to use this adapter?

CORRECTION: You will not need the adapter. That's only for cars produced prior to 3/2006 (i.e. before DCAN was introduced).

Originally Posted by steelersfan

So as I was going through the steps of the DIY , hopefully on my way towards my first successful coding up to the step where you select the module to read from the ECU, I looked up and noticed lights on the instrument cluster flashing, my windshield wipers were wiping even though I never touched the wiper stalk. It was kind of "nerve racking" for lack of a better description.

Is that "normal" behavior to be expected when you're in the process of coding, or reading the ECU from the car?

I was on the original Ediabas version 6.4.7 (I believe) although I had updated the daten file, to version 43.

Note: I don't remember exactly when the madness started, but I intend on finding out today.

Hmm, not sure what's up with that. I've never seen that issue before; I just make sure the car is in full-on Ignition mode (i.e. pressing Start twice with Comfort Access or keyfob in slot and press Start without CA). Good luck though!

[steelersfan]

Originally Posted by jphughan

Daten version is just determined by the Modified date of the daten files themselves; nothing in the files actually lists the version numbers.

As for EDIABAS, I'm not sure why you're seeing different 7.2 packages floating around, but try either one. All you should need to do is rename your existing EDIABAS folder to EDIABAS-old, copy the new one to C:\, copy the ECU folder from your active daten package into the new EDIBAS folder, and then check EDIABAS.INI to make sure the 3 Path configuration lines at the top all start with C:\EDIABAS (on my package one of them started with P:\ and that broke stuff).



CORRECTION: You will not need the adapter. That's only for cars produced prior to 3/2006 (i.e. before DCAN was introduced).



Hmm, not sure what's up with that. I've never seen that issue before; I just make sure the car is in full-on Ignition mode (i.e. pressing Start twice with Comfort Access or keyfob in slot and press Start without CA). Good luck though!

I used the ediabas version 7.2.0_Package_2.0 and it's seems to have worked fine. I successful coded "BC_DIGITAL_V" today and as far as I can tell all is well. I didn't experience any of that instrument cluster lights flashing, or windshield wipers wiping strangeness this time around. I hate not knowing what caused that strangeness to happen, but hopefully it doesn't happen again.

I would be remiss if I didn't say "thank you" to you, and a special thank you to forum member "srwatters" who graciously put up with my PM's all weekend. And to all the other forum members who have posted valuable information to the thread. And last but not atleast, the OP.

[AW128i]

I'm reading about the updated version(s) of EDIABAS and it's got me wondering if it's absolutely necessary or recommended to update it. My car is a '08 1-series.

[jphughan]

Originally Posted by AW128i

I'm reading about the updated version(s) of EDIABAS and it's got me wondering if it's absolutely necessary or recommended to update it. My car is a '08 1-series.

It's not necessary, but in my case with the older version I had to swap between two different versions of the ECU folder depending on which modules I was coding; some required an older one, some a newer one, and most worked with either. The new version lets me access all modules with the new one.

[quasitime]

Does anyone with an e90 know where the shadow codes are possibly stored?

I cleared my "Error Memory" and my triggered errors are no longer showing up there, which is one of the main reasons I got the cable, vs a BT Tool.

There's also "information memory" and "history memory". Are these possible areas for shadow codes? If so I can't read them... there's no option.

[creaminz]

So! Which cable is it??

Originally Posted by 1QuikWS6

We are all using this cable:

http://www.ebay.com/itm/BMW-INPA-Edi...item2569c47c64

Vendor name is 'Automotive-Tools'

Cables may look similar, but their quality and reliability is not...

Originally Posted by revlimit

Is this still the best cable to get?
http://www.one-stop-electronics.com/...&product_id=16

or This
http://www.ebay.com/itm/BMW-INPA-Edi...ht_3729wt_1398

[Bmw2007]

I have a 01/2007 328i(e92). Should I get a Kline cable or a Dcan cable. At this time I want to start with the diagnostics and then once i am more comfortable playing with the software move to coding.
I have chatted with different sellers on eBay and none of them gives me a firm response since my car falls on the cusp where BMW switched from Kline to scan.

[mr_milo]

Originally Posted by creaminz

So! Which cable is it??





or This
http://www.ebay.com/itm/BMW-INPA-Edi...ht_3729wt_1398

Either the first or second link are fine (actually the same cable and vendor). The third link is different, it looks like he stole the picture from one stop.

[EVO350]

Do you think you could code the standard "M-Button" features (on 2011.5 M3s and above) to a pre-2011.5 M3? It has been suggested in the past that adding 2MD to the vehicle order might do the trick.

[longhorn335]

Could somebody please give me some pointers to solve my problem? I still have the same issue described below. FZD module doesn't respond when accessed via BT tool. I hooked up another FZD module one I got on eBay and same result. Do I need to reset any other module ordo anything else to activate the module? Or is it supposed to work, plug-and-play?

thanks

Originally Posted by longhorn335

Just got my cable from automotive-tool. I am hoping this will help me resolve my problem with the control module. Brief summary of the problem:

I retrofitted the compass/homelink rear-view mirror last week. After finishing installation, seatbelt and airbag light indicators went off. Also the sunroof and lights do not work. Checked the connections of the module that's above the FZD (roof light cluster) and they are ok. Tried to clear code with BT Tool and failed. BT Tool did say it couldn't communicate with some modules.

Then took to dealership and they said the module was bad, repair would cost $1,000+. I politely declined.

(I am embarrassed to say that I did not disconnect car battery during mirror install. Perhaps that is the reason the module went bad, if in fact that is the problem).

My plan is to get the module (possibly from a junk yard, or getbmwparts if no luck) and install myself.

My question is: will I be able to code this module myself with the tools and software described in this thread?

Thanks very much in advance.

[jphughan]

Originally Posted by EVO350

Do you think you could code the standard "M-Button" features (on 2011.5 M3s and above) to a pre-2011.5 M3? It has been suggested in the past that adding 2MD to the vehicle order might do the trick.

It's not that easy, but Mike Benvo is working on it. Search for. Thread called E90/E92 Coding Possibilities.