4 ms·
The hardware folks picked fancy stuff that was not intended for automotive use. Look up the screen yellowing for an example — no manufacturer would sell a scree
by amluto 6y ago
The hardware folks picked fancy stuff that was not intended for automotive use. Look up the screen yellowing for an example — no manufacturer would sell a screen in the size Tesla wanted that was rated for hot car interior temperatures, so Tesla went with one that wasn’t.
- rektide 6y ago1.4 drive writes per day is a shit ton of a lot of writes to hit a drive with daily. this is a computational not an automotive concern, & a pretty frelling heinous oversight at that.
- o-__-o 6y agoTo be expected when not-a-car company makes cars :) (For instance GM has a strict list of test scenarios for their onstar integration)
- maxerickson 6y agoThey still screw up. I like this example because it's their infotainment screen failing prematurely: https://cadillacsociety.com/2019/10/28/second-lawsuit-filed-over-cadillac-cue-screen-issues/ https://cadillacsociety.com/2019/10/28/second-lawsuit-filed-...
- o-__-o 6y agoSure but that’s not a software issue, that’s poor material selection
- amluto 6y agoI wonder if a “cycle” is actually a full drive write. If it is, then they have ~11GB/day, which is nuts, at least in the pre-dashcam models. But I can easily imagine that a cheap eMMC part has poor wear leveling and eats a “cycle” after much less than 8GB.
- NathanielK 6y agoIt's not, the issue was there is no wear leveling, so it's 1.4 writes per day. This is approximately 2 trips a day, 5 days a week. Reading between the lines I believe the car "eats into" the 3000-5000 cycles everytime it is cycled on.