Jump to content

Heads Up 3.0L Owners. Def System Re Flash TSB

ILSilverado
 Share

Recommended Posts

ILSilverado Enthusiast

ILSilverado

Posted
Posted

Well I had the required re flash done for the DEF system and now she is drinking DEF like a $2 hooker drinks Ripple. I would say 50% more def consumption than before. Keep an eye on the DEF gauge folks.

Sierra 3.0 Enthusiast

Sierra 3.0

Posted
Posted

I can confirm.  I had mine done about 2200 miles ago.  I pulled a camper for the first time and, wow, it used a lot of def.  Now back to normal driving and it's still more than it was.  I'm guessing the update solved an emission issue with not running clean enough?

ILSilverado Enthusiast

ILSilverado

Posted
  • Author
Posted
9 hours ago, Sierra 3.0 said:

I can confirm.  I had mine done about 2200 miles ago.  I pulled a camper for the first time and, wow, it used a lot of def.  Now back to normal driving and it's still more than it was.  I'm guessing the update solved an emission issue with not running clean enough?

Im guessing so. The regeneration cycles are much more frequent now.

Max Z71 Enthusiast

Max Z71

Posted
Posted

Mine REGENs about every 120 miles. I have a Banks iDash gauge and can see when it goes into REGEN.

 

What is your average distance between REGENs?

ILSilverado Enthusiast

ILSilverado

Posted
  • Author
Posted
20 minutes ago, Max Z71 said:

Mine REGENs about every 120 miles. I have a Banks iDash gauge and can see when it goes into REGEN.

 

What is your average distance between REGENs?

I have not measured mileage vs regens what is this gauge you have?

 

Max Z71 Enthusiast

Max Z71

Posted
Posted

Check the internet for Banks iDash.

 

It is a 52 mm gauge made by Gale Banks that plugs into your OBD II port and reads hundreds of parameters from your truck.

 

One of those is called "REGEN". It tells me if Regen is "OFF" or "ACT" for active. It also has average miles between Regens which mine stays about 120 in my 2000 miles I've had my truck.

 

I have two of them, one for REGEN and the other for temperatures, oil, transmission and water as well as oil pressure.

 

Each gauge can display up to 8 different parameters. 

 

Max

Sierra 3.0 Enthusiast

Sierra 3.0

Posted
Posted (edited)

I do not have any specifics on my regens but it's doing it at least 2-3 times on each tank.  I'm a little disappointed in this as the fuel mileage goes down significantly each time.  If these did not have the emission controls the mileage would be incredible.  I have not seen my average to be anywhere near 29 MPG on the highway going 70 MPH.  My average mileage so far has only been around 24-25 MPG and the faster I go on the highway the lower it gets.  Then when regens hits I get 20 MPG.

Edited by Sierra 3.0
newdude Senior Enthusiast

newdude

Posted
Posted (edited)

https://gm-techlink.com/?p=13143

 

Quote

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.

 

 

I wouldn't doubt that the consumption rate will adjust as the ECM is learning/adapting.  Probably because the reprogram does a hard reset on the system, the ECM is still adjusting the amount of DEF needed.  I'd give it a few hundred miles and see what it does.  

Edited by newdude
Colossus Senior Enthusiast

Colossus

Posted
Posted

Don't plan on being able to delete the emissions crap off of these newer trucks, the EPA has really cracked down hard on the tuners and such that help with emissions removal. 

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
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined

  • Who's Online   4 Members, 0 Anonymous, 1,691 Guests (See full list)

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...