i Phone Dyno, New & Improved with "Dynolicious" Pix

[ronnyek]

this app cannot possibly be that accurate... number one iphone accelerometers were designed for orientation, not retrieving gforces etc... and number to I can personally say with experience to back it up... there must be a lot of voodoo, because in my testing (I'm an apple dev)...

Location Manager does infact update sometimes as little as every 2-3 sec with location and speed... theres no such thing as getting values real time on it. (at least as far as I've been able to tell.)

[rocketpop]

I put mine in the cup hold (extra idrvie one), the mounting instruction does say it has be perfectly vertical, can be ant any angle from flat to straight up and down, just can't be skewed left or right. I hope that make sense.

[Noize]

Originally Posted by Bizall

If you look in the picture, it's for a 2003 Mini Cooper S. :wink:

I've drag raced more FWD cars than anything. If you pull a 2.1 on street tires, you're doing well. 2.2-2.3 is average. 2.5 is pitiful. 3.47, though? That's asinine. I've never seen a real car 60' that slow, hence something is wrong with that ap.

[tkbr0wn]

Originally Posted by Noize

I've drag raced more FWD cars than anything. If you pull a 2.1 on street tires, you're doing well. 2.2-2.3 is average. 2.5 is pitiful. 3.47, though? That's asinine. I've never seen a real car 60' that slow, hence something is wrong with that ap.

Who said he was trying to do a fast run. Maybe he just accellerated from the stop light like he normally would.

[Charles1]

Originally Posted by Noize

I've drag raced more FWD cars than anything. If you pull a 2.1 on street tires, you're doing well. 2.2-2.3 is average. 2.5 is pitiful. 3.47, though? That's asinine. I've never seen a real car 60' that slow, hence something is wrong with that ap.

Many ppl just testing on the street. I ran a 17.5 in my V3 135i. What does that make me... Pitiful?

[Charles1]

Originally Posted by ronnyek

this app cannot possibly be that accurate... number one iphone accelerometers were designed for orientation, not retrieving gforces etc... and number to I can personally say with experience to back it up... there must be a lot of voodoo, because in my testing (I'm an apple dev)...

Location Manager does infact update sometimes as little as every 2-3 sec with location and speed... theres no such thing as getting values real time on it. (at least as far as I've been able to tell.)

I disagree it is proving to be quite accurate. What does Location Manager have to do with anything?

Have you even test the app or are you just posting your thoughts?

Sent from an iPhone.

[E82tt6]

Originally Posted by Noize

I've drag raced more FWD cars than anything. If you pull a 2.1 on street tires, you're doing well. 2.2-2.3 is average. 2.5 is pitiful. 3.47, though? That's asinine. I've never seen a real car 60' that slow, hence something is wrong with that ap.

I agree. I've done a few tests, and it doesn't seem that it can register off the line acceleration well at all. I did some tests with the phone taped in place so it wouldn't move, and was getting 60' over 2.3s, even with what felt like perfect launches on sticky tires. 3k clutch drop yields minor tire slip through most of first gear, feels just about perfect to me, but 60' varies between 2.3 and 2.6. Furthermore, if you artificially place 1G on the iPhone (turn it straight up, after calibrating horizontally), it WILL NOT register a 60' faster than 2.1s, no matter what.

I'm inclined to think that this thing needs some fine tuning...

[E82tt6]

Found a better way to mount the phone, per E90 post.

Open up the armrest, and lay the phone flat in the back of the cubby. If you close the armrest, the phone will be held perfectly still. Did a quick run with this method, and it seems a bit more accurate and consistant. This was a badly bogged launch, so the 2.3s 60' seems realistic, compared to the 2.3-2.7s 60's I was getting with perfect launches.

Attachment 10185

Attachment 10186

Attachment 10187

[JB135i]

http://dynolicious.com/index-5.php

Seems they are aware of the calibration issues some are having.

Interesting statement they make about the variability of iPhones too. Not sure why a device such as this should vary at all. Given all the hype in the past about stability and consistancy of Apple products.

Looking foward to a fix, my 1st gen iPhone will not complete the calibration (face down step).

[rocketpop]

Just in case you missed it on thier site, you can delete run and cars but swiping your finger across the run or car and the delete button will appear.

[adrean8j]

Me
1974 Human American
Max Speed: 3.6mph
Max Acceleration: 0.68 G's
Peak HP: 2 HP

[135iPSU]

Originally Posted by adrean8j

Me
1974 Human American
Max Speed: 3.6mph
Max Acceleration: 0.68 G's
Peak HP: 2 HP

not bad, i ran .7 G yesterday, nearly ripped the sole off my shoes

[Jumpman]

Woah, slow down there mister! Where's the fire? :biggrin:

[JB135i]

Originally Posted by adrean8j

Me
1974 Human American
Max Speed: 3.6mph
Max Acceleration: 0.68 G's
Peak HP: 2 HP

What intake and exhaust you running?

Gross, but I thought it was kinda funny, not very, but kinda.

[adrean8j]

Intake: Marlboro Menthol Lights
Exhaust: Popeye's Fried Chicken

LOL...there...now its funny...LOL

[R32]

i emailed their customer support asking about gps and lap timing. they said they are working on it and hope to bring it soon!

[WAY]

Anyone tried this on the drag strip? That's one way to see how accurate it is.

[xa-coupe]

Originally Posted by rbernard1984

so if its not just me whats up? any solutions yet? I'll have to install it on my wifes phone and see if it works.

any updates on this ? I downloaded the app about 1/2 hour ago on a new 3g Iphone and it's stuck at the same point.

[gio]

I just downloaded this app. I was really excited about it but unfortunately it was raining all day today so I didn't really get to try it out as much as I'd like.

My first impression is that it isn't anywhere near as accurate as it claims to be. I frequently would get resuls saying I had 600+ whp and max speeds of 125+ mph when I never went higher than 65mph.

I have the calibration problem that others have been seeing (it never completes the 4th calibration step) so maybe that is why I've been finding it is so inaccurate. If this calibration issue isn't fixed, I'm going to complain and try and get my money back. I'm guessing it's probably why numbers are all over the place (the other possibility is the rain, perhaps it can't deal with severe wheel hop).

Because of the rain, I think I was able to get one decent launch. I've posted the results below. It still seems a little bit suspicious. I doubt my 0-60 was anywhere near 5.11s. I don't think I actually hit 85mph (probably no more than 70) and of course I couldn't have had 1.52g of acceleration at any point. Because of the wet pavement I had a significant amount of tire spin in both 1st and 2nd gear and a ridiculous amount of wheel hop (I always have a lot of wheel hop when launching in 1st gear, even on dry pavement, is this normal??), so I'm guessing my 0-60 was realistically in the 6-7 second range.

Hopefully it will be dry out someday and I can try this again.

[xa-coupe]

I'm going to guess that the calibration step is critical to it's accuracy... which makes the issue more annoying. It's only $15 AUD but I would like it to work !

[JB135i]

I got this email from Dynolicious yesterday-

Sorry for your frustration. We have provided the update containing the calibration fix to Apple. As soon as they review it, it will be made available for download. It's hard to say how long this will take, but it should be about a week, maybe less.

It's cool they are on top of this, kudos for the fix so soon.

[Charles1]

A must see: