|
|
|
|
|
|
BMW Garage | BMW Meets | Register | Search | Today's Posts | Mark Forums Read |
|
BMW 3-Series (E90 E92) Forum
>
Cloned DME with EEPROM Error
|
|
02-13-2020, 12:26 PM | #1 |
Enlisted Member
3
Rep 47
Posts |
Cloned DME with EEPROM Error
My DME was water damaged so I bought a used DME and had someone clone my one. This was successful apart from the EEPROM which is was missing some data and the car won't start with it attached. Its coming up with 2fa3 and 2fa4 errors:
Is it possible to reset the EEPROM data? Last edited by stevethresh; 02-15-2020 at 06:58 AM.. |
02-13-2020, 12:49 PM | #2 | |
Colonel
996
Rep 2,287
Posts |
Quote:
You might get lucky and a program + calibration file reflash with winfkp comfort mode will get you running. |
|
Appreciate
0
|
02-13-2020, 01:16 PM | #3 |
Banned
3
Rep 42
Posts |
|
Appreciate
0
|
02-13-2020, 02:33 PM | #4 |
Registered
0
Rep 1
Posts |
Ive got a junkyard DME MSV80 to replace my currenly bad DME, also an MSV80. Im wondering how to clone the DME and rewrite the old files onto the replacement DME. I'm not against buying hardware, I have jsut found a ton of conflicting information. I have seen people on youtube swap DMEs in 15 min, and others use kess v2, yet another guy used AD-200. I'm just not sure if this is something I can do. The Kess V2 setup looked pretty straight forward.
|
Appreciate
0
|
02-13-2020, 04:01 PM | #5 | |
Enlisted Member
3
Rep 47
Posts |
Quote:
Could you please expand on your suggestion. I'm just not familiar with the tools yet. Perhaps there's already a walkthrough showing how to do what you have suggested. |
|
Appreciate
0
|
02-15-2020, 06:33 AM | #6 |
Enlisted Member
3
Rep 47
Posts |
I've had a go at getting WINKFP configured to flash the ECU but it has failed with the errors shown below. The progress bar went to 100% once and then the errors were displayed. Is there something obviously wrong with my config?
|
Appreciate
0
|
02-15-2020, 02:36 PM | #7 |
Enlisted Member
3
Rep 47
Posts |
I've managed to update the DME with winkfp but I'm still left with the following two errors and the car will only turn over, not start.
$ SGBD: MSV70 version: 6.00 ================================================== ========================================= $ DATAID: 004 9PP0L 822S 0BI3S === 13.02.2020 === 16:32:57 Current kilometer reading: 148746 km __________________________________________________ _________ comment line 1: comment line 2: __________________________________________________ _________ $ Error location number: 12195 $ ErrorLocationText: 2FA3 coding missing 57022FA35404062F0128000000740500000000000000000000 000000 Error: 1 (2) No: 12195 2FA3 coding missing frequency: 1 error type: 4 (31) coding data in EEPROM incorrect Readines Flag: (17) Test conditions not yet met error status: (34) Error currently present, not yet debounced MIL status: (48) Error does not light up the warning lamp (MIL) P code: P062F control unit - internal EEPROM error F_LZ: 40 environment text / entry at 0 km (1st) Motor speed 0.00 rpm Voltage class 87 11.78 V Engine control status ENG_LOCK Time since start 0.00 s __________________________________________________ _________ $ Error location number: 12196 $ FehlerOrtText: 2FA4 Wrong data record 57022FA4580432350128000000740500000000000000000000 000000 Error: 2 (2) No: 12196 2FA4 Incorrect data record frequency: 1 error type: 8 (172) variant monitoring Readines Flag: (17) Test conditions not yet met error status: (34) Error currently present, not yet debounced MIL status: (48) Error does not light up the warning lamp (MIL) P code: P3235 Control unit monitoring safety function - error variant coding F_LZ: 40 environment text / entry at 0 km (1st) Motor speed 0.00 rpm Voltage class 87 11.78 V Engine control status ENG_LOCK Time since start 0.00 s __________________________________________________ _________ Anything else I can update that might patch whatever is missing from the EEPROM? |
Appreciate
0
|
02-15-2020, 05:17 PM | #8 | |
Colonel
996
Rep 2,287
Posts |
Quote:
|
|
Appreciate
0
|
02-16-2020, 05:39 AM | #9 |
Enlisted Member
3
Rep 47
Posts |
I used the comfort mode. Selected MSV70 and set it going. There was an initial pass which I assume was clearing out the old data. Next a slow pass which took few minutes and finally a quick pass which took less than a minute. I'm assuming the last two passes were the two files you're talking about. Is there any way to check with INPA? I can see the DME has been updated. Is there a last coding datestamp?
The programming option showed this: --------------------------- Result - Assembly identification number update --------------------------- ECU -> ZBNr. from UIF: 7562994 Update -> current ZBNr.: 7581280 Program current ZBNr.? --------------------------- Yes No --------------------------- Following the update: Last edited by stevethresh; 02-16-2020 at 06:04 AM.. |
Appreciate
0
|
02-16-2020, 07:07 AM | #10 |
Lieutenant Colonel
654
Rep 1,893
Posts |
If you used comfort mode you've flashed both 0pa and 0da.
ZB-NR (ZUSB or assembly identification number) specifies an allowed combination of TYP-NR, HR-NR and SW-HR files for a given module. Give the ZUSB to WinKFP in comfort mode and it does the rest HR-NR (hardware number) is actually the filename of the 0pa (program) file which you can find in the daten. SW-NR (software number) is the filename of the 0da (data or calibration or map) file. |
Appreciate
0
|
02-16-2020, 08:28 AM | #11 |
Lieutenant Colonel
654
Rep 1,893
Posts |
As far as I know 2FA3 is a completely benign code, at least for the MSD80 and MSS60 DMEs. You can eliminate it by coding the DME to defaults with NCSExpert. But it is very unlikely to affect your no-start condition
Who "cloned" your DME and how what equipment/approach did they use to do it? Last edited by dpaul; 02-16-2020 at 10:36 AM.. |
Appreciate
0
|
02-16-2020, 09:03 AM | #12 |
Enlisted Member
3
Rep 47
Posts |
Genuine BDM-100 was used. He's going to let me have the files. It was noted that the donor DME unit had data in the EEPROM file that is zeros in my EEPROM file.
Is the 2fa4 error also benign? |
Appreciate
0
|
02-16-2020, 09:09 AM | #13 |
Enlisted Member
3
Rep 47
Posts |
There are a couple of other errors but from searching these seem innocuous.
Date: 15.02.2020 19:16:56 Model: E89X Scope: all control module JobStatus: OKAY Quantity: 15 ---------------------------------------------------------------- ADR Gen. name JobStatus 92 VIRTSG92 ERROR_ECU_SERVICE_NOT_SUPPORTED ---------------------------------------------------------------- ADR Gen. name JobStatus Number of errors Error code Kind of error 00 JBBF OKAY No Error stored 12 DME/DDE OKAY No Error stored 17 EKP OKAY No Error stored 18 EGS OKAY No Error stored 1C LDM/ICM OKAY No Error stored 36 TEL/MULF OKAY No Error stored 40 CAS OKAY 1 Error stored A0B4 60 41 DWA OKAY No Error stored 50 SINE OKAY No Error stored 60 KOMBI OKAY No Error stored 62 MOSTGW OKAY No Error stored 63 MASK/CCC OKAY No Error stored 72 FRM OKAY 1 Error stored 9CCE 62 78 KLIMA OKAY No Error stored ================================================== =============== |
Appreciate
0
|
02-16-2020, 10:36 AM | #14 | |
Lieutenant Colonel
654
Rep 1,893
Posts |
Quote:
BDM should have had no problem cloning the MSV70. Hassmaschine is the poster you want to ask about this: https://www.e90post.com/forums/showthread.php?t=1035058 Last edited by dpaul; 02-16-2020 at 10:52 AM.. |
|
Appreciate
0
|
02-16-2020, 10:43 AM | #15 | |
Lieutenant Colonel
654
Rep 1,893
Posts |
Quote:
|
|
Appreciate
0
|
02-16-2020, 12:41 PM | #16 | ||
Colonel
996
Rep 2,287
Posts |
Quote:
Are you sure you reflashed the program section? Probably a 15 min flash and then a two minute flash for the calibration file. If I'm not mistaken much of the eeprom data is written during flash updates or just generally pulled from the car , CAS and Kombi during use. Last option would be recoding with NSCexpert. Are you able to reflash the EEPROM yourself? I probably have an eeprom file that a can provide that will get you closer then all zeros. |
||
Appreciate
0
|
02-17-2020, 06:23 AM | #19 | |
Lieutenant Colonel
654
Rep 1,893
Posts |
Quote:
That said, a 2FA4 (variant coding) error will not necessarily prevent the vehicle from starting, including at least some cases when 2FA4 results from power class mismatch. But I do not know what other sorts of problems might trigger 2FA4 and how they might affect starting. I think the suggestion rjahl made earlier to make sure that the WinKFP flash executed correctly is a very good one. |
|
Appreciate
0
|
02-17-2020, 07:14 AM | #20 |
Enlisted Member
3
Rep 47
Posts |
Could this be a DME / EWS alignment issue? INPA cannot communicate with EWS when I try to use the EWS alignment functions but maybe I'm doing it wrong.
reset EWS --------------------------- EDIABAS-Error --------------------------- ApiResultText: Error #19 IFH-0009: NO RESPONSE FROM CONTROLUNIT API job error or no such result ! Continue script processing ? --------------------------- Yes No --------------------------- Is this relevant? |
Appreciate
0
|
02-17-2020, 07:22 AM | #21 | |
Lieutenant Colonel
654
Rep 1,893
Posts |
Quote:
I think you'd first reset code (F1?) then program start value (F2?) Don't think this can hurt |
|
Appreciate
0
|
Bookmarks |
Thread Tools | Search this Thread |
|
|