Found the issue of DieselPower, much simpler way to find HP based off of 1/4 mile E.T. and vehicle weight. From the Jan '09 issue:
CALCULATING HORSEPOWER FROM QUARTER-MILE ELAPSED TIME AND SPEED
E.T. divided by 5.825, then cube the result (multiply by itself three times, ie: 4x4x4) then divide the vehicle weight by that cubed number. That gives a very close number to the flywheel horsepower. To get RWHP, you must allow for driveline loss of about 20%, so take the number above and multiply by .8 to get RWHP. This is a very close approximation, but is subject to error due to things like traction problems, transmission slip, reaction time, turbo spooling, etc.
Here are two examples of number crunching:
Vehicle weight: 8,000lb. E.T. 15.9 sec. => 15.9 / 5.825 = 2.73 => 2.73 x 2.73 x 2.73 = 20.346 => 8,000 / 20.346 = 393 hp. 393 x .8 = 312 rwhp
V.W.: 7,200 lb. E.T. 11.55 sec. => 11.55 / 5.825 = 1.974 => 1.974 x 1.974 x 1.974 = 7.692 => 7,200 / 7.692 = 936 hp. 936 x .8 = 748 rwhp
Thanks to DieselPower for the numbers, the article can be found starting on page 144 of the Jan '09 issue.
So, let's pull some numbers out of our *ss for shits and giggles for Leroy's conversion project.
Let's assume a weight of 7,100 lbs including driver and a full tank of fuel for the Burb, and after getting his Optishift dialed in, he laid down a respectable 15.4 E.T. at the local 1/4 mile "midnight test run" location. Let's run the numbers:
15.4 / 5.825 = 2.644 => 2.644 x 2.644 x 2.644 = 18.484 (I'm rounding to the nearest 3 digits after the decimal point) => 7100 / 18.484 = 384.12 hp => 384.12 x .8 = 307.2 rwhp, a very realistic number. Using the S.W.A.G. method of hp to torque (torque is approximately twice rated flywheel hp) and you get 770 lb/ft at the flywheel and 615 on the ground.
Of course, nothing beats putting it on the rollers, but that even will vary from machine to machine as well as ambient conditions such as temp, humidity and roller traction will affect the results.
Much easier to understand. I'll try to meassure out a 1/4 mile somewhere and give it a try before the second OptiShift table is programed