Need help re scaling maf
the formula in evoscan is probably wrong thats why your fuel trims look like that
On your cpu follow this path:
-C:\Program Files\EvoScan\EvoScan v1.0\DataSettings
-You will see a xml file in there, right click on it and select to open it up in wordpad or notepad doesnt matter which one you pick
- Find Fuel Trim LOW, Fuel Trim MID, Fuel Trim HIGH, and 02 Feedback (its not that far from the top, Look for <DataListItem DataLog="N" Color="" Display="Fuel Trim Low" and you will see the rest)
-Remove all 4 lines and replace it with the code below
-Now you should be able to log fuel trims in evoscan
mitsulogger will work right off the back and does not require any editing
But to explain the different meaning:
O2 feedback is STFT
Fuel Trim Low is LTFT for idle
Fuel Trim Mid is LTFT for crusing
Fuel Trim High is LTFT for WOT
The main ones you want to focus on trying to get your fuel trims in order is 02 feedback, fuel trim low (log this @ idle like explained), and fuel trim mid (log this @ a steady cruise like explained)
On your cpu follow this path:
-C:\Program Files\EvoScan\EvoScan v1.0\DataSettings
-You will see a xml file in there, right click on it and select to open it up in wordpad or notepad doesnt matter which one you pick
- Find Fuel Trim LOW, Fuel Trim MID, Fuel Trim HIGH, and 02 Feedback (its not that far from the top, Look for <DataListItem DataLog="N" Color="" Display="Fuel Trim Low" and you will see the rest)
-Remove all 4 lines and replace it with the code below
-Now you should be able to log fuel trims in evoscan
Code:
<DataListItem DataLog="N" Color="" Display="Fuel Trim Low (LTFT)" LogReference="FuelTrim_High" RequestID="0C" Eval="(0.1961*x)-25" Unit="%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="200" ChartMin="0" ChartMax="200" ScalingFactor="1" Notes="Long Term Fuel Trim - Low" Priority="1" Visible="false" />
<DataListItem DataLog="N" Color="" Display="Fuel Trim Mid (LTFT)" LogReference="FuelTrim_Mid" RequestID="0D" Eval="(0.1961*x)-25" Unit="%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="200" ChartMin="0" ChartMax="200" ScalingFactor="1" Notes="Long Term Fuel Trim - Mid" Priority="1" Visible="false" />
<DataListItem DataLog="N" Color="" Display="Fuel Trim High (LTFT)" LogReference="FuelTrim_Low" RequestID="0E" Eval="(0.1961*x)-25" Unit="%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="200" ChartMin="0" ChartMax="200" ScalingFactor="1" Notes="Long Term Fuel Trim - High" Priority="1" Visible="False" />
<DataListItem DataLog="N" Color="" Display="Oxygen Feedback Trim (STFT)" LogReference="O2FeedbackTrim" RequestID="0F" Eval="(0.1961*x)-25" Unit="%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="200" ChartMin="0" ChartMax="200" ScalingFactor="1" Notes="Short Term Fuel Trim - When the fuelling is under closed loop control by the lambda sensor(s), this refers to the amount of fuel added or subtracted from the value retrieved from the fuel map. -5% would mean that the ecu is fuelling 5% less than the map says in order to achieve the ideal air/fuel ratio. Under high loads, the ECU switches off closed loop control, and uses values from the map. At this point, you will see AFC drop to 0%. This is why it is important that fuelling mapping is accurate (or at least rich) at high loads - the ECU does not compensate for errors here. " Priority="1" Visible="false" />
But to explain the different meaning:
O2 feedback is STFT
Fuel Trim Low is LTFT for idle
Fuel Trim Mid is LTFT for crusing
Fuel Trim High is LTFT for WOT
The main ones you want to focus on trying to get your fuel trims in order is 02 feedback, fuel trim low (log this @ idle like explained), and fuel trim mid (log this @ a steady cruise like explained)
Last edited by bnice01; Apr 5, 2008 at 10:07 AM.
Thread
Thread Starter
Forum
Replies
Last Post
