Jump to content

Recommended Posts

Posted

I usually make a trip from Colorado to Alabama in March-April to do some fishing and help my mother do some stuff around the house.  This year I had to wait till July due to everything going on.  To say the least I was very pleased with how the truck performed on the trip.  I like to take the southern route cutting down through New Mexico and picking up I-40 in Amarillo.  Last year I made the same trip in a 18 Crew Cab 4wd Sierra with a 5.3.  For that trip the MPG going out was about 18-21.  On the return after passing Oklahoma City, I had a head wind and best the truck would do was about 16.  With the Baby Duramax the trip average was 22-24.  I was easily able to go over 500 miles between fillups.  With a little prior planning I was also able to find diesel between 1.99-2.09 a gal.  Total trip was 3100 miles and DEF usage was 2.5 gal.

  • Like 1
Posted

I have read nothing but good things about this motor. I think GM hit a home run on this motor. Really glad they took their time on it, did lots of research, and built it from the ground up. Unlike what Furd did with their diesel and just brought it over from Land Rover. Congrats on the truck MPG's. 

  • Like 1
Posted

What was your best millage when going thru the mostly flat interstate driving? I would have thought that with all those highway miles your average would have been better.

Posted
12 hours ago, deepsouth said:

What was your best millage when going thru the mostly flat interstate driving? I would have thought that with all those highway miles your average would have been better.

Me too.  I was expecting closer to 27-30 for the trip.  Especially after passing Ok City on the trip out.  Now I do have a lead foot and had the cruise set at 80 for most of the trip.  If I had kept it at 75 or below that would have probably gotten me into the 27 range.  Still pretty impressed with the mileage I did get.  I have also made a few trips to Denver and seen a 30 mpg average.    

Posted

I have made one trip in my 20 Silverado with the 3L diesel. From south of the Roanoke area in Virginia to the Baltimore area in Maryland on I-81, I-66, I-495 and I-95 I averaged 29 mpg (hand calculated) with a few speed runs to 95mph. The trip was 325 miles. ?

 

Posted
21 hours ago, swervin36 said:

Me too.  I was expecting closer to 27-30 for the trip.  Especially after passing Ok City on the trip out.  Now I do have a lead foot and had the cruise set at 80 for most of the trip.  If I had kept it at 75 or below that would have probably gotten me into the 27 range.  Still pretty impressed with the mileage I did get.  I have also made a few trips to Denver and seen a 30 mpg average.    

Every time I see a 3.0 post that says low to mid lows on highway,  I'm always disappointed to hear,  then I find out that was at or near 80mph.  Now that is impressive MPG at that speed.   My 6.2 would be a couple mpg off its highway rating too if I kept it around 80.

 

The fact that you can do 80 in a truck and comfortably get over 20mpg is impressive - especially with your leveling kit and tires.

Posted

Note the cruise control setting.  I had just exited freeway.  These trucks are ridiculous. 

A9CCF170-57DE-45FA-8D7A-2455984BE541.jpeg

  • Like 1
  • 2 weeks later...
Posted
On 7/16/2020 at 12:09 AM, swervin36 said:

Me too.  I was expecting closer to 27-30 for the trip.  Especially after passing Ok City on the trip out.  Now I do have a lead foot and had the cruise set at 80 for most of the trip.  If I had kept it at 75 or below that would have probably gotten me into the 27 range.  Still pretty impressed with the mileage I did get.  I have also made a few trips to Denver and seen a 30 mpg average.    

Nice. My wife drove the truck on our last trip back home. She has a lead foot and was absolutely screaming down the highway. I thought for sure a trooper would bust her but luckily not. Definitely 80+ with a heavy foot. I just looked at the DIC for the 280 miles after reset and it shows 24 mpg which I was pleasantly surprised by. Little city majority highway all flat land

Posted

Just got my RST 3.0 last week and already have nearly 500 miles.  First lengthy drive was all highway from Mass to Maine on Monday, cruise control set at 7 over, so 72 or 77 MPH depending.  Trip computer showed 25.6 MPG, which I thought was pretty good for a brand new engine but I topped it off and hand calculated was even better: 249 miles / 9.2 gallons = 27 MPG.

 

Posted

I recently completed two more trips from SW Virginia to Maryland and got 28 and 29 MPG. I'm satisfied with that.

Posted
9 hours ago, gf2020 said:

Just got my RST 3.0 last week and already have nearly 500 miles.  First lengthy drive was all highway from Mass to Maine on Monday, cruise control set at 7 over, so 72 or 77 MPH depending.  Trip computer showed 25.6 MPG, which I thought was pretty good for a brand new engine but I topped it off and hand calculated was even better: 249 miles / 9.2 gallons = 27 MPG.

 

Awesome! Welcome to the 3.0 family. I don't hand calculate often, but everytime I do it has been better than what the DIC indicates. Not staggering by any means but a little higher which is great

  • Like 1
Posted
2 hours ago, Duramax3oh said:

Awesome! Welcome to the 3.0 family. I don't hand calculate often, but everytime I do it has been better than what the DIC indicates. Not staggering by any means but a little higher which is great

I've noticed that from many of those that have reported DIC vs hand calc for the 3.0L.

Posted
4 hours ago, Duramax3oh said:

Awesome! Welcome to the 3.0 family. I don't hand calculate often, but everytime I do it has been better than what the DIC indicates. Not staggering by any means but a little higher which is great

It was the opposite with my 18 5.3.  The DIC always showed about .5 - 1 mile better than the hand cal.

 

Posted

I  just went on a 500 mile round trip, and averaged 26.4 for the whole trip in my 3.0L 4x4, with 5 peeps in the truck and cruise set on 79mph most of the time. 

I was pretty happy, my last 2015 6.2L 4x4 averaged between 21-22 mph to the same destination. Very happy with the baby D-max!!!

 

Mike

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   4 Members, 0 Anonymous, 1,891 Guests (See full list)

  • Latest Articles

  • Posts

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...