[grahams]

Car 135i 6mt EUR 0909

Coding
Today I attempted to update my DME with winKFP to cure an oscillation issue.
Datens were e89 the latest from BimmerGeeks

Now admittedly I did make a mistake doing it (followed a bad tutorial), selected MSD80v2 instead of MSD81 by not searching for the ZB number and failed to put in the VIN but the flash ran as expected.

I have a store of the ZB numbers before attempting any work.

Prior to flashing the box came up noting that the two versions of software were the same so I didn't foresee any issue and proceeded.

Issue
Unfortunately the car now doesn't boost at all. MHD is showing no target boost

If I had the wrong map I would expect the car to simply not run but it is running with no fault codes, cold start as expected, idles absolutely fine and drives with no fault codes.

When accelerating I can hear the turbos starting to spool but the wastegate duty cycle is running and changing to keep inline with the expected boost.

Attempted remedy
Since the issue has happened I've completely reinstalled the BMW tools on the laptop, updated the data and e89 daten files using Coding tool and followed the correct proceedure

Comfortmode, enter zb number, enter vin, done, process ECU but to no avail.

Would appreciate any steer on this. I am comfortable doing this type of work and have many years experience using dealer level software with other brands but am less familiar with BMW, this being my first experience with winkfp.

Thanks
Graham

[grahams]

https://datazap.me/u/grahams/no-boos...o=2-3-13-14-23

[rjahl]

Originally Posted by grahams

Car 135i 6mt EUR 0909

Coding
Today I attempted to update my DME with winKFP to cure an oscillation issue.
Datens were e89 the latest from BimmerGeeks

Now admittedly I did make a mistake doing it (followed a bad tutorial), selected MSD80v2 instead of MSD81 by not searching for the ZB number and failed to put in the VIN but the flash ran as expected.

I have a store of the ZB numbers before attempting any work.

Prior to flashing the box came up noting that the two versions of software were the same so I didn't foresee any issue and proceeded.

Issue
Unfortunately the car now doesn't boost at all. MHD is showing no target boost

If I had the wrong map I would expect the car to simply not run but it is running with no fault codes, cold start as expected, idles absolutely fine and drives with no fault codes.

When accelerating I can hear the turbos starting to spool but the wastegate duty cycle is running and changing to keep inline with the expected boost.

Attempted remedy
Since the issue has happened I've completely reinstalled the BMW tools on the laptop, updated the data and e89 daten files using Coding tool and followed the correct proceedure

Comfortmode, enter zb number, enter vin, done, process ECU but to no avail.

Would appreciate any steer on this. I am comfortable doing this type of work and have many years experience using dealer level software with other brands but am less familiar with BMW, this being my first experience with winkfp.

Thanks
Graham

Are you 100% sure of your ZF number?

Its like you are running a N53 flash. No boost , no throttle body action but the engine load values look like targets for the NA motors

[grahams]

Yes definitely, I took a record before it was flashed although I completely agree it looks to have an N/A map on the car.

ZB number was 7628540 which maps to the n54 https://www.mastertuning.it/file-original/

Hardware number is 7616431

the PABD file is 11msd80.IPO
the P-SGBD file is 11MSD80.PRG

[rjahl]

Originally Posted by grahams

Yes definitely, I took a record before it was flashed although I completely agree it looks to have an N/A map on the car.

ZB number was 7628540 which maps to the n54 https://www.mastertuning.it/file-original/

Hardware number is 7616431

the PABD file is 11msd80.IPO
the P-SGBD file is 11MSD80.PRG

Well it's a calibration file from a turbo N54.

If it's not storing any codes then the only things I can think of:

Traction control, but that should come with an error. No timing on your log, that might have been a clue

Incorrect dataset, limp mode, again an error would have been stored.

Just saw another log that looked like yours, Brocken vacuum hose.


https://www.e90post.com/forums/attac...8;d=1403875744

[grahams]

Have now managed to resolve this. For anyone who had this in the future this is what I found.

Updated WinKFP configuration
Deselect fast baudrate
Selected UIF write in comfort mode
Selected Force program programming in comfort mode
Restart WINKFP

Correction to the procedure mentioned previously
Comfort mode (F1)>>Update UIF (F3)>>Enter VIN (F4)>>Done (F8)>>Prog. ZB-Update (F3). Selected yes to write UIF (twice as force write)

Write time with fastbaud deselected was significantly slower, about 20 minutes

What I found was that looking in the kmm_sg.txt file in the kmmData folder of the raw datens, the ZB number was associated with the N53 engine as correctly pointed out above. Below I have copied a portion of this document. As I had a copy of the ZB number before undertaking any programming I knew this worked and evidently the VIN changed a configuration within the file to effectively "switch" the turbos on. The files used by WinKFP were the same; PABD file as 11msd80.IPO and P-SGBD file as 11MSD80.PRG.


+G;1;98257;A;DME_4I4_N53_6Z_MSD81_B30
4580440;7596022;7578033;0909450;WHNSL
7606848;7602118;7578033;0912510;WHNSL
7611000;7602118;7578033;0912512;WHNSL
7611790;7611358;7578033;1009410,1009450-1103350,1003501-1006502;WHNSL
7608984;7608621;7578033;1103310,1003500;WHNSL
7607278;7605662;7578033;1003450;WHNSL
7617852;7616431;7578033;1009500;HNL
7628540;7616431;7578033;1103500;HNL
7602452;7602118;7578033;1003400-1103300,0909500-0909516;WHNSL

There's very little back end workflow information out there about how WinKFP uses the VIN and adapts it's writing method.

Follow up question. Does one need to reset the adaptations after writing update or will that automatically be done as part of the process and the ECU is now starting a fresh?