As the subject says.
I am very happy with the calculations, my numbers are exactly where i thought they would be.

 

i would take a GTEK PRO, or go to a track before datamaster calc.

 

Knowing exactly where to start the calculation from in datamaster is the only problem. Moving it one step either way in the record can cause some big differences. Ive played with it a little and figured it wasnt very accurate

 

I chose the starting point (record) that displayed 0MPH that is just before the record that shows XMPH.

If nothing else it should be very good as a reference tool to use when doing upgrades and test runs.

 

But how do you know what mph you were at when you crossed the 1320 foot mark, then you have to correllate that with the recording.

Also I would assume you need to have the car running engine only @ 10 readings a second.

This to help get it close as you possibly can. Having a passanger reading this helps but then the added weight will throw off your time (at least 100-230 pounds more)

 

The calculator somehow calculated. Whether its accurate is open to debate.
Could be fuzzy math.

 

Datamaster has the time and speed. It will calculate the distance based on that. The biggest error comes from doing the calculation starting right before the mph changes from 0. You will not be able to get a 60' as nice as the one in Datamaster very easily in reality. Besides that, all of it is based on calculations, averaging, etc., so it should only be used as a general reference (and not a very accurate one at that).

 

i have datamaster you use the rec and its from when your mph goes to 1 and then whenever you cross the traps, if you dont know what Recording that was, you cannot Accurately figure out your ET/MPH, but you can Approximate at best.