The table was actually stolen from someone in CT9A land - I forget who

But yes I thought about running 3 legitimate LTFT's, but really without exhaustive testing it's hard to know exactly how to set it all up.

I found that the mid trim varied so much that the stock setup really wasn't ideal. So "disabling" it seemed like the best option. So far my WOT AFR's have been much more predictable.

I settled on 343/350, since this is about 140-160 load (at 2500rpm) .

Same 1byte MAFHz setup on the X btw...

 

Have you found the fuel trim calc subroutine for the Evo 10? The subroutine for CT9A is much simpler than I thought it would be. Looks like the LTFT mid and high are calculated in exactly the same manner.

 

From a tuning aspect would the LTFT change trigger a CEL (system too lean) if the trims go too far positive (+12.5%) even if you disable their effect on AFR at WOT?

If the trims no longer impact AFR at WOT, is there a way to disable the CEL coming on as a result of the LTFT going max positive because of the use of intakes?

 

These crossover LTFT points were discovered in part by my constant begging for adjustment of the Hz values for running aftermarket intake pipes that affect idle Hz values. By increasing the value you can get LTFT low to adjust quite easily for any intake. Simply log your idle Hz and increase the low values to make sure that you are ideling under them.

I love that you discovered more of a use for them. I always wondered why the high was never called. Now I know.

Thanks again Tephra....you are the EVO GOD ! !

 

It is the same code compiled for different processor.

 

This is a related side issue. The published formula for fuel trims for Evoscan and Misulogger is (x*.1961)-25. However, isn't the exact formula [25(x-128)]/128 which calculates to (x*.1953)-25. Which one is correct?

 

I use this formila, works fine.

 

I use x * 0.1953125 - 25 - which is basically your formula.

In truth it doesn't really matter either way. I prefer mine/yours since it results in 0% and not 0.1008 or whatever

 

Could you please confirm MUT50 for 53040010 or the address for the MUT table

 

Think i found mut table 3e3b8

 

yep thats right...

 

sub'd

 

Does this work on the 2010 USDM Evo X? I added the code to the 2010 rom xml file and got the same table/values for the 2008 USDM Evo X. Does that mean that it should work?

TIA

 

This tweek is great.....we can leave Lean Spool enabled and now do WOT pulls that are consistant from pull to pull.

 

doesn anyone know location of mut table for 5304007 ? Need it for logging mut50 adress .