[phil.harlow]

Hey Guys,

Here's a little walkthrough/augmentation to the existing docs out there to make it as easy as possible to get started with DIY coding. The steps below worked 100% for me with my 2011.5 E90 LCI 335xi, using Windows 7 on a Macbook air. I have zipped every needed file and uploaded them for you. Please read the ENTIRE post BEFORE starting. Trust me, you'll be glad you did. Links at the bottom.

WARNING!!! These steps require altering the computer in your $40k+ toy. If you are not 100% comfortable trying this, please hit your back button now. This guide is intended for people who have done a fair amount of reading into the coding process, and are completely understanding of the risks associated with coding your car. I’ve heard first hand stories about cars being bricked by not following the directions correctly or using outdated files. PROCEED WITH CAUTION!! Read, re-read, and then read again before trying. I accept no liability for anything that could go wrong. I offer this guide as appreciation for the work done by those before me who made it possible for me to recode my car. That said, it’s fairly straightforward once you’ve read enough. You can start with
http://www.e90post.com/forums/showthread.php?t=480261
http://www.e90post.com/forums/showthread.php?t=451145


The cable we used, and the ONLY cable confirmed to work is this one.
Ebay: BMW INPA / Ediabas K+DCAN USB Interface, D-CAN, CAN
http://cgi.ebay.com/ebaymotors/BMW-I...item25667c576d

Other cheaper cables could work, but I can make no guarantees. From what I understand the only cables that will work for ‘08+ are over $100.

This cable came with an adapter. I did not use the adapter on my ‘11.
Drivers: http://osefactory.com/tools/k+dcan/USB_Driver.rar (see pdf notes below for how/when to use)

I used a 2011 Macbook air with windows 7 x64 installed via bootcamp. I booted into windows 7, and downloaded and installed Windows XP Mode. Then everything else is done in the xp virtual machine.

Windows XP Mode - http://www.microsoft.com/windows/vir.../download.aspx

Then I followed xxxjecxxx's pdf. There are some tricky/ambiguous parts, so I have noted some of the steps below. Read the notes BEFORE and again as your progress through the pdf. Link below the notes.


Pdf Notes:

The first couple times running through this I think I had different language files, so I would get two error boxes popping up somewhere in the middle of this walkthrough that say something about the languages not matching with a yellow exclamation point. If these do pop up, they will pop up back to back and are normal and it's safe to close them and move past. (Sorry for the vagueness, I can't get them to come up anymore!!) If you get a different error, I would stop and ask for help.

Step 9b: For newer cables like the one above, there may only be an option to set the latency, which you want to set to 1. Also make sure it is com1.

Step 11. Connect the cable via USB first to preload the drivers. Then you can plug into the car. When you first connect the cable, windows 7 will recognize it and install drivers automagically. After that, select USB from the XP VM Window tool bar, and attach the k dcan cable. Now when windows xp sees it and wants drivers, select not this time, then install from specific location and point it to the folder where you've extracted the drivers from above.
(http://osefactory.com/tools/k+dcan/USB_Driver.rar)

Step 12. I have Comfort Access, so I still put the key in, but had to push the start/stop again, without ever touching the pedals, to get into the correct state, where the dash shows the key icon.

Step 13a. My ignition dot took a while to turn black but after waiting a bit I was good.

Steps 18-35. With this package, the profile is already made, which is named "FSW PSW MAN (mine)". Use this one and skip steps 18-35.

Step 36. Click File>Load Profil. Choose "FSW PSW MAN (mine)". I've read you can encounter problems if you don't clear out your FSW_PSW .TRC and .MAN files before each NCSExpert session so I would recommend doing that.

Step 53. As far as I know, always choose CAS here. This is not where you pick the module.

Step 54. IMPORTANT!! When running through this for the first time, stop here and backup your FSW_PSW.TRC file somewhere else, like the conveniently named backup folder in "Work". This will be your only way of fixing anything that goes wrong. This is extremely important.

Step 57. Choose KOMBI if you are actually doing the digital speedo. Otherwise see this spreadsheet and choose the appropriate module: https://docs.google.com/spreadsheet/...CPqY7sEC#gid=0
If you get an error here, stop and ask for help. Something is wrong.
After completing this step it's a good idea to back up your FSW_PSW.TRC file and place it in a folder named the current module you are editing, just in case you need to revert any changes you make.

Step 72. If this does not say perfect ended, stop here and ask for help. Something is wrong.

Step 73. Look at the "coding active" line and wait for "coding ended". Check your cluster for any error symbols, otherwise assuming everything worked, you're done! Just unplug the cable and the feature should be immediately active.

Fyi, for the window auto up through door open code, immediately after "coding ended" the windows wouldn't work at all, up/down, any window, nothing. Scared the crap out of me. But I took the key out, turned it off, put it back in and viola! It all worked again! including my new feature But boy that got my heart going!

Master zip file with everything needed. Includes:
NCSExpert 3.1.0
EDIABAS 7.2
INPA 5.0.1
v41 daten files
NCSExpert profile already made
xxxjecxxx's Pdf
http://www.philharlow.com/files/NCSE..._EDIABAS_7.zip

Or, if you want just xxxjecxxx's Pdf: http://rapidshare.com/files/429875523/NCS_DIY.pdf

Good luck!

[melloww22]

Thanks Phil for posting your instructions and sharing the Master Zip... saved me alot of time

[Peertwelve]

Nice work Phil. I just setup another vm using these instructions.. Worked perfectly

[jopa489]

Excellent guide, very nicely done!

[pc_boy]

Hi Phil.
I live East side and can drive to Bothell any time..Can you code my 2011 335 xi Sedan or let me borrow your cable? I ordered the cable from ebay and can't wait for 2/3 weeks for it to arrive from Honk-Kong.

Thanks,
Pavan.

[phil.harlow]

Hi Pavan,

Unfortunately the cable I used was borrowed from another forum member. You could ask around and see if anyone has one you can borrow or just hold out for yours from Hong Kong.

Also, could you rate the walk through a little higher? I doubt you actually thought it was a 1 out of 5. Hopefully other members can use it too.

Good luck!

Phil

Originally Posted by pc_boy

Hi Phil.
I live East side and can drive to Bothell any time..Can you code my 2011 335 xi Sedan or let me borrow your cable? I ordered the cable from ebay and can't wait for 2/3 weeks for it to arrive from Honk-Kong.

Thanks,
Pavan.

[Elliott@DetailAddict]

Step 54 note is incorrect.
Correct way is to code the module in Expert Mode to return to defaults.

[sandman0615]

i think the master zip link is dead. reupload? how big is the zip

[hsleiman]

Originally Posted by sandman0615

i think the master zip link is dead. reupload? how big is the zip

It's working for me. 160MB it's about an hour download for me from megaupload.

[Yvette]

what is supposed to mean by
clear out FSW_PSW .TRC and .MAN files?

Step 36. Click File>Load Profil. Choose "FSW PSW MAN (mine)". I've read you can encounter problems if you don't clear out your FSW_PSW .TRC and .MAN files before each NCSExpert session so I would recommend doing that.

[Yvette]

Originally Posted by Grant@DetailAddict

Step 54 note is incorrect.
Correct way is to code the module in Expert Mode to return to defaults.

so you recommend not to skip the steps?
start with expert mode and create FSW_PSW . MAN file?

[phil.harlow]

Link seems to be good to me too.

@e90sexion
what is supposed to mean by
clear out FSW_PSW .TRC and .MAN files?

Clearing them out is just opening them with notepad, deleting the text inside, then saving.

Grant@DetailAddict's comment is extremely vague, but I think he means that if something did go wrong, there is a different way of reverting back to defaults. I would copy the FSW_PSW.TRC file to another folder like I suggest, that way if something does go wrong, you can try either way.

[Peertwelve]

Originally Posted by phil.harlow

Link seems to be good to me too.

@e90sexion
what is supposed to mean by
clear out FSW_PSW .TRC and .MAN files?

Clearing them out is just opening them with notepad, deleting the text inside, then saving.

Grant@DetailAddict's comment is extremely vague, but I think he means that if something did go wrong, there is a different way of reverting back to defaults. I would copy the FSW_PSW.TRC file to another folder like I suggest, that way if something does go wrong, you can try either way.

Grant means that to unwind a bad coding session, do not revert back to a backup .man file and instead load the Expertmode NCS profile and recode the module. It will reset the default values to the selected module. Grant is a BMW coding stud muffin

[Virterm]

Originally Posted by Peertwelve

Grant means that to unwind a bad coding session, do not revert back to a backup .man file and instead load the Expertmode NCS profile and recode the module. It will reset the default values to the selected module. Grant is a BMW coding stud muffin

So, basically the instruction #54 is correct, only in case of any trouble the recovery procedure should be different?

[Peertwelve]

Originally Posted by Virterm

So, basically the instruction #54 is correct, only in case of any trouble the recovery procedure should be different?

I am not sure of the value of step 54. The preferred way to reset any coding errors is to use expert mode per Grants response. I take a backup anyway, but I have yet to refer to

[arc1880]

For Step 9b: "For newer cables like the one above, there only be an option to set the latency, which you want to set to 1. Also make sure it is com1."

Where is the latency setting? I don't see it when I follow the entirety of step 9.

[Peertwelve]

Originally Posted by arc1880

For Step 9b: "For newer cables like the one above, there only be an option to set the latency, which you want to set to 1. Also make sure it is com1."

Where is the latency setting? I don't see it when I follow the entirety of step 9.

Do you have the USB version or the serial version of the cable? The recommended cable is USB. 99% of the current information is on the recommended cable. I have never used the serial port version so i can't help to troubleshoot it. good luck!

[arc1880]

Just to add a few updates to this writeup from my experience:

Step 9) in the PDF should really be replaced with the following notes from Phil with the cable mentioned because at this point you have not setup the drivers for the cable in Windows 7 and in the XP Virtual Machine.

Step 11. Connect the cable via USB first to preload the drivers. Then you can plug into the car. When you first connect the cable, windows 7 will recognize it and install drivers automagically. After that, select USB from the XP VM Window tool bar, and attach the k dcan cable. Now when windows xp sees it and wants drivers, select not this time, then install from specific location and point it to the folder where you've extracted the drivers from above.
(http://osefactory.com/tools/k+dcan/USB_Driver.rar)

From my experience, during the installation of the drivers in the XP VM, I was prompted twice to install the USB Serial Port as well as the USB Serial Converter.

After installing the proper drivers in the XP VM, you can start up the Device Manager. Select Ports and you should see USB Serial Port (COMx). You need to change the USB Serial Port to use COM1. In order to do so, you will have to change Communications Port (COM1) to use another COM. So select the Communications Port (COM1) and go to its properties. Select the Port Settings tab and click on the Advanced button. Here, you can select a different COM port under the COM Port Number dropdown list. Click OK, then OK. Now go to the properties of the USB Serial Port (COMx). Select the Port Settings tab and click on Advanced. Change the COM Port Number to use COM1. Then find the Latency Timer (msec) dropdown and select 1. Click OK, then OK.

You can then proceed to the next step.

HINTS: If you want to speed up your Virtual Machine, make sure you enable Integration Features. Even though I had Integration Features enabled in my XP VM it was still really slow. I did some searching and found that there is an xml file that you can edit to help improve your VM. First, make sure you shut down all VMs. Then navigate to the following directory: C:\Users\<your user profile>\AppData\Local\Microsoft\Windows Virtual PC\Options.xml

I added the following item in bold:

<virtual_machines>
<enable_idle_thread type="boolean">true</enable_idle_thread>
<power>
<mm_timer_duration type="integer">16</mm_timer_duration>
</power>
</virtual_machines>

[Yvette]

master zip nice

[plotino]

Can some one please repost the master zip file?
thanks

[phil.harlow]

Put it up on my site so the link won't die anymore:

http://www.philharlow.com/files/NCSE..._EDIABAS_7.zip

Originally Posted by plotino

Can some one please repost the master zip file?
thanks

[Treize]

I'm getting a "versions mismatch" and "languages mismatch" error when I try to do the airbag test. I'm currently using windows xp 32-bit, will this problem go away if I updgrade to windows 7 32 bit? It's a 2009 335i coupe. Followed the pdf exactly. Thanks in advance!

Edit: I also noticed the "Version.txt" file in EDIABAS says 6.4.7 while the original post says it should be 7.2