Hi

The HP and Torque readouts require you to keep accelerating until they display a value, the readings will be invalidated if you:

a) Allow a significant deceleration between gear changes
b) Don't accelerate to at least 70-75mph - as most speedo's over-read by at least 4mph.
c) Don't have a reliable GPS signal (Samsung handsets appear to have exceptionally poor GPS implementations)

The Eco widget works with the OBD bluetooth module. Can you post details of the bluetooth adapter module you are using? Thanks.

Hey Guys,

Ian thanks for the hard work you are putting into your app (and support too)!

Does the 0-100km/h time start automatically, as long as you accelerate from a dead stop?

Also, does this go on the OBD wheel-speed sensor, or only the GPS confirmed speed?

I have gone over 100km/h but never got a reading (or should i do as you suggested and just continue until there is a reading?).

Thanks again ey 😉

a) Allow a significant deceleration between gear changes

I've seen the time to speed and time to distance calculations do this if I take too long to shift. This is not the problem I'm seeing though. Accelerating past 100 kph they are still showing the ellipses. They only switch to Xs when I let off the gas after getting past 100 kph.

b) Don't accelerate to at least 70-75mph - as most speedo's over-read by at least 4mph.

My speed is reading 7% fast, but I had assumed those parameters were looking at the vehicle reported speed, not the GPS reported speed. I will try it again this afternoon and see if I see any difference considering GPS speed.

c) Don't have a reliable GPS signal (Samsung handsets appear to have exceptionally poor GPS implementations)

I've got the Motorola Droid. Sometimes it takes awhile for the GPS to get a lock. Once it is locked, it maintains a good lock.

The Eco widget works with the OBD bluetooth module. Can you post details of the bluetooth adapter module you are using?
The bluetooth module I am using is the OBDKey from KBM Systems:
http://www.obdkey.com/

Hi thanks for getting back, it seems you may have hit some odd bug with the eco widget, so I'll have a look at that before the next update

On the accelerating to 100kph, yes it will display a value when you stop accelerating, but if it then changes to an X then you didn't reach the required speed (ie: you didn't actually hit 100kph) according to your vehicle OBD.

For the widget OBD is used over GPS as the reported speed from the ECU is very accurate and updated faster than GPS.

However, your actual speedo dial is deliberately calibrated to read about 5% higher than it should, even though the ECU knows the correct actual speed :-), hence accelerate to about 70mph/110kph and you should be fine

The speedo reads the OBD speed. The OBD speed reads 5% fast, which is a source of frustration because it is not deliberate and only the dealer can change it.

In any case, to be safe, I verified yesterday I had accelerated well past 100 kph on both the OBD and GPS sources and it still went to an “X” after letting off the gas. So as of this point, the 60 mph, 100 kph, 1/8 and 1/4 mile times, HP, and Torque have never successfully registered a value. I even tried it in my roommate’s Volvo with no success.

I'm afraid I have to disagree regarding the OBD speed.

The OBD speed as reported from the ECU is always well within 1% of the actual speed when measured from GPS (though this is not the case if you have different diameter wheels on the vehicle to standard).

All the diagnostics in the car read the actual values, not 5% higher and not 5% lower. Otherwise there is no use in having a diagnostic interface.

The over-reading speedometer is deliberate. This is standard through nearly every manufacturer. It is done at the dial end and can be changed by the dealer. To save any ambiguity on the matter, Torque uses the direct, un-tampered with, actual value delivered direct from the ECU for speed measurements.

I will have another look at the 0-60 code just in case there is a bug, however the only reason why a run would be invalidated (with an 'X') would be due to significant deceleration, or not reaching the required speed to provide accurate readings.

I think there are two separate discussions here.

Related to the reported bug:
By all means of speed reference, I have been unsuccessful in getting the above listed widgets to work. The timing widgets do not go to an X during shifts, they go to an X when I let off the gas after passing 70 mph by all sources of speed data.

It appears that the start conditions work properly (vehicle stopped results in widgets saying “Ready”). It appears that the invalidate conditions work properly (not failing during reasonably quick shifting, failing when letting off the gas). What does not appear to be working is the successful end conditions (the 60 mph test does not complete when getting past 60, the 100 kph test does not complete when passing 100 kph, the 1/8 and 1/4 mile tests do not complete when passing 1/8 or 1/4 miles. I have also never seen the torque or HP widgets work at all.

So it seems that whatever is causing the timing widget to fail is related to the successful end conditions. What parameters go into that? Does it make assumptions about on-board phone sensors, such as accelerometers? Does it make assumptions about receiving data from PIDs that may not be present on all vehicles?

Unrelated to this bug:
My speedometer is digital and reads exactly what the OBD speed parameter reads (rounded to an integer value, of course). It is, the OBD speed that is in error. The PCM determines speed by counting wheel revs and converting it to speed using a stored “revolutions per mile”. As far as I can tell, this can only be changed by the dealer flashing the PCM on my car. I ran a few numbers on tires I have had installed on this vehicle. The variability in reported speed due to tire wear is nearly 2.5-3%. With this taken into account it seems that at best my OBD speed is off by 4% and at worst off by 7%.

I too have this bug. I have accelerated hard past 60 and on to 80 and still it won't register a time, or a distance.

Okay could be a bug then - I'll have a look at that today.

Checked it and it appears to be a bug. Also units appear to not be updating correctly as well.

A fix will be out sometime today, sorry about this.

Hi

Found the problem a new version is uploading now, fixes for mph/kph units problem and the HP/Torque/0-60/etc reading being faulty.

tested update, 0/60 & 0/100 now working didnt get a chance to test the rest. hp now working too.
thank you
keith

Timers working for me as well. Will report back on HP and torque when I get a chance as well.

Ah. I have a couple of comments after reading this thread. First of all, if the timers are using the OBD ECU speed, those of us using different tires will need to have an adjustment factor. There a re a couple of ways this could be handled. The uses could input the stock tire size and the "as used" tire size, or Torque could use GPS to learn the the difference. All it would take is a low pass filter with a time constant of several minutes or so.

Also, it seems that my best times are lost after I exit Torque. I'd like Torque to remember my top 5 or so.

Thanks for a great product.

geosynch

Same here:( never worked, and accelerated to 160 km.h...

Hope this can be fixed 🙂

EDIT: whoops didnt see page two:p