FSD AWD not recognizing speed signs.

[CyberGus]

Traffic signs are not erected on a whim. Governments have processes for implementing traffic controls in order to comply with the law.

• Some streets have statutory speed limits, such as school zones, rural highways, etc.
• For other streets, engineers conduct traffic studies to determine the optimal speed for safety and flow.
• The relevant data is compiled into reports, drawn up on maps, etc.
• A work order then directs crews to install exact signage at specific points.

Therefore, the database isn't compiled from a survey of the signs; the signs are installed to match the database.

I suppose there's a few city engineers hired in the 1970's that refuse any of that new-fangled "cum-pweter" stuff and keep stacks of maps all over the office, but most is digital data. Because, you know, it's 2026 ffs.

When the signage does not match the database, then I submit that the signage is incorrect. If FSD is cited for speeding, I would argue that the nav database has the prevailing info, and I should not be punished for a faulty sign.

Where's my lawyers at lol

Sponsored

 

[txtravwill]

Traffic signs are not erected on a whim. Governments have processes for implementing traffic controls in order to comply with the law.

• Some streets have statutory speed limits, such as school zones, rural highways, etc.
• For other streets, engineers conduct traffic studies to determine the optimal speed for safety and flow.
• The relevant data is compiled into reports, drawn up on maps, etc.
• A work order then directs crews to install exact signage at specific points.

Therefore, the database isn't compiled from a survey of the signs; the signs are installed to match the database.

I suppose there's a few city engineers hired in the 1970's that refuse any of that new-fangled "cum-pweter" stuff and keep stacks of maps all over the office, but most is digital data. Because, you know, it's 2026 ffs.

When the signage does not match the database, then I submit that the signage is incorrect. If FSD is cited for speeding, I would argue that the nav database has the prevailing info, and I should not be punished for a faulty sign.

Where's my lawyers at lol

Don't think that would fly here in TX, everything is written for "driver to observe and obey posted speed limits" which makes signage the meaningful speed limit dictator.

 

[CyberGus]

Don't think that would fly here in TX, everything is written for "driver to observe and obey posted speed limits" which makes signage the meaningful speed limit dictator.

Even in TX we have laws. I would argue that if the State has negligently published conflicting traffic regulations that are meant to be legally binding, then they owe me the benefit of the doubt. Otherwise, it is a form of entrapment.

If some joker puts a 65MPH sign up on a residential street, can drive that speed with impunity? Or would the arresting officer tell me "ignorance of the law is no excuse"?

Even if there are no signs at all, I am still expected to obey the "speed limit" whatever it may be.

 

[CyberLucky]

My issues with speed limits:

• Signs that say "30 kmh when flashing" cause the truck to go 30 regardless of flashing, sometimes for very long stretches.
• 3 hours on a 110 kmh highway with 110 signs posted regularly and every sign was seen by the truck as 70.
• As mentioned previously, if there's a thick sheet of ice on the road and conditions warrant 75 in a 110 zone, every profile, including sloth, will try to go at least 110 and will try passing cars (which are smartly going slower) to get there. Scary stuff. We need "Banana Slug" mode that goes 75% of the speed limit (or, better, return of manual control).

Really, we are all in the process of beta testing speed profiles for Tesla.

 

[DeanSirovica]

Wrong speed is much worse for me since V14. I wonder if Tesla diverted compute from reading signs to other FSD functions and now relies on map data more ?

 

[Cybertrock]

my Truck will see every speed limit sign except 70mph signs. i have started creating bug reports every time it misses a speed limit. It is, after all, a software flaw and thus a bug. Like any software company they probably address bugs based on the number of reports. If everyone does this they might address the problem

 

[PungoteagueDave]

FSD gets it's speed information primarily from map data with embedded speed data for each section of road that has a different speed limit. I believe most of this information is primarily sourced from state and local government public works departments (and not all are very good at it). I'm fortunate where I live and drive that the data is relatively accurate, with only rare mismatches between map data and actual signage.

I think as long as FSD is still "FSD Supervised" this is not currently a Tesla priority. As it becomes FSD Unsupervised they will need to do one of two things:

1) Pour big resources into validating the map data with the reality on the ground, or

2) Dedicate more FSD bandwidth into reading signs. This could require that Tesla update the hardware to version 5, if the bandwidth of hardware 4 is already stretched thin just driving safely.

It would be relatively easy for Tesla to make existing hardware read signs, but it could come at the expense of actual FSD safety. Tesla prioritizes safety for obvious reasons.

BUT tesla has had really good speed-limit-reading capability in its former AP and FSD iterations as long ago as 2016 (when they partnered with Mobile-eye). Ten years later that capability has regressed. Given the proliferation of construction zones, school zones with varying dates/time limits, etc, this seems core to the FSD task, and we know they can do it. So it is a bit depressing to have to intervene so much, with something we’ve essentially had working in driver assist for ten years.

 

[HaulingAss]

BUT tesla has had really good speed-limit-reading capability in its former AP and FSD iterations as long ago as 2016 (when they partnered with Mobile-eye). Ten years later that capability has regressed. Given the proliferation of construction zones, school zones with varying dates/time limits, etc, this seems core to the FSD task, and we know they can do it. So it is a bit depressing to have to intervene so much, with something we’ve essentially had working in driver assist for ten years.

Such are the pains of being an early adopter of bleeding edge technologies. Personally, I find the joys to outweigh the negatives by at least 50 to 1. If it's not worth it to you, don't buy it (or at least don't use it).

Tesla is making as much progress as they physically can. If they sacrificed the bandwidth needed to read speed limit signs in exchange for more safety (putting resources into being ready for edge cases), that seems like a very reasonable thing to do. At least to me, some people will only complain it's not perfect.

I guarantee there will be angry/upset people talking FSD down, even once it's statistically proven to be far safer than a human. How do I know? Two ways:

1) People already complain about the driving habits of perfectly good drivers, everyone thinks the exact way they drive is the best and only way to do it. Some people think you should never exceed the speed limit, even by one mph. Others think it should go 10 mph over when it's safe to do so (or when other traffic is going 10-15 mph over). Some think it should never go below the speed limit, others think it's prudent to do so when the situation warrants.

2) Just by observing the people who endlessly complain it's not perfect yet, even though the FSD team is doing amazing and ground-breaking work, as fast as physically possible.

I guess it takes two types to make the world go round, the doers and the complainers. Just know that complaining about the obvious will not advance the technology any quicker than it's already progressing. To do that you would have to join the FSD development team (and have better insight than they already do).

Sponsored