• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer

Microcontroller Tips

Microcontroller engineering resources, new microcontroller products and electronics engineering news

  • Products
    • 8-bit
    • 16-bit
    • 32-bit
    • 64-bit
  • Applications
    • 5G
    • Automotive
    • Connectivity
    • Consumer Electronics
    • EV Engineering
    • Industrial
    • IoT
    • Medical
    • Security
    • Telecommunications
    • Wearables
    • Wireless
  • Learn
    • eBooks / Tech Tips
    • EE Training Days
    • FAQs
    • Learning Center
    • Tech Toolboxes
    • Webinars/Digital Events
  • Resources
    • Design Guide Library
    • DesignFast
    • LEAP Awards
    • Podcasts
    • White Papers
  • Videos
    • EE Videos & Interviews
    • Teardown Videos
  • EE Forums
    • EDABoard.com
    • Electro-Tech-Online.com
  • Engineering Training Days
  • Advertise
  • Subscribe

The danger of treating autonomous vehicle control as a solved problem

August 4, 2017 By Lee Teschler Leave a Comment

LEE TESCHLER EXECUTIVE EDITOR

A panelist made an interesting comment during the recently concluded TU-Automotive connected car conference near Detroit. It happened during one of the many sessions devoted to software infrastructure and connected services.

“In Silicon Valley, autonomous vehicle control and driving is viewed as a solved problem. The Leland-Teschlerreal emphasis is on making use of the associated data for connected services,” said a speaker from a software start-up.

What was noteworthy about this comment was the smug tone with which it was delivered. But the self-satisfied nature of it seems out-of-whack in that statistics show a self-driving car failed roughly every three hours in California during 2016. This data comes from the state’s Dept. of Motor Vehicles. Carmakers testing self-driving cars in California must file annual “disengagement” reports with the state showing how many times their vehicles malfunctioned. The definition of a disengagement includes every time a human driver has to quickly grab the controls, either because of hardware or software failure or because the driver sees a problem.

The reports cite 2,578 failures among the nine firms that conducted road-testing in 2016. The total autonomous miles driven aren’t impressive, coming in at a little under 657,000 with the vast majority of those miles accumulated by Google-parent Alphabet’s spin-out company Waymo. For comparison, Tesla’s Elon Musk has estimated that worldwide regulatory approval of driverless vehicles will require something on the order of six billion miles of data.

It’s probably safe to say that most people engaged in autonomous vehicle development see nothing sinister about the number of reported disengagements. None of this year’s disengagements resulted in an accident. And it is clear that some of them happened during tests of subsystems. Bosch and Delphi, for example, — both Tier One automotive suppliers — were at the top of the disengagement list. It’s likely their engineers were using city streets to get real-world performance data for R & D projects, not ironing out the last few bugs in prototypes.

Nevertheless, the results cited in the California report don’t inspire confidence about the reliability of autonomous systems. This is particularly so because some autonomous vehicle developers have a loose idea of what constitutes a disengagement. Waymo’s definition, for example, doesn’t include every time a human driver is forced to take over. It’s disengagement count – just 124 in its 60 self-driving cars during 2016 — only includes incidents where something unsafe would have happened if the human driver weren’t there. In contrast to what it reports, Waymo admits its drivers have to go hands-on many thousands of times annually.

Critics claim these results indicate the technology isn’t ready for prime time and won’t be for the foreseeable future. They also note that at least one firm – Uber – stopped a self-driving pilot program in San Francisco in favor of running tests in Arizona and Pennsylvania, states where failure reports aren’t required. Such tactics have bloggers questioning whether it makes sense to unleash autonomous technology on public streets at this stage of the game. Says one about autopilot systems, “Drivers should not be Guinea pigs and misled into a false sense of confidence.”

Which brings us back to the comments made during the TU-Automotive show. People in self-driving vehicle technology do themselves no favors when they come across as cavalier about the shortcomings of current autonomous systems. Nobody needs the perception that a traffic accident involving a self-driving vehicle is just a bug report incident for software engineers.

You may also like:


  • Sensing is key to autonomous operation

  • Researchers find a way to confuse autonomous vehicle cameras
  • edge_case_predictions
    Simulations help explain why autonomous vehicles do stupid things

Filed Under: Applications, Automotive, Featured, Lee's blog Tagged With: bosch, delphi, tesla, uber, waymo

Reader Interactions

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

Featured Contributions

Five challenges for developing next-generation ADAS and autonomous vehicles

Securing IoT devices against quantum computing risks

RISC-V implementation strategies for certification of safety-critical systems

What’s new with Matter: how Matter 1.4 is reshaping interoperability and energy management

Edge AI: Revolutionizing real-time data processing and automation

More Featured Contributions

EE TECH TOOLBOX

“ee
Tech Toolbox: Internet of Things
Explore practical strategies for minimizing attack surfaces, managing memory efficiently, and securing firmware. Download now to ensure your IoT implementations remain secure, efficient, and future-ready.

EE Learning Center

EE Learning Center

EE ENGINEERING TRAINING DAYS

engineering
“bills
“microcontroller
EXPAND YOUR KNOWLEDGE AND STAY CONNECTED
Get the latest info on technologies, tools and strategies for EE professionals.

RSS Current EDABoard.com discussions

  • How can I get the frequency please help!
  • 12VAC to 12VDC 5A on 250ft 12AWG
  • ILI9163 LCD driver
  • Elektronik devre
  • Powering a USB hub: safely distributing current from a shared power supply

RSS Current Electro-Tech-Online.com Discussions

  • 100uF bypass Caps?
  • Fuel Auto Shutoff
  • Actin group needed for effective PCB software tutorials
  • how to work on pcbs that are thick
  • compatible eth ports for laptop

DesignFast

Design Fast Logo
Component Selection Made Simple.

Try it Today
design fast globle

Footer

Microcontroller Tips

EE World Online Network

  • 5G Technology World
  • EE World Online
  • Engineers Garage
  • Analog IC Tips
  • Battery Power Tips
  • Connector Tips
  • DesignFast
  • EDA Board Forums
  • Electro Tech Online Forums
  • EV Engineering
  • Power Electronic Tips
  • Sensor Tips
  • Test and Measurement Tips

Microcontroller Tips

  • Subscribe to our newsletter
  • Advertise with us
  • Contact us
  • About us

Copyright © 2025 · WTWH Media LLC and its licensors. All rights reserved.
The material on this site may not be reproduced, distributed, transmitted, cached or otherwise used, except with the prior written permission of WTWH Media.

Privacy Policy