Logging VE Values

[animuL]

For doing a VE tune its easy enough to create a parameter that adds the STFTs and LTFTs automatically and then create a histogram with that to modify the VE table. It would be even better if the scanner had a parameter of the VE table itself. Just as it will give a read out of spark advance, it would be cool if it would read the VE table out in the scanner. Then you could add that into the custom parameter and eventually you end up with a histogram that is what the VE table should be.

[Russ K]

Just add the LTFT+STFT pid to the default VE histogram.

Russ Kemp

[eficalibrator]

With a little more involved math, it's also quite possible to start with a perfectly tuned MAF transfer function and back-calculate to VE on the fly. One could then plot this in a histogram agains RPM and MAP to populate a VE table from scratch as long as you trust the MAF curve. I've already added this to the "Advanced GM Tuning" class material.