Fuel trims not logging in Evoscan - only getting 0.1? - evolutionm.net
I'm not able to log trims aswell. Wonder if it's similar to the lancers. I have rear o2s disabled.
Printable View
Fuel trims not logging in Evoscan - only getting 0.1? - evolutionm.net
I'm not able to log trims aswell. Wonder if it's similar to the lancers. I have rear o2s disabled.
You're able to log trims. It's just with periphery 2, the front trims are disabled.
There are 2 sets of trims. If you don't see both, you aren't using my evoscan XML.
I replaced the data file with yours Greg, so I'll check if I missed another trim setting then try replacing it again if that doesn't work. Then I'll re-enable any cel to do with the rear o2s and see if that fixes it. Finally I'll change the injector size if all else fails.
Do you have Bit 2 Disabled in the Periphery 0 bits? That must be disabled (for now). Make sure your periphery bits match mine as posted earlier in this thread. Until V2 is released you will only have 1 02 actually doing anything, but that is fixed in V2.
Mine match, I made sure to find that post when I was setting it up.
Does it happen to be the front o2 that does anything? Because uh... mines cut.
I'd say that's your problem.Quote:
Originally Posted by Goallie11
The rear 02 is the one that is used when bit02 is disabed. Also verify that your 02's are properly hooked up on your adapter harness. Finally the front 02 trims should all be zero'd out, because they are disabled.Quote:
Originally Posted by Goallie11
On the 99 harness pin 71 if the rear o2 and pin 72 its the front o2....
Are we supposed to be using ODBII 96+ or MUTIII in evoscan, I saw earlier in the thread it's MUTIII but after replacing my data.xml file and looking there aren't anymore fuel trims in it, but ODBII 96+ has a lot.
hell yeah that's the problem. When the ecu sees 0 volts on the o2 it adds maximum amount of fuel. The exact same thing happened to me when my o2 wire was damaged. Use mutIII