i've began logging and modifying VE table which has only led to more questions hence the new post.
from what i've read and come to understand is that your VE table should be fairly smooth which will aid in transition between SD and MAF references. my VE table looks like a canyon runs right through it but by log 5 most cells seem to be where they need to be with the exception of a few outliers. why so spikey? wouldn't you be back to a larger lambda error if i were to smooth out those spikes? shouldn't the WB do most of the work?
i have noticed PE is kicking during my logs. commanded lambda goes down according to PE table but there is no change in lambda, only lambda error %. i'm questioning if i missed something setting up my SD tune or if this is normal in SD tuning.
i've done 5 logs and updated the VE table 5 times. there are many references as to how quick VE tuning falls into place but this doesn't seem to be the case for me. would anyone care to share how long it took to fine tune their VE table?
also, i understand many don't pay much attention to VE after 4k as that is when MAF kicks in but i plan on boosting at some point and will likely go 100% SD when that happens.
my car is an M6 and i live in atlanta GA with hills. does decel affect the accuracy of lambda error %?
thanks in advance for the help.
-beau