http://www.bradbarnhill.com/projects/VirtualDyno/

I came across this on another forum and it looked pretty interesting. Apparently they've created software that will allow you to convert a datalog into a dyno graph. It seems like this would be very helpful in tuning or giving feedback on a particular mod. It doesn't look like megasquirt is currently supported, but from what I've read it sounds like it could potentially be made to work. Has anyone played around with something like this before? Or know of software that works right out of the box?

Obviously there are going to be some limitations but it seems like all the data should be available in the log (time, acceleration, rpm) or able to be reasonably estimated (drag, weight, tire size, gearing). I could even see it being useful for aero tuning which would theoretically show up in the hp/tq of the "dyno".

 

MLV will calculate horsepower.

 

Lots of software/loggers can do the same. Even some air fuel ratio loggers!

 

Guess I'll have to look into that, I never noticed the option.

 

From memory the LC1 software also had that option.

 

I have exchanged messages with the creator before while giving the software a go using some of my programs. He would need vehicle specific data for the MX-5 generations to get things going. Afterward, feedback with datalogs and VD plots versus actual dyno results will help with revised "accuracy" for future updates/releases.

This is my personal tuning sample with an EMU exported .txt/.csv file:


It is useful when fine-tuning for gains or MBT. In the meantime, I will probably use my G-Tech Pro RR with the Mazda

 

It now claims to support "megasquirt3" but it doesn't seem to recognize any of my log files... and google doesn't seem to know anything about it. I tried renaming a msl file to csv and txt, no dice. I even tried converting all the tabs to commas and it still won't read the file.

 

were you SD logging?

 

Not specifically, but they look to be the same tab delimited format. (once you convert them)

 

yeah, okay. weird. I do like how it presents the data if you can get it to work.

 

Sent the guy an email, we'll see what he says... has to be something stupid right?

 

Quick update, if you delete the first line from an msl file it seems to be able to parse the files (I've been renaming them .txt so it finds the files)

 

oh yeah, the MS adds some info above the header row of the database file.

 

Some NA Miata aero data for using this app:

Cd = 0.38
Frontal Area = 1.711m^2 = 18.42ft^2
CdA = 0.65m^2 = 7.00ft^2

 

Neat... I just made this:

<?xml version="1.0" standalone="yes"?>
<CarDataset xmlns="http://tempuri.org/CarDataset.xsd">
<CarParameters>
<CarMake>Mazda</CarMake>
<CarModel>Miata</CarModel>
<CarSubModel>1.8</CarSubModel>
<StartYear>1994</StartYear>
<EndYear>1997</EndYear>
<Weight>2300</Weight>
<TransTypeManual>true</TransTypeManual>
<TransGear2>1.888</TransGear2>
<TransGear3>1.330</TransGear3>
<TransGear4>1.000</TransGear4>
<FinalGearRatio>4.100</FinalGearRatio>
<DragCoefficient>0.38</DragCoefficient>
<FrontalArea>18.42</FrontalArea>
<TireDiameter>23.68</TireDiameter>
</CarParameters>
</CarDataset>

call it miata_94.xml, create a 'Miata' directory under this directory

C:\Documents and Settings\(your account)\Application Data\Virtual Dyno\Cars\Mazda

 

Don't forget to include driver weight.

 

Just started messing around with this. It is working just fine with MS1 data in *.csv format (after deleting the first line, that is). Basically, it works off of column titles.

Hmmm . . . may have to go do some dedicated runs.

 

Here's my file for 89-93 Miatas. I bumped up the weight to account for AC/PS/Turbo + the steel hood that found its way onto my car sometime over the last 21 years. Tire diameter is for a 205/50R15.

<?xml version="1.0" standalone="yes"?>
<CarDataset xmlns="http://tempuri.org/CarDataset.xsd">
<CarParameters>
<CarMake>Mazda</CarMake>
<CarModel>Miata</CarModel>
<CarSubModel>1.6</CarSubModel>
<StartYear>1989</StartYear>
<EndYear>1993</EndYear>
<Weight>2250</Weight>
<TransTypeManual>true</TransTypeManual>
<TransGear1>3.163</TransGear1>
<TransGear2>1.888</TransGear2>
<TransGear3>1.333</TransGear3>
<TransGear4>1.000</TransGear4>
<TransGear5>0.814</TransGear5>
<FinalGearRatio>4.30</FinalGearRatio>
<DragCoefficient>0.38</DragCoefficient>
<FrontalArea>18.42</FrontalArea>
<TireDiameter>23.1</TireDiameter>
</CarParameters>
</CarDataset>

 

He's going to add my 1.8 and 1.6 miata definitions to the program for the next version. Does anyone know what the cd and frontal area of an NB is? I'll make up a 5sp and 6spd NB for him to add too.

 

That with the barn door headlights up or down?