Jim in Tucson

iTrader: (3)

I've been struggling to learn EvoScan; however, I have not been able to locate any documentation, so the educational opportunity is rather limited. I thought an EvoScan Glossary would at least be a starting point and might well eventually evolve into actual documentation.

Please post definitions and I'll update this thread.

I also have a similar thread for EcuFlash.

EvoScan Glossary in process

Throttle Position - Reading in % from the throttle position sensor on the throttle body.

Engine RPM – DUH! - Engine Revolutions Per Minute.

Boost (MDP) - Reading from the USDM MPD sensor in the intake manifold (in volts I believe). This info isn't really useful and the sensor can be replaced with the JDM MAP sensor for boost logging.

Airflow/Rev -

Timing Advance - Current ignition advance and should go along with your high octane timing map unless there is a problem (knock).

Fuel Trim Low - Short term fuel trim applied to reach stoic during idle/cruise. Fuel trims are also applied to open loop fueling which can throw off your tuned AFR values. the base value in EvoScan is 100%. A positive change means that fuel is being added and a negative change means that fuel is being taken away. If these values get too far off (beyond 5% or so) you will need to adjust your MAF scaling, Injector Scaling or Injector Latency to compensate.

Fuel Trim Mid - Same as short term but this value changes less often.

Fuel Trim High - Highest level of fuel trim. If this number changes from 100%, you have likely got some serious issues to track down.

Oxygen Feedback Trim - Immediate trim applied to the fuel to reach stoich. This value will change many times per second. If this value stays away from 100% for a specific period of time, the offset is rolled over to the fuel trim low value.

Oxygen Sensor - voltage reading from the O2 sensor in the turbo outlet pipe.

Oxygen Sensor #2 - Voltage reading from the O2 sensor in or after the cat.

Speed - Vehicle speed. This value has a slow response time and will be 'choppy' in your log.

Coolant Temp - Current coolant temperature.

Air Flow Hz - Air flow reading from the MAF sensor. this value is capped at 1600. There is a 2-byte mod available to extend the 1600 limit.

Air Temperature - Intake air temp at the MAF. This value does not reflect the turbo or IC's effect on the intake charge temperature.

Injector Pulse Width -

Battery Level - Current voltage output from the battery. This more accurately might be considered alternator output, measured at the battery.

AFR Map -

Load Calculated - Calculated value used to determine the actual ECU load value for tuning. this is fairly accurate on a stock car but the calculation must be altered when injectors are changed. This value has shown to be slightly higher than the 2-byte load value.

Wideband A/F Ratio - A:F reading from an installed wideband O2 sensor. This can not be logged if you have not installed an aftermarket 5v O2 sensor and controller.

Air Volume -

Barometer - Barometric pressure reading (from the MAF?).

Knock Sum -
With IX, counts of knock detected, 6 or greater and the ECU will switch to the low octane map.
With VIII, counts of knock detected, 4 or greater and the ECU will switch to the low octane map.

ISC Steps -

ECULoad - This is a measure of the Load % the ECU is receiving. This value is limited to 200 and therefore not useful on a modded car. The 2-byte load value will give the same information and extend the 200% limit to the ~500 range.

Load MUT 2Byte Mod - This is a 2-byte response from ECU RAM that gives the actual load read by the ECU. This is very accurate for tuning.

RPM MUT 2Byte Mod - This is a 2-byte response from ECU RAM that gives the actual RPM read by the ECU. This gives more accurate RPM values and is useful for road dyno calculations.

E1 RAM 1Byte Mod -

E4 RAM 2Byte Mod -

Octane Level - This value is a reflection of sustained knock counts. When the ECU sees knock of 6 or more, this octane value decreases from 100. When this value decreases the ECU begins to interpolate with the low octane fuel and timing maps. The lower the octane value, the greater the interpolation between the high and low maps.

Target Idle RPM
Knock Voltage
knock_adc_processed
knock_base
knock_var
knock_change
knock_dynamics
knock_flag
EGR Temperature

80210

iTrader: (23)

Logging: Usually a 3rd gear pull starting at 2500rpm to 7000rpm
Log: The information that the computer recieves while logging is transfered to an excel file. Within the file are many different ramifications including the famous knock sum column.
Real Time Graph: You can actually graph various attributes (speed versus knock sum, etc.)
Gauge Templates: You are able to create your own gauges in evoscan that will work during logging. I don't usually take much advantage of this feature but I suppose some people may find them useful.

slicedbreadno2

iTrader: (9)

Subscribes.

TouringBubble

iTrader: (2)

Throttle Position - Reading in % from the throttle position sensor on the throttle body.

Boost (MDP) - this is the reading from the USDM MPD sensor in the intake manifold (in volts i believe). This info isn't really useful and the sensor can be replaced with the JDM MAP sensor for boost logging.

Timing Advance - this is the current ignition advance and should go along with your high octan timing map unless there is a problem (knock).

I don't know too much about the fuel trims, but I'll take a crack at it ...

Fuel Trim Low - this is the short term fuel trim applied to reach stoic during idle/cruise. Fuel trims are also applied to open loop fueling which can throw off your tuned AFR values. the base value in EvoScan is 100%. A positive change means that fuel is being added and a negative change means that fuel is being taken away. If these values get too far off (beyond 5% or so) you will need to adjust your MAF scaling, Injector Scaling or Injector Latency to compensate.

Fuel Trim Mid - same as short term but this value changes less often.

Fuel Trim High - Highest level of fuel trim. If this number changes from 100%, you have likely got some serious issues to track down.

Oxygen Feedback Trim - this is the immediate trim applied to the fuel to reach stoich. This value will change many times per second. If this value stays away from 100% for a specific period of time, the offset is rolled over to the fuel trim low value.

Oxygen Sensor - voltage reading from the O2 sensor in the turbo outlet pipe.

Oxygen Sensor #2 - Voltage reading from the O2 sensor in or after the cat.

Speed - Vehicle speed. this value has a slow response time and will be "choppy" in your log.

Coolant Temp - Current coolant temperature.

Air Flow Hz - Air flow reading from the MAF sensor. this value is capped at 1600. There is a 2-byte mod available to extend the 1600 limit.

Air Temperature - Intake air temp at the MAF. This value does not reflect the turbo or IC's effect on the intake charge temperature.

Battery Level - Current voltage output from the battery.

Load Calculated - This is a calculated value used to determine the actual ECU load value for tuning. this is fairly accurate on a stock car but the calculation must be altered when injectors are changed. This value has shown to be slightly higher than the 2-byte load value.

Wideband A/F Ratio - this is the A:F reading from an installed wideband O2 sensor. this can not be logged if you have not installed an aftermarket 5v O2 sensor.

Barometer - Barometric pressure reading (from the MAF?)

ECULoad - this is a measure of the Load % the ECU is receiving. This value is limited to 200 and therefore not useful on a modded car. the 2-byte load value will give the same information and extend the 200% limit to the ~500 range.

Load MUT 2Byte Mod - This is a 2-byte response from ECU RAM that gives the actual load read by the ECU. This is very accurate for tuning.

RPM MUT 2Byte Mod - This is a 2-byte response from ECU RAM that gives the actual RPM read by the ECU. this gives more accurate RPM values and is useful for road dyno calculations.

Octane Level - This value is a reflection of sustained knock counts. when the ECU sees knock of 6 or more, this octane value decreases from 100. when this value decreases the ECU begins to interpolate with the low octane fuel and timing maps. The lower the octane value, the greater the interpolation between the high and low maps.

BigBallin

iTrader: (9)

in to learn

nothere

iTrader: (23)

short term trim is idle
mid term trim is cruise
long term trim changes glacially so you will normally see zero.

the .99 version of evoscan reverses the labels of idle and cruise.

the mitsulogger records in a scale of 12 to zero, twelve being pegged at the extreme,(negative or positive).
logworks scales from 50 to zero, fifty being pegged, (negative or positive).
in either case one strives for the elusive and impossible zero.
evoscan uses still another scale (which eludes me at the moment)

the trims are affected by cold start enrichments and all other "special cases" doctoring of regular running by the ecu. this will impact your log readings and skew the results until the car is in normal mode.
*see the ecuflash forum for more.

Jim in Tucson

iTrader: (3)

Thanks to all contributors.

supeazn

iTrader: (3)

subcribes....

TouringBubble

iTrader: (2)

"Battery Level - Current voltage output from the battery. Is this more accurately the alternator output?"

I think this depends on how you look at it ... Nothing is really powered directly from the alternator, but the alternator is technically powering the battery. The reading more than likely is a reflection of the alternator output voltage thought the reading is somewhat "filtered" through the battery.

For example, try to log this value with the switch on but the engine off. You should get a voltage reading from the battery itself since the alternator is producing 0 voltage when the car isn't running.

80210

iTrader: (23)

knock sum- counts of knock detected, 6 or greater and the ECU will switch to the low octane map

TouringBubble

iTrader: (2)

Not necessarily (as mentioned above). At 6 counts the Octane value decreases ... when the octane value decreases the ECU begins to slightly interpolate with the low octane map.

80210

iTrader: (23)

Oh. I thought it defaulted to the low octane map.

Mellon Racing

iTrader: (38)

great idea Jim, this will be very helpful for others.

Sap12687

iTrader: (11)

Excellent idea. Hopefully we can get more in depth in these definitions and tie in numerical "boundaries" to help beginners like myself get a feel for the extremes.

asdfasdf128

iTrader: (60)

subscribed