Customizable traction control settings

[JohnDaviz]

My wish is to have the traction control more loose as it is yet. I am driving the car on the nordschleife and by now i am not skilled/brave enough to turn it completely off. I thought by going to a higher level the TC would let me to have the rear end more loose. This is how i understand lvl 1-6.

 

[RSL]

1-6 is drive logic levels for the trans and I'm not aware of any modifications to the DSC from it. AFAIK, the only way to change the partial DTC/MDM DSC characterisitcs is through coding/programming.

 

[aus335iguy]

Easiest way I know is to change the non m DSC friction coefficient values to M values using nettodat coding. There’s nothing really special about MDM other than that.

 

[JohnDaviz]

Easiest way I know is to change the non m DSC friction coefficient values to M values using nettodat coding. There’s nothing really special about MDM other than that.

can you describe this in more detail so an idiot like me understands?

 

[aus335iguy]

can you describe this in more detail so an idiot like me understands?

DSC off is DSC off
DTC = MDM it’s just that DTC has different calibration

There are numerical values in the DSC for DTC that can be changed so that DTC feels like MDM….EXACTLY LIKE MDM

In this thread it describes the concept and nettodat coding you’d need

Pete's toy with a licence plate - E92 335i Build Thread

Pete's toy with a licence plate - E92 335i Build Thread - Page 3

www.e90post.com

The process for making the change has not been written however it’s not very different from any other nettodat coding change and just requires knowing which values to change which can be found elsewhere on the internet
They are called friction coefficients and the GTS values are known

The reason most like me want the M DSC regardless is the M mode button functionality
Pressing it on a non m DSC does nothing unless you go with an arduino can bus intercept

 

[carabuser]

DSC off is DSC off
DTC = MDM it’s just that DTC has different calibration

There are numerical values in the DSC for DTC that can be changed so that DTC feels like MDM….EXACTLY LIKE MDM

In this thread it describes the concept and nettodat coding you’d need

Pete's toy with a licence plate - E92 335i Build Thread

Pete's toy with a licence plate - E92 335i Build Thread - Page 3

www.e90post.com

The process for making the change has not been written however it’s not very different from any other nettodat coding change and just requires knowing which values to change which can be found elsewhere on the internet
They are called friction coefficients and the GTS values are known

The reason most like me want the M DSC regardless is the M mode button functionality
Pressing it on a non m DSC does nothing unless you go with an arduino can bus intercept

Is there any more details on changing the friction coefficients? Is it just 1 value or are there multiple settings for wheel slip and lateral movement?

I'll read my DSC module and compare the Z4 to the 335i. Would be interested to see what the M3 GTS uses.

 

[aus335iguy]

From what I recall there’s more than one that needs changing but I need to find the site where I found the info

 

[JohnDaviz]

Thanks for the Link. I think Post #49 describes probably what i am looking for.

The solution to above, is to flash the 1M DSC software, and then code the NETTODAT file with the data from the M3 GTS Coupe.

If i understand correctly i will have a working button without re-wiring and by coding the GTS values over Nettodat i will get a less intrusive TC

 

[aus335iguy]

Discussion and details on Euro M3 MDM and GTS coefficients here

Euro MDM Coefficient of Friction

Euro MDM Coefficient of Friction

www.m3post.com

 

[aus335iguy]

Here is a trace file from a 135
Similar coefficients are mentioned on page 4

In other words I don’t think you need to even flash to 1M

 

[aus335iguy]

So for those that want to see the trace files M3 trace first and x35 second

 

[aus335iguy]

For those that don’t know nettodat coding
Essentially what you’re doing is changing or creating a the values that doesn’t exist/isn’t available and then coding that module once you’ve created it
It’s described in other guides
The one that I’ve used in the past was video in motion where you set a new speed rating when VIM gets switched off to bypass it
You create a new wert 6 value of 255kmh and then once applied to the daten file you then code the module with that wert 6 active and viola! No video in motion

 

[JohnDaviz]

So for those that want to see the trace files M3 trace first and x35 second

May be @doublespaces extracts the posts about this topic to a seperate one where we can continue talking without being offtopic actually

I will definitly check this process and learn about it to actually achieve something like the guy posted about his experience with Wert=07

Great information! How do i figure if the values behind the Wert are equal between M3 and x35?

 

[aus335iguy]

May be @doublespaces extracts the posts about this topic to a seperate one where we can continue talking without being offtopic actually

I will definitly check this process and learn about it to actually achieve something like the guy posted about his experience with Wert=07

Great information! How do i figure if the values behind the Wert are equal between M3 and x35?

I think if you use NCS dummy you can look up the actual values as part of the nettodat code
Look up video in motion coding in NCS expert and you’ll see the kmh values. I’m not sure about the hex values but I’d say it’s in there somewhere
You don’t need to be connected to a car to find them you just need the corect module and datum

 

[RSL]

Wert_nn and active/not active are essentially like option #. What matters are the hex values assigned to the options, not the option number itself. NETTODAT will pull the actual hex rather than the wert, so you can see/modify it directly.

Not all keywords are defined in all daten files, but most that aren't seem to cross/be similar. Unoccupied means a value is there, but the keyword isn't defined to say what it is.

Some of the first 8 bits of 30000A seem to be different functions between M and non-M. Either that, they or have different names for the same functions, which would mean "M dynamic" is active front steering?

I just picked ones that were in a range or obvious, like over/under steer coefficients and threshold. I don't know what the yaw torque compensations actually do. Sometimes, just figuring out what the functions are is the hardest part.

 

[JohnDaviz]

thank you for the idea looking directly into NCS

I opened NCS Dummy and checked the oversteer (uebersteuern) values.

Different to the M3 Post i see other values under the different "wert" (value) cells for the MK60_M3_C08

Under Uebersteuern_MUE_0 there is no unit described
Under Uebersteuern_MUE_1_2 i took the values where the unit is described with "m/s²" (meter per second squared)

MK60_M3_C08 (NCS Dummy)				MK60_M3_C08 (M3Post)				MK60_87.C0A
M3_UEBERSTEUERN_MUE_0		No Unit		M3_UEBERSTEUERN_MUE_0		No Unit		C0A_UEBERSTEUERN_MUE_0		No Unit
wert_00:	0x00	0​		wert_00:	0x00	0​		wert_00:	0x00	0​
wert_01:	0x66	102​		wert_01:	0x66	102​		wert_01:	0x06	6​
wert_02:	0xE6	230​		wert_02:	0xE6	230​		wert_02:	0xE6	230​
wert_03:	0x33	51​		wert_03:	0x33	51​		wert_03:	0x00	0​
wert_04:	0x26	38​		wert_04:	0x26	38​		wert_04:	0xF3	243​
wert_05:	0x7F	127​		wert_05:	0x7F	127​		wert_05:	0xC0	192​
wert_06:	0xE6	230​		wert_06:	0xE6	230​		wert_06:	0x13	19​
wert_07:	0xE6	230​		wert_07:	0xE6	230​		wert_07:	0xF7	247​
								wert_08:	0x0D	13​
M3_UEBERSTEUERN_MUE_1_2		m/s²		M3_UEBERSTEUERN_MUE_1_2	m/s²			C0A_UEBERSTEUERN_MUE_1_2		m/s²
wert_00:	0xE0	2​		wert_00:	2.5​			wert_00:	0x00	2.5​
wert_01:	0x13	2.797​		wert_01:	4.094​			wert_01:	0xED	2.203​
wert_02:	0xCD	1.703​		wert_02:	2.094​			wert_02:	0xA0	1​
wert_03:	0xED	2.203​		wert_03:	3.297​			wert_03:	0xE0	2​
wert_04:	0x06	2.594​		wert_04:	3.094​			wert_04:	0xD3	1.797​
wert_05:	0x40	3.5​		wert_05:	4.484​			wert_05:	0xBA	1.406​
wert_06:	0xCD	1.703​		wert_06:	2.094​			wert_06:	0x80	0.5​
wert_07:	0xCD	1.703​		wert_07:	2.094​			wert_07:	0xFA	2.406​
								wert_08:	0xD2	1.781​
								wert_09:	0xC6	1.594​
								wert_10:	0xF3	2.297​
								wert_11:	0xD4	1.813​
								wert_12:	0x00	2.5​

So the actual calculation seems to be the same between M3 and x35i. At least this is what shows up in NCS.
I am in the office so i can only work in theory right now.

By choosing MUE_0 = wert_02 (1.703) and MUE_1_2 = wert02/06/07 (2.094) it seems the car can drift now with TC support

I set wert_07 and euroMDM and it's pretty cool! I was able to drift out of the car wash with 90 degrees of opposite lock, and it pretty much held the drift for me.

So comparing the values i will try to code MUE_0 = wert02 and MUE_1_2 = wert_08

If i understood right the lower the value, the less TC intervention i get. I could then also choose wert_05 but i think 08 is a good starting point.

Another thing one can do additionally:

To update you guys, I also changed two values DRUCKMODELL_HA and DRUCKMODELL_VA to the GTS option in NCSDummy (there are only two, so i'm guessing it was wert_01 since I don't have my laptop with me). NCSDummy describes wert_00 as !MAN_UMF_GTS and wert_01 as MAN_UMF_GTS.

It may just be in my head, but normal acceleration with full DSC on (not MDM) is less intrusive, doesn't cut as much throttle, and keeps you closer to the grip limit. I notice this in 1st and 2nd gear powering out of turns. Can someone else test and verify?

But opposed to 0 and 1 as in the M3 DSC

the x35i has:

DRUCKMODELL_HA
Wert_00	0​
Wert_01	0​
Wert_02	2​
Wert_03	1​
Wert_04	4​
Wert_05	3​
DRUCKMODELL_VA
Wert_00	0​
Wert_01	0​
Wert_02	5​
Wert_03	1​
Wert_04	4​
Wert_05	2​
Wert_06	3​

I will check which values are set in my car and then probably see if and what changes with those different values.

 

[doublespaces]

May be @doublespaces extracts the posts about this topic to a seperate one where we can continue talking without being offtopic actually

I will definitly check this process and learn about it to actually achieve something like the guy posted about his experience with Wert=07

Great information! How do i figure if the values behind the Wert are equal between M3 and x35?

I haven't been keeping up. Which post numbers shall I move?

 

[JohnDaviz]

I haven't been keeping up. Which post numbers shall I move?

i would say it started with #463 completely until my last post #478

 

[aus335iguy]

Wert_nn and active/not active are essentially like option #. What matters are the hex values assigned to the options, not the option number itself. NETTODAT will pull the actual hex rather than the wert, so you can see/modify it directly.

Not all keywords are defined in all daten files, but most that aren't seem to cross/be similar. Unoccupied means a value is there, but the keyword isn't defined to say what it is.

Some of the first 8 bits of 30000A seem to be different functions between M and non-M. Either that, they or have different names for the same functions, which would mean "M dynamic" is active front steering?

I just picked ones that were in a range or obvious, like over/under steer coefficients and threshold. I don't know what the yaw torque compensations actually do. Sometimes, just figuring out what the functions are is the hardest part.

View attachment 60981

I find the table fascinating. It was previously said that the M3 DSC was much simpler than the non m in its implementation but the GTS DSC looks to have more in common with Non M than other M DSCs (actual calibration values differ)
That might mean we can just use straight up GTS values in Non M and be done with it.

 

[aus335iguy]

@JohnDaviz itd be really cool if once you’ve tried it you can report back on how much difference it made
Does your car have an lsd and if so have you switched off all of the other Nannie’s in the DSC ?