|
|
|
|
|
|
BMW Garage | BMW Meets | Register | Today's Posts | Search |
|
BMW 3-Series (E90 E92) Forum
>
How to find correct ZB number (DME)
|
|
09-11-2015, 05:34 AM | #1 |
Private
17
Rep 84
Posts |
How to find correct ZB number (DME)
Hi everyone,
I've been lurking for a bit and need a bit of help. I was trying to upgrade the firmware of the DME in my Australian 10/2007 E91 323i with the N52 2.5l 6 cyclinder controlled by the MSV80 DME since I was having an issue with the EGS and it was reported an error transmitting from the DME to the EGS module. I used a USB K+DCAN cable from Onestop Electronics I used WinKFP and it detected the MSV80 no problem with Comfort -> Update ZUSB and the upgrade started. For whatever reason it failed about halfway and stopped responding. Of course it would no longer start (cranked only) and threw a whole stack of errors in other modules because the DME no longer responded. S**t. Unfortunately I lost the screen shot I took with the initial message with the before and after firmware versions so I don't know what was originally programmed nor what it was trying to program. This is essentially my first problem. I had an old dump of module information taken months ago that reported: ADR Gen. name JobStatus SGBD GROUP Part No. VarI DiaI CoI HwI SW-No FSV SW-No OSV SW-No MCV SW-No res Date Supplier Name 12 DME/DDE OKAY MSV80 D_MOTOR 7602220 4D57 0000 13 00 0.0.0 0.0.0 0.0.0 255.255.255 24.09.2007 Siemens Motorelektronik MS 80 6 Zylinder N51/N52K WinKFP would no longer work if I did Comfort -> Update ZUSB. However I managed to use the Choose ZUSB option of WinKFP, selected the MSV80 and then found a version (7603196) that reported a Hardware Number of 7602220. I decided to risk it and programmed it. It programmed successfully and the whole thing mostly came good. Car started no problem, idled smoothly and even drove *mostly* OK. I seems a little out of puff in the top end though (maybe code 2AA9 below). However the ECU is now flagging these 3 new codes that weren’t there before and won’t clear (some for obvious reasons): 2AA9 DME: variable intake system, servomotor 2: activation 2FA3 DME: No coding 2FA4 DME: Incorrect data record I don’t seem to be able to find much about these errors in particular but presume in particular I need to code the DME now the firmware has been changed. However firstly I want to make sure I have the right firmware. How do I find out which ZB I should use for my particular engine / ECU combination since that ECU seems to be used for numerous different motors for a start which will have different maps etc? If I do the Update ZUSB again it suggests another new ZB (7606474) but that has a different hardware version (7605429). Second, should I just code the DME and hopefully that will resolve the error codes? What is the best way to do this? Thanks guys. |
09-11-2015, 05:12 PM | #4 |
Private
17
Rep 84
Posts |
Thanks. I was toying with doing that but it does seem to be a bit of an involved process. I'm probably at the point though where spending a few hours to get it out and back in is going to be necessary.
|
Appreciate
0
|
09-11-2015, 06:54 PM | #5 |
Colonel
529
Rep 2,503
Posts |
MSV80 has 23 ZB numbers for that HW-NR
You have the correct hardware number but wrong ZB-NR variant. PM me you vin... I think update ZUSB in comfort mode with VIN will choose the correct variant for you though... |
Appreciate
0
|
09-12-2015, 08:00 AM | #6 |
Private
17
Rep 84
Posts |
So to be clear 7602220 is the hardware number. Is the hardware number just the BMW part number i.e. I can physically check it by looking at the DME? It's a little confusing since that same hardware partnumber can be used on multiple fairly different motors. Is that where the ZB number comes in which is essentially the firmware version so really for a complete unit you need the correct pairing of hardware and firmware.
If I use comfort mode now that the ECU is working (it wouldn't work after the failed flash) it selects a new ZB Nr which if manually selected has a different Hardware number. Should it do that or is that because I've manually selected a wrong ZB Nr? Currently it says 7606474 but that has a different hardware version 7605429. I don't think that was my original number but can't be sure. I've sent you a PM with my VIN. Was hoping you'd chime in after reading a bunch of your posts whilst I searched for answers before posting. Thanks. Last edited by Shonky; 09-12-2015 at 08:06 AM.. |
Appreciate
0
|
09-12-2015, 03:51 PM | #7 |
Colonel
529
Rep 2,503
Posts |
That new hardware number is for an RMFD 'remanufactured' ECU. Do you know the history of your vehicle? Has it ever had DME replaced.
If you look through realoem re your vin you will see the part revisions. To be honest, I would double check the label on the DME. Alternatively you could find a member with the same vehicle from same period and region and check their UIF for a suitable zusb number... |
Appreciate
0
|
09-12-2015, 05:03 PM | #8 |
Private
17
Rep 84
Posts |
Ok. I'll get the DME out then it seems. Much more likely than finding another car I can read the UIF data from. Hopefully it has the right labels on it. From photos I can find sometimes it seems they don't always have the second sticker with the info I think I'm looking for - just the main part number.
Is there a limit to the number of times I can flash this? It did say something like 1 time remaining when I flashed it both times. I read mention of a programming history via WinKFP. Might that tell me what I need to know? To my knowledge the DME hasn't ever been replaced although the only number I'm sure of is the 7602220 which indicates 9/1/2009 onwards over a year after the car was built so perhaps it has been replaced back then under warranty. I am the third owner but it had been under full BMW warranty all the time I before so if it had been replaced it was by BMW. The remanufactured number is only what it's saying if I manually choose the ZB Nr it's proposing to upgrade to. Thanks a lot for your help so far. |
Appreciate
0
|
09-12-2015, 07:46 PM | #9 | |
Banned
522
Rep 1,527
Posts |
Quote:
|
|
Appreciate
0
|
09-12-2015, 09:37 PM | #10 |
Private
17
Rep 84
Posts |
This is my current configuration (which I think is basically the defaults - I set this up a while back). I've found other setups showing fast baudrate set, test checksum cleared, the two tracelevels set to 1.
Is that what you mean regarding configured properly or just that it's working properly which mine does seem to be doing? |
Appreciate
0
|
09-12-2015, 11:04 PM | #11 |
Private
17
Rep 84
Posts |
I pulled the DME and now I'm a bit more confused. 7602220 appears no where on the DME. See photo below. It does appear to be the original but I'm not sure what would tell me that. The manufacture date seems right at least. The VIN and serial numbers removed but all match the car.
RealOEM says 7581123 is not fitted to anything but looks up as the right part with a number of superseded versions: http://www.realoem.com/bmw/enUS/partxref?q=7581123 The other numbers (I'm pretty sure all are correct - they're a little faded but just legible) Top label 7580866 Bottom label Correct VIN 7568566 7581123 (part number repeated) 7580866 (repeated from the top label) 7580866 does appear in the MSV80.HIS file in three lines which I understand is the old version, new version MSV80.HIS(1205): 4558080,7580866,00,MW MSV80.HIS(1206): 7580866,7587236,01,MW MSV80.HIS(1791): 7576602,7580866,00,MW When I did the initial upgrade that failed from whatever version I had installed it picked a version starting with 8xxxxxx I'm quite sure. So how do we get from 7580866 to an 8xxxxxx version? Or how did the 7602220 hardware number come to be? There's no 7580866 versions that I can see in the folder either. I await your wisdom Last edited by Shonky; 09-13-2015 at 06:14 AM.. |
Appreciate
0
|
09-12-2015, 11:30 PM | #12 | |
Private
17
Rep 84
Posts |
I found I was able to read some history with the Read UIF function of WinKFP:
Quote:
Soooo.... I need to find 7580866 I think to get back to where I was at least and then maybe I'll need to code the DME and those errors will go away at least. Still I don't understand why the history for 7580866 shows only a new version to 7587236 and it has no further upgrades and why there's no 8****** path but perhaps I'm misreading the .HIS files etc. Sorry for the wall of text but I like to be thorough Last edited by Shonky; 09-12-2015 at 11:52 PM.. |
|
Appreciate
0
|
09-13-2015, 04:21 AM | #13 |
Colonel
529
Rep 2,503
Posts |
If: 7587236 is the newer version of your assembly number from your UIF read then that is what you need. I would stick with that...
Maybe the HIS file wasn't updated when the latest 8******* zusb was added? Just a though. I'd try the update, the clear the fault codes. |
Appreciate
0
|
09-13-2015, 04:43 AM | #14 |
Private
17
Rep 84
Posts |
Thanks. The problem is that 7587236 only exists in the .HIS file. There is no other reference to it in the latest v54 DATEN and manually entering it gives an error to that effect. Would there be a more complete DATEN possibly? This is supposed to be the full one I believe.
Somehow though WinKFP decided to pick a 8xxxxxx version earlier. That should be from the .HIS file right? |
Appreciate
0
|
09-13-2015, 05:04 PM | #17 |
Private
17
Rep 84
Posts |
Ok v54 I thought was latest. I presume any newer isn't going to be any help. Either way it doesn't have what I need so I'm trying to get older versions.
V48 doesn't either. V28 is the version that matches the I level of the factory build. It looks to have been updated to the I level matching v45. Finding the old DATEN files is not so easy. |
Appreciate
0
|
09-13-2015, 05:31 PM | #18 | |
DOPE
148
Rep 758
Posts |
Quote:
|
|
Appreciate
0
|
09-13-2015, 06:34 PM | #19 |
Private
17
Rep 84
Posts |
Hi
Thanks. v48 is no go and v41 which I just found is the missing it as well unfortunately. So if anything I need to go older. I don't quite get it. It seems they are all referring to versions that don't exist, yet before my failed flash, WinKFP was quite happy to upgrade to something it had available. I just can't figure out how to calculate what version that should be. |
Appreciate
0
|
09-13-2015, 07:41 PM | #20 |
Colonel
529
Rep 2,503
Posts |
The information as to what variant the zusb refers to is held within the matching *.0da file.
You could use a cool little app like BMW intelhex to bin converter to read this information from the latest *.0da files in the MSV80 folder. You should then get what variant that zusb number refers to e.g engine type, KW power, etc etc. Find one that matches your vehicle then use it. |
Appreciate
0
|
09-13-2015, 09:22 PM | #21 |
Private
17
Rep 84
Posts |
OK. Yep I think I understand that. the 0pa is the firmware and the 0da files contain the maps. So often there's one 0pa file that works with multiple 0da files for multiple different engines/chassis.
I'll give that application a go. It looks like it might give me enough information to select a 0da file and then I can work backwards to a ZB. Unfortunately it seems unable to decode them like your screen shot. I get: case ":": carMake = "BMW"; carType = ": Muster-SW KW_43/2009"; softwareID = ":"; ecuType = "MSV80"; engineType = "Muster-SW KW_43/2009"; break; or case ":": carMake = "BMW"; carType = ":"; softwareID = ":"; ecuType = "MSV80.1"; engineType = "Test-SW"; break; Perhaps I have found an older version. Hmm.. latest version gives the same kind of info for the MSV80 DME. No real information. I have the last source code for it so I might have a bit of a look around and see what I can find. |
Appreciate
0
|
09-13-2015, 09:49 PM | #22 |
Private
17
Rep 84
Posts |
Yeah unfortunately all the helpful data just comes from text fields at the start of the 0da and 0pa files. It's not encoded in the binary anywhere so that little app doesn't provide any more useful info.... It seems whoever builds the MSV80 is not properly creating any of those fields.
I have a lead on an old data folder I think so maybe that will help me out at least to get the original version and I can decide to upgrade from there. |
Appreciate
0
|
Bookmarks |
|
|