-
Dialing in PE at WOT
Any tips on how to dial in PE perfectly?
Right now high rpm disabled above 3000, I see +- 5 percent of my target PE at WOT. I primarily use my MAF frequency to change actual AFR, but it seems it will either shoot a little high or low, and you can see lambda fluxuate rapidly within a given MAF frequency tab (example bounce .82-.88 lambda at 10,750HZ from 6000-6600rpm)
Would scaling the VE table help, even if the ECM is using primarily the MAF for fueling?
-
I can't see your Lambda fluctuate.
Got any info on the setup, and you know the routine---post the tune and log. :)
-
2 Attachment(s)
Here are the files. Let me know what you think!
Its a 2000 Transam, Cam only FBO LS3 with a t56. 0411 ECM, DBC
-
That attached file is a fuzzy picture of something. Post your .hpt tune file and your .hpl scan file.
-
2 Attachment(s)
Tell me if this works? Uploaded directly from scanner and editor save folders.
-
-
The VE is always used, even in the background.
Tune your VE tables and see if it gets better. You should have applied the speed density OS to remove the secondary VE table, makes things much faster for tuning VE.
Don't rule out other possible causes like a minor voltage drop to the fuel pump causing a drop in fuel pressure. But in the end if you are within a few percent of the commanded the entire time I wouldn't even bat an eye when dealing with a decently modded engine.
-
Thanks for the information.
Should I still apply the speed density OS? Or, is it not worth it?
-
It's up to you.
You could flash back to stock, then apply the speed density OS and copy over the previous tune data. The speed density OS just removes the secondary VE and it's just something I prefer to do on those early computers. The MAF still functions like normal. If you keep what you have it's not a big deal, it's just another step for copy/pasting the data between the two VE tables because the primary isn't used during speed density tuning.