onthemove
Member
I spoke w/an engineer over at Scangauge today in reference to the accuracy of the unit. Notice how I always get and even numbered 10th of a second, never an odd. I asked why it doesn't give 10th's of a second but instead 2/10's. He said for a couple reasons. One, it's very demanding on the ecu for something like the scanguage to constantly request information and 2, there's not enough memory in the scanguage with all it has going on.
He told me it's optimistic to neutral at the start but at the finish, pessimistic, so in other words, starting at 0 might be off a tick making a recorded time look slightly better but whether you look at a 0-60, 1/4 mile or anything in between, the scanguage records time until the next data point. He said if I recorded a 12.6 second 1/4 mile run on the scanguage (I wish) it's a 12.5 to 12.6. Best way I can explain it. That makes sense because there's no doubt onthemove shits-n-gits a bit better with these smaller, lighter tires than he did with the crapho's yet I'm still getting a 5.8 0-60 on the one road, yet got a 5.8 on the slightly inclined road after the tire swap whereas before the swap, got a 6.0.
He told me it's optimistic to neutral at the start but at the finish, pessimistic, so in other words, starting at 0 might be off a tick making a recorded time look slightly better but whether you look at a 0-60, 1/4 mile or anything in between, the scanguage records time until the next data point. He said if I recorded a 12.6 second 1/4 mile run on the scanguage (I wish) it's a 12.5 to 12.6. Best way I can explain it. That makes sense because there's no doubt onthemove shits-n-gits a bit better with these smaller, lighter tires than he did with the crapho's yet I'm still getting a 5.8 0-60 on the one road, yet got a 5.8 on the slightly inclined road after the tire swap whereas before the swap, got a 6.0.



























