Jump to content

Recommended Posts

Posted

I have an order for a 2022 3500HD SLE double/long 4X4 that was placed last month with Event Description 1100 - Preliminary Order Accepted.  As I look over the output from the Order Workbench I see packages listed but then some of the items that should be in a package are not listed.  For example, Driver Alert Packages I and II (PQB/PDJ) are listed but items in those packages like Rear Cross Traffic, Lane Departure and Lane Change (UFG, UFL and UKC) are not.

 

There are discussions on this chip gap on forums but I cannot find anything official from GM on what is happening and its mitigation process.  I would like to know if these items may automatically be installed at time of build if components exist?  Or, can these items be added at a later date by the dealer?  What are others doing with their builds?

 

Thanks

Posted (edited)

A lot of trucks are showing up without some of the features and GM gives a $50 to $75 credit depending on the feature.  When I was shopping for my AT4, I noticed that new 1500s were coming without the following features:

HD Radio

Rear Heated Seats

AFM/DFM

Auto Start/Stop

Wireless Phone Charger

Technology Package (HD Surround Cameras & HUD)

 

My truck was a Feb 2021 build delivered on 8/28 and it had everything installed.  I think new builds just will not get these features.  I believe that the safety package requires the technology package as it uses the surround cameras.

 

The other thing that appears to be on restraint are some of the assist steps.  My truck didn't come with any and I can't find any that I want anywhere.

Edited by TxTruckMan
Posted

After almost 6 months, it finally arrived.

 

Dealer priced at MSRP.

 

Dealer honored supplier pricing & $2,750 in rebates.  Absolutely a great deal in today's environment.  

 

Denali 3.0L   Produced one week before the duramax got stopped.   Has everything I ordered (Driver Alert II) except they deleted HD radio and read heated seats.

 

 

Screen Shot 2021-09-13 at 9.18.10 AM.png

Posted (edited)

Finally getting around to sharing my experience! I stopped at the dealer on June 16th just to get pricing and to see if I was even able to afford a new truck. The dealer gave me great prices on my trades, dealer discount, Costco discount and the GM discounts so I was happy to hear it was going to be possible!! They order my truck on June 18th. The only options I added were steering wheel controls, trailer brake, spray on bed liner and the 6.2L so there were no delays. They told me 8 weeks and my truck should be in which I thought was never going to happen. I took delivery on September 16th!! I came from a 05' Silverado, 5.3, 6" lift and 35's so this 6.2L is an insane difference in power! 

 

image2.jpg

image.jpg

Edited by bgardner119
  • 2 weeks later...
Posted

Thousands of new trucks parked in fields off I-75 in Michigan waiting for chips and/or missing parts that cannot be shipped out to dealers.

Posted

Has anyone heard anything about the 3.0 Duramax availability since the news of the halt in production in late August?  Mine is on hold for parts.  I'm seeing some 3.0 Duramax show up on the GMC inventory page (of course they are all sold) lately so it has me thinking that there are some being finished?  My deal doesn't have great updates on this so hoping people have info to share?

Posted

Yes, the dealership will have all the info on the 2022 Limited.  I ordered mine on 08/19/21 and as is scheduled to be built this week.  If you are waiting on the 2022 refreshed model, reports are they will be taking orders after the first of the year with delivery late spring, 2022.

 

Posted

My 2022 Limited AT4 with the 3.0 Diesel was built today, started after midnight.  I am about 30 minutes from the factory and know a few supervisors.....one told me that I was the 239th 2022 produced.  He was hoping to get pics but was unable as the truck was done and Bayed by the time he got to work.  Anyway, it will likely sit in that spot for another month before it is delivered but at least I was able to sneak in the order for the Diesel.  

Posted

I put a deposit on a truck (‘21 LT TB) that was “in transit”.  We all know that it isn’t.  Dealer is giving me the 4D00 missing parts story.   I contacted GM and gave them the VIN and asked for the build sheet.  The sheet shows the build date to be in FEB.  seriously? 
 

I’m hoping it will be here before Christmas.    How long do y’all think? 

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