Hi

Suspected this was a similar issue to the average distance not updating, and it seems to have been - I've just released 1.6.2, which hopefully fixes this issue for you!

Taken 3 trips with v1.6.2

Two seemed to be giving high readings. I logged one of those trips. 45 dropouts out of 605 time steps. Seems better, but not fixed. What seems to be the issue?

Think it can be fixed?

Hi

You shouldn't be getting dropouts - can you post what adapter you are using and the phone device as well - once Torque has started logging it should never 'miss' any readings from there (i would expect it not to log at all, due to the way the app is built)

If it is, then it's one of the symptoms you can get with a clone adapter. I would definitely check, at the end of a trip the 'Error Count' numbers in the 'Adapter Status' screen - if these numbers are nonzero, then it means that the app has detected instances of the adapter not doing what it should

Another thing it could be is a bad electrical connection to the diagnostic socket (such as a pin intermittently making contact, or breaking contact every time you go over a large 'bump' - typically this will be picked up by the app in the error count section though)

If those numbers are 0, (it's important to check them at the end of a trip, not the start) then it could be that the app has been 'swapped out' of working memory by the phone (android can do this if the device hasn't much ram, or you switch between a couple of big applications like navigation, etc)

Lastly, on some phones, multiple bluetooth connections can be an issue (handsfree/torque/music streaming) - there are issues with some vendors drivers that mean you may have issues using more than one bluetooth connection at the same time. For testing, it might be handy to temporarily disable the other connections (unpair them) and see if that makes a difference

When I said dropout, I meant the "Fuel used (trip)" figure didn't change between triplog timesteps even though there is a nonzero number in "Fuel Flow rate/minute". I don't mean the adapter is dropping out all data. The problem seems to be in Torque, not the adapter/phone.

I'm using a OBDLink adapter and an HTC G2 (Desire Z).

Here's a picture of a recent triplog where I calculated 'Fuel Delta per time step; using "Fuel used (trip)" I also calculated the fuel delta per time step using the Fuel Flow and the raw MAF data (assuming 14.7:1 A/F ratio and no fuel trim adjustment).

For the full trip Torque indicated 55mpg.
Using Fuel Flow, I got 37.3mpg.
Using raw MAF, I got 35.9 mpg.

I have similar issue. (newest version, enhance mpg calc turned on on/off).

On moderate load (0-20%) Torque does not regiter consumption. Only when gas pressed firmly. That is why consumption is very low (metric system)

Hi!

That spreadsheet helps a lot, thanks! - if you have the time, is it possible that you could include the 'throttle position' sensor as well (if it is supported in your vehicle) - that will give me the full picture of what's going on

Here's a snippet with the TPS also logged. Closed throttle is ~15%.

Torque mpg = 80.7
Fuel Flow mpg = 51.2
MAF mpg = 40.9

Do you need any more info?

Bueller? Bueller? Bueller?

Same thing happens in a 2006 Subaru Impreza. 270 out of 815 time steps give no fuel flow when in reality, fuel flow is present (according to "Fuel Flow" calculation from Torque).

Torque indicated mpg = 55.6
mpg using fuel flow = 41.9
mpg using MAF and sensors* = 36.3

Adapter Error Count = 0

HTC G2 (Desire Z)
RAM Used = 142MB
RAM Free = 172MB

*Using logging for Accord sensors, hard to account for A/F changes and decel. fuel cutoff.

Think this bug will get fixed in the next release?

Hi

Think I've got this one now - there were 2 methods used for fuel detection - if you have the relevant sensor in your vehicle, it should now use that solely (and ignore the other method) - when you get 1.6.10 make sure you have Enhanced MPG Calculation enabled and see how you get on with that version. Hopefully it will be working correctly for you.

If not, let me know - there is one more thing I can do to sort this out (and it will definately fix this issue, now I know where it is)

(the screenshots you posted were very helpful, thankyou)

Took a trip in the 2006 Impreza with v1.6.10. Problem still exists. Torque reported 118 mpg on a 6 mile trip. 323 out of 525 time steps showed 0 fuel used when nonzero fuel flow was reported.

I'll give it another go in the morning and report what sensors the Impreza has.

Second trip shows the problem hasn't been fixed. >100mpg for the trip

List of sensors on the Impreza

Number of trouble codes and I/M info
Fuel system status
Calculated engine load value
Engine coolant temperature
Short term fuel trim - Bank 1
Long term fuel trim - Bank 1
Intake manifold pressure
Engine RPM
Vehicle speeed
Timing advance
Intake air temperature
MAF
Throttle position
O2 sensor present
Bank 1, Sensor 2: O2 and STFT
OBD Standards
O2S1 eq. ratio and/or current
O2S1 eq. ratio and/or voltage

Protocol used is ISO14230 KWP Fast
PIDs/sec
Avg = 5.5
Max = 7.5

Any less leads the problem?

It seems odd the inst. mpg reading is correct, but the fuel flow doesn't get counted!

I turned Enhanced MPG off and finally got some reasonable trip mpg numbers. Should be pretty simple to find out what is fudged up on Torque's side. Made any progress?

Without enhanced mpg, the fuel used figure is far too low... on part with what would be reported if I had enhanced mpg enabled.

Any updates on getting this bug fixed?

Hello,
I am having similar issues. One thing I noticed is that the mpg average is recalculated after i turn off the engine. A reading of 6.5 lpk goes up to 8-9-10, after turning off the engine. Any idea what this is all about?