RomRaider

Mustangs do indeed use a non-linear load...it's an exponential curve based on roller speed IIRC. There are also a number of testing modes -- most of the world is familiar with the "Power Curve" test, which tests the car in a single gear through a set RPM range. There are also vehicle simulation modes.

One Question.

Is it Wheel Horse Power or at Crankshaft?

Cause: my logs with my 2004 EDM STi are good, all seems to be right,
light tuning an the spreadsheet says 230 HP.
So if its WHP its ok i think.
BUT, when i log my 1999 Impreza Turbo (original 218PS at crankshaft),
the spreadheet says 211 HP. Thats really to much if this are wheel horse power.
So where is the problem?? All data are ok, i have the right weight, wheel diameters,
drag coefficient and so on.

Both cars feel normal, so there is no problem that the STi are too slow or the
1999er too fast or so.

Can anyone explain me these numbers?

Sorry for my bad english

it is estimated WHP. Check to ensure the weight and gear ratios are correct for your 1999 model, otherwise the WHP will be very skewed (incorrect).

Leslie

Soo... I've been fooling around with the spreadsheet and figured out how to extract data from a rom file and populate the tables for Base Timing. Populating the other tables is just a matter of writing the code and cleaning things up.

I'm still trying to figure out how to get the hex addresses and calculations from the XML definition file in an automated fashion. Currently, I have a worksheet with a manually created table that lists some various roms and their timing map specifications. Excel grabs the ROM ID, looks it up on the definition worksheet, then populates the tables. It seems to be working pretty well and has potential.

Is there any want/need for this?

The ability to have the spreadsheet transfer tables directly from the ROM would be awesome. I wanted to but lacked the macro knowledge. Are you doing this via ActiveX controls?

Can you share your spreadsheet? I would love to take a look.

Can't seem to get it to plot right.
2009 wrx sedan premium
TP Stage 1
75* about 55% humidity

This would save a lot of stuffing around if you could get it to work. It would also be great if someone could port this spreadsheet to excel 2007/2010 as it doesn't work 100% using excel's own conversion.

Cheers,
Matt.

Is there a later edition of this?

It would be nice to get accurate info in the drag co-eff, and the frontal area of our cars. Right now it looks like ver#4 just has the exact same numbers for all cars, which is not correct.

hey guys for some reason when I import the csv file and look at the dyno plot it reads very low, something like 178 whp and 188wtq, car is an 06wrx with vf39. can't figure out if i'm doing anything wrong.

is there a cure to mate ecuedit log files with this tool?
I keep getting 1004 error upon applying accel calculations, and I did rename the log file so it has a short name with no brackets

'The factor 45.54865424430 converts mph/milliseconds to Gs.
'conversion factors
' 5280 ft = 1 mile
' 1 hr = 3600 seconds
' 1000 ms = 1 second
' 1 G = 32.2 ft/second^2
' cell N9 is the conversion from mph to rpm
Cells(row, 5).Value = "=SLOPE(D" & (row) & ":D" & (row + 1) & ",A" & (row) & ":A" & (row + 1) & ")" & " * " & 45.5486542443 & "/" & Time_multiply

ecuedit has a road dyno built in, doesn't it?

The first column in the log file has to be time stamps. Would be helpful if you attach a sample log as well.

yeah it does
I am actually curious to compare it

here's a sample log

The file ran fine through the spreadsheet.

Are you using MS Excel?

yep, 2007 office

hmm... I might have an idea,
I am located in EDM zone with local windows settings, it might interpret some values wrong thus I am not able to use the dyno?
however everything else shows up ok

run the macro and get a screenshot of the error message, then hit the "debug" button and see which line of code it highlights