Perhaps your point would be better understood if you toned it down a notch. No need to be defensive.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Perhaps your point would be better understood if you toned it down a notch. No need to be defensive.
Exactly!
We all know that kids never trip and fall - especially if they are running around and maybe being distracted by seeing a car drive itself.
All humans are equipped with the at least the 2003 version 3.11 auto-gyroscoptic-self-righting system.
Kids.
Never.
Fall.
And it isn't as if people ever did things like put their kid strapped in a car seat on top of a car and drove away, so it is impossible that anyone would accidently put them in front or back of a car.
In the history of cars, no parent ever put their kid on the ground after unpacking the car.
Never.
Ever.
Happened.
Chillaban, let's hope Tesla takes you up on your suggestion. There's no substantial extra effort added by following a parking button double-click with a touch of an "OK" button on the touchscreen, but this simple additional step should eliminate the type of situation that occurred here. It's just too easy to accidentally double-click the parking button, thinking you only pushed it once, and then step out of the car without looking at the touchscreen. Outside noise could cover up any tones generated by the car.
Exactly. I think this is very poorly designed. Even if you hit the park button twice, there should be a confirmation on screen to ACCEPT, not CANCEL the choice.
So where was the car thinking of going to "Summon" itself? Joyride? Picking up girlfriend at the next block? If it's a "Summon" feature, it should work only at a designated place (like in your home), and GPS should've indicated that the car wasn't anywhere near that.
Unfortunately someone has to get hurt by this accidental double-press, which is rather easy to do, before they will change the operation. Imagine if there's a baby in a stroller in front of the car and it starts moving because someone forgot to CANCEL the feature?
Last edited:
Tam
Well-Known Member
That's great! It's a welcoming step beyond double-pressing-the-parking-stalk to make sure if the act was intentional or not.
Last edited:
So you're saying "the car isn't going to run over someone... without fail and without question". But then you acknowledge it wouldn't detect a baby, which is contradictory. How about a toddler that fell on the ground? Or even an adult laying on the ground? can the car detect that?
Ulmo
Active Member
Here is my guess: the driver was twitchy, and probably activated the autopark on the gear stalk by pressing 3 times rather than one to just park.
Here is my reason for guessing he is twitchy: calling the news reporters was a very twitchy reaction. I think he has a twitchy personality.
Having said all that, using the park button to make the car go someplace is probably a bad idea, for just this reason. Tesla should put more buttons for this feature (perhaps on the big touchscreen), rather than have cryptic buttons on the steering wheel for those functions.
Now, back to the driver of the trailered car:
Here is my reason for guessing he is twitchy: calling the news reporters was a very twitchy reaction. I think he has a twitchy personality.
Having said all that, using the park button to make the car go someplace is probably a bad idea, for just this reason. Tesla should put more buttons for this feature (perhaps on the big touchscreen), rather than have cryptic buttons on the steering wheel for those functions.
Now, back to the driver of the trailered car:
- Why did he park so close to the trailer?
- Why did he park the wrong way on the road? In many states, it's even illegal to park that way.
- Doesn't he realize that the tractor for that trailer would need to pull in right there, and he was blocking it? Why would he do that?
Putting a function that's going to move the car when you get out on the park button is a mistake waiting to happen. The car should have chimed when he did that and the center screen should have changed to the park mode, which would have alerted most people something was wrong, but some people are oblivious. I agree that some other control would be a better choice for such a function.
The center screen did display a large Autopark pop-up, but it didn't require user interaction. Now with software update 2.18.77, just released, it does require interaction.
jeffro01
Active Member
Yeah I'm not going to keep defending my position on this. You are free to disagree as you wish but I stand by my assertion.
Jeff
Ulmo
Active Member
I agree. The KEEP THE CAR STOPPED NO MATTER WHAT WHEN I LEAVE and MAKE THE CAR GO SOMEPLACE ON ITS OWN buttons should not be the same button, and GO SOMEPLACE ON YOUR OWN should have obvious feedback.
I like the mechanical parking brake foot pedal on other cars because it is obvious when it is on. These new "e-brake" features get me pissed off because I think they're not obvious when they're on, so I have to spend extra time verifying this. If anything, they should use a knob like on tractor-trailers. But it is up to the driver to know when their brake is on. For instance, no licensed Commercial Motor Vehicle driver should ever complain "I didn't know that pushing in the parking brake button would release the parking brakes" and get away with it. In a CMV, there's an obvious physical position that means parking brakes engaged. The best analog I can think of on the no-buttons Tesla is the screens. The driver dash should say "PARKING BRAKE ENGAGED" and/or "AUTOPARK ENGAGED", and they should be different colors (such as RED and YELLOW, respectively).
I just watched
- Huge improvement by Tesla: now, the car will not automatically go start driving around once you've hit the button that parks the car (twice). I still see a potential for a toddler sitting in the passenger seat to hit a button like his dad did before, and the touch screen would take the command. I'm not sure when this would happen in any type of situation in which the driver would not realize the car was put into autopark mode (hazard lights on, green notice on the dash), except my accident scenario below, but in that case, probably the toddler wouldn't be feeling that comfortable, and themselves would be in accident mode.
- Even back before this improvement, the car makes a special beep, the dash lights up GREEN as in "I'm about to go somplace!!!", the main screen shows that it is in an autopark mode, the flashing lights start lighting up everything with flashes, the flashing light relay makes a huge huge clicking noise, and someone would have to be EXTREMELY irresponsible to not be paying attention to that.
And still, Tesla shouldn't overload a STOP button with a GO function. I can imagine an emergency scenario where this could happen: You are driving, then an accident happens, and you have to exit the vehicle very quickly. Perhaps even your Tesla was hit, which as you know, automatically starts the hazard lights. You are super nervous, get out after hitting the parking brake, to attend to some emergency element, such as oncoming traffic or someone who could be hit by oncoming traffic laying on the ground or whatever emergency element is there. Well, since you were nervous, you double-clicked autopark and the Tesla starts moving around, perhaps toward someone laying on the ground after an accident, or gets in the way of traffic, possibly causing more accidents, possibly other cars running over people on the ground. Not cool.
So, while I still blame the original driver of this accident, part of me says "thank god", because Tesla fixed this problem as a result; the original accident was a very peaceful accident. The car was unoccupied and the trailer was unoccupied and no innocent bystanders were hurt. And, I also blame Tesla for the accident, and I hope this kind of STOP button creates GO reaction never happens again.
Last edited:
Similar threads
