Sorry Bill, You made my case for me. "* If you think about it, how would _anyone_ be able to, *since the device that could record the incident data was off-line at the time it happened and this was the root cause of the incident?"
My point exactly. "If he says it happened, I completely believe it happened." * I just want real numbers, not conjecture*. Not saying the comments are wrong, just that it sounds like BS. And it does. The plural of anecdote is not data. I would not quote what Mark wrote without seeing what it is based on. I am not trying to be an a$$. Not saying anyone else is an a$$. Returning to the original topic. The problem with self driving is when the computer gets a glitch, it drops out and the vehicle goes straight, usually into a tree on a curvy road (happened to my friend last year and previous year to his wife in a Tesla3)." My understanding is that the driver can always override, so this curvy road business could have been a matter of driver not on board to do their job. We need to balance this out with the positive notes. Was the unconscious guy whose car delivered him to the ER he was trying to reach after a heart attack - was that not a mitigation of some sort? If the empirical evidence was to show that a tenth of the accidents and fatalities are experienced with autonomous vehicles, I would like that very much. I don't know where those numbers come from either. So I like them equally well - not at all. On Fri, Feb 4, 2022 at 6:51 PM Bill Dube via EV <[email protected]> wrote: > Michael - > > How, exactly, would Mark be able to provide "factual data" on this > incident? If you think about it, how would _anyone_ be able to, since > the device that could record the incident data was off-line at the time > it happened and this was the root cause of the incident? Mark speculated > that it was quite possible that other similar "glitches" have caused > other similar unrecorded incidents. > > I have known Mark for more than 20 years and have found him utterly > truthful and reliable. If he says it happened, I completely believe it > happened. > > Also, I can envision how this could easily happen and how it would > completely escape the notice of Tesla. On commercial airplanes, they > have two (2) separate flight computers, using two different brand CPUs, > using two completely "firewalled" separate teams of code developers for > their flight computers. The two systems continuously monitor each other > for faults and warn the pilots when they see any divergence in flight > control between the computers. There are two _other_ separate systems > recording flight data as well. They do this because peoples lives depend > on these systems working perfectly and continuously. There is no similar > multiple redundancy in Tesla. _YOU_ are the redundancy that they are > depending on to take over if there is a computer glitch. > > "The world is an imperfect place. Screws fall out." (Quote from > "The Breakfast Club.") > > Bill D. > > On 2/5/2022 11:08 AM, Michael Ross via EV wrote: > > Mark, Can you show me where this anecdotal information might be gathered > as > > factual data? I have become very wary of information that is not > > attributed to some source that I can trust. No offence intended. > > > > On Fri, Feb 4, 2022 at 4:38 PM Mark Hanson via EV <[email protected]> > wrote: > > > >> Tesla should just drop the whole self driving thing and just focus on a > >> great electric car. My Tesla Y was the only EV I could find with towing > >> capacity for my H20 ski boat and an excellent nationwide charging > network. > >> The problem with self driving is when the computer gets a glitch, it > drops > >> out and the vehicle goes straight, usually into a tree on a curvy road > >> (happened to my friend last year and previous year to his wife in a > >> Tesla3). Of course when the computer drops out it doesn’t record the > crash > >> as a self driving error. How convenient for Tesla. The actual crash > rate > >> is much higher than recorded. > >> Best regards > >> Mark > >> > >> Sent from my iPhone > >> _______________________________________________ > >> Address messages to [email protected] > >> No other addresses in TO and CC fields > >> UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub > >> ARCHIVE: http://www.evdl.org/archive/ > >> LIST INFO: http://lists.evdl.org/listinfo.cgi/ev-evdl.org > >> > > > > _______________________________________________ > Address messages to [email protected] > No other addresses in TO and CC fields > UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub > ARCHIVE: http://www.evdl.org/archive/ > LIST INFO: http://lists.evdl.org/listinfo.cgi/ev-evdl.org > -- Michael E. Ross (919) 585-6737 Land (919) 901-2805 Cell and Text (919) 576-0824 <https://www.google.com/voice/b/0?pli=1#phones> Tablet, Google Phone and Text -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.evdl.org/private.cgi/ev-evdl.org/attachments/20220204/8f10bd1e/attachment.html> _______________________________________________ Address messages to [email protected] No other addresses in TO and CC fields UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub ARCHIVE: http://www.evdl.org/archive/ LIST INFO: http://lists.evdl.org/listinfo.cgi/ev-evdl.org
