Jump to content

Recommended Posts

Posted (edited)
2 hours ago, goosehunter said:

 Did you have prices in front of you, ie base price and option prices?   Thanks!

 

 

Screenshot_20220128-170813_Gallery.jpg

Screenshot_20220128-170758_Gallery.jpg

Edited by 20Denali21
  • Thanks 1
Posted (edited)
On 1/28/2022 at 8:12 AM, 20Denali21 said:

Definitely one of the affected engines. I'd pass on it and wait for the 22.5 trucks at this point. It'll have a reissue VIN and they'll change it to a 22. 

 

Kinda feel that way, but damn, It's so close.   I'm at least going to have a look at it. Maybe they will offer some other incentives and it will drop the price a few more dollars.  I also feel like this thing was held up somewhere so they could do all the factory corrections before getting it to customer. Fingers crossed.  we'll see what happens. Maybe I'll hold onto my trade, in case of some catastrophic failure!

 

Edited by thekcwolf
Added content
Posted (edited)

I ordered a LT Trailboss on 12/27/21. It was accepted by GM a couple of weeks ago and given a production date of 2/21 this week.

Edited by rascal71
Posted

I ordered a 5.3 LTZ back in October and was told that GM had canceled my order based on shortage of 5.3 engines. I reordered with a 3.0 diesel on Veterans Day. Had a so-called guaranteed build date of dec 6th. Had been delayed 4 times since then now a build date of 2/21.  In all honesty they will probably have 22.5 on the lots before they finish with all of the LTD orders. If that happens I’ll switch over and get a 22.5. Mine is a repurchase from the leaking rear window that has been replaced several times and still develops leaks  

Posted
On 2/3/2022 at 11:01 AM, JohnCasey said:

I ordered a 5.3 LTZ back in October and was told that GM had canceled my order based on shortage of 5.3 engines. I reordered with a 3.0 diesel on Veterans Day. Had a so-called guaranteed build date of dec 6th. Had been delayed 4 times since then now a build date of 2/21.  In all honesty they will probably have 22.5 on the lots before they finish with all of the LTD orders. If that happens I’ll switch over and get a 22.5. Mine is a repurchase from the leaking rear window that has been replaced several times and still develops leaks  

I think you will be getting a 22.5 -- Feb 21 is the new production start date for 22.5 crew cab models.  They won't be building 22 LTDs and 22.5s simultaneously.

Posted

So is GM doing rebates if you order a truck kinda like ford does?  I've been out truck shopping but none seem to do more than like 500 off.

Posted
On 2/12/2022 at 9:24 PM, SuthrnZ71 said:

So is GM doing rebates if you order a truck kinda like ford does?  I've been out truck shopping but none seem to do more than like 500 off.

I've been in waiting since September. You'll be lucky to find one at MSRP. Basically they offer "incentives". Many dealerships place a "Market Adjustment" on top of the MSRP which you will also be lucky, to chisel them down on that cost, too. There's an article about GMC warning dealers of price gouging, but in this high demand market, you're bound to see some sort of price increase. I've seen dealers with prices on AT4's that have less options, stickered for what I'm waiting for which has all the options. 

Posted

Any guesses as to how much longer they will be making and shipping ‘22 limited AT4s? 
has the backlog of trucks sitting in various lots near the factories been depleted, or will there still be a few more months of new limiteds being shipped out 

thanks

Posted
On 2/13/2022 at 11:17 AM, KansasHawk said:

@Nathan Younghow did you get 6K off MSRP? I'm wanting to order a Denali ultimate as well and wanted to check. 

 

Thanks!

Call or text Mike at Robideaux.  Tell him Nate sent you and he’ll take care of pricing for an ultimate +1 (208) 755-9685.  

Posted

I went yesterday and put in a order for a  22 AT4 with the 3.0. Dealer told me 8-10 weeks for delivery, but we shall see. My 21 AT4 took around 6 months to be delivered. 

Posted
54 minutes ago, z28tranz said:

I went yesterday and put in a order for a  22 AT4 with the 3.0. Dealer told me 8-10 weeks for delivery, but we shall see. My 21 AT4 took around 6 months to be delivered. 

What kind of pricing?

Posted
22 hours ago, Nathan Young said:

What kind of pricing?

Paying MSRP for the truck minus a couple dealership discounts for return buyer and veteran. 

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