Jump to content

Recommended Posts

Posted

Sounds very normal for a HD gasser running empty.  I average around 9 - 9-1/2 mpg with my 3,200 lb truck camper in the box with a 6.0 gasser.

Posted

I have a 2020  like yours. Under 60 mph, flat road, no wind, and cruise control I can get a little over 20. Interstate from home in Louisiana to Houston Tx on i10 @ 70mph average about 18. Any headwind will kill it. It does not like town driving either. Pulling my 8500lbs camper at 70 is about 8.5mph. Last time out had a 15 to 20 mph headwind at that was down to 6.5. It’s not much worse than my 1500 4x4 5.3 not towing.

Posted

I get around 17.5 on the highway doing 65-70 on rolling terrain when empty. With my 1800 lb popup camper, I get 14.5 to 15 on the same terrain same speed.  I have the stock 18” wheels and Michelin tires. No suspension mods. 

Posted

My general experience is 11 to 12 in city driving, 13 to 14 mixed driving, and around 16 highway driving around 75.  I have gotten as low as 5.5 towing around GCW. 

 

#iworkforGM

Posted

I have a 22’ ccsb 4wd. I get between 13 & 14 city driving and 17 +/- on the highway. Towing our travel trailer I’m around 9.5, my bass boat about 12. All combined, I’m probably right around 14 average across the life of the truck. 

Posted

With the leveling kit and 35" tires on 20x10"s I generally get around 11-13.  Less when towing my 30 foot camper but that is to be expected.  As far as the 17-20 mph statements - mine couldn't hit that in neutral going 100% downhill.

Posted

What are gas prices like in everyone's area?  My local gas station has gone up 20 cents in two days and was at $3.83/gallon.  This is a local town gas station...not sure what the higher ends are charging right now.....

Posted
10 hours ago, CT Chevy Connoisseur said:

With the leveling kit and 35" tires on 20x10"s I generally get around 11-13.  Less when towing my 30 foot camper but that is to be expected.  As far as the 17-20 mph statements - mine couldn't hit that in neutral going 100% downhill.

I had a trip mileage of 24.1 returning from Mt Rainier to South of Seattle last Fall. Quite a bit of coasting downhill in the first third of the trip and a lot of 50 mph driving. 

Posted
12 hours ago, Another JR said:

I had a trip mileage of 24.1 returning from Mt Rainier to South of Seattle last Fall. Quite a bit of coasting downhill in the first third of the trip and a lot of 50 mph driving. 

 

What about the trip up?  To get a real average you need to check every tank and average out the rare downhill coasting trips and 40mph headwind uphill trips.

Posted
3 hours ago, MORSNO said:

 

What about the trip up?  To get a real average you need to check every tank and average out the rare downhill coasting trips and 40mph headwind uphill trips.

I was simply responding to the person I quoted, who said he didn’t think his truck could hit 20 mpg even coasting downhill. I understand I consumed extra fuel climbing on the way up. 

  • Thanks 1
Posted (edited)

Picked up the truck from the dealership with a full tank of gas, and drove 360 miles from Murray, UT to Winnemucca, NV.  98% of the trip was on the highway with a max speed of 75mph. Filled up, but didn't top off (like TFL does), because I wasn't sure what the dealership did.  Hand calculated fuel mileage as 14.19mpg.  Clear weather, not much wind, temps in upper 40s.

Next day Winnemucca, NV to Roseburg, OR was 450 miles of two lane roads. Nevada speed was just under 70,  Oregon speed limit was a combination of 65mph and 55 mph. Climbed through the Cascades with the highest ascent being 6,100-ish feet, descending into Roseburg which is about 500'.  Fuel mileage was 15.6mpg hand calculated (no top off).  Weather was good until the west sice of the Cascades where it was raining pretty good.

Both legs of the trip I used the cruise control as much as possible (I suck at maintaining a consistent speed without using cruise).

 

The key to excellent fuel mileage is to drive slow, and only go downhill with a tail wind. :cheers:

I'm very happy with the fuel mileage.  If I can average 7mpg when pulling the 5th wheel, I'll be ecstatic. 🤞

Edited by sheath
forgot weather conditions from Winnemucca to Roseburg
  • Thanks 1
Posted (edited)

My lifetime avg so far 9k miles is 13.6 I think. Haven't been on any really long highway drives/road trips yet, so mostly just running around at work. 

Edited by apresler
  • Thanks 1
  • 3 months later...
Posted

geez, I don't get anywhere near any of those numbers!!! I hover around the 9-10 mpg mark empty!!! Guess thats what short trips to and from work will do do you (10 miles one way) 

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

  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...