Doug
OR, ref your No 2, to use one as a terrorist weapon (a “suicide” bomb, but without the suicide bit = more “gain”, less “pain”, to the “user” that is L). BTW: apart from the “smart” energy meters now installed here, I can’t see me installing any IoT stuff in the foreseeable future – don’t need it anyway –, and I have no intention/inclination whatsoever, nor the money, to purchase/lease an automated vehicle. John E Allen W.London, UK From: Doug Powell [mailto:[email protected]] Sent: 06 November 2016 02:17 To: [email protected] Subject: [PSES] Automated vehicles. Although it's Saturday, I'll use this as my Friday Question. In light of two recent reports in the InComplisnce Magazine. I feel prompted to ask if anyone on this forum can address a couple of questions. http://incompliancemag.com/u-s-dot-releases-federal-policy-on-automated-vehicles/ http://incompliancemag.com/uber-self-driving-truck-delivers-budweiser-beer/ Aside from the obvious concerns about vehicle safety, it occurs to me that there two problem that presently are missing in recent media reporting. In particular for the Level 4 & 5 vehicles as described by the SAE and DOT report. 1) I understand that these vehicles, such as the fully automated Budwiser truck have avoidance systems. Given the human condition of today, I foresee the distinct possibility of drivers in other vehicles "playing around" in such a way as to try and force a response from the avoidance algorithms and cause these vehicles to crash themselves. This kind of sport would be exactly what some types would enjoy. What sort of preventative measures have been taken in this regard? 2) Given the lack of attention to hacking we have already witnessed in the Internet of Things (IoT) crowd, how are the driverless vehicle people doing with regard to the cyber security of these vehicles. That is, is it conceivable that someone may try to hack the truck's operating system and hijack it? Thanks all, doug -- Douglas E Powell [email protected] http://www.linkedin.com/in/dougp01 - ---------------------------------------------------------------- This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. To post a message to the list, send your e-mail to <[email protected]> All emc-pstc postings are archived and searchable on the web at: http://www.ieee-pses.org/emc-pstc.html Attachments are not permitted but the IEEE PSES Online Communities site at http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used formats), large files, etc. Website: http://www.ieee-pses.org/ Instructions: http://www.ieee-pses.org/list.html (including how to unsubscribe) <http://www.ieee-pses.org/list.html> List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <[email protected]> Mike Cantwell <[email protected]> For policy questions, send mail to: Jim Bacher <[email protected]> David Heald <[email protected]> - ---------------------------------------------------------------- This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. To post a message to the list, send your e-mail to <[email protected]> All emc-pstc postings are archived and searchable on the web at: http://www.ieee-pses.org/emc-pstc.html Attachments are not permitted but the IEEE PSES Online Communities site at http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used formats), large files, etc. Website: http://www.ieee-pses.org/ Instructions: http://www.ieee-pses.org/list.html (including how to unsubscribe) List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <[email protected]> Mike Cantwell <[email protected]> For policy questions, send mail to: Jim Bacher: <[email protected]> David Heald: <[email protected]>
