RomRaider

He just put that function there so that you can copy it into RomRaider. Standard practice is to take max wgdc- 8 or 10 and make that you initial wgdc.

thank you!

looks like ive been going about it all wrong . back to the drawing board...

I just wanted to give Airboy & mickeyd2005 a big thank you for all of their hard work. This is an amazing tool that makes it sooooo simple to check your tune and make adjustments.

Damn I love open-source and contributions from the community

I really wish I had the skills to contribute myself .....

jm2c

Sunny, I don't know how useful this is... but I incorporated my acceleration plotter. I used a similar spreadsheet to estimate how beneficial changes made to the tune are. Acceleration is related to horsepower and torque so it's a primitive road dyno. I just need to calibrate it.

For comparison purposes, it's still handy even if it is not calibrated. As long as the road is the same and the environmental conditions are similar then it can be used to compare between tunes.

BTW, I also modified the get headers macro for the boost interpolation sheet. Now, it will automatically select Manifold Rel. (corrected) pressure as boost in addition to the Manifold Relative Pressure.

edit: <see 3 posts down for updated spreadsheet>

Just a couple of days ago I was thinking about adding HP/Torque calculation based on RPM and time (like the program mentioned in the road dyno thread). I was not sure how to implement the filter function but it looks like you have something that might work.

It looks like if you include some user entries for vehicle mass, gear ratio, tire size, and frontal area you should be able to convert the numbers to power/torque.

Thanks for extra work.

No thanks necessary. I hacked this spreadsheet together out of necessity and am just glad that others have found it useful.

Sunny

I modified the acceleration module so that acceleration is now in units of G's instead of the funky rpm/millisecond. Hopefully, my math is correct.

There are some parameters that will be used to generate torque and horsepower curves. It will be difficult to account for all the variables so I'm thinking about using calibration constants for each model type (LGT, WRX, Spec B, STi, FXT, Baja). If people have good dyno charts in 3rd gear that they can contribute in combination with a good 3rd gear datalog on a flat windless road then we can easily come up with a lookup table for allt he model types.

This module MAY work with automatic transmissions. However, they would need to datalog speed in MPH in addition to RPM and I have absolutely no idea how it would compare to a real dyno chart with an unlocked torque converter (those plots have x-axis as a function of wheel rpm and not true engine rpm).

Let me know what you think and if I made any mistakes. When I was younger, I used to program in C (ancient forebear) and never learned VBA or EXCEL so I don't know all the methods in VBA EXCEL.

EDIT: See later post.

Unfortunately, it looks as if Excel 2007 pukes on the spreadsheet. Right after I import in the csv log it blows chunks.

jt

What error message do you get?

Security settings?

Security at the opening of it which is easily correctable by hitting [Options] then selecting [Enable this Content], and hitting [Ok].

The major one is when you get into the spreadsheet, goto the Data tab, Click [Import CSV File], Select your csv log file, Click the [Select Data Items to Graph].

Odd, this time it did not do it. This is the first time it hasnt done it (two different computers, two different clean installs of the OS/Software on this laptop). I have no clue, but the only thing I did here that I dont normally do, is I went slow to make sure to copy down all the options to this e-mail that I was selecting.

Freaky, heck with it for now.

jt

Are you importing ecuExplorer logs? The square brackets in the file names will crash the macros unless you rename the files. RomRaider logs don't have the square brackets and will import without renaming.

Nope, RomRaider logs, and the log in question is literally named log.csv. I'll see if I can get excel into debug mode and figure out what the deal is.

jt

I'm using Excel 2007 and all looks to work fine but my plots are way off when I do timing interp. Not sure if it's me or the spreadsheet. Here's the sheet. Notice timing interp. is way off. Red line and black line should be much closer from what I understand. I'm I doing something wrong or is it Excel?

I was hoping to avoid posting a clueless newbie post, but I am just not seeing my error.

I loaded up a log from the current version of RomRaider, filtered out a single short WOT run from 2700 to 4300 rpm (just trying to figure out how the spreadsheet works). I click plot and get a nice graph showing my base timing, ignition timing, and boost, plotted against rpm. Plot looks correct according to the data in the log.

I pasted in my Base Timing map from RomRaider into the Base Timing tab. Pasted in Timing Advance (Maximum) table into the Advance tab. In both I have lined up the headers row with the Table3D label, so I have a nice square of data. I removed the extra rows that were there by default before pasting in my table. Data in the table matches what I see in RomRaider.

Now, when I go to the interpolate Timing Interpolate tab, everything has defaulted correctly except for engine load. So I choose the correct Engine Load from ram item, and hit Get Data. I see the correct load data listed, along with correct rpm and timing and KC.

Next I click Interpolate Timing on the Timing Interpolate tab, and I get the headers for Map Base Timing, Map KC, Base + KC, and Logged Timing - Map KC. But all of these new headers have no values in the rows beneath them.

This makes me think I must have pasted the map data in wrong, but it looks 100% correct. I cannot think of anything else I may have done wrong :confused:.

I'll attach my spreadsheet in case anyone is up for glancing at it to show me the error of my ways.

Thanks for the awesome tool!

You should use the "Filter (WOT data only)" button to extract the full throttle data or at least delete the empty rows between the header and the actual data. An empty cell in the RPM column is how the interpolation macro figures out that it has reached the end of the data and stop.