Hi Steve,
Some comments/oobservations:
Calc.VET is the same as AutoMAF (MAF correction using wideband-only) with calculation of VE table thrown in;
Calc.MAFT is the same as AutoVE (VE correction using wideband-only) with calculation of MAF table thrown in;
both methods can be tailored to use wideband, LTFT, STFT or any combination thereof for the correction BEN pid;
both methods will correct/calculate the cells in the MAF/VE whose operating condition (i.e. the axes) have been hit
(i.e. for example, Calc.VET can calculate VE table only from the MAP and RPM points hit)
you still have to interpolate/smooth to obtain the unhit cells.
Calc.VET is quick/easy to setup and log (disabling VE, or allowing transient filter to remove VE contributing frames);
Calc.MAFT takes a bit more effort (disabling MAF).
PE:
I would leave PE enabled for several reasons:
- the pids GM.EQIVRATIO and GM.AFR both match the PE table when PE is enabled (I prefer to use GM.EQIVRATIO);
- it is safer to allow PE to kick in as required while driving;
- PE kicking in/out usually coincides with throttle movement, and the transient filter filters this out.