Virtual Dyno - Standalone Software
Thread Starter
Evolved Member
iTrader: (1)
Joined: Oct 2008
Posts: 692
Likes: 1
From: Kansas City, KS
Thats due to a fix in the smoothing algorithm that was exponentially smoothing the later parts of the log. Im surprised it wasnt flattening the crap out of the last part of the logs for people.
Thread Starter
Evolved Member
iTrader: (1)
Joined: Oct 2008
Posts: 692
Likes: 1
From: Kansas City, KS
hahahaha ... it was hardly noticeable on any graph but it did flatten parts of the graph more than others so it had to be fixed. It caused some to think they were making more power with 1.1.8 and questioned its accuracy. *Sigh* all from fixing a long standing bug.
It's late, and I don't feel like searching, so how do I get the RPM to show my full pull? my pull went to 8800. 2byte RPM in my log shows the correct RPM, but the default RPM only showed the 7996 which limited the VD to reading 7907
Delete the regular rpm column in your log so that you only have 2byte rpm left, and add the 2byte rpm column name to the list of column names in the options
Thread Starter
Evolved Member
iTrader: (1)
Joined: Oct 2008
Posts: 692
Likes: 1
From: Kansas City, KS
Thread Starter
Evolved Member
iTrader: (1)
Joined: Oct 2008
Posts: 692
Likes: 1
From: Kansas City, KS
Also this shows to only log the columns you need and not every column you recognize.
I have a thought about the smoothing your using, When used it seems to have a more 'averaging' effect , Some people are using it to smooth out huge dips in the road.
I have no technical way to say this as im not computer literate, but it seems if the smoothing could focus on a narrower band of RPM you would have less people making the mistake of posting up graphs with a smoothing of 8 just to cover up a dip in the road that is creating a 100 HP spike...
Im not upset in the least bit, i usually look at my graphs on 1 and smooth them to 2 to get rid of the little stuff in the road so its not a problem personally, But has caused some to question the programs accuracy when in fact its user error.
I have no technical way to say this as im not computer literate, but it seems if the smoothing could focus on a narrower band of RPM you would have less people making the mistake of posting up graphs with a smoothing of 8 just to cover up a dip in the road that is creating a 100 HP spike...
Im not upset in the least bit, i usually look at my graphs on 1 and smooth them to 2 to get rid of the little stuff in the road so its not a problem personally, But has caused some to question the programs accuracy when in fact its user error.
Little bug I noticed Brad:
If I have "show maximums" enabled, then toggle data points on, then back off again, the maximums will also disappear even though they are still enabled. I have to go to the options, turn them off, save, then turn them back on again.
If I have "show maximums" enabled, then toggle data points on, then back off again, the maximums will also disappear even though they are still enabled. I have to go to the options, turn them off, save, then turn them back on again.
Hey Brad, first I want to say awesome job with VD, its a sweet program. I've just got an evo 9 and it works fantastic. I do have a question tho, what does your program look for in the csv file to open in VD? I have a honda and datalog with a program called ecucontrol. It datalogs a file very close to that of evoscan with the RPM, TPS, and TIME as the top columns and then the data going down. I tried loading a log into VD but it keeps saying no wot data. I tried moving the TPS column to the same column as a evoscan datalog but it still won't read. I can send you the datalog to look at if you like, If I can use VD on my honda that would be awesome. Thanks



