Jump to content

Recommended Posts

Posted

Quick comment, I took a drive earlier and it moved back up to 1/2 full.  The description above from @redwngr is likely what is happening.  Thanks again!

  • 1 month later...
Posted

Have gone 800 some odd miles, added 2.5 gallons of def and the level shows to be very close to what it was when I drove the truck off the lot.  So probably around 320 miles per gallon.  

  • 3 weeks later...
Posted

Slightly different because I actually am on my second part being replaced in 10k miles. At 2k I noticed a burning smell and smoke under my hood. Took it in. They said it was a ceramic coating burning off. I accepted this. 5k miles later I take my trailer on a 3k mile trip. At the end of the trip engine light comes on. Its the PPF. Packed full of carbon.  Dealership said it was the smell and smoke from the issues at 2k. Had it replaced.  Blue def usage is tops at 300 miles a gallon. Its now in the shop because the blue def float sensor is bad and was false reading and putting the truck into limp mode. GM is repairing that without a code. From what I read people have been getting 1k miles a gallon out of this model. Mine is just one exhaust issue after another.

Posted
13 hours ago, Jeepvkng1 said:

Its now in the shop because the blue def float sensor is bad and was false reading and putting the truck into limp mode

Kind of wondering if this is a common issue and this is something I am kind of watching for on mine right now.  My level showed it was at like 3 bars a couple weeks ago, according to the supplemental manual it should have been able to take 3.5 gallons of def.  I added less than 1.5 gallons and it was full at the tank, overfilled.  The level then showed one bar less than full.  Drove for about a hundred miles with it at that level and then the level went to full, all bars lit up green.  It has been showing full for the past 200+ miles since.  I question the accuracy of this.

Posted

When the sensor went it would go all over the place. Full, half full 160 miles down to none at all while in park. Took 2 trips to the dealership to get them to realize that it was reading full and there was one gallon of def in the tank. 

  • 1 month later...
Posted

7500 miles so far on my 2020, picked it up with a full def tank and I’ve put over ten gallons in it myself. Just made a 2k miles trip pulling a 24’ Livestock trailer Not even half loaded And went through 5 gallons easily. 

Posted

My gauge stayed pegged to the full side for nearly 1000 miles.  Finally went down one bar, then after about another 500 miles it went down another bar.  Will refill it when I get to about 3 bars and see how much it takes to fill it up.  So not really sure how it is doing now, but seems to be a little better than my early estimations.  

Posted

Anyone interested in finding out what their truck is really getting for def mileage, find a nearby bulk def location.  Likely in a truck stop. Likely in the truck lanes. 

 

This 3.0L wasn't full when I got it so today I decided to fill it so at next fill I'll be able to calculate mpg. 

Anyway, with the new def fill beside the fuel fill it is super easy to use the bulk pumps.

 

The do have auto shut off.  I was in noisy fuel lanes so there was no way it would be possible to hear change in sound as fluid level starts up fill tube. 

DEF pump nozzle shut-off worked perfect.  No splash back. 

 

 

Just like checking fuel mileage, the only way to check def mileage is to fill tank, record odometer, drive, refill tank.

Miles driven divided by gallons to refill.....

 

If the tank isn't filled at both the start or end of exercise, then the mpg is just a wild ass guess.

Posted

I have a 2020 Duramax 3500 single axle 4x4 pickup and I have used over 10 gallons of DEF fluid since new.  I am currently at 4700 miles with 1/2 of the DEF tank remaining according to the DEF gauge.  This seems excessive to me since my brother has the same truck in 2018 that he has never added DEF fluid to in 14k miles.  He is at the 30% mark in his pickup but hes waiting to get that level really low before adding more since it has been in the truck so long.

Posted

My problem seems to have been fixed? since I had the def tank replaced.  They did it because I kept complaining about it and after a lot of screaming and several trips to the dealer after the gauges kept freaking out they said it was per customer request. Night and day difference all around.  Def usage is where it is supposed to be and gas mileage has improved.  Thinking they may have thrown in a update also but nothing was said to me. 

  • Like 1
  • 3 weeks later...
Posted

I also had a 2016 DRW Silverado and I just got a 2020.  I’m in Canada so we go by KM.  I’ve driven about 1700km and burned half a tank of DEF.  it seems very excessive to me.  I called the dealer and they are looking into it .  

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