Im kinda excited. lol 2 years, and 4 programs l8r, finally get it to work for me. Tried w/ 2.1, 2.3, and 2.5, and could not get it up and running... Since my laptop **** the bed on me, and lost all my ish, I DL 2.6, gave it a shot... and bingo! Pretty cool how it shows all rpm point that got logged, when you put the cursur on any cell...

So for those that have had an issue getting the MapTracer to work, give 2.6 a shot. Hopefully it'll work for every1!

 

Since I don't use EvoScan, is this a realtime map tracer, or after the fact when viewing logs?

Just curious, as in the LiveMap app, there is a realtime map trace, which is really nice. It is also color coded to show cells with knock and amount of knock.

 

After the fact.

 

2.6 still doesn't work for me.. i think the fact that i have rearranged the data order in the program has something to do with it.. like im assuming most people compile all the things they are logging together. i think that may be the problem... did you rearrange anything and have it work with the logs which have been rearranged?

 

its not real time... I have edited the list. tps/rpm/wgdc/load/boost/boost error/afr, etc.

did you guys save your rom as ".hex"? I know it shows that it will save as either, (.bin/.hex) but I saved as "rom name.hex"

Then I dragged/dropped the current rom into desktop (the desktop option, on the left of the screen, not just dropping it out of the ecuflash screen, onto the desktop. (not sure if it matters, just what I did)...
Open up evoscan, pull a log, (r) click on the bottom map, browse to desktop, and open rom... Just as u normally would.

I was quite surprised that it worked, as Ive done the same thing on every program... I also noticed, you do NOT need to load your .xml any longer, just the "current" rom...

 

I have been using EvoScan map tracer since it came out. It has always worked for me.

I rearrange the data items order, and maptracer still works. I edit the list using the "Edit data item list" under "Logging" though.

 

the samples work but not my logs.. i dont know why...

 

A couple things.

-Did you right click on the lower box and select your ROM?

-Next, when you edited your list of data items did you use the "edit data item list" under "loggin" or did you do it by editing the actually "data.xml" in the "DataSettings" folder?

 

I have made a bunch of posts referencing how to get it to work (with big or standard maps). I've been meaning to update the wiki, but haven't got to it yet. I'll make a big red note for myself

 

Ok, its in the wiki: http://evoecu.logic.net/wiki/EvoScan#EvoScan_Map_Tracer

Feel free to make it more detailed.

 

Nice. Great job!

 

So you still need to modify the XML to see the alt maps tables?

 

I'm not sure why maptracer is needed. I have 0 problems locating exactly the cell I need using 1byte load and RPM. Maptracer might speed up the process just a tad I guess and eliminate the need to look at an excel sheet, but I've never needed it.

 

Yeah, I usually prefer to look at 1000 item long lists of items and not really be able to visualize what I'm looking at in a different and more effective way. This is why I threw out my graphing calculator and am considering writing a CLI Evoscan....

 

Sarcasm noted. I gave up on it like 2 years ago and learned to do it "the hard way" effectively and never had a regret.