Jump to content

Recommended Posts

Posted

I have been getting better milage as the truck breaks in as other members said would happen

Posted (edited)

2014 Silverado Double Cab 4x4 5.3L 3.08 gears......

 

I am getting 18 mpg city & 23 mpg Hwy....

 

Screenshot 2014 07 15 20 45 45 (2)

Screenshot 2014 07 15 20 48 34 (2)

Edited by meanjoe
Posted (edited)

 

Not sure where it went...there was an 89 octane thread not long ago...lost it. Anyway. There is supposed to be a benefit to running 89 octane due to differences in LTFT and reduced knock retard. Before taking this trip I had run nearly 4 tanks of 89 octane. Turned 11k miles on my trip to do a kid exchange. Trip was 628 miles each way in mountainous terrain (elevation on trip ranged from ~40ft to ~1900ft) and run on 89 octane. On the way out in light rain I averaged 67 mph and 21.8 mpg while exceeding 80mph once. On the way back 68.4 mph and 20.7 mpg while exceeding 80mph six separate instances up to 90. Basically in a hurry to get home. Driving patterns roughly the same no matter the octane and no increase in fuel economy. btw 5.3, 4x4, CC, std bed, 3.73

Edited by calgator73
Posted (edited)

I just filled up before I towed a 2300 pound trailer the other day, I went a total of about 140 miles trying hard to be as easy on the pedal as I could, but the best it would give me is 12.2 mpg.

 

They have it geared so you really cannot feel the trailer behind you - maybe if you gunned it from a dead stop or tried passing at highway speeds I guess maybe then you would notice it, but just normal driving I didn't even feel it behind me. They have it setup for performance, which is good - but wow, I was surprised how much more fuel it uses with just a relatively light trailer.

 

I wonder, does anyone know if there is an easy way to manually switch between V4 and V8?

Edited by NoProblem
Posted

I haven't posted in awhile because we are moving. Here is a update on the mileage while towing a 7500lb loaded trailer 2400 miles. During this trip we went up hills and down hills, we even did some flat land driving. The towing was done in the tow-haul mode on the transmission. We got a low gas mileage of 9.5mpg, a high of 19.5mpg and a complete trip mileage of 13.5 mpg. A friend of mine with a Ford F-350 diesel told me that I get better mileage then he does with a lighter trailer.

Posted

What are your specs again?

2014 CCSB 6.2 LTZ with 3.42, most of the time was spent at 70-75mph on cruise control.

Posted

Consider yourselves lucky. After my tire swap and 2.5 level kit, I'm getting 14-15 mpg on the highway at 70-75 mph. This SUX but I only have myself to blame, I went with looks over economy. I didn't think it would be such a drastic change but I was clearly wrong. My tires are 275/65/20 Toyo Open Country M/T (34x11 toyo specs). Don't get me wrong, I love the truck but I do miss the good mpg days! lol

Posted

6asesa4a.jpgMy 4.3 was struggling to switch to V4 mode. So I filled up w/ 91 Octane top tier gas and it is performing a lot better! My average was 17 mpg with the low grade 87 Octane, and now my average for the 400 mile average is 20.0 mpg. Once I run another tank through it, I should be 21or 22+ mpg.

 

 

Go Army! GO ORDNANCE!!!

Posted

2014 CCSB 6.2 LTZ with 3.42, most of the time was spent at 70-75mph on cruise control.

That's exceptional. I'll post up my results next weekend after our camping trip.
Posted

 

a3eda7u3.jpg Averaged 12.2 driving around 75 mph 373 mile round trip pulling my yamaha rhino & trailer with tow/haul button on the entire time

Posted (edited)

5.3, 3.42, 87 octane. Driving back and forth to work. Mixed driving.

post-130182-0-98931200-1406430554_thumb.jpeg

post-130182-0-69879300-1406430790_thumb.jpeg

post-130182-0-28340300-1406431016_thumb.jpeg

post-130182-0-64164500-1406431331_thumb.jpeg

post-130182-0-30206000-1406431483_thumb.jpeg

post-130182-0-55991600-1406431594_thumb.jpeg

post-130182-0-98931200-1406430554_thumb.jpeg

post-130182-0-69879300-1406430790_thumb.jpeg

post-130182-0-28340300-1406431016_thumb.jpeg

post-130182-0-64164500-1406431331_thumb.jpeg

post-130182-0-30206000-1406431483_thumb.jpeg

post-130182-0-55991600-1406431594_thumb.jpeg

post-130182-0-98931200-1406430554_thumb.jpeg

post-130182-0-69879300-1406430790_thumb.jpeg

post-130182-0-28340300-1406431016_thumb.jpeg

post-130182-0-64164500-1406431331_thumb.jpeg

post-130182-0-30206000-1406431483_thumb.jpeg

post-130182-0-55991600-1406431594_thumb.jpeg

post-130182-0-98931200-1406430554_thumb.jpeg

post-130182-0-69879300-1406430790_thumb.jpeg

post-130182-0-28340300-1406431016_thumb.jpeg

post-130182-0-64164500-1406431331_thumb.jpeg

post-130182-0-30206000-1406431483_thumb.jpeg

post-130182-0-55991600-1406431594_thumb.jpeg

Edited by Ventilator

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