Let me try again those other tables where plotted with the gm Cyl air.
Also I have not made any adjustments to any spark tables from what I had before.

Here are the tables using calc cyl air.

Before
After
This after was actually a log done on the street not the track. I wasn't logging a parameter I needed for the Calculated Cylinder air to work.

 

opps sorry i am wrong, you had the right PID in the beginning, GM.CYLAIR_DMA is for MAF and GM.DYNCYLAIR_DMA is for Speed density when trying to reference airmass and correlate it to your spark tables.......

 

Ok that makes sense and explains why my times are slower although I still don't think something is right. Doesn't seem like helping the truck breath better should make it slower and for some reason on the street it just feels like it has much more power than before even though it's not showing it in the numbers or on the track. I'm confused.

And to top it all off I'm still having the problem with the P1516 code on long WOT runs at the top of second gear.

 

Did you retune the VE and/or MAF tables?

 

VE is currently disabled and the MAF was retuned. Maybe my wideband is crap.

 

Are you sure it is p1516 and not p1514? P1514 is easily fixed, i am not sure on P1516, are you using the DRx harness? Have you tried cleaning the TB really good, i had a problem before where my ported TB would stick, and go into REP...


Also since your airmass has changed since before that means that your gonna get a different spark value... If you could do the same plot above but put in spark advance and this way you can see if your timing has changed... The reason this is important is because on NA vehicles timing = power...

 

Unfortunately I'm sure it is the P1516 code. I have run into the P1514 code before and know how to deal with it. The first time it happened I thought that's what it was but found that not to be the case and have no idea what is going on and it seems odd that it only goes to REP at the top of second gear. I am using the Dr. X harness and no wires are cut.

Thanks for your input so far. I will look at working on the timing and fueling some more to get that ironed out and see if I can get the power up where it should be, but the big issue is to get the P1516 code to go away so I can actually make a full run without having REP kick on.

 

In EFI live we have a table called "ETC Max Predicted MAF Flow" (This table limits the estimated airflow for ETC diagnostics), it is related to DBW TBs Try increasing that table by 25%. From looking at a stock 5.3 tune, it looks like your out flowing that table. It might help or it might not, but it is worth a shot...

A stock 5.3 table looks like this. Notice it is in Milligrams to divide that number my 100 to translate it to Grams/Cylinder and you will see what i am talking about...

LABELS ETC Max Predicted MAF Flow (Milligrams Per Cylinder)
RPM Value
0 615.000000
500 590.000000
1000 625.000000
1500 645.000000
2000 655.000000
2500 665.000000
3000 665.000000
3500 685.000000
4000 705.000000
4500 685.000000
5000 690.000000
5500 635.000000
6000 635.000000
6500 635.000000
7000 635.000000
7500 635.000000
8000 635.000000


Also i assume you increased the ETC Predicted Airflow table too???
it is TB % vs RPM

 

Another thing to try if the above does not help is lower your VE table by 5-10%. Even thou your running pure MAF, the computer still references/tests the difference between teh MAP/MAF airmass calculations....

 

I've did increased the ETC Predicted Airflow table. I had to after I put the cam it because I was getting the P1514 code on occasion. My first run down the track after with the TBSS intake I thought this was the problem again so I actually upped it a little more before I checked and found that code wasn't the problems this time. I'll try lowering the VE table and getting it tuned in as soon as I can to see if the problem goes away and I will check the ETC Max Predicted MAF Flow cause I can't remember if I did anything with it or not.

I also found some diagnostic procedures for the P1516 code so I can go through those and see if I can find an issue there.