My only concern here is the accuracy of the app.
Earlier in this post I posted a youtube link of a guy that used this app on the drag strip and compared it to the actual drag ticket. It was within 1 second.
Also reviews of this app showed many complaints about gps lock and losing signal. I ran into that as well. What I found out was it must be a clear sky (not cloudy) and you can't be right at the base of a couple of mountains LOL. It needs a clear shot at the sky.
I know for sure that the top speeds are very accurate based on other tests I ran years ago with a gps and a truck speedo.
But at the end of the day this is still the best data we got to date.
CO

I really wish I had an all when I was changing clutches. And see the difference in each. My machine is down right now need to find crank seals.

Sorry guys but I am still learning about this app on my phone.
I couldn't figure out why the screen suddenly only showed me the results from 10mph to 40mph and the graph but nothing else.
The reason was that I didn't know how to use it. Apparently all you have to do is swipe the screen and more info shows. I could now see the 0-60 time and feet and also the 1/16th and 1/8th times, as well as the graph.
So now I am going to post those results again but with all the info.
I will post each machine separately in a new section.
CO

Ralph's machine (super Engine)
CO

My machine.
CO

Death machine.
CO

This is the data:

Mph - seconds - feet
Ralph corrected times (minus 1 second for wheel spin)
10 - 1.4 -23
20 - 2.8 - 80
30 - 4 - 153
40 - 4.5 - 212
50 - 6.5 - 305
60 - 10.2 - 719

Mine
10 - 1.6 - 13
20 - 2.1 - 45
30 - 3.1 - 96
40 - 5.3 – 217
50 - 9.3 - 496
60 - 16 - unknown

Death Machine
10 - 1 - 8
20 - 2.3 - 51
30 - 3 - 90
40 - 5.1 – 211
50 - 8.2 - 431
60 - 15.5 - unknown

So at the end of the day the answer to the question 0-60 is:
About 15 to 16 seconds for a basically stock oddy with a pipe/carb and 10 seconds for an oddy with a built Engine.
CO

Super cool.
I'm home now so I can play with the new numbers. Sound like you have a handle on it now.

I should be able to get some base line HP numbers as well using this data.

Once I get the sheet working we will add some info related to runs.

Thanks for taking the time to do it. Some guys are going to LS this weekend. Even though there not pilot /Odyssey. Maybe then do some runs. I know a pilot will be there also a ace 900 and some others.

So hopefully there reading and down load the app and post a comparison run.

If Fl takes his bad ass 670 it would be cool.

It would be real cool if someone would post this kind of info for a Pilot or even other machines using this app.
Also if you are actually able to figure out HP numbers from these runs that would also be cool because then I would be able to compare it to my actually homemade dyno info.
CO

You can get some HP numbers two different ways. I plan on doing both. You can use a online calc that will show you around 28 to 30. Use your times and weight.

What I'm going to do is use some vectoring to get a numbers than you can compare all.
The spread sheet will have time, distance, acceleration and kinetic energy than derive a hp number from that.

Should be able to get pretty far tommorow if nothing comes up.

Yes I plan on running my two pilots with the exception dirt runs. Just waiting on weather.

Can't wait to see what you come up with. Interesting.
CO

I'll post up a result once the site is fixed. My main computer says rut ru. May be the scum bags.
The base line results are flawed. And I solved two unknowns.

I may try another method to post for review and instructions on what you want to do.

Here's is a pic
Let me know which two fields you want to use and I'll do a corrected and move forward

I will let you decide what fields or data you want to correct or use.
In my opinion you are the best one to decide any math issues.
Pick one you decide will give us the best info.
It's probable that gps data is not 100% and that link to the youtube vid that showed data to a drag strip ticket is proof.
You choose which data to get us best info.
CO

I did make an data entry error. I'll correct in dm1.

If you scan the fields based on how the triangle works you can draw a conclusion.
I feel they messed up the ft per sec calc.
I look when scan for the ovious then investigate. Based on the triangle 3,30,90 stuck out like sore thumb
Based on basic math it can't add up.
The mph should be calculated on the 30 divide by 1.47 for feet per sec or 20. 47 mph.
So now I have to analyze each set of field to find which has a smaller margi of error. To do this I will factor in acceptation rates and refine to conclusion. I feel the app may be built. On mm2 and they messed up the conversion.
Do we want to stick to feet or meters.
Who likes what?
By chance you run a measuring tape at you run area. This may tell us what we need. Go back and measure footage,best guess and see how it matches up.
I may need to set time up a strip for pavement test.

When I do mine I will measure off set points. Compare to my vapor set up then run app.
My vapor is set up off of feet per sec and the triangle math. The tire setting at 5 psi was used measured in a circumference using a fiber tape. Then I used distance to dial in wheel dia. So I'm pretty sure it's close.

This is getting fun, for me anyway.
What you can do is go use a calc for trap times and hp and use what you think you have and run speed in 1/8 and 1/4.

I will also dig up an old file on what I came up with for hp on the ody. Based off of math from Gordon Jennings.

Here is a pic of a app that verified my number for mph.

This app is from a physics fourm.

1) Please stick to feet. Metric screws with my old mind. I'm old school.
2) Measuring tape at run area: I have a 50' tape and would have time today but I didn't really start and finish at the same spot all the time. It would just be a guess. I'll go out later and see how much hassle that is.
CO

OK adnoh I went out to measure the run distance.
Please keep in mind that there are no lines on that road to use as a measuring stick.
When I was a teenager in the late 1970's we did have lines painted on that road for the 1/4 mile drags we did out there but those lines are long since gone.
Therefore the exact run distance of each test is going to be plus/minus 50' each side of this number.
So the measured distance of these runs was 1257' each.
CO

a problem with most of the GPS apps is they only update 1/sec, unless you get something at least 10X/sec ideally 1000x/sec. I think the data is going to be all over the place.

OK what I did was use some of the data to get a corrected the best I can.
An Item to note is the estimated stuff.
Most likely since you did not travel the 1/4 mile it did not register.
What I did was use top speed and set it for 1/4 mile. since you almost ran that far.
Looking at the numbers not there seam to be a pattern that look ok.

Please let me know if you feel this is OK and I will move forward to the rest.
It does make the data entry a little more rough to do on a large scale. I decided to use the distance scale and took times from that and turn that into speed. So every one log both and post so I can enter for comparison.

I'm actually surprised by that chart because it shows my brothers machine only a second faster in the quarter mile. The app graph seemed to show a huge difference in the machines. Interesting because it felt a lot faster than the other two machines. Keep doing what you're doing, it's interesting.
CO

I certainly can't argue the point you make here.
All I know is it's more data than we have ever had on these machines and even if it is flawed how far out could it actually be ??
I think we are damn close but that's just my opinion.
CO

Hey adnoh I was just looking at that last chart you posted.
Something doesn't look right to me.
Take a look at the 1/8 mile and the 1/4 mile lines of Ralph's machine and CO machine.

My brothers machine shows 64 mph and 20.63 ft/sec
Mine shows 59 mph and 22.37 ft/sec

That don't make sense to me. How can the ft/sec be slower if a machine is running more mph than the other machine ??
CO

I probably messed up the whole thing. Ill try again
SORRY!
Maybe too many cold ones from lake?????