So I'm cycling thru the AutoVE process. Make a run, log it, get the BEN/Map recommended changes and multiply them to the VE table. Repeat the process.
I must admit, I barely unstand what I'm doing as I go through the motion of the tutorial from a engine standpoint, but now that I have some data, I'm starting to see what is happening.
The Tutorial starts by increasing the Kpa numbers by 15% across the table. Richening things up for protection. As you drive and log, the process makes real world changes to the table, bringing those numbers into line with reality, usually lower. Best case scenario, you would get real world number for every cell in your VE table. Seems that isn't going to ever happen, and this is the cause for the Rocky Mountains that many have complained about. Especially at the high RPM's where you car doesn't usually go there but for a quick moment.
In the image below, you see the graph of the mountains and valleys and the cells causing the affect. These cells started out with much higher values per the tutorial, the the logging process makes real world changes to only some of the cells.
In the image below you see on the top my original tune. The middle tune had the 15% tacked on, and then the real world changes from a spirited run around town. The bottom tun is after 4 iterations of this process. Note the highlighted cells in across the 3 tunes.
They start in the original tun with
83
85
91
Tutorial process pumps them up with some fuel to much higher values and they start working down
90
90
94
Now actually leaner than my original tune from many real world iterations.
79
81
86
My theory here is that the huge valleys created are actual real world reading from the cells that are getting hit. The peaks are not getting hit (enough anyway) so no adjustments are being made to them. So in theory, the valleys are correct, and the peaks should be leveled off to match the cells that had valid real world readings. Anybody disagree with that theory, please explain if you do.