Calc.VET: correcting MAF and calculating VE (in single log)

[zayne0]

When you see spikes (up or down), manually flatten them out, avoid doing too much smoothing, make the rest of the curve (not hit in the log) follow the shape/curvature of the corrected portion of the curve.

I do understand what you are saying. I'm just wondering why the corrected table curves up to max at about 4500rpm range.

[darcy]

I do understand what you are saying. I'm just wondering why the corrected table curves up to max at about 4500rpm range.

VE table should approximately mimic torque - 4500 is about the right spot for efficiency to start declining in a stock engine.

[zayne0]

VE table should approximately mimic torque - 4500 is about the right spot for efficiency to start declining in a stock engine.

My bad I didn't specify that the corrected table for maf is wanting to max out the maf around 4500rpm

[joecar]

Post a screenshot (SHIFT-PRTSCR and save to .png file, post .png file).

[zayne0]

my first time to screen shot something sorry it took so long.

[darcy]

Something wrong with your data there zayne0.
Maybe paste your log and tune files.

[zayne0]

15mile log.efiandres 6.0 original tune cacl ve tips.ctz

[joecar]

my first time to screen shot something sorry it took so long.

No worries (many people don't even realize screenshots can be taken like this)...

also post screenshot of your scantool map that you applied to tunetool MAF table .

[joecar]

+1 what darcy said...

EXT.WO2LAM1 is stuck at 28.5...

which wideband do you have...?

[joecar]

CALC.DAT is jumping alot... and maybe it's too high.