FSD 2022.20.17 Coasts forever from a posted 55mph Speed Zone to a posted 35 MPH Speed Zone

[KurtSanders]

When I activate FSD Beta 2022.20.17 in a posted 55 mph speed zone and it accelerates to that posted speed and then when I encounter a posted 35 mph posted speed zone, the MY does not use regenerative breaking to slow down. The MY recognizes the posted 35 mph speed limit sign and automatically changes MAX Speed to 35 mpg but it freely coasts forever (like regenerative breaking is disabled) subjecting me to a potential speeding ticket. The green line showing regen is barely visible.

When I drive without FSD engaged, regenerative breaking allows for one pedal braking as expected. But the FSD beta mode appears to prefer a 'low regen' in certain posted speed zones?

 

[Aikidoka]

I noticed the same thing today. Traffic wise it wasn't inappropriate but going into a school zone it would be. It's the usual two steps forward and one back.

 

[DWtsn]

I noticed the same thing today. Traffic wise it wasn't inappropriate but going into a school zone it would be. It's the usual two steps forward and one back.

Same here! I have tried scrolling to a lower speed prior to the speed limit sign also and that didn't work.

 

[dannycamps]

It's always been like this with the FSD Beta. It does not handle speed traps well at all. There is an area where I live that goes from 55mph to a (strictly enforced) 35mph. In that area, I deactivate FSD Beta to slow down to 35 and then re-engage it.

 

[mackgriggs]

Yep...can confirm that its been like this for a long time with FSD beta. When going into a lower speed zone, it just coasts there instead of applying any regenerative braking.

 

[KurtSanders]

Still happening on 2022/20.18... Not sure why Tesla software engineers are so obtuse to this undesired bug!

 

[Jarends]

deceleration is much slower in FSD then it is in AP. Can't figure that one out. I hope I can blame the car if a cop stops me for speeding.

 

[KurtSanders]

The interesting odd behavior when driving under FSD Beta is it uses regenerative breaking to aggressively slow down for corners, stop signs, traffic lights, people, bikes, phantom ghosts, etc, but completely ignores using regenerative breaking for posted speed signage. It is very annoying in cities where speed can frequently go from 50 mph to 35 mph and the car takes almost a 1/2 to 3/4 mile to get to the slower posted speed. Of course, it totally ignores active school posted speed zones.

I'm not sure who at Tesla is coding this weird "coasting" behavior, but I'm sure that Elon will proudly state at some FSD Beta release how his autonomous AI now adheres to posted slower speed signs using regen technology....

 

[Geech72]

In AP if you tap the posted speed limit to the right of the set speed it more aggressively reduces your speed to match the limit. Has anyone tested to see if this is the same for FSD?

 

[DWtsn]

Tonight I came from a 70mph zone into a 55mph zone and my MSLR barely slowed. A few hundred yards later it dropped to a 50mph zone and by the time that change occurred the car was still doing 68mph and barely slowing. I had to brake pretty hard to get the car to an appropriate speed. I really wish they'd fix this before someone gets a ticket and tries to blame Elon!!! lol.

 

[KurtSanders]

Exactly!!!! I am baffled that Tesla's FSD Beta engineers have chosen to defeat regenerative braking when on activated FSD... It is so irritating and I have to turn off FSD at each slower posted speed zone and school active hours.

How hard can it be to make FSD beta acknowledge upcoming posted speed zones and school zone active hours! Ugh!

 

[mooredre]

What I have noticed since a few updates ago, I usually set my cruise 5 to 10 over the speed limit using FSD. If I’m in a 65, I’ll set it to 70 or higher then when I pass a 65 speed limit sign, the speed adjust to 65 and starts slowing down. This didn’t happen before the updates. Is anyone else seeing this issue and/or does anyone know a fix for it? Version FSD Beta 10.80.3.1 (2022.36.20 016153657840).

 

[dannycamps]

What I have noticed since a few updates ago, I usually set my cruise 5 to 10 over the speed limit using FSD. If I’m in a 65, I’ll set it to 70 or higher then when I pass a 65 speed limit sign, the speed adjust to 65 and starts slowing down. This didn’t happen before the updates. Is anyone else seeing this issue and/or does anyone know a fix for it? Version FSD Beta 10.80.3.1 (2022.36.20 016153657840).

When it detects a speed change (e.g. a speed sign different than the one before it), it will adjust to that speed regardless of what you set it to. For example (in this order):

1 You drive past a 45 MPH speed sign, car sets speed to 45 MPH

2. You then drive past a 55 MPH speed sign, car speeds up to 55 MPH

3. You manually set the speed limit to 65 MPH, car adjusts to the speed you set

4. You drive past a 55 MPH speed sign (same as prior sign), car remains at the 65 MPH you set

5. You drive past a 50 MPH speed sign, car sets speed to 50 MPH and slows down.

It's always been like this with the FSD beta.

 

[Jarends]

Mph over posted speed can be set under navigation in controls

 

[KurtSanders]

The issue is NOT that the FSD speed changes to the posted limit, but that the car under FSD never uses regeneration and coasts for over ½ mile to get from 55mph to 35mph. In that time, many cities have their police sitting there waiting for speeders..

 

[DWtsn]

The issue is NOT that the FSD speed changes to the posted limit, but that the car under FSD never uses regeneration and coasts for over ½ mile to get from 55mph to 35mph. In that time, many cities have their police sitting there waiting for speeders..

Mine does the same. I've seen multiple times as I drive through rural east Texas towns as the posted speed limits descend from 70 to 60 to 45, etc., that I am quite often 20+mph over the posted speed limit if I don't intervene. This is WELL above what is acceptable by local law enforcement and drivers not having the ability to give/show feedback to Tesla via a button or some other manner is simply unacceptable in my eyes.

 

[dannycamps]

This is WELL above what is acceptable by local law enforcement and drivers not having the ability to give/show feedback to Tesla via a button or some other manner is simply unacceptable in my eyes.

We had a button. They took it away

 

[DWtsn]

We had a button. They took it away

I know!! That upset me because I use to push that damn button everyday, several times a day!!

 

[Whoze]

Tonight I came from a 70mph zone into a 55mph zone and my MSLR barely slowed. A few hundred yards later it dropped to a 50mph zone and by the time that change occurred the car was still doing 68mph and barely slowing. I had to brake pretty hard to get the car to an appropriate speed. I really wish they'd fix this before someone gets a ticket and tries to blame Elon!!! lol.

The car is probably thinking that "Phantom braking" is occurring!