Jump to content

windshield chip repair? leave it alone or buy the 10$ kit?


Recommended Posts

Posted

Hey everyone. So I was cruising a rural freeway yesterday and the guy in front of me decides to hit the brakes and then throw on his blinker and immediately hit the shoulder before the turn lane begins. He kicks a block of broken asphalt up at me. I saw it coming and actually ducked.

 

It left a triple chip in the window, not exactly in my line of vision but close. It is not deep and does not appear like it has or will crack anything. Its just the surface layer.

 

So my question is- should I just get one of those adhesive repair kits to fill the 3 little chips? (I've done it before on older vehicles. I can buy one for like $10 online)

 

Or is the repair pointless and I should just ignore it and wait for the inevitable crack and full window replacement down the road? could be weeks, could be years, but I know this glass won't last the life of the truck.

 

I tried to search for windshield chips and nothing came up, so just looking for pros and cons to the self-repair job.

Thanks.

Posted

Call Safelite, they can repair it professionally. Do this imeadatly before the chip turns into a crack that cannot be repaired. That's what happened to me, it cracked the very next day, before I could even call to make the appointment.

Posted

I second on Safelite or similar "local" glass repair shop..

Those $10.00 kits really do not work,, tried on 2 cars years ago and glass still started hairline cracks within weeks..

Proper windshield prep-work and great epoxy job was key..

 

Safelite did repair on my old 96 Tahoe that lasted 4+ years and 4 cold winters in Iowa until I sold it to buddy..

It's still holding strong at a $35.00 fix..

 

Cheers----K

Posted

Jeeze, now I feel like a fool for not calling my insurance co first.

 

Turns out they will send out safelite for a patch job and it doesn't even trigger my deductible. I should be able to leave the truck in the garage this week to avoid heat stress from the sun. I'll try to post a before and after photo of the repair if anyone cares to see their work.

 

Thanks for the tips!

Posted

If it has not been fixed yet, put a piece of clear packing tape on it to keep out the dirt. This also helps the crack from "running".

Posted

Insurance covered the cost of my chip repair that was done 10 years ago. All is still good, but will have to replace the windshield anyway due to serious hazing from all the small sand blasting it seems to have taken over the years.

Posted

Even it it doesnt crack further (it likely wont) if you dont repair it soon, it will get dirt in it and it will be more obvious when you do repair it. The sooner you fill it the less noticeable it will be. Most insurances cover the repair for free. A few bucks now saves them a lot of bucks later.

Posted

I got a chip in my 2014 Volvo when it was about 1 month old. I called insurance (liberty mutual) and Safelite did the chip repair. It last almost 3 years before it finally cracked on a hot summer day. Safelite then replaced the windshield with a new OEM Volvo to the tune of something like $1100 dollars! Covered by liberty mutual with no deductible.

 

Naturally, depending on the depth of the chip, some patches will work better than other.

 

A triple chip is a different story. I'm curious to hear Safelite's take on that. Let us know if they feel that a triple chip is even worth patching. They may recommend a replacement.

Posted

safelite is on the way to fix it this afternoon. I grabbed some before photos. The 3 spots would all fit under a quarter. they are pretty small.

 

(sorry, I couldn't get my phone to focus on the glass.)

post-172242-0-36285800-1505928923_thumb.jpg

 

The smudging is from when I licked my finger and rubbed it to wipe the dust off and see how deep the dings were.

post-172242-0-55728800-1505928975_thumb.jpg

post-172242-0-36285800-1505928923_thumb.jpg

post-172242-0-55728800-1505928975_thumb.jpg

post-172242-0-36285800-1505928923_thumb.jpg

post-172242-0-55728800-1505928975_thumb.jpg

post-172242-0-36285800-1505928923_thumb.jpg

post-172242-0-55728800-1505928975_thumb.jpg

Posted

Well the good news is they already came and fixed it.

Unfortunately, I'm going to be left with visible spots forever. I guess that's what I get for the free chip repair covered by my insurance. If I wanted new glass, I'm paying the deductible.

 

The guy said it wasn't even technically a "chip" since no glass was missing, it was more a "scratch" in the protective layer of the glass. He filled it with epoxy, but it made almost no difference in appearance. It is straight in front of my view, but below the horizon so hopefully it won't annoy me forever. The guy said it will always look like a bug spot. darn.

post-172242-0-46629700-1505931722_thumb.jpg


post-172242-0-52370500-1505931745_thumb.jpg

post-172242-0-46629700-1505931722_thumb.jpg

post-172242-0-52370500-1505931745_thumb.jpg

post-172242-0-46629700-1505931722_thumb.jpg

post-172242-0-52370500-1505931745_thumb.jpg

post-172242-0-46629700-1505931722_thumb.jpg

post-172242-0-52370500-1505931745_thumb.jpg

Posted

I have dealt with those before. Its harder to hide a scratch, than a chip that penetrates to the plastic layer. Many glass shops will waive the deductible for you, so that the windshield is free. Here is how they do it:

 

 

If you don't have insurance, they charge you $200

 

If they use your insurance, they just increase the cost of the windshield to $300 and then they pay your $100 deductible for you.

 

You get the window for free, the insurance pays their own deductible, and the glass shop still gets their $200.

 

I was really surprised to find out that its standard practice to inflate the repair bill if it goes through an insurance company. Its normal practice, and the insurance companies accept it. Same thing with car accidents and other comprehensive claims.

 

My neighbor broke his back window with a weed eater rock. The glass shop quoted $500. He sent the bill to the insurance company. The glass shop rejected the payment from the insurance, and "adjusted" the bill to $1,500 because it was through insurance. The insurance company accepted the new bill and paid it. Crazy.

 

Anyway, just call around to the local glass shops and tell them you want to get a windshield and that you want them to take care of the deductible.

Posted

Anyway, just call around to the local glass shops and tell them you want to get a windshield and that you want them to take care of the deductible.

 

Interesting. I'll keep that in mind if I decide I can't stand the scratch.

 

Grand scale of things its pretty minor and since it is a pick-up truck that I use as a truck- it already has a few dings and whatnot. I'll probly just ignore it for now. Even if its free to me, a replacement would show up as a claim on the ole insurance. If I don't need to do that, I probly won't.

Archived

This topic is now archived and is closed to further replies.

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