Jump to content

Recommended Posts

Posted (edited)

I just purchased a 2019 gmc Sierra Limited elevation, it has 63km on it a I noticed this ticking sound ,anyone know what it is or anyone else's doing it or done it  at firdt thought i was something becasue it was cold but left it in my heated garage and set temp to about 10 degrees celeus and still made it  Thank you 

Edited by Asd A
Posted

If you’re talking about the tick that sounds kind of like a clock, then my 19 has that too. I haven’t figured out where it is coming from yet either and am curious what others have to say.

Posted

MY TB has done this since new exhaust manifold,other metal parts expanding when warming up thats all

Posted
50 minutes ago, K455 said:

MY TB has done this since new exhaust manifold,other metal parts expanding when warming up thats all

+2 on this.

The K2 trucks have this warm up tick also.

Posted (edited)

Ok. Thanks everyone, I'm still going to take it to the dealership just to make sure . I'll let everyone know what they tell me .

 

So just wondering a friend of mine has the exact truck but a 17 or 18 and a co worker has a 19 trailboss ,would they to have the similar ticking noise ?

Edited by Asd A
Posted

My 2019 with about 7k miles does it as well. Doesn't matter if the engine is hot or cold. If it still does it around 15k miles, I'll probably mention it to the dealer. 

Posted

2017 5.3l also does it no matter the temp of my block. I have wondered if it my be the vac pump as that's where I hear most of the sound. This is my first Ecotec3 so I'm unfamiliar.

Sent from my SM-N975U using Tapatalk

Posted

All of these trucks tick, click, and kinda sound like a sewing machine. Totally normal with direct injection. It does take some getting used to, especially in the drive thru, with the window down and all the noise bouncing off the wall at ya! They sound like a real junker! ? 

Posted

Its the fuel pump and is 100 % normal under certain operating temps . 2016 with 120k and no issues here . 

Posted

I really cant see it being a normal sound , like I mentioned earlier I have   a friend of mine has the exact truck but a 17 or 18 and a co worker has a 19 trailboss andvtheres dont make that noise 

Posted

2019 SLT 5.3 same thing. Clicks and clicks till the cows come home, regardless of the engine temperature. It’s really noticeable when I remote start the truck in the garage before I head out. The sound is amplified and as someone above mentioned makes it sound like a junker! I’m curious if anyone here has taken the truck in for this reason? I’m close to doing it just in case. 

Posted
13 hours ago, Asd A said:

I really cant see it being a normal sound , like I mentioned earlier I have   a friend of mine has the exact truck but a 17 or 18 and a co worker has a 19 trailboss andvtheres dont make that noise 

So they say or so you have witnessed?

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, 1,803 Guests (See full list)

  • Latest Articles

  • Posts

    • 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.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...