Jump to content

GM Protection Plan comes through again...

mikeyk101
 Share

Recommended Posts

mikeyk101 Senior Enthusiast

mikeyk101

Posted
Posted

I just picked up my truck from dealer and very glad I spent the money to get a GM Protection Plan. It has more than paid for itself now. I found out when getting my oil changed that during the inspection, they discovered the transmission cooling lines were leaking as well as a leak from the upper oil pan. The repair bill for this came out to just over $2900 including 2 days of car rental and was covered by the plan. All except for the oil filter??? I was to pay about $8 for a new oil filter. I slightly complained but was respectful because the oil filter was practically new from the recent oil change. I said that if I had known beforehand, I would have just waited on repair to be done instead of having the oil changed. On top of this, all that new oil had to be wasted and changed out as well. But surprisingly the 8qts of new oil was covered under the plan. The service guy said that a new oil filter was just part of the repair but not covered under the plan. I groaned that had I been notified of the oil pan leak beforehand, I would have just held off on oil change and would have gladly paid for the oil filter now. He begrudgingly agreed and finally said don't worry, it would be taken care of and it was.  

 

This is the third time I have been able to take care of something with the plan. I've actually been pretty lucky with this truck so far. I haven't had anything too major but the repairs I've needed have been a bit pricey. Besides this repair, I had a fuel injector that was stuck open and needed to be replaced last year and a crack in front differential housing 2 years ago that was also covered. I never found out why that crack happened and was a bit surprised that the plan covered it.

 

When I got the truck new in 2016, it already had almost 600 miles on it. I got in touch with GM and after haggling a bit, I got them to extend the original bumper to bumper from the 3 year 36k miles to 4 years 60k miles. That ran out Mar of 2020. Prior to it running out, I was still able to buy a 5 year 60k additional Protection Plan. I went with the Platinum and $0 deductible. So I am covered for another 35k (125,000) miles and until Mar of 2025. This last repair has by itself covered that cost. After seeing post after post about lifter failures, torque converter failures, condenser failures, etc, I am praying that if this is going to occur, it needs to happen in the next 2 years before it costs me money. I'm at 7 years of ownership now and plan on keeping this truck for a quite a few more years.

  • Like 3
rav3 Senior Enthusiast

rav3

Posted
Posted

Alway good to hear about a happy out come.

  • Like 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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.
    • KARNUT
      2027 GMC Sierra: Official Discussion

      By KARNUT · Posted

      It was all part of the tiny bit of fuel savings it goes towards what was mandated by the government. Much like cylinder deactivation. That was relaxed by the recent administration. All that doesn’t help the individual buyer. But as a whole helps the manufacturer to try to reach the previous ridiculous past mileage per gallon mandate. So yes it was mandated and added cost to the vehicle. 
    • newdude
      2027 GMC Sierra: Official Discussion

      By newdude · Posted

      You do realize that auto stop/start...was never mandated by the fed...right?     EPA Says It's 'Killing' Stop-Start, and Here's What Automakers Have to Say   "Start‑stop technology has never been federally mandated, and the EPA’s recent action removes regulatory incentives associated with it rather than prohibiting its use."
    • Jsdirt
      2027 GMC Sierra: Official Discussion

      By Jsdirt · Posted

      Anytime the government mandates something, you can bet on it being absolutely senseless.
    • c4racer2
      summer road trips in the 2026 2500HD

      By c4racer2 · Posted

      just logged my best MPG for one leg this am - drove home from the Denver Airport, 45 min drive - all freeway, lots of traffic so speeds were limited and some stop and go, got 17.7 for the ~30 mile trip.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...