FSD Reading the speed signs wrong in one place

[mongo]

Scroll wheeling to adjust speed likely also gets tracked.

Sponsored

 

[eswimm]

I'm purely speculating, but I think it's less that Tesla is reading speed limit signs (i.e. using OCR to identify words and/or numbers on the sign) and more that it's using a neural network to recognize a 55 mph sign (or whatever speed) and override the limit appropriately. I notice in my area (NC) that the vehicle correctly identifies the speed on the highway when there are dual purpose signs (min/max on 1 sign) in NC and SC, but when I get to GA and they have separate signs spaced on the interstate (70 mph max, 45mph min) the car gets confused and keeps changing the speed limit as it passes each sign. Before the update that allowed FSD to use the prevailing speed of traffic it would slow down, now it simply displays a message that it is keeping up with the flow of traffic even though it thinks the limit is 45. I've never had it pick up a suggested speed limit as the actual limit, I assume it identifies the yellow background as optional.

 

[MInnesooooooota]

One problem with FSD are the Tesla maps. They suck.

A second problem is they changed from using GPS data for speed limits (very reliable) to only reading signs. That was a stupid choice and is failing.

Everyday when I go on a side road (25 mph) the car speeds up to 55. Why? There is a 55 sign from the highway. But it is on the far LEFT side of the road. See pic.

Even when I turn right at the stop sign, car accelerates to 55 on a 25 mph side road. It only adjusts when it sees a 30 MPH sign a block down the road. Stupid.

And this happens in other places as well.

Or I enter a main road from a side road and it won't accelerate until it sees a speed limit sign - pissing people off behind me.

FSD is high tech - but misses on some very basic things. Don't count on Robo Taxis for a while. If they can't fix this simple issue after me messaging them 20 times, I can't see how Robo Taxis can be let loose.

 

[Kikichan]

I have that problem in Texas with loop roads. CT traveling along at 65 and suddenly dropped to 40. It was not subtle. 40 was for the loop not the highway. luckily there was no one behind me.

 

[Thunderstrike44]

I dont know if it can read signs or not, but if it is map based, then they need to update those maps. I have 5 spots on my drive to work that it thinks its 25 MPH when its really 50,45,40,30 and for no other reason all of sudden drops from 50 to 25 HARD in the middle of driving. Very annoying for me and the people behind me not safe at all. Its fine on the highways but get off on rural streets all bets are off....
One last thing I can't completely complain because the signs are still up but there is a school zone close to home that the school has not existed/Closed for over 5 years now but still causes the FSD to think it needs to go 25 mph.

 

[cybercricket]

One problem with FSD are the Tesla maps. They suck.

A second problem is they changed from using GPS data for speed limits (very reliable) to only reading signs. That was a stupid choice and is failing.

Everyday when I go on a side road (25 mph) the car speeds up to 55. Why? There is a 55 sign from the highway. But it is on the far LEFT side of the road. See pic.

Even when I turn right at the stop sign, car accelerates to 55 on a 25 mph side road. It only adjusts when it sees a 30 MPH sign a block down the road. Stupid.

And this happens in other places as well.

Or I enter a main road from a side road and it won't accelerate until it sees a speed limit sign - pissing people off behind me.

FSD is high tech - but misses on some very basic things. Don't count on Robo Taxis for a while. If they can't fix this simple issue after me messaging them 20 times, I can't see how Robo Taxis can be let loose.

I've had the opposite impression. Every time FSD exits a state highway (55MPH) it drops the speed to 45MPH despite no signs being present. It also does that on the highway itself in areas with junctions. There is no prescribed 45MPH anywhere around here, so the only place that could be coming from is the maps.

 

[Sjohnson20]

In my case the latest map update fixed this issue in Orlando on the I4 express lanes for me. It's getting the speeds from bad map data at least sometimes. Seems like Teslas maps are way behind.

 

[txtravwill]

Mine misses clear sins on every device, doesn't read them. Seems like not even using them honestly.

 

[Crissa]

There is no prescribed 45MPH anywhere around here, so the only place that could be coming from is the maps.

FSD also tries to guess the speed of unlisted spaces from what the lane looks like.

And for those of you saying the signs is worse, signs are literally supposed to override map data.

-Crissa

 

[Jhodgesatmb]

When we are driving towards Sonora, CA on CA-108, there is a section that changes the speed limit from 55 to 65. For some reason my CT does not change the speed limit accordingly. It works everywhere else. My Model X did not have any issues in the same location. I wonder if CT is reading the with Trailers 55mph sign instead. I noticed it both directions. The problem is when have FSD on, the cars behind you are not very patient with your speed. My model X only had issues on highway 101 where it got stuck with 55 in San Jose.

I had this happen between i40 and the Grand Canyon a couple weeks ago. Very weird.

Sponsored