lightfoot
12-22-2007, 09:42 AM
I had noticed that my ScanGauge II shows 0.2gph in my 2003 Subaru Outback MT even when coasting NICE-OFF (it also shows 0.2 gph when coasting NICE-ON). But I was never sure whether this affected the Average MPG figures.
I contacted ScanGauge and was told that the Subaru ECM might be holding the 0.2gph figure when the engine was off, but wasn't given a workaround.
Yesterday I had to stop several minutes at the steam train crossing in town, so I shut down the ICE and sat there ICE-OFF with the ignition on. When I started up again I noticed that the Avg MPG was horribly low, <10mpg.
So today I did a test. I drove 2.3 miles, at which point the Avg MPG reading was 22.1, stopped, keyed off the ICE, turned the ignition back on, and sat there for several minutes ICE-OFF without moving. Here are my Avg MPG figures:
0 min 22.1
1 min 21.3
2 min 20.6
3 min 19.8
The fuel consumption reading showed 0.2gph throughout.
This means the ScanGauge can't distinguish between idle and ICE-OFF in my Subaru, so I can't see whether it is helpful to coast NICE-OFF or to go ICE-OFF at lights, etc.
Any suggestions on how to work around this? Would the new firmware help?
I contacted ScanGauge and was told that the Subaru ECM might be holding the 0.2gph figure when the engine was off, but wasn't given a workaround.
Yesterday I had to stop several minutes at the steam train crossing in town, so I shut down the ICE and sat there ICE-OFF with the ignition on. When I started up again I noticed that the Avg MPG was horribly low, <10mpg.
So today I did a test. I drove 2.3 miles, at which point the Avg MPG reading was 22.1, stopped, keyed off the ICE, turned the ignition back on, and sat there for several minutes ICE-OFF without moving. Here are my Avg MPG figures:
0 min 22.1
1 min 21.3
2 min 20.6
3 min 19.8
The fuel consumption reading showed 0.2gph throughout.
This means the ScanGauge can't distinguish between idle and ICE-OFF in my Subaru, so I can't see whether it is helpful to coast NICE-OFF or to go ICE-OFF at lights, etc.
Any suggestions on how to work around this? Would the new firmware help?
