Jump to content

chirping noise ,still not addressed

6.2 man
 Share

Recommended Posts

6.2 man Enthusiast

6.2 man

Posted
Posted

I still have a chirping noise upon startup of the truck. 2019 GMC Denali 6.2 , sounds like a fan belt or serpentine belt but im told its in the exhaust valve built into the exhaust system. GM has told the servicing dealer who by the way has been GREAT to deal with that if they can find another truck to make this chirping noise that it is supposed to be like that. I told them NO ,if another truck makes a chirping noise that means they have 2 trucks that have a problem. I have requested to have the exhaust replaced and to speak with a engineer or regional representative to find out why they refuse to fix this issue .it has been well over a month but no response from GM ,This is becoming VERY annoying to have to spend this much time to fix a brand new vehicle with 3000 miles on it. Where is the service after the sale from GM .Things break,I get it ,just fix it already.  Sorry for the rant everybody 

  • 2 weeks later...
  • Replies 66
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

OnTheReel
OnTheReel

Just put a cat-back on it and be done! Even if they do replace it, it will make noise again before too long. 

TriadAT4
TriadAT4

My dealer just checked my truck for this. I’m being told it’s the exhaust manifold and that it’s normal.

ShamrockShooter
ShamrockShooter

Problem solved for under $6, clamp it open. Do that and see if the noise goes away.  Sent from my Pixel 2 using Tapatalk      

Sierra Dan Senior Enthusiast

Sierra Dan

Posted
Posted

6.2 man, is your 2019 the new T1 design or the LD version ?

If you have the K2 LD version then the chirp is most likely your exhaust flapper valve.

Many have had their whole exhaust systems replaced due to this.

The flapper was re-designed in 2016 after many complaints on the earlier 14 & 15 models like mine.

Sometimes when out driving you can also hear the chirp when the engine switches from V4 back to V8.

 

 

6.2 man Enthusiast

6.2 man

Posted
  • Author
Posted

The dealership has diagnosed the noise to the exhaust flapper but will not order me a new exhaust,they are waiting on a engineer to come in but say he is very busy and it may take a while,well its been about a month and a half with this and no thing has changed,I have repeatedly asked them to order me a exhaust but for some reason they will not.

Sierra Dan Senior Enthusiast

Sierra Dan

Posted
Posted

Sounds like the run around to me.

Try a different dealer. Any GM dealer can provide you with service.

OnTheReel Senior Enthusiast

OnTheReel

Posted
Posted

Just put a cat-back on it and be done! Even if they do replace it, it will make noise again before too long. :cool:

  • Like 2
K455 Enthusiast

K455

Posted
Posted (edited)

When I start my 19 Trailboss 5.3 cold with 1100 miles I hear a click sound every second when at idle,like something making a full revolution then click.Not a tap or chirp,when the rpms drops down to 500 it goes away. Done this from the first day only does this with a cold idle ,I am thinking fuel injection.You have to have the window down to hear,or next to another car or wall.I am not worrying about it,I am calming down in my elder yrs.

Edited by K455
Donnyb313 Enthusiast

Donnyb313

Posted
Posted
On 4/5/2019 at 4:59 PM, K455 said:

When I start my 19 Trailboss 5.3 cold with 1100 miles I hear a click sound every second when at idle,like something making a full revolution then click.Not a tap or chirp,when the rpms drops down to 500 it goes away. Done this from the first day only does this with a cold idle ,I am thinking fuel injection.You have to have the window down to hear,or next to another car or wall.I am not worrying about it,I am calming down in my elder yrs.

By your description, I have the same clicking sound on my 5.3l trailboss. I was just at the dealer asking if it was normal, the tech "guessed" it was normal. I'll be finding a new dealer to ask and maybe start a couple trucks on the lot to hear what they sound like. 

 

6.2 man, mine sounds like a click every second at idle, kinda sounds like a bad serpentine belt would, need to be standing close to the front of the truck to hear it. is that what yours sounds like? 

TriadAT4 Enthusiast

TriadAT4

Posted
Posted

My dealer just checked my truck for this. I’m being told it’s the exhaust manifold and that it’s normal.

  • Like 1
Donnyb313 Enthusiast

Donnyb313

Posted
Posted
8 hours ago, TriadAT4 said:

My dealer just checked my truck for this. I’m being told it’s the exhaust manifold and that it’s normal.

Did they say why the exhaust manifold would click? Seems odd 

K455 Enthusiast

K455

Posted
Posted (edited)

I am glad I am not the only one noticing this, it is not a major damaging sound I am thinking it may be the exhaust manifold getting hot.Ever notice when you shut your bike off Harley etc.. and hear the exhaust clicking. I wonder,I really do not think it is major,but It is not a tap,tick,slap, CLICK I say only on cold start idle and stops at 500 rpms when idle comes down or soon after.It just may be the manifold expanding because new.I have to say this Trail boss rides plush for what it is,I seen a post where a female was complaining about the ride,I disagree.

I am glad My OCD is not alone.

Keith

Edited by K455
ShamrockShooter Senior Enthusiast

ShamrockShooter

Posted
Posted
I still have a chirping noise upon startup of the truck. 2019 GMC Denali 6.2 , sounds like a fan belt or serpentine belt but im told its in the exhaust valve built into the exhaust system. GM has told the servicing dealer who by the way has been GREAT to deal with that if they can find another truck to make this chirping noise that it is supposed to be like that. I told them NO ,if another truck makes a chirping noise that means they have 2 trucks that have a problem. I have requested to have the exhaust replaced and to speak with a engineer or regional representative to find out why they refuse to fix this issue .it has been well over a month but no response from GM ,This is becoming VERY annoying to have to spend this much time to fix a brand new vehicle with 3000 miles on it. Where is the service after the sale from GM .Things break,I get it ,just fix it already.  Sorry for the rant everybody 

Problem solved for under $6, clamp it open. Do that and see if the noise goes away.7a6f544546af0959e8b9440e30396d1f.jpg

 

Sent from my Pixel 2 using Tapatalk

 

 

 

  • Like 1
  • 2 weeks later...
MyTwoChevys New Member

MyTwoChevys

Posted
Posted

I had this same noise. I tied off my flapper valve and that made no difference.

 

I put my truck up on a rack and was looking for anything that could be causing this noise. It sounded like it was coming from just left of center of the dash from the inside. I found that the drivers side of the engine the ignition coil cover was off and was down and wedged between the steering shaft and the engine. And it is not like it could just fall off. It has a crankcase vent line that goes through it when it is installed in its correct place. So it had to have been there from the factory. Maybe they tried to install it without pulling the vent line out and that caused it to come off over time. I put it back where it belonged and the noise went away.

  • Like 1
ShamrockShooter Senior Enthusiast

ShamrockShooter

Posted
Posted
I had this same noise. I tied off my flapper valve and that made no difference.
 
I put my truck up on a rack and was looking for anything that could be causing this noise. It sounded like it was coming from just left of center of the dash from the inside. I found that the drivers side of the engine the ignition coil cover was off and was down and wedged between the steering shaft and the engine. And it is not like it could just fall off. It has a crankcase vent line that goes through it when it is installed in its correct place. So it had to have been there from the factory. Maybe they tried to install it without pulling the vent line out and that caused it to come off over time. I put it back where it belonged and the noise went away.
Wow. Did you take a picture of it?

Sent from my Pixel 2 using Tapatalk

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,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

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

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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 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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

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