EVOscan 2.0 maptracer issues
EVOscan 2.0 maptracer issues
I can get my sample logs to work but not any logs from my car. I loaded my .csv and my rom .xml data as per the instructions and my maps load correctly but no map tracing.
I noticed that the .xml file for my version of rom in EVOscan 2.0 has many patches, way more than what my rom has, could that be a problem? I tried loading the rom data from ecu flash instead and that caused EVOscan to wig out.
Can anyone help me? I think at least one other person is having this issue as well. This is a great time saving feature if it can be made to work.
I noticed that the .xml file for my version of rom in EVOscan 2.0 has many patches, way more than what my rom has, could that be a problem? I tried loading the rom data from ecu flash instead and that caused EVOscan to wig out.
Can anyone help me? I think at least one other person is having this issue as well. This is a great time saving feature if it can be made to work.
Last edited by smartbomb; Nov 27, 2007 at 11:48 AM.
I E-Mailed Hamish and i will let everyone know what he says when he replys. I was hoping that more people here would have experiance with this but its new so I guess not.
I've had it happen as well.
Here is how I got it to work well:
1. Select your log you want to view
2. Select the XML he supplies in the ROMS folder of evoscan
2. Select your Rom for the log in #1.
Works everytime for me on #15 Evo 9 ROM.
Here is how I got it to work well:
1. Select your log you want to view
2. Select the XML he supplies in the ROMS folder of evoscan
2. Select your Rom for the log in #1.
Works everytime for me on #15 Evo 9 ROM.
I did notice that his .xml that he supplies has a lot of patches in it. I wonder if that might have something to do with it?
You have to excuse my ignorance, computer stuff is pretty painful for me.
So we select the log we want and open the file in the maptracer viewer, but then what do we do with the xml he supplies in the roms?
Could you be a little more specific? Us noobs are still trying to work out the kinks in 2 byte load, let alone getting the tracer to work.
So we select the log we want and open the file in the maptracer viewer, but then what do we do with the xml he supplies in the roms?
So we select the log we want and open the file in the maptracer viewer, but then what do we do with the xml he supplies in the roms?
Trending Topics
I just checked the ROMS folder and the 96940011 xml is not in there. I added mine and still no go with any logs other than the sample. I sent my log, rom and xml to Hamish over a week ago with no response.
I can get my sample logs to work but not any logs from my car. I loaded my .csv and my rom .xml data as per the instructions and my maps load correctly but no map tracing.
I noticed that the .xml file for my version of rom in EVOscan 2.0 has many patches, way more than what my rom has, could that be a problem? I tried loading the rom data from ecu flash instead and that caused EVOscan to wig out.
Can anyone help me? I think at least one other person is having this issue as well. This is a great time saving feature if it can be made to work.
I noticed that the .xml file for my version of rom in EVOscan 2.0 has many patches, way more than what my rom has, could that be a problem? I tried loading the rom data from ecu flash instead and that caused EVOscan to wig out.
Can anyone help me? I think at least one other person is having this issue as well. This is a great time saving feature if it can be made to work.
The map tracer always worked for me, but because i like everything to be organized and such, I did the following and it still works.
I deleted all the supplied definition .xml files that came with EVOscan in the "ROMS" folder. I then copied all the definitions from my ECUflash evo definitions folder.
Then I deleted all the supplied ROMs in the EvoScan "ROMS" folder, because you should always load the ROM your working on.
Also, my take on the maptracer feature is that its a good start, its just gonna take some time and work to make it great.
I deleted all the supplied definition .xml files that came with EVOscan in the "ROMS" folder. I then copied all the definitions from my ECUflash evo definitions folder.
Then I deleted all the supplied ROMs in the EvoScan "ROMS" folder, because you should always load the ROM your working on.
Also, my take on the maptracer feature is that its a good start, its just gonna take some time and work to make it great.
The map tracer always worked for me, but because i like everything to be organized and such, I did the following and it still works.
I deleted all the supplied definition .xml files that came with EVOscan in the "ROMS" folder. I then copied all the definitions from my ECUflash evo definitions folder.
Then I deleted all the supplied ROMs in the EvoScan "ROMS" folder, because you should always load the ROM your working on.
Also, my take on the maptracer feature is that its a good start, its just gonna take some time and work to make it great.
I deleted all the supplied definition .xml files that came with EVOscan in the "ROMS" folder. I then copied all the definitions from my ECUflash evo definitions folder.
Then I deleted all the supplied ROMs in the EvoScan "ROMS" folder, because you should always load the ROM your working on.
Also, my take on the maptracer feature is that its a good start, its just gonna take some time and work to make it great.
One thing I think it needs is the abilty to average multiple logs but other than that, it seems pretty good.
The map tracer always worked for me, but because i like everything to be organized and such, I did the following and it still works.
I deleted all the supplied definition .xml files that came with EVOscan in the "ROMS" folder. I then copied all the definitions from my ECUflash evo definitions folder.
Then I deleted all the supplied ROMs in the EvoScan "ROMS" folder, because you should always load the ROM your working on.
Also, my take on the maptracer feature is that its a good start, its just gonna take some time and work to make it great.
I deleted all the supplied definition .xml files that came with EVOscan in the "ROMS" folder. I then copied all the definitions from my ECUflash evo definitions folder.
Then I deleted all the supplied ROMs in the EvoScan "ROMS" folder, because you should always load the ROM your working on.
Also, my take on the maptracer feature is that its a good start, its just gonna take some time and work to make it great.
Whats your take on it not being great? I think it's a pretty awsome thing because it saves all the time messing around with macros and cutting and pasting into logworks.
One thing I think it needs is the abilty to average multiple logs but other than that, it seems pretty good.
One thing I think it needs is the abilty to average multiple logs but other than that, it seems pretty good.
I just view logs in the EVOscan regular graphing. No macros, no cutting and no logworks.
The "review/analyse saved log in a graph" feature.
Also, " review log- rpm vs. load/fuel/timing knock" feature gave me wrong info and had a bug or two in it (maptracer that is).
I also think its pretty awesome, but I still believe it needs to have the bugs worked out.
Last edited by Evo_Jay; Nov 30, 2007 at 12:29 PM.









