Boeingpilot
Member
I'll add my tale of woe.....
Purchased a 2015 S90D several months ago. First inkling of issues was driving home from work (180 mile). Being a new car (to me) started to examine all the streaming audio options. Noticed after 20 minutes responsiveness of the MCU became worse and worse. Also noticed LTE not available indications. Outside air temperature on IC showed dashes. Then a 'flash', black screen and almost 3 - 4 minutes for the MCU to spontaneously reboot. Chalked that up to a random reboot. 10 days later, selecting Spotify MCU locked up, and got IC warnings of autopilot and cruise inop. Auto highbeams stopped working. Had to manually reboot to gain control. Fast forward 12 days, opened door to car and MCU reboots. Then 4 days later driving to work, set streaming and started to get extremely sluggish response, LTE with slash through it. Then the FUN starts. Car is on autosteer on the turnpike. Screen reboots and then I get alert chimes followed by aggressive automatic braking!! Next day driving home, MCU locks up and auto reboots. So... Lets see, in the course of a month 5 reboots. Tesla did examine remotely, said I was and I quote "Found internal memory running low. Cleared several file caches, freeing up a significant amount of memory for application processing."
This was after the first two reboots. The remote tech indicated that the MCU has been replaced prior to my ownership.
My observations
- This is starting to become a safety issue. The car should not be slamming on its brakes from 70 mph
- Yes the MCU was probably replaced, but my guess, with the old 8g eMMC. So a lot of good that does
- The nVidia Tegra was probably more than adequate for the older software loads. I believe that the amount of stuff the latest loads are straining the whole MCU, not just the eMMC chips
- I agree with Akikiki, Tesla is doing triage. But I also think they are denying a more fundamental problem with the MCU1.
- I know that I am, and would recommend to everyone, open a service call with Tesla every other time the MCU shows problems. I'm starting to show a pattern so when it comes push come to shove, I can show Tesla, hey, this thing's been having issues for weeks (months)
Don't get me wrong, I love the car, and I got a terrific deal on it. But, this is bush league. Tesla is no longer a startup. The Model S is a mature design now. Just like Tesla had to step up to the plate and address drive unit failures on early RWD Model Ss, they need to step up to the plate and admit they have a huge problem with the MCU1 on the S and X. While I purchased the vehicle used, I expect certain things to work reliably. While Tesla says this is 'only' the infotainment system, the reality the MCU is a major computer in the car. Problems with it can cause safety issues. The fact that it happens to control the entertainment is purely coincidental.
It's just a matter of time before a accident occurs that will be traced to the MCUs. If they think they have public relation problems with HV batteries having fires, just think what it will be like if some loss of functionality on a failing MCU causes an accident.
Purchased a 2015 S90D several months ago. First inkling of issues was driving home from work (180 mile). Being a new car (to me) started to examine all the streaming audio options. Noticed after 20 minutes responsiveness of the MCU became worse and worse. Also noticed LTE not available indications. Outside air temperature on IC showed dashes. Then a 'flash', black screen and almost 3 - 4 minutes for the MCU to spontaneously reboot. Chalked that up to a random reboot. 10 days later, selecting Spotify MCU locked up, and got IC warnings of autopilot and cruise inop. Auto highbeams stopped working. Had to manually reboot to gain control. Fast forward 12 days, opened door to car and MCU reboots. Then 4 days later driving to work, set streaming and started to get extremely sluggish response, LTE with slash through it. Then the FUN starts. Car is on autosteer on the turnpike. Screen reboots and then I get alert chimes followed by aggressive automatic braking!! Next day driving home, MCU locks up and auto reboots. So... Lets see, in the course of a month 5 reboots. Tesla did examine remotely, said I was and I quote "Found internal memory running low. Cleared several file caches, freeing up a significant amount of memory for application processing."
This was after the first two reboots. The remote tech indicated that the MCU has been replaced prior to my ownership.
My observations
- This is starting to become a safety issue. The car should not be slamming on its brakes from 70 mph
- Yes the MCU was probably replaced, but my guess, with the old 8g eMMC. So a lot of good that does
- The nVidia Tegra was probably more than adequate for the older software loads. I believe that the amount of stuff the latest loads are straining the whole MCU, not just the eMMC chips
- I agree with Akikiki, Tesla is doing triage. But I also think they are denying a more fundamental problem with the MCU1.
- I know that I am, and would recommend to everyone, open a service call with Tesla every other time the MCU shows problems. I'm starting to show a pattern so when it comes push come to shove, I can show Tesla, hey, this thing's been having issues for weeks (months)
Don't get me wrong, I love the car, and I got a terrific deal on it. But, this is bush league. Tesla is no longer a startup. The Model S is a mature design now. Just like Tesla had to step up to the plate and address drive unit failures on early RWD Model Ss, they need to step up to the plate and admit they have a huge problem with the MCU1 on the S and X. While I purchased the vehicle used, I expect certain things to work reliably. While Tesla says this is 'only' the infotainment system, the reality the MCU is a major computer in the car. Problems with it can cause safety issues. The fact that it happens to control the entertainment is purely coincidental.
It's just a matter of time before a accident occurs that will be traced to the MCUs. If they think they have public relation problems with HV batteries having fires, just think what it will be like if some loss of functionality on a failing MCU causes an accident.