Double checking CSL tune conversion/flashing process for MSS54HP non-CSL

[steliosm3e46]

hi guys..i flash terra's full binary and partial but i cant read fault codes..thanks for your help

[Slideways]

Anyone have issues downloading the 0401 v4 XDF? When I hit download it opens as a new window text document. Any direction would be appreciated.

The Basic XDF does not show a download button, but the Complete XDF does.

[Kdubski]

Anyone have issues downloading the 0401 v4 XDF? When I hit download it opens as a new window text document. Any direction would be appreciated.

[oceansize]

I had a look at your file in your attachment and some of the stuff ticked aren't implemented or have been implemented incorrectly. As I have been saying the tool has issues.

What's your email?

For the benefit of all of us and Martyn why don't you share the before and after of a file that demonstrates the issue? Or is this something you can't recreate and you think is seemingly random?

[heinzboehmer]

I'm also going through this process and want to make sure I've got this sorted out. Can I get a quick sanity check on these steps below

Car - 03 M3 with MSS54
Replace DME with MSS54HP (EWS delete) and wire in IAT / Map sensor
Flash Terras modified BIN via MSSFlasher
Pull partial and send to my tuner (or set Cam offsets / pressure sensor / injector / flap DTCs myself)
Flash updated partial

Car should now run and drive properly + OBD compatible

That will work. But if you're replacing your current DME with an HP, you don't need to modify the binary for the pressure sensor. That's only necessary on non-HP to HP hardware conversions, as the physical sensors on the board are different.

[Amalgam]

I'm also going through this process and want to make sure I've got this sorted out. Can I get a quick sanity check on these steps below

Car - 03 M3 with MSS54
Replace DME with MSS54HP (EWS delete) and wire in IAT / Map sensor
Flash Terras modified BIN via MSSFlasher
Pull partial and send to my tuner (or set Cam offsets / pressure sensor / injector / flap DTCs myself)
Flash updated partial

Car should now run and drive properly + OBD compatible

[R3Z3N]

^FYI both are binary files...... To keep wording consistent, we have a Full Binary consisting of Operating System and Tune, and the Partial Binary which is the tune only.

[ATB88]

^It can't hurt to try. Or just pull the partial from Terra's and copy YOUR values back as you can compare up to 4? binaries in TunerPro. However there is no easy way to compare values in TunerPro between versions IE 0301 and 0401.

Okay, yeah, so FWIW, if you go into the tune and just change all three version strings located at 0xBFB8, 0xBFC8 and 0xBFD8 to match the version of the full binary running on the DME that you're flashing the tune to, that's enough to get MSSFlasher to let you. But, to anyone reading this, obviously, only do this if the tune you're flashing matches the tune version of the full binary you're running (i.e. 0401 tune to 0401 binary). Otherwise this seems like a great way to really f*** up your engine.

[R3Z3N]

^It can't hurt to try. Or just pull the partial from Terra's and copy YOUR values back as you can compare up to 4? binaries in TunerPro. However there is no easy way to compare values in TunerPro between versions IE 0301 and 0401.

[ATB88]

So, I'm now running Terra's binary (211323000401PD31) and I want to load a tune file that's 211325000401PD31. MSSFlasher won't let me because the version doesn't match Terra's binary. I know that the tune's version information is stored at 0xBFB8. If I look at it in a hex editor I actually see the version number string repeated three times in a row, at 0xBFB8, 0xBFC8 and 0xBFD8.

If I just modify all three to read 211323000401PD31 rather than 211325000401PD11 can I expect MSSFlasher to flash it and also expect everything to run properly? Or is it more complicated than that and doing this is a bad idea?

[SliM3]

Thanks for this, absolutely willing to try it. When you say to change the Lambda_.... values to 231 and 130, are you specifying in dec or hex?

Yes, the values are decimal (231 = E7 hex) (130 = 82 hex).

When I convert DME's I typically use Terra's file, however, I stress that if the person/tuner has access to WINKFP to flash the complete CSL tune, which will populate the AIF field that's specific to their vehicle.

[ATB88]

To add on to this, terra's and paffy's files are 2300 because they have been modified to work with the regular HP bootsector. The bootsector can't be flashed with an OBD-II cable, which is why these modified files exist. However, the tune portion is the same as any other CSL tune.

Ah good, thanks both of you. So that means I should be able to flash any 0401 *tune* file I please while running either Terra's or Paffy's full binary. Huzzah!

Thanks for all of the clarifications, everyone. I hope they help anyone else who comes across them wondering the same things!

[heinzboehmer]

@ATB88: Yes the CSL conversion Full Binary and Original CSL DME use the same "mapping" IE offsets for the tunes, hence why 0401 is 0401 and 0301 is 0301. Paffy/Terra modified the OS to run the CSL tune on the non CSL HP DME.

To add on to this, terra's and paffy's files are 2300 because they have been modified to work with the regular HP bootsector. The bootsector can't be flashed with an OBD-II cable, which is why these modified files exist. However, the tune portion is the same as any other CSL tune.

[R3Z3N]

Thanks. Corrected the TERRAs filename to reflect the correct tune IE PD31.

Steps 1 and 2 can be combined as when flashing the full binary, your are flashing the "Operating System+Tune" , so when you flash ANY full binary, the tune is on the DME as well. Hence why Terra states to flash back YOUR CSL tune for whatever build your car has, then fix the value at TUNE/Partial offset 0xE002 from 00 to 01. Note if you search the 0401 XDF for that offset, it is set to read a WORD instead of a BYTE, AND the XDF is applying a conversion, AND I think it may be reading it as an integer (though 00 and 01 will still read the same as an integer/hex, but NOT with the applied conversion.) There is a reason Paffy wanted people familiar with altering Tunerpro in how one can view the data. When I was accepted, I didn't know that tunerpro could make an XDF (its painstaking by hand by the way) and I wrote my "proof" in plaintext and saved as .xdf. Smack my forehead. Now I know better, but not enough to program scripts to search for commonalities or change all XDFs to fix conversions or how data is viewed. I simply correct the xdf as I go and try my hardest to then correct all XDFs.

@ATB88: Yes the CSL conversion Full Binary and Original CSL DME use the same "mapping" IE offsets for the tunes, hence why 0401 is 0401 and 0301 is 0301. Paffy/Terra modified the OS to run the CSL tune on the non CSL HP DME.

[ATB88]

Here's my friendly observation based on the file you attached, and may help your situation:

Secondary Air Injection_ON-BOARD DIAGNOSIS (K_SLS_OBD) - should be set to '0'
DTC 19 Aux Air Pump Relay - should be patched (00 00 00 00 00 00 00 00 00 00 00 00 00 00)
DTC 63 Aux Air Valve - should be patched (00 00 00 00 00 00 00 00 00 00 00 00 00 00)
DTC 171 Aux Air Valve Jammed - should be patched (00 00 00 00 00 00 00 00 00 00 00 00 00 00)
Fuel Injection_COLD START ENGINE TEMP (K_TI_TMOT_KS) - change to -40

Lambda_CONTROLLER ENABLED (K_LA_FREIGABE) - change to 231 (this will set BIT's 3 & 4 "Post Cat 1 Enabled and Post Cat 2 Enabled" to OFF)
Lambda_OBD ENABLED (K_LA_OBD_FREIGABE) - change to 130 (this will set BIT 2 "Post-Cat Sensor Diagnosis" to OFF)


I would also use '00' across the board for all DTC patches, instead of doing '00' at the end. Especially if you've removed (unplugged) hardware.

Thanks for this, absolutely willing to try it. When you say to change the Lambda_.... values to 231 and 130, are you specifying in dec or hex?

Also a somewhat related side question: are tune/partial files that are meant for a 2500 DME variant (I guess that means authentic CSL or HP converted to CSL?) compatible with a 2300 DME variant (normal HP) running Terra or Paffy's CSL binaries? Suppose I wanted to try out someone else's tune that is a PD11 tune for a converted CSL DME with h-bridge (so, its version is 211325000401PD11, rather than the 211323000401PD31 that I'm running), could I just flash the tune with my current 23000401PD31 binary setup and expect it to work? Or would I need to start with Paffy's PD11 bin (211323000401PD11)? Or would it be totally incompatible with my DME since it's meant for a 2500 DME variant and mine's 2300? Not sure exactly which hw/sw differences are trivial and which are important, especially in light of the modified binaries.