So I just ignore the load and rpm values on the scale (for ex. 260 on the tracer will be 280 or whatever my map is scaled to), right?

OT, is %load just the # the ecu uses for IPW?

 

I don't know if you could ignore the values pictured in the screenshot.

When it parses the CSV file it's looking in each line for the rpm and ecu calculated load and just highlighting the cross-referenced cell. So the 240 column is only going to get highlighted if your load is 240 at 'x' RPM.

 

seriously.. i hope mj gets to support it!

 

I'll do my best, not sure if I'll get access to the source for bug fixes and whatnot, but I understand the reasoning.

 

The reasoning behind not releasing the source to the community is because it would not be a good base for development to continue from. The code is not optimized or put together in a fashion that would facilitate multiple developers in a project type format.

This should be considered an interim application since the idea (map tracing) is already a planned feature for multiple apps coming out.

 

Anyone else having a problem downloading it from Jack's site?

I forgot my password, so I did a reset. No problem. I click on 'Downloads', go into the correct subcategory, and see the MapTracer program. But then when I try to click on it, it asks me to log in again, but this time the same password doesn't work.

 

Scratch that.. I got it to work (still not sure what was wrong before though).

This is a cool little program! I'm very impressed with it. It's especially cool to click a sample in the log below, then step through pressing the up/down arrow keys. You can watch the actual timing versus the map value. It's interesting how the actual timing seems to lag a few steps behind the desired cell values.

 

I'm just glad some one besides myself can get some use out of it.

 

Now that I have a chance,

You are the author of the guages and widgets, right? If so what are the chances of being able to incorporate a Cental Aural Warning system within the gauge template? That is, while running EvoScan having the capability of turning my laptop volume control to max and using warning horns to signify knock conditions over a count of - say 5 or having an audible warning to indicate WB readings leaner than 12:1

 

Evo4Mad is the person who is developing EvoScan.

 

leakness, I logged a few pulls on the way to work and ran them through the MapTrace, good stuff man, works like a charm, it was a real eye opener to see what cells were being hit.

thanks for sharing it with us.

 

Some get confused because of our earlier contributions to Evoscan, your name still shows up in the Definition file for DataLogLab that you helped me create when I started releasing the Log Analyzer for Evoscan.

 

Ah yes, that I did start.

 

got to play with this today and its great . Whoever takes over this (if someone does) needs to add another thread/extend the functionality of the map control (if its custom). The way its written now it appears that when its tracing quickly it can highlight the block that it is in but not keep the actual value of the block on screen (at least thats what it did for me).

 

Works pretty good. I just put my maps in to the 260 cell since my runs normally dont go into the 280 -300 columns. It would be nice if there was a IX version or a version for those that have rescaled load (adjustable).