that's unrealistic. you're probably ~3.9/4 secs
I'm thinking the car didn't really go 3.2-3.3 secs, hence my use of the word "allegedly."
But it
is my sense that every tenth-of-a-second-point-in-time is a significantly different data point than it's neighboring one-tenth-of-a-second point … which is to say that the difference between 3.2 secs and 3.5 is quite large and the difference between 3.2 secs and 3.9/4.0 secs is simply enormous.
If I was forced at gunpoint to guess what an OBD tool's variance from the truth would be, then I would toss out a "WAG" of 0.2 to 0.3 secs differential (and would point out as well that the 0.2/0.3 secs deviation for the device would be expected to run "both ways" - sometimes understating times; sometimes, overstating them).
I'd like to know how a phone-app-OBD-device system comes up with time and speed data for 0-60 computations.
If anyone knows how it works, I'd really love to be educated.
I would
think (but am just pulling this out of thin air) that devices like Torque don't do much measuring, but rather they would (or should) rely on measured data stored on the car's computer. It would make a lot of sense to me if the phone app performed only simple calculations based on data stored on the car's computer, with the only function of the OBD unit to be transfer of the data between car and phone.
If neither the OBD unit nor the phone app are measuring time or speed or correlating the two, then I would think the error in 0-60 reports would be based on either or both of (i) data rounding limitations in the data the app gets from the car's computer (i.e., the more decimal places of stored time and speed data available to Torque from the car's computer, then the more accurate Torque's displayed 0-60 should be) or (ii) the car computer's method of determining speed or (iii) some combination of those rounding and measurements by the car.
If that was/is they way this stuff works, then Torque would be one part simple calculator (of the number of secs passing between to speed points reported by car computer) and a bigger part graphic interface with decorative themes. If - IF - that is the way these things work, then time lags between transmission of data between car computer and phone app through the OBD device shouldn't introduce more error. [And it would also be true then that accuracy shouldn't vary much between one phone-app-OBD-combination and the next.]
Finally, I know what a cynic would say about the data provided by tune sellers or some forum member's reporting of speeds, but there is a difference between cynicism (which can be funny but often not useful) and healthy skepticism (which allows for decent two-way communication and pursuit of better understanding). I much prefer skepticism ...
- I am somewhat skeptical of the Torque 0-60 report of the 3.2/3.3 secs because I am only guessing at how the app and other components work.
- Also am somewhat skeptical of 0-60 times reported by tune sellers like APR and some forum members, but my skepticism runs more along the line of (i)sellers cherry picking data that is uncommon and (ii) for some forum members outright fibbing or (iii) as someone else has said in these threads, for some members to report speeds significantly aided by wind and/or downslope pulls.
In another post reply that I added to one of these threads, I shared information from APR reporting it's stage1 tune being measured at 3.8 seconds for 0-60mph. If that speed has been achieved in truth (which I tend to believe), then it's not a stretch to think an APR stage2 car might be doing 0-60 in 3.5 secs.
WOULD LOVE TO BE CONTSTRUCTIVELY CRITICIZED/EDUCATED with data/research/expert opinion or thoughtful weekend warrior input!