Coding M modules in a non M car
- Thread starter aus335iguy
- Start date
UPDATE: Seems I tested on my own flash and forgot I was sending higher torque values now, but didn't up my torque limit tables to give plenty of overhead. I bumped them up and after taking it back out, seems better. I'm guessing I was getting close to the torque limit, so the DME was gently removing timing to keep it under control. At least that seems to explain why the DSC light flickered when it was obviously having full tire traction.
After logging it looks like when traction kicks in, timing cuts to 0. But it does it gracefully. Not nearly as painful as the 135i programming.
The only off thing I noticed is rolling on throttle below 3000 rpm, the dsc light kicks on blinking and power is cut, but 3000+ putting the hammer down and it spins a bit but no dsc light.
I didn't log to see what is going on. One of these days. Besides that it does really well with DSC on.
After logging it looks like when traction kicks in, timing cuts to 0. But it does it gracefully. Not nearly as painful as the 135i programming.
The only off thing I noticed is rolling on throttle below 3000 rpm, the dsc light kicks on blinking and power is cut, but 3000+ putting the hammer down and it spins a bit but no dsc light.
I didn't log to see what is going on. One of these days. Besides that it does really well with DSC on.
Last edited:
If possible, can I pay you to code and flash my 135i N55 DCT with the 1M or M3 DSC software?
My DME is the late E series N55 DME (MEVD1726)
Sorry, my time is very limited. This is a hobby for me. But I'm sure there is someone else here that would be open to it.
Hi All.
I noticed today i got a SZL M Button error in MHD.
There is no errors on my dash, or driving issues, but would just like to confirm that this is related to the 1MDSC coding spoken about in this thread?
Also, just to touch on the MDM/M Button offering better throttle response.
I know that with my car (2009 E92 335i DCT). if i press my Sport button, the car increases responsiveness a helluva lot. its fantastic.
Would this be the same as to what the M Button would do on the steering wheel?
I am aware that MDM would provide more lenient DSC control, and i assume this is what flashing the 1M DSC would give us?
Also, as per the comment about Sport+ process in iDrive much like the Z4, its highly possible that the 1M does have a slightly different DSC process more in tune with the Z4 than the 135i/335i?
I say this because i did notice that my Launch Control no longer works since flashing the IKM0S EU 1M bin to my car. i will test it again this afternoon when i drive it again to confirm, but if its not working, it may be similar to my post about the DCT ZSUB numbers between Z4 and 135/335 being different.
Z4 - Sport toggle next to lever (for LC)
135/335 - DSC button (for LC)
If my LC is indeed not working, i believe that loading the Z4 35is DCT software would cure this aspect.
I noticed today i got a SZL M Button error in MHD.
There is no errors on my dash, or driving issues, but would just like to confirm that this is related to the 1MDSC coding spoken about in this thread?
Also, just to touch on the MDM/M Button offering better throttle response.
I know that with my car (2009 E92 335i DCT). if i press my Sport button, the car increases responsiveness a helluva lot. its fantastic.
Would this be the same as to what the M Button would do on the steering wheel?
I am aware that MDM would provide more lenient DSC control, and i assume this is what flashing the 1M DSC would give us?
Also, as per the comment about Sport+ process in iDrive much like the Z4, its highly possible that the 1M does have a slightly different DSC process more in tune with the Z4 than the 135i/335i?
I say this because i did notice that my Launch Control no longer works since flashing the IKM0S EU 1M bin to my car. i will test it again this afternoon when i drive it again to confirm, but if its not working, it may be similar to my post about the DCT ZSUB numbers between Z4 and 135/335 being different.
Z4 - Sport toggle next to lever (for LC)
135/335 - DSC button (for LC)
If my LC is indeed not working, i believe that loading the Z4 35is DCT software would cure this aspect.
I haven’t tried to launch since going IKMOSbut if it doesn’t work, I’m not sure I follow as to how the z4 TCU software will fix that at all?
your below post from page 5 shows that it may be a possibility that the 1M would have the similar DSC protocols as the Z4.
Its not definitive i know, but if the M Button, and MDM button are differently configured and are closer to the Z4 than the 135i/335i, then it may be plauseable, however can only know once actually load and test the Z4 DCT software, (if in fact my LC is not working)
That part is correct. DSC protocols might be similar. The Z4is TCU part I think will be more like 135is/335is I think.
Not likely. its possible, but in my experience from loading the Z4 TCU software onto a 135i DCT, the LC did not work, and vice versa when loading 335i DCT software to a Z4, again LC didnt work.
I agree my thoughts are only theoretical, but if going by your snippet of information, if the the 1M does in fact use that similar DSC structure in the background as the Z4, then it may be a simple TCU flash for the DCT, but as i said, its only in the air as a thought. i may be dead wrong, which has been known to happen from time to time
Oh and the 1M MDM button error is normal as you don’t have the DSC. Once it’s coded and working with the correct SZL you’ll be able to activate sport throttle from the button(according to those that have done it)
You could be right that makes sense. All of my thinking is theoretical also. Well there’s only one way to be sure ...Not likely. its possible, but in my experience from loading the Z4 TCU software onto a 135i DCT, the LC did not work, and vice versa when loading 335i DCT software to a Z4, again LC didnt work.
I agree my thoughts are only theoretical, but if going by your snippet of information, if the the 1M does in fact use that similar DSC structure in the background as the Z4, then it may be a simple TCU flash for the DCT, but as i said, its only in the air as a thought. i may be dead wrong, which has been known to happen from time to time
The reason I thought the 1M and z4 were related was because of commentary and stats on how the z4 launched
I assume this can still work with my current SZL, just need to code it with the 1M? or do i need the SZL from the 1M? as my button where the M button should be is just the Multimedia button, but if i keep my own SZL and the Steering wheel, then the Media button would then become the M Button.
Yea, i think the configuration may very welll be similar, will test my current configuration for launch this afternoon to see if it was just a user error on my part and then give feedback over the weekend.
It’s not been shown but Tom from Brintech said that any SZL works. apparently you have to keep trying to code it and it eventually takes. I dug up the post recently. He knew what he was talking about though
Hey there,
I've got a 2008 M3 6MT no iDrive that I am trying to retrofit M-drive and MDM to, but running in to some issues. Perhaps one of you have encountered this issue and can shed some light.
I acquired the appropriate SZL clock spring from an M3 part-out that had M-drive and rain sensor. I've installed it and added $2MD to the VO, and performed the process ECU procedure (SG_CODIEREN) on the CAS and NFRM. Then I unplugged the battery for an hour to let the modules restart. Pressing the change audio source button on my steering wheel (which would be an M button on M-drive equipped M3s) brings up the green M icon on my dash and changes my throttle response (Sport mode) and suspension (EDC) settings, but doesn't bring up MDM on my dash. I tried pressing and holding the button for 5 mins as I have read that this enables MDM on non iDrive vehicles (as there is no iDrive to turn it on), but this does nothing.
Any ideas? Thank you in advance.
I've got a 2008 M3 6MT no iDrive that I am trying to retrofit M-drive and MDM to, but running in to some issues. Perhaps one of you have encountered this issue and can shed some light.
I acquired the appropriate SZL clock spring from an M3 part-out that had M-drive and rain sensor. I've installed it and added $2MD to the VO, and performed the process ECU procedure (SG_CODIEREN) on the CAS and NFRM. Then I unplugged the battery for an hour to let the modules restart. Pressing the change audio source button on my steering wheel (which would be an M button on M-drive equipped M3s) brings up the green M icon on my dash and changes my throttle response (Sport mode) and suspension (EDC) settings, but doesn't bring up MDM on my dash. I tried pressing and holding the button for 5 mins as I have read that this enables MDM on non iDrive vehicles (as there is no iDrive to turn it on), but this does nothing.
Any ideas? Thank you in advance.
Last edited:
Well done you are one of very few that got this far!
MDrIve and MDM is part of the M3 DME and when you press it the DME requests m dynamic mode from the DSC ...IF ...that’s how you have it set in the I drive. (I haven’t dug into how non I drive m3s models store It.
edit: wrote a bit about non m cars that wasn’t relevant
Last edited:
Lol 
I’ve just realised he has an M3(thanks for pointing out @derekgates
Look up in the manual for non idrive MDM if it’s calling up EDC ithe coding is working and likely a process issue
I’ve just realised he has an M3(thanks for pointing out @derekgatesLook up in the manual for non idrive MDM if it’s calling up EDC ithe coding is working and likely a process issue
Last edited:
At first I tried performing the "Process car" procedure on NCS Expert, but I was getting errors so I default coded each individual module instead. Since then, I've managed to default coded all modules, except for the 2MULF, 8BMOT, and MASK modules. So I have default coded the M3 DSC module (which is aptly named M3DSC).
I've read somewhere (I think in this thread) that the M3 traction control relies on inputs from the DME - which in my case, would be the 8BMOT module. I don't believe the 2MULF and MASK module are relevant to this retrofit as they control audio related functions.
Currently, I am running in to some issues with default coding the 8BMOT DME module - in NCSExpert, I am getting the following error: COAPI-2000 Fehler in EDIBAS oder in "SG-Beschreibungsdatei" SYS-0008: Job nicht gefunden MSS60.
I suspect it has to do with my Daten files not being up to date, but I am not sure. I will update and report back.
Side note - I have also read warnings about potentially bricking the DME when coding with NCSExpert and a DCAN cable. As long as I am using a K+DCAN cable, will it be safe?
I've read somewhere (I think in this thread) that the M3 traction control relies on inputs from the DME - which in my case, would be the 8BMOT module. I don't believe the 2MULF and MASK module are relevant to this retrofit as they control audio related functions.
Currently, I am running in to some issues with default coding the 8BMOT DME module - in NCSExpert, I am getting the following error: COAPI-2000 Fehler in EDIBAS oder in "SG-Beschreibungsdatei" SYS-0008: Job nicht gefunden MSS60.
I suspect it has to do with my Daten files not being up to date, but I am not sure. I will update and report back.
Side note - I have also read warnings about potentially bricking the DME when coding with NCSExpert and a DCAN cable. As long as I am using a K+DCAN cable, will it be safe?
With respect to coding your DME I have no experience or knowledge of it so I can’t advise.
do you have ISTA-D? If so see if you can see anything with it perhaps?
do you have ISTA-D? If so see if you can see anything with it perhaps?
Similar threads
