Also, to add, there is some really weird interactions between the cruise control speed setting and the perceived speed limits. Sometimes it’ll maintain the cruise control speed, despite the speed limit, and sometimes it’ll change the set speed. I usually set to 5 mph over the speed limit. The car will spontaneously lower the setting, but then raise it again to what I had it. It’s never gone over what I’ve set it, but I don’t entirely trust it.
Similar here, but when I press it the rear camera switches off, which is not that useful when backing up. So I just move the car 6 inches back and the alarm shuts up.
Well, that’s a weird design decision.
Truly. Thanks, Audi. I mean, it makes sense that the parking features turn off if you’re not parking. But still.
I can corroborate the same weird glitch. Sometimes the reason is clear: I’m accelerating into a slower car ahead of me. That usually happens in the special circumstance that the car ahead slowed for a turning car in front, I see the way has cleared and expect the car directly in front of me to accelerate very soon. In those circumstance the alarm is annoying, but I wouldn’t really call it wrong, just overly sensitive.
Other times it’s like you say. I’m not sure exactly why the car is yelling at me. Maybe I’m not slowing quickly enough?
At least it stopped doing the thing where it would alert for parked cars on curved roads.
I think I have my alerts set for “medium” sensitivity, and it’s fine. Mostly I get false positives, but any alerts are pretty rare, so I haven’t messed with it.
I don’t have enough experience with other cars with similar safety systems to know if the Tesla is better, worse, or about the same as others.
Oh another one
You cannot turn off the windshield wipers while in cruise control.
Is this on Autopilot (cruise control plus steering) or just TACC (traffic-aware cruise control)? My wife has had a Model Y for a couple of years now and I’ve taken it on a few road trips, but as far as I’ve ever been aware, when I’m using TACC, I set the desired speed with the thumbwheel and it maintains that speed, or the best possible speed given traffic in front. I swear I don’t remember it changing speed based on signage. Am I that oblivious?
Both. But it’s very dependent on the route. There are other routes (like I15 towards Las Vegas) where the Tesla is just fine holding the speed.
But there is something weird going on with when it decides to adjust its speed. I think sometimes the car is following the speed limit (and so adjusts the speed based on the perceived speed limit) and sometime it’s following the speed I’ve set (and ignores the signs completely).
I had the CC set to 45mph on a county road known as a speedtrap (hence using CC so my speed wouldn’t accidentally creep up). The Tesla decided that since I had at some point been on a freeway that it should reset my speed to 75mph.
I will never, ever own a Tesla for these reasons:
- They are Fugly
- This Thread
- Musk
Why after putting the car in park do I have to wait \frac{3}{4} of a second for the animation to finish before I can tap the screen to open one of the trunks or the charge port?
Why is it even using speed limit signs in the first place? It should have (either onboard or in the cloud) a database of road speed limits that it can cross-check against the GPS. OK, sometimes there are special conditions like construction that cause a lower-than-normal speed limit, but those signs are orange. So use the database speed or a speed on an orange sign, whichever is lower (and ignore the black-on-white signs).
It does, and originally that was all it had. It still uses that, unless it reads a sign overriding the map data. Reading signs was added later to fix some kind of errors, which ended up creating others:
Map based speed limits problems:
- Incorrect data on the map
- Missing data on the map
- Special conditions should override map data
Reading street sign problems:
- Reading signs that don’t apply (truck speed limit, “unless otherwise posted”, max left lane, etc.)
- Fooled by people adding a bit of black tape to signs (I’ve never seen this in the wild)
- Reseting the cruise control set speed to a “new” speed limit, when it actually didn’t change (this is a software error, and only happens sometimes, perhaps in combination with map conditions)
Right, but the “special conditions” signs are all orange. And missing or incorrect map data only needs to be fixed once, to fix it for the entire fleet.
Here they are white, often with an orange border. I’ve also seen the orange signs you mention. Sometimes they are white with orange flags on top. Maybe Colorado doesn’t have strict rules.
Yes, fixing the map data fixes it for everybody, and I wish there was an easy way to send feedback to google.
Huh, I thought that coloring and other design features of road signs were a federal standard. Maybe it’s one of those things where a federal standard exists, but it’s up to the individual states to actually adopt the standards.
That federal standard would be the MUTCD (manual on uniform traffic control devices).
You can read the 800-odd page publication at the link below if you so desire:
https://mutcd.fhwa.dot.gov/pdfs/2009r1r2r3/pdf_index.htm
As you suspected, the manual is not uniformly adopted throughout the US. Although many states have adopted it as written, some states have adopted modified versions of it as well. From the MUTCD website:
It is interesting to note that the MUTCD is the national standard in all facets of using traffic control devices, but State transportation agencies differ in how they comply with MUTCD standards. For example, some States adopt the national MUTCD as their standard. Other States adopt the national MUTCD along with a State supplement that might prescribe which of several allowable options are selected for the State’s specific purposes. Still other States use the national MUTCD as the basis for developing their own State Traffic Control Device manuals, which must be in substantial conformance with the national MUTCD.
When a new edition or revision of the national MUTCD is issued, States have two years to adopt it, with or without a State supplement, or to adopt a State MUTCD that is in substantial conformance with the new edition of the National MUTCD. For the 2009 edition, the date by which adoption by the States was required was January 15, 2012.
This is the Full Self Driving software, not the Autopilot. But there have been substantial advances in the software in the almost two years since the accident.
Important bit of information for those who don’t click through to the article: the driver had a BAC of 0.26, which is three times the legal limit. Obviously FSD should not swerve off the road into a tree, that is a major fault. However, the driver being that drunk is also a huge contributing factor.
If “Full Self Driving” meant what the common meaning of those words meant it shouldn’t make any difference if he was that drunk.