Coding M modules in a non M car

Begood69

Corporal
Nov 13, 2016
234
113
25
Fayetteville, NC
Ride
335i N54 Predator 3.2L stroker
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.
 

Attachments

  • 20200404_095418.jpg
    20200404_095418.jpg
    145.1 KB · Views: 665

S54ca

Private
Apr 4, 2020
28
31
0
Looking forward to the above response as well. I have a 135i with all the 1M / M3 suspension bits, brakes, and LSD and would like to code the DSC module to match that hardware.

Default coding the DSC after changing the VO does not work, and WINKFP I’m comfort mode will not flash the 1M ZB due to ‘HW Mismatch Error’, which makes sense.

I believe I can force it to take the ZB in expert mode, but want to confirm I won’t brick the module before doing so.
 
  • Agree
Reactions: derekgates

aus335iguy

Colonel
Nov 18, 2017
2,248
803
0
Down under
Ride
335i DCT 2009
I don’t believe it will brick the module, but I’m not 100% on that. There’s lots of people who have swapped modules and others that have flashed, its left me confused. If it does brick it though they are relatively cheap to replace 😃
 
  • Like
Reactions: Begood69

S54ca

Private
Apr 4, 2020
28
31
0
Wasn't able to get it to flash using expert mode either. @Begood69 , can you confirm that you've flashed an MK60e5 the M3/1M file even though the HW number doesn't match?
 
  • Like
Reactions: Begood69

Begood69

Corporal
Nov 13, 2016
234
113
25
Fayetteville, NC
Ride
335i N54 Predator 3.2L stroker
Wasn't able to get it to flash using expert mode either. @Begood69 , can you confirm that you've flashed an MK60e5 the M3/1M file even though the HW number doesn't match?
I can confirm. I done it why i was troubleshooting the mk60 on a dsc90.
When u create and copy the mk60 opa in the develop folder on winkfp folder as pic on previous reply. Then open winkfp. Check config. Make sure u write vin and force programming in expert. Then go like u r trying to update the mk60 and back to where u see program button. It will show u all the parameters to expert code. Take a pic as ref.
Then go expert. Make sure u have the right data. And last u should see only one file the zb for mk60 in the last step. Then just program. It should work just like a normal coding. Until it tell u programming ok or some like that.
Lmk
 

S54ca

Private
Apr 4, 2020
28
31
0
Thanks to the instruction above, I was able to program it successfully. After default coding in NCS Expert and performing the adjustment routine in ISTA, it works 100% with no codes.

Programming steps I used:
  1. Checked original ZB / HW PN in ISTA (but can be done in INPA as well). Specific DSC PN/ZB I had originally as shown in 'DSC Readout ISTA'
  2. Opened the ZB number in Comfort Mode of WinKFP to retrieve the PABD, P-SGBD, and ECU integration position details.
  3. Dropped the .0pa file corresponding to the ZB I wanted to flash (1M) in the develop folder. See 'ZB in Folder'
  4. Opened expert mode in NCS Expert, and entered the PABD, P-SGBD, and ECU integration position that was populated during step 2.
  5. Hit 'Done' (takes you back to main page) and then hit program.
  6. Percent complete counter will quickly go from 0-100, and then restart at zero. Once complete, WinKFP will return a message saying 'flash sucessful'
    1. NOTE: I performed this while my car was running to keep the battery voltage up, but soon after flashing the engine stalled and the iDrive and KOMBI became un-responsive. This was scary, and would not recommend others to do the same -- please use a battery charger.)
  7. After the flash completed, many different errors were present on the dash. To eliminate them, I first used NCS Expert to Default Code the DSC Module by:
    1. Using NCS Expert to read VO from CAS or FRM/NFRM - Ensure that the 'Modify with FSW/MAN' is turned OFF for whichever profile you are using.
    2. Editing the V0 - I deleted my vehicle code (forget what it was, but it should look like something like "*KG13"), and added the 1M vehicle code of "*UR93". Click OK.
    3. Go to 'Change ECU' and you should now see '1MDSC' or 'M3DSC' listed depending on what vehicle code you changed to in step 2.
    4. Change coding operation to 'SG_CODERDATEN' if not already selected and click 'Process ECU'
  8. Go into ISTA, carryout vehicle recognition and vehicle test
    1. Clear all faults for every module first - Should get rid of most lights on dash
    2. Run DSC Calibration procedure - If all goes well, you should now have a fully function 1M / M3 DSC module now. INPA now lists the module as 'MK60E5 E82 M-Version'.
 

Attachments

  • ZB In Folder.PNG
    ZB In Folder.PNG
    14.3 KB · Views: 635
  • ISTA Module Readout.JPG
    ISTA Module Readout.JPG
    644.2 KB · Views: 453
  • DSC readout ISTA.PNG
    DSC readout ISTA.PNG
    87.8 KB · Views: 428
  • NCS Expert Configuration.PNG
    NCS Expert Configuration.PNG
    14.1 KB · Views: 432
  • NCS Expert Coding Settings.PNG
    NCS Expert Coding Settings.PNG
    82.1 KB · Views: 494
Last edited:

Begood69

Corporal
Nov 13, 2016
234
113
25
Fayetteville, NC
Ride
335i N54 Predator 3.2L stroker
Thanks to the instruction above, I was able to program it successfully. After default coding in NCS Expert and performing the adjustment routine in ISTA, it works 100% with no codes.

Programming steps I used:
  1. Checked original ZB / HW PN in ISTA (but can be done in INPA as well). Specific DSC PN/ZB I had originally as shown in 'DSC Readout ISTA'
  2. Opened the ZB number in Comfort Mode of WinKFP to retrieve the PABD, P-SGBD, and ECU integration position details.
  3. Dropped the .0pa file corresponding to the ZB I wanted to flash (1M) in the develop folder. See 'ZB in Folder'
  4. Opened expert mode in NCS Expert, and entered the PABD, P-SGBD, and ECU integration position that was populated during step 2.
  5. Hit 'Done' (takes you back to main page) and then hit program.
  6. Percent complete counter will quickly go from 0-100, and then restart at zero. Once complete, WinKFP will return a message saying 'flash sucessful'
    1. NOTE: I performed this while my car was running to keep the battery voltage up, but soon after flashing the engine stalled and the iDrive and KOMBI became un-responsive. This was scary, and would not recommend others to do the same -- please use a battery charger.)
  7. After the flash completed, many different errors were present on the dash. To eliminate them, I first used NCS Expert to Default Code the DSC Module by:
    1. Using NCS Expert to read VO from CAS or FRM/NFRM - Ensure that the 'Modify with FSW/MAN' is turned OFF for whichever profile you are using.
    2. Editing the V0 - I deleted my vehicle code (forget what it was, but it should look like something like "*KG13"), and added the 1M vehicle code of "*UR93". Click OK.
    3. Go to 'Change ECU' and you should now see '1MDSC' or 'M3DSC' listed depending on what vehicle code you changed to in step 2.
    4. Change coding operation to 'SG_CODERDATEN' if not already selected and click 'Process ECU'
  8. Go into ISTA, carryout vehicle recognition and vehicle test
    1. Clear all faults for every module first - Should get rid of most lights on dash
    2. Run DSC Calibration procedure - If all goes well, you should now have a fully function 1M / M3 DSC module now. INPA now lists the module as 'MK60E5 E82 M-Version'.
I would even add the vin writing in expert mode. So u have that done at once. Good write up. Thx for the extra details
 
  • Like
Reactions: derekgates

S54ca

Private
Apr 4, 2020
28
31
0
Following up here. I'm trying to get MDM (DSC) mode working as well via the iDrive toggle. Was this ever possible in 1M's equipped with iDrive?

The settings show up on iDrive, but the fields do not change with the lights on the KOMBI. So far I can only tell if DSC is completely on or completely off, as I have no 'MDM' light on my cluster.

According to TIS, the DSC switch on both the 1M and 135i communicate over CAN instead of being pinned directly to the ECU as in the M3. Does an option code need to be added to enable this? I dug through some 1M vins / option codes and didn't see anything that appear to correspond to MDM.

Adjustable servotronic settings would be nice as well, but pretty sure the 1M JBBF doesn't support this like the M3 ECU does.
 

Mr Rage

Lurker
Feb 12, 2020
40
21
0
27
Crewe
Ride
2009 E92 335i M-DCT IKM0S 2.81
I found this on an m3 forum maybe it would help with getting MDM to work.
 

Attachments

  • 798ED0FC-7E7A-4D69-B1A4-2165EA652C77.png
    798ED0FC-7E7A-4D69-B1A4-2165EA652C77.png
    414.8 KB · Views: 626

S54ca

Private
Apr 4, 2020
28
31
0
Unfortunately, those options aren’t available in the 1M DSC trace file.

At this point I’m thinking that this functionality didn’t exist in 1M’s with iDrive or that the IKM0S code is needed on the DME. I’ll try the later once I figure out how to convert it from IJE0S.
 

S54ca

Private
Apr 4, 2020
28
31
0
IKMOS has been flashed. The MDrive options in iDrive now show 'Unchanged' instead of '-'. Changing the options within the M Drive menu results in no change. Unless other modules need to be coded to 1M spec, it seems that MDM isn't configurable via iDrive with the M1DSC.

I've also noticed that my steering wheel button configuration has changed. The HVAC recirculation button now controls the radio input, and the radio input button doesn't seem to do anything (the 'M' button on 1M's). I'm assuming that the 1M SZL is needed to trigger the adjustable throttle response associated with the 'M' button. I may go ahead and do this.
 

aus335iguy

Colonel
Nov 18, 2017
2,248
803
0
Down under
Ride
335i DCT 2009
Theoretically If someone in Australia in a 2009 dct and Ikmos wanted to try and flash the 1M and or M3 SZL file into that car with active cruise what’s the best order of operation? I mean should they code out active cruise first you think ? What could go wrong ?

Asking for a friend :)
 
  • Funny
Reactions: doublespaces

Begood69

Corporal
Nov 13, 2016
234
113
25
Fayetteville, NC
Ride
335i N54 Predator 3.2L stroker
IKMOS has been flashed. The MDrive options in iDrive now show 'Unchanged' instead of '-'. Changing the options within the M Drive menu results in no change. Unless other modules need to be coded to 1M spec, it seems that MDM isn't configurable via iDrive with the M1DSC.

I've also noticed that my steering wheel button configuration has changed. The HVAC recirculation button now controls the radio input, and the radio input button doesn't seem to do anything (the 'M' button on 1M's). I'm assuming that the 1M SZL is needed to trigger the adjustable throttle response associated with the 'M' button. I may go ahead and do this.
I have the M button working. I do feel the throttle change. That do work.
 

ccfj1

Specialist
Jul 26, 2018
64
54
0
UK
Ride
bmw e92 n55 335i Sport manual
Interesting reading.....

Just to clarify, if i were to buy a normal 1-3 series dsc/abs module, (mk90???) i would be able to force a 1m or m3 firmware update to it and flash it to either of the models.?

1-3 series dsc/abs pumps are dirt cheap here in the UK and i dont mind buying one to test with (i have a full bench setup at home), connecting it up to flash with my icom would be no problem.

Getting the m-drive button working for the dsc would be nice (if it would work).

P.S, ive ordered a m3 szl and switch pack (and mfsw buttons) and they should be here this week (its should be the part number above too).

I have a full cic on the bench too (as well as jbbr3, cas, key elv etc).
 
  • Like
Reactions: Begood69