While very few details have come out, Reuters reports that new proposed congressional bills on self-driving cars will reverse many of the provisions I critiqued in the NHTSA regulations last year.
Recently we’ve seen a series of startups arise hoping to make robocars with just computer vision, along with radar. That includes recently unstealthed AutoX, the off-again, on again efforts of comma.ai and at the non-startup end, the dedication of Tesla to not use LIDAR because it wants to sell cars today before LIDARs can be bought at automotive quantities and prices.
California published its summary of all the reports submitted by vendors testing robocars in the state. You can read the individual reports. They are interesting, but several other outlines have created summaries of the reports calculating things like the number of interventions per mile. On these numbers, Google’s lead is extreme. Of over 600,000 autonomous miles driven by the various teams, Google/Waymo was 97% of them — in other words, 30 times as much as everybody else put together.
NHTSA released the report from their Office of Defects Investigation on the fatal Tesla crash in Florida last spring. It’s a report that is surprisingly favorable to Tesla. So much so that even I am surprised.
Oxbotica, a UK technology company with a focus on mobile robotics and driverless vehicles, has created Selenium, an autonomous software system acting similar to a ‘brain’ for a vehicle. Selenium can work in pedestrianised environments as well as roads and motorways, and is not reliant on GPS to operate – meaning it can transition between indoor and outdoor settings, overground or underground. The system has been developed to be “vehicle agnostic” and can be applied to cars, self-driving pods (e.g. for campuses and airports), and warehouse truck fleets.
Some people have wondered about my forecast in the spreadsheet on robotaxi economics about the very low parking costs I have predicted. I wrote about most of the reasons for this in my 2007 essay on Robocar Parking, but let me expand and add some modern notes here.
Michigan’s Senate are reviewing several bills related to automated driving. SB995, 996, 997, and 998 are now out of committee, and SB 927 and 928 are not far behind. These bills seem to be a mixed bag. Critically, they are in desperate need of clarification followed by thoughtful discussion.
Editor’s note: Please note that this article refers to the versions that came out of the senate before moving to the house, where they have been slightly modified.
The long awaited list of recommendations and potential regulations for robocars has just been released by the National Highway Traffic Safety Administration (NHTSA), the federal agency that regulates car safety and safety issues in car manufacture. Normally, NHTSA does not regulate car technology before it is released into the market, and the agency, while it says it is wary of slowing down this safety-increasing technology, has decided to do the unprecedented — and at a whopping 115 pages.
At the recent AUVSI/TRB conference in San Francisco, there was talk of upcoming regulation, particularly from NHTSA. Secretary of Transportation Foxx and his NHTSA staff spoke with just vague hints about what might come in the proposals due this fall. Generally, they said good things, namely that they are wary of slowing down the development of the technology. But they said things that suggest other directions.
At the recent AUVSI/TRB symposium, a popular research topic was platooning for robocars and trucks. Platooning is perhaps the oldest practical proposal when it comes to car automation because you can have the lead vehicle driven by a human, even a specially trained one, and thus, resolve all the problems that come from road situations too complex for software to easily handle.
October 16, 2018
Need help spreading the word?
Join the Robohub crowdfunding page and increase the visibility of your campaign
