Hand smoothing the VE table
1.) I carve up my VE table into cells...I run '01 Z06 LTFT boundaries, not the stock '01 F-body ones, get more LTFT cells into play.
2.) I get plenty of EFILive scan data during closed loop, full operating temp, varying driving conditions...try to hit as many LTFT cells as possible.
3.) I export that data {LTFT Cell, LTFT % both banks, RPM, MAP KPa} into CSV and open in Excel.
4.) I sort on LTFT Cell, then RPM, then MAP KPa. This gets the data into "chunks" I can do quick averaging on...
5.) For each VE table LTFT cell ara, I average the LTFT % data (both banks) and apply that percentage to the entire cell area using LS1-Edit. This gets me into the ballpark and I start seeing part-throttle driveability improving.
6.) When I'm averaging close to zero LTFTs for a given cell, I capture more data and start trimming individual RPM/KPa coordinates or ranges. Same export and sort in Excel.
It was much much easier in TPI, there's a public domain program called VEMaster which automates this right down to directly modifying the binary and re-checksumming it. I haven't played with Chris' automation tool but it may do something similar. The process is very time consuming but yields good results for me.
Let the discussion ensue...
HumpinSS - Make the table flow along with the existing. Look at the graph for VE and check it as you make changes. I'll send you mine.I have a new adapter/charger for my ThinkPad....$ 99.00!! IBM's are unique.
joel
1.) I carve up my VE table into cells...I run '01 Z06 LTFT boundaries, not the stock '01 F-body ones, get more LTFT cells into play.
2.) I get plenty of EFILive scan data during closed loop, full operating temp, varying driving conditions...try to hit as many LTFT cells as possible.
3.) I export that data {LTFT Cell, LTFT % both banks, RPM, MAP KPa} into CSV and open in Excel.
4.) I sort on LTFT Cell, then RPM, then MAP KPa. This gets the data into "chunks" I can do quick averaging on...
5.) For each VE table LTFT cell ara, I average the LTFT % data (both banks) and apply that percentage to the entire cell area using LS1-Edit. This gets me into the ballpark and I start seeing part-throttle driveability improving.
6.) When I'm averaging close to zero LTFTs for a given cell, I capture more data and start trimming individual RPM/KPa coordinates or ranges. Same export and sort in Excel.
It was much much easier in TPI, there's a public domain program called VEMaster which automates this right down to directly modifying the binary and re-checksumming it. I haven't played with Chris' automation tool but it may do something similar. The process is very time consuming but yields good results for me.
Let the discussion ensue...
Bink- I think Ed said it best in the Cam Discussion thread. "The only thing unique about Fill in the blank is the price"
Comapq got me with that bs also
Access would prolly be a lot more efficient. Bink can atest to that

Also what is this VE MAster you speak of.
Trending Topics
Anything you need to know just ask. You can do anything with access!!!!!!!!!!!
The Best V8 Stories One Small Block at Time






