News

Not really. "Self drive mode" isn't the name of either of the driving systems, that could be either Autopilot or the Full Self Driving beta. The spokesperson was for the police department, not Tesla. They're unlikely to know there is a difference between the two systems, like most people.

It's at best, secondhand info from the driver, and most likely him saying he was on the phone and the car was driving, which would be the same thing they likely said with either system running. I doubt the driver is explaining differences between AP and FSD to the police.

It is simple, it depends on what the vehicle is using to actually process other vehicles to maintain distance from.

These systems process a lot of information, and a lot of it is pretty bad data that needs to be cleaned to remove erroneous readings before it can be processed. Sensors stream a lot of info, and not all of it is perfectly accurate. The same is true for a Tesla or any other vehicle, and filtering that data accurately means a better experience.

Say your vehicle has a forward facing radar, and you're driving along the highway and the radar gets a return for a large object in front of the car 100 feet ahead when the returns immediately before were showing a 300 foot clear zone. Is it more likely that a large object suddenly appeared in front of the car, or that this return is erroneous and the next few returns after will show a clear zone again? Overhead signs and overpasses can show similar returns to a large truck in your lane for instance. This is one advantage lidar has over radar, more accurate angle measurements at all distances.

So say the vehicle acts on that return and slam on the brakes because the "object" is only 100 feet ahead at highway speeds. Then the erroneous return goes away and there's a clear road again. That's the "phantom braking" I'm sure you've seen various people talk about. The system reacting to an erroneous return instead of filtering it out as a bad reading. Now random braking in the middle of a highway is dangerous as well, need to minimize that. Is it more likely a massive wall suddenly appeared directly in front of the car, or that it's a couple bad readings? The car has to determine that to make a decision on what to do. And different types of sensors will detect things differently. To some sensors, materials like paper are essentially invisible for instance but metal is clear as day. If the sensor can't detect something, it won't react.

Note that these readings do not involve a camera at all. They inherently work differently than a human driver does by looking at the road. So many people online want to point out that sensors are more "reliable" or "trustworthy" compared to vision since there's little processing, you just get a data point, yet sensors will provide bad data often enough that it needs to have a filter to remove bad data. A camera works like a person, it can see everything, you just need to teach it to ide tify what it needs to pay attention to, and what it can ignore, like the sky, or power lines, or trees passing by on the side of the road. But not the human on the side of the road, need to see that.

Then we get into the fact that various sensors exist on older vehicles that have been removed from newer ones. Things like radar and ultrasonic sensors have been removed in favor of using computer vision via the cameras directly, like a human driver watching the road. Going frame by frame to categorize what it sees for vehicles, people, cones, lanes, etc. and comparing to previous frames to extrapolate things like motion, movement, and relative speed. But with cameras you have issues with things like lights blinding them, just like a bright light blinds a person. Maybe the camera can't see for some reason, like a light shining directly in the lens. It takes a little time for it to try and adjust exposure to compensate for a bright light shining directly in the lens.

You might suggest using as many sensors as possible then, but that makes it nearly impossible to actually make a decision then. Sensor integration is a huge data processing issue. how do you determine what data to accept and what to ignore when you get conflicting results from different types of sensors? This is why Tesla is trying to just do it all via vision. One type of sensor, roughly equivalent to a human but with wider visual spectrum sensitivity. Just classify what's in each frame and act on it. Simple implementation, just needs A LOT of data to train it in as many situations as possible.

And that camera is where we get to emergency vehicles specifically. In my opinion, these emergency vehicle accidents are likely the camera being blinded repeatedly by the emergency lights rotating and the camera shifting exposure up and down every second or so to try and maintain an image it can actually process. As a human, at night, those lights make it hard for even me to see the rest of the road.

It's not like regular drivers never crash into emergency vehicles either, they just don't make national news, just like the 33 car fires every hour in the US alone.

It's not a simple thing, and even your "simple" car by comparison is doing a lot to filter the data it gets. It could be using completely different kinds of data than another vehicle for that cruise control, so given the right circumstances it may react differently.

For what it's worth, my Model 3 has rarely had issues with Autopilot acting in any sort of dangerous manner. A few phantom braking issues back when I got it in 2018, but I haven't had a single one of those in maybe 4 years now, even in areas where it would almost always react that way back when I got it. Sometimes a little lane weirdness with old poorly marked lane lines, or even old lane lines visible in addition to the current ones in some areas. It's pretty easy to tell the situations AP might have issues with once you're used it just a few times.

Is that the actual time cutoff? My 2018 model 3 that came with Enhanced Autopilot was originally said to have the hardware necessary for FSD (Computer 2.5 the car says), but there were updates before FSD became actually available.

I never considered buying it so I never paid more than cursory attention to all of the different hardware revisions, only major ones like Computer 3, removing radar during parts shortages around COVID, the Ultrasonic sensors, etc.

Also I hadn't realized that it had actually been that long since I bought it, without most of the regular time-based car maintenance like oil changes time has flown by with it. Or that production had ramped up so significantly since I got my Model 3. I knew it had ramped obviously and that the Model Y launched, but I didn't realize how significant all of that actually was when added together.

You seem to have missed the simple fact that there are cars produced prior to that. And the fact that the hardware announced there also wasn't enough on its own. There were additional changes in 2019 to a newer computer necessary for FSD. My 2018 Model 3 has that hardware, but I cannot get FSD without a computer upgrade. Not to mention even older vehicles that can't even accept the new computer hardware.

So yeah, not ALL Teslas in the road are capable of FSD.