[dbworld4k]

Originally Posted by rich123321

So people without an upgraded LSD would have no benefit from this coding?

Correct.

Originally Posted by lowside67

I suspect it will actually be worse than factory with this coding.

Mark

More than likely. If you disable the "E-Diff" programming on a stock differential, you now have a totally open differential without any electronic pseudo-torque vectoring across the rear axles. You will constantly have one wheel rotating faster than the other while cornering/sliding instead of the DSC braking the individual wheel. This would be shit.

[808AWD325xi]

Originally Posted by dbworld4k

EDIT: I read my car's DSC module and the file is actually MK60_87.C0F for my 2009 335i. The Brake Overheating Reduce Engine Power parameter is slightly different. Instead of aktiv or nicht_aktiv, it has options wert_00 and wert_02 coded into the car. I have attached a picture showing the descriptive values for wert_00 and wert_02 (they are the same effective hex values and descriptions), and a copy of the wert_01. You will see that wert_00 and wert_02 have N54 specific settings whereas wert_01 has no mention of N54. I am honestly unsure what to do from here as my guess is that wert_01 will still have E-Diff coding but set to the other BMW models listed...



I've set mine to wert_01 which has a data value of01, which is coincidentally the same data value used for various nicht_aktiv settings in other Datens. I'm thinking that data value of 01 just corresponds to Zero aka "off/noting" (wert_00 and wert_02 have data values of 00).

Alpina B3 parameters were adjusted in CDB file MK60_87.C0B at I-level E89X-08-09-500. The first public release of which was I-level E89X-08-09-515 (Progman 31.0). DSC_VARIANTE in CDB file KMBI_PL2.C08 was corrected for Alpina at I-level E89X-11-09-490. The first public release of which was I-level E89X-11-09-501 (SP Daten 43.0).

[...]
              Li 08-09-500               DSC  MK60_87.C0B [EFE91.X, j] E90,E92,E93: nur B3 Alpina Parameter angepasst
[...]
     11.04.11 So 11-09-490             KOMBI KMBI_PL2 C08 [EEL93.1,av] Steuerung fuer DSC_VARIANTE: Korrektur fuer Alpina angepasst
[...]

Perhaps altering the value of DSC_VARIANTE in KOMBI will have some impact on DSC functionality as well? Just a guess...

[brakthru]

Originally Posted by 808AWD325xi

Alpina B3 parameters were adjusted in CDB file MK60_87.C0B at I-level E89X-08-09-500. The first public release of which was I-level E89X-08-09-515 (Progman 31.0). DSC_VARIANTE in CDB file KMBI_PL2.C08 was corrected for Alpina at I-level E89X-11-09-490. The first public release of which was I-level E89X-11-09-501 (SP Daten 43.0).

[...]
              Li 08-09-500               DSC  MK60_87.C0B [EFE91.X, j] E90,E92,E93: nur B3 Alpina Parameter angepasst
[...]
     11.04.11 So 11-09-490             KOMBI KMBI_PL2 C08 [EEL93.1,av] Steuerung fuer DSC_VARIANTE: Korrektur fuer Alpina angepasst
[...]

Perhaps altering the value of DSC_VARIANTE in KOMBI will have some impact on DSC functionality as well? Just a guess...

I tried this but the only thing I noticed was the DSC symbol changed in the instrument panel. How did you get access to the Alpina info? I've been trying for months now to disable all traction intervention when DSC is completely off like it used to be before my software update. I'm on the latest I level as of July 2015. Car does not like to spin wheels anymore even with LSD. I wonder if DME is keeping wastegate open during WOT launches.

I tried disabling diff lock, changing over and understeer settings among other things and still can't stop boost reduction, braking and throttle closures with DSC fully off. Do you happen to have access to old datens say v35 and below? My original is v26.

[808AWD325xi]

Originally Posted by brakthru

I tried this but the only thing I noticed was the DSC symbol changed in the instrument panel. How did you get access to the Alpina info?

It's in the NAEL (New Release and Changes List) daten file (C:\NCSEXPER\DATEN\E89AEDOC.000).

Originally Posted by brakthru

Do you happen to have access to old datens say v35 and below? My original is v26.

No, I don't.

16.0-32.1 are from Progman. SP daten files overlap Progman at 32 & 32.1 and go on from there.

[paradoxical3]

Can someone please send me the TRC file from the DSC module from a 335i (not an xdrive, I already have that)?

I am trying to put together a comprehensive list of BMW's electronic nannies, what they do and how to code them off. I would like to be able to list each BMW model and what the exact parameters are for each different DSC module. Right now the info is too scattered and hard to find.

Here is what I have so far:

http://www.onelapx1.com/the-story/ho...w-actually-fun

[LMB335IS]

Originally Posted by paradoxical3

Can someone please send me the TRC file from the DSC module from a 335i (not an xdrive, I already have that)?

I am trying to put together a comprehensive list of BMW's electronic nannies, what they do and how to code them off. I would like to be able to list each BMW model and what the exact parameters are for each different DSC module. Right now the info is too scattered and hard to find.

Here is what I have so far:

http://www.onelapx1.com/the-story/ho...w-actually-fun

Pm me your email and I'll get you mine.

[808AWD325xi]

Originally Posted by paradoxical3

Can someone please send me the TRC file from the DSC module from a 335i (not an xdrive, I already have that)?

I am trying to put together a comprehensive list of BMW's electronic nannies, what they do and how to code them off. I would like to be able to list each BMW model and what the exact parameters are for each different DSC module. Right now the info is too scattered and hard to find.

Here is what I have so far:

http://www.onelapx1.com/the-story/ho...w-actually-fun

2009 335i

SZL
	wert_05
C0X_C8
	wert_02
C0F_AFH_HSA
	wert_01
C0F_AFS
	wert_00
C0F_ASC_AMR_STB
	wert_05
C0F_ASC_BMR_STB
	wert_04
C0F_ASL
	wert_00
C0F_BAUART
	wert_11
C0F_BB_RAB
	wert_01
C0F_BBV
	wert_00
C0F_BBV_KORR_VA
	wert_00
C0F_BERGAB_GERASTET
	wert_02
C0F_BERGAB_KENNEN
	wert_02
C0F_BERGABANSATZ
	wert_01
C0F_BTM
	wert_00
C0F_CBC
	wert_00
C0F_CF_ESM_HB
	wert_00
	wert_01
C0F_CF_ESM_LB
	wert_00
	wert_01
C0F_CR_ESM_HB
	wert_00
	wert_01
C0F_CR_ESM_LB
	wert_00
	wert_01
C0F_DBC_MIN_AUSLOESEDRUCK
	wert_00
C0F_DCC_C_AAT
	wert_01
C0F_DCC_C_ATT_SCHUB_AUS
	wert_01
C0F_DCC_C_ATT_SCHUB_EIN
	wert_01
C0F_DCC_DTC
	wert_00
C0F_DELTA_PSI_BETA_LIMIT
	wert_03
C0F_DF_DIR
	wert_00
	wert_01
C0F_DIFF_LOCK
	wert_02
C0F_DRUCKMODELL_HA
	wert_04
C0F_DRUCKMODELL_VA
	wert_05
C0F_ECBA_DCC
	wert_02
C0F_FBS
	wert_01
C0F_FLR
	wert_00
	wert_02
C0F_GETRIEBE
	wert_01
C0F_GMB
	wert_00
C0F_GMK_ECBA_HA
	wert_03
C0F_GMK_ECBA_VA
	wert_06
C0F_GMR_MAX_LIMIT_SCHRAEG
	wert_00
C0F_GMR_MIN_LIMIT_SCHRAEG
	wert_00
C0F_HSA
	wert_07
C0F_HSA_AFH_AFU
	wert_00
C0F_IPM_MAX_P_RES
	wert_01
C0F_KUEHLSCHACHT
	wert_00
	wert_01
C0F_LCL
	wert_00
C0F_LENKWINKELKENNLINIE
	wert_00
	wert_01
C0F_LF_ESM
	wert_00
	wert_01
C0F_LR_ESM
	wert_00
	wert_01
C0F_LUEFTER
	wert_00
C0F_LWK_X2
	wert_00
	wert_01
C0F_LWK_X3
	wert_00
	wert_01
C0F_LWK_X4
	wert_00
	wert_01
C0F_LWK_Y1
	wert_00
	wert_01
C0F_LWK_Y2
	wert_00
	wert_01
C0F_LWK_Y3
	wert_00
	wert_01
C0F_LWK_Y4
	wert_00
	wert_01
C0F_M_ESM
	wert_00
	wert_01
C0F_MIN_DRUCKAUFBAU_GRAD
	wert_00
C0F_MOTOR
	wert_07
C0F_MOTOR_LEISTUNG_MAX
	wert_09
C0F_MOTOR_SCHLEPP_P
	wert_02
C0F_PRE_MSR
	wert_00
C0F_PRE_USC
	wert_00
C0F_RPA
	wert_01
C0F_RPA_SCHWELLE
	wert_00
	wert_02
C0F_SC_X_ESM
	wert_00
	wert_01
C0F_SC_Y_ESM
	wert_00
	wert_01
C0F_SCHUBABSCHALTUNG
	wert_01
C0F_SDR_CTC
	wert_00
C0F_SETZ_V_MAX
	wert_02
C0F_SPURWEITE
	wert_00
	wert_01
C0F_SST
	wert_00
C0F_TB_BDD
	wert_01
C0F_THETA_ESM
	wert_00
	wert_01
C0F_UEBERSTEUERN_MUE_0
	wert_07
C0F_UEBERSTEUERN_MUE_1_2
	wert_07
C0F_UNTERSTEUERN_MUE_0
	wert_00
C0F_UNTERSTEUERN_MUE_1_2
	wert_00
C0F_UNTERSTEUERSCHWELLE
	wert_03
C0F_V_EINHEIT
	wert_01
C0F_VERZOEG_NEG_FEIN
	wert_01
C0F_VERZOEG_NEG_GROB
	wert_01
C0F_VERZOEG_POS_FEIN
	wert_01
C0F_VERZOEG_POS_GROB
	wert_01

[brakthru]

Originally Posted by paradoxical3

Can someone please send me the TRC file from the DSC module from a 335i (not an xdrive, I already have that)?

I am trying to put together a comprehensive list of BMW's electronic nannies, what they do and how to code them off. I would like to be able to list each BMW model and what the exact parameters are for each different DSC module. Right now the info is too scattered and hard to find.

Here is what I have so far:

http://www.onelapx1.com/the-story/ho...w-actually-fun

Not sure how to shrink the text down to size but here you go.


SZL
wert_05
C0A_AFS
wert_02
C0A_ASC_AMR_STB
wert_05
C0A_ASC_BMR_STB
wert_01
C0A_ASL
wert_01
C0A_BAUART
wert_12
C0A_BBV
wert_01
C0A_BBV_KORR_HA
wert_00
wert_01
C0A_BBV_KORR_VA
wert_00
wert_01
C0A_BERGAB_GERASTET
wert_01
C0A_BERGAB_KENNEN
wert_01
C0A_BERGABANSATZ
wert_02
C0A_BTM
wert_01
C0A_CBC
wert_01
C0A_DBC_MIN_AUSLOESEDRUCK
wert_01
C0A_DCC_C_AAT
wert_01
C0A_DCC_C_ATT_SCHUB_AUS
wert_02
C0A_DCC_C_ATT_SCHUB_EIN
wert_02
C0A_DELTA_PSI_BETA_LIMIT
wert_03
C0A_DF_DIR
wert_00
wert_02
C0A_DIFF_LOCK
wert_02
C0A_DRUCKMODELL_HA
wert_05
C0A_DRUCKMODELL_VA
wert_06
C0A_ECBA_DCC
wert_03
C0A_FLR
wert_02
C0A_GETRIEBE
wert_02
C0A_GMB
wert_01
C0A_GMK
wert_00
C0A_GMK_ECBA_HA
wert_05
C0A_GMK_ECBA_VA
wert_06
C0A_GMR_MAX_LIMIT_SCHRAEG
wert_01
C0A_GMR_MIN_LIMIT_SCHRAEG
wert_01
C0A_HSA
wert_01
C0A_HSA_AFH_AFU
wert_01
C0A_IPM_MAX_P_RES
wert_02
C0A_KUEHLSCHACHT
wert_00
wert_02
C0A_LCL
wert_01
C0A_LENKWINKELKENNLINIE
wert_00
wert_04
C0A_LUEFTER
wert_01
C0A_MIN_DRUCKAUFBAU_GRAD
wert_01
C0A_MOTOR
wert_07
C0A_MOTOR_LEISTUNG_MAX
wert_09
C0A_MOTOR_SCHLEPP_P
wert_01
C0A_PRE_MSR
wert_01
C0A_PRE_USC
wert_01
C0A_RPA
wert_01
C0A_RPA_SCHWELLE
wert_00
C0A_SCHUBABSCHALTUNG
wert_01
C0A_SDR_CTC
wert_01
C0A_SETZ_V_MAX
wert_03
C0A_UEBERSTEUERN_MUE_0
wert_02
C0A_UEBERSTEUERN_MUE_1_2
wert_09
C0A_UNTERSTEUERN_MUE_0
wert_01
C0A_UNTERSTEUERN_MUE_1_2
wert_01
C0A_UNTERSTEUERSCHWELLE
wert_04
C0A_V_EINHEIT
wert_02
C0A_VERZOEG_NEG_FEIN
wert_02
C0A_VERZOEG_NEG_GROB
wert_02
C0A_VERZOEG_POS_FEIN
wert_02
C0A_VERZOEG_POS_GROB
wert_02
C0A_WLC
wert_01
CF_ESM_HB
wert_01
CF_ESM_LB
wert_01
CR_ESM_HB
wert_01
CR_ESM_LB
wert_01
LF_ESM
wert_01
LR_ESM
wert_01
LWK_X2
wert_01
LWK_X3
wert_01
LWK_X4
wert_01
LWK_Y1
wert_01
LWK_Y2
wert_01
LWK_Y3
wert_01
LWK_Y4
wert_01
M_ESM
wert_01
SC_X_ESM
wert_01
SC_Y_ESM
wert_01
SPURWEITE
wert_01
THETA_ESM
wert_01
C09_C8
wert_02
C0B_AFH_HSA
wert_01
C0B_BB_RAB
wert_01
C0B_FBS
wert_01
C0B_SST
wert_01
C0B_TB_BDD
wert_01

[Bimmer-Bob]

Originally Posted by LMB335IS

Thanks for the help. Just read out my module and it's MK60_87 C0F. The functions are there, C0F_DIFF_LOCK and C0F_FLR but of course they're not simple "aktiv-nicht_aktiv" but wert values 00,01,02 for each. Time to dig more.

Originally Posted by dbworld4k

See my previous post. The wert_00 and wert_02 values have the same hex data value, but wert_01 is set to 01. Most other values like nicht_aktiv and other "off" functions also correspond to hex data of 01. I'm fairly certain that setting ours to wert_01 is the same as nicht_aktiv because of this. I set mine from wert_00 and wert_02 to wert_01. No errors or anything.

paradoxical3, could you send me your TRC file for your DSC module? I'd like to load it up in NCS Dummy and see what hex data values are there for your options of setting FLR/Diff_Lock to nicht_aktiv.

Did you guys ever figure this out definitively? Does wert_01 correspond to off?

I get confused when people talk about "hex data," from what I can tell my wert_02 (which is selected by default) has a hex data value of 01, while wert_00 and wert_01 have hex data values of 00. Huh? Isn't that the revers of yours? I'm running the same module (MK60_87.C0F) but could it be that the e-diff is already disabled by default on my 128i? Or am I misunderstanding something?

Also, if the different werts just correspond to either on or off, why didn't BMW just use the aktiv/nicht_aktiv format? Why have two versions of on and on of off? Or is there really a distinct difference between all 3 values, like degrees of e-diff activity?

[paradoxical3]

Originally Posted by Bimmer-Bob

Did you guys ever figure this out definitively? Does wert_01 correspond to off?

I get confused when people talk about "hex data," from what I can tell my wert_02 (which is selected by default) has a hex data value of 01, while wert_00 and wert_01 have hex data values of 00. Huh? Isn't that the revers of yours? I'm running the same module (MK60_87.C0F) but could it be that the e-diff is already disabled by default on my 128i? Or am I misunderstanding something?

Also, if the different werts just correspond to either on or off, why didn't BMW just use the aktiv/nicht_aktiv format? Why have two versions of on and on of off? Or is there really a distinct difference between all 3 values, like degrees of e-diff activity?

I will take a look at your trc file in a little bit here and see what I can come up with. If for some reason the 128i values are different I will be able to test it definitively in the spring, I have a friend I will be coding his ediff off on and he has a LSD so it will be obvious if it is working or not.

[dailowill]

Originally Posted by Bimmer-Bob

Did you guys ever figure this out definitively? Does wert_01 correspond to off?

I was playing around with NCSDummy today and checking out the options part of C0F_DIFF_LOCK. I noticed that wert_00 has the value of "E82+!(N43B20O0,N46B20O2,N47D20O0,N47D20T0,N47D20U 0,N51B30M0,N52B30M1,N52B30U1,N54B30U0,N55B30M0)" while wert_01 has the value of "E82+(N46B20O2,N43B20O0,N47D20U0,N47D20O0)". Maybe wert_00 is applicable to our n52 engines while wert_01 is applicable to different engines? This is just a guess since I just started using NCSExpert as of this morning...so take this with a grain of salt.

EDIT: When I check off wert_00, it also checks off wert_01

[dailowill]

As an update, I coded off my ediff on my 128i with values wert_00 and wert_01 and that seemed to have worked. I was able to slide the car without the e-diff/brakes kicking in. I need to do more testing though.

[Bimmer-Bob]

Originally Posted by dailowill

As an update, I coded off my ediff on my 128i with values wert_00 and wert_01 and that seemed to have worked. I was able to slide the car without the e-diff/brakes kicking in. I need to do more testing though.

Ok, so you had wert_02 selected by default, too? And when you selected wert_00 or wert_01, you're saying that both values were automatically selected? If that's the case, that sort of makes it easy, since there are only two possible configurations (either wert_02, or wert_00 and wert_01).

I normally just code in NCS Expert, altering my .TRC files manually, so I never would've figured this out. In fact, I didn't even know it was possible to have two values selected for a single parameter.

[dailowill]

Originally Posted by Bimmer-Bob

Ok, so you had wert_02 selected by default, too? And when you selected wert_00 or wert_01, you're saying that both values were automatically selected? If that's the case, that sort of makes it easy, since there are only two possible configurations (either wert_02, or wert_00 and wert_01).

I normally just code in NCS Expert, altering my .TRC files manually, so I never would've figured this out. In fact, I didn't even know it was possible to have two values selected for a single parameter.

That's correct! I didn't know either since it was the first thing I've ever coded with NCSExpert/NCSDummy, but looking at the trace file again, there are a few keys with multiple values.

[brakthru]

Originally Posted by Bimmer-Bob

Ok, so you had wert_02 selected by default, too? And when you selected wert_00 or wert_01, you're saying that both values were automatically selected? If that's the case, that sort of makes it easy, since there are only two possible configurations (either wert_02, or wert_00 and wert_01).

I normally just code in NCS Expert, altering my .TRC files manually, so I never would've figured this out. In fact, I didn't even know it was possible to have two values selected for a single parameter.

This is correct for me too on my N54. wert 00 and wert 01 both have the same hex value of 00 which is not active.

After much heart ache and pain, i finally figured out how to truly code off diff lock. I found out at least in my case it was impossible to code out diff lock with the DSC software update latest file from June 2015, SP daten v56. Even though i had coded out the diff lock function in NCS Expert, there was still a subfunction of DSC still operating and not totally unlocking the wheel. What a nightmare. I did some searching and found SP daten files v41 which are from 2011. 2011 was the last software update I had where DSC worked normally. I had multiple dealer updates in 2014 and 2015 in an attempt to fix problem. After re-flashing DSC with Winkfp and encoding with NCS Expert the 2011 files my car was back! Tons of power, wheel spin and drifting on tap now. No power cuts at all and no boost reduction. No feeling of the brake holding the inside wheel! The car feels unleashed, free and normal again. I have an LSD installed as well. Also, i had to recalibrate DSC/ABS pump valves with ISTA-D. I truly hopes this help someone. It took me over a year of to figure this out. Not even BMW knew what was going on. None of the dealers understood why my car was managing power and traction even with DSC completely off.

[Bimmer-Bob]

Originally Posted by brakthru

This is correct for me too on my N54. wert 00 and wert 02 both have the same hex value of 00 which is not active.

Are you sure about this? That would make sense, as my car defaults to wert_02 with a hex value of 01; wert_00 and wert_01 are both available with hex values of 00.

Someone in this thread previously mentioned that hex value 01 corresponded to nicht_aktiv, which is what was confusing me. Does anyone definitively know this stuff? Or are we all just guessing?

[brakthru]

Originally Posted by Bimmer-Bob

Are you sure about this? That would make sense, as my car defaults to wert_02 with a hex value of 01; wert_00 and wert_01 are both available with hex values of 00.

Someone in this thread previously mentioned that hex value 01 corresponded to nicht_aktiv, which is what was confusing me. Does anyone definitively know this stuff? Or are we all just guessing?

My bad. I meant wert 00 and wert 01 has the same hex value of 00. Wert 02 has a hex of 01 which means active in the case of diff lock. i corrected my previous statement.

[brakthru]

Originally Posted by brakthru

My bad. I meant wert 00 and wert 01 has the same hex value of 00. Wert 02 has a hex of 01 which means active in the case of diff lock. i corrected my previous statement.

Honestly, ive seen more cases where a hex value of 00 corresponds to not active. I rarely see hex 01 for not active but it does happen.

There are 2 ways to tell what the hex value represents.
1. Compare it to someones trace module who has nicht active or active and there respective hex values.
2. Code to each of these values and test them out for your self which is what i did along with researching how these things work in other modules. I was also able to compare modules values within NCS Dummy.

I also coded my own hex values on several features within the modules for real world testing such as torque reduction, oversteer and understeer. But this is before i solved my DSC problem. Im back to defaults now. Keep in mind these values already exist in the base programming of the module although NCS may only show 1 parameter to select (wert 01) with a hex value of 00 like my cornering brake control. NCS Dummy shows there are only 2 possible values the module can be assigned. 00 and 01 making it a simple on and off situation. So, i could easily add custom data and create a wert 02 or whatever i want to call it and assign a hex data of 00 to see how the car behaves. Its a little more difficult with oversteer because there are way more Mask(hex data) options that can be programmed in. Hope this helps.

[Neversatisfied1]

I'm sure glad I found this thread. I think this is the issue I'm encountering. I have a 2009 328 rwd nonsport 6mt that I just started taking to the track. About 15 minutes into a session it starts to cut power and the throttle is extremely laggy. It seems to activate after 2nd gear corners where I'm sure the car sees minor inside wheel spin. It also seems to kick in on 3rd gear sweepers that have some undulations that Has the inside tire spinning periodically through the corner. Or trail braking seems to activate it. If I chill out for a couple minutes, it goes back to normal, but will kick in again once I get back to hammering on it

No errors on the dash, I would think if coolant or oil was getting hot is get a warning? It's a n52 and holds 7qts of oil, this is not a tuned n55. 70 degree ambient yesterday at track. Has the feel of something I'm doing to piss off the computer and not something failing or overheating. If I pull back and run the car 8/10ths it never activates. Once I get in the 9.5/10ths of giving the car everything it's got, that's when it kicks in

I'm surprised how much fun this "girls" car is on the track for the first 15 minutes, but whatever it's doing had me wanting to put a "for sale" sign on it after yesterday at the track

I am trying to read up as much as I can about coding as this just has the feel of some BMW nanny.

Has anyone gotten to the bottom of how to turn all this stuff off?

I really did not want to become proficient in coding, but I may have to. Anyone near Pittsburgh I could bring the car to that knows how to turn this crap off?

[bNks334]

Originally Posted by Neversatisfied1

I'm sure glad I found this thread. I think this is the issue I'm encountering. I have a 2009 328 rwd nonsport 6mt that I just started taking to the track. About 15 minutes into a session it starts to cut power and the throttle is extremely laggy. It seems to activate after 2nd gear corners where I'm sure the car sees minor inside wheel spin. It also seems to kick in on 3rd gear sweepers that have some undulations that Has the inside tire spinning periodically through the corner. Or trail braking seems to activate it. If I chill out for a couple minutes, it goes back to normal, but will kick in again once I get back to hammering on it

No errors on the dash, I would think if coolant or oil was getting hot is get a warning? It's a n52 and holds 7qts of oil, this is not a tuned n55. 70 degree ambient yesterday at track. Has the feel of something I'm doing to piss off the computer and not something failing or overheating. If I pull back and run the car 8/10ths it never activates. Once I get in the 9.5/10ths of giving the car everything it's got, that's when it kicks in

I'm surprised how much fun this "girls" car is on the track for the first 15 minutes, but whatever it's doing had me wanting to put a "for sale" sign on it after yesterday at the track

I am trying to read up as much as I can about coding as this just has the feel of some BMW nanny.

Has anyone gotten to the bottom of how to turn all this stuff off?

I really did not want to become proficient in coding, but I may have to. Anyone near Pittsburgh I could bring the car to that knows how to turn this crap off?

Coding takes nothing more than a laptop, a $15 cable from amazon, and an NCSdummy/expert installation. It takes maybe 15 minutes to do the coding once you become familiar with the process.

Download this virtual machine: (http://www.e90post.com/forums/showthread.php?t=1220039). It comes pre-loaded with EVERY BMW tool you'll ever need. It is a huge file but it's well worth it since everything comes setup for you.

Read this thread (what causes limp): http://www.e90post.com/forums/showthread.php?t=412156

and read through this thread (what to code off and how/why): http://www.1addicts.com/forums/showt...hlight=nannies

I would get power cuts with my auto 128i on track after about 15 minutes. Turns out the DME was reducing power due to high brake temps (an estimated number based on driving conditions). No lights came up on the dash when this happened on track.

Once I coded that off I was able to really push the car. That is when I found out that the stock oil cooling was completely insufficient for using the car in this manner. Oil temps were hitting 290f. The DME pulls power in stages once oil temps begin to rise over 270f. You wont get a light on the dash until the car goes into full limp mode at around 300f. I have never had a water temp issue with the 128i (N51 and 2013 which comes with the V2 electronic water pump). I've never seen it above 99c.

I would log temps next time you go out. Look into retrofitting an oil cooler if you expect to keep driving the car hard.

[Levanime]

so, basically it was AX_Ref that so much people had been looking for, for so long
i guess its in X -s only?

[Neversatisfied1]

Originally Posted by bNks334

Coding takes nothing more than a laptop, a $15 cable from amazon, and an NCSdummy/expert installation. It takes maybe 15 minutes to do the coding once you become familiar with the process.

Download this virtual machine: (http://www.e90post.com/forums/showthread.php?t=1220039). It comes pre-loaded with EVERY BMW tool you'll ever need. It is a huge file but it's well worth it since everything comes setup for you.

Read this thread (what causes limp): http://www.e90post.com/forums/showthread.php?t=412156

and read through this thread (what to code off and how/why): http://www.1addicts.com/forums/showt...hlight=nannies

I would get power cuts with my auto 128i on track after about 15 minutes. Turns out the DME was reducing power due to high brake temps (an estimated number based on driving conditions). No lights came up on the dash when this happened on track.

Once I coded that off I was able to really push the car. That is when I found out that the stock oil cooling was completely insufficient for using the car in this manner. Oil temps were hitting 290f. The DME pulls power in stages once oil temps begin to rise over 270f. You wont get a light on the dash until the car goes into full limp mode at around 300f. I have never had a water temp issue with the 128i (N51 and 2013 which comes with the V2 electronic water pump). I've never seen it above 99c.

I would log temps next time you go out. Look into retrofitting an oil cooler if you expect to keep driving the car hard.

Thanks for all the advice. I downloaded all the software, the cable driver and my cable is on order.

Hopefully I can figure out how to find the right module and turn some of the brake and brake temp items off. I figure worst case I found some people on the website I can pay to code this stuff off remotely once my cable is here

Interesting you found oil temp an issue after turning off calculated brake temp. I have no idea how to trend this? I just never thought a 7qt sump and 200 whatever hp could overheat that much oil.

What did you do to trend and solve your oil temp issue in an N52?

THANK YOU FOR THE HELP!