Jump to content

Recommended Posts

Posted

I have owned my 20' Sierra SLT for 2 yrs and have always noticed some small amounts of water on my driver side rubber mat, I initially thought it was from windy rain making its way through the door seal, but we have had some heavy rains this year that I noticed the water stain on headliner above the driver A-pillar, and noticed the water dripping down behind the dash, near the obd2 port...originally thought the source could be the shark fin antenna, so I partially lowered the headliner and ran a hose over the truck, only to realize the source is the sunroof drain...HAS NO DRAIN TUBE ATTACHED, looked to see if it had disconnected but it is not installed at all, anyone else have this happen?

IMG_1448.jpeg

Posted

Sad thing is its only a $7-$8 part…and drips down into a location of the truck that can cause thousands in repair…I have trust issues with dealerships and would attempt to add drain hose myself but can’t seem to find an schematic or diagram showing where the hose routes down to… if anyone has any idea, I would appreciate it.

 

im out of dealer warranty and my extended warranty is iffy about water issues even though I’m pretty sure this is a “manufacture error” I mean its completely missing.

Posted

I had originally posted this in an old thread to see if I could find any users with same issue. All the rain I got in the last few days in the northeast and now the issue appears to be worsening and I now have my beautiful truck missing panels so I can keep my driver side fuse box dry

 

I might even have to have the sunroof wrapped as a temporary fix.

Posted
29 minutes ago, BIGF46 said:

 

Sad thing is its only a $7-$8 part…and drips down into a location of the truck that can cause thousands in repair…I have trust issues with dealerships and would attempt to add drain hose myself but can’t seem to find an schematic or diagram showing where the hose routes down to… if anyone has any idea, I would appreciate it.

 

im out of dealer warranty and my extended warranty is iffy about water issues even though I’m pretty sure this is a “manufacture error” I mean its completely missing.

 

30 minutes ago, BIGF46 said:

I have owned my 20' Sierra SLT for 2 yrs and have always noticed some small amounts of water on my driver side rubber mat, I initially thought it was from windy rain making its way through the door seal, but we have had some heavy rains this year that I noticed the water stain on headliner above the driver A-pillar, and noticed the water dripping down behind the dash, near the obd2 port...originally thought the source could be the shark fin antenna, so I partially lowered the headliner and ran a hose over the truck, only to realize the source is the sunroof drain...HAS NO DRAIN TUBE ATTACHED, looked to see if it had disconnected but it is not installed at all, anyone else have this happen?

 

 

 

 

Book time its 5.2hrs do replace the tube.  It runs from the sunroof frame down the A pillar and exits through an outlet in the cowl area under the LF dash speaker region.  

 

Headliner gets lowered, A pillar trim out and the upper dash pad to properly access the hose/install a new hose.  

Posted

Thanks for the info @newdude I really appreciate it, I already ordered the drain tube, but now I’m thinking I should let a dealership install this as I am now afraid that the prolonged moisture to the fuse box on the driver side could potentially cause an issue later on and it would at least be on record that the truck was missing the hose in the first place.

  • 2 weeks later...
Posted

So my truck has been at the dealership for a week, so far it has been determined that the driver side front sunroof drain was in fact missing and appears to have never been installed from factory, and the water that had entered the truck for the past 5 yrs has caused corrosion to the driver side fuse panel and fuses which are currently being replaced, at the moment the dealership has been treating this as though my aftermarket warranty will not cover this and warning me of the costly labor that is accumulating. 
 

for something that is an original part of the vehicle that was neglected and missing I would think should be covered especially since my aftermarket warranty mimics a factory 5yr new car warranty.

 

I am in need of my truck back, but it looks like this could be a long drawn out fight where fingers are pointed and no one wants to own, I don’t think this dealership should be stuck eating this bill, but wish helping me get this covered by manufacturer was on there list of things to do for a customer 

Posted

If you’re not interested in using the sun roof seal it. It’s the cheapest way to go. I’ve done it. It took me minutes and the cost of sealer. Unless you’re under warranty of course. 

Posted

Yeah, once I’m out of this headache that may be what I look into as I never use it, I purchased my truck preowned so didn’t have a choice of sunroof or not

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