Jump to content

Recommended Posts

Posted

For those who have received their trucks (I am still waiting), and do not have, heated wheel and/or seats, did you ask the dealer when the retrofit might happen?  I am just curious, as the waiting game seems to be something GM is good at making us do.  

 

Lee

Posted

When I picked mine up at the end of April, the dealer had me sign paperwork that said Q3 for the heated steering wheel and Q4 for the parking sensors.

 

Hopefully you get yours soon 🤞

  • Like 2
Posted

Q3 is what I've heard as well.  From the dealer and from the GM web site. 

Based on how long it takes to get trucks out of a parking lot,  I'm guessing Q3 of 2025.😉

  • Like 1
Posted
15 hours ago, sheath said:

Q3 is what I've heard as well.  From the dealer and from the GM web site. 

Based on how long it takes to get trucks out of a parking lot,  I'm guessing Q3 of 2025.😉

2025..ouch...LOL

Posted

put my place in line for a 22 in late Jan guy told me they were talking JUN/JUL for the retrofit, my truck will be build mid next month said it will be a crap shoot if its built with it. 

Posted

In reality, no set date ONLY estimates. 

  • Like 1
  • 1 month later...
Posted

Purchased mine at end of April also and have not heard a word on retrofits either. I will be pulling my camper this weekend on a somewhat long trip. I plan on getting first oil change when I get back and plan to ask about it then.

  • 2 weeks later...
Posted

Purchased in Jan and was told end of the year. Upon signing paperwork said Q3 and Q4. Salesrep said that was being optimistic. That I believed.

Posted

I had my truck in for oil change a week or so ago. I asked them about it and they said my dealer in which I purchased it from should have placed an order for the parts on day i purchased. I called my salesman and he told me "not correct." He said GM will eventually send me a letter and notify me on when parts are available. He said it will be similar to a recall notice.

Posted

I'll probably end up selling the truck before the retrofit happens.  If the prospective buyer gives me any grief, I'll just tell him I've been driving it this way for 40 years sonny... 😉

  • Like 1
  • Haha 1
  • 2 months later...
Posted

Anyone have any updates on this? Has anyone actually had this done on a 2022 or gotten any info from GM or a dealer?

Posted

 Sierra rear out board heated seats.


For those that have NOT gotten this option due to micro chip shortage.
have you added it back in, or have the dealer quote and install the missing parts?
(provided they are able to get them in due time I presume)
can we presume the harness is still there?
also would the heating elements still be in the seats?

If successful, do you have a cost, parts list?
Was the PCM needing programming at dealer to activate?

Posted

got an email from gmc that they will notify me and the dealer when my parts are available,  asked parts at the dealer today, said they have received a few but not on a steady basis

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