Flashing DME with DCAN

[bmwlover0725]

Before I start, I SWEAR that I was attempting to flash the FRM only with ISTA/P in Expert Mode. This was my first time using it and I didn't realize that I still had the DME checked. I continued with the flash...

As most of you could imagine, the programming of the DME failed. It is now reading "Programming status is 5" and the status at the top of the information dialogue reads "OK." The car turns over, but doesn't start beyond that. I'm also getting a million different warnings and dash has been decorated as a result of my stupidity to resemble that of a Christmas tree.

I've spoken with a dealer and they told me that I it sounds programmable for them, but I haven't had it towed yet. I know you're all going to tell me to just take it there (especially because they said it will be 160 dollars to reprogram and code all of the modules), but I'm wondering if there is ANY way to do this using my dcan cable that wont destroy my DME if it hasn't been already. I know I run the risk of this just by plugging a computer into my car and flashing anything, but I want to know if there is a way to flash it with my cable that is reasonably successful in other cases or if there is NO way that is marginally safe.

Please advise - and for the record, I've searched and found that this is dangerous to do in most cases so no need to quote it from another thread. I have to at least give it a shot and see if there is anything new

[BimmerRookie]

If you don't know how to do it, I think $160 is a fair/ cheap price to get everything fixed... Just my honest opinion. Pay up and be on your way.

[tdott]

I'd rather get a remote coder to try, then if that fails you can try the dealer.

[bmwlover0725]

I have roadside that I never did anything with for the past several years and finally got to make use of. I had it towed to my dealer and they got it started after reflashing and udpating. It will be 233 after tax. They're recoding the DSC module because it wasn't originally responding, but they think it will be good to go today. Needless to say, I'll be getting an icom clone to use from now on.

[BPMSport]

If you purchase a tune or have a tuning cable, that will fix it. Otherwise using a proper programming interface is the only way to fix it. Would not attempt programming again with a DCAN cable.

[bmwlover0725]

Well I picked up the car earlier this afternoon and it works fine. Everything is good and it's all updated. 252.05 after all was said and done. I'm definitely not going to complain with that other than how I hate myself for being an idiot and not just buying a new for several hundred more since I'll be needing one anyway at some point.

EDIT: I have one question though (and don't worry, I'm done with this until I get the correct equipment) - what is the difference between a k+dcan cable and your average tuning cable from somewhere like Turner? I know that since my cable fails and the Turner one works, there must be something. I'm just curious as to what the difference is. I'm assuming the chip. I thought about this as I watched everything go to hell the night I was attempting my update.

[Rajmun340]

Originally Posted by bmwlover0725

Well I picked up the car earlier this afternoon and it works fine. Everything is good and it's all updated. 252.05 after all was said and done. I'm definitely not going to complain with that other than how I hate myself for being an idiot and not just buying a new for several hundred more since I'll be needing one anyway at some point.

EDIT: I have one question though (and don't worry, I'm done with this until I get the correct equipment) - what is the difference between a k+dcan cable and your average tuning cable from somewhere like Turner? I know that since my cable fails and the Turner one works, there must be something. I'm just curious as to what the difference is. I'm assuming the chip. I thought about this as I watched everything go to hell the night I was attempting my update.

tough crowd, I see you've got no response, quite indecent to ignore a honest question while they're making a quick buck flashing and being overprotective about it. They do little to dissipate the stereotype of the shady ramifications of that business. I'd feel dirty to pay to have my car tuned when you know it's all tracable to hacking files at some point

[dpaul]

Originally Posted by Rajmun340

tough crowd, I see you've got no response, quite indecent to ignore a honest question while they're making a quick buck flashing and being overprotective about it. They do little to dissipate the stereotype of the shady ramifications of that business. I'd feel dirty to pay to have my car tuned when you know it's all tracable to hacking files at some point

Aside from the fact that it's two years since the last post, you're staking out a rather extreme position.

The sad fact is that the OP used a DCAN cable, which was well known at the time to disable the MSS60 and few other modules. Benvo (BPM) actually made the first post that I'm aware providing a detailed explanation for that problem. The OP was already aware of the issue at the time of his first post.

in early 2016, the OP had no choice but to pay a tuner for a properly designed flashing device or take the car to the dealer and hope for the best.

For the record, the "Pro" DCAN cable sold by Bimmergeeks (https://www.bimmergeeks.net/) has firmware updates that address this problem and can be safely used to flash the MSS60 with WinKFP - I have done so successfully a number of times.

I'm not a professional tuner and have no horse in this particular race. However, I feel it is unfair to dismiss the skill and effort required to develop a safe and effective tune, much less a system to permit writing altered calibration files the DME, as simply "hacking files". Even with A2L or DAMOS descriptions to start with, developing a tune takes time and some artistry is involved. Producing reliable flashing hardware requires equal effort of a different sort and it appears that most BMW tuners these days purchase such hardware from Freiling (https://www.frieling-group.com/). So the cost of the devices have to be factored into the price of the tune. If there were more S65 engines with more owners interested in tunes, the price would be lower. But there aren't.

[Ggeezer]

Originally Posted by dpaul

Aside from the fact that it's two years since the last post, you're staking out a rather extreme position.

The sad fact is that the OP used a DCAN cable, which was well known at the time to disable the MSS60 and few other modules. Benvo (BPM) actually made the first post that I'm aware providing a detailed explanation for that problem. The OP was already aware of the issue at the time of his first post.

in early 2016, the OP had no choice but to pay a tuner for a properly designed flashing device or take the car to the dealer and hope for the best.

For the record, the "Pro" DCAN cable sold by Bimmergeeks (https://www.bimmergeeks.net/) has firmware updates that address this problem and can be safely used to flash the MSS60 with WinKFP - I have done so successfully a number of times.

I'm not a professional tuner and have no horse in this particular race. However, I feel it is unfair to dismiss the skill and effort required to develop a safe and effective tune, much less a system to permit writing altered calibration files the DME, as simply "hacking files". Even with A2L or DAMOS descriptions to start with, developing a tune takes time and some artistry is involved. Producing reliable flashing hardware requires equal effort of a different sort and it appears that most BMW tuners these days purchase such hardware from Freiling (https://www.frieling-group.com/). So the cost of the devices have to be factored into the price of the tune. If there were more S65 engines with more owners interested in tunes, the price would be lower. But there aren't.

I just bought the Bimmergeeks cable specifically for the MSS60 flashing functionality. I'm glad to hear that it actually works and I'll be attempting a DME update soon.

How long does the flash typically take? Is it as easy as selecting the MSS60 in the Update ZUSB (F3) button and then proceeding with the flash? Any further coding required after the fact?

[dpaul]

Only takes a few minutes - haven't done it in a while and can't remember exactly - either ~8 minutes or ~20 minutes.

For WinKFP 5.3.1, one way to do it:
Select Comfort mode
Select Update ECU
Select Module (MSS60)
Select Prog ZUSB

Obviously, make sure your datens are reasonably current - the latest ZUSB is 7854376, corresponding to "241E" in many postings about this DME. It's in the daten available from link on BimmerGeek site (v60.1)

About subsequent coding: I notice that I have one persistent fault code (2780 - "DME - no coding"). I am not sure when it first appeared so I cannot absolutely correlate it with a WinKFP update. I've done some flashing with KessV2 for tuning purposes and it might have been set by that. In any case, this fault does not set the CEL and the vehicle runs well so I haven't chase it down yet. Coding with NCSEXpert might eliminate the error. Could not hurt

[BPMSport]

Be careful as we have seen the DME fail flashing with that cable as well. The only 100% safe bet is an ICOM or Tuning cable.

Try coding the DME with NCS and that should take care of the no coding issue - although it's not normally lost after flash on this platform as it is on F series Bosch control units.

[dpaul]

Mike

Interesting to hear that you've encountered DME flashing failures with the Bimmergeeks Pro cable. I've had great results but of course my testing only involved one vehicle/DME.

I've been experimenting with methods to bypass the RSA signature checks using WinKFP as a flashing platform so I've put the DME into a failure mode quite a few times. I've always been able to recover by flashing stock 0da/0pa files. At least a dozen times. It is quite reliable and reproducible on my car.

It would be interesting to know something about the configuration of the vehicles in which Bimmergeeks Pro cable failed.

[derbo]

Originally Posted by dpaul

Only takes a few minutes - haven't done it in a while and can't remember exactly - either ~8 minutes or ~20 minutes.

For WinKFP 5.3.1, one way to do it:
Select Comfort mode
Select Update ECU
Select Module (MSS60)
Select Prog ZUSB

Obviously, make sure your datens are reasonably current - the latest ZUSB is 7854376, corresponding to "241E" in many postings about this DME. It's in the daten available from link on BimmerGeek site (v60.1)

About subsequent coding: I notice that I have one persistent fault code (2780 - "DME - no coding"). I am not sure when it first appeared so I cannot absolutely correlate it with a WinKFP update. I've done some flashing with KessV2 for tuning purposes and it might have been set by that. In any case, this fault does not set the CEL and the vehicle runs well so I haven't chase it down yet. Coding with NCSEXpert might eliminate the error. Could not hurt

I noticed there is a 7854377 (one number higher than the 376) Anyone know what that corresponds to? BPMSport ? Alex@Alpine dpaul ?

$ PS10INIT N00000000000000000000000055000000000000 V
$ VERSIONKFCONF: kfconf10.dat
;Zusbauvorschrift vom 20.10.2014 11:44
;SG-TYP: MSS60
;ZB-NR  TYP-NR  HW-NR  IX SW-NR     AM          PIN S CS
7854376,7838840,7854317,A,7848136DA,0FFFFFFFFFD,000,1 G
7854375,7838841,7854317,A,7848134DA,0FFFFFFFFFD,000,1 8
7854371,7844915,7854317,A,7850264DA,0FFFFFFFFFD,000,1 I
7854372,7844915,7854317,A,7848128DA,0FFFFFFFFFD,000,1 V
7854373,7843727,7854317,A,7848130DA,0FFFFFFFFFD,000,1 B
7854377,7838724,7854317,A,7848138DA,0FFFFFFFFFD,000,1 M
7854374,7838724,7854317,A,7848132DA,0FFFFFFFFFD,000,1 V

[derbo]

Maybe BIMGE can help too?

Calling out gurus!

[dpaul]

Sorry I wasn't clear at all.

The ZUSB describes the combination of program and calibration files ("HW-NR" and SW-NR", respectively) used to flash the DME. Note that the HW-NR files which are the program code, are all the same number. The SW-NR files contain vehicle-specific tables relating to operating parameters that may be region- and configuration-specific. ZUSB 7854376 is for my car, a US M3 with manual transmission.

WinKFP in comfort mode will pick the right one for you.

[derbo]

Originally Posted by dpaul

Sorry I wasn't clear at all.

The ZUSB describes the combination of program and calibration files ("HW-NR" and SW-NR", respectively) used to flash the DME. Note that the HW-NR files which are the program code, are all the same number. The SW-NR files contain vehicle-specific tables relating to operating parameters that may be region- and configuration-specific. ZUSB 7854376 is for my car, a US M3 with manual transmission.

WinKFP in comfort mode will pick the right one for you.

Thanks dpaul I saw someone reference the 375 as the Japan 241E. I'm not sure what the 377 is and looking at the .0da files doesn't show anything in the notes either in the top part. Curious if anyone knew. I'm just curious more than anything.

7854377: $REFERENZ 0569QT0Z240EEKEV0 2
7854376: $REFERENZ 0569QT0Z240EEKUV0 E

[Flyboy161]

I am sad to say my DME is now in prodramming status 5 with the same Christmas tree of faults described by the OP. Yes, I was trying to update the integration level of the software when the DME quit. I tried reflashing with WinKfp with no success. I keep getting EDIABAS.98 sys-0008 and EDIABAS sys-0012 errors in ISTA-P, WinKfp, and INPA. So, before I tow my 4000 pound paperweight to the dealer, any ideas?

[derbo]

Originally Posted by Flyboy161

I am sad to say my DME is now in prodramming status 5 with the same Christmas tree of faults described by the OP. Yes, I was trying to update the integration level of the software when the DME quit. I tried reflashing with WinKfp with no success. I keep getting EDIABAS.98 sys-0008 and EDIABAS sys-0012 errors in ISTA-P, WinKfp, and INPA. So, before I tow my 4000 pound paperweight to the dealer, any ideas?

Contact Alex@Alpine or BPMSport and they can help you if with their tuning cable and purchasing their tune. (I believe that is the case.)

[Alex@Alpine]

Originally Posted by Flyboy161

I am sad to say my DME is now in prodramming status 5 with the same Christmas tree of faults described by the OP. Yes, I was trying to update the integration level of the software when the DME quit. I tried reflashing with WinKfp with no success. I keep getting EDIABAS.98 sys-0008 and EDIABAS sys-0012 errors in ISTA-P, WinKfp, and INPA. So, before I tow my 4000 pound paperweight to the dealer, any ideas?

Send me a text message I can lay out your options for you. 310-560-0808

[Flyboy161]

Thanks derbo! Alex is just the ticket! I’ll follow up on this post this weekend.

[brettcp]

Originally Posted by Ggeezer

I just bought the Bimmergeeks cable specifically for the MSS60 flashing functionality. I'm glad to hear that it actually works and I'll be attempting a DME update soon.

How long does the flash typically take? Is it as easy as selecting the MSS60 in the Update ZUSB (F3) button and then proceeding with the flash? Any further coding required after the fact?

The DME took around 7-8 minutes I believe. I did it with the Bimmergeeks Pro cable, no problems. I updated all modules (except those on the MOST bus) with the Bimmergeeks Pro cable, all worked well. I did have to use expert mode to flash the FRM for some reason, but it worked just fine. I had the car jumped to another car for power.

[Flyboy161]

Alex @ Alpinemss hooked me up! I'm mobile again! Greatest customer service I've ever seen!

The Alpine tune is awesome!