I did a little fiddling when I went to move my car from the Chargepoint. I was able to reproduce the behavior of a double pull being required, yet sometimes it will go to Drive when the Easy Entry has not finished its job.
I tried to get it to engage Autosteer/TACC, but it said Cruise was unavailable, even with a car in front (and showing up on the screen) - may be geofenced to some extent - or maybe some other requirement was not satisfied.
In any case, further experimentation needed to see if this is actually reproducible.
One thing I was thinking, though - normally you would have your foot on the brake when trying to engage Drive (it's required!). I
f your foot is on the brake, then it should not be possible to engage either TACC or Autosteer (they would be immediately canceled I assume).
So, it's a little mysterious how this could ever happen - unless you actually follow this sequence:
1) Get in car, hold brake.
2) Shift to Drive
3) Look down, see the car is still in Park, based on the screen indication and lack of parking brake removal (audio cue would be no parking brake release sound)
4) Release Brake (as you do this, the delayed shift to Drive occurs without further input)
5) Try to shift to Drive again, without pressing the brake - this would be a TACC command presumably (but the screen displays Autosteer not available - it does not reference "Cruise control" in my experience, usually).
In this sequence, it would be possible to send a TACC or Autosteer enable command, because the foot is not on the brake. But you SHOULD have your foot on the brake if you're trying to put the car in Drive.
So the questions are:
1) Is there some "defeat" which allows the car to try to enable Autosteer/TACC even when the foot is on the brake (and if it did enable, wouldn't it immediately cancel)?
2) Why would you shift to Drive with your foot off of the brake? What is it about the car's behavior that causes users to do this? I've done it, and the OP has done it. I don't quite understand why I would have done it. (I guess I have no control of my actions.
)
3) Why does the car complain about Autosteer not available? We're talking about two stalk pulls here - the first one puts it in drive, and the second one should only engage TACC - not Autosteer. I would argue that from Park, THREE pulls of the stalk should be required to even attempt to engage Autosteer - not two (two would be for TACC). Now, to be clear, the OP thought it wasn't Autosteer, but it was TACC causing his issue. But the question is why does the car complain about Autosteer not being available? We only pulled twice from Park - under no circumstances should that be interpreted as a request for Autosteer. Right? I think it says "Autosteer not available" (it might say "Autopilot not available" but I don't think so)
Like I said, further investigation needed to develop a full understanding, if you have concern about this. I guess I'm not too concerned because I haven't had the car accelerate...yet.