Jump to content

2021 Diesel break in

Bayou Cajun

By Bayou Cajun
in 6.6L Duramax Diesel (L5P)

 Share

Recommended Posts

Bayou Cajun Enthusiast

Bayou Cajun

Posted
Posted

I know this question probably has been asked a hundred times.  I just put a deposit down on a new 2021 2500HD AT4.  I bought it out of state and will have to drive over 800 miles to get back home.  I know the owners manual says, do not drive it over 55 miles per hour for the first 500 miles, vary your speed etc.  My question is, with the new diesels, is this old language they are printing for the new engines.

 

Thanks for your help.

Paul

  • Replies 36
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

XY74
XY74

Take the 2 lane roads for a while on the way home, more to see and far more interesting than the bland highways.  

u3putt
u3putt

I wished I had thought about that.  I just bought a 2021 Z71 LTZ yesterday about an hour from my house.  Came home on the freeway with a big smile at about 90mph with 31 miles on the ODO when I bought

wade_660
wade_660

It’s not going to hurt anything. You think people are adhering to break in procedure on a test drive? Drive it like you stole it Sent from my iPhone using Tapatalk

Posted Images

kylant Enthusiast

kylant

Posted
Posted

i bought a Ford 2 states away, about 600 miles. 

I just drove it. I varied the throttle and never held it at a constant speed for any length of time. 

It was fine

Njmurvin Enthusiast

Njmurvin

Posted
Posted

If it's like my Dodge was, the break-in was more for the rear end than the engine/trans.  With my new Silverado, I followed the 500 mile break-in as best I could before towing. It had 136 miles on the odo when I got it. So, I don't know how those miles were driven. For the rest, I really tried to stay at 55 and under but that's nearly impossible on So Calif freeways (unless it's rush hour on the 405 in which case it's more like 5.5mph - if you're lucky).  So, I'd say most of my break-in miles varied between 58-63.

Bayou Cajun Enthusiast

Bayou Cajun

Posted
  • Author
Posted

Thanks, I guess my trip back will be a long one.  I will follow the manual's recommendation just to be on the safe side.  I appreciate the feedback.  Looking forward to my new toy.  I will not have any problems now going up the passes in Colorado with a loaded snowmobile trailer.

 

Take care and stay safe.

Paul

XY74 Enthusiast

XY74

Posted
Posted

Take the 2 lane roads for a while on the way home, more to see and far more interesting than the bland highways.  

  • Like 2
u3putt Enthusiast

u3putt

Posted
Posted

I wished I had thought about that.  I just bought a 2021 Z71 LTZ yesterday about an hour from my house.  Came home on the freeway with a big smile at about 90mph with 31 miles on the ODO when I bought it.  ?

 

  • Like 2
wade_660 Enthusiast

wade_660

Posted
Posted

It’s not going to hurt anything. You think people are adhering to break in procedure on a test drive? Drive it like you stole it


Sent from my iPhone using Tapatalk

  • Like 2
u3putt Enthusiast

u3putt

Posted
Posted
14 minutes ago, wade_660 said:

It’s not going to hurt anything. You think people are adhering to break in procedure on a test drive? Drive it like you stole it


Sent from my iPhone using Tapatalk

Boom.  Consider it stole.

Grumpy Bear Senior Enthusiast

Grumpy Bear

Posted
Posted
On 11/2/2020 at 10:13 PM, Bayou Cajun said:

I know this question probably has been asked a hundred times.  I just put a deposit down on a new 2021 2500HD AT4.  I bought it out of state and will have to drive over 800 miles to get back home.  I know the owners manual says, do not drive it over 55 miles per hour for the first 500 miles, vary your speed etc.  My question is, with the new diesels, is this old language they are printing for the new engines.

 

Thanks for your help.

Paul

The 'old language' in your 'new manual'? The question then is; it good advice? So what your asking a bunch of forum jockeys is, do to the people who designed and built my truck have the foggiest clue what's good for it.

 

How about an answer in the form of a question?

 

If you don't trust their advise, why buy the truck they designed and built? 

?

 

What you can trust from any manufacture is the LEAST you should do. 

 

They don't want to see that thing for a warranty repair EVER

 

 

Jglew82 Enthusiast

Jglew82

Posted
Posted
The 'old language' in your 'new manual'? The question then is; it good advice? So what your asking a bunch of forum jockeys is, do to the people who designed and built my truck have the foggiest clue what's good for it.
 

How about an answer in the form of a question?

 

If you don't trust their advise, why buy the truck they designed and built? 

[emoji848]

 

What you can trust from any manufacture is the LEAST you should do. 

 

They don't want to see that thing for a warranty repair EVER

 

 


This pretty much sums it up.
diyer2 Senior Enthusiast

diyer2

Posted
Posted

So many people are smarter than the engineers. But having the title engineeer doesn't mean you know it all. 

 

  • Like 1
Grumpy Bear Senior Enthusiast

Grumpy Bear

Posted
Posted
1 hour ago, diyer2 said:

So many people are smarter than the engineers. But having the title engineeer doesn't mean you know it all. 

 

This is a knife with two edges.

Yes some of the dumbest people I've ever met were engineers.

Could put a man on the moon but can't make a cuppa.

 

But no one is asking him how to make a cup of coffee. He asked him to get to the moon. That he can do. 

He may not know the differance between a Arabica, Robusta, Liberica or Excelsa beans but I'll bet he can accurately calculate the escape trajectory and hit the entry point with enough precision to keep my dumb butt in one piece. He isn't making my cuppa wake up but he is my go to guy for all things aero engineering. 

 

This OP question is one of....

Should I trust the engineer who designed a nut and bolt to tell me how to properly torque it?

 

I'm thinking yes is the answer. 

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