FSD 14.2.2.1 Still Reading Speed Signs Wrong

[CG Cowboy]

Within a half mile, speed limit sign pattern is

Speed Limit: 70
Buses: 65
Trucks: 60
Minimum: 45

Each of these signs will change the FSD speed limit creating erratic driving.

Anyone else seeing this?

Sponsored

 

[CyberTexas]

Well that is a lot to read in one sign!

 

[Leifmb]

Well that is a lot to read in one sign!

Not for a ROBOT!

 

[Qixer01]

Yes!! When driving down mountain they have truck speed limit signs. The CT sees these and lowers its speed. And sometimes it don’t even change the speed when a new sign is seen.

 

[drrussellhogue]

They aren’t reading the signs, right? They are using gps map data. If they start using vision to override gps map data then it would be better. Hopefully that’s coming.

 

[TexasRaider]

Hopefully in the future, it’ll be able to comprehend school holiday schedules so it won’t slow to 20 MPH in school zones when school isn’t in / when it isn’t applicable.

 

[cyberjeff25]

I assume it really uses gps map speed limits.

 

[CG Cowboy]

Definitely not using gpa map data consistently if at all. I can watch the signs appear on the side of the road and it changes. If it were using GPS data, this problem wouldn't happen.

 

[PungoteagueDave]

They aren’t reading the signs, right? They are using gps map data. If they start using vision to override gps map data then it would be better. Hopefully that’s coming.

Tesla’s AP used vision starting in 2016 vision. Vision worked until FSD 14x but appears to be gone at least for now.

 

[PungoteagueDave]

It has to use vision as a key input if we’re ever going to achieve unsupervised FSD. Construction zones, temporary restrictions etc. Vision in earlier iterations was sketchy because there are so many “exceptions”. For example, in Virginia there are assumed legal speed limits depending on the road nature. It’s 55 on normal rural roads with a double center line. However that’s often not posted. When entering a town the reduced (often 25) limit is posted. When leaving a town or restricted zone the signs say “End 25 MPH restriction”. AP and older FSD versions read this as the current speed limit, while the reality is 55, although not posted as such. We humans know this and drive appropriately, but the computer would need more information than is evident visually. With the 14.x switch to prioritizing map speed data this is “solved” but there are a host of data errors, and of course no situational speed limit awareness, at least for now.

 

[PungoteagueDave]

Definitely not using gpa map data consistently if at all. I can watch the signs appear on the side of the road and it changes. If it were using GPS data, this problem wouldn't happen.

GPS “data” usually agrees within a few feet of sign placement (the signs are placed using GPS data). Watch this in standard mapping apps to confirm for yourself.

 

[CG Cowboy]

GPS “data” usually agrees within a few feet of sign placement (the signs are placed using GPS data). Watch this in standard mapping apps to confirm for yourself.

GPS data is accurate. Agree with that. But if it were using it, it wouldn't change the speed limit to limits meant for trucks, buses, and minimums.

 

[WormtownKris]

Def not a problem with GPS data. Back when it used GPS data the speed limits were very accurate.
The "speed limit" shown on my screen is very often wrong, and it has been that way with our Model 3 before I got my CT. On some state routes the vehicles will read "Route 49" or "Route 62" as "Speed Limit 45" or "Speed Limit 60", and ping pong "speed limits" based on the alternating route signs and speed limit signs. Driving towards a local ski mountain that has some windy roads, all the speed limits are shown on little square yellow and black "local hazard" signs, and they go from a regular 40 mph down to 30 mph on curves. But for that whole 4-mile stretch of Mountain Road, my truck says the speed limit is 20 mph. That's because the previous white and black speed limit sign is a brief 20 mph stretch in downtown Princeton. Once you go up the hill past the common and the library you get a 40 mph sign. But since it is small and square and yellow, Teslas do not "see" them.
This is one of the big reasons I am reluctant to use FSD other than my enjoyment of driving the truck so much. Concerned what would happen if my truck thinks the speed limit is 30 mph off what it really is.

 

[CyberGus]

I posted this elsewhere, but it seems more relevant here; apologies for the double-post.

Yesterday I noticed a blue halo around the speed-limit indicator, which was showing 55MPH while on a 75MPH highway. I believe vision had captured the slower limit from a sign on the parallel frontage road.

(It switched back to 75 before I was able to snap a photo; the blue halo disappeared shortly thereafter.)

Note that it didn't actually slow down, which suggests that there's some logic to handle discrepancies between mapping data and real-world signage. I think it would very helpful if it displayed greater detail, showing the speed from the Map, from Vision, and the resulting target based on your preferences.

Currently, when the wrong speed is chosen, it's difficult to discern why.

 

[earthworm]

this has been a problem for me as well - after taking a clover leaf or merging, it wants to slow down to 45mph on the interstate.

Sponsored