Top Myths of Robocars (and why V2V is not the answer)
There's been a lot of press on robocars in the last few months, and a lot of new writers expressing views. Reading this, I have encountered a recurring set of issues and concerns, so I've prepared an article outlining these top myths and explaining why they are not true.
Perhaps of strongest interest will be one of the most frequent statements -- that Vehicle to Vehicle (V2V) communication is important, or even essential, to the deployment of robocars. The current V2V (and Vehicle to Infrastructure) efforts, using the DSRC radio spec are quite extensive, and face many challenges, but to the surprise of many, this is largely orthogonal to the issues around robocars.
So please read The top 10 (or so) myths or robocars.
- They won't be safe
- The big issue is who will be liable in a crash
- The cars will need special dedicated roads and lanes
- This only works when all cars are robocars and human driving is banned
- We need radio links between cars to make this work
- We wont see self-driving cars for many decades
- It is a long time before this will be legal
- How will the police give a robocar a ticket?
- People will never trust software to drive their car
- They can't make an OS that doesn't crash, how can they make a safe car?
- We need the car to be able to decide between hitting a schoolbus and going over a cliff
- The cars will always go at the speed limit
You may note that this is not my first myths FAQ, as I also have Common objections to Robocars written when this site was built. Only one myth is clearly in both lists, a sign of how public opinion has been changing.