From what I can tell, Evoscan v2.4 uses exactly the same requests and calculations for trims as Mitsulogger.

 

I haven't tried mid yet, just been lazy. Hopefully tomorrow I'll get some time to do a nice cruise log.

 

Still having lean idle issues on my PTE 780s

Injectors are scaled to 680 and injector latencies are:

3.312
1.68
1.032
1.056
0.888
0.672
0.528

cant figure out how to adjust in order to fix the issue... as a bandaid i only increased timing on idle load cells, from 5 to 7 which helps a little bit but i am a bit frustrated since PTE780s are known for their nearly stock idle and response...
any ideas?

 

What are your trims? If you are lean then you could go down on your global or add more latency on your 14v trims are the key here though IMO

 

Here's the scalings I found on the boards that have worked well for me on my car. I also have the PTE780's

3.504
2.184
1.224
0.96
0.744
0.552
0.432

Scaling of 696

I scaled at idle with v2.4 and it was perfect, right at -3.2, I haven't done cruise yet but my car idles perfect and cruises fine too.

Hope it helps.

 

thanks guys!

I will definitely try your scaling since youngave the same injectors and see how my car reacts. When you say v2.4 I assume you mew evoscan right?

Increasing the latency we make the number higher and vice versa correct?

 

I'm having some problems logging my trims.......no matter what I do these trims will not move! I can vary the injector scaling by 100cc and the latencies by 1V and nothing happens....they stay the same.....both on evoscan and mitsulogger, has this happened to anyone else? Any ideas?

 

Be aware that the trims changes can take a long time. Sometimes after 10 min of driving nothing changes. Same for idle trims which changes only after a long idle running time.
I do it that way: Drive a few days. Than check what is changed.

 

I had to remove and re-install evoscan due to trims not changing. It is best to look at trims with multiple programs to make sure the program itslef is not faulty. (learned my lesson the hard way)Mitsulogger is what i used to dial in my FIC's and i used both Evoscan and Scantech to make sure trims were moving. Scantech is cool in that you can see multiple trims actually moving in real time. I believe these trims are averaged to create final trims after what the ecu calls a drive cycle or something like that . STFT low occurs after around 10-15 minutes of idle and it is said stft mid occurs after 15 min. of steady cruising at highway speeds. I am repeating a lot of what i have read from others and what I have seen in my own experiences.

 

First thing to look at is 02 feedback, that should be changing in real time and you do not have to wait for that to "cycle", just make sure the car is at operating temp.

if 02 feedback doesn't move whatsoever, then either you have a logging issue or your 02 is dead or disconnected.

 

02 feedback is cycling just fine.....it's just my fuel trims that are stuck. I've logged for 20 min+ multiple times changing the voltages by almost 1 and injector scaling by 100cc.....the car runs noticeably difference (sometimes real ****ty....other times good) but the fuel trims don't change. I've reinstalled evoscan....used older version/newer versions etc.....nothing works....and I've tried logging with multiple programs....mitsulogger says the same thing

 

Alright....just a little update. If I unplug my battery the trims reset to zero I can log for 16 minutes and see my fuel trims.....kinda a ghetto rigged way to go about things, but it works I guess....

 

That is correct.

On a Evo 8, fuel trims do not reset unless you cut the power to the ECU.

On a Evo 9, fuel trims reset every time you flash the ECU.

Now I understand the "issue" you are having. You have a 03-05 Evo correct?

 

Nope....2001 eclipse gs.....the ecu is interchangable with the 03-05 evo though......and I have an evo8 rom on it......

 

Ok then it will work the same way.

It does make it a bit of a pita to scale injectors on the 03-05. I alway start by pulling the power first.

The 02 feedback should give you a good idea if the latency changes you are making are moving you in the right direction or not, regardless of the longer fuel trims.