4 ms·

>That would be like if the CD player in my ICE car broke This is not an apt analogy at all. In a Tesla, there is no separate dashboard or control so it's not a

>That would be like if the CD player in my ICE car broke This is not an apt analogy at all. In a Tesla, there is no separate dashboard or control so it's not an optional part like a CD player. It would be more like saying that your transmission failed. It just happens that, because it doesn't need all the other mechanical parts, an EV's "transmission" is the same box that runs the radio, AC, etc.

umvi 7y ago
Well that is a massive engineering fail to decide to make the "infotainment" system tightly coupled with critical car functionality. A good engineering team would have decoupled them. In an ICE car half of your dashboard could be non functional (climate control completely broken, etc) and the car will still drive because the two systems are decoupled.
- dkonofalski 7y ago
  >a massive engineering fail It's not the infotainment part that causes the failure, though. It's the firmware flash chip which happens to be in the same board as the infotainment array. It's not like the radio breaking would cause the car to stop working. Again, this is more akin to the transmission going out. It's just easy to make this sound like an engineering failure because of that. It's similar to saying that the new Google Pixel has a "massive engineering failure" because the "Ok, Google" voice assistant breaks. It's disingenuous to say that because all that happens on the security module. You wouldn't want someone to have access to your phone if the security module breaks but, if that breaks, it also breaks the voice assistant functionality. This phrasing makes it sound like a fault in the voice assistant can block access to the entire phone which is intentionally misleading.
  - umvi 7y ago
    It's a coupling engineering failure no matter how you spin it. Diagnostic logging should be stored on a separate (re: decoupled) flash chip. If that flash chip wears out, the car should still drive. Something is too tightly coupled right now, as evidenced by the existence of the article.

umvi 7y ago

Well that is a massive engineering fail to decide to make the "infotainment" system tightly coupled with critical car functionality. A good engineering team would have decoupled them. In an ICE car half of your dashboard could be non functional (climate control completely broken, etc) and the car will still drive because the two systems are decoupled.

dkonofalski 7y ago
>a massive engineering fail It's not the infotainment part that causes the failure, though. It's the firmware flash chip which happens to be in the same board as the infotainment array. It's not like the radio breaking would cause the car to stop working. Again, this is more akin to the transmission going out. It's just easy to make this sound like an engineering failure because of that. It's similar to saying that the new Google Pixel has a "massive engineering failure" because the "Ok, Google" voice assistant breaks. It's disingenuous to say that because all that happens on the security module. You wouldn't want someone to have access to your phone if the security module breaks but, if that breaks, it also breaks the voice assistant functionality. This phrasing makes it sound like a fault in the voice assistant can block access to the entire phone which is intentionally misleading.
- umvi 7y ago
  It's a coupling engineering failure no matter how you spin it. Diagnostic logging should be stored on a separate (re: decoupled) flash chip. If that flash chip wears out, the car should still drive. Something is too tightly coupled right now, as evidenced by the existence of the article.