C’mon Tesla - Focus on Getting Speed Limit Signs Correct

[Jhodgesatmb]

I haven't had these speed issues I see others reporting. Not sure if they are just hypersensitive or if their FSD works worse than mine. We have four cars with FSD (two hardware 3 and two hardware 4) and I don't find the minor speed variations to be a big deal because they are so easy to correct.

Someone should at least do a poll. I am not convinced, from many comments seen here, that CTOC members are overly sensitive or overly insensitive but I have my own guesses. That said, I think that France has it right.

it really doesn’t matter, in the grand scheme of things, what Joe/Josephine driver thinks or wants. Tesla is targeting FSD as a fully-autonomous system, so it will eventually need regulatory certification. My guess is that, to get it, Tesla will have to get rid of speed profiles and follow the law. In the huge number of cases where the posted speed limit is incorrect FSD should be able to figure it out based on context. So far, if it has this ability, it hasn’t done too well.

Sponsored

 

[65SoYoLO]

Black Rhino offset. 18 inch for better off road conditions. Sand/ gravel/ snow and rocky approved.

What are the tires?

 

[Zwick]

My main issue is slightly different than any I've seen posted on this thread with regard to speed regulation. I'm in rural Texas. The speed limit on the main roads I travel is generally 75. On the occasional towns, of course, you're slowed down to appropriate town speeds. It seems to be almost flawless at slowing down when there is a speed reduction. However, it very frequently has trouble seeing the signs as you're leaving allowing you to speed up to any posted speed limit greater than 60. I find myself frequently driving in mad Max mode just to go roughly the speed of local traffic. I don't know if it has enough impact, but I've recently learned that you can punch the voice button and say "bug report" and then describe the problem. I've been doing this for a bit, but if more people bug report this issue perhaps eventually it will get dealt with.

 

[SCTesla]

I've recently learned that you can punch the voice button and say "bug report" and then describe the problem. I've been doing this for a bit, but if more people bug report this issue perhaps eventually it will get dealt with.

Bug Reports don't go to Tesla. They stay in your vehicle for a period of time for service to pull upon request.

If you want to report issues with FSD, you have to disengage.

 

[Blue Oval Ron]

What are the tires?

Mickey Thompson Bajas

 

[agordon117]

I have found that feathering off the accelerator is less effective at holding the speed, compared to holding the accelerator just long enough that you are travelling at a steady speed and then abruptly letting off the accelerator). 9 times out of 10 it will hold the new speed although it's still dependent upon weather, traffic and other road conditions. In other words, it won't drive any faster than it deems safe for the conditions and the speed profile chosen. Higher speed profiles entail a higher risk, just like with human driving.

Every time I let off quickly no matter how long I held it there before to steady the speed, the truck slams on the brakes

 

[65SoYoLO]

Mickey Thompson Bajas

I tried, but i cannot read the size. I know they are 18" and I tried looking them up on tire rack but I don't know the tire size.

 

[Cybertruck2024]

Just went 200 miles the last two days and tried to use FSD as much as possible. Half of the time it is a miracle product and makes driving incredible. The other half of the time it is the worst driving experience imaginable.

There's a long stretch of road that is 55mph where FSD thinks it is 45mph. No matter how much you try to fight the truck, it is impossible to get it to do a speed that makes sense. Then there are a lot of areas with road work and speed cameras. Without disengagements, you will get a speeding ticket. The other thing the truck cannot do is slow down when entering small towns. There's a lot of 55mph to 35mph speed changes on rural highways, police always sit just after the speed changes downward. If the truck on standard is doing 62 in the 55, it is never going slower than 50 when the speed turns to 35. That is a ticket 100% of the time near me, so FSD doesn't work.

If Tesla somehow was liable for speeding tickets and points on my license, I would just let FSD run wild. Since it isn't, the constant speed battle is more tiring than just driving yourself. FSD under its current build simply isn't usable.

i had a rental car last week for work, they gave me a Honda Accord with adaptive cruise control and lane assist. I hate to say it, but for a long highway drive, it absolutely destroyed the CT's FSD. Sure i had to press the button up and down a few times to account for speed changes, but this was low effort and it just worked as intended. No guessing, no fighting, just a reliable product.

 

[Djinndjinn]

I understand that Tesla is on this journey to self driving, and from their perspective that journey involves removing more and more of the decision-making process from the driver. Hence the profiles to define certain behavioral preferences, but removal of the granularity of adjusting the speed through the scroll wheel.

I can even deal with the fact that the profiles don’t match up great with my personal driving profile, but my beef is with the decision-making that allows the vehicle to drive 55 in a 25 because it can’t see and adjust to a posted speed limit. That actually increases the stress of driving, not decreases it, and does not make driving safer.

i’m trying to balance this with the pluses, including sometimes the truck responding to things quicker than I would be able to as a human. Right now, the trade-off doesn’t seem positive. To me, while the self driving capabilities have clearly improved, the driving experience has actually become worse since version 13.

TBH, if they could nail being able to extremely accurately read signs, then nuance that speed based on driver profile, surrounding traffic flow, end of Construction sign, etc., that would be not an iterative step, but a huge leap. But it all starts with being able to accurately define the source of truth, which is … The posted speed limit.

 

[CallsignVega]

The speed control issue is definitely the largest problem with FSD now. Multiple time just yesterday it tried to drive 55 in a 25. I have to flick between the speed profiles just to get it to respond properly and have to downright disengage FSD in some scenarios due to the massively wrong speed. We aren't anywhere near actual autonomous driving.

One of the most odd things to me is that reading speed limits signs and adjusting accordingly would seem to be one of the easier things to accomplish for visual sensors but alas it seems to be Tesla's Achilles heel.

 

[Granch]

This is a IP issue, mobile eye owns the patent.

 

[CallsignVega]

Apparently, FSD reads the signs but weighs that against map data and current conditions.

https://www.notateslaapp.com/news/3...-speed-limit-its-not-just-about-reading-signs

It does very well when following traffic, or on well-traveled routes. Exception-handling is the weak link.

Disagree with that article. There are brand new, super clear speed limit signs in my area that are 100% ignored by FSD at all times of day and weather conditions. 100% relying on old map database.

Sponsored