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

[Bry5on]

Got two sessions in and it was super clear in the map that one small ‘island’ in the tune was sending my long term fuel trims to ~115%, causing every other spot to run rich. Thank you! Really clever solution you’ve come up with here

[SliM3]

Mind sharing the most up to date/accurate one?

I don't mind, but I need to clean it up and get rid of all the custom stuff.

I'll post when we get back home in a couple days.


Sent from my iPhone using Tapatalk

[Obioban]

I'm the author (Brian H.) and don't mind that it is shared, albeit I've probably made quite a few revisions to that XDF since it was posted.


Sent from my iPhone using Tapatalk

Mind sharing the most up to date/accurate one?

[SliM3]

Although you can remove all transients using a filter in Megalog Viewer (they have a tutorial just for this), Lambda Integrator correction is a closed loop system only, it disables itself otherwise and defaults to a 1. This really only tunes the drivability portions (closed loop) you are on your own for the rest.

And yes, you need to have a lot of data points and rely on the power of large data sets, you don't want to make a change with very few hit counts.

If the lambda regulator is constantly shutting down due to accel enrichment you can change the value at which they cut-off using K_LA_BA_OFF_POS (shuts down regulator if resulting accel enrich factor exceeds 1.04) and K_LA_BA_OFF_NEG (shuts down regulator if resulting accel enrich factor falls below 0.94).

[SliM3]

I forget who the author of this one is, it was on the old M3 forum MSS54 master thread. I did not make it, but since it was publicly posted in the past, I don't mind sharing it: https://drive.google.com/file/d/1nyV...ew?usp=sharing

If the author does not want this XDF shared, please let me know and I'll delete the link.

I'm the author (Brian H.) and don't mind that it is shared, albeit I've probably made quite a few revisions to that XDF since it was posted.


Sent from my iPhone using Tapatalk

[Pavlo]

How do you filter accel fuel because you must not correct your VE table when accel fuel is ON ? Reving up with constant pedal position can be a solution.

Although you can remove all transients using a filter in Megalog Viewer (they have a tutorial just for this), Lambda Integrator correction is a closed loop system only, it disables itself otherwise and defaults to a 1. This really only tunes the drivability portions (closed loop) you are on your own for the rest.

And yes, you need to have a lot of data points and rely on the power of large data sets, you don't want to make a change with very few hit counts.

[Bry5on]

How do you filter accel fuel because you must not correct your VE table when accel fuel is ON ? Reving up with constant pedal position can be a solution.

I’ve been wondering the same. Maybe if you log long enough it averages/filters out? Seems worth disabling for the tuning session if that’s possible.

[MpowerE36]

How do you filter accel fuel because you must not correct your VE table when accel fuel is ON ? Reving up with constant pedal position can be a solution.

[Pavlo]

If anyone wants to play around with other methods, that would also be cool.

I've tried logging Lambda with my wideband and do a similar approach, not good. Ended up with heavy overshoots so I added a multiplier in to reduce the percent value but sort of abandoned the project when the Integrators worked exceptionally well.
I still kind of want to try using wideband Lambda values and maybe do a full chemistry calculation for the target corrections, but don't think its really needed. A fun opportunity here can be a way to create a target AFR table first (this can include the open loop high load sections), then divide the target table by your logged lambda to get a percent by which you are off, and then come up with some scaled value to incrementally reach your target AFR instead of just Stoichiometry for closed loop. If you know how many lonely fuel or air molecules you have (Lambda), you should be able to math your way into a pretty decent VE table.

Next time I go to the mountains I may try to get a nice data sample and see if I can make the high load portions of my tune a little cleaner just as a proof of concept for this method.

[Pavlo]

A bit slow on the draw here, do you need to download megalog viewer, tunerstudio as well as tunerpro?

You don't need TunerStudio, only MegalogViewer HD (Its such a mouthful of a name). I think the free version does not allow you to view data in a historgram table.
My work flow is: Datalog with Testo >> Get the average value with MegalogViewer >> Grab VE table with TunerPro >> Change it with Excel Spreadsheet >> Back to TunerPro >> Flash the tune.

[Pavlo]

Got a question, so i made first run, edited RF table, all was good, but i undertstand that run was really short, so today i made a new run, used new RF table from last edited, paste them in Excel and got numbers like 21.023 i paste them in TABLE in Turner pro, press save, and when i reopen all digits changed from 21.023 - to 21.000, can some one send XDF parametrs for this table? Because i think some thing is wrong in settings of that table (from github)
she rounds to tenths, instead of leaving thousandths, it doesn’t seem like a big difference, but something tells me that this is not entirely correct
Thanks!

It will do that, that is ok. The value size allocation allows for a finite number of significant digits, so TunerPro will simply round off (its insignificant).

I would stay away from doing short runs, you want nice long drives or at least high hit counts for the cells or area you are targeting. I am also a bit skeptical of any cell that has a strange value at quantity 2 or 5 hits or something, manually replace it with 1. If you are seeing high corrections (stock limits in many cars are 1.1 to 0.9) then do short drives to get them closer before you spend a lot of time in these areas.
This is sort of when the LTFT become important, Lambda Integrator is applied as an instant correction OVER the longer term fuel trim. This is partially why I disabled it, after long periods of time cruising at high speeds (4k+ rpm for example) the fuel trim would apply to everything and then car would hunt during idle when I stop afterwards. Without a MAF I don't really see a point to long term fuel trims, unless you have a significant drop in fuel pressure there isn't a whole lot that it can help with.

[Pavlo]

Hello! A little question where can be find such XDF file with 24*20 table and such parametrs? XDF from github does not have such parametrs

I forget who the author of this one is, it was on the old M3 forum MSS54 master thread. I did not make it, but since it was publicly posted in the past, I don't mind sharing it: https://drive.google.com/file/d/1nyV...ew?usp=sharing

If the author does not want this XDF shared, please let me know and I'll delete the link.

[Pavlo]

Sorry, that was a vague question!
I was referring to the y-axis conversion formula for hex to decimal in your TunerPro VE map. I use (0.0030517578125*x) and mine doesn't align like it should (i.e. 10.01, 14.99, 64.99 aq_rel; instead of 10.00, 15.00, 65.00 aq_rel like yours), so was curious what formula you're using.

Also man, great work on your tuning tool!!!!

I've never changed it and interestingly enough as I opened TunerPro just now it looks just like yours! Aside for some minor changes (like units) the XDF I use is the commonly found for the CSL -335 variant. Seems its some strange rounding structure in TunerPro, but can probably drop it down to a single decimal point. I totally read that as a Multiplier that is applied to the logged aq_rel!

And thank you! The result of many hours of suffering.

[Cubieman]

A bit slow on the draw here, do you need to download megalog viewer, tunerstudio as well as tunerpro?

[pnvhome]

Got a question, so i made first run, edited RF table, all was good, but i undertstand that run was really short, so today i made a new run, used new RF table from last edited, paste them in Excel and got numbers like 21.023 i paste them in TABLE in Turner pro, press save, and when i reopen all digits changed from 21.023 - to 21.000, can some one send XDF parametrs for this table? Because i think some thing is wrong in settings of that table (from github)
she rounds to tenths, instead of leaving thousandths, it doesn’t seem like a big difference, but something tells me that this is not entirely correct
Thanks!