Jump to content

2014+ Gas Mileage (MPG) Topic

BringTheRain403
 Share

Recommended Posts

mdes0 Enthusiast

mdes0

Posted
Posted

First highway trip with the Denali 6.2:

 

IMG_20140222_131712_036.jpg

 

I have 34" tires and have not corrected the computer. Adjusting for the 7.4% error the actual numbers are 17.3 MPG at a 68 MPH average.

 

This was a round trip from the Seattle area to the top of Snoqualmie Pass (3000 ft elevation) and back again. The engine is still new (fewer than 300 total miles).

 

I'm pretty happy with that. It's rated at 20 for the highway, I've taken off the front airdam, lifted it 2" front, 1" rear, and put much bigger and heavier 34" tires on it.

 

IMG_20140222_110255_144.jpg

 

On flatter ground it should easily be in the 18-19 range, mountain passes kill your mileage. So I think that's pretty good considering what this engine is capable of when you put your foot down.

What size tires did you go with? Any rubbing?

My gas milage has been in the crapper since the recall flash. I'm lucky to see 17 on the highway! Seems to get better mileage under 60.

  • Replies 1.6k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Natek
Natek

I think if I was a salesmen I would research the products I would be selling. I wouldn't like it if a customer came in knowing more than me.

nibael
nibael

Mine gets pretty bad mileage at 180 mph. Maybe I should get a bed cover.

Eddie 70
Eddie 70

This was taken last week when I filled up. So far I have put this many miles on the truck. Hopefully it stays like this. We will see.  

Posted Images

fondupot Senior Enthusiast

fondupot

Posted
Posted (edited)

That average speed screen is nice. I wish my SLT model had that. Must only be on Denali.

Edited by fondupot
Dnt Senior Enthusiast

Dnt

Posted
Posted (edited)

That average speed screen is nice. I wish my SLT model had that. Must only be on Denali.

I saw that too, I was also wondering if the DIC has an option for the average mph on the lowly SLT or is this Denali only?

Edited by Dnt
dfwvtxman Enthusiast

dfwvtxman

Posted
Posted

Bought an 2014 Silverado LTZ 2 wheel drive. Thru 3 tanks I'm getting anywhere from 10.8 thru 13 mpg. Mainly city driving yes, but a couple 75 mile city/highway combinded trips thrown in there. Got the highest MPG during the 1st tank., Then had the recall throttle body flash done along with 2 other recalls. Since then the truck does seem to drive smoother with maybe a little transmission gear seeking now and again. But the MPG has gone down. And I've been babying the throttle trying to keep it in V-4 as much as possble.

 

Took it back to the serivce shop that did the recalls. The service guy just said it's due to bad gas. Well 2 tanks later and no better. He needs the truck for an entore day to go thru it but won't give a loaner. I feel I should be averaging at least 16.. But closer to 18 at lowest. I have an 01 jeep with dana 44's and 35 in tires that gets almost this good of MPG.

 

Anyone else having this issue?

jmontz32 Enthusiast

jmontz32

Posted
Posted (edited)

2014 sierra 4 wheel drive with 2" level and drive it hard....still avg 20 mpg

Edited by 4x4offroad
  • Like 1
fondupot Senior Enthusiast

fondupot

Posted
Posted (edited)

I saw that too, I was also wondering if the DIC has an option for the average mph on the lowly SLT or is this Denali only?

 

I don't have it in my SLT.

Edited by fondupot
Dnt Senior Enthusiast

Dnt

Posted
Posted (edited)

 

Sorry .. it's the 5.3 And Chevron gas.

above results from my 2014 Crew Cab SLT Z71 4x4 5.3 3.42 with 20in all terrain tires......Set your DIC to the 25 mile range and reset it so you start with a fresh average, now go for a a minimum 25 mile drive watching the DIC mpg meter adjust your driving habits to produce great gas mileage and never return to your wicked fuel wasting ways now that you know what you were doing wrong. HEAL THY EVIL DEMON above results are from intense training watching the DIC meter. As Arnold would say Yuuooo can dooooo it

Edited by Dnt
dfwvtxman Enthusiast

dfwvtxman

Posted
Posted

attachicon.gifIMAG1029.jpgattachicon.gifIMAG1030.jpgattachicon.gifIMAG1031.jpg

Set your DIC to the 25 mile range and reset it so you start with a fresh average, now go for a a minimum 25 mile drive watching the DIC mpg meter adjust your driving habits to produce great gas mileage and never return to your wicked fuel wasting ways now that you know what you were doing wrong. HEAL THY EVIL DEMON above results are from intense training watching the DIC meter. As Arnold would say Yuuooo can dooooo it

Go where and do what?? Speak in english man..lol

  • Like 1
Dnt Senior Enthusiast

Dnt

Posted
Posted

Trying to remember how to do the setup. I have a Sierra but I think the Silvy is the same. On the steering wheel controls right hand side punch the < button that should open the display on the center of the dash between the tach and speedometer scroll to info and press the center button on the steering wheel right hand cluster this should get you into your selection screen now scroll to the fuel mileage one and once on there you can press the > button to be able to scroll between the 25 50 and 400 ranges.

Dnt Senior Enthusiast

Dnt

Posted
Posted

It is very interesting how a small change in driving habits can affect the fuel mileage tremendously just makes you very conscious of how you are moving your nearly 6000lbs of weight (Your truck with all your stuff in it) around. I still have to punch it now and then just for fun I left some long black streaks this morning out of the car wash sum bich will raise heck with the traction control turned off LOL but it has also been fun to see what I can get out of it as far as mpg.

Dnt Senior Enthusiast

Dnt

Posted
Posted (edited)

Totally Unacceptable, GM will have to give us what we want. Where is my customer service girl at? haha

Edited by Dnt

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • 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   4 Members, 0 Anonymous, 1,640 Guests (See full list)

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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...