Jump to content

Recommended Posts

Posted (edited)

Yesterday was my first time driving my truck in snow and my wiper blades froze to the windshield.  It wasn't snowing real hard, and it's garage kept, so I started with a clean windshield.  The whole defroster and wiper design is terrible.  The defroster vent sits high on the dashboard, so it misses the lower few inches.  But then the wipers sit so low on the windshield that it is actually below where the windshield and dashboard meet.  So even if the defroster did blow lower, the dashboard still blocks the air from getting down there.  There is no way I see to heat that part of the windshield or the wipers.  You can see it in the pic.  Luckily I was close to home, but I would think on a longer trip the only way to take care of it would be to pull over and spray de-icer on it or clear it by hand.  But even when it did come free, the wipers worked for crap because they were frozen solid.  

The only other thing I can think of is installing some kind of defogger strips like the rear windows have, but I don't see anything like that online.  I felt it was such a safety issue I filed a complaint with NHTSA.  Anyone else have any experience with this and any fixes.  My first oil change is coming up so I will be seeing what the dealer says, but I don't see anything they'd be able to do, it the design of the truck that sucks.  

20210201_090707.jpg

Edited by Greg B
Posted

I didn't have that issue all last winter and this year (Maine).  I usually run my defrost on a fairly high setting (temp and fan).  I did get the occasion ice build up on the wipers and the where the wipers stop (on both ends of the range of motion).  

 

I always use rain x de-icer washer fluid so that helps to break up the ice with a spray.  With any truck I have had to sometimes remove the ice if it impacted the wiping ability.

 

Never had the wiper blades freeze to windshield.  I do let the truck warm up before using them (in the garage or outside).

  • 1 year later...
Posted

Yes! Horrible design! For the price of the truck you'd think they could have done some better planning. Even my '03 outback had a wiper defrost system. The defrost on high for over an hour did nothing in our big storm. I'm not lazy, I scrape, dig out all the snow I can, and the wiper blades and where they sit are still iced up.  It's not just you and your truck. Our is sometimes garaged but also not. We're currently out of town without garage access and have iced up wipers. It sucks. Driving with that problem is a little scary. I have a four hours drive to get home through rural MT, the last thing I want to have to deal with in encountering crap weather is my vehicle not working right. If you come up with a solution please post again. Our dealership said yep, it's a problem but had no solutions.

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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...