EvoScan

From EvoEcu
Jump to: navigation, search


EvoScan is a program created by Evo4Mad (Hamish). The program connects to the ECU via an OpenPort 1.3U or OpenPort 2.0 USB Cable Logging Cable. EvoScan allows you to log ECU data and also has the ability to connect to and log from a Wide Band Air Fuel Meter.

Problems with the Map Tracer Feature

Logged Items

Unfortunately EvoScan bases this chart off of ECULoad (or LoadCalc, in some cases) and standard RPM. If you are using the 1 byte load mod or 2 byte RPM you can run into issues.

Incorrect XML Definitions

You can also run into issues if your XMLs are incorrectly defined in the Evoscan XML directory. It is often easiest to simply remove all unnecessary tables from the EvoScan definition files to ensure that you will not run into any snags. You can also add Alt-map tables (which are not included by default) and/or Big-Map tables for newer versions of the TephraMod.

How to: For problematic map tracers or BigMap tracing

EvoM user Fostytou details this method in a thread here and here and further down.

Essentially all you are going to do is make sure everything is properly defined for your rom, and as minimalistically as possible.

  • 1) Get loadCalc values in your log. The first time I did this I copied the load1byte column to to a column with "LoadCalc" in the header in the EvoScan XML (be sure to delete the old "LoadCalc" column.) (You can also just make a copy of the log and rename the load1byte or do as others have suggested and rename it in evoscan). This is silly because it allows you to then select which column you want to use for load. I assume if you log loadcalc or forced evoscan to populate it with 0 in each entry you would then be able to just select the correct load column.
    • More progress... Unfortunately you can't just have evoscan write a first and last entry of 0 with calc/priority 100. No matter what is selected in the drop down tracer is looking for loadcalc. You have 2 options:
    • 1) Rename the logged item for load1byte to "loadcalc" (less data, but could be confusing in the future)
    • 2) Replace your loadcalc and 1ByteLoad evoscan entry with these 2. Log the DEAD version. This should not really have an impact on performance, just create a very slightly larger log.
<DataListItem DataLog="N" Color="" Display="Load Calculated REAL" LogReference="LoadCalcXXX" RequestID="29" Eval="5*[InjectorScaling]*((0.256*x)-(-0.1026*[Battery]+1.8741))/(14.7*128/[AFRMAP])" Unit="Load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" Notes="This is just an extended calculation to forumulate the real Load value beyond that shown in ECULoad. A more accurate method is to reflash your ecu with a ROM mod that allows you to log 2Byte Load.&#xD; &#xD; Dont forget to update the InjectorScaling on the Main Form, with your injector scaling value used for your rom.&#xD; &#xD; 5*InjScaling*([InjPulseWidth]-(-0.1026*[Battery]+1.8741))/[AFRMAP]" Priority="1" Visible="False" />
<DataListItem DataLog="N" Color="" Display="Load Calculated DEAD" LogReference="LoadCalc" RequestID="CALC" Eval="[Load1B]" Unit="Load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" Notes="Fake Load to get map tracer to work." Priority="1" Visible="False" />


  • 2) Modify an XML to have no includes, just all of the scalings from the base file and the fuel and timing tables. EG:
<table name="High Octane Fuel Map - ALT" category="Fuel" address="49b4d" type="3D" swapxy="true" scaling="AFR">
<table name="Engine Load" address="6ec8" type="X Axis" elements="20" scaling="Load"/>
<table name="RPM" address="6ea0" type="Y Axis" elements="15" scaling="RPM"/>
</table>
<table name="High Octane Ignition Map 1 - ALT" category="Timing" address="49c8d" type="3D" swapxy="true" scaling="Timing">
<table name="Engine Load" address="6f2c" type="X Axis" elements="21" scaling="Load"/>
<table name="RPM" address="6efa" type="Y Axis" elements="20" scaling="RPM"/>
</table>
<table name="High Octane Fuel Map" category="Fuel" address="2dbd" type="3D" swapxy="true" scaling="AFR">
<table name="Engine Load" address="6ec8" type="X Axis" elements="20" scaling="Load"/>
<table name="RPM" address="6ea0" type="Y Axis" elements="15" scaling="RPM"/>
</table>
<table name="High Octane Ignition Map 1" category="Timing" address="33e9" type="3D" swapxy="true" scaling="Timing">
<table name="Engine Load" address="6f2c" type="X Axis" scaling="Load" elements="21"/>
<table name="RPM" address="6efa" type="Y Axis" scaling="RPM" elements="20"/>
</table>


  • 3) Open EvoScan MAP Tracer and pick your log file.
  • 4) Right-click on the bottom and click "Load HEX and XML files."
    • The first file you load is the ROM XML file you copied from ECUFlash. This would be the 88590715.xml file that you just made, and if it works properly it should load automatically from now on when you select your ROM.
    • The second file is your actual .hex/.bin ECUFlash flash file (your current tune or the one you were using when the log file was created). If you don't have one, you will have to use ECUFlash to connect to your ECU and download whatever tune you currently have.
  • 5) Now everything should be loaded and you can click on the parameters on the left to view them.