Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Cruise control and autopilot slamming brakes when passing under blinking yellow lights on rural highway...

This site may earn commission on affiliate links.
I have owned a new model 3 (with autopilot) for 3 weeks now. I have a long rural commute (60 miles each way), and I encounter blinking yellow lights over one of the highways twice along the route. The cruise control and autopilot both essentially *slam* the brakes as I approach the lights (both systems actually wait until I am probably within 30 feet of the lights--maybe less--before they slam the brakes).

Keep in mind that the posted speed limit on this highway is 75mph and most are usually doing 80+ mph! This obviously creates an extremely dangerous situation. The fact that this occurs with cruise control too is beyond ridiculous. I've noticed that when the flashing yellow lights are on the side of the road, the systems handle it appropriately and slow down slightly and more gradually. It is the situation where the lights are overhead (like a typical intersection traffic light) that the systems apparently think I am running a red light. Absolutely unacceptable that his is happening, and I am amazed someone hasn't been killed yet.
You do slow down, though, right? Yellow lights mean caution, and that means you slow down. I'd be surprised if it "slams on the brakes" (thank you for correct spelling!) if you slow down and "proceed with caution" as the DMV suggests.
 
Not on Model 3's sold in North America.
Not anymore.

Tesla has been on a spree to de-content Model 3's to save money (HomeLink, auto-dimming mirror, standard 433Mhz TPMS, etc, now front radar).
You still get them on Model S's and X's. BTW, Model S is a much better long distance highway cruiser anyway.

a
Parts issues not for saving a few bucks. They keep increasing the price anyway and the margin is improving continuously.
 
The subject of traffic signals has been discussed here before. It would be great if colors of signals were standardized to a specific wavelength in nm but they still follow a standard based on a chromaticity diagram first published in 1931. You can read more about that here:


Standard stoplights are not hard to conceptualize and model. Except in rare instances, red is on the top, amber in the middle and green on the bottom. The sequencing is always the same. Red then green then amber and finally red again. Green arrows add to the complexity, but they generally apply to a specific travel lane, which is often defined in the map data. More recently, certain jurisdictions have added flashing amber arrows indicating an unprotected turn. Canada also has a flashing green light but it is becoming rare except in BC and Yukon. It indicates a pedestrian controlled crossing in those provinces.

But the flashing red-amber and red-red signals are the ones that cause issues with FSD. Their recognition by FSD seems to be a mix of mapping data and vision. A further complication is that standard signals may revert to flashing in times of low traffic density.

The first challenge in modeling flashing signals is the angle of the intersection, since the lighting on the cross street can often bleed through to a forward facing vehicle. This seems to be the main problem if the signal is not properly mapped. Of course, flashing signals just possess a repetitive on/off signal so there are no hints from sequencing like there is with a standard signal. Some flashing amber lights are not overhead and may alert the driver to a hazard like a tight curve or a school zone.

On the red flash street, there is no issues. It is no different that a two way stop sign. It's the amber flash side that's a problem. It means proceed with caution. The easiest solution for modeling is to completely ignore flashing amber lights. The problem is the bleed through mentioned above. Red and green are far apart in the light spectrum, but red and amber are not. This is why FSD presently does a hesitation dance at flashing ambers. It's amber, no wait it's red. Oh forget it, someone get me a cheeseburger. (apologies to Gary Larson). It's also possible that the signal is a full stoplight that is flashing amber during a low traffic period.

Anyway, that more than anyone wanted to know about this but not everything that could be said. I didn't even mention overhead lane signals for bridges and tunnels and other alternating traffic flow situations.
 
  • Like
Reactions: Phil Stasik
The first challenge in modeling flashing signals is the angle of the intersection, since the lighting on the cross street can often bleed through to a forward facing vehicle.
Actually the first challenge for the car is to determine the that it is indeed flashing .. that takes a full on/off/on cycle at a minimum (off/on/off isnt enough), which, given the flash rate, is quite a bit of time, and depending on visibility and approach speed means the car may be quite close before it has determined its flashing.
 
You do slow down, though, right? Yellow lights mean caution, and that means you slow down. I'd be surprised if it "slams on the brakes" (thank you for correct spelling!) if you slow down and "proceed with caution" as the DMV suggests.
I knew someone would show up and tell me this is my fault.

The cruise control and autopilot are dangerous as they are currently configured. We are talking about a rural intersection with clear visibility from a mile away in all directions with a posted speed limit of 75mph. Even if I slow down to 65 mph from a quarter of a mile away, the system will still SLAM the brakes and start squealing red alert within 25 ft of the intersection.
 
  • Like
Reactions: Sporty
I knew someone would show up and tell me this is my fault.

The cruise control and autopilot are dangerous as they are currently configured. We are talking about a rural intersection with clear visibility from a mile away in all directions with a posted speed limit of 75mph. Even if I slow down to 65 mph from a quarter of a mile away, the system will still SLAM the brakes and start squealing red alert within 25 ft of the intersection.
Can you post some video? Always useful to understand others experiences and when/where this happens.
 
Yes, this is what I do. But because of the length of my commute, and the fact that it is 99% highway and is a reverse commute (so little traffic), I can't live without cruise control. And having to "tune-in" to make sure I am not killed by a system that is ostensibly there to protect me is a bit annoying. Also, because my speed is about 80mph, having to hit the accelerator to avoid emergency braking when autopilot is engaged is an issue since the max speed for autopilot is 80mph.
Not sure I even want to try this feature when I get my new M3 - I would shut it off and on as you approach these lights - maybe slow down ….
 
I have these “safety zones” all over the place in Vegas and so the car brakes hard frequently. I cannot stand it when the system “sees” those yellow lights or the bars across the walkIng zone. I was thinking of getting a “Student Driver” sticker for the back of the car so people do not run into me! 😄
 
  • Funny
Reactions: afadeev
Because of all the bad press Tesla gets, out of an abundance of caution, it slows for blinking yellows (and yes...it slows too much). It happens to me too in our town. However, since getting into the FSD beta program, I can tell you that it handles the blinking yellows much better. As they move parts of the FSD stack to standard AP, you should see some improvements.
I hope that's true about FSDß handling blinking yellows better. I guess I've mostly experienced trouble on freeways, where the non-FSD stack is in effect. There'll be a sign for something benign like "Tune to AM 540 for weather update" with flashing yellow lights. No need to slow down--it's just trying to get the driver's attention.

Well, I suppose slowing down gives slow readers more time to read the sign. ;)

But seriously, this is as annoying as phantom braking.