laservet
Member
And again this morning, decelerated 15-20 mph, hung behind the vehicle in the adjacent lane for 15 seconds before it picked up speed and passed it.
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
I have a good solution as long as you will be traveling at one speed for the majority of the trip.Phantom braking makes Auto Pilot on our MY nearly unusable, especially in certain lighting conditions.
I live in Moab, UT, a red rock desert with wide open vistas and deep rock canyons. I often leave early in the morning and drive 250 miles of mostly wide well-striped 2-lane roads to Salt Lake City. In that distance we can experience upwards of more than 25 instances of phantom braking. In the dark, oncoming headlights as far away as 200 yards (really!) can initiate sudden violent braking dropping speed from 65 mph to 40 mph in less than 2 seconds. Other times approaching bridges or guardrails, oncoming trucks (usually dark colored) or sometimes absolutely nothing will cause an event. Most but by no means all braking events occur in poor lighting or with strong side light shadows.
I've endeavored to record many "bug reports" and have force-saved dash cam video but nothing out of the ordinary shows in later reviews. I've recalibrated the cameras with no effect. Here's my personal take on what could be behind phantom braking:
1. It would make sense for Tesla's AP to use the same object recognition algorithms as FSD. When dealing with self-driving, I'm sure Tesla is going to be ultra-conservative in their assessment; they don't want to be accused of causing collisions. Hence, braking is deemed preferable to incorrect analysis leading to a potentially fatal accident. (Although phantom braking can and likely will lead to rear end collisions.)
2. The forward looking cameras used for distance in our MY appear to be spaced no wider apart than human eyes, maybe less. In every other vehicle I've owned with "adaptive speed control" the traffic aware cameras have been spaced upwards of 10"-12" apart. This wider spacing offers far better distance/range analysis. Tesla is counting on their camera quality and range finding technology - but it's not there yet.
Anyway, neither of these conditions are likely to be resolved anytime soon so I end up driving my high tech automobile as if it was 1960.
I agree completely. As a software developer myself I appreciate the complexities involved in dynamic real-time graphic analysis based solely on limited and variable video data. It seems unfortunate that Tesla apparently doesn't solicit owners' video and functional "black box" data (with the owner's explicit permission, of course) to serve as beta test information. I know you can create a "bug report" by making the verbal command, "bug report - phantom braking" which supposedly captures vehicle data, including video, for later download at your next service visit. But making a service visit appointment for phantom braking is useless.On the long road trip I recently took with TACC, there were many no-reason braking incidents, but I didn't notice any messages about emergency vehicles. I also tried to engage my problem-solving brain to figure out the causes of the braking, but there seemed to be no consistent thread. Sometimes no traffic nearby, no overpasses with shadows, sometimes there was traffic nearby... I really could not find a pattern before I turned it off and one-pedaled it the rest of the way.
I would accept "dumb" cruise control right now.
As has been pointed out, this used to work much better. I'm guessing we are caught in the wash of the massive merge of city and highway FSD code that apparently happened recently, and much was made worse for us highway drivers. I thought I would avoid a lot of this "bleeding edge of technology" pain by not choosing FSD, but apparently FSD's bleeding edge has caught up with me anyway.
I really hope this is worked out by the Spring - I am considering my next major road trip then. Somehow I am not buying Elon's current "so much better in 2 weeks" statements. I'm a software guy. Spring might be doable, but I am becoming convinced it won't be fixed by Christmas.
I know there is no marketing department, but does Tesla ever acknowledge problems like this? I like to believe they read these forums (I would if I were them) but it'd be good to know we are heard. And yes, I am pretty sure this is a problem a service center can't do a thing about.
Have recalibrated multiple times without noticeable effect. Minimal phantom braking on interstates and whenever an "extra" lane such as passing lane is between an oncoming semi and me. Also, I often use TACC to help hold slow speed limits (25-30 mph) in town with no phantom braking evident. extreme phantom braking prevalent as previously described at 55mph or higher on wide, well-striped, two-lane highways with long range visibility.For those of you having issues, try recalibrating your cameras.
Curious - as a beta tester, are you able to provide feedback for events like this?I got some phantom braking using FSDbeta 10.3.1 last night.
1) A car was passing on the right and my Tesla braked hard which slowed me from from ~55 to 45 mph.
2) There was another coasting slow-down right as I was going through a clear intersection.
Curious - as a beta tester, are you able to provide feedback for events like this?
Not it didn't. I'm sure that's what it felt like, but those numbers don't work. Best case braking for passenger tires on warm, dry pavement (and this is winter, and there's snow on the ground in VA!) is about 0.7G, or 15 mph/sec. Getting down 35 mph thus takes a little more than two full seconds, with the ABS fully engaged and hearing rubber squealing at the edges of your grip. It didn't take you two seconds to get your foot to the pedal; typical reaction time in an emergency is about 1/4 to 1/8th of that.my car decelerated hard from 75 to 40 mph before I hit the accelerator