M-Drive and MDM in non M cars
- Thread starter aus335iguy
- Start date
Many thanks, @Hotter!!!
I compared our trace files, yours should bei RAD22.C34, mine is RAD22.C32. In the following picture I show you what I found what is different and might be the problem, my red comment is a parameter from your trace file, which might have to be switched in my trace. May this help?
IN ADDITION, there is another parameter in your RAD22.C34, which I am not able to find in my RAD22.C32.
So my question is, could it be possible that I have to flash mine to RAD22.C34 first to have this parameter “MODE_BEHAVIOR”?
Could you PLEASE tell me your ZB or ZSUB number, @Hotter??
That way I might be able to flash mine to the last RAD22.C34…
MODE_BEHAVIOR is just mode change when switching between sources, I have activated the new one.
But update to C34 maybe would help. Just select module and let WinKFP take the newest version It should become C34.
Is it possible to get "Funktionsrahmen MSS60"?
I want to find more information on shift lights can bus message 206hex id.
@Hotter It is possible, you need to flash the DSC with M firmware. That's if you have the newer versions of the DSC (2007+ I believe)
You will lose the eDiff functionality, not sure if you can re-enable it via coding, I think it's not possible.
That's the phase I'm at, I flashed the DSC firmware and now the dtc button isn't working anymore as it needs to be rewired.
On the M3 the button is wired directly to the dsc module.
It's wired to the jbbe for other versions of the E9x
You will lose the eDiff functionality, not sure if you can re-enable it via coding, I think it's not possible.
That's the phase I'm at, I flashed the DSC firmware and now the dtc button isn't working anymore as it needs to be rewired.
On the M3 the button is wired directly to the dsc module.
It's wired to the jbbe for other versions of the E9x
My car is 2009 so DSC should be ok?
Is MDM worth it? What exactly do I loose when loosing eDiff functionality?
This seems to be easy mod just flash and wire some wires? No need to change to M modules?
Isn't it not more easy to adjust the DSC sensitivity by using the M3 value tables in the original 3 series flashfiles?
In that way you can drift etc in DTC mode for example.
About eDiff, it's a solution to manage slip. It has nothing to do with the concept of a slip differential, as it is brake based, the wheel that slips receives intervention via the brake system. It's save but not making your car faster, the opposite, and useless on a racetrack.
When you have a real diff installed, you should decode ediff anyway otherwise your physical diff will almost not get utilized. Removing eDiff without an LSD is up to you, not my advice to remove it. I do feel comfortable in a BMW without LSD and eDiff but that's my personal taste so to say.
The M fw does not know about eDiff, it will be messy when combined.
In that way you can drift etc in DTC mode for example.
About eDiff, it's a solution to manage slip. It has nothing to do with the concept of a slip differential, as it is brake based, the wheel that slips receives intervention via the brake system. It's save but not making your car faster, the opposite, and useless on a racetrack.
When you have a real diff installed, you should decode ediff anyway otherwise your physical diff will almost not get utilized. Removing eDiff without an LSD is up to you, not my advice to remove it. I do feel comfortable in a BMW without LSD and eDiff but that's my personal taste so to say.
The M fw does not know about eDiff, it will be messy when combined.
Hi, I also want to get rid off this DSC intervention, it ruins everything. I played with custom coding every single value( like GMR_MAX_LIMIT_SCHRAEG ; FRICTION COEFFICIENT's and so on...) in my DSC module without much success, things even get worse. How can you tell, if I have the newer versions of the DSC. And if yes, which ZB number should I flash?
Last edited:
https://www.e90post.com/forums/showthread.php?t=1598910&page=3 (no offense intended)
Hi guys,
I'm trying to achieve mdm and mdrive on a non-M car as well.
I have the following M modules installed: kombi, jbbf, SZL, frm, edc-k and M3 software on the DSC.
I'm using a modified version of superwofy's module to save the idrive mdrive settings, trigger mdrive, shift-lights and other stuff.
My DME is Msd80 but currently I have the non-turbo N53 engine.
The problem is, I can't get the (M) light to turn on on the kombi, with the module, the 0x399 message gets sent correctly I believe, but the light doesn't turn on.
I know I'll have to handle applying the settings from the module as well, but first I want to get over the m light issue.
Tried different codings on the kombi too.
Is the Ikm0s firmware sending something to the kombi to turn that light on? Does anyone have any info on that?
Thanks
I'm trying to achieve mdm and mdrive on a non-M car as well.
I have the following M modules installed: kombi, jbbf, SZL, frm, edc-k and M3 software on the DSC.
I'm using a modified version of superwofy's module to save the idrive mdrive settings, trigger mdrive, shift-lights and other stuff.
My DME is Msd80 but currently I have the non-turbo N53 engine.
The problem is, I can't get the (M) light to turn on on the kombi, with the module, the 0x399 message gets sent correctly I believe, but the light doesn't turn on.
I know I'll have to handle applying the settings from the module as well, but first I want to get over the m light issue.
Tried different codings on the kombi too.
Is the Ikm0s firmware sending something to the kombi to turn that light on? Does anyone have any info on that?
Thanks
I see, so it should all be in the message with Id 399 even for the kombi. I'll review my message creation tomorrow to make sure it does it properly and report back.
I did see that for people that don't have the M3 cluster, the power steering light turns on, making me think it's maybe a different can message.
Thanks.
I have my stock 335is Kombi. With it coded, the steering lock light comes on with M Drive, which is where the M light would be on the M3 cluster. My 0x399 is MSD81 native (N54), no CAN shield or interposer.
The stock MSD81 0x399 differs slightly from M3 and is missing one bit via logic that will tell DSC/DKG MDrive is active to automatically pass the presets and it's annoyed me for years. I still have to do DSC and DKG settings manually with buttons after turning on MDrive.
Byte 4 0xDF is servtronic sport mode and kombi light on. Make sure MDrive Kombi coding is done and 0x399 counter/checksum are working.
The stock MSD81 0x399 differs slightly from M3 and is missing one bit via logic that will tell DSC/DKG MDrive is active to automatically pass the presets and it's annoyed me for years. I still have to do DSC and DKG settings manually with buttons after turning on MDrive.
Byte 4 0xDF is servtronic sport mode and kombi light on. Make sure MDrive Kombi coding is done and 0x399 counter/checksum are working.
So, I wasn't able to make it work yet.
Some things I learned are:
The rewiring for the DTC button is not M3 stock, on DSC, pin 41 is for the center console button switch ( the one with power, EDC, DSC) which I have wired but DSC isn't working, EDC does work. Stock M3 has an RDC button in place of the DTC.
I have the complete wiring loom from an 2011 E93 M3 so I'm able to cross check stuff.
Tried the 1MDSC and the hazard switch DTC button works that way, no MDrive though. I'd like to have the M3DSC software anyway.
I have a spare MSD81 which I'm going to use with the N54 engine I'm buying, I'll try to write IKM0S, and pair it with my CAS and try it that way to see if it does the trick.
I have the brake pad sensors broken so red indicator in the Kombi is always on, I'm wondering if this has an effect maybe?
Some trace from me trying to turn MDrive light on. The messages are hardcoded and going through the checksum function.
Status MDrive on.
0x399: 0x92 0x51 0x35 0x2A 0x51 0x97
0x399: 0xA3 0x51 0x35 0x2A 0x51 0x97
0x399: 0xB4 0x51 0x35 0x2A 0x51 0x97
Status MDrive off.
0x399: 0xC5 0x50 0x35 0x2A 0x41 0x97
Status MDrive on.
0x399: 0xD6 0x51 0x35 0x2A 0x51 0x97
0x399: 0xE7 0x51 0x35 0x2A 0x51 0x97
0x399: 0xF8 0x51 0x35 0x2A 0x51 0x97
Some things I learned are:
The rewiring for the DTC button is not M3 stock, on DSC, pin 41 is for the center console button switch ( the one with power, EDC, DSC) which I have wired but DSC isn't working, EDC does work. Stock M3 has an RDC button in place of the DTC.
I have the complete wiring loom from an 2011 E93 M3 so I'm able to cross check stuff.
Tried the 1MDSC and the hazard switch DTC button works that way, no MDrive though. I'd like to have the M3DSC software anyway.
I have a spare MSD81 which I'm going to use with the N54 engine I'm buying, I'll try to write IKM0S, and pair it with my CAS and try it that way to see if it does the trick.
I have the brake pad sensors broken so red indicator in the Kombi is always on, I'm wondering if this has an effect maybe?
Some trace from me trying to turn MDrive light on. The messages are hardcoded and going through the checksum function.
Status MDrive on.
0x399: 0x92 0x51 0x35 0x2A 0x51 0x97
0x399: 0xA3 0x51 0x35 0x2A 0x51 0x97
0x399: 0xB4 0x51 0x35 0x2A 0x51 0x97
Status MDrive off.
0x399: 0xC5 0x50 0x35 0x2A 0x41 0x97
Status MDrive on.
0x399: 0xD6 0x51 0x35 0x2A 0x51 0x97
0x399: 0xE7 0x51 0x35 0x2A 0x51 0x97
0x399: 0xF8 0x51 0x35 0x2A 0x51 0x97
The M3 DSC pin wire is well known and documented. The 1M DSC works like others, the M3 doesn't have a DTC button. M3 MDM is activated via M wheel button and M3 DSC can only be turned off via the center console button (direct wire). AFAIK, pin 41 can be wired to the non-M DTC button or any button really. I'd have to look up the wiring again to check, but IIRC, it just needs to be grounded to turn M3 DSC off, similar to what the Power button does in M3 for DME.
The DTC button only becomes RDC reset when you default code JBBF as M3. When I ran M3 DSC, I disabled it because I kept pushing it out of habit.
0x399 byte 1 bit 1 needs to be 1 when MDrive is active or DSC/DKG/JBBF will ignore it. Make that 0x52 when on.
Make sure you don't have an actual brake pad sensor problem. That happened to me once. Popped up shortly after a DSC flash and couldn't get it cleared. After messing with it, pulled the wheels to find a sensor had actually come somewhat loose and worn down at a coincidental time.
There are logics that need to be on for native M Drive messages to be active. No idea if DME is going to do anything with them just because you're sending the messages, but other modules may. LV_VAR_SPT_SWI needs to be true for MSD81 to even broadcast the M Drive messages and maybe pay attention to them. It's enabled by default in IKM0S.
The DTC button only becomes RDC reset when you default code JBBF as M3. When I ran M3 DSC, I disabled it because I kept pushing it out of habit.
0x399 byte 1 bit 1 needs to be 1 when MDrive is active or DSC/DKG/JBBF will ignore it. Make that 0x52 when on.
Make sure you don't have an actual brake pad sensor problem. That happened to me once. Popped up shortly after a DSC flash and couldn't get it cleared. After messing with it, pulled the wheels to find a sensor had actually come somewhat loose and worn down at a coincidental time.
There are logics that need to be on for native M Drive messages to be active. No idea if DME is going to do anything with them just because you're sending the messages, but other modules may. LV_VAR_SPT_SWI needs to be true for MSD81 to even broadcast the M Drive messages and maybe pay attention to them. It's enabled by default in IKM0S.
Similar threads
