[GreaseJunkie]

Hey all, my e90 was built on 5/13/2005. Because of this early build, I am missing a few noticeable functions such as DRLs and Car Venting. I realize these seem minor, but looking at the bigger picture, if my FRM and Kombi are so old and out of date, then the whole car is probably running some very archeaic software. What I am looking to do is update every module in my vehicle to the most current (and easily attainabl software.

I currently have BMW Standard Tools downloaded (BMW Coding Pack May 2013) and running on a Windows xp machine, I can use NCS Expert to successfully code my car, but INPA and WinKFP are useless, and I get missing file errors whenever I try to do anything. I'm guessing I might be missing some files, but before I go and download another set of BMW Standard Tools and 25gb of probably-gonna-be-corrut daten files, I was wondering if there was an alternative method to getting my car updated?

[cryptomit]

You need to download a big 10GB pack of daten to your E90 and import them to WINKFP, then you are ready to update your modules. However it is not so easy as it looks, you should have a battery tender to keep proper voltage during updating process.

I assume that you have K+DCAN cable. When you have ICOM it is really comfortable to use ISTA-P to make sure that an Integration Level is proper.

[GreaseJunkie]

I've downloaded several. From v41 to v50, they just don't seem to work.

I am using a K+DCAN cable currently and tending the battery with a 14v charger.
I found a version of ISTA D/P with a built-in ICOM emulator that's downloading now

[joe335in54]

Originally Posted by GreaseJunkie

I've downloaded several. From v41 to v50, they just don't seem to work.

I am using a K+DCAN cable currently and tending the battery with a 14v charger.
I found a version of ISTA D/P with a built-in ICOM emulator that's downloading now

like the last person said you neeed 10gb of data to update your modules....

the regular spdaten files flying over the internet are not the complete files so you wont be able to update your modules until you download the complete daten files for e89 should be around 10gb of data.

[GreaseJunkie]

And as I said before, I've tried several, and they're at least 10gb apiece, and had no luck. But I guess I'll just keep downloading. I wish I could just find a good source

[GreaseJunkie]

Originally Posted by joe335in54

like the last person said you neeed 10gb of data to update your modules....

the regular spdaten files flying over the internet are not the complete files so you wont be able to update your modules until you download the complete daten files for e89 should be around 10gb of data.

Sorry to come off as rude, I've just wasted several days trying to download files that don't seem to work.

[Sensible_]

The BMW coding pack may 2013 works well.

When using INPA just google the missing files. You will find them. I had this problem.

ISTA-P should really only be used with an ICOM and a powerful laptop.

With regards to your problem with daten files, instead of just saying 'it doesn't work' please specify exactly what isn't working. Are you getting an error code? Then everyone can help.

[GreaseJunkie]

Originally Posted by Sensible_

The BMW coding pack may 2013 works well.

When using INPA just google the missing files. You will find them. I had this problem.

ISTA-P should really only be used with an ICOM and a powerful laptop.

With regards to your problem with daten files, instead of just saying 'it doesn't work' please specify exactly what isn't working. Are you getting an error code? Then everyone can help.

Thanks Sensible. I'm actually downloading your ISTA-P Lite version right now to try on my more powerful laptop, but can I use it on an x64 machine?

The error message I get in INPA is about missing files, cant remember exactly but I have a screenshot on my camera at home , I will google them as you suggested. And see what I find tonight after work.

Essentially, I am trying to use INPA to get my ZUSB, when I try to read a module, I get an error thay something is missin. I will report back to you guys on the exact message when I get a chance

[GreaseJunkie]

And, as usual, thanks for the responses and info from all!

[GreaseJunkie]

Error reads:
C:\EC-APPS\INPA\SGDAT\EXX. ipo(1) : error I300: Error opening object file

[Sensible_]

Originally Posted by GreaseJunkie

Error reads:
C:\EC-APPS\INPA\SGDAT\EXX. ipo(1) : error I300: Error opening object file

http://netload.in/dateiPC6CItSuFE/EXX.IPO.htm

Then place the EXX.ipo file in:

C:\EC-APPS\INPA\sgdat\

-------

INPA should now run and you can read UIF to get the info. Ignore any language mismatch warning.

[GreaseJunkie]

Originally Posted by Sensible_

http://netload.in/dateiPC6CItSuFE/EXX.IPO.htm

Then place the EXX.ipo file in:

C:\EC-APPS\INPA\sgdat\

-------

INPA should now run and you can read UIF to get the info. Ignore any language mismatch warning.

You sir, are the man. No more errors. (except language, but I've been there before) Still downloading daten files at the moment, but once theyre all done I will update everything and see what happens. I'll report back tomo rro. Thanks again!

[GreaseJunkie]

Got everything up and running last night, MUCH THANKS TO ALL. I was able to successfully update my KOMBL and LCM60 modules, however nothing changed. Oh well I suppose. However I tried to update my DDM/DME this morning and upon entering the ZUSB in winKFP, I get this error:

Assembly Identification Number not found in the files determined by "xxkfconf. Da2

Does this mean I have a bad file somewhere? Or is there a different process for updating the DME? I'm only trying because its the only module that shows a SW version of 0.00.00, what's up with that?

[Sensible_]

Glad it's working for you. The error you are getting is to do with configuration. Did you import the data to winkfp correctly? Try using bmw coding tool to make sure all data is imported correctly.

Although, reading your post again. Why enter zusb number at all? Use 'update zusb' and enter your vin. Then chose module family.

[GreaseJunkie]

I initially tried to update with the BMW Coding Tool, but it kept freezing, and would ask me to close the program. I tried 2x after a reboot, spent almost 2 hours waiting. Then I just reinstalled winKFP and updated them manually, and so far so good until I tried the DME.

Trying your suggestion, I couldn't get it to work simply because I dont know which ecu family to select. Would it be one of the 7 options that start with DDE____?

[GreaseJunkie]

Interestingly enough, when I check ECU update on BMW Coding Tool after I enter my ZUSB, it says:

Nothing found, check assembly line data

[Sensible_]

Originally Posted by GreaseJunkie

Interestingly enough, when I check ECU update on BMW Coding Tool after I enter my ZUSB, it says:

Nothing found, check assembly line data

Are you selecting the correct ecu family for your DME? I think for your vehicle it will be MSV70. Bu double check that as its off the top of my head.

[GreaseJunkie]

I don't know what ecu family to select. The only way (I know) to find that out is by clicking Enter ZUSB, enter the 7 digits, and then it will highlight the correct ecu family. Unfortunately I get file not found errors after I enter the ZUSB

[Sensible_]

Originally Posted by GreaseJunkie

I don't know what ecu family to select. The only way (I know) to find that out is by clicking Enter ZUSB, enter the 7 digits, and then it will highlight the correct ecu family. Unfortunately I get file not found errors after I enter the ZUSB

But this is wrong way...and risky.

The safest way is to:

Instructions on how to update a module with WinKFP.

0 - Choose comfort mode.
1 - Select F3:- Update ZUSB
2 - Select ECU type and the ECU will appear along with a list of part numbers.
3 - Select ok and the main menu will re-appear
4 - Select VIN and enter the cars VIN no. and select OK. (FULL VIN)
5 - Select Done
6 - Select Prog. ZB_update, you will be asked to confirm the update, Winkfp wil state the number of times the module can be re-programmed.
7 - Sit back and wait.

Your ECU family will be MSV70 I think. Double check this. T putting your vin into realoem.com and under engine electronic system / control units it will shows your your DME part number and type.

[GreaseJunkie]

You were right, realoem said MSV70. And it worked perfectly. But it only took about 5 mins. Is that right for flashing a DME? I was under the impression it was gonna take close to an hour over a DCAN with a slow computer... I'm a little suspicious because (and I know that there's not a lot to notice) but I've updated all the modules and not a thing has changed. I was mainly looking out for the newer DSC off icon, and control and function of DRLs thru the BC stalk. Am I wrong to think this should be addressed thru an update? Or did I just not actually update anything?

[wildcatcrazy]

Originally Posted by GreaseJunkie

You were right, realoem said MSV70. And it worked perfectly. But it only took about 5 mins. Is that right for flashing a DME? I was under the impression it was gonna take close to an hour over a DCAN with a slow computer... I'm a little suspicious because (and I know that there's not a lot to notice) but I've updated all the modules and not a thing has changed. I was mainly looking out for the newer DSC off icon, and control and function of DRLs thru the BC stalk. Am I wrong to think this should be addressed thru an update? Or did I just not actually update anything?

You may need to go back in code the module to turn those features on.

[Sensible_]

You need to update the DSC module, you should really update the EGS as well. And EKP should be updated with DME as they work together.

Together you may notice a small difference, but updating modules with stock bmw software isn't going to change the car that much.

Your DME is MSV70, maybe it will take longer for a full flash, but for update no problem.

But please be careful, I guess you are not using a power supply? At least check your vehicles battery voltage first as at any point you might lose the required voltage and brick the module you are flashing.