Notices
ECU Flash

EVOscan 2.0 maptracer issues

Old Nov 27, 2007 | 11:17 AM
  #1  
smartbomb's Avatar
Thread Starter
Newbie
 
Joined: Apr 2006
Posts: 50
Likes: 0
From: Cypress
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.

Last edited by smartbomb; Nov 27, 2007 at 11:48 AM.
Reply
Old Nov 28, 2007 | 08:45 AM
  #2  
20psiMR's Avatar
Evolved Member
iTrader: (6)
 
Joined: May 2006
Posts: 731
Likes: 0
From: From Vegas to Reno
Same problem. Mine opens up, shows my maps, but doesnt display any data on the maptracer top box when I select anything on the left. The sample logs worked fine for me.
Reply
Old Nov 28, 2007 | 02:03 PM
  #3  
smartbomb's Avatar
Thread Starter
Newbie
 
Joined: Apr 2006
Posts: 50
Likes: 0
From: Cypress
Originally Posted by 20psiMR
Same problem. Mine opens up, shows my maps, but doesnt display any data on the maptracer top box when I select anything on the left. The sample logs worked fine for me.
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.
Reply
Old Nov 28, 2007 | 02:26 PM
  #4  
RazorLab's Avatar
EvoM Guru
20 Year Member
Liked
Loved
Community Favorite
iTrader: (8)
 
Joined: Aug 2003
Posts: 14,094
Likes: 1,092
From: Mid-Hudson, NY
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.
Reply
Old Nov 28, 2007 | 02:30 PM
  #5  
smartbomb's Avatar
Thread Starter
Newbie
 
Joined: Apr 2006
Posts: 50
Likes: 0
From: Cypress
Originally Posted by razorlab
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.
Hummm, that is exactly what I did. I have the same rom as you as well. I sent Hamish copies of my rom and my log to see if there is anything weird about them.

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.
Reply
Old Nov 28, 2007 | 04:24 PM
  #6  
broddey's Avatar
Evolving Member
iTrader: (5)
 
Joined: Nov 2005
Posts: 498
Likes: 0
From: Tampa, FL
Originally Posted by razorlab
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.
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?
Reply
Old Nov 28, 2007 | 04:44 PM
  #7  
RazorLab's Avatar
EvoM Guru
20 Year Member
Liked
Loved
Community Favorite
iTrader: (8)
 
Joined: Aug 2003
Posts: 14,094
Likes: 1,092
From: Mid-Hudson, NY
Originally Posted by broddey
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?
Ok I was doing a writeup with screenshots to post here. Unfortunatly, what worked on my laptop did not work on my desktop machine. So something is screwy here. Maybe Hamish can chime in?
Reply
Old Nov 28, 2007 | 07:04 PM
  #8  
fixem2's Avatar
Evolved Member
iTrader: (30)
 
Joined: Dec 2003
Posts: 929
Likes: 0
From: USA
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.
Reply
Old Nov 28, 2007 | 07:34 PM
  #9  
SWOLN's Avatar
Evolved Member
20 Year Member
Photogenic
Liked
Loved
iTrader: (6)
 
Joined: Sep 2005
Posts: 1,791
Likes: 13
From: In the Florida Swamps
Originally Posted by smartbomb
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.
+1 same problem here.
Reply
Old Nov 28, 2007 | 07:38 PM
  #10  
smartbomb's Avatar
Thread Starter
Newbie
 
Joined: Apr 2006
Posts: 50
Likes: 0
From: Cypress
Good to see that I am not alone! Its a great feature, I hope Hamish can figure out what our problem is soon.
Reply
Old Nov 28, 2007 | 11:07 PM
  #11  
Evo_Jay's Avatar
Evolved Member
20 Year Member
Photogenic
Photoriffic
Shutterbug
iTrader: (17)
 
Joined: Jun 2005
Posts: 3,419
Likes: 14
From: Chico, CA (NOR-CAL)
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.
Reply
Old Nov 29, 2007 | 08:09 AM
  #12  
smartbomb's Avatar
Thread Starter
Newbie
 
Joined: Apr 2006
Posts: 50
Likes: 0
From: Cypress
Originally Posted by Evo_Kid
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.
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.
Reply
Old Nov 29, 2007 | 10:40 PM
  #13  
smartbomb's Avatar
Thread Starter
Newbie
 
Joined: Apr 2006
Posts: 50
Likes: 0
From: Cypress
Originally Posted by Evo_Kid
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 tried this and the program went tilt and now doesnt work at all.
Reply
Old Nov 29, 2007 | 11:05 PM
  #14  
Evo_Jay's Avatar
Evolved Member
20 Year Member
Photogenic
Photoriffic
Shutterbug
iTrader: (17)
 
Joined: Jun 2005
Posts: 3,419
Likes: 14
From: Chico, CA (NOR-CAL)
Originally Posted by smartbomb
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.
Huh??

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.
Reply
Old Nov 29, 2007 | 11:07 PM
  #15  
Evo_Jay's Avatar
Evolved Member
20 Year Member
Photogenic
Photoriffic
Shutterbug
iTrader: (17)
 
Joined: Jun 2005
Posts: 3,419
Likes: 14
From: Chico, CA (NOR-CAL)
Originally Posted by smartbomb
I tried this and the program went tilt and now doesnt work at all.
Umm... You must have deleted something more then what i said.

Anyways, ill forward hamish this thread.
Reply

Thread Tools
Search this Thread

All times are GMT -7. The time now is 08:57 AM.