Hi,

I’ve spotted an oddity which happens while I’m freewheeling – sometimes if I’m driving downhill I’ll put the clutch in, take my foot off the accelerator and let gravity do its work. The engine speed falls to idle and instantaneous fuel consumption drops to around 1l/hour in my car (a 1.1l petrol Citroen Saxo).

If I’m going at say 50mph the calculated MPG will show around 225 – all is well and good. If I exceed approximately 55 to 60mph then the MPG will exceed 255 which is the maximum displayed value. However, when the MPG exceeds 255, the instantaneous fuel consumption then drops to 0, which can’t be correct because the engine is idling and must be using fuel.

To be clear, I’m not talking about coasting with the clutch engaged and my foot off the accelerator – this does cause the fuel status to show “open cycle – deceleration” and Torque to correctly show no fuel consumption. This issue happens when the clutch is disengaged and the engine is idling, but while I’m still travelling at speed. When it happens Torque will still show normal (i.e. blank) for fuel status.

The erroneous zero fuel consumption is present in the logs and the total fuel consumed does not increase when this happens, so it appears to be a calculation issue, not just a display issue.

Does anyone else see the same problem? Can I safely say this is a bug in Torque rather than a quirk of my car?

-Tom

Hi

It’s because the fuel used is so small it is difficult to accurately detect with several sensors in some engine configurations, so it’s simply pegged when the app says 255, the fuel use is put as 0

I will increase the ‘255’ to a larger value in the next beta version, though this does require careful testing before it can go live

Edit: done, ready for the next beta update