Virtual Dyno
I've tried this on one of my logs I took while tuning a 99 car. As much stronger as it feels compared to stock, I'm guessing it's not close to 220hp/246Nm
Takes the log just fine, edited the car info slightly to change to the 3.636 diff ratio etc. It was a 3rd gear pull.
How do I get something slightly more realistic out of this?

Takes the log just fine, edited the car info slightly to change to the 3.636 diff ratio etc. It was a 3rd gear pull.
How do I get something slightly more realistic out of this?
1. Try using English units. Since most users have been in the US, it may have bugs when using metric. If you find that to be the case, you should make a bug report.
2. Double check the gear ratios in the car profile. 5 spd vs. 6 spd (both were available on your model year) -- there could easily be an error.
3. Double check tire diameter and weights.
4. I usually do runs both ways to cut down on wind and slope effects.
2. Double check the gear ratios in the car profile. 5 spd vs. 6 spd (both were available on your model year) -- there could easily be an error.
3. Double check tire diameter and weights.
4. I usually do runs both ways to cut down on wind and slope effects.
Last edited by hornetball; Nov 20, 2013 at 04:09 PM. Reason: Just saw you reported "no wind."
1. I'll give that a try
2. I checked all ratios for the 6 speed with FMs gearing calculator
3. I took stockish weight for a 99 and added my own, tire diameter calculated by inputting the tire size in VD itself
4. I've tried multiple logs, all give me >2xx hp.
2. I checked all ratios for the 6 speed with FMs gearing calculator
3. I took stockish weight for a 99 and added my own, tire diameter calculated by inputting the tire size in VD itself
4. I've tried multiple logs, all give me >2xx hp.
Not sure that's an oscillating AFR. The AFR's correspond to torque (i.e., being overly rich on pull 2 was hurting torque and power as compared to pull 3). That tells me the AFR is accurate.
Brad is it possible to make the minimum and maximum ranges customizable. For example say you want your boost range to be from 110kpa to 200kpa, just be able to click the bottom number set it to 110, and set the upper number to 200 and have the graph automatically scale.
No, I have a thread about my TunerStudio/MS AFR signal oscillation. MY gauge reads fine. The signal at the input pin for AFR is good, but somewhere in the MS it gets messed up and oscillates. Maybe something to do with the two burn components. But DIY said they are my idle circuit.
Okay, this is annoying. I updated VD on my personal computer. Try to load log and

Yo, No wide open throttle TPS data found. Do you want to close this log?
I'd post my log but MT.net isn't letting me go to Advanced.

Yo, No wide open throttle TPS data found. Do you want to close this log?
I'd post my log but MT.net isn't letting me go to Advanced.
I'm trying to run my log, but keep getting an error that there is no TIME collumn.
Using VD 1.2.7 and log from MS3
Log_Here
*EDIT: This is a sample log, that I have available right now. Last night I had a better log of just a 2K to 7K 3rd gear pull. Error Message is the same, and VD will not allow the log to be processed.
Help, please.
Using VD 1.2.7 and log from MS3
Log_Here
*EDIT: This is a sample log, that I have available right now. Last night I had a better log of just a 2K to 7K 3rd gear pull. Error Message is the same, and VD will not allow the log to be processed.
Help, please.
Here's what I got from your file David:

Nice numbers!
I'm not sure if VD is being actively supported or not. What I did to your file to get it to load was delete the first row (only had "#" in first column) and third row (with units) and then save it as a *.csv file. I did this with MS Excel. With that done, VD opened it just fine and produced the above output. The modified file is attached.
Send a query to the VD developer along with the MS3 file so he can make whatever changes are needed for native support.

Nice numbers!
I'm not sure if VD is being actively supported or not. What I did to your file to get it to load was delete the first row (only had "#" in first column) and third row (with units) and then save it as a *.csv file. I did this with MS Excel. With that done, VD opened it just fine and produced the above output. The modified file is attached.
Send a query to the VD developer along with the MS3 file so he can make whatever changes are needed for native support.
Well, I would not expect those numbers to be real, but the important thing is how to get the files to run.
Thanks heaps, Rick.
The 1st row I had heard about, but the third one not.
Thanks heaps, Rick.
The 1st row I had heard about, but the third one not.







