Okay, I recently traded in my 2009 MCS and brought home a new 2012 Clubman. I figured I'd go do some coding and I had great luck with everything that I wanted to do until I got to the KOMBI module.

The Clubman now thinks it's a Cabrio with a defective top...

I saved the KOMBI .TRC file before writing it back to the module but writing the original file back didn't help.

I've got an appointment at the dealership to get it recoded on Friday but I sure would like to figure out why that module is so different.

Anyone else coding on a 2012 model yet?

 

Hey guys, I am new to these forums, but been an avid BMW programmer.
Myself and TerraPhantm from M3forum.net did a bunch of Programming on E46 M3's (I used to own one, went from the M3 to the Mini... lol) Myself and TerraPhantm were the first ones to get the "One Touch Rear Vent's" option working, the "M Track Mode" working, Uploading OE BMW software to update Euro Engine DME and SMG CSL Software.

I am now trying to code the mini and have no idea what I'm doing lol.
The module style seems to change (No CKM, just CAS) but the basic coding functions are the same. Just not sure what is actually available.

Could I get access to the spread sheet? I think once I get a general grasp of how the newer modules work, I'll be able to find some things out.

Thanks Guys!

 

Which Daten files do you need for the 2009 R56?

 

I used the v34 datens for my 09 R56.

 

Fantastic.
I have v39 from the E46 days.

 

North American Motoring spreadsheet: https://docs.google.com/spreadsheet/...hl=en_US#gid=0

BMW Coding.com Spreadsheet: https://docs.google.com/spreadsheet/...hl=en_US#gid=0

BMW E9x Spreadsheet: https://docs.google.com/spreadsheet/...hl=en_US#gid=0

 

Thanks TheCheatOSX I was gonna do the same thing

 

After changing the config, can the entire file be saved in case MINI flashes the box and wipes out all the previous changes?

 

You don't want to do that. You only want to keep track of the particular options you change. Because when a new firmware version goes on options get changed and added. It could really goof up the functioning of the module if you apply a different version of a trace file.

 

I just picked up my 08 MCS after having the cold start rattle fixed. I was coding in the kombi module, and now it thinks it is a coupe with the trunk open and the gas gauge doesn't work. The trunk open error never goes away, so I can't see any of the stalk activated menus. I have reset every module I can, but the error remains. Any idea how to make it think it is a hardtop again?

 

Check the vehicle order stored in the CAS and FRM modules. The model code should read MF73 for a 08 MCS hardtop, MS33 for a MCS cabrio (R57). If it is wrong, then change the VO and FA_WRITE or FA_SCHREIBEN to both CAS and FRM modules. Then you should recode all the modules back to default (blank file).

Keep in mind, the hardtop model was also named coupe by BMW engineering before the true coupe project started...

 

Juppers, As alexs3d2 stated, double-check the model in the VO. You can find the VO string in the FA.txt (I think that's what it was called) in the NCS Work directory.

Try to reset your KOMBI back to default.

1. Go into the profile editor and turn off trace file manipulation. Password to edit the profile is repxet
2. Then hit the Process CPU button (when you have the KOMBI selected).

Should take just a few seconds, but any changes you have made should be corrected and you will back to normal. Somehow you fed the module bad information in your coding attempt, either some settings got changed inadvertently or you ended up with the wrong coding level.

I have done this process a few times and what it does it "defaults" the module back to a factory defined state based on the vehicle order string. It has always worked for me.

 

I have already defaulted all the modules that I can read. Haven't had a chance to verify the VO string, but it is scary that it may have somehow changed itself.

The car runs, but no tach and no gas gauge. Definately seems like something wonky in kombi, but I have defaulted it several times with no change. The image below is why I said it thinks it is a coupe. See the weird trunk icon that won't go away.

 

Oh boy. That's probably the alert for the spoiler of the coupé. Do you have your original trace backup? Program that in if you have it.

 

Strobeyprobey what you are saying is that you can make an backup of the original config prior to modifying? Just In Case!

 

I have an 08, I can send you my file. But I don't have as S model.

And yes, the trace file you first pulled from your kombi is your original backup. That file should should be copied to a different location. And that entire file can be copied into the. Man file and programmed into the kombi to restore it to default.

 

I do have a backup of my kombi trace from before I took it to the dealer. But that was on the older firmware. I don't have a copy from the new firmware. I guess that is a start. I will pull a trace and compare the 2 to see if I can find any differences.

 

Excellent yeah compare the files! So the dealer updated your car?

So don't install your original file just yet.

 

Oh but you should be able to take the original trace file pulled after the dealer update and copy the entire contents to the .man file and install that.

 

Yeah. The paperwork says they updated to the latest programming when changing out the timing chain. Old was R056-10-03-503 and new is R056-11-07-511.

 

If I managed to keep that one. Which I didn't. :(

 

Darn that's so new. You maybe running into an issue because of that newness. Try to get the v43 datens for the r56. And even those are may not be new enough.

 

I'll check the version number you listed... I don't think there was any update for the R56 after v41 but I may be mistaken. You can get the v41 for R56 at BMWcoding.

And it is true, if you code the module with an older version than the one you have installed you get such results. It happened to me when I updated my IHKA (ac) with WinKFP and the auto recirculation would not work as NCS Expert was still using the older files. This is probably what happenned here: Your NCS is using older DATENs...

 

So I still don't understand why the Kombi won't wont default. have you tried coding a blank .man file to the Kombi ?

 

Because he probably uses a lower index file in NCSExpert than the one in his car. The default values are not stored in the unit itself, but are determined by NCSExpert based on the coding index and the VO. NCS interperts the man files, and based on the index file used changes the appropriate hex offsets. But with newer version software, the offsets often change address so you need a newer index file to address them, otherwise you are changing the wrong offset.

PS: Try to use v41 Datens, as they appear to include indexes for the newer R58/59 models.