Ok, here is my original log by Evoscan :

click

Here the columns separate by , and the numbers in format like that : 1.34

I create one by me :

here

non of working

When I would like to use the Virtual Dyno 5.71 than I have to replace in openoffice the . to , ( 1.23 to 1,23 ) and than copy the RPM and logentryseconds than it is working. I tried everything with the Virtual Dyno standalone but always got some error message I'm bit confused with that because the program looks like great and faster to analyz my log as any other . Shoud be work without any trick just open my logged Evoscan .csv ?

 

If you look at your file in notepad, you will see double quotes (") surrounding your time and rpm numbers.

I don't think these are necessary. Taking them out seems to fix the issue.

I uploaded the same file with the double quotes removed to my server. It seemed to work fine for me.
http://www.codevsme.com/fixed.csv

 

It is not working for me.. " E107 : Input string was not in a correct format"

I did it on 2 differenct notebook.

 

are you dragging and dropping the original.csv file from evoscan directly into VD? I suspect you may be opening the evoscan .csv file with open office and saving it as something else which fouls up the formatting.

 

+1 OpenOffice can mess up a lot of stuff if you're not careful.

 

I have some .csv logs what i never opend with openoffice but not working.

What would be the problem with file that IrightI posted for me ? I didn't open it with openoffice only by VD.

 

then I have to assume these logs didn't come from an evo ecu and your ecu is spitting out gibberish to the diagnostic/logging port.

 

The same file that I linked I can open fine with VD. I'm not sure what issue you may have.

The only other thing I can think of is character set? maybe. What version of windows are you running and in what language? I see that you are in Hungary.

 

I'm here because i have no more idea what to do and not for funny or boredom
The logs are from an US 2003 Evo 8 with his stock ecu and V7 9653 ( option 4 ) rom on it, the cable is the op1.3 . But ok lets leave it that I will continueing to use the vdr.

 

one of the notebook is xp sp3 and the setting was on Hungarian, than I set it to US english ( need to restart the computer ) but nothing was happend. the other has windows 7 and US english settings I will ask somebody here maybe coud see something.

 

VGergo, IrightI:

Your problem is that they are CSV files but they have commas in the data instead of decimal points. Have you set a setting in Evoscan to have it output commas for decimal places or is this a setting in windows? If so let me know. Im thinking how I could detect this and handle it without REALLLLLLLY complicating the code that reads files in.

 

That was my first thought, but the file I posted up on my server for him to try has only the field delimiters. I don't see any commas in the float values.

You can count columns and make sure they are all the same? mehbeh.

 

VGergo, attach a small .csv file in a zip format that came straight out of an evoscan. Don't open it with open office or anything before attaching it, that could mess up the data.

 

I can open the first file he posted no problem. seems like that evo is a beast lol. 577hp?

 

Thanks for the idea mellon thats a great idea. I agree ... get me an 'unadultrated' file. I want to know what is putting the commas in there. I have contacted hamish to see if there is an option in evoscan to keep it from putting commas instead of periods in there. I want to find the source of the problem.