E90Post
 


TNT Racewerks
 
BMW 3-Series (E90 E92) Forum > E90 / E92 / E93 3-series Technical Forums > BMW Coding > N55 PPK Flash DIY



Reply
 
Thread Tools Search this Thread
      12-06-2016, 07:14 PM   #1
AJL
New Member
United_States
1
Rep
11
Posts

Drives: 2011 335i M Sport
Join Date: Oct 2015
Location: Bradenton, FL, USA

iTrader: (0)

N55 PPK Flash DIY

After a few months of pondering whether or not I want to try, I’ve finally gone through with it and attempted the BMW PPK flash on my car. Honestly, the most difficult and time consuming part was setting up the software. Actually flashing the car only took a couple minutes (once I worked out some initial issues). Before you say it didn’t take because it flashed in a couple minutes, I can assure you that it did. After flashing, there is a very noticeable difference in the exhaust sound and my butt dyno seems to indicate a change.

Because I couldn't find a detailed DIY, only vague overviews of what to do, I figured it was about time for someone to write one. I am not an expert at these things, I freely admit it. If you notice an issue with my instructions, please let me know and I will correct it.

Vehicle information:
• Model: 335i (M Sport)
• Production Date: 5/2011
• Engine: N55
• Transmission: Automatic
• Market: US
• ECU/DME: Mevd172 (or just 17)
• Completely stock except for:
o ER Chargepipe (OEM one blew up on my way home after buying the car!)
o Alpina B3 transmission flash (I highly recommend this as well, it’s loads of fun)
Workstation Information:
• 17” Macbook Pro
• Windows 10 fresh install specifically for this purpose
• Full E89/E9X V53.3 SP-Daten files
• Mike’s Easy BMW Tools Package
o INPA 5.0.6 (in English)
o EDIABAS 7.3.0
o NCS Expert 4.0.1 (in English)
o NCS Dummy 0.6.0.4
o Tool32 4.0.3
o WinKFP 5.3.1
o BMW Coding Tool v2.5.0
o Came with basic SP-Daten v53.3 files for diagnostic purposes. I loaded full Daten files for coding after installation
NOTE: The USB Cable drivers that were bundled with the tool package did not work correctly and caused the flashing to fail on my first attempt. There were not issues after the correct WHQL certified drivers were installed.

---

The following are the steps I followed to successfully flash the BMW PPK (Not including updating the SP-Daten files, as this is already a well-documented procedure)

DISCLAIMER:
I offer this information with NO GUARANTEE that it will work, nor do I guarantee that it will not break your vehicle. I am not liable for any damage to your vehicle, person or ego. I do not guarantee that this information is completely accurate. Follow these steps with extreme care, do your research, don’t break your car. If you feel uncomfortable with modifying your vehicle, then pay a professional to do it. Don’t try and blame me.

If you have no prior experience with these BMW tools, I recommend you learn about them before attempting this.


1. IMPORTANT: Connect your car to stable power supply. I used a 15 amp battery charger which managed to hold the voltage at a minimum of 12.7v throughout the whole process. I also recommend turning off all lights and other power consuming devices on the vehicle.
2. Get in, close the door, plug in your OBD cable, put the key in the ignition, press the start button without the brakes pressed.
3. Open INPA. Battery and Ignition should both be ON. If ignition is not on, you didn’t press the start button!
4. Next, we are going to get the current ZB with INPA
a. Choose your chassis
b. Choose Functional Jobs
c. Then choose “Read User Information Field”. This lists your current ZB (Zusub) numbers for each module. Save this report for reference purposes.
My DME/DDE ZB No. before flashing was 8615734
5. Close INPA
6. Now it’s time to flash the DME using WinKFP
a. Open WinKFP and select “Comfort mode”
b. Select “Enter VIN” and put your VIN in carefully
i. Double check to make sure you have entered the VIN number correctly!
c. Now select “Choose ZUSB”
d. Select the correct option from “ECU Family” for your vehicle. In my case, the correct option was MEVD17
e. Next select the PPK ZB-Number that is appropriate for your vehicle. I used 8639146, and that seemed to work. There are charts floating around the internet to help you determine the correct number for your vehicle.
f. Select “Done” and if there are no communication problems (yet), the main menu will re-appear with a new option “Prog. ZB_update”
g. You will be asked to confirm the update and WinKFP will then state the number of times the module can be re-programmed.
h. The update will begin. It only took a couple of minutes for my flash to complete, however this may vary depending on the speed of your computer, the battery charger or your vehicle.
i. When complete, WinKFP will let you know.
NOTE: The first time I tried this flash, I received error code 211, and my car went a little crazy (i.e. the windshield wipers wouldn’t stop). Turning the car off and back on fixed this, and my car still started after, albeit with a CEL. In my case, the problem was caused by bad drivers for my K+DCAN cable. After installing the correct drivers, I did not have a problem.
7. Now we need to write a blank FSW_PSW.MAN file to 62BMO or 63BMO from NCSExpert
a. This step is to remove an encoding error that the car will throw supposedly (I did not check, and my CEL was already on)
b. Open NCSExpert and load the correct profile (Mine is called FSW PSW MAN, there are plenty of tutorials on setting this up)
c. Press “VIN/ZCS/FA” (F1) and then press “ZCS/FA f. ECU” (F3)
d. Select your chassis code. (E89 = E9X)
e. This will bring up a list of ECUs. CAS, FRM and NFRM. Select CAS. NCSExpert will now communicate with your vehicle to pull the VIN and other needed info.
f. Now that the vehicle information is populated, click the back button to the main menu.
g. You should now see a button labeled “Process ECU” (Shortcut is F4). Press this and choose 63BMO.
h. Press the button labeled “Read ECU”. This will pull the current settings from the ECU into an FSW_PSW.TRC file in the NCSExpert WORK folder. If this step is successful, a NETTODAT.TRC file will open automatically.
i. In the WORK folder, there should be a blank FSW_PSW.MAN file, if not then create one.
j. Back in NCSExpert, press the button labeled “Change Job” and select the job “SG_CODIEREN”
k. Double check that you are on the correct module, then press “Execute Job”. This will write the blank FSW_PSW.MAN file to your ECU.
NOTE: NCSExpert is a dangerous tool and should be used with caution.


8. Finally, open INPA and clear the error memory
a. Shift+F2
b. Functional Jobs
c. F4 – Error Memory
d. F2 – Clear Error Memory
9. Turn the car off, then start it up and make sure you don’t have a CEL

10. I’m not sure if this step is necessary, but I’ve seen people say to do it before so I did.
- Button up your car, lock it and wait 15 minutes (so the car goes to sleep)
11. Enjoy the PPK!

Last edited by AJL; 12-06-2016 at 07:21 PM.
Appreciate 0
      12-07-2016, 08:25 PM   #2
Richards335
Private
Richards335's Avatar
4
Rep
78
Posts

Drives: 2011 335i Xdrive e92
Join Date: Oct 2015
Location: NYC

iTrader: (0)

what are the chances of "Bricking" your car if someone where to do this incorrectly?
Appreciate 0
      12-07-2016, 08:36 PM   #3
Sensible_
Lieutenant Colonel
146
Rep
1,594
Posts

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

iTrader: (1)

Quote:
Originally Posted by Richards335
what are the chances of "Bricking" your car if someone where to do this incorrectly?
If someone were to do it incorrectly then you have a 100% chance of bricking your car...

However, it isn't rocket science. You are simply flashing a module. The guide above is good. However I'd just add that BMW recommend a power supply able to supply a constant 13.8v at 70amp, for programming ECU's. Also a decent quality cable should be used.

Also, after programming the ECU, you should revert its configuration to default by coding the 2 modules identified by the OP to default with expertmode and not blank man files. Using the blank man method can cause unexpected results.

Also, also, make a bit of your existing ECU zusb number! In case you ever need to go back to it.
Appreciate 0
      12-07-2016, 09:28 PM   #4
Ibo24
New BMW owner
Ibo24's Avatar
Turkey
3
Rep
79
Posts

Drives: BMW 320d
Join Date: Jan 2012
Location: Turkey

iTrader: (0)

Don't you need to give in your VIN after choosing the right update? Before you press Done?

Edit: My bad, you did it the second after comfort mode!
Appreciate 0
      12-07-2016, 10:33 PM   #5
AJL
New Member
United_States
1
Rep
11
Posts

Drives: 2011 335i M Sport
Join Date: Oct 2015
Location: Bradenton, FL, USA

iTrader: (0)

Quote:
Originally Posted by Sensible_ View Post
However I'd just add that BMW recommend a power supply able to supply a constant 13.8v at 70amp, for programming ECU's. Also a decent quality cable should be used. Also, after programming the ECU, you should revert its configuration to default by coding the 2 modules identified by the OP to default with expertmode and not blank man files. Using the blank man method can cause unexpected results.
Haha yes, a better power supply would ideal! But I work with what I have. There weren't any dips in voltage and my battery is good, so I didn't run into any issues.

The profile I was using is simply expertmode adjusted to the settings specified at the codinge90 website.
Also, I can definitely see how coding a blank MAN file could cause issues, luckily for me it didn't. Whatever instructions I could find scattered around all seemed to suggest it was how to remove a supposed encoding error code (which I didn't actually check for )
So I agree with you, especially if you're not the "hold my beer and watch this" kinda person, try writing the default configuration first.
Appreciate 0
      Yesterday, 05:43 AM   #6
Katkarot
Private First Class
6
Rep
129
Posts

Drives: 2010MDX 2012135i
Join Date: Sep 2012
Location: Lotusland

iTrader: (4)

since getting PPK installed with ZB 8684958 for my 2012 135i, I been getting error code 28A0 repeatedly (after clearing code).

I never got this error code prior to the PPK install

Any one have any idea what may be the cause and a possible resolution?

Thanks in Advance
Appreciate 0
      Yesterday, 12:18 PM   #7
Terraphantm
Lieutenant
64
Rep
452
Posts

Drives: E46 M3 Coupe
Join Date: Apr 2009
Location: N/A

iTrader: (1)

Quote:
Originally Posted by Sensible_ View Post
If someone were to do it incorrectly then you have a 100% chance of bricking your car...

However, it isn't rocket science. You are simply flashing a module. The guide above is good. However I'd just add that BMW recommend a power supply able to supply a constant 13.8v at 70amp, for programming ECU's. Also a decent quality cable should be used.

Also, after programming the ECU, you should revert its configuration to default by coding the 2 modules identified by the OP to default with expertmode and not blank man files. Using the blank man method can cause unexpected results.

Also, also, make a bit of your existing ECU zusb number! In case you ever need to go back to it.
I think it's important to note the difference between a recoverable brick vs a permanent brick. 99% of the time if your flash messes up, it can be recovered.

Where things get a little hairy is during the boot sector update. There is a brief window after the DME is done downloading the flash and performing the security check where it erases a section of the boot sector and copies over the new one. If the power is cut at this point, the DME is permanently bricked; it just won't boot. If you don't have the passwords for bootstrap access, you can't even get in with a debugger to fix it.

Expert mode vs blank MAN file doesn't matter. They'll both literally accomplish the same thing.
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 -4. The time now is 03:43 AM.




e90post
e90post
Powered by vBulletin® Version 3.7.0
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
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