Jump to content

How to screw up checking our gas mileage...


Recommended Posts

Posted

Excuse my little rant here, but it annoys the crap out of me when I see people post their gas mileage and can't figure out why other are getting more than them. Yes, at times there could be a mechanical issue, but usually it's driver/owner error. So I decided to post a list of ways that you can screw up checking your mpg's. Here we go:

 

1. Not resetting your trip meter/mileage tracker when checking your mpg's. Your on board computer is constantly averaging your mpg's. To get an accurate number, clear it when you fill up and want to check it. If you don't, you're just getting an overall average regardless of how you drive during this fill up.

 

2. Drive aggressively. Accelerate hard from stops, pass full throttle even when you don't really need to, exceed all posted speed limits, brake at the last minute rather than coast to slow your speed, and do lot's of idling! That'll show that silly computer who's boss!!!

 

3. Start your truck, and let her warm up for a good, long time! Remember, you can actually achieve ZERO miles per gallon if you're really good at this!!!

 

4. Upgrade to larger tires, and forget about adjusting the tire size difference. That requires some math, and using the calculator in your smart phone. Who's got time for that???

 

5. Don't bother with putting a reasonable amount of miles on the truck while checking your gas mileage. 2 miles should do it. Just remember to keep the peddle mashed to the floor during this time. Otherwise, you won't be able to post how terrible your gas mileage is on forums!!

 

 

OK, I'll stop with all the extreme sarcasm. Listen guys, you can't do the things I posted above and get an accurate reading of what your truck is CAPABLE of getting mpg wise! If you do, you are making the conscious decision to impair the ability of your truck to get great mpg's. My truck is capable of a solid 21-22 mpg in 70% highway, 30% in town driving as long as I do my part. I could easily take that down to around 10mpg if I don't do my part, but how could I blame my truck for that? My point is, many don't understand how to get an accurate reading, or how to get the most out of their truck. If you don't, the fault lies with you. Feel free to disagree, but I hope some of you understand what I'm saying here. Rant off..... :)

  • Replies 32
  • Created
  • Last Reply
Posted

I hand calculate every tank and track it in fuelly. Best way to get an accurate reading.

 

Sent from Tapatalk App - Samsung S6

Posted

21mpg in my 1st tank on the 6.2L. Pretty impressive to me!!!

 

Mike

Posted

I hand calculate every tank and track it in fuelly. Best way to get an accurate reading.

 

Sent from Tapatalk App - Samsung S6

True, but the on board computer does a great job IF you use it correctly. Many don't.

Posted

True, but the on board computer does a great job IF you use it correctly. Many don't.

On board was .5 off for me most of the time. But, still decent.

 

Sent from Tapatalk App - Samsung S6

Posted

Nice write up, heavy on the sarcasm lol

Posted

On board was .5 off for me most of the time. But, still decent.

 

Sent from Tapatalk App - Samsung S6

How do you know you are not .5 off most of the time? I find it hard to believe that people can accurately, or at least more than the computer, calculate how much gas has been used and how much is left in the tank when they fill up. I know my truck says 26 gallon tank and I have put more gas than that in before and it was still running.

 

Unless you drive it till it stops and then put exactly 26 gallons in then it isn't completely accurate right?

Posted

I do everything noted above (plus) and I only get between 15 to 17 mpg in the New England (CT - not flat) area. I have a regular cab and only a few major options on this truck. I also have a bed cover. Travel very light all the time and have about 15,000 miles. Highways and back roads. I never seen anything over 17 mpg in this area when I checked. I have 3.08 rear end. Use different gas from different gas stations etc.. No towing. Left stock. I don't feel the gas mileage is that great with a 5.3 V-8 period.

 

My summer car 2006 MX-5 six speed manual (167 hp - 4 cyl) gets 34 to 42 mpg in the same area of travel and a lot of fun to drive. Don't see the gas station that often with this vehicle.

Posted

I live in a very hilly area as well and my 5.3 3.42 geared truck gets 19 to 20 mpg in the summer, 17 to 18 in the winter. I keep my truck in M5 when I am crossing over curvy mountain roads and on the really curvy ones I just knock it down to 4 the gear, truck is not going crazy shifting gears and gets better mpg's. I seriously think that a large portion of the population does not know how to manually calculate their gas mileage.

Posted

I got 22 on my first tank and that was mostly highway. I have averaged 21 and change on my second tank with a mix of highway/city...That' with a 6.2L

Posted

I agree how you drive plays the biggest part in your MPG. Mine turned 20K miles yesterday. Bought it Dec '14. It's a CC, 5.3, 3:42 4wd. Per my Onstar app the lifetime MPG is 21. I can easily drive through a tank and make it get 14 or even less.

 

You probably don't want to get stuck behind me though.

Posted

My '14 with a 5.3, 3.42 gears, 2.5 level, and 285/65/18 AT tires gets 17.5-19 driving in hilly western Pennsylvania. I hand calculate it every now and then when I fill up (always account to tire size difference too). I don't baby the throttle or mash on it much. I just drive..how I drive. Depends on traffic, time, and type of road.

 

All I can really say is: you're driving a TRUCK with a V8, if you're worried about MPG's you purchased the wrong vehicle....

Posted

How do you know you are not .5 off most of the time? I find it hard to believe that people can accurately, or at least more than the computer, calculate how much gas has been used and how much is left in the tank when they fill up. I know my truck says 26 gallon tank and I have put more gas than that in before and it was still running.

 

Unless you drive it till it stops and then put exactly 26 gallons in then it isn't completely accurate right?

Hand calculate is way more accurate, it's simple. Reset the trip when you fill up (first click of pump at same station). Drive until you feel the need to fill up again. (First click again). Take those gallons and divide the trip miles, and you have your mpgs. Reset trip and repeat.

 

Gas pumps are very accurate on their output. I know there is a little variable in where the pump shuts off, but if you use the same station, it's best.

 

Sent from Tapatalk App - Samsung S6

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   3 Members, 0 Anonymous, 1,554 Guests (See full list)

  • Latest Articles

  • Posts

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...