jeffro01
Active Member
I wish this wasn't referred to as a 'user error'. The correct terminology is 'use error', which doesn't assign blame. A use error can be the result of a user error, an error in the design that makes it difficult for some users to do the right thing, or an implementation error.
I suspect (because maybe I know someone who has done it -ahem-) that when coming off AP by taking control of the wheel, people forget that they have not yet released TACC. And when the traffic ahead clears by virtue of turning or cars getting out of the way, the vehicle accelerates just as designed. And yes, the blue circle around the max speed is illuminated, so the user has been told ... but most of us are used to seeing the word 'cruise' somewhere near the speedometer, confirming that cruise is enabled.
This does not mean the implementation is wrong. I'm now able to spot that blue circle and know that TACC is operating. I don't want to see that change - so the idea of user configurable settings as to the rate of acceleration is a great one. Perhaps when taking the wheel back from AP, TACC should also be disabled. That way, IF I wanted TACC to continue, I'd have to enable it again. Which would be no big deal and ensure that I was well aware that I was still driving with TACC on.
Exceptionally well worded as usual.
Jeff