Jump to content

Recommended Posts

Posted

I have multiple issues with rattles in the dash are.  It has been in the shop over 3 times for this and I have lost at least 2 weeks use of the truck.  They found loose bolts in both fenders.  They also replaced a cowling along the firewall and windshield that broke on the rights.  They were taking running boards off, fenders skirts, mud flaps, etc.  They finally found the culprit after a good length of time.

Posted
17 hours ago, Joe Sargent said:

I have multiple issues with rattles in the dash are.  It has been in the shop over 3 times for this and I have lost at least 2 weeks use of the truck.  They found loose bolts in both fenders.  They also replaced a cowling along the firewall and windshield that broke on the rights.  They were taking running boards off, fenders skirts, mud flaps, etc.  They finally found the culprit after a good length of time.

And the culprit would be??  Was it the loose bolts in both fenders?

Posted

Yes, it appears it was the loose bolts.  

 

On another note, family member works at another dealership in another state.  Her brother purchased 2019 like mine and had same issues.  His turned out to be pins in the brakes system on the front wheels.  The pins were too long and this caused them to rattle against other metal.   Replaced the pins with shorter pins that resolved the issue.

  • 1 month later...
Posted

I took my 2019 Trail Boss in this week for a rattle that sounded like it was coming from below glove box on the passenger side, noise worst at low RPM around 35-40mph. They pulled panels off dash and test drove as replaced one by one, noise still there. Another tech went along for last test drive with stethoscope and pinpointed the noise to below floor pan.  The problem ended up being the O2 bank 2 sensor rubbing on floor pan of cab causing noise, sensor harness was re-routed, problem fixed. Hope this helps. Good work to my local Wollam Chevy. 

  • 3 months later...
Posted

The rattle begins at 800 rpms on a 2020. The problem is the glove box strut retainer clip is not attached. Remove glove box and strut and re attach. Boom youre welcome

Posted

Any of you had a rattle with the passenger (or driver) dash speaker grille? Thought it was my glove box but turns out its this. Assuming it comes off with clips? Didn't realize that the grille is this whole part. 

Door Speaker.png

Posted
4 hours ago, hotrodz37 said:

Any of you had a rattle with the passenger (or driver) dash speaker grille? Thought it was my glove box but turns out its this. Assuming it comes off with clips? Didn't realize that the grille is this whole part. 

Door Speaker.png

I know on the k2's part number 3 which is a plastic cover directly under the steering wheel has 4 bolts behind it that work loose. Unless the mounting has changed for the 19's the dash is literally the same thing so anyone still having issues that's a easy place to check for a rattle. It always sounded like it was coming from the passenger side dash too for some reason.

  • 10 months later...
Posted
On 7/31/2019 at 9:41 AM, derek01f said:

Yep, sure enough was missing the bolt that connects to the backside of the mud flap.  The dealership mailed me a bolt, but it was wrong one, so I'll probably have to take it in to get the correct one on.

 

On 7/31/2019 at 9:43 AM, eppieguy said:

I had the same issue, missing bold from the mudflap. Rattle Rattle Rattle.

Would either of you mind sharing a picture of the location of the missing screws? It looks like I may have some missing, but both sides don't have the screws.

IMG_0185.jpeg

  • 1 month later...
Posted
On 11/19/2020 at 1:57 PM, 2020SilveradoCC said:

 

Would either of you mind sharing a picture of the location of the missing screws? It looks like I may have some missing, but both sides don't have the screws.

IMG_0185.jpeg

Anyone have a picture? Or can you tell me based on mine if I have the missing bolt or screw?

Posted

It would be under, pointing up towards the windshield.

7BAFFBBB-834F-4F7B-879C-21ED05EFC7F6.jpeg

  • 11 months later...
Posted
On 1/1/2021 at 6:28 PM, eppieguy said:

It would be under, pointing up towards the windshield.

7BAFFBBB-834F-4F7B-879C-21ED05EFC7F6.jpeg

Thanks for the image. I have the same rattle on RHS of my '21. Will verify.

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

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