Tag Archives: robotics

Tesla’s Latest FSD Beta Doesn’t Seem Ready For Public Use, Which Raises Big Questions

What I like about this test is that it presents a very good mix of everyday, normal driving situations in an environment with a good mix of traffic density, road complexity, lighting conditions, road markings, and more. In short, reality, the same sort of entropy-heavy reality all of us live in and where we expect our machines to work.

There’s a lot that FSD does that’s impressive when you consider that this is an inert mass of steel and rubber and silicon that’s effectively driving on its own through a crowded city. We’ve come a long way since Stanley the Toureg finished the DARPA Challenge back in 2006, and there’s so much to be impressed by.

At the same time, this FSD beta proves to be a pretty shitty driver, at least in this extensive test session.

Anyone arguing that FSD in its latest state drives better than a human is either delusional, high from the fumes of their own raw ardor for Elon Musk or needs to find better-driving humans to hang out with.

FSD drives in a confusing, indecisive way, making all kinds of peculiar snap decisions and generally being hard to read and predict to other drivers around them. Which is a real problem.

Advertisement

Drivers expect a certain baseline of behaviors and reactions from the cars around them. That means there’s not much that’s more dangerous to surrounding traffic than an unpredictable driver, which this machine very much is.

And that’s when it’s driving at least somewhat legally; there are several occasions in this video where traffic laws were actually broken, including two instances of the car attempting to drive the wrong way down a street and into oncoming traffic.

Advertisement

Nope, not great.

In the comments, many people have criticized Kyle, the driver/supervisor, for allowing the car to make terrible driving decisions instead of intervening. The reasoning for this ranges from simple Tesla-fan-rage to the need for disengagements to help the system learn, to concern that by not correcting the mistakes, Kyle is potentially putting people in danger.

Advertisement

They’re also noting that the software is very clearly unfinished and in a beta state, which, is pretty clearly true as well.

These are all reasonable points. Well, the people just knee-jerk shielding Elon’s Works from any scrutiny aren’t reasonable, but the other points are, and they bring up bigger issues.

Advertisement

Specifically, there’s the fundamental question about whether or not it makes sense to test an unfinished self-driving system on public roads, surrounded by people, in or out of other vehicles, that did not agree to participate in any sort of beta testing of any kind.

You could argue that a student driver is a human equivalent of beta testing our brain’s driving software, though when this is done in any official capacity, there’s a professional driving instructor in the car, sometimes with an auxiliary brake pedal, and the car is often marked with a big STUDENT DRIVER warning.

Advertisement

Image for article titled Tesla's Latest FSD Beta Doesn't Seem Ready For Public Use, Which Raises Big Questions
Image: JDT/Tesla/YouTUbe

I’ve proposed the idea of some kind of warning lamp for cars under machine control, and I still think that’s not a bad idea, especially during the transition era we find ourselves in.

Advertisement

Of course, in many states, you can teach your kid to drive on your own without any special permits. That context is quite similar to FSD beta drivers since they don’t have any special training beyond a regular driver’s license (and no, Tesla’s silly Safety Score does not count as special training).

In both cases, you’re dealing with an unsure driver who may not make good decisions, and you may need to take over at a moment’s notice. On an FSD-equipped Tesla (or really any L2-equipped car), taking over should be easy, in that your hands and other limbs should be in position on the car’s controls, ready to take over.

Advertisement

In the case of driving with a kid, this is less easy, though still possible. I know because I was once teaching a girlfriend of the time how to drive and had to take control of a manual old Beetle from the passenger seat. You can do it, but I don’t recommend it.

Of course, when you’re teaching an uncertain human, you’re always very, very aware of the situation and nothing about it would give you a sense of false confidence that could allow your attention to waver. This is a huge problem with Level 2 semi-automated systems, though, and one I’ve discussed at length before.

Advertisement

As far as whether or not the FSB beta needs driver intervention to “learn” about all the dumb things it did wrong, I’m not entirely sure this is true. Tesla has mentioned the ability to learn in “shadow mode” which would eliminate the need for FSD to be active to learn driving behaviors by example.

As far as Kyle’s willingness to let FSD beta make its bad decisions, sure, there are safety risks, but it’s also valuable to see what it does to give an accurate sense of just what the system is capable of. He always stepped in before things got too bad, but I absolutely get that this in no way represents safe driving.

Advertisement

At the same time, showing where the system fails helps users of FSD have a better sense of the capabilities of what they’re using so they can attempt to understand how vigilant they must be.

This is all really tricky, and I’m not sure yet of the best practice solution here.

Advertisement

This also brings up the question of whether Tesla’s goals make sense in regard to what’s known as their Operational Design Domain (ODD), which is just a fancy way of saying “where should I use this?”

Tesla has no restrictions on their ODD, as referenced in this tweet:

Advertisement

This raises a really good point: should Tesla define some sort of ODD?

I get that their end goal is Level 5 full, anywhere, anytime autonomy, a goal that I think is kind of absurd. Full Level 5 is decades and decades away. If Tesla freaks are going to accuse me of literally having blood on my hands for allegedly delaying, somehow, the progress of autonomous driving, then you’d think the smartest move would be to restrict the ODD to areas where the system is known to work better (highways, etc) to allow for more automated deployment sooner.

Advertisement

That would make the goal more Level 4 than 5, but the result would be, hopefully, safer automated vehicle operation, and, eventually, safer driving for everyone.

Trying to make an automated vehicle work everywhere in any condition is an absolutely monumental task, and there’s still so so much work to do. Level 5 systems are probably decades away, at best. Restricted ODD systems may be able to be deployed much sooner, and maybe Tesla should be considering doing that, just like many other AV companies (Waymo, Argo, and so on) are doing.

Advertisement

We’re still in a very early transition period on this path to autonomy, however that turns out. Videos like these, that show real-world behavior of such systems, problems and all, are very valuable, even if we’re still not sure on the ethics of making them.

All I know is that now is the time to question everything, so don’t get bullied by anyone.

GM And Cruise Want Ford To Stop Calling Its Hands-Free Driving Technology “BlueCruise”

Image for article titled GM And Cruise Want Ford To Stop Calling Its Hands-Free Driving Technology "BlueCruise"

Photo: JEFF KOWALSKY / AFP (Getty Images)

General Motors is not happy with Ford’s driver-assistance technology name, Reuters reports. Why? Because BlueCruise, Ford’s tech, sounds too much like GM’s Super Cruise and Hyper Cruise, its own driver-assistance technologies, and Cruise, its robo-taxi service subsidiary.

Advertisement

Both Ford’s BlueCruise and GM’s Super and Hyper Cruise systems are base-level autonomous driving technologies that would allow drivers to lift their hands from the steering wheel while still being alert. These technologies aren’t fully self-driving, but they’re what the SAE would term a level-2 tech, which allows the car to do a little bit of heavy lifting while the driver can relax — while still being alert, of course.

“While GM had hoped to resolve the trademark infringement matter with Ford amicably, we were left with no choice but to vigorously defend our brands and protect the equity our products and technology have earned over several years in the market,” GM said in its statement.

Ford has argued that GM and Cruise’s claim is “meritless and frivolous” because “drivers for decades have understood what cruise control is, every automaker offers it, and ‘cruise’ is common shorthand for the capability.”

Basically, Ford is calling BlueCruise a kind of advanced cruise control, which isn’t totally accurate but also not totally wrong.

GM, on the other hand, has argued that automated driving is definitely not cruise control, so Ford can’t use the word “cruise” to describe it. Because GM got there first. GM is arguing that Ford intentionally named its technology BlueCruise to create a sense of confusion between the brands and to capitalize on all the hard marketing work GM has done.

Ford is still arguing that other automakers have used the word “cruise” for decades to refer to a variety of other technologies and simple acts people engage in behind the wheel.

Advertisement

Ford announced BlueCruise in April of 2021, which will be available in the Mustang Mach-E and F-150 later this year through over-the-air updates at a cost of $600 for three years of service.

For GREAT deals on a new or used Nissan check out Nissan of Van Nuys TODAY!