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

[heinzboehmer]

Adaptations back on and they're at 1.01 and 1.00 after driving around for a bit. Nice.

[heinzboehmer]

Alright, first warm up data log done after flashing the interpolated warm up table. Waited for the car to cool down fully (more than 24 hrs) and started logging immediately after start up. Still only got like 4 minutes of logs before the engine switched over to the hot map...

Here's the interpolated warm up table compared to the first iteration using the same lambda integrator method:



(I made sure to filter out any points >= 80 C in megalogviewer)

So, it's super close to the interpolated table. Considering this table only ever really gets used for a handful of minutes, I think this is my last iteration. Very happy with all this drivability tuning

Edit: Attached the megalogviewer warm up settings profile to this post if anyone wants it. Forum doesn't like the ".settings" extension, so just remove ".txt" from the filename and use like normal.

[pnvhome]

Set "Lambda Adaptation_MINIMUM ENGINE TEMPERATURE (K_LAA_TMOT_MIN)" to some value above operating temp. I set mine to 210 F. The XDF linked in the video on the first post has this parameter identified.

Also, make sure to reset adaptations after flashing. Turns out that turning them off means that the DME won't update the stored value and not that the DME won't use the stored value in its VE calculations (ask me how I know...).

Thanks a lot! Hope i understand all)))
Now i need to wait some warm days) Because its too cold outside, just 0-1 celsius, and engine don't warm up correctly)

[heinzboehmer]

A little question, how you off the adaptations? I read all the tread few times, but not understand =(

Set "Lambda Adaptation_MINIMUM ENGINE TEMPERATURE (K_LAA_TMOT_MIN)" to some value above operating temp. I set mine to 210 F. The XDF linked in the video on the first post has this parameter identified.

Also, make sure to reset adaptations after flashing. Turns out that turning them off means that the DME won't update the stored value and not that the DME won't use the stored value in its VE calculations (ask me how I know...).

[pnvhome]

A little question, how you off the adaptations? I read all the tread few times, but not understand =(

[Bry5on]

Thanks a lot for this Pavlo! Just finished the warm tune and my car drives much better now. My car needed fuel in a lot of places (much like Bry5on's):



Rev matching is more responsive (have yet to get the engine to stumble like it sometimes did before) and the car feels a little livelier. Won't go as far as saying that it feels more powerful, but it does feel like it struggles less with around town driving. But by far, the most noticeable change is the engine behavior at very low throttle inputs, like when pulling away from a stop or changing gears. Before, the rpms would oscillate quite a bit and make things pretty jerky (sidenote: hadn't realized I was driving around this until now), but that is completely gone now. Feels sooo much more refined. No more weird stumbling when pulling away from a light.

Next up is applying the same process to the warm up map. It's painfully obvious when the car switches over from that to the warm map now. For now, I interpolated the final scaling factors (what's in the table above), as the Relative Opening and RPM axes are slightly different, and applied them to the warm up map. Will probably data log a couple drives, but I'm betting it will be pretty close.

Also, I took some notes while tuning and figured I'd share as they might be useful to others:

• Testo
  • Under "MSS54 (SERIAL)", open "STATUS_MOTOR_1" and "STATUS_MOTOR_2"
  • Log "relativer Oeffnungsquerschnitt", "RPM", "Lambdaintegrator 1" and "Lambdaintegrator 2"
  • Logging "Motor Temp." is useful for the warm up tuning
• Megalogviewer
  • Need premium version to apply settings file
  • Can replicate settings file with free version, but it's more work
  • Did not bother adding any filters to the data, just made sure to datalog when warm
• Integrator Data Interpretation
  • Initially averaged out integrators for both banks and used that, but bank 1 consistently wanted more fuel than bank 2, so ended up just using bank 1
  • Seemed to be off by a fixed offset, so decided long term trims could take care of it
  • Would have gotten there eventually with average, just would have taken longer for the same result
  • Kept iterating until I saw most integrator values oscillating around 1
• Linked XDF
  • Truncates decimals to int in both warm up and warm VE tables
  • Table stores values as decimals with 1 decimal point, but XDF makes tunerpro display them as ints and thus truncates any decimals (does not round) -> affects next iteration calculations
  • To fix, in parameter tree, right click "Density Correction_VOLUMETRIC EFFICIENCY (RF)", go to "Edit Parameter XDF Info" and change "Output Type" to "Floating Point"
    • Do the same for warm up map
• Flap map
  • I do not have a flap, so I zeroed out the entire flap map
  • Map contains additive compensation factors, so it's effectively not doing anything now
• Logging strategy
  • Mostly drove around normally, to try and capture as many data points as possible when I spend the most time
  • After a few iterations, there were some areas where engine was clearly still stumbling, so I focused on those combinations of throttle/rpm for a couple iterations
    • Found hills with no traffic to load up engine and be able to slowly climb up the rev range at a fixed throttle input
    • Think of replicating how the car would behave on a dyno

Lastly, here's my version of Pavlo's spreadsheet. Not the most readable thing in the world, but has some useful things like a (very hacky) way to autofill 1s and the warm up interpolation strategy: https://docs.google.com/spreadsheets...it?usp=sharing

Could not agree with this more! I also did the warmup map by building an excel re-map of the normal map using interpolations for missing data points. My warmup map is now smooth and the weird hesitations and oscillations are gone. Big difference. I don’t think it’s 100%, but certainly good enough for the first three minutes of driving as there’s no chugging anymore.

thanks again Pavlo!

[heinzboehmer]

Thanks a lot for this Pavlo! Just finished the warm tune and my car drives much better now. My car needed fuel in a lot of places (much like Bry5on's):



Rev matching is more responsive (have yet to get the engine to stumble like it sometimes did before) and the car feels a little livelier. Won't go as far as saying that it feels more powerful, but it does feel like it struggles less with around town driving. But by far, the most noticeable change is the engine behavior at very low throttle inputs, like when pulling away from a stop or changing gears. Before, the rpms would oscillate quite a bit and make things pretty jerky (sidenote: hadn't realized I was driving around this until now), but that is completely gone now. Feels sooo much more refined. No more weird stumbling when pulling away from a light.

Next up is applying the same process to the warm up map. It's painfully obvious when the car switches over from that to the warm map now. For now, I interpolated the final scaling factors (what's in the table above), as the Relative Opening and RPM axes are slightly different, and applied them to the warm up map. Will probably data log a couple drives, but I'm betting it will be pretty close.

Also, I took some notes while tuning and figured I'd share as they might be useful to others:

• Testo
  • Under "MSS54 (SERIAL)", open "STATUS_MOTOR_1" and "STATUS_MOTOR_2"
  • Log "relativer Oeffnungsquerschnitt", "RPM", "Lambdaintegrator 1" and "Lambdaintegrator 2"
  • Logging "Motor Temp." is useful for the warm up tuning
• Megalogviewer
  • Need premium version to apply settings file
  • Can replicate settings file with free version, but it's more work
  • Did not bother adding any filters to the data, just made sure to datalog when warm
• Integrator Data Interpretation
  • Initially averaged out integrators for both banks and used that, but bank 1 consistently wanted more fuel than bank 2, so ended up just using bank 1
  • Seemed to be off by a fixed offset, so decided long term trims could take care of it
  • Would have gotten there eventually with average, just would have taken longer for the same result
  • Kept iterating until I saw most integrator values oscillating around 1
• Linked XDF
  • Truncates decimals to int in both warm up and warm VE tables
  • Table stores values as decimals with 1 decimal point, but XDF makes tunerpro display them as ints and thus truncates any decimals (does not round) -> affects next iteration calculations
  • To fix, in parameter tree, right click "Density Correction_VOLUMETRIC EFFICIENCY (RF)", go to "Edit Parameter XDF Info" and change "Output Type" to "Floating Point"
    • Do the same for warm up map
• Flap map
  • I do not have a flap, so I zeroed out the entire flap map
  • Map contains additive compensation factors, so it's effectively not doing anything now
• Logging strategy
  • Mostly drove around normally, to try and capture as many data points as possible when I spend the most time
  • After a few iterations, there were some areas where engine was clearly still stumbling, so I focused on those combinations of throttle/rpm for a couple iterations
    • Found hills with no traffic to load up engine and be able to slowly climb up the rev range at a fixed throttle input
    • Think of replicating how the car would behave on a dyno

Lastly, here's my version of Pavlo's spreadsheet. Not the most readable thing in the world, but has some useful things like a (very hacky) way to autofill 1s and the warm up interpolation strategy: https://docs.google.com/spreadsheets...it?usp=sharing

[Bry5on]

Update: Bank 1 long term fuel trim is 1.01 and bank 2 is 1.00 after turning adaptations back on. That’s as good as it gets!

[Bry5on]

Wideband for this-- should we put it pre or post cat?

I run my wideband pre-cat, it’s most useful for the open loop WOT tuning

[Bry5on]

Do you use map sensor as kassel kit? When it installed on intake, or kit when it is installed near to ecu box? Or original csl tube for map?

I use a map sensor in the ebox area, connected to the brake booster hose

[Obioban]

Wideband for this-- should we put it pre or post cat?

[pnvhome]

For the record, here’s the difference between the default CSL tune and the 5 runs in version using this method on my car. Super clever, thank you for sharing!


Throttle tip in is so much smoother and the motor seems much happier. I agree that a good amount of the rasp is gone in that mid-2k RPM range. Looks like those CSL cams and the SS headers really do make a difference. With these headers, I needed fuel almost everywhere, and particularly in two islands.

My motor is a 180k mile stock internal CSL conversion, with flap, SS v1 headers and matching catted section 1. This tuning was done with flap closed to the appropriate map.

Adaptations are now turned back on, so I’ll be watching what the motor does.

edit: I’d bet that the resonances and jitteriness in the 2k RPM range can be totally tuned by changing the interpolation motor RPMs. I did this for my WOT tune and was able to get a super flat AFR curve by targeting the resonant and nodal frequencies as the interpolation points.

Do you use map sensor as kassel kit? When it installed on intake, or kit when it is installed near to ecu box? Or original csl tube for map?

[Bry5on]

For the record, here’s the difference between the default CSL tune and the 5 runs in version using this method on my car. Super clever, thank you for sharing!


Throttle tip in is so much smoother and the motor seems much happier. I agree that a good amount of the rasp is gone in that mid-2k RPM range. Looks like those CSL cams and the SS headers really do make a difference. With these headers, I needed fuel almost everywhere, and particularly in two islands.

My motor is a 180k mile stock internal CSL conversion, with flap, SS v1 headers and matching catted section 1. This tuning was done with flap closed to the appropriate map.

Adaptations are now turned back on, so I’ll be watching what the motor does.

edit: I’d bet that the resonances and jitteriness in the 2k RPM range can be totally tuned by changing the interpolation motor RPMs. I did this for my WOT tune and was able to get a super flat AFR curve by targeting the resonant and nodal frequencies as the interpolation points.

[pnvhome]

I was absolutely dummy) Made about 5 runs, last one was almost absolutely ideal, also changed WOT table from the topic near this, and cleared FLAP table, i have turner intake. So now car runs almost perfectly just a little jigs on 2200rpm with 4 celcius outside, also there is no more bad resonations in exhaust. And car runs absolutely smooth even from 1800rpm
also i think problem in jigs becouse of map sensor with kit from kassel, on logs it shows that to many pulsations

[chapmans]

Any potential for a 'dummies' guide to this? I have edited tunes very basically but never been in the tables or anything.