Okay - this could be difficult to resolve. The problem is that the wiring of your X14272 connector appears to be different from an R56. The picture in your thread earlier shows a wire in terminal 13. This location and colour code corresponds to the parking brake switch - this is good. The problem is you don't appear to have a wire in terminal 14 right next to it - this is bad.

Are you sure you actually have the DSC On/Off button? (Don't mean to be rude - but just checking).

If you do have the button and given that you have an R60, my suspicion is that the wiring of this connector has changed. This will be a real problem because (to my knowledge) there is no publicly available version of the MINI WDS (Wiring Diagram System) for the R60.

So, not only might your DSC button be in a different location in this (or another!) connector, but so might the Sport button input be different! At this point, without knowing for sure I definitely would not recommend connecting anything to your X14272 terminal 19. Who knows what it might be for on your vehicle! And those other twisted-pair yellow wires on X14272 are possibly for various CAN bus connections - you definitely don't want to be playing around with those!

Sorry - but I think you are stuck until we know more about the Countryman wiring.

 

so, i've the DSC button on the R60 Coopper S it have as standard also the ASC+T... i can confirm you that the wire on the pin 13 is the parking brake light switch. The cable in the pin 7 is the power steer.

Unplugging the connector i get a central unit fault.. In this way all the switches (expect the rear windows block) are OFF, with them also the joystick for the Visual Boost... That's all i discovered... I reached to see the wires coming out from the central swicth panel and it seems that none of them goes there to X14272... But if i unplug the connector, nothing works... mha!

 

can you send me the V32 daten

 

Yes, you will get a system fault indication when you unplug X14272 (it scared me the first time too!) - but it will clear when you plug the connector back in (as you've probably found).

In an R56 at least, the functions of the other wires in X14272 are:
Terminals 1 & 2 - D-CAN bus (OBD-II diagnostic connector)
Terminals 3 & 4 - PT-CAN bus (Powertrain communications)
Terminals 5 & 6 - K-CAN bus (Body communications)
Terminal 7 - 15WUP - Terminal 15 wakeup

All of the above are critically important to your vehicle's computer system - don't touch ANY of them.

Again, even if you do find where the wire from your button goes, we don't know for a fact that terminal 19 is the Sport button input (it PROBABLY is - but we don't know for sure).

So, proceed at your own risk until the R60 WDS is found.

 

This makes sense.... Who knows where are all the other plugs.... Do you know if the plug for the DSC+ASC is another location?

Is there any kind soul that will take a picture of his X14272 connector on the R60 cooper S (possibly with the sport button on) ??

 

thanks so far, still 1 error.....

when it is coding there is an error pop up, the mpg stats works now....but sport is still not yet enable....

it stuck at the EPS...

please help

 

i am using the v32 to code.....it is not in the ECU folder....i think it's missing the eps_r56.prg.....

can i just copy from the later daten into it or change all folder to new daten now? i was using the v32 to fix the FRM VO issue.

Now it's the last bit of coding into CAS...

please help

 

thanks everyone, i passed the EPS by copying the one from V38 file and I stuck at the RAD1.prg one, it got the same error. However, when i fired up the car and hit the button......YEAHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH HHHHHHHHHHHH....Sport is ON, it is just like another car.....throttle, shift point, shift delay has been much improved.....

As a result....it didn't matter for the rest of the module, they are default as before...so i guess i don't need to go thru again.....

however, i tried to READ the CAS after the test drive, the TRC file is not as the same as before, it only got 8K, without sport and comp in there...

Does it suppose to load the current CAS TRC???? strange.....

 

Now that i think, when i did the mod on my friend R56 we had the same error... But when we turned on the car it was working perfectly

 

Hello everybody.

I need some help :-)

I've coded the CAS and the FRM modules following your guide (if I read the option in both of them I can see $4UF option present); I've changed the pin (yellow cable) from 14 to 19 on the X14272 terminal but nothing happens. Do I need to do something more ? (obv. dsc button does not work anymore).

I do not clearly understand, I did also this:

once you've created your empty FSW_PSW.MAN file, fire up NCS Expert and perform the following steps:After a minute or so, NCS Expert should be done. If the "Process Car" option is too scary for you (it was for me the first time!), you can process each module separately.

But nothing happens (process does not even start).

Do I need to modify

FACTOR_SERVO_SPORT
wert_01

SPORT_SWITCH
nicht_aktiv

VEHICLE_VARIANT_SPORT
variant_sport_3

SPORT_TASTER
nicht_aktiv

SPORT_ANZEIGEDAUER
wert_01

SPORT_FUNKTION_SZM
nicht_aktiv

SPORT_TASTER_C05
nicht_aktiv_invalid

in the FSW_PSW.TRC and then copy to the FSW_PSW.MAN (like NCS_CHANGING_THE_VEHICLE_ORDER pdf says?)

I've added the Close Windows/Roof from Fob without any problem but with the sport button I can not get it


Thanks for replying.

R

 

hi rolant, got busy lately....

it is missing a step, you have to hit EXECUTE JOB(I think it's F2), then it will set everything up automatically. you will see the progress as well. NO NEED to modify the code separately..

good luck

happy driving with sport on...........

 

this is my screen before I press F3 (like Chernobyl's instruction).
If I press F3 nothing happens.

When have I to press the F2 execute job in the Chernobyl's steps?

thank you very much for your reply.

 

As I remember, f2 is the last step after f3

 

I don't understand what I'm doing wrong...here's a video of the procedure I follow (the first part is to show that the $4UF option is in CAS and FRM list):

http://youtu.be/oPDBMYmg7zM

As you can see there's no F2 clickable at the end of the procedure, no execute job, just F3, but nothing happens even with F3..
Suggestions?

 

F1 - code car.

 

It works. Thank you all. :-)

(same error like you all but everything works fine)

 

I managed to encode the sport button but I have a simple problem.
To prove it I decided to use the wires of the star / stop (black and purple) and unfortunately now I do not remember what position they were in the connector x14272.

some of you know which pins are inserted in the black and the purple of the start / stop?

 

Found the solution to this:

in the FRM set the following:


Also, you may have to make settings as well or customize to your liking.
BL_2 is the side marker lights. BL_1 was the lower brake (bright) bulb. KZL is the plate lights, and I didn't try the others.

You can turn this on and off via your BC. Basically this is replicating the Angle Eye DRL running lights that are on the new E90s.

 

Hi all, I try to retrofit the sport button on my 2007 German country coded MCS.

I started out with v32 ecu files + v41 daten and sgdat files.
I was able to change the VO in both CAS and FRM, ending with "process ECU". If I now connect the car, it shows $4UF just fine. I also changed pin 14 to pin 19. Result, no sport button active..

Then I tried "Process car", but that failed first on "ESP" - fixed with some v41 ecu files. At this moment, it fails on MULF (tested with v32,v38,v41 ecu files). Eventually I ended up trying to process each ECU, one by one. MULF and SZL are the 2 that fail.. So at the end, still no sport button..

I'm also looking for a trace file from a 2007 cooper S with factory bluetooth and usb, preferably european as I expect some differences(?).
I have bluetooth but not usb, I'm trying to retrofit that as well.

edit - my fa/vo: R56_#0307&T8E1%0A25*MF71$1CA$210$249$255$2PA$2RP$3 13$314$345$346$359$381$3AB$423$428$431$441$450$473 $481$493$494$4A7$4AU$4BF$4UF$520$521$522$534$548$5 50$563$5AA$5DD$609$644$736$785$851$863$872$879$896-B070-EWS4

 

Hi - first thanks for this great topic!

I try to code my german 2007 MCS to get the sport button, but up till now no success.
I started with v32 ecu files and V41 daten+sgdat files. Changing the VO in CAS and FRM modules workes fine, ending the process with "process ecu" with an empty MAN file.
As this didn't activate the sport button, I tried to do all modules with "process car" and an empty MAN file. This keeps failing on MULF (no answer from ECU).
Eventually, I ended up doing all the modules with "process ecu" - only MULF and SZL are failing.
I also tested to take v38 an v41 ecu files, no success.
And before you ask, yes I changed pin 14 (dsc) to pin 19.

Any help is welcome!

My FA/VO: R56_#0307&T8E1%0A25*MF71$1CA$210$249$255$2PA$2RP$3 13$314$345$346$359$381$3AB$423$428$431$441$450$473 $481$493$494$4A7$4AU$4BF$4UF$520$521$522$534$548$5 50$563$5AA$5DD$609$644$736$785$851$863$872$879$896-B070-EWS4

 

@MCSR56:

I don't have any immediate explanations of why this isn't working for you. I can say that the problems with accessing the MULF (Bluetooth) module are normal - the version of NCS Expert available to us is unable to communicate with that module. You should be able to access the SZL module, but in this case it doesn't matter - it has no part in the Sport mode and so doesn't need to be recoded.

You wrote that you had problems with the "ESP" module - I assume you meant "EPS" (electric power steering). This one definitely needs to get coded to activate the tighter steering response in Sport mode. But it looks like you got it in the end.

I haven't bothered to track down all of the changes that adding $4UF makes, but I believe the settings below are the key ones. Try reading each of the modules below and see if the correct settings are showing up. If they aren't, you can try changing them manually.

[SPEG]
SPORT_TASTER
aktiv

[EPS]
SPORT_SWITCH
aktiv

[KOMBI]
SPORT_ANZEIGEDAUER
wert_02

If these are all set correctly, then you might want to see if your "Sport" button really is connected to the right terminal. The easiest way to do this is to use INPA; it has a function that allows you to see the status of inputs (i.e. it reports in real-time whether the Sport button input is pressed or not). I don't remember the exact choices to get to this screen - if you need help let me know and I'll try it on my car to remind myself.

 

Can you confirm exactly what you mean by this? Are you referring to the ability to have ONLY the city lights (top half of the fog lamps) and NOT the xenons on as daytime running lights? Will the xenons still come on automatically when it gets dark? What function exactly are you able to turn on/off with the BC control - the auto city lights or the auto xenons?

If this does what I think it does, it is a bit of a holy grail for a number of people - if so, we should move this to a new thread so that more people are aware of it.

I'm too lazy to try it on my car right now (too cold out!) - but if this works I'll definitely make the change (to reduce wear and tear on the xenons!).

 

@Chernobyl

Thanks for your reply. Meanwhile, I managed to get everything working!

Has anyone tried to add the start/stop function as well?

Besides that, I'm trying to add USB to my car.

First option:
My car came with AUX-in and bluetooth (S644A).
My guess is that I only need to add $6NDA or $6FLA to the VO and order the usb interface + cable cable (part nr 61119202728) and the USB/Aux-in Jack (part nr 61319129651). The car already has the expensive charging base from the bluetooth.
I prefer the OEM retrofits, but I guess this means trouble? :


Second option:
I still have a Dension Gateway 500 for BMW lying around. I guess I can install it in the Mini by coding in the CD Changer (or CD Changer prep). Has anyone coded this without the CDC actually being present?

 

Yes! The ONLY lights that come on are the two city lights in the front of the car.

No dash lights, no side markers, no Xenons, no taillights (however you can also enable the rear brake lights with the DRL if you desire).

The BoardComputer settings allow you to turn DRL off or on. From the factory this setting basically was just like turning the headlight stalk switch to ON. Now turning that BC setting on or off just turns my front city lights on or off respectively.

If you have the AUTO light switch set the HIDs/halogens and the rest of the lights will come on like normal (I don't have the the AUTO light feature).


I added the code to the spreadsheet. And yeah, I love the look of the city lights (I just got done physically adding them to my Z3) and hate having the HID lights fire up every time I start the car so I never used the DRL setting. But now that I finally found the settings to do this, I may try to find a super-bright LED multi-watt LED bulb to pop into that spot (of course I would have to turn off the bulb checks then in the FRM).

 

I would try it if I had the manual tranny. But the models with auto start/stop have a heavier-duty starter motor so I can't recommend this setting without risking wearing out your starter.

That may work, but not being able to read the MULF from NCS will make it so the updated VO (adding USB) won't get coded into the MULF (basically enabling the USB port settings in the trace file). Unless you have an OPPS (optical) connection to code the ULF I think you maybe out of luck.


May RAD2 just showed a dash when it couldn't read my IBOC module I coded in. You can easily test it by changing CDC to aktiv in your head unit.