i am datalogging fuel trims in my evoscan 2.9, but the values don't look anything like the numbers from OLEDBC.
Can someone check over the formulas in my Evoscan screen grab and confirm they are correct ?
gawdzinner
i am datalogging fuel trims in my evoscan 2.9, but the values don't look anything like the numbers from OLEDBC.
Can someone check over the formulas in my Evoscan screen grab and confirm they are correct ?
Can someone confirm the fuel trim formula in Evoscan to match OLEDBC?
i am datalogging fuel trims in my evoscan 2.9, but the values don't look anything like the numbers from OLEDBC.
Can someone check over the formulas in my Evoscan screen grab and confirm they are correct ?
So every 4 points is 1% on lcdbc
132 would be +8%, 84 would be -4%. 100 is 0 adjustment. 150 is max it can add (12.5%) 50 is max it can pull. You want them to fall within 80-120, or + or minus 5%.
132 would be +8%, 84 would be -4%. 100 is 0 adjustment. 150 is max it can add (12.5%) 50 is max it can pull. You want them to fall within 80-120, or + or minus 5%.
Also. Evoscan should have options to view front and rear o2 trims. If you are tuned you’ll want to pay attention to low and mid more than high. My 92 TT is that way anyways.
Im not sure you modified evoscan correctly. You should have an option to select 3000gt. You can look on chromed website for how. Look for this image in the getting started tab, and start reading a few paragraphs before it.
![Image]()
^^^ This
You're using the wrong evoscan file. You need the Chrome specific one.
That will give you access to both front and rear bank data, but It won't change the protocol difference between the MUT data displayed on the LCDBC, and the OBDII data displayed in evoscan. OBDII centers on zero, and displays true percentage of fuel being added or removed. MUT centers on 100, and the trim counts are not true percentage. (as posted above, roughly .25% each count.)
You're using the wrong evoscan file. You need the Chrome specific one.
That will give you access to both front and rear bank data, but It won't change the protocol difference between the MUT data displayed on the LCDBC, and the OBDII data displayed in evoscan. OBDII centers on zero, and displays true percentage of fuel being added or removed. MUT centers on 100, and the trim counts are not true percentage. (as posted above, roughly .25% each count.)
I got it working with assistance from Blackstealth.
Again, my setup is jester ECU, with chrome in my 1993 dodge stealth r/t tt. My laptop running win10 and evoscan 2.9 is connected to the oledbc with the serial cable for data logging in pass thru mode. My fix may not work fir other people with different data logging setips.
Here are the evoscan 2.9 settings that i am now using for fuel trims to match the eight fuel trim quantities shown on the oledbc:
![Image]()
Again, my setup is jester ECU, with chrome in my 1993 dodge stealth r/t tt. My laptop running win10 and evoscan 2.9 is connected to the oledbc with the serial cable for data logging in pass thru mode. My fix may not work fir other people with different data logging setips.
Here are the evoscan 2.9 settings that i am now using for fuel trims to match the eight fuel trim quantities shown on the oledbc:
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
