When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Hey guys, I'm working on a quartermile dragstrip simulator. It works off of dyno numbers. I've got the stuff setup but I need some more real world data to double check everything is right. If anybody can step up with some info I'd love to have it. Here's what I'd need.
Horsepower from a dyno
2500:
3000:
3500:
4000:
4500:
5000:
5500:
6000:
6500:
7000:
Type of dyno: Mustang or Dynojet
Type of Transmission(be specific please)
Shift RPM
Rear End Ratio
Tire Size
Race Weight of veicle and driver
60' times
Type of vehicle (for aerodynamic properties)
Then I would need a timeslip 60' and quarter stats are the only ones I really need, but the rest would help.
Type of dyno: Dynojet
Type of Transmission(be specific please): 700R/4 with 2,000rpm TC
Launch RPM: 1,700rpm
Shift RPM: 1-2 @5,200rpm; 2-3 @5,800rpm
Rear End Ratio: 2.59:1
Tire Size: 25.6" diameter, GY Eable 275/40-17
Race Weight of veicle and driver: 3355 lbs
Type of vehicle (for aerodynamic properties): 1988 Corvette coupe
Then I would need a timeslip 60' and quarter stats are the only ones I really need, but the rest would help.
60' - 1.913sec
330' - 5.481sec
1/8 mile @ mph - 8.447sec @83.01mph
1000' - 11.013sec
1/4 mile @ mph - 13.205sec @101.73mph
mn_vette interesting that you got pretty close.
Have you put in vehicle frontal area & form factor?
Do you take into account traction and converter slippage percentage.
Some of these may help you get even closer.
But don't foreget that some things, like coolant temp, can vary engine HP at the time of a race so that the actual power curve may not exactly agree with the dyno.
I use Drag2000 drag strip simulation to optimize parameters for the strip and found that I have to tweak items like traction and launch RPM to get the numbers to exactly agree with time slips.
Quarter Jr. and Performance Trends ET Analyzer are the two best programs I've used. On the Super Stocker using PT's 4-link calculator and ET program we're within .02 of our actual ET's and MPH is DEAD on! Of course 2.5 hours worth of screwing with the parameters to make sure EVERYTHING is spot-on helps with the results.
-Jeb
mn_vette interesting that you got pretty close.
Have you put in vehicle frontal area & form factor?
Do you take into account traction and converter slippage percentage.
Traction is covered in the 60' time, if you don't have traction after that point then I'm not sure what to tell you.
The converter slippage is actually covered in the RWHP numbers. if there is any kind of sliping going on it will show up in the numbers.
I do use drag coefficients and square feet of frontal area to find the aerodynamic resistance used. If I modified it slightly I could find the theoretical top speed of a vehicle(hp limited not gear limited), but it would take longer for the thing to run. http://www.teknett.com/pwp/drmayf/tbls.htm
I know that this isn't one of those hightech calculators, but its nice to have something to give you just a general reference. Besides I was bored a few days at work and whipped it up. I'm just trying to figure out if I'm close to accurate. I'd still like to get some more hp and timeslip numbers.
I smell AS/400! Oh wait, iSeries. Whoops! Think they're calling it the eServer i5 this week
Sorry, couldn't resist.
Ben
Well, you've got a pretty good educated guess, but I'm not with the server group. Have you ever heard of the new Cell Processor that IBM has been talking about lately? I've been working on that. Its the new processor that's going into the new Playstation.
As far as the 60' times go its an itterative process that asks what you want the 60' time to be and it makes an educated guess as to what the g-force should be. It calculates out the 60' and if it's out of tolerance it adjusts and recalculates. It does this only 5 times due to the fact that it takes a while to run the program. It takes about 2-5 minutes to run depending on your computer speed. Since this is running in Excel you can only imagine the overhead that it generates to slow things down. It would be really easy to make this into a C++ program that would run atleast 10 times faster but I don't currently have access to a development environment.
Last edited by mn_vette; May 17, 2005 at 10:01 AM.