Jump to content

Recommended Posts

Posted

Brand new ‘21 Sierra Denali 3.0 diesel truck, going on 2k miles.  Upon acceleration, the engine makes a pinging or knock noise.  Sounds like a gas engine with low octane fuel.  Dealer said they all sound this way.  Anyone else?

Posted (edited)
18 hours ago, designzio said:

Brand new ‘21 Sierra Denali 3.0 diesel truck, going on 2k miles.  Upon acceleration, the engine makes a pinging or knock noise.  Sounds like a gas engine with low octane fuel.  Dealer said they all sound this way.  Anyone else?

The diesel is designed as a detenation ignition compared to a spark ignition(gasoline), so your diagnosis is correct, a diesel will knock and clatter. But the 3.0 is pretty darn good at hiding the fact. I can't get over the fact that they can hide the light blue/gray smoke a diesel produces at cold start-up.

 

Be thankful you don't have a Detroit under the hood.

 

 

Edited by gemarsh
Spelling
Posted

My 2021 3.0 was extremely quiet for the first 400 miles and then it started under light acceleration and light deceleration like when I am going stop sign to stop sign in a 25 mph area around where we live. It is like the pistons are hitting the cylinder head. It is really loud.  

Our Grand Cherokee eco diesel does not sound like that and I never heard any of my 7 Ram's with Cummins motors do it either. 

Posted

It seems to be pretty common for the 3.0. Mine does it as well. During regen it is even more prevalent.

 

My truck did not do it at all when new And within the first 1000 miles developed the rattling under light acceleration. It bugged me and I searched all over the internet. Apparently, the injectors can be “relearned” or something which will get rid of the knock/clatter under light accel. I read information that it’s temporary relief from the noise and it will return. Someone on some forum mentioned a TSB on this but I never found it.

 

I considered taking it to the dealer, and would have if my local one was not totally worthless. But they are, so instead I have driven the truck for 13,000 miles, the noise is still there but I don’t even notice anymore.

 

I really think it’s a non-issue. Try some premium quality diesel or an additive if you don’t like hearing it. 

Posted
On 10/3/2021 at 11:03 PM, designzio said:

Brand new ‘21 Sierra Denali 3.0 diesel truck, going on 2k miles.  Upon acceleration, the engine makes a pinging or knock noise.  Sounds like a gas engine with low octane fuel.  Dealer said they all sound this way.  Anyone else?

Welcome to owning a diesel engine.😀

 

 

  • 3 weeks later...
Posted

I have the same clatter, fuel knock, and pinging with mine as well. I notice it’s really sensitive to different fuels with BP causing the worst sounds from the engine. Love’s with 7 oz. of Stanadyne additive gives the best results for me. I’m also thinking the oil is way to thin for these diesels which is contributing to the noise.

  • Like 1

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

  • Latest Articles

  • Posts

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...