A quick and easy way to street tune your CSL conversion for drivability.

[Obioban]

MSS54HP CSL CONVERT /// TUNER — v2.2.0 released
https://mss54hp-csl-convert-tuner.tsunagi.app/

I've been developing a large number of features and apps, so verifying this release took longer than expected. It also took time because I went back and re-studied a few things I had only a vague understanding of before. (I'm still not there yet, but this kind of research never really ends.)

The update reaches into a lot of small details, so I can't list everything — here are the main points.

Released
- Credits: my highest praise to karter16 and to everyone who has contributed to this research so far.
- TETV patch: now included in the MAP & LTFT on/off patch.
- VANOS offset adaptations excluded from the learned-value reset.
- Fast flash (including 125000 baud / flash counter reset): this covers reading as well as writing. Only the very first read takes time — after that, both reading and writing run at the higher speed.
- aq_rel_rf (RO) now shown in the live LAMBDA FEEDBACK view while driving.
- Restore of tuning maps.
- VE curve correction: experimental. It unlocks once tuning has converged to within 2% variation across all cells.
- Minor UI refinements.

Removed
- WOT (KF_TI_N_RF_VL) correction: I found it was removing fuel twice, so the feature is gone. If you enable the WOT transition threshold patch in this tool and tune at full throttle, you end up achieving what the WOT tuning feature was meant to do anyway.

Not ready for release yet
- RF_KORR_DRREL tuning: it requires anchoring each cell at ΔEGT ≤ 30, i.e. RF_KORR = 1.000, and logging that on Japanese highways is close to impossible. The feature is built, but I have no way to test it.
- Calibration: XDF built in, giving binary editing equivalent to TunerPro, plus Karter16's disassembly logic tree view, linked to the definition currently selected. The functionality is there, but it still needs adjustment.
- Built-in community patches: so that even someone new to CSL conversion tuning can do everything within this tool. Full binary writing will be implemented alongside it.

Notes
- A number of statistical settings are now exposed. If you aren't familiar with statistics, please leave them at their defaults. I spent most of my development time verifying the data processing on real drives and adjusting those defaults.
- Wherever a statistical setting is adjustable in the app, I've tried to include an explanation. Those explanations were generated by Claude, and I reworded them until I understood them myself — but with so many small fixes spread across the app, I haven't been able to review every comment. Please forgive any explanations that turn out to be wrong.

Anything on disabling tank ventilation during the tuning run?

[mushitaro]

Obioban Anything on disabling tank ventilation during the tuning run?

It's included in that patch:

- TETV patch: now included in the MAP & LTFT on/off patch.

[Obioban]

It's included in that patch:

Ah, excellent!

[mushitaro]

I foolishly forgot to add the single most important person to the credits. Pavlo has now been added. If you know of anyone else who has contributed to this project, please let me know and I'll add them to the credits.

[paulpbmw]

Yeah good call - I mentioned this in the disassembly thread but hadn't really expanded on it here. For reference for everyone here are the details below of how I'm now setup for VE tuning.

The steps below will use the naming conventions as per V3.2 (newly published today) of the XDF I've put together here: https://nam3forum.com/forums/forum/s...p-csl-0401-xdf

1: Disable and clear Long Term Fuel Trims
In TunerPro (with the XDF above loaded along with your current 0401 partial (tune) binary) Open the K_LAA_TMOT_MIN parameter and set it to 100 degrees C. As noted in heinzboehmer's earlier post this has the effect of raising the point at which the LTFTs are updated above the operating temperature of the motor (e.g. the LTFTs will never change).



2: Clear current engine adaptions in INPA.
Again as heinzboehmer notes this is necessary because the above step only stops LTFT's from being updated, not used. So you need to reset them to 1.00 so that they have no effect.

3: Disable the MAP Sensor Integrator
The MAP Sensor is a good thing under normal conditions in that it, in real time, accounts for variation between the AlphaN VE table and actual real-world conditions. This is why running the MAP Sensor results in a smoother drive. However this correct is counter-productive when performing the VE tuning process. To disable the MAP sensor input to calculation of Relative Fill and rely solely on the AlphaN VE table set k_rf_cfg to 0x02 (if you would like more reassurance that this does what I say it does see here: https://github.com/karter16/CSL_0401...put-parameters)



4: Go for a drive and log in TestO.
Log the following Parameters (you can log other parameters as well, just need at least these):
- Relative Opening
- RPM
- Lambda Integrator 1
- Lambda Integrator 2
- Motor Temp (if you're going to log from cold, otherwise only start logging once car is completely up to temp)

5: Process the log file to correct the AQ_REL (Relative Opening) values
Take the resultant log file and run it through https://docs.google.com/spreadsheets...it?usp=sharing to adjust the Relative Opening values to scale correctly for the AlphaN VE table.

6: Load the processed log file into MegaLogViewer
Load the processed log file into MegaLog Viewer.

7: Calculate the new VE table
Copy the lambda table from MegaLogViewer into heinzboehmer's spreadsheet and process as per the instructions there.

Hey I folllowed this post and read the whole thing multiple times to implement on my mss50 and i noticed something horrifying.

When i disabled adaptions, my oil temp went straight to 300 F !! I dont know about the mss54 but i figured id share that info so people can keep track of that and not blown their baby up.

[karter16]

Hey I folllowed this post and read the whole thing multiple times to implement on my mss50 and i noticed something horrifying.

When i disabled adaptions, my oil temp went straight to 300 F !! I dont know about the mss54 but i figured id share that info so people can keep track of that and not blown their baby up.

Without having some more information on what you exact setup is with your MSS50 it's a bit hard to say what's going on (e.g. are you running in alpha-n mode? with a MAF sensor? etc?). It's important to note that this process in this thread is designed specifically for the 0401 CSL variant of the MSS54HP. It probably can be adapted to other programs but I doubt it's as simple as you're expecting.

In regard to disabling adaptions, I'm not familiar with the MSS50 software, so can't comment on what effect it might have. I do know that the MSS50 has some material differences when it comes to fuelling. Possibly your setup is using the adaptions to add a lot of fuel, and disabling it caused the engine to run hot and lean? (I'm guessing at this though to be honest, could be all sorts of things)

People running an MSS54 with 0401 software with an engine that's in normal functional condition aren't going to blow up their engine by disabling the lambda adaptions for running this process.

[paulpbmw]

Without having some more information on what you exact setup is with your MSS50 it's a bit hard to say what's going on (e.g. are you running in alpha-n mode? with a MAF sensor? etc?). It's important to note that this process in this thread is designed specifically for the 0401 CSL variant of the MSS54HP. It probably can be adapted to other programs but I doubt it's as simple as you're expecting.

In regard to disabling adaptions, I'm not familiar with the MSS50 software, so can't comment on what effect it might have. I do know that the MSS50 has some material differences when it comes to fuelling. Possibly your setup is using the adaptions to add a lot of fuel, and disabling it caused the engine to run hot and lean? (I'm guessing at this though to be honest, could be all sorts of things)

People running an MSS54 with 0401 software with an engine that's in normal functional condition aren't going to blow up their engine by disabling the lambda adaptions for running this process.

I used xdf created by user MpowerE36 on this forum. It has a parameter that disables adaptions by changing a temperature threshold. Not sure how it works because MSS50 damos files were never leaked like mss54 so maybe no one knows.

As far as the spreadsheets, i modified them to fit the 18x12 format of the mss50 map LOADxRPM. Changed the formula to work with my setup that does not use VE values but lambda. Its works fine but the adaption part was the only sketch thing.

IM NOT SAYING DISABLING ADAPTIONS IS NOT GOOD FOR CSL 0401 GUYS BUT JUST POINTING OUT SOMETHING I NOTICED THAT WOULD BE A GOOD IDEA FOR EVERYONE TO KEEP AN EYE ON JUST IN CASE, GOD FORBID.

It makes sense though because if you disable adaptions the engine will run closer to 14.7 the more you tune it and that is going to run hotter. With adaptions on it will oscillate, at least thats what i saw in my data logs. IDK what caused that but when i turned adaptions on, the temp normalized.