LTFTs are all the same for ALL roms.
23804577

 

my fuel trim high address is 238071FE in evoscan under mode23 JP/EU/AU. thats the only one that doesnt log properly, i'll try the address you posted golden. ps thanks for your help on evoxforums re 3port tuning today (username: bentX). sent you a pm over there!

 

Fuel trim High is 23804577 for all roms. Every single one.

 

I input the code from the first post into my MISC section of my XML file right?

 

So going through issues with the LTFT applied values. I almost wonder if the 8/9 did this but since I disable them when I do the rear O2 fix I never noticed.

Question-

Why even set the values as high as they are (300) and not lower, for instance 160ish?

Aaron

 

My best guess was they wanted what was happening at mid throttle to have a small effect on WOT, and an unmodified car wouldn't really go above that area. The system was probably designed to have a different feedback at WOT (maybe for wideband equipped cars or just an analyst who didn't know what he was doing) and this was a bandaid to get some feedback, but base it on the normal expected narrowband fueling.

 

Yes the 8/9 has this table as well.

 

if you set the value too low, then you will populate LTFT-High...

why?

because you will still be in closed loop.

you want to pick a value that will be in openloop and thus STFT will always be zero...

 

So it would seem that if the 8/9 has this table cant we also fix with the rear O2 periphery and disable the LTFT application to WOT? I understand what you mean David, I didnt think it all the way out. I have a car here that the values are set to 350/335 and it still is applying LTFT to WOT. Oddly enough it only seems to be doing it on pumpgas so I am thinking maybe its a matter of not having the trims dialed as close as they should be.

Aaron

 

Was the 350/335 had the MAF rescaled?

if the MAF isn't scaled correctly (ie its over scaled to compensate for injectors that arn't scaled properly) then your bin hz's will be wrong.

easiest way would be to log MAFHz (whatever MUT ID it is) and then you can find your best cutover hz..

 

Just log your trim in use and your STFT and see if it goes to 0 when you get into throttle.

 

cool

 

MAF was rescaled for the Primo 3.5 I will look into it a little deeper then.

Aaron

 

I just about get it, but its my first time tuning with non stock injectors so take it easy. Sometimes reading all this stuff for hours late at night I fear tephra will respond with a post of all hex code I don't understand, and that will make acamus jump out of his icon/avatar and strike me down!

I understand the thread, mostly, great, but why exactly is the STFT 0% in Open Loop?

Besides seeing in my logs that at WOT STFT is 0, what is the reason? Should I understand and know why?

 

openloop means running without any input from the oxygen sensor.

so when running in openloop the ECU doesn't bother setting up the STFT.. which is why its 0