When I am logging with Evo Scan and review the logs, there are always differences between the logged items when I hover over them even though they are in the same location. To show what I mean I have attached to images, when I hover the mouse over each value, and move vertically to the next, the values are different.

Is there something wrong, or a new version that fixes this?

If there is no way on how to fix this can anyone direct me to a link or tell me how to convert my log files to logworks?

Thanks!

 

Anyone? This info would be much appreciated. I searched and could not find someone with a similar problem.

Thanks in Advance,

-George

 

I have seen this happen.

The lines and the scaling on the side will not be wrong, but sometimes what it says in the box is. Usually just taking the arrow off and putting it back on fixes it.

 

For me, the box is always wrong, I just want to make sure that what I am reading is correct and I am tuning the correct load columns.

I have seen people export the log files to a spreadsheet that is similar to the load tables, which makes it easier to visualize where you need to make the changes.

Is there any threads showing how to do this?

Thanks for the response Evo Kid.

-George

 

Bump, anyone else have any input?

 

I gave hamish the link to this thread last night. Dont know if he checked it out or not. If i see him online tonight, ill ask him again.

 

Thank you, It is much appreciated.

 

Also, I noticed this discrepancy is only with the wideband input, everything else seems to be spot on. Although I could be wrong.

 

So, I talked to hamish. He said it should be fixed by 2.1 or 2.2. He just did or is about to release 2.0 but 2.1 shouldnt be far behind.

 

Thanks for the response Evo Kid, Any idea when the new version should be released?

 

2.0 or 2.1/.2??

 

Either one, which one will include Map tracing, Also I would like to get in on the BETA testing if its not to late, I do quite a bit of logging, daily.

-George

 

Map tracer should be in 2.0. So far its flawless after he fixed some of the resolution. I have one little knit pick I guess you can say. He fixed the resolution to have all the rpm and load match up but when I open the timing tables I cant see my last 2 rows of timing, the task bar cuts it off. If I hide the task bar its fine and its fine on my desktop pc aswell. I know that wont be fixed for the 2.0 release

 

2.0 is about to be released, if it hasn't been release already.

2.0 will include map tracing.

Beta tests is done, I believe.

2.1 shouldn't be far behind.

 

Awesome, I am very excited for this release of EVOscan, where can I check for updates?

Thanks guys!

-George