Let me get to my laptop and do it. I will post some pics on most of the steps.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.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.
I can confirm. I done it why i was troubleshooting the mk60 on a dsc90.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 would even add the vin writing in expert mode. So u have that done at once. Good write up. Thx for the extra detailsThanks 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:
- 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'
- Opened the ZB number in Comfort Mode of WinKFP to retrieve the PABD, P-SGBD, and ECU integration position details.
- Dropped the .0pa file corresponding to the ZB I wanted to flash (1M) in the develop folder. See 'ZB in Folder'
- Opened expert mode in NCS Expert, and entered the PABD, P-SGBD, and ECU integration position that was populated during step 2.
- Hit 'Done' (takes you back to main page) and then hit program.
- Percent complete counter will quickly go from 0-100, and then restart at zero. Once complete, WinKFP will return a message saying 'flash sucessful'
- 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.)
- 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:
- 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.
- 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.
- Go to 'Change ECU' and you should now see '1MDSC' or 'M3DSC' listed depending on what vehicle code you changed to in step 2.
- Change coding operation to 'SG_CODERDATEN' if not already selected and click 'Process ECU'
- Go into ISTA, carryout vehicle recognition and vehicle test
- Clear all faults for every module first - Should get rid of most lights on dash
- 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 have the M button working. I do feel the throttle change. That do work.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.
Do you have the 1M/M3 SZL?I have the M button working. I do feel the throttle change. That do work.