E90Post
 


Coby Wheel
 
BMW 3-Series (E90 E92) Forum > E90 / E92 / E93 3-series Technical Forums > BMW Coding > How to find correct ZB number (DME)



Reply
 
Thread Tools Search this Thread
      09-14-2015, 02:31 AM   #23
Shonky
Private
Australia
16
Rep
84
Posts

Drives: F31 320i, E46 M3
Join Date: Jan 2014
Location: Brisbane, Australia

iTrader: (0)

Wow this is doing my head in .

I found SSS Progman v32 with a set of data files mid 2008 i.e. about 8 months after my car was built. Should be good for information.

1) It has a completed MSV80.ATS file. My production code is VW52 and there are two specific lines for it

;Fahrzeugzuordnung (Auftrags-Steuerdatei) vom 11.07.2008 08:55
;TAIS-Abfragedatum (ab) 24.07.2008
FZG;LA;SA;ZB_NR;SE_VS
VW52;;;7592816;SE
VW52;;;7594564;SE

Great. Some brand new to me ZB numbers.

2) If I look up those numbers it pulls in a bunch of other production codes in the ATS file but all (I think all - I've not checked every one) E9x 323i with the 140kW N52B25U1 engine. So we're in the ball park at least but why are there two entries?

2) The ZB that's on the sticker on the DME and in the plant/factory data read via INPA (7580866) is referenced in the same file as being for a WB12 which is a E92 323i Coupe.

;Fahrzeugzuordnung (Auftrags-Steuerdatei) vom 11.07.2008 08:55
;TAIS-Abfragedatum (ab) 24.07.2008
FZG;LA;SA;ZB_NR;SE_VS
WB12;;;7580866;SE
WB12;;;7587236;XX
WB12;;;7592816;SE
WB12;;;7594564;SE

WB12 refers to a number of others above including the same two ZB numbers given for the VW52. It also has the 7587236 which is listed as the upgrade in the latest data. Anyone know what the XX vs SE means in the "SE_VS" column?

3) There is still no entry for 7580866 in the MVS80.DAT file nor 7587236 so I can't program these specific ZB numbers.

4) There are for the 7592816/7594564 entries listed against the VW52.

Should I take a punt and try one and hope for the best. I was really hoping for something more definitive though like the original ZB or at least the upgrade it points to. What should I do to ensure I don't hit any upgrade limits?

Any further ideas? Maybe find older version again? v28 should be about the oldest I can go so I can't be that far off. I'd be surprised if versions were removed within 6 months. I still think there must be another source of data or linking of versions somewhere that I'm not seeing.

Confused....
Appreciate 0
      09-14-2015, 08:31 AM   #24
Sensible_
Colonel
527
Rep
2,505
Posts

Drives: 2008 E90
Join Date: Feb 2012
Location: London

iTrader: (1)

What is your I-level? If the vehicle hasn't been updated it should have original I-Level. You can look at the spreadsheet to see the daten version.

Read it with tool32:

Tool32-->e89.prg-->I_STUFE_LESEN
Without any arguments.
Appreciate 1
      09-14-2015, 08:46 AM   #25
Shonky
Private
Australia
16
Rep
84
Posts

Drives: F31 320i, E46 M3
Join Date: Jan 2014
Location: Brisbane, Australia

iTrader: (0)

It does appear my I-level has been upgraded although none of the modules appear to reflect that.

I_STUFE_WERK = E89X-07-09-520
I_STUFE_HO = E89X-11-09-506
I_STUFE_H__BACKUP = E89X-10-06-502

First is factory (Werk) right and correlates to the build date of 10/2007, HO I presume is the current version. I bought the car in late 2013 so not sure what happened around 09/2011 exactly if anything but I know it was sold by BMW as an approved used about 11/2012.

If I go by the E89X-11-09-506 version that gives me a daten version of P2.45.0, P2.45.1 or P2.45.2. I've not found a v45 of it yet but have v41 and v48. Would they be that different that I'd need to get exactly v45? Even the old v32 refers to the 7580866 and 7587236 but perhaps it had been upgraded after all and what I read via WinKFP regarding the history is misleading? It would at least explain the differing hardware version.
Appreciate 0
      09-14-2015, 08:57 AM   #26
Sensible_
Colonel
527
Rep
2,505
Posts

Drives: 2008 E90
Join Date: Feb 2012
Location: London

iTrader: (1)

Ok, so I've been thinking. Maybe you don't actually need the old daten. You just need to trick winkfp. As far as I known winkfp reads the UIF to decide what to update it to. So if you were to edit the uif to your original state then update it should be correct.

Checkout
for UIF writing with tool32. Obviously back it up first...
Appreciate 1
      09-14-2015, 09:14 AM   #27
Shonky
Private
Australia
16
Rep
84
Posts

Drives: F31 320i, E46 M3
Join Date: Jan 2014
Location: Brisbane, Australia

iTrader: (0)

OK. That looks feasible and you're right regarding not really needing the old version. I only have the ZB number though. I don't have the pa0 or da0 numbers or anything else.

The video is a little confusing as it jumps around so quickly, so will need to watch it a few times to follow what's being done exactly.

Thanks again.
Appreciate 0
      09-14-2015, 09:51 PM   #28
Shonky
Private
Australia
16
Rep
84
Posts

Drives: F31 320i, E46 M3
Join Date: Jan 2014
Location: Brisbane, Australia

iTrader: (0)

Ugh. There's no seed_key function to unlock the MSV80 ECU and it won't let me write....

apiJob("12MSV80","aif_schreiben","WBAVW52010****** *;081007;7580866;7580865;7568560;011111;12345;0;00 49QK0MG10S","")

Satz : 0
OBJECT = 12msv80
SAETZE = 1
JOBNAME = aif_schreiben
VARIANTE = 12MSV80
JOBSTATUS =
UBATTCURRENT = -1
UBATTHISTORY = -1
IGNITIONCURRENT = -1
IGNITIONHISTORY = -1
Satz : 1
JOB_STATUS = ERROR_ECU_SERVICE_NOT_SUPPORTED_IN_ACTIVE_DIAGNOST IC_MODE
AIF_NUMMER = 2 00 02 ..
AIF_DATEN = 64 Bytes

There's a whole bunch of other functions but I can't find one that obviously unlocks things. There's quite a very quite dangerous ones in there though like erasing and writing flash.

Can't seem to find anyone else writing the AIF on an MSV80.

diagnose_ende is successful but still can't write with the same error.
Appreciate 0
      09-15-2015, 01:47 AM   #29
Shonky
Private
Australia
16
Rep
84
Posts

Drives: F31 320i, E46 M3
Join Date: Jan 2014
Location: Brisbane, Australia

iTrader: (0)

Nearly a disaster!

So after trying to trick WinKFP by changing the AIF I couldn't figure it out. It seems this ECU only has two AIF locations - the factory one and the current one so the arguments for the write command are a little different to that Youtube.

I didn't really want to go playing around too much in Tool32's writing/erasing functions so I decided to just bite the bullet and selected one of the ZB numbers identified in my old v32 data as being applicable to the VW52 but tracked it through to the latest in my v54 (8608460)

7594564 -> 7603112 -> 7609604 -> 8608460

I somewhat arbitrarily picked 7594564 over 7592816. It did have the original 7602220 hardware number I had initially found though so possibly more correct.

But then I kept having interface errors. Scarily WinKFP was giving me the error "programming mode failed 12MSV80, DIAGNOSE_MOD (ECUPM): ERROR_SECURITY_ACCESS_DENIED__SECURITY_ACCESS_REQU ESTED" followed by "IFH-0003 Datatransmission to interface disturbed" at random points during the flashing. Both ZB numbers were doing it as well as the old incorrect version I had flashed the other day. I thought I was stuffed after trying to get it to program for a few hours.

When it failed I thought it was because the voltage was dropping as every time it happened the fuel pump came on and the display flashed up a bunch of errors about DSC, ABS, flat tire monitor etc. It was on a small charger and eventually a bench supply was added too. I pulled the pump fuse but still had the problem and added a fuel pump error to the list . Eventually I rebooted my VM and closed everything on my host machine (not a lot). The laptop is old but not underpowered, has plenty of RAM, SSD etc. After doing that it finally programmed with the 8608460 ZB number. In hindsight I think what was happening was WinKFP was failing on its own and when it failed it allowed the rest of the car's modules to start back up and they started to send out their errors. It just looked like the modules starting was the actual problem and they were interrupting with the 22 or so flagged errors.

So, it started up fine with the new flash. Two of the errors flagged initially are gone on their own and it runs fine. The low rev hole it seemed to have with the random tune seems to be fixed. Even the EGS/DME comms error has gone now which was I think my problem with it not kicking down properly. It seems to drive better but I've only done an around the block so far and could probably do with a bit more learning. I might look at upgrading the EGS but after this I'm wary

I still have the "2FA3 DME: No coding" error but I presume that's fairly easily fixed/coded into the DME. It doesn't seem to cause any significant issues and I had been driving it with that plus the other two for a few days now with the random flash I found. Should that be a simple thing?

WinKFP reports it will just upgrade to the same version that's installed so I presume that means it thinks it's the latest. I'll probably never know but I'm going to take a guess and say this ZB is what it was trying to upgrade to originally before things all went bad. All I know is it started with an 8.

So not all the way there but pretty close now. Some choice words were being spoken when it wouldn't flash. Hopefully this might help anyone. My Googling kept bringing me back to this thread pretty quickly.

Thanks for your help guys, particularly Sensible_ . Again apologies for the wall of words but hope this might help someone someday....
Appreciate 0
      09-15-2015, 06:28 AM   #30
Sensible_
Colonel
527
Rep
2,505
Posts

Drives: 2008 E90
Join Date: Feb 2012
Location: London

iTrader: (1)

I wondered if sooner or later you would make an educated guess. I didn't want to suggest it incase it bricked the ECU I would have done the same though.

Glad it's sorted. It's a shame there isn't a complete revision history of module updates.
Appreciate 0
      09-24-2015, 12:18 AM   #31
vespa
First Lieutenant
211
Rep
245
Posts

Drives: 2011 335i
Join Date: Dec 2014
Location: Thousand Oaks

iTrader: (0)

How do you guys figure out the latest zusb for the module in question? I keep seeing references to things like "WinKFP will suggest..." but mine doesn't seem to be so helpful, it just gives a list of dozens of zusbs to choose from.

Specifically I want to flash the power kit firmware to my N55 DME but want to be ready to revert to stock in case the flash fails. My i-level is 2.51.3 which is older than the internet so I'm stuck with 2.55.0 which doesn't have my old zusb (8615764). How can I find an equivalent in 2.55?

Sorry for the off topic question but you guys seem to have sorted this issue better than most. Any help is appreciated.
Appreciate 0
      09-24-2015, 01:15 AM   #32
Shonky
Private
Australia
16
Rep
84
Posts

Drives: F31 320i, E46 M3
Join Date: Jan 2014
Location: Brisbane, Australia

iTrader: (0)

When you open WinKFP select Comfort Mode then Update ZUSB (Not Choose ZB or Enter ZB). Select the ECU family only, enter the VIN, OK, then Done, then Prog.ZB Update. When you do that it will tell you the old version and then the new version (which might be the same if there's nothing newer)

I think that's the right steps and buttons. There are numerous guides on a basic update.

You only tell it the ECU type normally but you can select a specific ZB for the ECU if you want. It then interrogates it and finds out what to upgrade to based on the history files and possibly others.
Appreciate 0
      09-24-2015, 09:10 PM   #33
vespa
First Lieutenant
211
Rep
245
Posts

Drives: 2011 335i
Join Date: Dec 2014
Location: Thousand Oaks

iTrader: (0)

Thanks Shonky! That's the trick I was missing! I wasn't hitting "Done" and even if I had, I would have been afraid to hit "Program".
Appreciate 0
      10-10-2015, 05:41 PM   #34
Shonky
Private
Australia
16
Rep
84
Posts

Drives: F31 320i, E46 M3
Join Date: Jan 2014
Location: Brisbane, Australia

iTrader: (0)

Bit of an update on this. I found a VM with (I think) v28 DATEN files.

MSV80.ATS has :
VW52;;;7580866;SE

MSV80.DAT
7580866,7568560,7581123,A,7580865DA,0FFFFFFFFFD,00 0,1 1

...all of which appear to match the DME label exactly

Bottom label
Correct VIN
7568566
7581123 (part number repeated)
7580866 (repeated from the top label)

So 7580866 for the ZUSB Nr and the data file ie map is "less by 1". All lines up.

Also the 0049QK0MG10S reference appears in the 7580865.0da so it all points to matching numbers etc.

Only number I don't have a reference to is 7568566 on the label.

As I'm still not convinced I have the right version I'm probably going to attempt to flash that older version I think to get me back to square one. I still have the DME coding error and whilst the car drives quite well, I would prefer to know it's the right version. Then I can upgrade from there again. Finally I also want to look at upgrading the EGS which is the whole reason I started on this (downshifts can be quite clunky)

Wish me luck....

Last edited by Shonky; 10-11-2015 at 02:25 AM..
Appreciate 0
      09-11-2018, 02:38 AM   #35
General.Massacre
New Member
South Africa
15
Rep
23
Posts

Drives: 2013 F13 640d MSport
Join Date: Sep 2018
Location: South Africa

iTrader: (0)

Quote:
Originally Posted by Sensible_ View Post
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...
Hi Sensible

Sorry for the call out on the thread, was hoping to try PM you, but i see your profile does not have that option.

I am from South Africa, and i have a 2009 E92 335i with DCT gearbox.
first off, i have NO knowledge yet about WinKPF, or understanding the programs to get most of the info here, as im still learning, but ive been reading alot, especially the ZB numbers.

From what i understand, the ZB number is what is found in MHD read as "Factory Software/Current Software" numbers, however, these numbers dont match my VIN on RealOEM under the DME section. (i have MSD81).

Perhaps i am wrong here, and not understanding or following the thread correctly.
Would be great to talk further if you have the availability.

One of the reasons i am looking at this, is to find out why my Launch Control doesnt work on the car. (i have followed the Sequences from the Vehicle handbook, as well as the advice online, and no help. my only conclusion, is that it could be something with the DME, but i cant be certain at this point, hence i am researching.

Out of interest, i am currently JB4 + Pump BEF with Kickdown delete for now. (LC was not working prior to me blocking the KickDown.

thank you in advance.
Justin
Appreciate 0
Reply

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



All times are GMT -5. The time now is 02:32 PM.




e90post
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
1Addicts.com, BIMMERPOST.com, E90Post.com, F30Post.com, M3Post.com, ZPost.com, 5Post.com, 6Post.com, 7Post.com, XBimmers.com logo and trademark are properties of BIMMERPOST