M-Drive and MDM in non M cars

[aus335iguy]

There will be more brake intrussion with the 1m firmware to compensate the wheelbase design implications. It will interact sooner in comparison to the M3.

I believe there is a way to load the dsc calibration into the 1m dsc firmware.

Always wondered if we could not adjust calibration ourselves or ease the calibration somehow (without endangering ourselves)

Apparently friction coefficients from the M3 GTS are the most relaxed and allow for the most slide.
Apparently you can change the coefficients in even a standard DSC to be the same as the M3.
Petes toy with a licence plate thread on the e90 post forum has the most detail that I know of but I’m still not sure it’s as easy as he said it was. Others have tried and couldn’t make it work. @superwofy might have from memory. I gave up when I heard he couldn’t do it lol

 

[RTA]

Yes, now I recall, I think he wrapped the M3 dsc data in a default e92 n54 firmware "header/signature" and then forced the loading.
Will give it a try on of these days.

On the other hand, since my springrates are in line with my power levels and the LSD, traction on track without DSC is pretty well doable, however a hooligan mode with sidewheels is always nice and usefull ;-) So still keen to have MDM, especially because I hope it also eases the corner braking interference, a nanny I can't get to shut up... (Even without DSC the car is braking at the track at certain corners, everything I could find has been disabled (e-diff etc) but the car still interferes at high torque cornering. )

 

[AzNdevil]

There will be more brake intrussion with the 1m firmware to compensate the wheelbase design implications. It will interact sooner in comparison to the M3.

I believe there is a way to load the dsc calibration into the 1m dsc firmware.

Always wondered if we could not adjust calibration ourselves or ease the calibration somehow (without endangering ourselves)

cant say for the 1m/m3 dsc coding but its possible to play with the calibrations on non m dsc

 

[RSL]

Reference material: 335is DTC (short) and full off DSC (long) button press logs - KCAN 0x316 and 0x19E.

 

[Olza]

Ok, so we stopped after determining that dsc button works, jbe sees short and long press (verified in inpa), long press can disable dsc off, but short press did not enables mdm/traction.
Why? Thoughts or reasons:
1. JBE can be the reason only if it sends short press not in suitable format (time) for DSC, OR sends not in proper place
2. MDM flag is routed to DSC, but DSC can’t broadcast it, OR didn’t get proper confirmation from, for example, DME. Question do we know, what status in CAN packet signalled for traction (except 0x19E) to KOMBI?
3. MDM flag is routed to DSC, but DSC can’t switch to it because of lack of conditions to enable it - sensors or other modules statuses.

What do you think? I like 3rd reason. How can we check it?

 

[RSL]

The signal makes it through to turn it full on/off, I can't imagine DTC/MDM signal would separately be a problem getting through from a timing standpoint.

If it's not 0x19E, I'm not sure what it would be. There aren't a whole lot of messages that I see from DSC.

BMW went out of their way to disable 0x399 to DCT on 1M, maybe they did something similar with 1MDSC for MDM since it's also a standalone ZB.

 

[Olza]

Who where has true 1M?
And any info available for 135/1M dsc program chip (processor type)?

 

[aus335iguy]

The DSC unit is common across M and Non M cars only the software calibration and hydraulic pump vary
Dunno anyone with an unfettered 1M

 

[Begood69]

Who where has true 1M?
And any info available for 135/1M dsc program chip (processor type)?

I have one i am putting back together. If by the time is ready u did not find one i can do what u need. But i need a lil how to to log it?

 

[dzid_]

Ok, so we stopped after determining that dsc button works, jbe sees short and long press (verified in inpa), long press can disable dsc off, but short press did not enables mdm/traction.
Why? Thoughts or reasons:
1. JBE can be the reason only if it sends short press not in suitable format (time) for DSC, OR sends not in proper place
2. MDM flag is routed to DSC, but DSC can’t broadcast it, OR didn’t get proper confirmation from, for example, DME. Question do we know, what status in CAN packet signalled for traction (except 0x19E) to KOMBI?
3. MDM flag is routed to DSC, but DSC can’t switch to it because of lack of conditions to enable it - sensors or other modules statuses.

What do you think? I like 3rd reason. How can we check it?

2*.
What if DSC broadcasts it using a different message? (Or was that already debunked - I haven't checked myself as I didn't figure out how to flash it yet ).

I noticed the following codings in KOMBI:

MOTORSPORT
    wert_02
ST_MDRV_ALIVE_MONITOR
    nicht_aktiv
ST_MDRV_CSUM_MONITOR
    nicht_aktiv
ST_MDRV_ID_MONITOR
    nicht_aktiv

Maybe they have to be enabled to read the missing message. ...Though now I am thinking these are for servotronic VO216.

 

[Olza]

2*.
What if DSC broadcasts it using a different message? (Or was that already debunked - I haven't checked myself as I didn't figure out how to flash it yet ).

I noticed the following codings in KOMBI:

MOTORSPORT
    wert_02
ST_MDRV_ALIVE_MONITOR
    nicht_aktiv
ST_MDRV_CSUM_MONITOR
    nicht_aktiv
ST_MDRV_ID_MONITOR
    nicht_aktiv

Maybe they have to be enabled to read the missing message. ...Though now I am thinking these are for servotronic VO216.

That is already all active (
One of the reason is JBE or KOMBI coding. KOMBI looks ok.
Also in INPa DSC sees both long and short press of button. But reacts only on long press…

 

[dzid_]

Or simply MDM status could be on a different bit within 0x19E.
And maybe KOMBI interprets it but perhaps the M cluster is different and MDM led is on a different output?

 

[Olza]

So we need to parse 19e packet from 1m and 135 with dsc 1m and compare.

 

[RSL]

I'd be curious if it worked on an MT car.

 

[dzid_]

I still haven't flashed any M firmware on my 135i, but I picked up M3 cluster.
As most of you probably know, MDM-led lights up when non-M DTC is pressed.
So it is unlikely what I thought earlier that KOMBI could be the reason why you guys don't see MDM led with 1M-DSC.

Strange thing though, when I coded in the M3 cluster with 135i coding I was getting transmission error chime/icon whenever I switched from P to D. Also, normally big P was on, but in D the gear indicator would disappear after a couple of seconds. Turns out it was due to MOTORSPORT = 0x0 (On) and probably due to lack of M CAN messages.

Interestingly I had MOTORSPORT enabled also with 135i cluster. On 135i cluster MOTORSPORT was ok, but on M3 cluster causing the error. I think M3 cluster must be aware that it is from M3. I am guessing data in the EEPROM makes it self-aware.


The next step for me is to enable the shift lights in that new cluster.

Yeah, I don't suspect it's rocket surgery. I tried but they don't work if you aren't moving so I couldn't get any data. I should be able to log this when the M1.5 is put together though.

Also, 0x206 comes from the DME, not the DKG.

I wonder if someone recorded shiftlights 0x206 while driving?

It would be cool to calculate optimal shift-point based on rpm, engine load (minus engine inertia torque - changing depending on uphill/downhill), torque curve, and next gear ratio.

 

[aus335iguy]

I still haven't flashed any M firmware on my 135i, but I picked up M3 cluster.
As most of you probably know, MDM-led lights up when non-M DTC is pressed.
So it is unlikely what I thought earlier that KOMBI could be the reason why you guys don't see MDM led with 1M-DSC.

Strange thing though, when I coded in the M3 cluster with 135i coding I was getting transmission error chime/icon whenever I switched from P to D. Also, normally big P was on, but in D the gear indicator would disappear after a couple of seconds. Turns out it was due to MOTORSPORT = 0x0 (On) and probably due to lack of M CAN messages. Interestingly I had MOTORSPORT enabled also with 135i cluster. On 135i cluster MOTORSPORT was ok, but on M3 cluster causing the error. I think M3 cluster must be aware that it is from M3. I am guessing data in the EEPROM makes it self-aware.


The next step for me is to enable the shift lights in that new cluster.

I wonder if someone recorded shiftlights 0x206 while driving?

It would be cool to calculate optimal shift-point based on rpm, engine load (minus engine inertia torque - changing depending on uphill/downhill), torque curve, and next gear ratio.

Wait up,
You’re saying you had a stock cluster with Motorsport coding and didn’t get an error ?

 

[aus335iguy]

To be clear Motorsport coding to me is that on DCT cars it shows large numbers and gears like in an M3…


Also The shift lights were only on M3 DME on cars with DCT. The 1M was manual only and I’m pretty sure had no shift lights and so neither would the IKMOS ROM/DME

Would be interesting if there was something related to vestigial 1M DME DCT code that might enable it

 

[dzid_]

Wait up,
You’re saying you had a stock cluster with Motorsport coding and didn’t get an error ?

Yes. No error. I am not 100% sure if it was doing anything, or was that due to DCT, but compared to other (manual) 135i, my gear indicator was always on and slightly bigger.
My 135i DCT looked like this (also for D1-S7, not only M1-M7):

While manual 1 series:

Oh, seems like this 1M also looks like the normal 1 series:

So my 135i DCT gear digit was slightly bigger than on the 335i cluster but still much 3x smaller than M3 cluster digits .

Now on the M3 cluster, I need to keep MOTORSPORT off because of the error.
The display is quite crowded, but not too bad. I like other features, e.g. cruise control display (and the needle) work again with dynamic cruise coded-in. I wonder if the dynamic cruise control display was not working because the MOTORSPORT was on...


I am on stock N55 DME (whatever MHD flash is called)... and I would be surprised the M3 cluster would do anything with the shiftlights.

There is also this thing called Gear Shift indicator (in manual transmission it shows arrows when to do the shift, and in DCT seems like it doesn't do anything) and it is programmable for per key. Shiftlights option seems to be also per key, but there is no value to choose.

First, the proximity of shiftlight to gear shift indicator option makes me think these two options are related. I wonder if, when the gear shift indicator (SPA) is on, whether the 0x206 message appears?!
Second, seems like shift ligts can be enabled per key too.
Apparently SPA can be turned on (in manual cars) by long pressing B/C button.

Would be interesting if someone looked on the can for the 0x206, when ECO gear change indicator is enabled.

 

[aus335iguy]

This is what I thought you were talking about

 

[dzid_]

This is what I thought you were talking about

Yeah.
And 135i cluster accepts the responsible coding for that (MOTORSPORT) without error (surprisingly), but it never displays digits that big.
M3 cluster takes this coding (obviously), but errors out when switching P to D.
Both had the same KMBI_PL2.C08 coding firmware.

Oh, so that's how the shiftlights appear stock. Nice.
(6-7 should be shifted pretty much at the redline - 7th gear is longer. Interesting.)
I wonder if 0x206 appears only when LEDs are lit up. Someone needs to log it Or I might try to brute-force it.