9!'clipseDOHC

iTrader: (7)

Let me preface this by saying that I am new to EvoScan. I have been using ECMlink V3 (aka dsmlink) for about a year now though so I understand the basics of tuning. With v3 to track the cell being used I just scroll through the log (graph) and it highlights the cells being used by the ECU on any given table and I can easily make any needed changes. I have yet to figure out how to do this with EvoScan. I just want to see what cells are being used in the timing table at any given point in the log. Any help is greatly appreciated!

07EvoIX

click on the map tracer button at the top middle of evoscan. when it appears, from the left select/tick timing.

the table to the right top is the map trace table that will show what is being hit. the table under is your actual map, right click it to select your desired map to correlate with.

cheers

9!'clipseDOHC

iTrader: (7)

I can open it and load a log but after that i can't figure out what to do. Here is a screen shot, my tables look retarded and I still have no clue which cell is being used. Am I doing something wrong?

GrumpyIX

Make sure that all your file paths are correct, try loading different WOT runs. Looks like EvoScan is getting the incorrect path to the file.

GrumpyIX

Click on "external WBO2" on the left hand side, presuming you have one. Did you load a run for the graph below the AFR map?

9!'clipseDOHC

iTrader: (7)

Those two tables look like that even before I load the log. I have tired several different logs and they all look the same. The lower boxes (Horsepower/torque, AFR, and Timing) seem to be loading properly. However all I want is to be able to scroll through the log and see which timing cells were being used at any given point in the log.

What do you mean to make sure my file paths are correct?

Yes, I am logging an external WB02. Regardless of what I select on the left hand side of the screen nothing changes in the middle.

mt057

iTrader: (6)

I have never liked to use map tracer as much. It can be useful but takes extra time.

I simply look at the log and and look for the given load cell on the map based on load/rpm.

But as others have said you have to make sure that the log that you want to check out has been saved into an area that maptracer can access and has been loaded in to maptracer. Not simply brought up with evoscan.

I decided to try it out myself and I got it to work once today and now it is giving me problems as well...

mt057

iTrader: (6)

OK so to get it to work I had to load the log file that I wanted in the Map tracer program by right clicking on the load % located between the two maps.

Then I had to right click the load% again and load my rom on to it and bam it showed up. Before that it would not show me anything in the top map area only the bottom showing my current rom.

Boosted Tuning

iTrader: (12)

+1

9!'clipseDOHC

iTrader: (7)

Thank you so much for your response! One small step forward! I right clicked the middle load% and loaded my ROM and it now displays my proper tables BUT the RPM and LOAD columns are still all jacked up. It is tracking the very first cell (which it shows as 0 RPM and 0 load) but that is it. How do I fix that?

Boosted Tuning

iTrader: (12)

You dont have your ROM correctly loaded into the maptracer. Or you have another issue.

But like mt057 said, its kinda a hassle to use the map tracer and is much easier to just look at the load and RPM in the log and then edit that cell.

9!'clipseDOHC

iTrader: (7)

I have tried looking at the RPM and Load in the log and seeing what cell it should be using for the timin but it doesn't seem to be lining up right. If there is something not loaded correctly I don't know what it is. I need some ideas. Thanks for the help so far guys!

Boosted Tuning

iTrader: (12)

You may be experiencing timing reduction because of high intake temps, leading the logs not to have the same timing value as the map.

Also, what load are you logging? What ROM are you using?

9!'clipseDOHC

iTrader: (7)

My ROM is 96940011 and I am logging LoadMUT2Byte. My MAFAirTempScaled is between 100-110 dropping durring the pull.

Also I just double checked and I am running EvoScan version 2.9.0021 which is the most recent one.

9!'clipseDOHC

iTrader: (7)

Bump! Anyone have any ideas on how I can fix this?