Jump to content

Recommended Posts

Posted
1 minute ago, newdude said:

 

 

Go aftermarket.

Yeah figured that could be easier. I probably won’t add them but was just wondering. 

Posted

My 22 SLT HD already has the control buttons on the dash so I assume the chip is buried in the seat ? I know replacing the actual seat heating pad is a MAJOR seat tear down, is the chip the same ?

Posted
On 12/4/2022 at 6:28 PM, Cheekster96 said:

Whole new panel plus new screen.

How long did it take from the time the dealer was able the parts to when they arrived and could be installed?

Posted
On 12/4/2022 at 3:28 PM, Cheekster96 said:

 plus new screen.

why would you need a new screen?
mine have buttons on the center stack and there is an icon on the screen. the icon is surly in the software

Posted (edited)
On 12/5/2022 at 12:14 PM, kevin74 said:

Still waiting. Bought a 2022 LTZ back in September (found one in transit to dealer and bought it before it arrived). Picked it up the 8th of September, still waiting for the heated/cooled front seat bottoms and the parking assist. 

Seats are "ventilated", no doubt a godsend for those suffering from excessive flatulence and something to watch out for when  buying a used vehicle.

 

spacer.png

Edited by It's Tim
  • Haha 1
Posted
11 minutes ago, It's Tim said:

Seats are "ventilated", no doubt a godsend for those suffering from excessive flatulence and something to watch out for when  buying a used vehicle.

🤣 LOL, I never thought of that - although my last 2500 was a High Country and had the ventilated (cool on my ass) seats and there was a funny smell in the cab for about a year after I bought it (used). I plan on keeping my current 2500 for the long haul, but I'll try to lay off the chili just in case 🤣

Posted
17 hours ago, Pryme said:

What was your need for the truck for such a short period of time? 
 

See if we could move the fleet away from Diesel.  We can't due to the type of loads & the mountainous terrain we drive in.  But we have figured out a work around that will make our lives better all around. 

So my vehicle no longer needs to be a full size truck.  That really opens up the opportunities. 

Just need to make sure if the next vehicle has heated and ventilated seats, we hire a good "seat sniffer".:cheers:

  • Like 1
Posted (edited)

for those that got retrofit 

 

are they doing FRONT and REAR ?  seats

Edited by Mic_
spealing erors
Posted (edited)
6 hours ago, kylant said:

why would you need a new screen?
mine have buttons on the center stack and there is an icon on the screen. the icon is surly in the software

 

 

The faceplate.  That radio faceplate that the screen, HVAC controls, etc. attach to is why.  GM doesn't sell just the faceplate.  They only sell the radio screen/faceplate assembly and only through GM approved Electronic Service Centers and not GM directly. 

 

All HD and some 1500s that are missing heated seats were built with non heated seat radio faceplates and don't have the holes present for the seat control switches.  

 

See below:

 

 

s-l1600.jpg

s-l1600 (1).jpg

Edited by newdude
  • Like 1
Posted
On 12/5/2022 at 9:09 PM, ShotgunZ71 said:

How long did it take from the time the dealer was able the parts to when they arrived and could be installed?

I ask that because of the reports of modules/chips ordered, but no or slow shipment. Hopefully people aren't getting led along to get their hopes up.

Posted

I was at the local GMC dealer and talked to the Service Manager.  He said GM was trying to get this completed by the end of this year.  Then said "...but don't get your hopes up."

Had a bit of a laugh with him. 

He is convinced they are trying hard to get this done.  He's been around plenty long enough to separate the chaff from the wheat. 

Posted

My GMC didnt come with park assist,  and cant remember what else.  I do have heated seats,  but they dont come on even when the option is selected for remote start, is that something else. 

Posted

Seems my dealer had no intention of contacting me for my "Seat Module"

 

I called them today and they said if I got a email from GM, they said the part must be available, and they will order it,  and in about 2 weeks they will schedule me a 2 hour appointment for the module install in each seat ...

 

Kinda lame the way they handled it

 

I could have been waiting forever +-

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

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