calc HP/TQ from EvoScan using Excel
This app is no different than the DLL concept, just freeware basically. It was my first attempt playing around with Excel and it will get better as I learn more, but as Bryan mentioned...just another tool. If Evoscan's HP/TQ simulator worked, or DLL was easier for the evoscan users (and cheaper) I wouldnt have bothered. I basically made it for the fun of it.


Great job man!! This thing has progressed very nicely and I am sure it will only get better. Very impressive work to all the people that have put time into refining it.
Thanks for the update 
The only thing I'm not as fond of with this version is that I can't modify final ratio for a different tire size. I know you are "done" but if you ever hop back to it the ability to put in actual gear/tire/etc would be nice

The only thing I'm not as fond of with this version is that I can't modify final ratio for a different tire size. I know you are "done" but if you ever hop back to it the ability to put in actual gear/tire/etc would be nice
That can be added easy enough. Gimme a few days

good work on the program though!
two questions:
1. smoothing really changes the numbers on a car that much (i thinking i am logging to much!)
2. when i enable the SAE corrections i get no change in the curves....i am thinking after i enable it i need to change the temperature and pressure conditions to those of SAE - what are they?
Could someone do a 3rd gear pull with the following conditions:
-wide open throttle pass from 3000 rpm to 7500 rpm
-datalog RPM ONLYYYYY
-'log to screen' feature disabled in evoscan
-super logging speed enabled in evoscan
-multi-threading disabled in evoscan
This would be of greathelp,thanks guys
-wide open throttle pass from 3000 rpm to 7500 rpm
-datalog RPM ONLYYYYY
-'log to screen' feature disabled in evoscan
-super logging speed enabled in evoscan
-multi-threading disabled in evoscan
This would be of greathelp,thanks guys
Could someone do a 3rd gear pull with the following conditions:
-wide open throttle pass from 3000 rpm to 7500 rpm
-datalog RPM ONLYYYYY
-'log to screen' feature disabled in evoscan
-super logging speed enabled in evoscan
-multi-threading disabled in evoscan
This would be of greathelp,thanks guys
-wide open throttle pass from 3000 rpm to 7500 rpm
-datalog RPM ONLYYYYY
-'log to screen' feature disabled in evoscan
-super logging speed enabled in evoscan
-multi-threading disabled in evoscan
This would be of greathelp,thanks guys
all pre-requisites have been met.
Last edited by nonschlont; Jun 10, 2009 at 06:52 PM.
Could someone do a 3rd gear pull with the following conditions:
-wide open throttle pass from 3000 rpm to 7500 rpm
-datalog RPM ONLYYYYY
-'log to screen' feature disabled in evoscan
-super logging speed enabled in evoscan
-multi-threading disabled in evoscan
This would be of greathelp,thanks guys
-wide open throttle pass from 3000 rpm to 7500 rpm
-datalog RPM ONLYYYYY
-'log to screen' feature disabled in evoscan
-super logging speed enabled in evoscan
-multi-threading disabled in evoscan
This would be of greathelp,thanks guys
Note that there was a NLTS to 4th at the end... I just couldn't resist. Looks like the RPM jumped about 150 RPM, so you might want to remove that.
68 °F
Barometer: 29.82"
EDIT: here is 3rd isolated from that log
http://thefrost.net/randomfiles/tuni...olated.csv.xls
Also, it would be nice if you could take the names of everything from one place IE so I can replace "base" somewhere with a more meaningful label (for later comparison) and have it populate through the spreadsheet. You can just use "Concatenate( text1, text2, ... text_n )" to make it look right in the other cells.
Last edited by fostytou; Jun 10, 2009 at 04:48 PM.
Well, so far the best combo is version 5.0 that I posted already. I can get the resolution to be ASTOUNDING but there are too many variances in datalog data per second to make it consistent. The software in a real dyno has a 'set in stone' pre-determined amount of data per second so its easy to have their graphs the same regardless of the pull. The thing that ruins the data is repeated RPM values. With a data file with poor resolution, the largest gap between RPM values is between 200-250 RPM, which is why I chose to have the data recorded every 250 RPM so no matter what size file you load, it'll work.
From 3000-8000 RPM we only have 160 possible RPM values when using the standard 1-byte RPM. If we use the 2-byte RPM instead we will have 1280 RPM values from 3000-8000 RPM but I'm not sure how the infamous 2-byte spikes will affect the data.
What I might do is have 2 seperate simulators built-in to one with a dropdown box for 1-byte or 2-byte RPM. What I will need is some logs from 3k-7+k RPM while logging ONLYYYY 2-byte RPM, hopefully some logs with the infamous 2-byte spikes in them. If I can prove that the smoothing will remove the spikes then I can make one VERY accurate simulator for us. Thanks to everyone who has contributed data files thus far!
I have the tire diameter stuff all figured out and I will make a label window so the users can change the base pull/comparison pulls.
From 3000-8000 RPM we only have 160 possible RPM values when using the standard 1-byte RPM. If we use the 2-byte RPM instead we will have 1280 RPM values from 3000-8000 RPM but I'm not sure how the infamous 2-byte spikes will affect the data.
What I might do is have 2 seperate simulators built-in to one with a dropdown box for 1-byte or 2-byte RPM. What I will need is some logs from 3k-7+k RPM while logging ONLYYYY 2-byte RPM, hopefully some logs with the infamous 2-byte spikes in them. If I can prove that the smoothing will remove the spikes then I can make one VERY accurate simulator for us. Thanks to everyone who has contributed data files thus far!
I have the tire diameter stuff all figured out and I will make a label window so the users can change the base pull/comparison pulls.
Evolved Member
Joined: Mar 2008
Posts: 730
Likes: 3
From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Very neat tool, thank you for sharing.
My wish list would include setting of custom gear ratio's (non-evo mitsu)
and metric unit system....
If it was not password protected I would do it myself...
,
And I am not in the mood to crack the password
My wish list would include setting of custom gear ratio's (non-evo mitsu)
and metric unit system....

If it was not password protected I would do it myself...
, And I am not in the mood to crack the password
Last edited by acamus; Jun 13, 2009 at 03:16 AM.
So I found a nice way to standardize how many lines of data gets inoutted thru the formulas by using the 'lookup' feature I can have the spreadsheet find the closest data at RPM intervals. So it will look in column 'B' for the closest value to 3000 rpm, then 3050 rpm,then 3100 rpm, etc... and also have it lookup the LogEntrySeconds in that same row. I will set it to check from 3000 rpm to 8000 rpm in 50 rpm intervals which will give us a constant 100 lines of data regardless of the file size. This should help make the spreadsheet more consistent between large and small datalogs, and make it easier to have the smoothing factor be consistent as well. I just need to do some more testing to find the best smoothing values to use and such.
Just a thought....
This is an awesome tuning tool, and you/we're soo close...
I notice that in Ver 4.1 if I start a pull at 2500 the plot pretty much starts at 2500 (just a little higher). On Ver 5 with the same data (pull starting at 2500 or even 2250) the plot starts at approx 3300 and by that time the stock 9.8 was almost full boost so I do not see the torque curve goingup like the earlier versions. Ver 5 has some nice features but in my case the plot look more complete and more like a dyno readout on ver 4.1 because of the late plot graph on ver 5. Also ver 4.1 it can be modified (not password protected like ver 5).


