Jump to content

Recommended Posts

Posted

Curious what's out there for the highest miles on the 3.0L. I have a 2020, that's at 63k now. Love this drivetrain. Only complaint is the fuel knock that's intermittent, not sure why it does that. 

Posted

Are you talking about the clattering at 1500-2000 rpm under light acceleration at low speed? If so seems to be pretty common. Some comments out there that it may be related to fuel quality. Maybe try an additive. 
 

Anyhow, there are more than a few trucks on autotrader with 90k+. Search Silverado 1500 with diesel fuel type and set the distance to Any, sort by highest mileage first. 
 

54DB3247-BDFF-4852-8564-E7255CD72131.thumb.png.3ec16ce7c165c32a67497d68e0f4b1c1.png

 

  • Like 1
Posted

$58k for a pre-refresh half-ton High Country with almost 100,000 miles on it. Will this madness ever end?!? :smash:

Posted
2 hours ago, jlong1984 said:

$58k for a pre-refresh half-ton High Country with almost 100,000 miles on it. Will this madness ever end?!? :smash:

Right?! The used market is awful right now.  The entire market is awful.  We all know who to thank for the economy turning to ******. 

  • Like 1
Posted
On 3/27/2022 at 6:56 AM, Dirk13 said:

Are you talking about the clattering at 1500-2000 rpm under light acceleration at low speed? If so seems to be pretty common. Some comments out there that it may be related to fuel quality. Maybe try an additive. 
 

Anyhow, there are more than a few trucks on autotrader with 90k+. Search Silverado 1500 with diesel fuel type and set the distance to Any, sort by highest mileage first. 
 

54DB3247-BDFF-4852-8564-E7255CD72131.thumb.png.3ec16ce7c165c32a67497d68e0f4b1c1.png

 

This is great info. I saw many trucks on there up to 100K. Great to see for this 3.0. Its really a winner. Any big issues would be out there with those miles. Lets face it, most people come to a forum for research or to complain about their issue. Not to say how great their truck is and that it has no problems. If I lost my truck tomorrow, I would ONLY consider the 3.0. It has been fantastic.

Posted
On 3/27/2022 at 10:07 AM, jlong1984 said:

$58k for a pre-refresh half-ton High Country with almost 100,000 miles on it. Will this madness ever end?!? :smash:

It’s going to end! And end HARD!!!  All I can say is: better have some money put away because a recession is coming!  
 

  • 8 months later...
Posted
On 3/26/2022 at 7:11 PM, Velislide said:

Curious what's out there for the highest miles on the 3.0L. I have a 2020, that's at 63k now. Love this drivetrain. Only complaint is the fuel knock that's intermittent, not sure why it does that. 


It's a different fuel map for when the truck is doing an active regen. You're hearing injector noise, it's not anything to do with any of the other moving parts. To be honest, it's my #1 complaint about an otherwise awesome engine. Regens happen way too often, probably because the DPF is small and either GM didn't want to pony up for a bigger one, or there were packaging considerations since the DPF is under the hood.

Posted (edited)

My neighbor got the new 3.0 (gmc/at4) a little before I got my 2.7 ho and hauls light gear (maybe few thousand lbs) to remote field for work so wanted high economy/longevity, so has about double miles I do, maybe 25,000 (40,000 kms) and has gone limp mode 4 times due to emissions stuff, he's pretty choked. Major car guy, two built mustangs, built bmw m40, lifts in his garage, couple trucks, motorbike also and works on all himself. Having said that...any of you gone into limp mode? If so how many times in your mileage?

Edited by 4banger
Posted (edited)
19 hours ago, 4banger said:

My neighbor got the new 3.0 (gmc/at4) a little before I got my 2.7 ho and hauls light gear (maybe few thousand lbs) to remote field for work so wanted high economy/longevity, so has about double miles I do, maybe 25,000 (40,000 kms) and has gone limp mode 4 times due to emissions stuff, he's pretty choked. Major car guy, two built mustangs, built bmw m40, lifts in his garage, couple trucks, motorbike also and works on all himself. Having said that...any of you gone into limp mode? If so how many times in your mileage?

Never. Not at all common on the 3.0 and certainly not repeatedly after whatever the issue is gets fixed. It’s not something that just happens on a fluke because the emissions system feels like causing an issue that day.

 

What’s the issue causing the “limp mode”? What codes is he getting? What does the dealer say or what have they replaced so far?

Edited by Dirk13
Posted

I have to catch him and get those answers for ya, I'm watching for him. Was curious if this was a pattern able thing with the gm diesels and how many a guy may have to live with per x amount of miles. His work partner has an older eco-diesel he was able to delete and no issues, gets better mileage also, they figure due to the better aero on brick front gm's and trailboss at4 lift/tires. They both do the same mileage to these remote sites empty or with the light trailer.

Posted
On 12/12/2022 at 12:47 PM, 4banger said:

My neighbor got the new 3.0 (gmc/at4) a little before I got my 2.7 ho and hauls light gear (maybe few thousand lbs) to remote field for work so wanted high economy/longevity, so has about double miles I do, maybe 25,000 (40,000 kms) and has gone limp mode 4 times due to emissions stuff, he's pretty choked. Major car guy, two built mustangs, built bmw m40, lifts in his garage, couple trucks, motorbike also and works on all himself. Having said that...any of you gone into limp mode? If so how many times in your mileage?

Sounds like Canada needs to hurry up and finish a delete and tune.🤷🏼‍♂️

Posted

34k on my 2020, no limp mode or performance issues to speak of. I do, however, keep myself aware of silt levels and burn off cycles using an iDash.

Posted (edited)

46k on a 22' LTD  . No issues at all. Wish there was an indicator for when it was in regen. (besides buying something like idash) 

Edited by John F.
Posted
On 12/13/2022 at 5:34 AM, Dirk13 said:

Never. Not at all common on the 3.0 and certainly not repeatedly after whatever the issue is gets fixed. It’s not something that just happens on a fluke because the emissions system feels like causing an issue that day.

 

What’s the issue causing the “limp mode”? What codes is he getting? What does the dealer say or what have they replaced so far?

Caught him, says def injector, replaced each time. 

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,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   3 Members, 0 Anonymous, 1,633 Guests (See full list)

  • Latest Articles

  • Posts

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