Originally Posted by triple88a
Any chance to add adaptronic logs to the supported log types?
This is what I've discovered so far playing around with Virtual Dyno:
1. Virtual Dyno uses the names found in the first row of a comma-delimited text file to get its parameters. The first row limitation is important. For example, a Megasquirt log writes the software version number on the first row and the parameter names on the second row. Therefore, you need to open that Megasquirt log and delete the first row for it to work with Virtual Dyno.
2. Virtual Dyno names can be assigned to match what is in your file with a pulldown menu (under File=>Options=>Columns and Profiles). The parameters that Virtual Dyno needs to work its magic are:
-Time (Required for dyno plot)
-RPM (Required for dyno plot)
-AFR (Optional, needed if you want the AFR trace below the dyno plot)
-Boost (Optional, needed if you want the Boost trace below the dyno plot)
-TPS (This is listed in the menu, but I can't discern how/if it is used)
3. Because of #2 above, I really wouldn't pay much attention to the "list of supported ECUs" on Virtual Dyno's website. If you are handy with a sheet or text editor program and your ECU's output is human-readable text, you'll be able to use Virtual Dyno.
Here's an example of setting up with a log file from a MSPNP9093 (basically a Megasquirt I):
1. Open log file in Excel and delete first row. New first row should be parameter names.
2. Edit the data so that the pull you want to show is the only data present. This isn't strictly necessary, but you will get a lot of unwanted artifacts on your plot if you don't do this.
3. MS1 plots have "Time" and "RPM" columns. These are used as-is by Virtual Dyno.
4. MS1 plots have the wideband readout in volts under "O2" in Excel column F. To convert this to AFR, you need to know what the volts represent. In my case, I'm setup so that 0VDC = 10:1AFR and 5VDC = 20.8:1AFR. So, I created a new column in my data called "AFR" and used the following equation:
"=10+F#/5*(20.8-10)" where # is the Excel row number
I then opened "File=>Option=>Columns and Profiles" in Virtual Dyno and put "AFR" into the "AFR" option. I had expected that by calling the column "AFR," Virtual Dyno would know what to do with it, but it didn't work out that way. ?? Make sure the check mark is on next to "AFR."
5. If you want Boost plotted in units of PSI, then you need another calculated column. MS1 plots have a manifold pressure readout in KPa under "MAP" in Excel column D. MS1 plots also have an atmospheric pressure readout in KPa under "barometer" in Excel column AC. So, create a new column in your data called "Boost" and use the following equation:
"=14.696/101.3*(D#-AC#)" where # is the Excel row number
Open "File=>Option=>Columns and Profiles" in Virtual Dyno and put "Boost" into the "Boost" option. I had expected that by calling the column "Boost," Virtual Dyno would know what to do with it, but it didn't work out that way. ?? Make sure the check mark is on next to "Boost."
6. I actually prefer plotting MAP in KPa instead of boost. This makes it easy for me to correlate to my spark and fuel maps. To make this happen, open "File=>Option=>Columns and Profiles" in Virtual Dyno and put "MAP" into the "Boost" option field. Done. Couldn't be easier. Again, make sure the check mark is on next to "Boost."
7. There is also a TPS field in Virtual Dyno. In MS1, the thottle position value is called "TP" in Excel column E. I put "TP" into the "TPS" option field. Doesn't seem to have any effect. ??
This is no different than a real dyno. To make valid comparisons, you need to eliminate variables so that, hopefully, only the effects of the tuning parameter you are working on are seen. To that end:
1. Do your comparison runs at the same time and place if possible. This is easy if you are just changing ECU parameters (make a run, reprogram ECU, make another run). Harder if you are changing mechanical items. If changing mechanical items, then use the same stretch of road and try to do compared runs under nearly identical weather conditions.
2. Be cognizant of aerodynamics. Windows, top and, for NAs, headlights will change your results. To get a "close" horsepower reading using the Mazda-published drag coefficient, you need to have windows closed, top up (or hardtop on), and NA headlights retracted.
3. Do two runs on the same stretch of road going opposite directions. This helps cut down on the effects of wind and slope. Your comparison plot would be the average of the two runs.
Does it work? Heck, yes, it works. Last night, I tried it in earnest for the first time. I wanted to compare two spark maps. The first is based upon the MSPNP default spark map as follows:
The second has a bit more timing, especially at high RPM:
Here's the result plotted by Virtual Dyno:
The additional timing at high RPM is clearly seen as increased torque and HP in that region. MUCH better than a butt dyno and, so far as I can tell, the data seems to be as useful as that from a real dyno. Now, if only I could hold a constant RPM . . . . Nonetheless, this looks like a valuable tuning tool to me.
Now, about the numbers . . . not too impressive. Keep in mind that my headlights were up. I'm certain that if they had been down, I would have gotten 270RWHP+ out of my non-intercooled Greddy.
Possible Bugs for Brad:
1. Need to specify AFR custom column name even if column name is "AFR."
2. Need to specify Boost custom column name even if column name is "Boost."
3. What does TPS do?
4. The auto update of car profiles overwrote a custom profile that I had stored. This was mildly annoying. It would be nice if there were a message that informs the user that new car profiles have been written.
5. I would love to be able to plot an average of multiple runs. That way, I could combine going two directions on a stretch of road. Doesn't seem like it would be too hard.
6. Help leaves a bit to be desired (there isn't any). Feel free to use anything I've written here to get that started.
7. Cool app. Glad to have you aboard. I'm not sure whether you are a Miata guy, but you owe it to yourself to take a drive one. If you're ever in the DFW area . . . .
8. You get a prop!!