EvoScan Map Tracer - Alt-Maps (and standard maps)
Thread Starter
EvoM Community Team
iTrader: (15)
Joined: Sep 2006
Posts: 3,143
Likes: 7
From: Aurora, IL
By alt-maps I'm referring to the alternate maps in my tephra-mod section.
I got it to work! Its not very smooth, but here is what I did:
1) Copied my load1byte column to to a column with "LoadCalc" in the header, 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.
2) Modified an XML to have no includes, just all of the scalings from the base file and the fuel and timing tables. EG:
(Note: Don't keep these in your ecuflash XML directory or it may have strange effects when trying to open your ROMs!)
3) R-clicked and loaded my hex and XML files
As a secondary tip for those out of the know, you can right click the actual map that is displayed below to then switch between which map you want displayed in the window.
----EDIT: If you move the xml you created to the evoscan\ROMs directory it will automatically be detected. Getting better....
I got it to work! Its not very smooth, but here is what I did:
1) Copied my load1byte column to to a column with "LoadCalc" in the header, 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.
2) Modified an XML to have no includes, just all of the scalings from the base file and the fuel and timing tables. EG:
Code:
<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) R-clicked and loaded my hex and XML files
As a secondary tip for those out of the know, you can right click the actual map that is displayed below to then switch between which map you want displayed in the window.
----EDIT: If you move the xml you created to the evoscan\ROMs directory it will automatically be detected. Getting better....
Last edited by fostytou; May 19, 2009 at 04:18 PM.
Thread Starter
EvoM Community Team
iTrader: (15)
Joined: Sep 2006
Posts: 3,143
Likes: 7
From: Aurora, IL
Ok, it looks like you can also just select the evoscan\ROMs file for your non-tephra ROM if you just want a quick fix and don't care what the lower window displays.
I tried to just make a copy of it and rename the file and ROMID header, but it didn't automatically detect it like it did for the one I created.
Either way, it seems like loadcalc is the only real barrier to entry here. Somebody get Hamish on it.
Other side note, I'm running v2.6 b11
I tried to just make a copy of it and rename the file and ROMID header, but it didn't automatically detect it like it did for the one I created.
Either way, it seems like loadcalc is the only real barrier to entry here. Somebody get Hamish on it.
Other side note, I'm running v2.6 b11
Thread Starter
EvoM Community Team
iTrader: (15)
Joined: Sep 2006
Posts: 3,143
Likes: 7
From: Aurora, IL
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 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.
1) rename the logged item for load1byte to "loadcalc" (less data, but could be confusing in the future)
2) Replace your loadcalc 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.
Code:
<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.

Dont forget to update the InjectorScaling on the Main Form, with your injector scaling value used for your rom.

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" />
Thread Starter
EvoM Community Team
iTrader: (15)
Joined: Sep 2006
Posts: 3,143
Likes: 7
From: Aurora, IL
Well, it seems to work for whatever items you log, but only under the conditions that you log ECULoad and rpm. This also assumes that you want the item displayed on a load vs RPM graph (that of your rom or any other rom you load).
I didn't know if it could, for instance, trace where you were on the boost maps because I had never seen the functionality before. Now I see that its more of a "plotter" than a "tracer".
I didn't know if it could, for instance, trace where you were on the boost maps because I had never seen the functionality before. Now I see that its more of a "plotter" than a "tracer".
Yeah, essentially all the tracker does is plot on the grid all of the cells used in a specific pull. I find it usefull to only have enough information in the log for the pull. Any extra information makes the tracked cells jumbled.
Typically I wil turn on EvoScan just before I start a 3rd gear pull (I start to log just after I go into 3rd gear at like 2000 rpm). As soon as I let off of WOT I shut EvoScan down. This way I am logging only the pull to make it easier to track the pull in map tracker.
Another way is to go into excel and delete any un-needed logged data. Then open file in EvoScan and plot your pull with map tracker.
Typically I wil turn on EvoScan just before I start a 3rd gear pull (I start to log just after I go into 3rd gear at like 2000 rpm). As soon as I let off of WOT I shut EvoScan down. This way I am logging only the pull to make it easier to track the pull in map tracker.
Another way is to go into excel and delete any un-needed logged data. Then open file in EvoScan and plot your pull with map tracker.
Evolving Member
Joined: Feb 2008
Posts: 214
Likes: 1
From: South Africa
By alt-maps I'm referring to the alternate maps in my tephra-mod section.
I got it to work! Its not very smooth, but here is what I did:
1) Copied my load1byte column to to a column with "LoadCalc" in the header, 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.
2) Modified an XML to have no includes, just all of the scalings from the base file and the fuel and timing tables. EG:
(Note: Don't keep these in your ecuflash XML directory or it may have strange effects when trying to open your ROMs!)
3) R-clicked and loaded my hex and XML files
As a secondary tip for those out of the know, you can right click the actual map that is displayed below to then switch between which map you want displayed in the window.
----EDIT: If you move the xml you created to the evoscan\ROMs directory it will automatically be detected. Getting better....
I got it to work! Its not very smooth, but here is what I did:
1) Copied my load1byte column to to a column with "LoadCalc" in the header, 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.
2) Modified an XML to have no includes, just all of the scalings from the base file and the fuel and timing tables. EG:
Code:
<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) R-clicked and loaded my hex and XML files
As a secondary tip for those out of the know, you can right click the actual map that is displayed below to then switch between which map you want displayed in the window.
----EDIT: If you move the xml you created to the evoscan\ROMs directory it will automatically be detected. Getting better....
I got this to work first time.
I am logging 2byte load with the V7t5 96530706 ROM, and using the above instructions, my map tracer is working perfectly again.
Here is how I got it working....
Step 1
First step is to copy the std 96530006 xml file from the ECUFlash\Rommetadata\mitsubishi\evo folder and paste in into your EvoScan2.5\ROM folder.
Then rename this file you just copied, to 96530706.xml
Step 2
Then using notepad, I opened the 96530706.xml file from the ECUFlash\Rommetadata\mitsubishi\evo folder, copied the Alt map entries for fuel and ignition maps out of that file, then pasted them into the new 96530706.xml file (which should be sitting in EvoScan2.5\ROM folder, if you followed Step1 above).
I also renamed the 96530006 entries in the header part of the file to 96530706, (not sure if it was needed) and then saved it.
Opened EvoScan, started maptracer, loaded my log file (I still got the error message), right click and loaded my last saved hex/bin file that the log was based on.
And then loaded the 96530706.xml file from the EvoScan2.5\ROM folder (which you just created from the steps above)
Map tracer worked perfectly. (Next time you go into map tracer you shouldn't get the error message any more.)
Thx Fostytou for the original idea/instruction.
Any idea why after working for a week EVOScan will not let me select the XML file I want to use for MapTracer? It work for a while, now it seems to be pulling it's own XML file and not using the one I made up so in turn it's giving me the same error again "Object reference blah blah blah". Anyone else have trouble with EVOScan not allowing you to even choose the XML?
~Zach
~Zach
Thread Starter
EvoM Community Team
iTrader: (15)
Joined: Sep 2006
Posts: 3,143
Likes: 7
From: Aurora, IL
Any idea why after working for a week EVOScan will not let me select the XML file I want to use for MapTracer? It work for a while, now it seems to be pulling it's own XML file and not using the one I made up so in turn it's giving me the same error again "Object reference blah blah blah". Anyone else have trouble with EVOScan not allowing you to even choose the XML?
~Zach
~Zach
If you have an xml in the evoscan xml directory that matches your ROMID it should automatically pull it up. Did you possibly rename one that you didn't want to your v6/v7 romID? (By rename I mean in the xml). You can move all of them out of that directory (to a folder on your desktop or something) and just put the one you want for sure to double check if that is the problem.... otherwise I think there is some way to force it to allow you to select.
Maybe it is a bug....
Thread
Thread Starter
Forum
Replies
Last Post
