Jump to content

Recommended Posts

Posted

I went from a 2020 LM2 (2wd) to a 26 LZ0 (4wd) and have been enjoying it a lot. I commute 60 miles, 1-way to work (120 round trip) from Orange County to Los Angeles. In the morning it takes my roughly 1-hour, heading home 1hr 45min - 2.5hours. My previous normal average was 30 - 33 mpg in my LM2 (modded with 3" lift, 33" tires, and a few PPE tubes). With the new stock truck (no mods, 31" tires, and 4x4), I average 28mpg. With the holidays, colder temps, and less traffic, I now jumped up to 30mpg. I use a fuel tracker and can confirm that the numbers on the dash are typically spot on with the actual driving.

 

Another thing I noticed, and maybe because it's new, but the DEF usage is much less. My background with DEF is, and is my opinion, that is is corrosive and crystalizes easily. Also being an emissions item, I don't like being less than half a tank. I figure with the heaters in the def tank and the way it can crystalize, I always want it full. Plus, when I get down to half a tank of DEF, it takes a single 2.5 gallon box. No over filling and spilling, no filling and realize you need more for full. My LM2 went about 2000-3000miles to a half tank (one box), and my first fill up in the LZ0 was 3770 miles. I hope this continues.

 

Below are some pics of the screen and mileage app

20260106_052028.jpg

Screenshot_20260106_061115_Fuelio.jpg

  • Thanks 2
Posted

Good info.

 

My truck was delivered with the DEF tank just under half full. Truck only had something like 30 miles on it so it was probably that way from the factory. Long story short, I didn't care. Threw in a 2.5 gallon jug of DEF when I got home and that brought it up to completely full. That's when I found out the capacity of the tank is probably ~5 gallons.

 

In 1500 miles of driving... The truck didn't see highway speeds for literally the first 500 miles. It didn't tow anything until just after 1,000 miles. The last 400 miles were towing a loaded trailer between 6k-7k lbs depending on the car that was on it. The DEF gauge has lost one bar in 1500 miles of driving so far.

 

I am thinking the DEF usage complaints are definitely limited to the LM2. The 2025+ LZ0 seems to consume DEF very slowly.

Posted
2 hours ago, Atlas said:

LZ0 seems to consume DEF very slowly.

That seems true. Until you start towing.

I now carry a box of DEF in truck when I am towing my travel trailer.

It seems to suck it down when towing. I have had to stop and get DEF once, just to get home.

Now, I just bring some with me.

Posted

Man i couldn't imagine owning a Fullsize truck in that god forsaken corrupt state!

  • Haha 1
Posted

Some info that may be helpful on DEF etc...from GM service info....

 

The DEF level gauge does not operate like a typical float-style gauge that is used in a fuel tank. The Engine Control Module (ECM) monitors the DEF level and consumption rate in order to calculate an estimated range. DEF levels are detected by the DEF level sensor.

There may be some fluctuation in the amount of DEF represented on the DEF level gauge. After filling the DEF tank, it may take a few key cycles to register the correct amount in the DEF tank. With the new segmented DEF level gauge, it is possible that after adding 5 gallons (18.9 L) of DEF that the gauge reads as a full tank after the fill event. However, if the actual level of DEF is just entering the last segment on the gauge, the gauge is likely to drop by one segment shortly after driving after the fill event. As a result, a driver could have an initial impression that the vehicle consumes an excessive amount of DEF.

 

Emissions Requirements

 

Every year, GM produces diesel engines that continue to meet aggressive federal requirements to reduce Nitrogen Oxides (NOx) in the vehicle exhaust. As DEF is required to reduce the NOx in the exhaust, DEF consumption will increase as NOx reduction requirements increase. Customer trading in an older model year diesel vehicle for a newer model year vehicle will likely see an increase in DEF usage. DEF consumption increases as the newer vehicles meet the more stringent emission requirements for that model year.

The amount of DEF consumed also is a function of how hard the engine is working, or engine load. Due to engine use, it is more representative to compare DEF consumption to the amount of fuel consumed – also a function of engine load – instead of miles traveled. In addition to engine load, other factors that affect the DEF usage rate are the humidity, temperature, and altitude where the vehicle is operating.

 

Under certain conditions, the ECM will increase or decrease the amount of DEF used based on learning or adaptive algorithms. In the event of a malfunction and Check Engine light, the ECM may double or even eliminate the amount of DEF that is being used. An improper amount of DEF use will continue until the vehicle is repaired and the learned value in the ECM is reset.

 

 – Thanks to Larry Yaw

 

  • Like 1
Posted

I thought I'd pop in here just for future reference as folks come across this thread.  My data is related to the LM2.  I bought my 22 (refreshed) in June of 2024 and for the first (roughly) six months, I tracked all of my fuel usage - sadly, I didn't with DEF but it's so minimal that it doesn't really matter.  The google spreadsheet linked below are the results.  The comparison was to real-world mileage of my final-year Chevrolet Avalanche with the 5.3 (I had the "displacement on demand" disabled because it was worthless and annoying).

 

https://docs.google.com/spreadsheets/d/1MKHG6HOO_osUZQHqQQuoGAeSveTb7jN0ePLnCsLUeVk/edit?usp=sharing

 

TL:DR, tracking cost per gallon of regular versus diesel and my driving experiences over that 6 monthly led to a roughly 30% "savings" compared to the 5.3.  Obviously the cost of DEF and other factors such as fuel filter replacement would bring this down but those costs are so minimal, I didn't bother to factor them in.  I will also note that I am a conservative driver, rarely speed more than a couple MPH over the limit with traffic flow.  I don't "hyper mile" but I don't drive my truck like a sports car either.

 

Not sure if anyone cares, just thought I'd drop it here for anyone that happens upon this thread looking for information.

 

 

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,858 Guests (See full list)

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