Can't open msl log in Virtual Dyno
Brand new to this, just been figuring out tuning in real time. Haven't gotten into logging anything too much, so I'm not super familiar with the software. Did a couple third gear pulls and logged it as MSL in megalogviewer, and i cant open the logs up in virtual dyno, it gives me an error saying "MISSING COLUMNS: Time, RPM, Throttle Position" I did some research and saw people tweaking stuff on excel, which i don't have so i messed with a copy of the file on notepad to no success. Here are a couple of my logs. Thanks for the help in advance!
Open up the log files in a text editor (like notepad). Remove the first two lines - the ones in double quotes that contain your firmware version and capture date. The first line should then be the actual header row that starts with "Time". Now, within that row, remove all of the parentheses characters that occur - in particular, you have some truncated field names that have a left-parenthesis character in them. Save the changes and you should be able to load the resulting file.
There's also a way to change the text that Virtual Dyno looks for in the logs. Basically you can override the expected column labels to the ones that MLV automatically applies.
I don't remember the exact way to do that right now, but it makes it so you don't have to manually adjust every log.
I don't remember the exact way to do that right now, but it makes it so you don't have to manually adjust every log.
There's also a way to change the text that Virtual Dyno looks for in the logs. Basically you can override the expected column labels to the ones that MLV automatically applies.
I don't remember the exact way to do that right now, but it makes it so you don't have to manually adjust every log.
I don't remember the exact way to do that right now, but it makes it so you don't have to manually adjust every log.
I'm not sure why the initial comment header lines had to be removed as well, but it was still failing to parse when I left them in. No strange characters or anything in those when comparing to the logs from my MS2 that VD parses just fine.
Thread
Thread Starter
Forum
Replies
Last Post





