M-Drive and MDM in non M cars
- Thread starter aus335iguy
- Start date
No.
I believe if you have the correct vehicle code and VO the correct options may appear in your current rad.
if indeed the m cars have a totally different ZSUB then you can probably flash it using ICOM via most. Look for guides elsewhere on how that’s done.
on Non m CIC systems all of the options are there. I find it hard to believe that the rad units have more sophisticated security.
in short make sure you have correct M3 build date (post’12) vehicle code (M3 for your region) and change your VO and then default code the rad. If that doesn’t work flash the M3 ZSUB
But you might need to use expert mode with altered vehicle code
read this post about flashing a non m DSC with m DSC ZSUB
www.spoolstreet.com
I believe if you have the correct vehicle code and VO the correct options may appear in your current rad.
if indeed the m cars have a totally different ZSUB then you can probably flash it using ICOM via most. Look for guides elsewhere on how that’s done.
on Non m CIC systems all of the options are there. I find it hard to believe that the rad units have more sophisticated security.
in short make sure you have correct M3 build date (post’12) vehicle code (M3 for your region) and change your VO and then default code the rad. If that doesn’t work flash the M3 ZSUB
But you might need to use expert mode with altered vehicle code
read this post about flashing a non m DSC with m DSC ZSUB
Coding M modules in a non M car
It’d be great if you could explain with some screenshots as I can see this in particularly is something lots of people are interested in. Let me get to my laptop and do it. I will post some pics on most of the steps.
www.spoolstreet.com
It seems I have bricked my test bench RAD2... It flashed 100% in expert mode, than got an error, restarted it and not able to flash it back to previous software. I am still able to read its UIF,
but when flashing its stuck at 0%, radio screen starts to blink and turns off, it should stay on, after some time I get this error:
Is it possible to restore it somehow?
but when flashing its stuck at 0%, radio screen starts to blink and turns off, it should stay on, after some time I get this error:
Is it possible to restore it somehow?
Last edited:
I think that was a bad idea to flash RAD22 (lci) firmware to RAD2 (pre-lci). I dont think I can unbrick it. Anyway I have wasted some more money on used RAD22 (9231928) which already has RAD22.C34 software! I was able to change RAD22_MDRIVE to active. Now radio ignores Rotate button, it still responds to Disk button. So at least I have one button available. Would love to edit radio software itself and disable other buttons, but I don't think that's possible?
Ok so to follow this up, I finally got a nice cable that I can code the radio with. My radio is a RAD22.C32 and setting RAD22_MDRIVE solved the double function issue.
So, to summarize this: setting the RAD correctly is needed for the steering wheel functions to work properly for the RAD and IHK but the RAD does not inhibit the function of M Drive with the right SZL and ECU.
So does it send two packets or does it send one and the rest of the car interprets what’s meant to happen?
M Button status has its own packet. Which is odd because the SZL clearly still sends it in the normal button status packet as well. The button status packet just sends the status of each button by location, not by function. It’s up to the receiving module to decide what to do with it.
double check vo and code your dsc again? i have a m3 szl now and the bitton doesnt do anything... but i do get a code complaining about the m drive button or something...
The message from sender SZL to receiver DME code will always be there if the button logic is enabled in the DME and there's no signal. If you just flash IKM0S, you'll have the error automatically because it's enabled by default.
M DSC flash and coding will stop that error, even without M SZL, but the button will not actually trigger M functions without the M SZL. On the other hand, it will trigger both M and media functions with the M DSC/SZL if the CIC/radio are not coded as M Drive to ignore the media source message.
M DSC flash and coding will stop that error, even without M SZL, but the button will not actually trigger M functions without the M SZL. On the other hand, it will trigger both M and media functions with the M DSC/SZL if the CIC/radio are not coded as M Drive to ignore the media source message.
im not sure if i have disabled it in my tune but i did the 1m IKM0S upgrade
i dont feel like doing much with my car these days and i dont feel like taking stuff apart or flashing my car in 36C weather..........
i will eventually get around to do the m dsc upgrade though...
speaking of which, i have tested mdm and m drive on a m3 and it doesnt feel too different from dtc mode... now i dont really have too much expectations for it...
Unless it was specifically turned off in IKM0S, it's enabled. I don't blame you, summer is on the way here too.
US 1M DSC is OK. On DCT, it doesn't trigger until high RPM when on, at least on mine. It's probably on MDM mode though and I tune so at least 2nd gear mostly sticks to begin with. Euro 1M DSC is complete garbage, might as well be a valet mode.
Euro M3 DSC is probably the best, but I haven't moved to it yet because I've been too lazy to wire the DSC. Some day I will, but I disable completely in the meantime.
Edit: DTC full on in M3 still let's a lot slide, literally. It's nothing like non-M. I almost never ran with it completely off. Full on or MDM can drive like a lunatic, slide it around and never lose it.
Last edited:
I'm facing the same issues as many here with my 135i. Flashed the DME to IKM0S, installed the SLZ from an M3 with Mdrive and Flashed the DSC as the DSCM80 for the 1M.
I modified my VO for a #0910 and UR93 built (USDM 1M) and coded 1MDSC, the SLZ, DME and JBE.
I have an M3 cluster as well, the Green (M) lights up with the thottle tables. The long press DSC off work, but no 1 click DTC/MDM anymore.
I compared the wiring diagram, the switch for DSC/MDM is only just a dumb switch to the JBE, Now I see the 1M part list reference the JBBE3R, M version only.
Is it possible it's the last piece of the puzzle ? The 1M only list this one as the possible part : 61359364819. My 135i has the JBE2.
I modified my VO for a #0910 and UR93 built (USDM 1M) and coded 1MDSC, the SLZ, DME and JBE.
I have an M3 cluster as well, the Green (M) lights up with the thottle tables. The long press DSC off work, but no 1 click DTC/MDM anymore.
I compared the wiring diagram, the switch for DSC/MDM is only just a dumb switch to the JBE, Now I see the 1M part list reference the JBBE3R, M version only.
Is it possible it's the last piece of the puzzle ? The 1M only list this one as the possible part : 61359364819. My 135i has the JBE2.
I see for the M3 wiring diagrams, that seems to be the case, but not for the 1M.
Otherwise, that would mean the wiring diagrams are incorrect, which is somewhat possible considering how limited the 1m production was.
Is there a known list of m3/1m ZB for the jbe ? I have the M3 rack as well.
Otherwise, that would mean the wiring diagrams are incorrect, which is somewhat possible considering how limited the 1m production was.
Is there a known list of m3/1m ZB for the jbe ? I have the M3 rack as well.
Read a bit back in this thread; in short as I understood the difference:
- M3 - MDM mode is achieved via a message send from the DME to the CANbus picked up by SZL, Gearbox and DSC
- 1M - DSC receives signal via physical button on dash send via a direct wire attached to the DSC module
A) The 1M DME did not has this logic onboard so workaround was chosen via the cable
B) The M3 MDM includes more and is governed in essence by the DME
Last, the M3 DSC firmware is best, the 1M is better then the rest but it's designed around a not so super suspension of the 1M and is more intrusive and is also designed to compensate the flaws of the 1M setup
- M3 - MDM mode is achieved via a message send from the DME to the CANbus picked up by SZL, Gearbox and DSC
- 1M - DSC receives signal via physical button on dash send via a direct wire attached to the DSC module
A) The 1M DME did not has this logic onboard so workaround was chosen via the cable
B) The M3 MDM includes more and is governed in essence by the DME
Last, the M3 DSC firmware is best, the 1M is better then the rest but it's designed around a not so super suspension of the 1M and is more intrusive and is also designed to compensate the flaws of the 1M setup
What do you mean "not so super suspension of the 1M"? 1M literally uses the same complete rear end and same control arms up front - only the front subframe is slightly different. Infact a 335i can run the M3 front subframe as well so I don't think there's much difference apart from rigidity (135/335 can run M3 rear end as well).
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)
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)
Similar threads
