Does FSD read speed limit signs anymore?

[sharpgator]

Maybe because I am talking about a more rural setting. It has not been a problem in most settings, but it used to be fairly instantaneous….. would pass a sign, it would “see” the new speed and change it. I am wondering if it is taking its cue from something other than visual information.

yes. This is exactly what I mean. It was reading signs and mistaking route numbers (eg. route 15) for 15mph. That was annoying, but that was a very early version. Then it learned to differentiate route # from speed, likely by color. But it was “reading” the actual sign and continued to do so until recently. Now it seems to be taking information from some navigation data set. From where? What’s wrong with reading? Unless as someone pointed out, it’s a place with no signs. In any case, getting back some control for those edge case scenarios would be very helpful!

Exact same thing in my area. Sometimes it's right on cue when the speed limit drops and the truck decelerates at the sign. Other times, it clearly "sees" the sign and ignores it.

Sponsored

 

[cybercricket]

For us to provide meaningful feedback to Tesla on this issue, they need to provide more detail on the current chosen speed limit: was it from map data? Or did it read a sign? Was there a conflict between the two??

Right now, we can't even agree if/when it is reading the signage. In my experience, non-standard speed signs (like construction zones) are ignored, so I assume it is using the map data.

From my observations it uses the map data until it sees a sign to override it. This is separate from it stopping to process signs. Now the interesting thing is map data is supposedly from Google, and Google allows people to submit corrections. I've tried doing that for one of the stretches were FSD incorrectly determines the speed limit, but nothing changed after months of waiting. Not sure if Google refused my correction, or perhaps something else is going on.

 

[FHWizard]

HWY 42 in Oregon is a twisty highway with 55MPH speed limit. I used to be able to set it to about 62 to flow with traffic and it would slow appropriately in the curves then pick back up - great. Now it shows up as 45MPH even though there are plenty of 55MPH signs and I have to toggle between Mad Max (where it wants to go 72) and Hurry (down to 53). As an experiment on our last trip I pulled over, parked (didn't want to do a reset while driving) and continued. It initially still showed 45 but changed to the correct 55mph in about a half mile and read the correct speed limits from there on.

While, if that didn't work, I was tempted to get out and do a rain dance while waving a dead chicken over my head, I knew that would just reinforce other drivers opinion of CT owners.

 

[Duran]

On rural Texas, Oklahoma, and New Mexico roads, it rarely reads the speed limit signs. I reported numerous speed errors out of frustration - don't have that satisfaction any more so have to bounce the scroll wheel back and forth to yoyo the speed where I want it. How can it be considered self-driving if it can't read signs?

Here’s what I’ve noticed and wondering could this be the reason. Driving back roads in Oklahoma going from 45-55-65mph then going thru small town speed limit goes all the way down to 35mph, then back up again. My CB rarely sees the 65 or the 35. One day I started paying close attention to the actual signs “what is different here than the highway?” On the highway CB does so much better. The highway signs are huge compared to back road signs. Could this be the reason? Could the size of the signs be confusing and/or are missed because of their size? <— I swear I can already hear the jokes. I’m just taking a stab at this so if I’m completely off base here, be kind. lol.

Sponsored