Here is the situation that I am having with this Evo 9. The car has the following mods:

TBE w/tp
ARC intake box
Works O2 housing
Full Race header
RC 1000 cc injectors
XS Engineering FMIC

The injectors were scaled and the Latencies were set. The LTFT Low and Mid were changing as well as the STFT.

Now the STFT changes, but the LTFT Low and Mid do NOT budge. After I flash the ECU the Low and Mid trims stay at the default 0.1008 number. I flashed the car with different flashes and they still do not budge. The STFT changes, but the Mid and Low do nothing. I logged the car at idle and at cruise for a long time and still they do not change.

I checked the same flash on my car and the Low and Mid trims move just fine. So I know that it is not the flash and not Evoscan.

I REALLY need help with this one, because I am stumped.

 

I've got a similar issue ... a customer is using EvoScan and can't get the trims to log. I've verified the XML on my computer and it works fine. But he gets the same 0.1008 on his. Mitsulogger and his scan tool can read the trims fine. I'm pretty sure this is an EvoScan issue.

This car is an Evo VIII. 94170015 from 94170008.

 

I've had this problem with evoscan as well. When I change some definitios for logging it gets all hosed up and won't log.

Just for an idiot check make sure you aren't throwing an O2 sensor code and that the coolant temp sensor is operation properly. With a coolant temp or O2 sensor code the ecu won't update the trims.

 

NJ, I suggest that you try logging with Mitsulogger.

In my case, the trims are changing, just not logging. I wish the guy was closer so I could check the issue myself.

FWIW, I've never had a trim logging issue with .99. He's running 2.1. However, it logs fine on my copy of 2.1.

 

NJ, just to be sure, use Mitsulogger to log the trims. I have seen so many issues with fuel trims and EvoScan, it's worth a shot.

Also, if Mitsulogger reports the same, check what dan l mentioned above.


Eric

 

Thanks guys,

I used my laptop and my Evoscan on HIS car and the trims did not budge. Then I used my laptop and my Evoscan on MY car and the trims changed.

That means that this is a car issue and not my Evoscan/laptop. If it was Evoscan/laptop then the trims would not budge on my car as well. We used the same flash on both cars.

Nevertheless, I will try Mitsulogger and see what happens.

 

this weekend I saw this too on a 0,3 but he did have a SES/CEL light.

 

Well again this 03... dtcs reset, reflased with my xml and after 1 week still no ltft lo and no ltft mid, both at .108. There is stft activity but trims won't set, and the car idles lean. Acts like it is in open loop at idle but AFR was spot on on the dyno.
I've looked at his open load & open throttle maps they are stock...what can cause this?