Noted

  • Thread starter Thread starter Ankh
  • Start date Start date
  • Replies Replies 1
  • Views Views 3K

Ankh

New Member
A friend of mine, who’s an avid Tesla fan (and all things Musk, just not the man himself) & owner is constantly proselytizing the car’s virtues. When I made the commitment to buy an EV, I ended up with a ‘23 Kia EV6 GT Line. While I believe that Tesla is a remarkable achievement in the realm of autonomous driving, I’m keenly aware of its design, aesthetic and functional faults.
He was driving us home autonomously from a group vacation last night and on a major, 8 lane highway, it braked hard as we approached an overpass. Could it have been the Tesla’s evolving hive mind response to a solid object in its path being navigable versus warranting a hard stop?
That particular conundrum previously resulted in a sleeping Tesla driver being decapitated when his car autonomously ran under a tractor trailer.
Mystified, even tho it immediately self corrected, we asked him why. He had no explanation, even tho he’s an electrical AND computer engineer and probably has a more intimate understanding of his car, than of his wife [emoji57]
I let the moment pass w/o needling him about the glitch.
As we exited the highway, it verbally cued him to take the exit. I asked him if it was still in autonomous mode?“
Him: “Yes”.
Me: “Then, why is it verbally/audibly cueing? Is it telling itself where to go?”[emoji57]
Just couldn’t pass that one up


Sent from my iPhone using Inside EVs
 
He was driving us home autonomously from a group vacation last night and on a major, 8 lane highway, it braked hard as we approached an overpass.
I have traced the reproducible ones to areas that were under road construction or repair. You can check by using Google Earth and look at the earlier versions of those road segments. This is mapping error of Google mapping that takes whatever their camera equipped cars show on any given day and has almost no way to correct. The clue is the indicated speed sign on the display will flip to a much lower number and then quickly clear as you pass through the problem area.

The proper answer is for the driver to hit the "voice command" mode and clearly state:
  • "Report this location is not a stopping or construction zone."
The fault shares two sources:
  1. Bad Google Map snapshot.
  2. Use of flawed Google Map data over camera data and signs.
It used to be these "phantom brake" events tried to pull your teeth out with hard emergency stops. Lately, they are softer, slow downs giving an alert drive enough time to hit the accelerator. Still socks!

Bob Wilson
 
Back
Top