Thoe99

iTrader: (25)

I've been opening my csv files directly in Excel in the past to get my numbers for tuning. Now that I'm using Maptracer, the numbers aren't exactly matching up with the csv files. Is there something I'm not aware of? I'm looking at 5500rpm showing 11.6 AFR, but the excel sheet shows 11.3. When I switch it to read averages, it shows 11.5 AFR at 5500 rpms. I don't even think the averages in the excel sheet around that rpm is 11.5 (there are a lot of 11.3's and 11.4's around there). And why is it using the 240 load column when the csv shows 220's? How are you guys interpreting this Maptracing feature?

merkzu

iTrader: (4)

I noticed this from razorlabs logs.

It put 11.6 because in your 5312rpm row you have 11.58, which rounded is 11.6. 5312 is greater than 5000, so it put 11.6 in the 5500 rpm row

It used the 240 load cell because 227 is greater than 220



I think it should use the closest cells.. which would put 11.6 in the 5500RPM/220load cell. How does LogWorks do it?

RazorLab

iTrader: (8)

I agree with you merkzu. I think if it also shows 230 load it should put numbers in both the 220 and 240 load cells.

The more I have been messing with the new maptracer feature the more I realize I won't be using it for day to day tuning yet.

mexevo

it takes the average of all the values that are on that particular cell, if you get the mouse over the cell it shous all the values that in one log fall in the same cell and that can be from one single value to many values, if you chose counts where you have maximums it shous the number of values that fall in each cell instead of the value or average..

mexevo

by the way why in my maptracer i can only see loads up to 100

Thoe99

iTrader: (25)

Ok, so the 5500 cell refers to everything from 5001-5500rpm then? When you guys tune, are you using maximum or avg values for AFR?

Mexevo, you have to load up your data and hex file for it to read more than 100 load. Right click the bottom table and it will give you the option to load up those files.

chmodlf

iTrader: (19)

Haven't had a chance to test v2.0 yet.

Has anyone tried the Evoscan maptracer back to back with Logworks? Doing so might illuminate the problem.

nothere

iTrader: (23)

[QUOTE

Mexevo, you have to load up your data and hex file for it to read more than 100 load. Right click the bottom table and it will give you the option to load up those files.[/QUOTE]

sounds bad, but what and how do I get those files?

kreionic

iTrader: (14)

^^^Go into ecuflash and see what your rom ID is then put that rom id xml in the roms folder in evoscan. Do the same with your tune (.hex, .bin) Put your current tune in the evoscan roms folder

Thoe99

iTrader: (25)

sounds bad, but what and how do I get those files?[/QUOTE]

1. When you open up Maptracer, right click the bottom grayed-out area and choose 'load hex and xml files.'
2. It first asks for an xml file, so browse to c:\programs files\evoscan\evoscan v2.0 map tracer edition\roms\, then choose the appropriate xml file for your car's year.
3. Then it asks for a hex file, so browse to your current rom file. Make sure you always do this when you update rom files, otherwise, you'll be looking at old fuel and timing maps.

chrisw

iTrader: (2)

I thought I downloaded v2.0, but it isn't the map tracer edition. Where can I order this version?

I have already looked on http://www.limitless.co.nz/evoscan/

as a registered owner what do I need to do to upgrade?

Jim in Tucson

iTrader: (3)

Clic for EvoScan with Map Tracer.

chrisw

iTrader: (2)

thanks!

coolguycooz

ok so let me get this figured out, when maximum is selected it takes all the cells between 5001-5500 rpms, picks the highest AFR rate and sets it in the cell? thats what it seems like its doing? Only 11.5 would not be the average of the AFR ratios in your log between 5001-5500. Unless it *ALWAYS* rounds up to the nearest tenth. meaning an AFR rate of 11.4001 would be looked at as 11.5 by map tracer in evoscan.

Jack_of_Trades

iTrader: (17)

Correct.


Hmm, I'll hae to see if thats how it always rounds up in my logs. If so, this is something that should be brought up with Hamish. If he has it rounding to the nearest tenth, maybe he can have a "less than" "greater than" setting to the second decimal instead of the first??