Jump to content

Recommended Posts

Posted

Anyone getting a popping noise from their roof?  Every morning when I pull out of my garage and go over a slightly angled transition between my driveway and the street I get a popping from the roof.  I've heard it several other times when driving at low speed as well.  It sounds like the sheet metal is flexing, like if you were to slightly indent a piece of sheet metal, it slightly indents and then you push it in another spot and it pops out of that indent.  I have gotten a very similar noise from the lid on my washing machine.  I do not have a sunroof.

  • Like 2
Posted

I have a similar sound, but mine sounds like a loose clip shifting when I come to a sudden stop, turn sharp etc.

 

I've learned long ago to not let interior noises/rattles irritate me.  If you let them, the dealer will end up tearing apart the interior, and I gaurantee it'll never be the same. Noise may be gone but you're left with ill fitting panels, and scratches everywhere.

Posted
On 5/3/2019 at 11:27 AM, Bftx said:

I've learned long ago to not let interior noises/rattles irritate me.  If you let them, the dealer will end up tearing apart the interior, and I gaurantee it'll never be the same. Noise may be gone but you're left with ill fitting panels, and scratches everywhere.

Ya, I try not to go into the dealer at all unless necessary.

Posted

my 2016 used to do that.. when I would take out of garage and the hot sun started beating down

Posted
10 hours ago, THE SILVERADO said:

Mine did this the first couple weeks, but seemed to have gone away recently. 

Hoping my goes away too then, I only have about 700 miles on it so far.

Posted

I have only heard the popping sound while washing my truck not while driving. When I spray water on the roof I do sometimes hear a loud "popping" noise.

Posted
5 hours ago, BlackLS said:

I have only heard the popping sound while washing my truck not while driving. When I spray water on the roof I do sometimes hear a loud "popping" noise.

Maybe the same noise, but different causes.  Cold water on hot metal might be having the same effect as my driving over un-level surfaces at low speeds first thing in the morning.  As long as it doesn't get worse I'm not going to worry about it.  I know the dealer would just give me "could not recreate" or "normal operating characteristics" of the vehicle.

Posted (edited)

Mine does it but its getting less and less and not as loud anymore . I had the truck out all day today and it didn't do it so I guess its about gone. Hell when I first heard it I thought a bird dropped a bomb on my roof.

Edited by Silverado4x4
Posted

I drive about 100 miles a day.  I get one clear pop on the way to my shop, and one on the way home.  Freeway, straight driving, normal consistent speeds.  Sounds like something dropping from a tree on the left rear side of the roof.  No trees in sight.  

 

Anyone had had this addressed yet?

  • 3 weeks later...
Posted

Bumping this to the top.  Anyone else getting this once and a while pop from the roof?  Mine is starting to do it more than once per drive now.  Hell, even my 7 year old daughter said “what just tapped the roof”?

  • 2 weeks later...
Posted (edited)

Dam, I am glad I am not the only one. Mine never had made any noise and then it randomly started one day and it drives me nuts. It sounds like something landing on the roof. I know for a fact that it is coming from the rear but I can't pinpoint. I thinking it could be coming from that rear spoiler these new trucks have but you have to pull down the entire headliner just to get to the damn thing. I really want to sound deaden the roof but I absolutely hate pulling down the headliner and wanted to avoid it for as long as I could. Just really curious as to what it could be.

Edited by Ericruiz911

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,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   6 Members, 1 Anonymous, 1,658 Guests (See full list)


  • Latest Articles

  • Posts

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