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

[HaulingAss]

The only way to stay in an acceptable speed range in this stretch (other than disengaging) is to feather back and forth between standard and hurry, triggering brake lights every 15s or so. If you get it just right, you can avoid the brake lights, but the way the scroll wheel input is ignored if it's too close to another input makes it difficult.

Switch to "Standard" and then, rather than switching back to hurry, just give it a bump on the accelerator to encourage it to hold a higher speed. This almost always works for me. But it will all be a moot point shortly, as FSD is improved to the point driver supervision is not necessary. then people will complain that it's angering other drivers because it will only go the speed limit (and almost NOBODY drives the speed limit)..

Which brings up an important truth: Some people will NEVER be satisfied with how it drives because no driver, man or machine, will ever drive exactly how THEY want it to in every situation. We call these people "backseat drivers".

Sponsored

 

[HaulingAss]

But how to make vehicle slow down without disengaging? scroll down to chill.

Standard, Chill or Sloth depending upon the road, road conditions and personal preferences.

 

[CyberGus]

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.

 

[Mikec3399]

Sorry if this was covered already.

Scroll wheel to sloth. Perfection.

I like to scroll wheel before when I tow in Traffic Awareness, the scroll wheel comes back, the vehicle is much more responsive and slows down when I need to scrolling to sloth, when these traffic cameras are coming up, the vehicle doesn’t slow down fast enough with FSD sloth mode.

 

[agordon117]

Switch to "Standard" and then, rather than switching back to hurry, just give it a bump on the accelerator to encourage it to hold a higher speed. This almost always works for me. But it will all be a moot point shortly, as FSD is improved to the point driver supervision is not necessary. then people will complain that it's angering other drivers because it will only go the speed limit (and almost NOBODY drives the speed limit)..

Which brings up an important truth: Some people will NEVER be satisfied with how it drives because no driver, man or machine, will ever drive exactly how THEY want it to in every situation. We call these people "backseat drivers".

It won't hold the speed though. And I do know the trick to try to feather as slow as possible off of the accelerator to try to make it hold the speed rather than slow down. It just won't do it. The only thing that used to keep it in a reasonable range was if I entered the zone at like +7mph on standard (which was rare that I would hit). It would stay at that speed for a few miles before slowing further down.

Now with 14.3.5 it immediately begins to slow down when it crosses the map zone to the phantom construction zone. Reminded me a lot of the old v12 days honestly. And it isn't necessarily a bad thing, because the alternative is that it keeps blowing through construction zones at 82mph.

Also, it's a nice theory that "eventually" this will all be irrelevant because it will be unsupervised. I have been hearing this as the reason that they don't need physical buttons, turn signal stalk, instrument cluster display, and many other things. Meanwhile, they gave up on the wireless charging option for the truck, so you will always have to manually plug it in even if it receives unsupervised driving.

However, until it's actually unsupervised and the driver is no longer responsible for tickets or accidents, the best thing they can do to prevent disengagements is allow us to set the speed if we want. I use FSD so much less (in miles driven) now than I used to because of the constant chore of trying to get the truck to go fast enough on back roads and in the sweet spot on the highway. Even though I had to set a manual max speed and then feather the throttle to get it to the max speed on 13.2.9, that was still a better experience than what I have now on 14.x.

 

[SCTesla]

Sorry if this was covered already.

Scroll wheel to sloth. Perfection.

Except when it thinks the Speed Limit is 55 in a 35, then sloth may go 45 or 40, depending on the road.

 

[mbrockus]

i know the speed limit compliance is a current thorn (and its on the top of my wishlist too) but every time i get in a rental car, I am quickly reminded how much I miss my CT. I hold out hope, that like phantom braking, this too will be a mere memory in the CT forum archive.

 

[BrockN]

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.

This is what I have understood too. But you'd think that an actual limit sign would be the given the highest confidence level.

What really made me aware of that was when a 120 km/h divided highway had bridge construction, funneling the other side over to my side, with one lane each direction over 'my' bridge. The construction zone had many signs posting a 50 km/h limit and the CT figured it was fine to blast through at over 80, which is as far as 'sloth' mode would drop me down. I felt that was beyond ridiculous.

 

[CyberGus]

you'd think that an actual limit sign would be the given the highest confidence level

Yes, the driver is responsible for obeying all legal signage. Which is great, until some joker comes by with electrical tape and does this:

Vision-based systems can misread this as "85". So, now what??

 

[HaulingAss]

It won't hold the speed though. And I do know the trick to try to feather as slow as possible off of the accelerator to try to make it hold the speed rather than slow down. It just won't do it.

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.

 

[Blue Oval Ron]

Surely wish we had the old scroll wheel adjustment for "tuning" our speed. It is a pain in the arsenal with the silly arsed profiles!!!

 

[sjarriel]

I have noticed the same issue, with the latest version of FSD (14.3.5).

 

[65SoYoLO]

Holy crap those are freaking awesome tires!!! What size wheels and what size tire!!! I can't afford them but I can dream. Do you ever going to beach, I bet you don't even have to add down

 

[Blue Oval Ron]

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

 

[Eka]

I think they should use both vision and data from Google. I turn out of my subdivision, and FSD thinks the speed limit is still 25. The next sign is end 35, so FSD switches to 35 then 100' later a speed limit sign says 45. Google Maps knows the speed limit without having to read a sign.

Here in Iowa, the state just invalidated most rural paved road speed limit data on maps by increasing the rural speed limit to 60 MPH on July 1st. Still doesn't help when the road goes into a rural area at the edge of town and there is no 55 MPH or now 60 MPH speed limit sign, or the sign is "END SPEED ZONE" or "TOWN LIMIT". In rural areas the speed limit on paved roads is 60 MPH unless otherwise marked. That "unless otherwise marked" is important and was even asked about on the written test. Google maps obviously only looked at the next speed limit sign in the next town and marked the whole rural road in between 35 MPH or 25 MPH when it really is 60 MPH outside the towns' borders. The same code section also tells the default speed limits in residential, business, etc districts unless otherwise marked.

We have a few roads in Michigan where road is marked 55 mph. On one the truck thinks the speed limit is 25 mph for about 5 miles in one direction but not the other. On another, it thinks the speed limit is 40 mph for about 20 miles even though I can read the signs in the display for 50 mph and then 55. It will then speed through a little town until I turn at a traffic light. It has the correct speed going the other direction.

In a town south of here the road in town is much like the rural highway and has a sweeping banked turn that easily could be navigated at 70MPH, but with business entrances. FSD insists it is marked 55 MPH through the town. The signs clearly state 50, 45, and then 35 MPH, and the cops live to ticket there. I have to totally disengage FSD there.

Anything other than bringing back manual control until the speed control is perfect is a misstep. Even if the latest thing Elon is talking about (where the car learns from disengagements individually) includes speed related disengagements, they still should have brought manual speed control back in 14.2.x and didn't.

We need much greater gradations in speed control. The 5 speed profiles don't work. They are too coarse and don't allow use to easily tell FSD it is going too fast or too slow and by how much. Some towns it is fine to go 3-5 over the limit, some 3-4 over is the max, but in a few anything over the speed limit will get you a ticket. Also on many highways 5 over is fine, but 6 over isn't. 7 over is a near guaranteed ticket, but if you drive only 2 over people are tailgating you to get you to go faster. FSD also needs to remember these inputs. Did FSD even send in the scroll wheel and accelerator press speed inputs? That was valuable teaching data.

Sponsored