I've officially released version 2.0 of the Log Analyzer for Evoscan Logs..

THIS VERSION CALCULATES LOAD FOR YOU! VERY USEFUL AND FAST TOOL!

See the thread on Aktivematrix, but the new app converts Evoscan log files to work with data log lab (alters the date/time/seconds fields to use seconds from start of log, this makes the file compatible with log analyzers) Additionally, it adds a new column called LOAD (the original Load column has been renamed MDP in the new data.xml and evoscan.txt files included in the package)

http://www.aktivematrix.com/forum/viewtopic.php?t=28

This software is being supplied with no support.. I just don't have the time to offer any serious support for this..

Enjoy, you now have a way to automatically calculate load without doing it in Excel..

Included is a new evoscan.txt (For Data Log Lab) and DATA.XML (for Evoscan) which fixes a bug in the speed calculation, also renames the old LOAD column to MDP (manifold diff pressure) to avoid having two load columns, Data Log Lab will load the last instance of it and shouldn't be a problem if you have an old data.xml file.. but you do need InjPulseWidth and AFRMAP columns... If they are old log files with those columns missing, it may not work right, if it doesn't, I'll release a new version that can tolerate that.

Also, Injector Scale, and 14v latency values are saved when you exit the program, so you don't have to set it every time you run the program, you can revert to defaults if you need to (Default is USDM Default of 513)

EDIT: I renamed the title of the thread, and some of the text to avoid confusion, this has nothing to do with Evoscan other than it uses Evoscan log files as input.

 

Thx a lot.

 

Just verified the program won't break on older log files, but it will get a final column of garbage data, but it won't show up in Data Log Lab..

 

will this work probably if i'm running 660cc injectors with SAFC ?? no injectors scaling on the ecu period.

 

Do i need data log lab?? if yes, where do i get it?

 

http://www.dataloglab.com/

I'm checking it out now...

 

No you don't need it but it is a nice tool to graph your logs. If you want you can do your own thing in Excel.

 

EDIT: What I meant about DLL is what "Data Log Type" do I use.

^Use the evoscan.txt included with the package DUH

 

Crap I'm stupid.. Look over my questions!

 

Yep leave the default values, but the MAF is obviously skewed by the S-AFC, but you know that already..

 

Its definitely not a requirement to use Data Log Lab.. but its a great visualization tool. There are other tools out there, and you can even do the same thing with Excel if your creative..

But I took the two huge steps out of the equation for you guys, which is formatting the logs in a manner that won't confuse third party analyzers, and calculating your load.. As everyone probably already figured out, can be a bit of a PITA on long logs in Excel..

I can pretty much now add any type of calculation if I wanted to.. I rewrote the code so its not dependent on the location of the columns, but it needs to have the header line to work right...

I think I'm going to add a "gear" column in the next version, since with RPM and Speed, I can easily calculate what gear its in in most cases.. It won't be perfect since free revving and shifting can confuse the calculation, but it should help you guys when you have logged several pulls in different gears in the same log.

This software is the first portion of the code for my Logger / dashboard / Map-Tracing tool, where this will happen in realtime and log to disk.. Still having trouble with the comm routines though so I may not have anything this weekend.

 

Awesome! I log pretty much everything.. some of my trips are 30min-3hrs so this will be very useful!

Keep up the good work

 

Damn Jack, you keep the status of "the man"

 

Just a quick sample of what "Load" looks like, this is from a part throttle run where MAF and Boost are high, it demonstrates that the load even at part throttle can be similar to WOT and how important part throttle tuning is.. However, the windows show the quantity of data gathered, and the Data Log Lab window shows the Load also using the new tool, the ECU+ is the same run matched up, showing the knock voltage and other values (MAF) not easily captured in Evoscan.. But as you can see, most of the useful information (Except AFR and unclipped MAF reading) is available from data in EVOScan (or any ECU Data logging)

 

careful there Jack, you wouldn't want to post a log and then have someone reverse engineer your timing information and steel your maps, lol.