LTFT learn ?
Kinda new at this tuning thing.
Kinda new at this tuning thing.Another question: Are you resetting your LTFT's after you tweak the VE table?
Another question: Are you resetting your LTFT's after you tweak the VE table?
They have moved closer to 0 and in some cell's they have gone +. Also I did re-set the trims after I changed the VE table.Let me throw another ? at ya, in the scanner utility it ask for "fuel trim learn" OFF or ON, what is the purpose of this function. I would have thought that the PCM would automatically do that. Thank you for your help!
And another question for you: you are running in SD mode, are you not?
Edit: At this point, I'm going to assume you are, because I think I see what's happening. From your first post you say the your LTFT's were -12 to -14, and that your STFT's "were not too far off", by which I assume you mean they were around -12 to -14 as well. So, if for a particular cell your LTFT is -12, and your STFT is -12, this equals a net fuel correction of -24. So, if you simply copy your LTFT histogram and "paste special - add" to the VE table in the editor, you are only making half the correction. So, your LTFT's will learn out to be about the same, but you STFT's will be closer to zero.
Tuning with LTFT's alone is not really utilizing all the info. To do it properly, you need to add both the LTFT and STFT value for a particular cell before applying it to the VE table. Otherwise you're taking the long way around. Then, once your LTFT's are within +/- 10, you can disable them and just tune with your STFT's.
Last edited by Silverhawk_02TA; Apr 9, 2005 at 02:16 PM.
And another question for you: you are running in SD mode, are you not?
Trending Topics

The Best V8 Stories One Small Block at Time

Since STFT's are a moment to moment reaction to what the O2's are reading, they vary wildly over time. In your STFT histogram, first display min value, and then max value, and you'll see what I mean. This is why we use the "average" option on the histogram. Under closed loop operation, the PCM is not maintaining a steady AFR. It is constantly cycling between rich and lean. This is why the charted O2 voltage looks like a sine wave. First, the O2's will read a rich condition, so the STFT's will go negative to lean the AFR down some. Then the O2's will read a lean condition, so the STFT's will go positive to compensate. If you ever hook up an AFR gauge, you'll be able to see this in action as the LED's bounce around from rich to lean.
This being so, if you only fall into a particular STFT cell for a brief period while you are logging, you could see almost any value, and it could have little correlation to what the true (average) STFT really is. The only way to get an accurate STFT is to hit the same cell again and again and again on the same run. This is where driving method while you are logging plays a huge role. Driving "normally" you will hit some cells quite often, and others very infrequently.
Now, this is the part where I leave you hanging...
Seriously though, I've seen several questions about tuning with STFT's in particular lately, so I guess I'll throw together an "STFT tuning guide" or some crap like that which outlines the method I used, which worked very well for me. Maybe I'll include it in a larger "Tuning Guide" to throw into the pile with all the others. It'll give me something to do with my time now that I'm unemployed.
So, keep your eyes on this forum. I'll throw something up here soon.
Since STFT's are a moment to moment reaction to what the O2's are reading, they vary wildly over time. In your STFT histogram, first display min value, and then max value, and you'll see what I mean. This is why we use the "average" option on the histogram. Under closed loop operation, the PCM is not maintaining a steady AFR. It is constantly cycling between rich and lean. This is why the charted O2 voltage looks like a sine wave. First, the O2's will read a rich condition, so the STFT's will go negative to lean the AFR down some. Then the O2's will read a lean condition, so the STFT's will go positive to compensate. If you ever hook up an AFR gauge, you'll be able to see this in action as the LED's bounce around from rich to lean.
This being so, if you only fall into a particular STFT cell for a brief period while you are logging, you could see almost any value, and it could have little correlation to what the true (average) STFT really is. The only way to get an accurate STFT is to hit the same cell again and again and again on the same run. This is where driving method while you are logging plays a huge role. Driving "normally" you will hit some cells quite often, and others very infrequently.
Now, this is the part where I leave you hanging...
Seriously though, I've seen several questions about tuning with STFT's in particular lately, so I guess I'll throw together an "STFT tuning guide" or some crap like that which outlines the method I used, which worked very well for me. Maybe I'll include it in a larger "Tuning Guide" to throw into the pile with all the others. It'll give me something to do with my time now that I'm unemployed.
So, keep your eyes on this forum. I'll throw something up here soon.
Don't know about the idle.
If you want, you can send your .bin and log file to bluetorp@yahoo.com and I'll take a look.
Don't know about the idle.
If you want, you can send your .bin and log file to bluetorp@yahoo.com and I'll take a look.


