Narrowband Tuning Tool

[Terminal_Crazy]

yeah it's definitely pretty good! remember that 132 is only a 3% fueling error, which is really nothing, it's just running at nearly 15:1 instead of 14.7:1, and that's just until your trims take effect. totally safe unless under really heavy load.

loose should be ideal even for fine tuning. by 'loose' it just means that samples close to the border are averaged into both cells. it's not spreading the data around very much. you can tighten the boundaries on map and rpm hysteresis (go a bit lower). i think there's no reason to use 'strict', rather just see you tune 'loose' until it behaves for you...

i wonder if at this point not using the integrator might help it get closer too. some configurations have a stable integrator and some don't.

edit: since obviously the shape of the table is pretty good, maybe just *0.98 the whole table in tunerpro and see where that gets you.

Steveo: Would it be better to have a configurable target value so you can calc the results to target 125 say rather than 128 ?

Thanks
Mitch

[Stokes1114]

yeah it's definitely pretty good! remember that 132 is only a 3% fueling error, which is really nothing, it's just running at nearly 15:1 instead of 14.7:1, and that's just until your trims take effect. totally safe unless under really heavy load.

loose should be ideal even for fine tuning. by 'loose' it just means that samples close to the border are averaged into both cells. it's not spreading the data around very much. you can tighten the boundaries on map and rpm hysteresis (go a bit lower). i think there's no reason to use 'strict', rather just see you tune 'loose' until it behaves for you...

i wonder if at this point not using the integrator might help it get closer too. some configurations have a stable integrator and some don't.

edit: since obviously the shape of the table is pretty good, maybe just *0.98 the whole table in tunerpro and see where that gets you.

Thanks for the tips Steveo! Im pretty new to tuning, but looks like I started at the perfect time.. I will give the no Int a shot first with another datalog and see how it does.. Will also compare it to just the TP *.98. Ill update tomorrow evening after.

[steveo]

Steveo: Would it be better to have a configurable target value so you can calc the results to target 125 say rather than 128 ?

Thanks
Mitch

i'll have to think about the implications of that. not sure if it's a good idea or not. it might be a really good idea.

[steveo]

Thanks for the tips Steveo! Im pretty new to tuning, but looks like I started at the perfect time.. I will give the no Int a shot first with another datalog and see how it does.. Will also compare it to just the TP *.98. Ill update tomorrow evening after.

that's cool, can you post a copy of the original bin, and the one that you last posted? i want to diff the tables and see how the shaping worked after 5 passes of my geometric interpreter thinger.

[steveo]

i found a bug that was preventing the integrator values from being used a lot of the time. explains why int and non-int values are so close. will fix it soon.

[steveo]

i'll have to think about the implications of that. not sure if it's a good idea or not. it might be a really good idea.

this is throwing me for a loop, but i think it's a very good (and all too easy) idea to have a control for target. thanks for the idea!

implementation-wise, all i really have to do is minus or plus the resulting value in the table, right? if we're at -2% and the target is -2%, +2%=0%=no modification required. or if using raw trims, if the trim is 124 and the target is 126, +2=126 trim. super easy to skew the table like that.

i think it would work well as long as you don't really change your target. you could probably get decent results targeting -2% or something (~125 in raw blm terms) especially as a new tuner, as everyone knows a hair richer is better than a hair leaner.

[steveo]

try the new version....

RESET YOUR ADVANCED SETTINGS WHEN INSTALLING THIS VERSION

the integrator strength needed to be nerfed a bit, i lowered the default to 25%

also new version lets you specify an arbitrary trim target in real-time

[steveo]

http://fbodytech.com/trimalyzer/trimalyzer-download/

[Stokes1114]

that's cool, can you post a copy of the original bin, and the one that you last posted? i want to diff the tables and see how the shaping worked after 5 passes of my geometric interpreter thinger.

Here is a copy of my stock bin and the latest bin that Im running, after the 6th pass through as of last night. I did another log today and Im getting ready to run the log through. Will post results soon

[Stokes1114]

TrimNoIntLoose.PNG
Heres my log from today and pics of the results in loose mode, one using Int and the other not.
The ability to change the target is awesome..Def gonna have to play with that a bit!

[steveo]

you should definitely hand-shape some of your ve table. you have a few spikes creeping up there.

i can see where trimalyzer's data has defined a new curve where you've actually driven, but you still have massive spikes where it meets areas that have no decent analysis data. you might not notice till you go haulin' a load up a hill or something.

a perfect example of where a hand-made approach is needed to supplement any tool

yours (not good)

ve1.png

mine (kinda good)

ve2.png

[Stokes1114]

VE#2.PNGTrim#2.PNG
Did some hand smoothing and did a log.. Ran the log through Trimalyzer. I can see how it really doesnt take much to make the table start going rich/lean.

[steveo]

that's for sure!

BUT

do you notice how uniform your trims are now? they're all mostly 118-120. it means you got the shape of the table right, but the overall needs a slight tweak.

[Stokes1114]

that's for sure!

BUT

do you notice how uniform your trims are now? they're all mostly 118-120. it means you got the shape of the table right, but the overall needs a slight tweak.

Ya definitely helped the shape. I hand tuned and ran another log through. The trims are looking great as of now. A couple tiny spots to still adjust but overall very nice. Heres the resultsTrim#3.PNG

[steveo]

there ya go, leave it there for sure!