Turbo tuning
Now you can go speed density also 2 or 3 bar. That gives some more choices for the afr under boost and off boost.
Trending Topics
The Best V8 Stories One Small Block at Time
Last edited by NicD; Dec 8, 2008 at 11:58 PM.
Not saying you're wrong, I'm just curious as to why the misfire no longer works.
BTW, I'm a fan of SD applications on FI motors. My STS was only at 5PSI, but ran great with the 2-bar setup. Run my NA application with the same operating system. Works fine. Tuned it myself.
A lot of what people repeat is not correct and it's just something they heard somebody else say. Message forums can be a dangerous place so don't believe everything you read on the interwebz.
You are making more power than your MAF's usable range which is why it "feels" smoother in SD during boost transitions. However if it was throwing MAF codes and stumbling getting in to boost it wasn't tuned well with the MAF properly to begin with. Misfire detection automatically goes out the window in SD since SD is just a backup mode and was never meant to be run full time. Granted if you are past the MAF than speed density is the way to go regardless. No link or details are necessary, it's just the way the operating system operates. Going from a 12.5 to a 13.8 doesn't sound consistent to me and those numbers definitely aren't a 14.7 which is stoich.
Not saying you're wrong, I'm just curious as to why the misfire no longer works.
HP Tuners does shadow applications between operating systems. Load a truck or corvette tune into an operating license for a F-body to read, and all the different parameters from one operating system to the other will be shadowed grey. I do understand what you mean concerning no shadowig for applications designed for the same car, those are not shadowed. I have noted that HP Tuners will default data that it doesn't use though. An example is that on a 2-bar operating system for example, the MAF freq data is defaulted to 0 by the operating system.
Anyhow, the real question is WHY does the PCM disable misfire when in SD mode? I understand that in MAF mode a MAF fail will default to the low octane spark table for safety + the ve table values (limp mode or dumbed down Speed Density.....however you want to look at it.) So, does the PCM determine a misfire based on MAF airflow data? THAT is my question......

Appreciate th info. Didn't know this before. Just want a better understanding why it is so.





