Calculated new MAF Table
My VE table is starting to look a lot like the picture I saw (I think of Magnus' tune). Just a little more work...
In the end, we are trying to achieve negative LTFT at stoich without lean charges passed into WOT. In the end, even modifying the VE or MAF you are doing exactly the same as rescaling the IFR's. This is because when you assign more air you indirectly alter the injector pulse width. Whether by IFR or VE or MAF, the injector pulse width will be impacted exactly the same. So you wont be maxing out the injectors any more using either technique.
Just food for thought. Im not saying you are doing the wrong thing. I wish the MAF and VE were easier to scale.
In the end, we are trying to achieve negative LTFT at stoich without lean charges passed into WOT. In the end, even modifying the VE or MAF you are doing exactly the same as rescaling the IFR's. This is because when you assign more air you indirectly alter the injector pulse width. Whether by IFR or VE or MAF, the injector pulse width will be impacted exactly the same. So you wont be maxing out the injectors any more using either technique.
Just food for thought. Im not saying you are doing the wrong thing. I wish the MAF and VE were easier to scale.
When we dyno we make sure it one of the logged values just to make sure
The Best V8 Stories One Small Block at Time

I also have a very similar problem, despite MAF and VE being tuned a zillion times, and having it really close to what it supposed to be, I still get knock. I was hoping it's old plugs/wires, so I changed them to new pimpy ones, but I still get the same <2deg knock in the silliest of moments (cruising at low rpm with barely any load on it), and I have very conservative spark/PE settings. if anyone has a good idea what should i scan for, please let me know. I've already ripped through the data, trying to find patterns of what could be possibly causing it, and I can't find anything. No tip-in, no sudden deceleration, none of the usual suspects cause this retard.
any ideas?

I also have a very similar problem, despite MAF and VE being tuned a zillion times, and having it really close to what it supposed to be, I still get knock. I was hoping it's old plugs/wires, so I changed them to new pimpy ones, but I still get the same <2deg knock in the silliest of moments (cruising at low rpm with barely any load on it), and I have very conservative spark/PE settings. if anyone has a good idea what should i scan for, please let me know. I've already ripped through the data, trying to find patterns of what could be possibly causing it, and I can't find anything. No tip-in, no sudden deceleration, none of the usual suspects cause this retard.
any ideas?
Yeah I had some knock in about 20 cells. I had about 40 cells of WOT and only 3 of those had knock, and that knock was only .35. It was kinda wierd. My PE and Spar settings are stock. Thanks for all the good work on the spreadsheet. I unfortunately wont get to do any tuning again for another week so hopefully then I will get the VE down and then try MAF again.

I also have a very similar problem, despite MAF and VE being tuned a zillion times, and having it really close to what it supposed to be, I still get knock. I was hoping it's old plugs/wires, so I changed them to new pimpy ones, but I still get the same <2deg knock in the silliest of moments (cruising at low rpm with barely any load on it), and I have very conservative spark/PE settings. if anyone has a good idea what should i scan for, please let me know. I've already ripped through the data, trying to find patterns of what could be possibly causing it, and I can't find anything. No tip-in, no sudden deceleration, none of the usual suspects cause this retard.
any ideas?
My new personal discovery is how sensitive MAF is to airflow changes in general, not just in the pre-MAF section. I put in LS6 intake on last week, and recalibrated my MAF, and it looks like there's more airflow through the whole range. that's kinda cool, demonstrates that if something's holding up the airflow even past the airflow measuring device, the whole flow is still affected, not just a section of it. oh how i love busting up internet myths
The cool part is when you plug both new tables in, and suddenly every works write and you get nice clean dead on VE values, trans doesn't shift like ****, and PE suddenly is smoother and without knock. And it also takes less time to do both at the same time

and stop screwing with IFR tables, people! you might be adjusting the mixture, but you're adjusting it through the wrong portion of the mixture, so while you might be fixing one thing, you're screwing up another. sorry, i ranted off there for a moment
IFR = Injector Fueling
Airflow = MAF or SD
Always change IFR. Never change MAF.
Can you make it work. Yes, but poorly.
Perry
Always change IFR. Never change MAF.
Can you make it work. Yes, but poorly.
Perry
Always change IFR = always BS to your PCM about what you really are pushing
Never change MAF = never change the device that deals DIRECTLY with what the problem is here... airflow.
MAF calibration does not pick up a change in air volume when we deal with ported/aftermarket MAFs since it is not adaptive. When we mod, we not only change air velocity but also air volume. These sensors have the ability to be accurate so long as they know what to be accurate about. So what we're doing is measuring and redefining the airflow as the motor requests and uses. You can see graphically, at least in my case, that after all my mods, my motor uses about 20-30% more airflow than what the MAF is reporting. I could actually breakdown how much % off my stock calibration was at each individual MAF calibration point but that would take a lot more space than I already have. With this kind of precision, why not use the MAF for what it's for and tell it correctly what kind of airflow it will expect to see through its calibration?
Even if we're not 100% totally on, it seems like scaling IFRs is like throwing fuel in to compensate for extra airflow, but there's no airflow data to really target from. You add fuel or subtract fuel to produce whatever AFR you want, despite what the PCM commands and all this while making your PCM think it's got bigger/smaller juicers. Why not work with readily available data? I used to get IFRs scaled around before I knew too much about this stuff and the one thing i look back and remember is that yes my car put out 13.0 AFR on the dyno, but my PCM was commanding 11.7. So it sounds more like scaling IFRs is the "make it work" solution here. Now when i command 13.0, i get 13.0, or 12.5 or whatever I want. No guess work anymore, just tell it to do and it does. Stock GM 26#er IFRs and my car runs smooth, makes awesome power, and the EFI responds to command and correction as it should. Also, my MAF reports almost exactly the airflow the VE calcs come up with during combustion so there's no fueling confusion there since even if it's a biased decision b/w MAF or SD, they both show the same airflow.
Can I make it work? I did and it worked VERY VERY well, while being VERY VERY easy too
Always change IFR. Never change MAF.
Can you make it work. Yes, but poorly.
Perry
Once that has been accomplished. For that particular set of VE references (your whole VE table) there will be SD airmass calcs that are a parameter of your whole VE fueling equation. This is how the car knows how much fuel to use. Now here's another question: how do we know these SD airmass calcs are correct? Well, I'm not exactly sure how GM came up with them, but they are adaptive, and if your VE is tuned correctly then whatever values they may be, are the direct airmass calcs that allow you to command an AFR and produce it during combustion. These airmass calcs are what the MAF ought to be reporting. The MAF can sense changes in air velocity, though not completely, but defintely not volume. that's why the MAF is such a wonderful thing, it was designed as a user input device to create a user inputted function! It's something we can measure and fix! YAY
Once you are on your final VE that responds to as been commanded, tune your MAF shortly after. You will want to do this on a medium weather type day for your climate as well, as to anchor your tune in the center of your weather conditions. We all know cold tunes don't work well in hot weather so we do a medium tune that works it all kinds of weather. In TX it's been going from 40 up to 70 back down to 40 all in a few days and my tune has held up very well. No loss of driveability and drive hard and strong at WOT. I'm waiting for those 90 degree days to come back to prove my statements of late but I have a good feeling it'll work out just fine.
Always change IFR = always BS to your PCM about what you really are pushing
Never change MAF = never change the device that deals DIRECTLY with what the problem is here... airflow.
MAF calibration does not pick up a change in air volume when we deal with ported/aftermarket MAFs since it is not adaptive. When we mod, we not only change air velocity but also air volume. These sensors have the ability to be accurate so long as they know what to be accurate about. So what we're doing is measuring and redefining the airflow as the motor requests and uses. You can see graphically, at least in my case, that after all my mods, my motor uses about 20-30% more airflow than what the MAF is reporting. I could actually breakdown how much % off my stock calibration was at each individual MAF calibration point but that would take a lot more space than I already have. With this kind of precision, why not use the MAF for what it's for and tell it correctly what kind of airflow it will expect to see through its calibration?
Even if we're not 100% totally on, it seems like scaling IFRs is like throwing fuel in to compensate for extra airflow, but there's no airflow data to really target from. You add fuel or subtract fuel to produce whatever AFR you want, despite what the PCM commands and all this while making your PCM think it's got bigger/smaller juicers. Why not work with readily available data? I used to get IFRs scaled around before I knew too much about this stuff and the one thing i look back and remember is that yes my car put out 13.0 AFR on the dyno, but my PCM was commanding 11.7. So it sounds more like scaling IFRs is the "make it work" solution here. Now when i command 13.0, i get 13.0, or 12.5 or whatever I want. No guess work anymore, just tell it to do and it does. Stock GM 26#er IFRs and my car runs smooth, makes awesome power, and the EFI responds to command and correction as it should. Also, my MAF reports almost exactly the airflow the VE calcs come up with during combustion so there's no fueling confusion there since even if it's a biased decision b/w MAF or SD, they both show the same airflow.
Can I make it work? I did and it worked VERY VERY well, while being VERY VERY easy too

Ive tried your method and got some success, but it stuffed up too many other things in my tune - things like calculated cylinder fill, calculated transmission torque, calculated engine torque to name a few. With IFRs I can mod without having to readjust my MAF or VE every time.
and Nup. 
The problem is not airlflow. The problem is AFR.
If you are running SD WITHOUT a MAF then sure - I agree - get the VE right - its all about VE. If you run a bastardised MAF - then sure - I agree - get the MAF right - its all about MAF. Better to leave the MAF alone though
.If you DO run a stock MAF - that device has been calibrated correctly in controlled conditions to generate the most stable average airflow reading possible. You will not do a better job by road tuning based on the residual LTFTs that are impacted by air density and temperature variations.
It's people who bastardise the MAF by pulling the laminar screen and porting the aerofoils that have changed the MAF performance and so a recal. is necessary.
Commanded AFR is a byproduct of airflow and injector pulsewidth calculations and rescaling the IFR will not cause fluctuating AFRs. If you have stable TRIMS you should get stable fuelling at WOT.
IFRs, however, will offset the actual AFR for a given commanded AFR - I agree with you on that - but so what? What happens if you reach a state where the actual AFR reads the Commanded AFR and you STILL have positive or unstable LTFTs?
The goal is not to get the commanded AFR reading actual AFR. It is what it is and will vary from car to car. You just need to know what the diferential is so you can begin making LINEAR adjustments.
Tuning is about maintaining the correct AFR for the intended engine load and RPM. Im glad it worked for you. Im glad it worked for me. If anything this debate has shown is that there are repurcussions with whatever you do and with whatever approach you adopt you need to be prepared to deal with the consequences.
Hope this helps some.



