Jump to content

Recommended Posts

Posted

After showing them the TSB which says both thermostat and radiator are covered, some debate, the service advisor called someone at GM.  That person at GM verified year/make/model/ engine RPO code, and told the service advisor it is in fact covered by powertrain warranty.  Thermostat, radiator, coolant, those little clips for the trans cooler lines, and labor.  If anyone wants help talking some sense into their service advisor on this issue, I’m happy to help.

  • 4 months later...
Posted

My 2014 Sierra SLE 5.3 w/68K miles started a while back running a lil less than 210 it was used to. I was not too concerned at first but the needle was drifting cooler as time passed so I hooked up my OBDII scanner and saw it was cycling between 160-175 running down the road so I thought no biggie till I read here about the cracking radiators. I called my Dealer but was told no warranty too far out so I bought a new Thermostat and some Dex Cool and swapped it out this morning. Job went well and now I am reading 210 on my gauge and scan tool. Hopefully I caught it before any radiator damage it looks good where I can see no signs of any leak.

Thanks for the thread Guys sure makes shade tree mechanic lives easier.

 

Yotaman

  • 4 weeks later...
Posted
On 11/18/2018 at 8:02 AM, mutex said:
I have had this problem on my Silverado Midnight Edition built early 2015 and bought new on July 2015 a month ago.
 
I went for an oil change at 67000KM and they found my radiator was leaking. At first Dealer asked me to pay for a full repair and then I found the recall on this Forum (Thank you). The Dealer/GM Canada told me the recall was for 2014 models only and they did not want to repair it under the 'Powertrain Warranty'. They asked me to pay 50% of the repair as the initial 3 years warranty was expired. I do not understand why GM does not fully honor this warranty (Powertrain) on early 2015 models that does have the same problem as 2014 models. The GM representative told me GM was doing modifications on their truck every year, but they did repair my truck with the same parts as of the recall. I can also tell the leak was minimal and was probably there for at least a year. Although I am a Chevy fan since I am young, I lost my confidence in GM products and might go elsewhere on my next purchase.
 
So I would like to advise every Canadian early 2015 owners to ask the dealer to check the Radiator before the initial 3 years warranty expires.
 
 

I realize this is a old post, but did you ever get them to fix it? Canada side of things seem to be lacking in comparison to the state side.

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