How to use Virtual Dyno Properly
Jul 8, 2012, 12:47 AM
#18
Former Sponsor
iTrader: (31)
Originally Posted by Drill_Sergeant
when you load up multiple logs onto VD, it will auto set different colors to differentiate between logs.
Thanks so much for posting this thread guys,lots of good info here
Jul 8, 2012, 12:36 PM
#20
Originally Posted by Drill_Sergeant
when you load up multiple logs onto VD, it will auto set different colors to differentiate between logs.
Jul 12, 2012, 08:57 PM
#22
Evolved Member
iTrader: (21)
Join Date: Feb 2005
Location: Clarksville, TN / Ft Campbell
Posts: 552
Likes: 0
Liked 0 Times
in
0 Posts
Originally Posted by wizzo 8
Yes I realize that. I was just wondering how do you change the color from red to something else if you only have one graph up?
but just uncheck the log from the left hand side of VD and it'll display only the log(s) you have checked.
Jul 13, 2012, 03:14 PM
#23
Originally Posted by Drill_Sergeant
i dont think you can change the graph to a specific color of your choosing. i think it has a default sequence it goes through.
but just uncheck the log from the left hand side of VD and it'll display only the log(s) you have checked.
but just uncheck the log from the left hand side of VD and it'll display only the log(s) you have checked.
Aug 10, 2012, 12:15 PM
#24
when will everyone start to use actual tire size when they use VD?????
https://www.evolutionm.net/forums/ev...-dyno-tip.html
https://www.evolutionm.net/forums/ev...-dyno-tip.html
Aug 16, 2012, 08:14 AM
#28
Evolving Member
In evoscan, the more parameters you log the less measure points per second you get and this as a huge influence on how much smoothing you can/must use
from my experience the less parameters you log the "smoother" the base curve is so the road is not the only reason for "spikes"
that said there's a limit at which you will get a lot of the same values in the same second because I guess the ECU and various sensors don't work that fast
I guess there must be a difference between Openport1.3 & 2.0 too since 2.0 is advertised as "slower logging"
it would be interesting to know the bare minimum parameters that Virtual dyno really requires to draw his curves, TPS and RPM ? so we can log only what's needed and nothing else
from my experience the less parameters you log the "smoother" the base curve is so the road is not the only reason for "spikes"
that said there's a limit at which you will get a lot of the same values in the same second because I guess the ECU and various sensors don't work that fast
I guess there must be a difference between Openport1.3 & 2.0 too since 2.0 is advertised as "slower logging"
it would be interesting to know the bare minimum parameters that Virtual dyno really requires to draw his curves, TPS and RPM ? so we can log only what's needed and nothing else
Last edited by Kakihara; Aug 16, 2012 at 08:23 AM.
Aug 16, 2012, 09:00 AM
#30
Originally Posted by Kakihara
In evoscan, the more parameters you log the less measure points per second you get and this as a huge influence on how much smoothing you can/must use
from my experience the less parameters you log the "smoother" the base curve is so the road is not the only reason for "spikes"
that said there's a limit at which you will get a lot of the same values in the same second because I guess the ECU and various sensors don't work that fast
I guess there must be a difference between Openport1.3 & 2.0 too since 2.0 is advertised as "slower logging"
it would be interesting to know the bare minimum parameters that Virtual dyno really requires to draw his curves, TPS and RPM ? so we can log only what's needed and nothing else
from my experience the less parameters you log the "smoother" the base curve is so the road is not the only reason for "spikes"
that said there's a limit at which you will get a lot of the same values in the same second because I guess the ECU and various sensors don't work that fast
I guess there must be a difference between Openport1.3 & 2.0 too since 2.0 is advertised as "slower logging"
it would be interesting to know the bare minimum parameters that Virtual dyno really requires to draw his curves, TPS and RPM ? so we can log only what's needed and nothing else
