[torr]

So after trying to figure this out on my own for the last 2 months and before throwing in the towel I am asking for HELP.
My problem (N55 + INPA + MEVD176K.IPO). INPA is fully functional for my 2011 335i N55 with the exception of loading
the MEVD176K.IPO engine tables. INPA incompatible with current Loader:error I305. I have failed with every version of INPA available multiple times.
Prior to DMM Update several months ago INPA was working using the MEVD17KW.IPO. If I try using the MEVD17KW.IPO now INPA error states somthing to the
effect of "looking for MEVD17KW but found MEVD176K. Attached below is a screen of the error. while using different versons of INPA gives same error
but with different [5.32.x] number.
Any help on this would be greatly appreciated.

[torr]

embarrassing it was the MEVD172.ipo

[AnthemX]

Hi Torr,

I've got the same issue with my 2011 335xi N55. Unfortunatly, the MEVD172.ipo file isn't working for me. Any thoughts?

[808AWD325xi]

Originally Posted by AnthemX

Hi Torr,

I've got the same issue with my 2011 335xi N55. Unfortunatly, the MEVD172.ipo file isn't working for me. Any thoughts?

There are several MEVD variants and hence, numerous scripts.

To determine which script you need, you need to know which SGBD is in use. To find out, display all installed control modules with INPA. See question 5. of my FAQ:
http://www.e90post.com/forums/showth...8#post18933848

What is the SGBD for your DME?

[AnthemX]

Weirdly SGBD is blank? Any ideas?

[AnthemX]

Sorry wrong photo before

[808AWD325xi]

Originally Posted by AnthemX

Weirdly SGBD is blank? Any ideas

More than likely none of the factory MEVD17.x.x scripts will be able to communicate with your DME because in the source code they define the supported SGBD(s). At runtime the script queries the DME and if a supported SGBD is found, program execution continues, otherwise it's halted.

Ironically, the MSD80 script that you ran in the photo above is one of the few that doesn't perform any such validation at start-up. Hence why it was able to run even though you don't have a MSD80 DME.

Originally Posted by AnthemX

Sorry wrong photo before

Based on the part number (7645283), you definitely have a MEVD17.2 DME. My educated guess is that the SGBD should be MEVD17KW. In which case the proper script would be MEVD17KW.IPO.

Have you tried the MEVD17KW.IPO script?

With regards to the missing SGBD information, that is definitely weird. Have you flashed your DME in the past with WinKFP or some other tool?

[AnthemX]

Thanks for the reply. MEVD17KW.IPO was part of the coding package I have downloaded and it doesn't work with my car. I have tried MEVD176K and MEVD172 without any success. The only time the DME has been touched was by the dealer when they installed the PPK when I purchased the car. Could that have anything to do with it? It was a long time ago but I remember the SA saying they had a hard time with it. But then again, I was the first car they had ever done the PPK on.

[808AWD325xi]

Originally Posted by AnthemX

Thanks for the reply. MEVD17KW.IPO was part of the coding package I have downloaded and it doesn't work with my car. I have tried MEVD176K and MEVD172 without any success. The only time the DME has been touched was by the dealer when they installed the PPK when I purchased the car. Could that have anything to do with it? It was a long time ago but I remember the SA saying they had a hard time with it. But then again, I was the first car they had ever done the PPK on.

It could possibly have something to do with it, which is why I asked if the DME had been flashed. It's almost as if the UIF information is corrupted.

One suggestion would be to run Tool32, open the D_MOTOR.GRP group file and run the identification job. It should return the variant string.

[AnthemX]

Thanks again for the info. I'll follow up next week when I get back home and have a bit of time to work on the car.

[AnthemX]

Originally Posted by 808AWD325xi

It could possibly have something to do with it, which is why I asked if the DME had been flashed. It's almost as if the UIF information is corrupted.

One suggestion would be to run Tool32, open the D_MOTOR.GRP group file and run the identification job. It should return the variant string.

Tried to open the D_MOTOR.GRP and got the following error. EDIABAS Fehler 102 : SYS-0012: IDENTIFICATION ERROR. Any ideas?

[808AWD325xi]

Originally Posted by AnthemX

Tried to open the D_MOTOR.GRP and got the following error. EDIABAS Fehler 102 : SYS-0012: IDENTIFICATION ERROR. Any ideas?

I would recommend reprogramming the DME. It appears that something went wrong when the dealer flashed the PPK.

I can provide you with the latest applicable ZB number for the PPK flash.

Can you post the chassis type code and current ZB number?

To determine the type code, you can input the last 7 digits of your VIN into a VIN decoder:
http://www.etkbmw.com/bmw/EN/vin/decoder/online/

To determine the current ZB number, display the UIF (User Information Field) data for all installed modules with INPA...E90 -> Select E90 -> Functional Jobs -> <F3> User information field:

[jame92r]

Any luck with getting n55 to work with inpa??