Jump to content

Can we talk about the omission of Adaptive Cruise Control

Chris Eaton
 Share

Recommended Posts

BSK New Member

BSK

Posted
Posted

I just bought a 2021 HD High County. I’m floored that this was not on my 80,000 truck. What a disappointment!

 

  • Replies 52
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Wiggums
Wiggums

The adaptive cruise control was the WORST feature in the car I rented in Germany, and could NOT turn the damn thing off! There's no speed limit so I would travel at 80 to 90 mph, trucks cannot go

KARNUT
KARNUT

I’m a driver not a rider. Driving is an art to me. Otherwise use Uber. Anti lock brakes, nothing else. I drove a car with all that. You still had to keep your hands on the wheel. I was uncomfortable t

CRApex
CRApex

GM needs to make this an option. For the old schoolers who don’t want it, they don’t have to order it then.  For the rest of us, make it available and have it available and ready on the first release

nards444 Senior Enthusiast

nards444

Posted
Posted
20 hours ago, BSK said:

I just bought a 2021 HD High County. I’m floored that this was not on my 80,000 truck. What a disappointment!

 

 

 

Ive noticed this on things.  No option on a 80k truck but yet they have it on a 40k SUV.  I get price points, engineering of systems etc and they all might have play.  But GMs option batching is terrible compared to rest tbh and up front.  Options make money  I can for one tell you 70%-80% Denali is the same as a work truck, and there is not 40k more in true value there just isnt.  but this where the big three make their money.

Knighti2 Enthusiast

Knighti2

Posted
Posted

Don't want ACC and glad its not there.  I like the HUD as I have it on my 2018 Camaro but to spend 4K+ to get it and have a bunch of "safety" garbage I did not want.  So No Thanks. 

  • 3 weeks later...
Hobbypro Enthusiast

Hobbypro

Posted
Posted
On 7/20/2019 at 12:25 PM, CRApex said:

GM needs to make this an option. For the old schoolers who don’t want it, they don’t have to order it then.  For the rest of us, make it available and have it available and ready on the first release of the new models, not 6 months later on the 1/2 model year.  They did this to me on my 15 3500 with the nicer mirrors.  Those should have been ready when the truck was debuted.  This discussion actually makes me want to hold off And wait until they update the new trucks in 6 months.

That’s not how that works. If added it would be lumped into a safety package that would be required for a tech package. Sure you could get a work truck but you would miss out on all the niceties because you don’t want the adaptive cruise. 

Hobbypro Enthusiast

Hobbypro

Posted
Posted

One of the primary reasons I bought my 21 Sierra was because it didn’t have the features like that. My Kia has it and I’m up to about 25 near misses due to the “safety” features. If my HD truck slams on the brakes or turns the wheel when I’m not expecting it that could do a lot of damage to someone. I guess that’s the difference though. I pay attention to what’s around me and tell my car what to do accordingly. If you don’t want to have to pay attention to the road in my opinion you shouldn’t have a truck this large. 

KARNUT Senior Enthusiast

KARNUT

Posted
Posted

I wouldn’t pay extra for it. I takes getting use to. You can adjust the sensitivity to it on our CRV. On two lane roads it pretty cool with traffic the speed varies. You have watch turn lanes it will hit the brakes when someone is moving over to make a turn. It comes down to sensitivity adjustments. 

CRApex Enthusiast

CRApex

Posted
Posted
6 hours ago, Hobbypro said:

That’s not how that works. If added it would be lumped into a safety package that would be required for a tech package. Sure you could get a work truck but you would miss out on all the niceties because you don’t want the adaptive cruise. 

Not rteally what I was saying. If it was actually available on a package when I bought you would be correct.  What I'm saying is they've had a history of adding options/features a half year into production.  I provided my example of the nicer mirrors  that came out 6 months later on my 2015 and it seemed like it might go that way again on my 2020 with adaptive cruise.  So far adaptive cruise hasn't happened and who knows if it ever will on the HD's.

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.
    • KARNUT
      2027 GMC Sierra: Official Discussion

      By KARNUT · Posted

      It was all part of the tiny bit of fuel savings it goes towards what was mandated by the government. Much like cylinder deactivation. That was relaxed by the recent administration. All that doesn’t help the individual buyer. But as a whole helps the manufacturer to try to reach the previous ridiculous past mileage per gallon mandate. So yes it was mandated and added cost to the vehicle. 
    • newdude
      2027 GMC Sierra: Official Discussion

      By newdude · Posted

      You do realize that auto stop/start...was never mandated by the fed...right?     EPA Says It's 'Killing' Stop-Start, and Here's What Automakers Have to Say   "Start‑stop technology has never been federally mandated, and the EPA’s recent action removes regulatory incentives associated with it rather than prohibiting its use."
    • Jsdirt
      2027 GMC Sierra: Official Discussion

      By Jsdirt · Posted

      Anytime the government mandates something, you can bet on it being absolutely senseless.
    • c4racer2
      summer road trips in the 2026 2500HD

      By c4racer2 · Posted

      just logged my best MPG for one leg this am - drove home from the Denver Airport, 45 min drive - all freeway, lots of traffic so speeds were limited and some stop and go, got 17.7 for the ~30 mile trip.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...