Jump to content

Recommended Posts

Posted (edited)

Man I was sitting in the truck on New Year’s Eve warming it up. Started hearing a sizzle/hissing sound, looked back saw a little smoke from the little box were the slider meets the passenger side window. Turn back to turn the rear defrost off  and hear a Big Bang. ?  This is my 17 Sierra AT

 

I am no tech but I only come up with the rear defrost or slider. From the picture u can see the break started from that slider connection.

20BF2371-9398-450C-93CE-690A80FD4C49.jpeg

Edited by Impala_98
Posted (edited)

Many, many posts on this exact issue. In Canada, there is a recall because of it but the U.S. has been very slow in responding to a fix. Some have been able to get service before having the window shatter but those that had the shattered window happen have had mixed success with getting GM to cover the costs of replacement. Mine luckily hasnt shattered and since I have a topper covering the bed, and the defrost us basically useless to me, I went ahead and pulled the rear window defrost fuse so that it also wont activate when remote starting. If a U.S. recall ever materializes, I may put the fuse back in and take it in for the recall...

Edited by mikeyk101
Posted

Dealer confirmed they have been seeing more of this happening here in the southeastern Michigan area. The they stated the parts need to fix it are on back order.

Posted
1 hour ago, Impala_98 said:

Dealer confirmed they have been seeing more of this happening here in the southeastern Michigan area. The they stated the parts need to fix it are on back order.

The parts for the recall are all allocated to Canada to answer the recall so hence a US back order.

 

I'm really surprised the US GOV. never did the same recall... GM should step up and just issue the recall in the US as well.

 

Of course since the did the recall on mine it's had a rattle in the back behind the panel.

 

 

  • 5 years later...
Posted (edited)

Hello I have a 2015 GMC Sierra 2500HD and the rear window  shattered when I used the remote start feature to warm the truck up one winter morning in Maine. I've had the window replaced at my expense and have since pulled the fuse.

Im still waiting to see if GM will make good on this defect and perhaps I could have a rear defrost that works and be reimbursed for the rear window?

 

This is the same truck that I had to put a transmission in at 50k miles again at my expense.  GM is aware they have a transmission issue and rear defrost, but haven't issued a recall on either items to my knowledge. I have been looking...

 

Toyota is looking pretty good for the next truck at least they stand behind their product. I'm sure some or all remember Toyota frame replacement or truck buy back.... This said a lot for Toyota in my opinion!

 

Let's go GM after all the American people tax payers did bail GM out let's not forget and given what  the trucks cost. Can we get a quality product?

 

Ps sorry for the rant just a little frustrated with my purchase and quality....

Edited by TSO
  • Sad 1

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

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