zanary
Active Member
I'd pay $1500 to upgrade from MCU1 to MCU2. Though I think I should get some kind of discount because I have the yellow-screen-of-death around the edges. So Telsa will have to replace the screen for free as soon as they get the new screens (hopefully this summer).
Not too sure they will give you a credit. They will swap out your Yellow display once the new ones are available. Then the retrofit will swap out everything once it becomes available. Just a guess on my part.
I am taking the my car for a MCU check up at the service center today. One issue are the yellow borders - I'll ask to have the screen replaced but there is more ... curious if anyone has found this strange correlation.
A week ago on Sunday 4/7/19 the MCU started rebooting frequently ... as in every 3-5 minutes. I must have had probably 7-9 reboots on a drive. Kinda makes the climate control tricky while it's rebooting frequently .... I tried removing the USB for dash cam, running different audio source (radio, slacker, phone), nav, no-nav, noa, not noa and these variations yielded identical outcomes. I parked the car at the destination of the drive and did the power off cycle. Waited 2-3 minutes, tapped the brakes. Everything was up. Started driving back and 3-5 min into the drive ....another reboot ... and a couple more on the way home.
Later it just got stuck in a reboot loop - blank screen, then the T logo, then blank screen, then T logo, etc. After about 3-4 of these it just went blank. So I thought, ok, that's it, it's kaput. Something changed - hardware failed, software changed in some way, or perhaps some data was corrupt someplace.
Tried calling Tesla support. Sunday, closed. F*
My home FW sends an 8am update of In/Out traffic for the past 24 hrs. I noticed two things: the car had received something on Sat 4/6/2019 or Sun 4/7/2019 before 8am. 15.3Mb of bits *sent to* the car. On Monday after 8AM I noticed that 58Mb were *sent to* the car.
So ... decided to reboot the MCU by doing the 2 finger salute on the wheel. The T came on ... booted OK.... and .... has been working without any issues since then.
When the MCU booted I called Tesla Support. I had told them what happened the previous day. They said my car was working great and there were no signs of any reboots or trouble with the MCU the prior day (wtf?) No, they said, everything is "green" and working great.
My working theory is that something went to the car on Sat->Sun that broke the MCU on Sunday and something went to the car Sun->Mon that fixed it. Skipping the facts that the MCU appeared to be kaput on Sunday (blank screen after the T) the car still received something on Sun->Mon night and somehow fixed it.
Thoughts ?
I wrote this in the context of asking for an MCU upgrade today too. Stay tuned.
The reboot of the MCU/1 are a common occurrence with the 2019.8.x and 2019.12 updates. They are aware of them. When you get a reboot, always do a Bug Report as those logs will give them sufficient data. I've been working with them for the past two weeks on the reboot, doing multiple Bug Reports for them every time it reboots. Two ways to do a Bug Report - Use the voice command and say "Bug Report <description>", or Tap+Hold the Car icon on the bottom left of the screen until you see "Thank you for submitting Feedback", on your instrument cluster. Both send a bug report.
My MCU was becoming super sluggish with constant lockups and even the trip and energy meters had quit working. I took it to my local service center and discussed it with a tech. He suggested a full reset to factory settings and completely reset everything in the car. He did that and that seems to have fixed my problems.
Sluggist is a problem of all the new capabilities (DashCam + Sentry Mode) since 2018.50.x. Either further code optimization can fix some of this while we wait for the MCU/2 retrofit program to start.