Hey I got a problem with V0.8. My 0.7 worked fine in conjunction with mikelaak.com/convert.php Now my 0.8 doesn't want to work with it. Not even the LoggerReader Second Chance posted worked. I think it has something to do with how the Log was saved. Before it was all just numbers. Now, at the top of the saved logs, there is a list of what is being logged up top. Accel Enrich, timing, etc...the 0.7 didn't have it...anyway to get it back to normal? It's hard to read because it is all crammed together.

I'll save this for people with the same problem or anyone that knows how to change back. I don't have excel but I got Works Spreadsheet to open it up and looks good.

 

The website posted by laakness and even the logreader that I created used the old log format to format/view.

As far as my reader goes, I don't know if I'll post an update as it looks like Evo4Mad should have something to replace it shortly. Either that or the log viewer that MalibuJack posted seems like a pretty good replacement.

 

I can't get the data Log lab to work correctly. I still like your logger the best... any way you can update it to read the v.8 EVOScan logs?? Who knows how long its going to be until EVO4MAD is finished his project.

Thanks.

 

DLL is the best log analyzer out there.. unfortunately it won't work 100% right unless Evo4Mad can accomodate combining the time and second columns together (Its actually going to cause problems for any log reader app eventually)

I can't get the other program to work with 0.8 logs.. It just crashes..

The logger is fantastic, now just have to find a way to use the data.. Unfortunately though, most of the MAF data is useless for me since all of my MAF readings needed for tuning are well over 1600hz..

 

I tried the custom requests and they dont get stored in the logs at all. that makes it tough to trend data to try to determine what channels are what. loging the custom request data translated from hex would be very good

also an option to log the raw data before it is proccessed by the formulas could be good

otherwise it is working well. sample rates went from 80 to 130ish. and the new charting is more native, I agree with jack on the time stamps.

 

Have you tried something as simple as opening the CSV with Notepad and replacing "2006," with "2006."? Furthermore, if the "/" for the date is a problem, then also replace all "/" with "."

This would end up reformatting each line from:
1,7/7/2006,16:32,2.90625,,22.74509804,201.6176,875,100,[etc.]

to:
1,7.7.2006.16:32,2.90625,,22.74509804,201.6176,875 ,100,[etc.]

You could also simply open the CSV in Excel and delete the LogEntryDate,LogEntryTime,LogEntrySeconds columns and use the LogID as your 'time' value.

l8r)

 

On a separate note, Evoscan v0.8 seems to work fine as long as I do not try to access the LC-1 from it. I can run Logworks to record from the LC-1 simultaneously to using Evoscan.

l8r)

 

Neither quite works.. the LogID entry would result in a all calculations being incorrect.. and a find and replace type change would have to be between the time and seconds column, replacing the comma with a : for it to work right (and be useful)

I'm in the process of writing a little tool that I can drag and drop the file on, it converts it and launches DLL for me..

 

It's not supposed to work with the new version. I only wrote it as a bandaid fix until Evo4Mad came out with .8. The new version of EvoScan writes to a column based CSV file, which is one everyone wanted...including myself. The output my site gave with the .7 logs is now what .8 produces by default.

 

check out the dataloglab thread in this subforum.. I wrote a small app that combines and deltas the time so you get a seconds from start of logging value.. It works perfectly with DLL..

 

Is there any news pertaining to the 1603.95 limit?